-
So you can create a pool across the 2x DCs no problem. We'll take a deeper look on telling where to replicate to avoid having everything on the same place.
-
@olivierlambert said in XOSTOR hyperconvergence preview:
So I imagine a very low latency between the 2 DCs? One pool with 6 hosts total and 3 per DC right?
For now, there's no placement preference, we need to discuss with LINBIT about topology.
And if the 2x DCs are far each other, I would advice to get 2x pools and use 2x XOSTOR total
This can be done using placement policies as outlined in the LINSTOR users guide. It will probably require a bit of extra work on XO to use those properties
-
Technically, you could use manual CLI call to do it until we expose it in XO
-
For those that might run across my questions here... there is a nice blog post at Linbit on how to span availability zones correctly to keep your data redundancy up:
https://linbit.com/blog/multi-az-replication-using-automatic-placement-rules-in-linstor/So CLI is doable
GUI would be nice in the future 
-
@Jonathon said in XOSTOR hyperconvergence preview:
@stormi said in XOSTOR hyperconvergence preview:
yum repolist
lol glad I checked then
# yum repolist Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Excluding mirror: updates.xcp-ng.org * xcp-ng-base: mirrors.xcp-ng.org Excluding mirror: updates.xcp-ng.org * xcp-ng-linstor: mirrors.xcp-ng.org Excluding mirror: updates.xcp-ng.org * xcp-ng-updates: mirrors.xcp-ng.org repo id repo name status !xcp-ng-base XCP-ng Base Repository 2,161 !xcp-ng-linstor XCP-ng LINSTOR Repository 142 !xcp-ng-updates XCP-ng Updates Repository 1,408 !zabbix/x86_64 Zabbix Official Repository - x86_64 79 !zabbix-non-supported/x86_64 Zabbix Official Repository non-supported - x86_64 6 repolist: 3,796I was wondering if anyone had any insight into this? Unable to upgrade xen hosts.
-
@Jonathon I see no issue in this output, except that you enabled zabbix mirrors which might or might not play a role in your update issue.
-
@stormi If you open a support tunnel and give me the ID in a private chat, I'll have a quick look.
-
@stormi Message sent, thanks!
No change if excluding zabbix
[13:20 ovbh-pprod-xen10 ~]# yum update --disablerepo=zabbix* Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Excluding mirror: updates.xcp-ng.org * xcp-ng-base: mirrors.xcp-ng.org Excluding mirror: updates.xcp-ng.org * xcp-ng-linstor: mirrors.xcp-ng.org Excluding mirror: updates.xcp-ng.org * xcp-ng-updates: mirrors.xcp-ng.org Resolving Dependencies --> Running transaction check ---> Package blktap.x86_64 0:3.37.4-1.0.1.0.linstor.1.xcpng8.2 will be updated ---> Package blktap.x86_64 0:3.37.4-2.1.xcpng8.2 will be an update ---> Package device-mapper-multipath.x86_64 0:0.4.9-119.xs+1.2.xcpng8.2 will be updated ---> Package device-mapper-multipath.x86_64 0:0.4.9-136.xcpng8.2 will be an update ---> Package device-mapper-multipath-libs.x86_64 0:0.4.9-119.xs+1.2.xcpng8.2 will be updated ---> Package device-mapper-multipath-libs.x86_64 0:0.4.9-136.xcpng8.2 will be an update ---> Package e2fsprogs.x86_64 0:1.42.9-12.el7_5 will be updated ---> Package e2fsprogs.x86_64 0:1.47.0-1.1.xcpng8.2 will be an update --> Processing Dependency: libfuse.so.2(FUSE_2.5)(64bit) for package: e2fsprogs-1.47.0-1.1.xcpng8.2.x86_64 --> Processing Dependency: libfuse.so.2(FUSE_2.6)(64bit) for package: e2fsprogs-1.47.0-1.1.xcpng8.2.x86_64 --> Processing Dependency: libfuse.so.2(FUSE_2.8)(64bit) for package: e2fsprogs-1.47.0-1.1.xcpng8.2.x86_64 --> Processing Dependency: libfuse.so.2()(64bit) for package: e2fsprogs-1.47.0-1.1.xcpng8.2.x86_64 ---> Package e2fsprogs-libs.x86_64 0:1.42.9-12.el7_5 will be updated ---> Package e2fsprogs-libs.x86_64 0:1.47.0-1.1.xcpng8.2 will be an update ---> Package forkexecd.x86_64 0:1.18.1-1.1.xcpng8.2 will be updated ---> Package forkexecd.x86_64 0:1.18.3-3.1.xcpng8.2 will be an update ---> Package gpumon.x86_64 0:0.18.0-4.2.xcpng8.2 will be updated ---> Package gpumon.x86_64 0:0.18.0-11.2.xcpng8.2 will be an update ---> Package grub.x86_64 1:2.02-3.1.0.xcpng8.2 will be updated ---> Package grub.x86_64 1:2.02-3.2.0.xcpng8.2 will be an update ---> Package grub-efi.x86_64 1:2.02-3.1.0.xcpng8.2 will be updated ---> Package grub-efi.x86_64 1:2.02-3.2.0.xcpng8.2 will be an update ---> Package grub-tools.x86_64 1:2.02-3.1.0.xcpng8.2 will be updated ---> Package grub-tools.x86_64 1:2.02-3.2.0.xcpng8.2 will be an update ---> Package guest-templates-json.noarch 0:1.9.6-1.2.xcpng8.2 will be updated ---> Package guest-templates-json.noarch 0:1.10.6-1.1.xcpng8.2 will be an update ---> Package guest-templates-json-data-linux.noarch 0:1.9.6-1.2.xcpng8.2 will be updated ---> Package guest-templates-json-data-linux.noarch 0:1.10.6-1.1.xcpng8.2 will be an update ---> Package guest-templates-json-data-other.noarch 0:1.9.6-1.2.xcpng8.2 will be updated ---> Package guest-templates-json-data-other.noarch 0:1.10.6-1.1.xcpng8.2 will be an update ---> Package guest-templates-json-data-windows.noarch 0:1.9.6-1.2.xcpng8.2 will be updated ---> Package guest-templates-json-data-windows.noarch 0:1.10.6-1.1.xcpng8.2 will be an update ---> Package http-nbd-transfer.x86_64 0:1.2.0-1.xcpng8.2 will be updated ---> Package http-nbd-transfer.x86_64 0:1.3.0-1.xcpng8.2 will be an update ---> Package irqbalance.x86_64 3:1.0.7-11.xcpng8.2 will be updated ---> Package irqbalance.x86_64 3:1.0.7-16.xcpng8.2 will be an update ---> Package kernel.x86_64 0:4.19.19-7.0.15.1.xcpng8.2 will be updated ---> Package kernel.x86_64 0:4.19.19-7.0.23.1.xcpng8.2 will be an update ---> Package kpartx.x86_64 0:0.4.9-119.xs+1.2.xcpng8.2 will be updated ---> Package kpartx.x86_64 0:0.4.9-136.xcpng8.2 will be an update ---> Package libcom_err.x86_64 0:1.42.9-12.el7_5 will be updated ---> Package libcom_err.x86_64 0:1.47.0-1.1.xcpng8.2 will be an update ---> Package libss.x86_64 0:1.42.9-12.el7_5 will be updated ---> Package libss.x86_64 0:1.47.0-1.1.xcpng8.2 will be an update ---> Package linux-firmware.noarch 0:20190314-5.1.xcpng8.2 will be updated ---> Package linux-firmware.noarch 0:20190314-10.2.xcpng8.2 will be an update ---> Package lldpad.x86_64 0:1.0.1-3.git036e314.xcpng8.2 will be updated ---> Package lldpad.x86_64 0:1.0.1-10.xcpng8.2 will be an update ---> Package message-switch.x86_64 0:1.23.2-3.2.xcpng8.2 will be updated ---> Package message-switch.x86_64 0:1.23.2-10.1.xcpng8.2 will be an update ---> Package microcode_ctl.x86_64 2:2.1-26.xs23.1.xcpng8.2 will be updated ---> Package microcode_ctl.x86_64 2:2.1-26.xs26.2.xcpng8.2 will be an update ---> Package nbd.x86_64 0:3.14-2.el7 will be updated ---> Package nbd.x86_64 0:3.24-1.xcpng8.2 will be an update ---> Package qemu.x86_64 2:4.2.1-4.6.2.1.xcpng8.2 will be updated ---> Package qemu.x86_64 2:4.2.1-4.6.3.1.xcpng8.2 will be an update ---> Package rrd2csv.x86_64 0:1.2.5-7.1.xcpng8.2 will be updated ---> Package rrd2csv.x86_64 0:1.2.6-8.1.xcpng8.2 will be an update ---> Package rrdd-plugins.x86_64 0:1.10.8-5.1.xcpng8.2 will be updated ---> Package rrdd-plugins.x86_64 0:1.10.9-5.1.xcpng8.2 will be an update ---> Package sm.x86_64 0:2.30.7-1.3.0.linstor.7.xcpng8.2 will be updated ---> Package sm.x86_64 0:2.30.8-7.1.xcpng8.2 will be an update ---> Package sm-cli.x86_64 0:0.23.0-7.xcpng8.2 will be updated ---> Package sm-cli.x86_64 0:0.23.0-54.1.xcpng8.2 will be an update ---> Package sm-rawhba.x86_64 0:2.30.7-1.3.0.linstor.7.xcpng8.2 will be updated ---> Package sm-rawhba.x86_64 0:2.30.8-7.1.xcpng8.2 will be an update ---> Package squeezed.x86_64 0:0.27.0-5.xcpng8.2 will be updated ---> Package squeezed.x86_64 0:0.27.0-11.1.xcpng8.2 will be an update ---> Package tzdata.noarch 0:2022a-1.el7 will be updated ---> Package tzdata.noarch 0:2023c-1.el7 will be an update ---> Package tzdata-java.noarch 0:2022a-1.el7 will be updated ---> Package tzdata-java.noarch 0:2023c-1.el7 will be an update ---> Package varstored-guard.x86_64 0:0.6.2-1.xcpng8.2 will be updated ---> Package varstored-guard.x86_64 0:0.6.2-8.xcpng8.2 will be an update ---> Package vendor-drivers.x86_64 0:1.0.2-1.3.xcpng8.2 will be updated ---> Package vendor-drivers.x86_64 0:1.0.2-1.6.xcpng8.2 will be an update --> Processing Dependency: mpi3mr-module for package: vendor-drivers-1.0.2-1.6.xcpng8.2.x86_64 --> Processing Dependency: r8125-module for package: vendor-drivers-1.0.2-1.6.xcpng8.2.x86_64 --> Processing Dependency: igc-module for package: vendor-drivers-1.0.2-1.6.xcpng8.2.x86_64 ---> Package vhd-tool.x86_64 0:0.43.0-4.1.xcpng8.2 will be updated ---> Package vhd-tool.x86_64 0:0.43.0-11.1.xcpng8.2 will be an update ---> Package wsproxy.x86_64 0:1.12.0-5.xcpng8.2 will be updated ---> Package wsproxy.x86_64 0:1.12.0-12.xcpng8.2 will be an update ---> Package xapi-core.x86_64 0:1.249.26-2.1.xcpng8.2 will be updated ---> Package xapi-core.x86_64 0:1.249.32-2.1.xcpng8.2 will be an update ---> Package xapi-nbd.x86_64 0:1.11.0-3.2.xcpng8.2 will be updated ---> Package xapi-nbd.x86_64 0:1.11.0-10.1.xcpng8.2 will be an update ---> Package xapi-storage.x86_64 0:11.19.0_sxm2-3.xcpng8.2 will be updated ---> Package xapi-storage.x86_64 0:11.19.0_sxm2-10.xcpng8.2 will be an update ---> Package xapi-storage-script.x86_64 0:0.34.1-2.1.xcpng8.2 will be updated ---> Package xapi-storage-script.x86_64 0:0.34.1-9.1.xcpng8.2 will be an update ---> Package xapi-tests.x86_64 0:1.249.26-2.1.xcpng8.2 will be updated ---> Package xapi-tests.x86_64 0:1.249.32-2.1.xcpng8.2 will be an update ---> Package xapi-xe.x86_64 0:1.249.26-2.1.xcpng8.2 will be updated ---> Package xapi-xe.x86_64 0:1.249.32-2.1.xcpng8.2 will be an update ---> Package xcp-networkd.x86_64 0:0.56.2-1.xcpng8.2 will be updated ---> Package xcp-networkd.x86_64 0:0.56.2-8.xcpng8.2 will be an update ---> Package xcp-ng-linstor.noarch 0:1.0-1.xcpng8.2 will be updated ---> Package xcp-ng-linstor.noarch 0:1.1-3.xcpng8.2 will be an update --> Processing Dependency: sm-linstor for package: xcp-ng-linstor-1.1-3.xcpng8.2.noarch ---> Package xcp-ng-release.x86_64 0:8.2.1-6 will be updated ---> Package xcp-ng-release.x86_64 0:8.2.1-10 will be an update ---> Package xcp-ng-release-config.x86_64 0:8.2.1-6 will be updated ---> Package xcp-ng-release-config.x86_64 0:8.2.1-10 will be an update ---> Package xcp-ng-release-linstor.noarch 0:1.2-1.xcpng8.2 will be updated ---> Package xcp-ng-release-linstor.noarch 0:1.3-1.xcpng8.2 will be an update ---> Package xcp-ng-release-presets.x86_64 0:8.2.1-6 will be updated ---> Package xcp-ng-release-presets.x86_64 0:8.2.1-10 will be an update ---> Package xcp-ng-xapi-plugins.noarch 0:1.7.2-1.0.0.linstor.1.xcpng8.2 will be updated ---> Package xcp-ng-xapi-plugins.noarch 0:1.8.0-1.xcpng8.2 will be an update ---> Package xcp-rrdd.x86_64 0:1.33.0-6.1.xcpng8.2 will be updated ---> Package xcp-rrdd.x86_64 0:1.33.2-7.1.xcpng8.2 will be an update ---> Package xen-dom0-libs.x86_64 0:4.13.5-9.30.3.xcpng8.2 will be updated ---> Package xen-dom0-libs.x86_64 0:4.13.5-9.38.3.xcpng8.2 will be an update ---> Package xen-dom0-tools.x86_64 0:4.13.5-9.30.3.xcpng8.2 will be updated ---> Package xen-dom0-tools.x86_64 0:4.13.5-9.38.3.xcpng8.2 will be an update ---> Package xen-hypervisor.x86_64 0:4.13.5-9.30.3.xcpng8.2 will be updated ---> Package xen-hypervisor.x86_64 0:4.13.5-9.38.3.xcpng8.2 will be an update ---> Package xen-libs.x86_64 0:4.13.5-9.30.3.xcpng8.2 will be updated ---> Package xen-libs.x86_64 0:4.13.5-9.38.3.xcpng8.2 will be an update ---> Package xen-tools.x86_64 0:4.13.5-9.30.3.xcpng8.2 will be updated ---> Package xen-tools.x86_64 0:4.13.5-9.38.3.xcpng8.2 will be an update ---> Package xenopsd.x86_64 0:0.150.12-1.2.xcpng8.2 will be updated ---> Package xenopsd.x86_64 0:0.150.17-2.1.xcpng8.2 will be an update ---> Package xenopsd-cli.x86_64 0:0.150.12-1.2.xcpng8.2 will be updated ---> Package xenopsd-cli.x86_64 0:0.150.17-2.1.xcpng8.2 will be an update ---> Package xenopsd-xc.x86_64 0:0.150.12-1.2.xcpng8.2 will be updated ---> Package xenopsd-xc.x86_64 0:0.150.17-2.1.xcpng8.2 will be an update ---> Package xs-openssl-libs.x86_64 1:1.1.1k-6.1.xcpng8.2 will be updated ---> Package xs-openssl-libs.x86_64 1:1.1.1k-9.1.xcpng8.2 will be an update --> Running transaction check ---> Package fuse-libs.x86_64 0:2.9.2-10.xcpng8.2 will be installed ---> Package igc-module.x86_64 0:5.10.200-1.xcpng8.2 will be installed ---> Package mpi3mr-module.x86_64 0:8.6.1.0.0-1.xcpng8.2 will be installed ---> Package r8125-module.x86_64 0:9.012.03-1.xcpng8.2 will be installed ---> Package xcp-ng-linstor.noarch 0:1.1-3.xcpng8.2 will be an update --> Processing Dependency: sm-linstor for package: xcp-ng-linstor-1.1-3.xcpng8.2.noarch --> Finished Dependency Resolution Error: Package: xcp-ng-linstor-1.1-3.xcpng8.2.noarch (xcp-ng-updates) Requires: sm-linstor You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest -
@Jonathon Ok, here's the solution, and the explanation:
First, just update
xcp-ng-release-linstor. This will update the repository file for linstor-related RPMs to make it point to a newer repository, located at a different place.Then updating the rest of the system will become possible again.
-
Unfortunately does not look like that works. Unless I am doing something wrong.
[12:26 ovbh-pprod-xen10 ~]# yum update xcp-ng-release-linstor Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Excluding mirror: updates.xcp-ng.org * xcp-ng-base: mirrors.xcp-ng.org Excluding mirror: updates.xcp-ng.org * xcp-ng-linstor: mirrors.xcp-ng.org Excluding mirror: updates.xcp-ng.org * xcp-ng-updates: mirrors.xcp-ng.org Resolving Dependencies --> Running transaction check ---> Package xcp-ng-release-linstor.noarch 0:1.2-1.xcpng8.2 will be updated ---> Package xcp-ng-release-linstor.noarch 0:1.3-1.xcpng8.2 will be an update --> Finished Dependency Resolution Dependencies Resolved ========================================================================================================================================================================================================================================================================================== Package Arch Version Repository Size ========================================================================================================================================================================================================================================================================================== Updating: xcp-ng-release-linstor noarch 1.3-1.xcpng8.2 xcp-ng-updates 4.0 k Transaction Summary ========================================================================================================================================================================================================================================================================================== Upgrade 1 Package Total download size: 4.0 k Is this ok [y/d/N]: y Downloading packages: Delta RPMs disabled because /usr/bin/applydeltarpm not installed. xcp-ng-release-linstor-1.3-1.xcpng8.2.noarch.rpm | 4.0 kB 00:00:00 Running transaction check Running transaction test Transaction test succeeded Running transaction Updating : xcp-ng-release-linstor-1.3-1.xcpng8.2.noarch 1/2 Cleanup : xcp-ng-release-linstor-1.2-1.xcpng8.2.noarch 2/2 Verifying : xcp-ng-release-linstor-1.3-1.xcpng8.2.noarch 1/2 Verifying : xcp-ng-release-linstor-1.2-1.xcpng8.2.noarch 2/2 Updated: xcp-ng-release-linstor.noarch 0:1.3-1.xcpng8.2 Complete! [12:26 ovbh-pprod-xen10 ~]# yum update Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Excluding mirror: updates.xcp-ng.org * xcp-ng-base: mirrors.xcp-ng.org Excluding mirror: updates.xcp-ng.org * xcp-ng-updates: mirrors.xcp-ng.org Resolving Dependencies --> Running transaction check ---> Package blktap.x86_64 0:3.37.4-1.0.1.0.linstor.1.xcpng8.2 will be updated ---> Package blktap.x86_64 0:3.37.4-2.1.xcpng8.2 will be an update ---> Package device-mapper-multipath.x86_64 0:0.4.9-119.xs+1.2.xcpng8.2 will be updated ---> Package device-mapper-multipath.x86_64 0:0.4.9-136.xcpng8.2 will be an update ---> Package device-mapper-multipath-libs.x86_64 0:0.4.9-119.xs+1.2.xcpng8.2 will be updated ---> Package device-mapper-multipath-libs.x86_64 0:0.4.9-136.xcpng8.2 will be an update ---> Package e2fsprogs.x86_64 0:1.42.9-12.el7_5 will be updated ---> Package e2fsprogs.x86_64 0:1.47.0-1.1.xcpng8.2 will be an update --> Processing Dependency: libfuse.so.2(FUSE_2.5)(64bit) for package: e2fsprogs-1.47.0-1.1.xcpng8.2.x86_64 --> Processing Dependency: libfuse.so.2(FUSE_2.6)(64bit) for package: e2fsprogs-1.47.0-1.1.xcpng8.2.x86_64 --> Processing Dependency: libfuse.so.2(FUSE_2.8)(64bit) for package: e2fsprogs-1.47.0-1.1.xcpng8.2.x86_64 --> Processing Dependency: libfuse.so.2()(64bit) for package: e2fsprogs-1.47.0-1.1.xcpng8.2.x86_64 ---> Package e2fsprogs-libs.x86_64 0:1.42.9-12.el7_5 will be updated ---> Package e2fsprogs-libs.x86_64 0:1.47.0-1.1.xcpng8.2 will be an update ---> Package forkexecd.x86_64 0:1.18.1-1.1.xcpng8.2 will be updated ---> Package forkexecd.x86_64 0:1.18.3-3.1.xcpng8.2 will be an update ---> Package gpumon.x86_64 0:0.18.0-4.2.xcpng8.2 will be updated ---> Package gpumon.x86_64 0:0.18.0-11.2.xcpng8.2 will be an update ---> Package grub.x86_64 1:2.02-3.1.0.xcpng8.2 will be updated ---> Package grub.x86_64 1:2.02-3.2.0.xcpng8.2 will be an update ---> Package grub-efi.x86_64 1:2.02-3.1.0.xcpng8.2 will be updated ---> Package grub-efi.x86_64 1:2.02-3.2.0.xcpng8.2 will be an update ---> Package grub-tools.x86_64 1:2.02-3.1.0.xcpng8.2 will be updated ---> Package grub-tools.x86_64 1:2.02-3.2.0.xcpng8.2 will be an update ---> Package guest-templates-json.noarch 0:1.9.6-1.2.xcpng8.2 will be updated ---> Package guest-templates-json.noarch 0:1.10.6-1.1.xcpng8.2 will be an update ---> Package guest-templates-json-data-linux.noarch 0:1.9.6-1.2.xcpng8.2 will be updated ---> Package guest-templates-json-data-linux.noarch 0:1.10.6-1.1.xcpng8.2 will be an update ---> Package guest-templates-json-data-other.noarch 0:1.9.6-1.2.xcpng8.2 will be updated ---> Package guest-templates-json-data-other.noarch 0:1.10.6-1.1.xcpng8.2 will be an update ---> Package guest-templates-json-data-windows.noarch 0:1.9.6-1.2.xcpng8.2 will be updated ---> Package guest-templates-json-data-windows.noarch 0:1.10.6-1.1.xcpng8.2 will be an update ---> Package http-nbd-transfer.x86_64 0:1.2.0-1.xcpng8.2 will be updated ---> Package http-nbd-transfer.x86_64 0:1.3.0-1.xcpng8.2 will be an update ---> Package irqbalance.x86_64 3:1.0.7-11.xcpng8.2 will be updated ---> Package irqbalance.x86_64 3:1.0.7-16.xcpng8.2 will be an update ---> Package kernel.x86_64 0:4.19.19-7.0.15.1.xcpng8.2 will be updated ---> Package kernel.x86_64 0:4.19.19-7.0.23.1.xcpng8.2 will be an update ---> Package kpartx.x86_64 0:0.4.9-119.xs+1.2.xcpng8.2 will be updated ---> Package kpartx.x86_64 0:0.4.9-136.xcpng8.2 will be an update ---> Package libcom_err.x86_64 0:1.42.9-12.el7_5 will be updated ---> Package libcom_err.x86_64 0:1.47.0-1.1.xcpng8.2 will be an update ---> Package libss.x86_64 0:1.42.9-12.el7_5 will be updated ---> Package libss.x86_64 0:1.47.0-1.1.xcpng8.2 will be an update ---> Package linux-firmware.noarch 0:20190314-5.1.xcpng8.2 will be updated ---> Package linux-firmware.noarch 0:20190314-10.2.xcpng8.2 will be an update ---> Package lldpad.x86_64 0:1.0.1-3.git036e314.xcpng8.2 will be updated ---> Package lldpad.x86_64 0:1.0.1-10.xcpng8.2 will be an update ---> Package message-switch.x86_64 0:1.23.2-3.2.xcpng8.2 will be updated ---> Package message-switch.x86_64 0:1.23.2-10.1.xcpng8.2 will be an update ---> Package microcode_ctl.x86_64 2:2.1-26.xs23.1.xcpng8.2 will be updated ---> Package microcode_ctl.x86_64 2:2.1-26.xs26.2.xcpng8.2 will be an update ---> Package nbd.x86_64 0:3.14-2.el7 will be updated ---> Package nbd.x86_64 0:3.24-1.xcpng8.2 will be an update ---> Package qemu.x86_64 2:4.2.1-4.6.2.1.xcpng8.2 will be updated ---> Package qemu.x86_64 2:4.2.1-4.6.3.1.xcpng8.2 will be an update ---> Package rrd2csv.x86_64 0:1.2.5-7.1.xcpng8.2 will be updated ---> Package rrd2csv.x86_64 0:1.2.6-8.1.xcpng8.2 will be an update ---> Package rrdd-plugins.x86_64 0:1.10.8-5.1.xcpng8.2 will be updated ---> Package rrdd-plugins.x86_64 0:1.10.9-5.1.xcpng8.2 will be an update ---> Package sm.x86_64 0:2.30.7-1.3.0.linstor.7.xcpng8.2 will be updated ---> Package sm.x86_64 0:2.30.8-7.1.xcpng8.2 will be an update ---> Package sm-cli.x86_64 0:0.23.0-7.xcpng8.2 will be updated ---> Package sm-cli.x86_64 0:0.23.0-54.1.xcpng8.2 will be an update ---> Package sm-rawhba.x86_64 0:2.30.7-1.3.0.linstor.7.xcpng8.2 will be updated ---> Package sm-rawhba.x86_64 0:2.30.8-7.1.xcpng8.2 will be an update ---> Package squeezed.x86_64 0:0.27.0-5.xcpng8.2 will be updated ---> Package squeezed.x86_64 0:0.27.0-11.1.xcpng8.2 will be an update ---> Package tzdata.noarch 0:2022a-1.el7 will be updated ---> Package tzdata.noarch 0:2023c-1.el7 will be an update ---> Package tzdata-java.noarch 0:2022a-1.el7 will be updated ---> Package tzdata-java.noarch 0:2023c-1.el7 will be an update ---> Package varstored-guard.x86_64 0:0.6.2-1.xcpng8.2 will be updated ---> Package varstored-guard.x86_64 0:0.6.2-8.xcpng8.2 will be an update ---> Package vendor-drivers.x86_64 0:1.0.2-1.3.xcpng8.2 will be updated ---> Package vendor-drivers.x86_64 0:1.0.2-1.6.xcpng8.2 will be an update --> Processing Dependency: mpi3mr-module for package: vendor-drivers-1.0.2-1.6.xcpng8.2.x86_64 --> Processing Dependency: r8125-module for package: vendor-drivers-1.0.2-1.6.xcpng8.2.x86_64 --> Processing Dependency: igc-module for package: vendor-drivers-1.0.2-1.6.xcpng8.2.x86_64 ---> Package vhd-tool.x86_64 0:0.43.0-4.1.xcpng8.2 will be updated ---> Package vhd-tool.x86_64 0:0.43.0-11.1.xcpng8.2 will be an update ---> Package wsproxy.x86_64 0:1.12.0-5.xcpng8.2 will be updated ---> Package wsproxy.x86_64 0:1.12.0-12.xcpng8.2 will be an update ---> Package xapi-core.x86_64 0:1.249.26-2.1.xcpng8.2 will be updated ---> Package xapi-core.x86_64 0:1.249.32-2.1.xcpng8.2 will be an update ---> Package xapi-nbd.x86_64 0:1.11.0-3.2.xcpng8.2 will be updated ---> Package xapi-nbd.x86_64 0:1.11.0-10.1.xcpng8.2 will be an update ---> Package xapi-storage.x86_64 0:11.19.0_sxm2-3.xcpng8.2 will be updated ---> Package xapi-storage.x86_64 0:11.19.0_sxm2-10.xcpng8.2 will be an update ---> Package xapi-storage-script.x86_64 0:0.34.1-2.1.xcpng8.2 will be updated ---> Package xapi-storage-script.x86_64 0:0.34.1-9.1.xcpng8.2 will be an update ---> Package xapi-tests.x86_64 0:1.249.26-2.1.xcpng8.2 will be updated ---> Package xapi-tests.x86_64 0:1.249.32-2.1.xcpng8.2 will be an update ---> Package xapi-xe.x86_64 0:1.249.26-2.1.xcpng8.2 will be updated ---> Package xapi-xe.x86_64 0:1.249.32-2.1.xcpng8.2 will be an update ---> Package xcp-networkd.x86_64 0:0.56.2-1.xcpng8.2 will be updated ---> Package xcp-networkd.x86_64 0:0.56.2-8.xcpng8.2 will be an update ---> Package xcp-ng-linstor.noarch 0:1.0-1.xcpng8.2 will be updated ---> Package xcp-ng-linstor.noarch 0:1.1-3.xcpng8.2 will be an update --> Processing Dependency: sm-linstor for package: xcp-ng-linstor-1.1-3.xcpng8.2.noarch ---> Package xcp-ng-release.x86_64 0:8.2.1-6 will be updated ---> Package xcp-ng-release.x86_64 0:8.2.1-10 will be an update ---> Package xcp-ng-release-config.x86_64 0:8.2.1-6 will be updated ---> Package xcp-ng-release-config.x86_64 0:8.2.1-10 will be an update ---> Package xcp-ng-release-presets.x86_64 0:8.2.1-6 will be updated ---> Package xcp-ng-release-presets.x86_64 0:8.2.1-10 will be an update ---> Package xcp-ng-xapi-plugins.noarch 0:1.7.2-1.0.0.linstor.1.xcpng8.2 will be updated ---> Package xcp-ng-xapi-plugins.noarch 0:1.8.0-1.xcpng8.2 will be an update ---> Package xcp-rrdd.x86_64 0:1.33.0-6.1.xcpng8.2 will be updated ---> Package xcp-rrdd.x86_64 0:1.33.2-7.1.xcpng8.2 will be an update ---> Package xen-dom0-libs.x86_64 0:4.13.5-9.30.3.xcpng8.2 will be updated ---> Package xen-dom0-libs.x86_64 0:4.13.5-9.38.3.xcpng8.2 will be an update ---> Package xen-dom0-tools.x86_64 0:4.13.5-9.30.3.xcpng8.2 will be updated ---> Package xen-dom0-tools.x86_64 0:4.13.5-9.38.3.xcpng8.2 will be an update ---> Package xen-hypervisor.x86_64 0:4.13.5-9.30.3.xcpng8.2 will be updated ---> Package xen-hypervisor.x86_64 0:4.13.5-9.38.3.xcpng8.2 will be an update ---> Package xen-libs.x86_64 0:4.13.5-9.30.3.xcpng8.2 will be updated ---> Package xen-libs.x86_64 0:4.13.5-9.38.3.xcpng8.2 will be an update ---> Package xen-tools.x86_64 0:4.13.5-9.30.3.xcpng8.2 will be updated ---> Package xen-tools.x86_64 0:4.13.5-9.38.3.xcpng8.2 will be an update ---> Package xenopsd.x86_64 0:0.150.12-1.2.xcpng8.2 will be updated ---> Package xenopsd.x86_64 0:0.150.17-2.1.xcpng8.2 will be an update ---> Package xenopsd-cli.x86_64 0:0.150.12-1.2.xcpng8.2 will be updated ---> Package xenopsd-cli.x86_64 0:0.150.17-2.1.xcpng8.2 will be an update ---> Package xenopsd-xc.x86_64 0:0.150.12-1.2.xcpng8.2 will be updated ---> Package xenopsd-xc.x86_64 0:0.150.17-2.1.xcpng8.2 will be an update ---> Package xs-openssl-libs.x86_64 1:1.1.1k-6.1.xcpng8.2 will be updated ---> Package xs-openssl-libs.x86_64 1:1.1.1k-9.1.xcpng8.2 will be an update ---> Package zabbix-agent.x86_64 0:7.0.0-alpha3.release1.el7 will be updated ---> Package zabbix-agent.x86_64 0:7.0.0-beta1.release1.el7 will be an update --> Running transaction check ---> Package fuse-libs.x86_64 0:2.9.2-10.xcpng8.2 will be installed ---> Package igc-module.x86_64 0:5.10.200-1.xcpng8.2 will be installed ---> Package mpi3mr-module.x86_64 0:8.6.1.0.0-1.xcpng8.2 will be installed ---> Package r8125-module.x86_64 0:9.012.03-1.xcpng8.2 will be installed ---> Package xcp-ng-linstor.noarch 0:1.1-3.xcpng8.2 will be an update --> Processing Dependency: sm-linstor for package: xcp-ng-linstor-1.1-3.xcpng8.2.noarch --> Finished Dependency Resolution Error: Package: xcp-ng-linstor-1.1-3.xcpng8.2.noarch (xcp-ng-updates) Requires: sm-linstor You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest -
Looks like the package is listed twice?
[12:32 ovbh-pprod-xen10 ~]# yum update xcp-ng-linstor Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Excluding mirror: updates.xcp-ng.org * xcp-ng-base: mirrors.xcp-ng.org Excluding mirror: updates.xcp-ng.org * xcp-ng-updates: mirrors.xcp-ng.org Resolving Dependencies --> Running transaction check ---> Package xcp-ng-linstor.noarch 0:1.0-1.xcpng8.2 will be updated ---> Package xcp-ng-linstor.noarch 0:1.1-3.xcpng8.2 will be an update --> Processing Dependency: sm-linstor for package: xcp-ng-linstor-1.1-3.xcpng8.2.noarch --> Finished Dependency Resolution Error: Package: xcp-ng-linstor-1.1-3.xcpng8.2.noarch (xcp-ng-updates) Requires: sm-linstor You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest[12:34 ovbh-pprod-xen10 ~]# yum list [...] xcp-networkd.x86_64 0.56.2-8.xcpng8.2 xcp-ng-updates xcp-networkd-debuginfo.x86_64 0.56.2-8.xcpng8.2 xcp-ng-updates xcp-ng-generic-lib-devel.x86_64 1.1.1-3.xcpng8.2 xcp-ng-base xcp-ng-linstor.noarch 1.1-3.xcpng8.2 xcp-ng-updates xcp-ng-release.x86_64 8.2.1-10 xcp-ng-updates xcp-ng-release-config.x86_64 8.2.1-10 xcp-ng-updates [...]Seems like the old package is just stuck there and is a duplicate version
[12:34 ovbh-pprod-xen10 ~]# yum remove xcp-ng-linstor.noarch 0:1.0-1 Loaded plugins: fastestmirror No Match for argument: 0:1.0-1 Resolving Dependencies --> Running transaction check ---> Package xcp-ng-linstor.noarch 0:1.0-1.xcpng8.2 will be erased --> Finished Dependency Resolution Dependencies Resolved =========================================================================================================================================================================================================================================================================================================================================================================================================================================== Package Arch Version Repository Size =========================================================================================================================================================================================================================================================================================================================================================================================================================================== Removing: xcp-ng-linstor noarch 1.0-1.xcpng8.2 @xcp-ng-linstor 0.0 Transaction Summary =========================================================================================================================================================================================================================================================================================================================================================================================================================================== Remove 1 Package Installed size: 0 Is this ok [y/N]: -
I don't see any duplicates in this output.
---> Package xcp-ng-linstor.noarch 0:1.0-1.xcpng8.2 will be updated ---> Package xcp-ng-linstor.noarch 0:1.1-3.xcpng8.2 will be an updateThis lists the current package, then the one which will update it.
-
The problem was yum cache. If I did yum update right after
yum update xcp-ng-release-linstorit would still fail. To get it working right away did the followingyum update xcp-ng-release-linstor yum clean all yum update -
Some questions about XOSTOR
Storage between the servers is not shared as a large file system like Gluster. Right?
So for example, each 4 hosts has 2TB storage then the max HD space is 2TB (widely)Is the NIC speed of the storage network important? Is 2x40G on each server for this overkill?
What software raid on the NVME disks is recommended?
/Christian
-
@Chr57 I'm no XOSTOR expert, but AFAIK the total available space will depend on the replication factor.
-
Storage between the servers is not shared as a large file system like Gluster. Right?
So for example, each 4 hosts has 2TB storage then the max HD space is 2TBAs @stormi mentioned, this depends on your replication factor. It works like this for your example:
Total Space = (No of Hosts x Storage ) / Replication Factor
(Assuming you have same storage on all nodes)Eg. replication factor is 2, then :
Total Space = (4 x 2)/2 = 4 TB
Note:
What you have to keep in mind though is it also depends on each SSD you have so say if you put 1.5 TB SSD & 0.5 TB SSD, then although you have 2TB on each node, but if you create a VM with 1TB space, you will not be able to create another VM with 1TB since there will not be enough contiguous space. What it means is that XOSTOR will not split the VM disk on two separate drives in case of JBOD.
In case of Raid 0 at bios level, you may be able to get away with this but Raid 0 is not recommended.Is the NIC speed of the storage network important? Is 2x40G on each server for this overkill?
The question is generic and it actually depends on your workload and SSD speed (Gen4 or Gen5 or if you have an old Gen1). At the outset 2x40G seems to be more than enough for most applications. If you have a an old Gen1 SSD or SATA SSD, then you might not even reach the full bandwidth in case of 2x40GB (practically speaking).
What software raid on the NVME disks is recommended?
For going production with Nvme SSDs, I would not recommend RAID at all ! JBOD would work just fine.(Assuming your are using generic applications)
-
Hello to you,
I am new to the XOSTOR solution,
I followed the instructions to build an SR XOSTOR, except that unfortunately I have been stuck for 2-3 weeks on an error when creating the SR, below is my error:
Error code: SR_BACKEND_FAILURE_5006
Error parameters: , LINSTOR SR creation error [opterr=Could not create SPxcp-sr-linstor_groupon nodeDEV-XCP02: The satellite does not support the device provider LVM],here is the command I run: xe sr-create type=linstor name-label=XOSTOR host-uuid=52c3a2bb-50a8-4700-a232-6e535e24d759 device-config:group-name=linstor_group device-config:redundancy=2 shared =true device-config:provisioning=thick
thank you in advance for your help, and this great project
-
Hi,
I am actually new to XOSTOR and I have very basic questions to begin with.
Does it support only Pools ? Can we attach such SR on many independent XCP-ng hosts?Thanks again for this incredible project.
-
Hi,
It works only at pool level, the only way have coordination between hosts and knowing which host have the lock on which VM. This is essential to avoid booting the same VM/disk at 2 different places without knowing, leading to data corruption.
-
@olivierlambert said in XOSTOR hyperconvergence preview:
- FINALLY YOU CAN CREATE THE SR:
Otherwise with thin provisioning:
xe sr-create type=linstor name-label=<SR_NAME> host-uuid=<MASTER_UUID> device-config:group-name=linstor_group/thin_device device-config:redundancy=<REDUNDANCY> shared=tru
Is this part of the command not needed?
device-config:hosts=XCP-01,XCP-02,XCP-xx - FINALLY YOU CAN CREATE THE SR:
