Adding the Linux server and Citrix XenServer host object to BMC Server Automation

The following sections provide instructions for adding a Citrix XenServer environment to BMC Server Automation:

Before you begin

Ensure that your environment meets the following requirements.

System requirements

To employ BMC Server Automation in an Citrix XenServer virtual environment, you must have the following minimum hardware and software:

  • A Red Hat Enterprise Linux server (version 5.4 or later) to act as a proxy server.
  • At least one installed and configured XenServer Host
  • A XenCenter application for managing the XenServer Hosts, installed and run on a Windows 2000/XP/Vista workstation

Supported Citrix XenServer versions

The following Citrix XenServer versions are supported:

  • XenServer 5.6 Feature Pack 1
  • XenServer 6.0
  • XenServer 6.0.2

Access and privileges

For a Citrix XenServer environment, the CONNECTION_USER property requires the following permissions:

  • Root user on the master server
  • Citrix VM Power Admin role, if you are using Active Directory-based authentication mode

Installing the Linux agent

Tip

Because the Citrix XenServer agentless managed object is managed through a proxy, do not overload the proxy server. The recommendation is to map one agentless managed object to one proxy host. However, if you are using one proxy server to host multiple agentless managed objects, all of the agentless managed objects using the proxy host must be running the same version of the Citrix XenServer configuration object. 

To install the Linux agent, complete the following steps:

  1. Install the RSCD agent on the Red Hat Enterprise Linux server that acts as the proxy server, as described in Installing only the RSCD agent (Linux and UNIX). Be sure to install the RSCD agent that is specifically designated for use with a Linux server.
  2. Open the /etc/rsc/exports file and add an entry with the application server IP address or host name and a read/write mapping. This restricts access to accept connections only from the listed application serve. For example:
    192.168.0.1 rw
  3. Open the /etc/rsc/users.local file and add an entry for a role and user that should be mapped to the root account. For example:
    BLAdmins:BLAdmin rw,map=root
  4. Save and close the files.
  5. Proceed to Adding the Linux server and Citrix XenServer host object to BMC Server Automation.

For more information about the exports and users.local files, see Setting up configuration files.

Adding the Linux server and Citrix XenServer host object to BMC Server Automation

The following sections provide instructions for adding the Linux server and the Citrix XenServer agentless managed object to BMC Server Automation.

To add the Linux server and Citrix XenServer host object to BMC Server Automation

  1. From the BMC Server Automation Console, add the Red Hat Enterprise Linux proxy server as a managed server to a server group (right-click a server group and select Add Server).
  2. Right-click the server group in the Servers folder.
  3. Select Virtualization > Add Citrix XenServer host to add a Citrix XenServer agentless device to BMC Server Automation.
  4. On the Add a new agentless managed object - Properties page, add the name or IP address of the Citrix XenServer master server.
  5. Optionally, add a brief description.
  6. Under Properties, locate the AGENTLESS_MANAGED_OBJECT_PROXY_HOST* property.
  7. Edit the property value by browsing to the name of the Linux system configured as the proxy host.
  8. Click OK.
  9. Click Finish.
    The agentless managed object for the Citrix XenServer is added to the folder you specified.

Recommendation

While it is possible to use the same proxy host for multiple agentless managed objects, the recommendation is to have separate proxy servers for each agentless managed object (representing a Citrix XenServer master server), for optimal performance.

To set the connection properties for the Citrix XenServer object

  1. From the BMC Server Automation Console, select Configuration > Property Dictionary View.
  2. Browse the Built-in Property Classes > Connection class.
  3. Click the Instances tab and set the connection details to the Citrix XenServer master host.
    When you add the agentless managed object, BMC Server Automation automatically created a Connection instance with the name Connection\_ <agentlessManagedObjectName> (where <agentlessManagedObjectName> is the name of the Citrix XenServer object).

    Note

    Your user role must have the appropriate RBAC permissions to update the Connection instance, otherwise the association between the instances will not be created and the server will not be enrolled. Also, if a Connection instance is already associated with the Virtualization instance then a new instance is not automatically created.


    This new instance contains the connection details to the Citrix XenServer master host.

    Tip

    The Citrix XenServer platform can run in two modes: Pool mode or as a standalone host.

    In Pool mode, multiple servers work together to provide capabilities such as workload balancing, high availability, and so on. In this configuration, one server is designated as the master server, while the other servers are designated as slaves. You must set the Connection instance to connect to the master server, rather than a slave server, so that BMC Server Automation can obtain configuration data or perform management operations.

    In Standalone host mode, the standalone server is considered the master server.

  4. Set the following properties for the newly added instance:

    PropertyValue
    CONNECTION_URLEnter the name of the Citrix XenServer master host.
    CONNECTION_USERSet this value to root. Citrix XenServer also supports users configured in Active Directory. If you intend to specify an Active Directory user, the user must be assigned at least the "VM Power Admin" role to be able to use all features supported by BMC Server Automation for Citrix XenServer. Enter the Windows Active Directory user in the following way: <domainName> \ <userName>.
    CONNECTION_PASSWORDEnter the password of the user root on the master host.
  5. Save this instance.
  6. Browse the Built-in Property Classes > Virtualization class.
    For each Citrix XenServer object you add, a corresponding instance is automatically created.
  7. Ensure that the VIRTUAL_ENTITY_CONNECTION property Virtualization instance points to the previously created Connection instance.
  8. Save this instance.
  9. Distribute the Citrix XenServer configuration object on the Citrix XenServer agentless managed object:
    1. From the BMC Server Automation Console, navigate to the Servers folder.
    2. Right-click a server and select New > Administration Task > Distribute Configuration Objects.
    3. Provide a name for the Job and click Next.
    4. Expand the Global Configuration Objects list, select the Citrix XenServer object, and add it to the Selected Configuration Objects section. Click Next.
    5. On the Targets panel, select the enrolled agentless managed object for the Citrix XenServer master server.
    6. Click Finish, and execute the job. For details, see Distributing configuration objects.

You can now use the BMC Server Automation Console to Live Browse the Citrix XenServer agentless managed object and access the *Citrix XenServer* node. For details on adding a server and setting its properties, see Adding a server to the system.

You are now ready to create the VGP in BMC Server Automation for Citrix XenServer, which you can then onboard in BMC Cloud Lifecycle Management as a XenServer compute resource for provisioning.

Where to go next

Creating the VGP in BMC Server Automation for Citrix XenServer

Was this page helpful? Yes No Submitting... Thank you

Comments