Child pages
  • XVP Nodes Tab

This documentation is for a previous version of Flexiant Cloud Orchestrator. The most recent version is v5.0. For the most recent documentation please see here

Skip to end of metadata
Go to start of metadata

Info: UUIDs and ID's in use in the XVPAdmin interface do not map to UUIDs from the User or Admin User Interfaces as they are separate systems.

The Node Information page has a number of tabs. This section describes the features of the Node Information page. There are two types of node, compute nodes and router nodes.

The main page presents an overview of all the Nodes in the platform, along with their status. The following fields are available:

  • Cluster ID
  • Node ID
  • Type
  • CPUs
  • Free Ram
  • Uncontended Ram
  • Load
  • No of Servers
  • State
  • Config Group
  • Router Group

Adding a Node

You can add a node from this page by clicking on the 'add' subtab.  For more details on adding Nodes please see Adding Compute Nodes or Adding Router Nodes

 

Managing Nodes

You can also manage the state of an individual node from here by clicking on it's IP Address.  This will then change to a page detailing information about the node as follows:

  • Node ID
  • Cluster ID
  • Cluster UUID
  • Cluster Reference
  • State
  • Available Ram
  • Available CPU
  • Current Load
  • Node Type
  • Config Group
  • Router Group
  • Router State
  • RAM without Contention
  • RAM Contention Ratio
  • CPU Contention Ratio
  • Number of Servers
A number of sub tabs are available, these are as follows:

System Keys

The System Keys tab allows you to set Keys related to the Affinity System of workload placement.

Servers

The Servers tab allows you to list any virtual servers running on that compute node.  The information displayed is the following:

  • Server ID
  • State
  • DOM ID
  • pvDrivers setting
  • vCPUs
  • RAM

You can then select a server from there and go to the XVP Servers Tab for that server.

Change State

This tab enables you to change the state of the node, available options are:

  • Running

This is the normal operating mode.

  • Maintenance

Set this if you want to prevent any virtual machines starting on the node (in the case of a compute node) or to prevent the node routing traffic (in the case of a router node).

  • Locked

Set this if you want to disable control for starting/stopping anything to do with the node.

 

Note:There is also a fourth state which is 'Error' which a Node will go into if it detects an error while it is running. It is not possible to set a node into error state manually.

 

Remove

This tab allows you to remove a node from a cluster if required.

  • No labels