Maestro Blog

Project teams often need to perform repeated processes on infrastructure setup and updates. This is not effective to be done manually, as is often highly time and resource consuming. It is a challenge to minimize the work done by admins, devOps, developers and users by automating routine flows and providing them with free time for real project work. The best way to solve this problem is to use Infrastructure as Code (IaC). Using Infrastructure as Code allows building and updating your infrastructure and applications by creating appropriate instructions (templates) that can be executed easily in a safe, repeatable manner. Moreover, it allows to delegate templates creation to a dedicated team of experts, and let the users just initiate changes with the Apply button click: The main IaC tool chosen for Maestro is Terraform. It allows managing complex infrastructures, even when they are hosted in multiple clouds. The separated planning and execution phases allow to review the in

Maestro supports AWS Consolidated Billing, in which you get a single bill for all your accounts. The billing data is obtained from AWS, Azure and Google clouds directly in the form of .csv files. The billing data is updated on the hourly basis, therefore, you can see the current cost of your infrastructure at any time. Maestro receives bills from providers and sends them to the customers "as is", without adding or removing anything. However, there is an option of making adjustments to the bills, for example, extending credits to particular accounts for certain amounts. The billing engine is based on the same concepts and mechanisms as were applied in EPAM Orchestrator. Virtual resources are billed according to the timelines - periods of time during which the resource is in a certain state. Timeline beginnings and endings are marked with audit events which in Maestro are supplied by CADF (Cloud Auditing Data Federation). A virtual machine start generates an audit event

Maestro front-end is written in Angular 6, an open-source JavaScript-based framework for web application development. Angular 6 was chosen as a flexible framework supporting component approach - if one of the components fails, this does not affect the rest of the system. As the previous versions of EPAM Orchestrator were written in Angular JS, it was only logical to continue with Angular 6 as such approach could speed up the application development by reusing the already developed elements with certain adaptations. In addition, Angular 6 allows creating dynamic items, for example, by supporting the drag-and-drop functionality featured in Maestro UI. The mobile Maestro application written in NativeScript based on Angular 6, can be used on Android and iOS without any special adaptations. Angular 6 supports backward compatibility, therefore, Maestro components can be easily integrated with other web applications. Finally, let's look briefly "under the hood" of the

In 2012, EPAM Cloud Orchestrator was created as a cloud solution for the EPAM Systems community. It appeared when the issue of redesigning the growing infrastructure of more than 500 projects became critical. After a thorough analysis of the existing solutions, EPAM experts had to admit that none of them fit the company needs. However, that was not a problem but a challenge. If no perfect solution existed, EPAM created its own from scratch. In six years, EPAM Cloud Orchestrator evolved into a true hybrid cloud with over 8000 virtual machines in hundreds of projects. In addition to its basic function - hosting virtual resources - it supports a number of related components helping the users to be in full control of their virtual infrastructures, such as audit, monitoring, billing, reporting. Meanwhile, a time has come to go out of the box of an enterprise solution and meet the market. This is how the new generation of EPAM Cloud Orchestrator - Maestro was born. Maestro is