SOVM is the Missing Link in Cloud Automation
The Site Ox Virtualization Management (SOVM) is the missing link for cloud service automation. SOVM provides the "glue" between the web site shopping cart and the cloud service deployment tools, between the user notification system and the cloud service deployment events, between the customer selected lease agreements and the automated lease scheduling manager.
SOVM Executive Summary Slide Show
SOVM Technical Overview Slide Show
SOVM is the reservation/lease management system for variable length customer reservations or lease terms. Customers can reserve or lease a VM/LPAR/Business Function for variable lengths of time and SOVM maintains a database of actions to perform, and the date/time at which to perform those actions. Actions associated with each reservation/lease consist of lease expiration, lease termination, extending a current lease, renewing an expired lease, archiving and unarchiving systems, other lease management functions, and various messages associated with the status of each lease and customer.
SOVM currently orchestrates the deployment of the following Operating Systems and associated business functions:
- IBM AIX on Power
- HPUX on Itanium
- Solaris on SPARC
- Solaris on Intel
- Red Hat Enterprise Linux on IBM Power LE
- Ubuntu 15.10 Linux on IBM Power LE
- CentOS on IBM Power LE
- CentOS on Intel
- Ubuntu Linux on IBM Power LE
- OpenSuse Linux on IBM Power LE
- Debian Linux on IBM Power LE
- Fedora Linux on IBM Power LE
- SUSE Linux Enterprise Server on IBM Power LE
SOVM is NOT the deployment tool, it retrieves the completed customer orders from any front end user interface, web site, or order management system, then instructs any and all remote backend deployment tools on how to implement those orders. It translates the customer order into remote deployment commands, then chooses the appropriate and available remote deployment tool, and issues commands in the API language of each different deployment tool, to perform the deployment.
SOVM is NOT the user notification system, it receives event notifications from the deployment tools and instructs the user notification system on what to do with them. It translates the deployment event into a message the customer can understand and then uses existing external user notification tools to send the message. To restate, it accepts incoming events from the various deployment tools, then creates customer messages based on the incoming events, and submits the messages to the notification system, using the API language the notification system expects, to notify the customer of the event.
- SOVM is designed to be decentralized in operation. It can remotely accept incoming orders from anywhere. It can remotely deploy onto any system in any datacenter anywhere in the world.
- SOVM is designed to be integrated with any user management front end, web site, order management system.
- SOVM is designed to be integrated with any customer notification system front-end.
- SOVM is designed to be integrated with any backend deployment tool i.e. KVM, VMware, Openstack, Cloudinit, NIM, HMC, VIOS, Jumpstart, Ignite, etc
- SOVM accepts a standardized order formats such as:
- Application Programming Interface (API)
- Configuration file format: variable=value
- Stanza file format: order.ini
- XML file format
- Any custom file format can be integrated with SOVM
- SOVM uses SSH and API calls to communicate with all front-end and back-end tools.
- SOVM can communicate using private, public, or VPN Networks.
A good analogy to understanding how SOVM works is to imagine a pre-paid telephone service company. There is a Web Site on the front-end hosted by Service Provider "Brand X". This company takes the orders and bills the customer, but they do not actually provide any telephone service. "Brand X" simply passes the service order to a middle man, such as SOVM. This middle man "SOVM" then determines a location that can provide the type of service requested by the end user and where capacity is available. SOVM then orchestrates the implementation of the requested service at the selected service provider (such as Verizon, AT&T, Sprint, etc). The service provider hosts the equipment and facilities needed to fulfill the end users need, SOVM simply orchestrated the fulfillment of the order.
You can see SOVM in action at http://siteox.com/lop
For information about how you can utilize SOVM to orchestrate automated deployment of operating systems and business functions in your data centers and cloud environments, please contact us.