Obtain A Virtual Server Information List: Service Details - HPE XP7 Automation Director User Manual

Hide thumbs Also See for XP7 Automation Director:
Table of Contents

Advertisement

If the network connection check is enabled, the firewall of the target virtual server must permit ICMP
(ECHO) replies.
If the network connection check is enabled, the local server (the loopback address that can be
resolved from the name "localhost") must be set as the connection destination for agentless
monitoring.
Server requirements
To use this service template, the following servers are required:
OpenStack server -- A server on which OpenStack is installed.
KVM server -- A server on which a Kernel-based Virtual Machine is installed.
OpenStack control server -- A server that runs REST-API functions on the OpenStack server.
Instance -- An instance (a normal virtual server) managed by the OpenStack server and by KVM.
Usage guidelines
To complete the network connection check, make sure that the total length of the IP addresses (IPv4)
set for all NICs of the instance does not exceed 1,024 characters (#1). If the total length exceeds
1,024 characters, an error might occur in the plug-in osSendIcmp, causing the task to end abnormally.
#1: The maximum length of one IP address (IPv4) including the comma used as an address separator
is 16 characters.
If you enable the network connection check, adjust the value of the property
common.icmpEchoTimeout based on your environment.
It is recommended that you do not change the value of the property openstack.waitTime from its
default value. However, if the wait time specified for the property is not long enough, the next step
might start before the OS setup finishes, causing the task to end abnormally.

Obtain a virtual server information list: Service details

The general steps for using this service template to add a virtual server are as follows:
1. An instance information list is obtained and the instance information is output to a specified remote file
in CSV format. The output file is encoded by using the default encoding format of the OpenStack
control server.
2. A remote temporary file is transferred to a specified local output file.
3. The remote temporary file is deleted.
Details output to the CSV file are listed below:
Hypervisor host name (header name: HostName)
Instance name (header name: InstanceName)
Image name (header name: ImageName)
Instance status (header name: Status)
The number of instance CPUs (header name: NumCpu)
Obtain a virtual server information list: Service details
311

Advertisement

Table of Contents
loading

Table of Contents