XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Questions about stretch cluster vsan and failover

    Scheduled Pinned Locked Moved Migrate to XCP-ng
    7 Posts 2 Posters 1.4k Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • G Offline
      giejo
      last edited by

      Hello
      I'm working for healthcare hospitals and we are currently vmware customers.
      We have some vxrail (vsan dell) and some classic SAN with vsphere and esx. This year we need to replace our oldest esx and our SAN.
      My team is happy with vxrail but with broadcom changes i want to challenge some differents strategys...
      Before testing xcp-ng i want to ask how can we make a redundant architecture wich can tolerate one room complete failure ?
      With vsan we can have stretch cluster what is the solution with xcp-ng ?

      Thanks for your help !

      J 1 Reply Last reply Reply Quote 0
      • J Offline
        john.c @giejo
        last edited by john.c

        @giejo The XCP-ng hypervisor can be organised into pools, which can be used with HA. The more XCP-ng hosts in pools, which are HA enabled the better. As the HA feature on pools keeps the pool available even if individual hosts in that pool go down.

        This is best paired with the appropriate edition of Xen Orchestra for management, backup and orchestration of the multi-pool installation, the load balancing is a Premium feature.

        Check out these websites more information, note that Xen Orchestra has XOSAN (currently v1 but has a closed alpha or beta of the next generation v2). In addition the Xen Orchestra has XO Proxy a means for interacting and managing off site instances of XCP-ng using it.

        https://xen-orchestra.com/#!/xosan-features
        https://xcp-ng.org/
        https://xen-orchestra.com/#!/xo-pricing

        Bear in mind that Vates has recently announced pricing for bundles which include XCP-ng and Xen Orchestra, these changes are coming next year during 2024. Currently they are priced separately, so can add up to more.

        Though you'll find Vates to be pretty responsive and offer better support than VMware.

        https://vates.tech/blog/introducing-vates-virtualization-management-stack/
        https://vates.tech/pricing-and-support/

        In addition since an earlier version of Xen Orchestra you can place both hosts and SR in maintenance mode (as required). This feature enables you do maintenance on an individual SR (or as many as required), it will allow you to potentially not have to put the whole host in maintenance mode. Though it depends on what you want to do.

        J 1 Reply Last reply Reply Quote 0
        • J Offline
          john.c @john.c
          last edited by john.c

          @giejo You can also utilise hardware security keys through an up to date release of Xen Orchestra, in order to secure the access. It also supports the use of Multi-factor authentication for the same purpose.

          With XCP-ng pools allow for live migration between members, thus allowing for the VMS or even containers to continue to be available and running. Combine that with continuous replication and you can replicate VMs which need to be present for availability in other pools.

          Also a good idea is if you don't already implement NetBox to aid in management of network resources (IPs etc). There native synchronisation support of configuration between them in Xen Orchestra. Additionally other integration solutions are available to integrate with the network hardware resources in the hospital.

          https://netbox.dev/

          1 Reply Last reply Reply Quote 0
          • J Offline
            john.c
            last edited by

            @olivierlambert Would you agree with what I have written above?

            G 1 Reply Last reply Reply Quote 0
            • G Offline
              giejo @john.c
              last edited by

              @john-c thanks for these informations
              Really interesting
              I think we have to contact vates.
              Xosan v1 will be replaced by v2 ? What kind of hardware will be supported ?
              I m convinced that we must engage a change and have an internal strategy about vmware and open source products. My team knows vmware and i have to be precise with them about strategy, migration, change management.
              We dont use netbox but we have itop with teemip extension

              Thanks

              J 1 Reply Last reply Reply Quote 0
              • J Offline
                john.c @giejo
                last edited by john.c

                @giejo Xosan and XOSTOR are virtualised SAN (vSAN) so it utilises the same hardware specifications as XCP-ng.

                Though its better to go for XOSTOR as its completely replacing XOSAN both v1 and v2. It's much better based product with a better storage filesystem.

                https://xcp-ng.org/forum/topic/5361/xostor-hyperconvergence-preview

                https://xcp-ng.org/forum/topic/5554/xosanv2-trial-in-xoce

                https://vates.tech/xostor/

                J 1 Reply Last reply Reply Quote 0
                • J Offline
                  john.c @john.c
                  last edited by john.c

                  @giejo In addition Vates is willing to make fixes and/or additions to their virtualisation stack. Though for LTS releases its dedicated to stability and security after release, so major new features will only be added in LTS before a certain stage in its development. Though are regularly making fixes and additions to Xen Orchestra.

                  That maintenance mode for SR in Xen Orchestra was result of my idea, from brainstorming what large deployments might require.

                  Also didn't mention but Xen Orchestra also supports the use of Web hooks and Vates has a public API actively in development.

                  If you find that the public API is missing feature(s) which would be of help to you and/or other users just let them know so it can be worked on for the next update.

                  1 Reply Last reply Reply Quote 1
                  • First post
                    Last post