Product Documentation

Creating a Resource Pool

Jun 14, 2017
Creating a Resource Pool
Prev Chapter 3. XenServer Hosts and Resource Pools Next

  • VM, local, and remote storage configuration is added to the pool-wide database. All of these will still be tied to the joining host in the pool unless you explicitly take action to make the resources shared after the join has completed.

  • The joining host inherits existing shared storage repositories in the pool and appropriate PBD records are created so that the new host can access existing shared storage automatically.

  • Networking information is partially inherited to the joining host: the structural details of NICs, VLANs and bonded interfaces are all inherited, but policy information is not. This policy information, which must be re-configured, includes:

    • the IP addresses of management NICs, which are preserved from the original configuration

    • the location of the management interface, which remains the same as the original configuration. For example, if the other pool hosts have their management interfaces on a bonded interface, then the joining host must be explicitly migrated to the bond once it has joined.

    • Dedicated storage NICs, which must be re-assigned to the joining host from XenCenter or the CLI, and the PBDs re-plugged to route the traffic accordingly. This is because IP addresses are not assigned as part of the pool join operation, and the storage NIC is not useful without this configured correctly. See the section called “Configuring a Dedicated Storage NIC” for details on how to dedicate a storage NIC from the CLI.


Prev Up Next
Requirements for Creating Resource Pools Home Creating Heterogeneous Resource Pools