As a FinOps lead and an AWS Cloud user I expect to – in Turbonomic – view my auto scaling groups as entities and eventually park them, so that I can save money on these cloud resources.
AWS Auto Scaling Group is a collection of EC2 machines (VMs), which operate collectively in provisioning their instances based on their utilization demand of the hosted applications. The action of maintaining the number of instances in an Auto Scaling group and automatic scaling are the core functionalities of the Amazon EC2 Auto Scaling service. The Parking feature in Turbonomic will provide the ability to Park the running Instances inside the ASGs and thereby realize savings.
Auto Scaling Groups are discovered by Turbonomic at present and realized under "Groups". This does not qualify ASG as an entity in the Supply chain Market.
The two-step enablement done to support AWS ASG parking:
- Maintain AWS ASGs as entities in the form of "VM Spec" under the Supply chain. Their EC2 instances as Virtual machines will be related to the VM Spec.
- Add AWS ASGs into the Parking filter and display them under the Parking UI, enable Parking actions support at the Group level.
https://docs.aws.amazon.com/cli/latest/reference/autoscaling/terminate-instance-in-auto-scaling-group.html
New feature in Parking permits the addition of an entity type (ASG), which in result allows the Turbonomic-AWS Cloud users to increase cost savings and optimize usage.
|
Is every ASG eligible for Parking from Turbonomic?
|
Yes. Standard ASGs which are allowed to be discovered from the AWS accounts are eligible for parking.
|
|
Is the ASG in EKS Clusters are Parkable?
|
No. ASGs which are the part of EKS Clusters will not appear in the Parking UI and therefore, will not be eligible for Parking.
|
|
Where the ASGs appear in the Supply Chain?
|
ASGs will be treated as Entity type "VM Spec" where they appear and are searchable. However, the current state where they are divided into Groups will persist.
|
|
Are the individual ASG Instances parkable selectively?
|
No. Parking action would be executed at the ASG level which Stops & Starts all the Instances that belong to the ASG.
|
|
Are the ASG Instances individually visible under the Parking UI?
|
Yes. User can click on every ASG resource in the Parking UI to view their instances with status and properties associated.
|
|
Will there be Realized savings report for ASGs parked from Turbonomic?
|
Yes. The Realized savings will be available from the Cloud Savings/Investments Widget.
|
|
Where are the Executed Parking action results displayed?
|
Action results will appear in the All-Actions widget like other parkable resources.
|
|
Will the member/instances of an ASG will appear as individual resources as EC2 Virtual instances in the Parking UI
|
No.
|
AWS ASG Workloads listed in the Parking UI, pictured as Workload Type “Virtual Machine Spec” in the Market
The (i) Icon to the right side of the table, extends the instances view of the ASGs.
Allowed Parking actions on AWS ASGs:
- Start (Starts the ASG and retain the last known setting of the instances min, max & desired)
- Stop (Stop action that enforces “Terminate” action as in AWS terms, that brings the instance setting to 0)
Turbonomic retains the last known configuration once the ASG is parked (stopped) and when resumed – it retains the last known settings which helps user to run the ASG with the latest configuration.
Executed Parking actions:
- All Actions Cloud widget will reflect the status of the executed parking actions
Realized Savings: Parking actions
- Cloud Savings (cumulative savings by action type) widget captures the savings sustained due to Parking actions.
- “Suspend” action type will represent the Parking actions, which could be further scoped to Parking resources using show all à expanding the action type and date.
The Parking actions Start & Stop (Terminate for AWS ASGs) would be permitted in Turbonomic with the following behaviour:
- The "Stop (Terminate)" action at AWS ASGs will stop all the instances, their instances count will become "0" & Turbonomic will continue the count before the stop action (ASG configuration).
- When the ASG is started again, Turbonomic will re-instantiate the ASG by restoring to its last known configuration. This will enable the user to continue the use of ASG without the need of reconfiguring the count and activating them back manually.
Author:
Rajesh Kanna, Product Manager - Turbonomic
rajeshkanna@ibm.com