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

    XCP pool server multiple IP/Names

    Scheduled Pinned Locked Moved Management
    5 Posts 3 Posters 121 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.
    • A Online
      Andrew Top contributor
      last edited by

      When setting up a XCP server in XO, is it possible to enter multiple IPs or host names for a single server entry? If I have a pool of 3 hosts then I can enter the 3 hosts individually and one will work and the others will show an error. I just want just have a single pool server entry with the three IPs (or hostnames) so XO will contact any/all of the a hosts to find a working master from a single entry.

      Like: 192.168.1.11, 192.168.1.12, 192.168.1.13

      D 1 Reply Last reply Reply Quote 0
      • D Offline
        DustinB @Andrew
        last edited by

        @Andrew no, you would only connect the management IP address of a given host to XO, either as a standalone pool or as a part of an existing pool.

        Is the goal to have a redundancy should you lose a network interface that is the "management interface"?

        A 1 Reply Last reply Reply Quote 0
        • olivierlambertO Offline
          olivierlambert Vates 🪐 Co-Founder CEO
          last edited by

          We did that last year, but it triggered more problems than solving. Maybe we'll try to get back on it, but it's a decision on XO team (@lsouai-vates )

          1 Reply Last reply Reply Quote 0
          • A Online
            Andrew Top contributor @DustinB
            last edited by

            @DustinB The goal is if the primary host is down then XO will connect to another host. If XO connects to a slave host then it will be redirected to the new master but it needs to connect to a working host in the pool.

            The idea is to have one entry per pool rather than per host since XO does not need to (or want to) connect to ever host in a pool, but needs to reach one working host per pool.

            @olivierlambert I'm just one user with an idea... If you found it caused more problems than it solves then maybe it's not a good idea. It's up to your team.

            1 Reply Last reply Reply Quote 0
            • olivierlambertO Offline
              olivierlambert Vates 🪐 Co-Founder CEO
              last edited by

              I mean I agree with the idea that sounds good, I need to be reviewed again to see if we could do better than we did 🙂

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