HP Matrix Operating Environment 7.3 and 7.3 Update 1 Infrastructure Orchestration User Guide

except for physical servers, which are freed for other uses. Deactivating a service is the default
policy for handling a lease expiration. The administrator can change this policy to:
• ignore the lease expiration
• de-provision the infrastructure service on lease expiration
The lease end policy can be changed in the ..\Program Files\HP\Matrix infrastructure
orchestration\conf\hpio.properties file.
# Specifies the lease period end policy.
# Acceptable values (not case sensitive):
# - Ignore = Simply ignore the lease period ending.
# - Delete = Deletes the infrastructure. This cancels all pending and in-progress requests.
# - Deactivate = Deactivates all infrastructure's resources. This cancels all pending and in-progress requests.
Cloud servers and lease.end.policy:
When lease.end.policy is changed to Deactivate and a lease end period is reached, cloud servers
will be powered off (when possible). However, some cloud servers cannot be powered off, such
as HP Cloud Services servers and EC2 instances that were launched from an S3–backed AMI. In
these cases, the power off request will fail and the cloud servers will continue to run.
Matrix infrastructure orchestration sends email notifications to the service owner one week and
one day prior to a lease expiration. For an expired service that is running or deactivated,
infrastructure orchestration sends email notification once a week after the expiration, until the lease
is extended or the service is deleted. These notification time periods are configured in the ..\
Program Files\HP\Matrix infrastructure orchestration\conf\hpio.properties
file.
# In *minutes*, when to send the first and the second lease ending notification
# emails and the frequency on which the expired notifications will be sent.
lease.ending.notification.email.first=10080
lease.ending.notification.email.second=1440
lease.expired.notification.email=10080
Edit virtual servers operation
To modify the number of processors and memory size of a virtual machine after a service is created,
use the Edit Virtual Servers operation. This operation is not available for Integrity VMs, and for
virtual machines provisioned to a cloud provider.
NOTE: If a template has been marked as Customizable, the networks, IP address assignment
types of a server group and network connections, memory size, processor count, VM storage
volume name, and operating system/software image can be changed when a service is created
by using the Edit button on the Create Service dialog. See “Customizing template attributes when
a service is created” (page 145) for more information.
To edit a virtual server
1. Open the infrastructure orchestration console, self service portal, or organization administrator
portal.
2. Select the Services or My Services tab.
3. Select a service and click Details or View Details.
4. From the Actions or Server Actions list, select Edit virtual servers.
5. Expand the tree and select the virtual machine you want to edit.
Matrix infrastructure orchestration lifecycle operations 115