Categories

  • All news regarding Xen and XCP-ng ecosystem

    136 Topics
    4k Posts
    A
    @stormi Got it... I missed that one for coretemp. Vates ticket opened for the XOA stats problem after 8.3 upgrade.
  • Everything related to the virtualization platform

    1k Topics
    13k Posts
    bleaderB
    @dmz0001 In theory, XCP-ng 8.3 is mostly on par with XenServer 8.4, it's only a naming thing that they did as their previous naming was confusing some of their customers. Long story short, XCP-ng ~= XenServer 8.4. So what you see in the compatibility list of XenServer 8.4 is the right reference for XCP-ng 8.3. Unfortunately we do not have much feedback on Zen 5 at this time on our side.
  • 3k Topics
    24k Posts
    lsouai-vatesL
    @love2scoot hello and thanks for the huge work you did on this subject! We are working on new ACLs organization for Xen Orchestra 6 and it would be very helpful for us.
  • Our hyperconverged storage solution

    29 Topics
    635 Posts
    A
    @acp Here is the procedure to re-insert your host in the SR. Make sure you have the required packages by running these commands on it: yum install -y xcp-ng-release-linstor yum install -y xcp-ng-linstor It should be the case because the node was running the services before, but better to check. And then restart the toolstack to detect the LINSTOR driver: xe-toolstack-restart Ensure you have the same configuration on each PBD of your XOSTOR SR using this command. xe pbd-list sr-uuid=<UUID> All device-config must be the same. Then, use this command with the correct <GROUP_NAME> and <HOST_UUID> to add the node to the SR: xe host-call-plugin host-uuid=<HOST_UUID> plugin=linstor-manager fn=addHost args:groupName=<GROUP_NAME> For a short description, this command (re)create a PBD, open DRBD/LINSTOR ports, start specific services and add the node in the LINSTOR database. A storage layer is not directly added to this node. You can verify the storage state like this: linstor sp list You shouldn't see the storage pool of your node yet. Run the correct command where the controller is running to add the volume group in the LINSTOR database: # For thin: linstor storage-pool create lvmthin <NODE_NAME> <SP_NAME> <VG_NAME> # For thick: linstor storage-pool create lvm <NODE_NAME> <SP_NAME> <VG_NAME> A new linstor sp list should show you the node now.
  • 30 Topics
    85 Posts
    GlitchG
    @Davidj-0 Merci pour le retour, j'utilisais aussi une Debian pour mon test ^^