Rhino VM automation is a solution that centralizes the deployment, configuration, and life cycle management of Rhino TAS and its applications with automated processes. In Rhino TAS 3.0 or later, you can use Rhino VM automation to deploy, configure, and maintain Rhino VM nodes on a virtualization platform.

During the automation, you create a custom Rhino virtual appliance and upload it to a SIMPL server, together with relevant configuration files. Then instruct the SIMPL server to deploy VMs based on the virtual appliance to the target virtualization platform and to configure the VMs accordingly. Rhino VM automation fully automates the deployment and configuration processes, with no manual operations involved.

Rhino VM automation is different from the classic deployment method, which requires the manual installation and configuration of each node. With the automated deployment and configuration processes in Rhino VM automation, you can significantly reduce the amount of manual work needed, and therefore shorten the deployment and configuration time and minimize the possibility of manual operation errors. In addition, Rhino VM automation allows you to manage the life cycle of the VMs easily. For example, from the SIMPL server, you can upgrade or destroy the VMs.

With the introduction of Rhino VM automation, you now have the flexibility of deploying and configuring Rhino TAS and its applications with the following methods:

  • Classic deployment: Manual deployment and configuration of Rhino nodes.

  • Rhino VM automation: Automated deployment and configuration of Rhino VM nodes on a virtualization platform, as described in this document.

  • Rhino VM automation with continuous integration (CI) and continuous deployment (CD): Rhino VM automation supplemented with CI/CD processes. For details, see VM and Rhino application reconfiguration.

Note In Rhino VM automation, you no longer use the Rhino element manager (REM) to configure Rhino applications. Instead, you do that through a configuration database. In this case, the role of REM changes. You only use it to check application configuration information.
Previous page Next page