Enterprise Deployment Models - On-Premise and Private Agent

We have been actively improving our Maestro solution in terms of deployment options. Recently we implemented the new functionality supporting private regions in order to complete the Enterprise deployment model, adding the possibility to install Maestro as a private agent in order to manage OpenStack and VMWare private regions, as well as install a refactoring full-functioning version of Maestro application on a single instance within the customers' infrastructure.

Thus, the set of SaaS deployment models supported by Maestro is this:
Standard deployment model
  • A single-entry point to the unified and simply organized reporting for all customer’s resources across all public clouds they use. 
  • A set of analytics tools for all virtual resources under the customer’s account. This includes analytics on instance and tenant levels. 
  • Quotas management tool, that allows to set up the monthly expense limits for virtual infrastructures and the scenarios for different stages of quotas depletion. 
  • Alerts and notifications informing the customer on the significant events on their resources. 
Professional deployment model, where the customer is provided with all the facilities of the Standard model, complemented with the following: 
  • Virtual machines management. An instance can be ordered in several clicks, and the process is unified for all the supported clouds. 
  • Using Terraform and other stacks solutions to automate infrastructure management. 
  • Managing virtual machines owners. This allows to set up the higher level of control on the infrastructure events, and better cooperation with the responsible persons. 
  • Auto configuration for complex automated infrastructure setup. 
Enterprise deployment model is provided as Platform as a Service solution. Maestro is set up on the customer’s side and includes all the features of the Standard and Professional models, as well as the ability to set up private virtual regions. Private regions can use the following technologies:
  • OpenStack
  • VMWare
The Enterprise deployment model also includes a set of additional features on different layers of the solution.

So, to sum up, Maestro can be provided in one of the following ways to our customers:
  • SaaS, where the customer can connect their account to Maestro and get the access to the functionality within the requested deployment model.
  • SaaS + Private Agent, where Maestro agent is installed in the customer’s OpenStack or VMWare private region to enable Maestro control over it. Due to agent settings, Maestro receives only the information, approved by the customer. If the customer also has infrastructures in public clouds, they can be added to Maestro according to the SaaS model.
  • On-Premise, where the customers can install Maestro on an isolated instance on their data center.

Private Agent

Maestro makes the necessary provisions for working with both private regions and public clouds. These provisions are based on the notion of a private agent.

Private agent is a Java application that processes Maestro SDK requests and uses these requests to manage clouds (only those supported by a private agent). SDK requests are sent according to the AMQP protocol and encrypted using the AES (Advances Encryption Standard) algorithm. 

Within the Maestro enterprise version, utilization and management of private clouds can be performed in two ways:
  • via the OpenStack private agent used for managing OpenStack regions,
  • via the private agent based on the VMWare technologies and installed on customer premises (VMWare private agent)
This diagram shows how Maestro communicates with private agents:

On-Premise

Maestro On-Premise solution is a full functioning version of our application which can be deployed on any individual instance, without reference to any cloud provider or their data centers. Being easily tunable, this version of our solution is able to satisfy the needs of any customers on their infrastructure.

The On-Premise solution was developed as an alternative to SaaS-based cloud management solutions which were unacceptable for some enterprises due to the specifics of business or local regulations for data storage.

Maestro On-Premise solution can be installed on lower capacities. At the same time, if the requirements to capabilities are more sufficient, our application can expand by using a set of bigger servers. Such an approach allows Maestro On-Premise solution to satisfy the needs of any customers on their infrastructure.

The development process of our On-Premise solution is also much easier and less time-consuming, as it is not required to obtain a specific knowledge to perform the development. The launching of application will be much faster, the development process can be set in such a way that development cycles become shorter allowing to make more useful changes in the same time.
_________________

Thus, we continue enhancing Maestro application in order to meet our customers' growing needs.

Follow the news in our blog to learn more about our new features and services.

:)

Comments

Popular posts from this blog

Maestro Analytics: Essentials at the Fingertips

Maestro: Greeting the Green Dragon

Maestro Orchestrator: Product? SaaS? Framework!