We well check the build numbers and see if that can be fixed - but as per Deployment Guide, when you extend the ScaleIO system with a new element, all the packages (including LIA and SDC) will be pushed to it from the IM - can you clarify whether your Windows host already had LIA and SDC installed manually? Can you see this problem if you simply upload appropriate .msi packages to the IM and try to add a "clean" Windows system to the cluster?
the installation was performed completely from IM.
The three linux hosts are Ubuntu Linux 16.04 (MDM Primary + SDS, MDM Slave + SDS, TB + SDS)
The SDC are two Windows 2012 R2
The package uploaded to the gateway were all taken from the official distribution package ScaleIO_2.0.1.0_Complete_Software_Download.zip downloaded from support.emc.com.
The first step performed from the gateway was the installation a new system with a complete CSV. The CSV was configured only to deploy packages/roles on the three Linux hosts.
The second step performed from the gateway was an "add to existing sys" of the first Windows SDC. That operation succeeded because the query phase check the available infrastructure and the LIA on the three windows hosts is at the same version. During this step is deployed the version mismatched LIA package to the windows host + SDC.
The third step was an "add to existing sys" of the second SDC. That operation fails because during the query phase the actually installed components are checked and the version of the LIA of the Linux hosts differs from the LIA version of the SDC installed at the second step.
That happens because in the package ScaleIO_2.0.1.0_Complete_Software_Download.zip there is a version mismatch of ScaleIO linux packages (version: 2.0-10000.2072) from the Windows (version: 2.0-10000.2075). All the ScaleIO components inside the Windows package seems newer than the Linux ones. During the query phase the LIA version is checked against all (already) deployed nodes and if there is a difference the deployment stops.
As a workaround I uninstalled manually the LIA on the Windows host added at the second step (leaving SDC installed) so the query phase succeeded (because LIA is installed only on the three Linux hosts). At this point the LIA package is redeployed on the Windows SDC added at the second step while on the new Windows SDC is deployed the LIA package + the SDC package.
Fixing the version of the packages inside the distribution package (ScaleIO_2.0.1.0_Complete_Software_Download.zip) will surely solve this problem.
I spoke with the Dev - for the time being I am afraid you will need to stick to the workaround (uninstall LIA whenever you want to extend the cluster with a Windows box - given the rest of it is running on Linux).
This behavior will be fixed in the newer ScaleIO versions - either by some IM GW configuration variable or simply by matching the build numbers, but for now it is what it is...
pawelw1
306 Posts
0
October 18th, 2016 07:00
Hi Davide,
We well check the build numbers and see if that can be fixed - but as per Deployment Guide, when you extend the ScaleIO system with a new element, all the packages (including LIA and SDC) will be pushed to it from the IM - can you clarify whether your Windows host already had LIA and SDC installed manually? Can you see this problem if you simply upload appropriate .msi packages to the IM and try to add a "clean" Windows system to the cluster?
Thanks!
Pawel
c0redump
68 Posts
0
October 18th, 2016 09:00
Hi Pawel,
the installation was performed completely from IM.
The three linux hosts are Ubuntu Linux 16.04 (MDM Primary + SDS, MDM Slave + SDS, TB + SDS)
The SDC are two Windows 2012 R2
The package uploaded to the gateway were all taken from the official distribution package ScaleIO_2.0.1.0_Complete_Software_Download.zip downloaded from support.emc.com.
The first step performed from the gateway was the installation a new system with a complete CSV. The CSV was configured only to deploy packages/roles on the three Linux hosts.
The second step performed from the gateway was an "add to existing sys" of the first Windows SDC. That operation succeeded because the query phase check the available infrastructure and the LIA on the three windows hosts is at the same version. During this step is deployed the version mismatched LIA package to the windows host + SDC.
The third step was an "add to existing sys" of the second SDC. That operation fails because during the query phase the actually installed components are checked and the version of the LIA of the Linux hosts differs from the LIA version of the SDC installed at the second step.
That happens because in the package ScaleIO_2.0.1.0_Complete_Software_Download.zip there is a version mismatch of ScaleIO linux packages (version: 2.0-10000.2072) from the Windows (version: 2.0-10000.2075). All the ScaleIO components inside the Windows package seems newer than the Linux ones. During the query phase the LIA version is checked against all (already) deployed nodes and if there is a difference the deployment stops.
As a workaround I uninstalled manually the LIA on the Windows host added at the second step (leaving SDC installed) so the query phase succeeded (because LIA is installed only on the three Linux hosts). At this point the LIA package is redeployed on the Windows SDC added at the second step while on the new Windows SDC is deployed the LIA package + the SDC package.
Fixing the version of the packages inside the distribution package (ScaleIO_2.0.1.0_Complete_Software_Download.zip) will surely solve this problem.
Thanks for your lighting fast reply!
Davide
pawelw1
306 Posts
0
October 19th, 2016 00:00
Hi Davide,
Thanks a lot for bringing this up - let me see what we can do to fix it...
Cheers,
Pawel
pawelw1
306 Posts
0
October 20th, 2016 07:00
Hi Davide,
I spoke with the Dev - for the time being I am afraid you will need to stick to the workaround (uninstall LIA whenever you want to extend the cluster with a Windows box - given the rest of it is running on Linux).
This behavior will be fixed in the newer ScaleIO versions - either by some IM GW configuration variable or simply by matching the build numbers, but for now it is what it is...
Thanks again!
Pawel