Cloud bursting with HP CloudSystem Matrix infrastructure orchestration and Savvis

All operations sent to Savvis are serialized. Concurrent VM provisioning in the same service is limited; Savvis
currently supports only a single operation at the service level.
Generic messages
Errors that occur when submitting a request to Savvis are non-specific as to the cause. For example, “Cloud provider
is not compatible with Logical Server requirements. Please refer to the Matrix OE infrastructure orchestration
documentation for further details.”
No VM customization and login
Some values (such as IP addresses) are not customized inside Savvis. Automatic login for the created VMs is not
allowed.
Software mapping
Software deployed in the Savvis cloud requires manual setup before it is used by infrastructure orchestration.
 Custom VM images created in IO must be uploaded to Savvis using the Savvis web portal.
 After the software is uploaded to Savvis, a mapping file must be createdto map each IO image to the
corresponding Savvis image.
Software provisioning
Using SA to deploy application software onto a Savvis VM (subsequent to OS deployment by Savvis) is not
supported. Using different deployment engines to deploy software to the same VM is not supported.
Visibility and management of cloud based VMs
Cloud based VMs are visible only to infrastructure orchestration. These VMs are invisible to Insight Control virtual
machine management and Systems Insight Manager, and have no logical server associated in logical server
management.
Localization
Savvis support in infrastructure orchestration 7.0 is English only.