XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. Cygace
    3. Topics
    C
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 3
    • Groups 0

    Topics

    • C

      Problem: XOA becomes unusable when XCP-ng master host is rebooted

      Watching Ignoring Scheduled Pinned Locked Moved Management
      2
      0 Votes
      2 Posts
      133 Views
      olivierlambertO
      Hi, This is perfectly normal. Only the master is the contact point for the entire pool. I would advise to go for manual promotion if you consider your host dead. To do it, go on any slave you want to promote (just one) and type xe pool-emergency-transition-to-master. If you use HA, this will be done automatically, but HA can be tricky. The result will be the same, if the master is down, you'll lose the view in XO about what's going on the pool, until you get a master back.
    • C

      Migrating a Client to XCP-ng – Stability of the Community Edition?

      Watching Ignoring Scheduled Pinned Locked Moved Migrate to XCP-ng
      5
      0 Votes
      5 Posts
      275 Views
      A
      @Cygace XO is not directly tied to XCP. So the versions have nothing to do with each other. You can look at the XO master commits and pick one that lists feat: release 5.xxx.x and that will line up with a XOA release. You can pick a version that is the same as the current XOA release and it will be the same tested base code.