1. EPAM Cloud Orchestration
Hello everyone, welcome to EPAM Cloud Orchestration v overview video
EPAM Cloud Orchestration V
March 26, 2016

2. EPAM Orchestration v.2.1.66 Update Overview
New Region: EPAM-DKR
PowerShell DSC Support
Hybris as a Service
EPAM-DKR – a new region for CoreOS usage
Docker on CoreOS via KVM
First month for free!
Auto configuration for DSC is supported by introducing Chef Client 12
Goes in two modes:
Single (1 VM)
Large (5 VMs)
Can be either fully configured or prepared for manual setup
MS SQL 2014 as a Service
Security Updates
Security Updates
Documentation Updates
Documentation Updates
MS SQL 2014 provisioned
DB hosting on hardware servers
Lock VMs termination for AWS
Daily utilization monitoring
VMs creation limits monitoring
Security reports updated
Glossary Added
3 New documents
6 Documentation updates
FAQ updated
The current version comes with a number of improvements and updates, and you can see the most significant of them on the screen.
So this is EPAM Mac region introduction, unknown VM owner resolution mechanism creation, expanding Delivery Manager’s facilities in Cloud, a number of Maestro Command line and Ambari service improvements.
We also started a big deal of improving EPAM Cloud security, and this time there is already a number of significant updates in this area.
See more at

3. Approvals for VMs run Use Manage Cloud wizard to activate approvals
Solution Overview
Use Manage Cloud wizard to activate approvals
When monthly quota is depleted, new VMs can be created only by approval
Applies to both user’s action and calls from Maestro Stacks
Approval flow

4. EPAM-DKR: A Region for Docker over CoreOS
Starting from March 26, 2016, EPAM Cloud users get access to a new region – EPAM-DKR, which embodies new approaches to virtualization and containerization. The region is based on OpenStack (Kilo), and is designed for Docker usage over Core OS operating system.
The region allows only Docker as a Service usage
Docker VMs are run under KVM and have Core OS
Each Docker Service instance is hosted on a separate hardware server
Only Large shape is available for Docker VMs
Each node in Docker Swarm cluster is a master
One month free (starting from March 26)!

5. Hybris as a Service
Hybris is one of the world top e-commerce software platforms.
The platform is widely used by EPAM teams
It was decided to develop our own Hybris as a Service, based on Hybris
The solution was developed within short time (3 weeks)
This was possible due to the close collaboration of EPAM Cloud and Hybris Competence Centers
The solution is based on Chef and Maestro Stacks engine

6. MS SQL With Guaranteed Capacities
Configuration
Prices
Database: MS SQL 2014
Base: Hardware Servers
Activate: or2rdb … -r EPAM-BY1 –s [50/100/150]
Login:
Windows (domain credentials)
SQL auth (generated login/password)
Creation Fee: $10
DB Storage Volume:
DB Storage Volume
Monthly Price
50 GB
$50
100GB
$62
150 GB
$74

7. PowerShell DSC Support
Auto configuration is an important part of Cloud service provisioning. Currently, EPAM Orchestration supports the following auto configuration scenarios:
Running a script on instance creation
Specifying the SSH key for Ansible usage
Using out-of-box and custom Chef recipes
LINUX systems
EPAM Orchestration v supports PowerShell DSC for Windows VMs due to Chef Client update to v.12
With the current update we introduce support of PowerShell DSC as the auto configuration tool to be used with Windows VMs. To enable this improvement, we updated the Chef Client provided on our VMs, to Chef Client v , which will be installed on all instances created after March 26.

8. Lock AWS VMs from termination
The or2lock command was implemented in previous Orchestration release, but the lock was checked only by Maestro CLI/UI. In this update, we expanded the command’s scope so that the lock affects native AWS tools (e.g., AWS Management Console).
Maestro CLI Use
or2lock –p DEMOPDO –r AWS-REGION -i INSTANCE
Project managers, Project Coordinators and Delivery Managers can manually customize the permissions of project members.
The screenshot shows how Lock Instance Termination operation can be prohibited for the users with the Developer role on the project.

9. Resource Creation Control in AWS
Challenge
AWS service limits are inconvenient for automated management: they are not applied immediately and need to be requested via Support center.
EPAM Orchestrator provides quotas management on self-service basis and the changes are applied immediately.
Quotas specified by Orchestrator were checked only on Maestro CLI/UI level
AWS IAM Users could create any number of resources omitting Orchestrator quotas check. This could result into unexpected costs.
Solution
Orchestration includes real-time analytics for VMs creation in AWS
Orchestration checks the number of created AWS VMs
If EPAM Orchestrator Quota is depleted, a letter for approving this activity is sent
If the activity is not approved, all the resources created within the observed time, are terminated, and the related IAM user(s) get locked

10. Hardware Billing Changes
The location-specific billing policy is based on a differentiated approach to hardware resource costs. Such policy allows to optimize the hardware resource costs and bring them closer to their prime costs.
Starting from April 1, 2016 the location-specific hardware billing will be applied in two locations:
Country
Location
Location Coefficient
Belarus
Minsk, Kuprevicha 1/1
0.8
Minsk, Kuprevicha 3V 1
See more in Account Management Guide (

11. Knowledge Base Updates
NEW: Glossary
NEW: 3 Overview Docs
EPAM Cloud Services Guide
New Docker facilities described
RDB Service info Updated
AEM Service info updated
Main concepts included
Gives references to related sources
EO Features Overview
EO Billing Overview
EO Hybridization Overview
Maestro CLI User Guide
FAQ
EO v Update Documents
Docker and RDB Service info updated
Latest CLI changes described
Reviewed
New questions added
What’s New
Release Notes
Video Overview
Find all documents on

12. Thank You For Attention!
EPAM Cloud Consulting team