ParkMyCloud Release: Parking Auto Scaling Groups & More - ParkMyCloud

ParkMyCloud Release: Parking Auto Scaling Groups & More

We pushed out a release over the weekend – most notably including the ability to park Auto Scaling Groups!  Here’s what’s new.

Parking Auto Scaling Groups

You now have the ability to park full Auto Scaling Groups. You can control Auto Scaling Groups in the same way that you can individual instances – with schedules and on/off toggles.

You will see these groups included on your dashboard:

Expanded auto scaling groups display

When an Auto Scaling Group is scheduled to be parked, ParkMyCloud will store the existing settings for minimum, desired, and maximum number of instances. Then, it will change those settings to Min, Desired, Max = (0,0,0) in AWS (while keeping the original values in our system) for the scheduled parking duration. Note that this means the individual instances will be terminated. When the instances are scheduled to run, we’ll set the parameters back to their original values and new instances will be spun up.

By the way, if you are using spot instances in those Auto Scaling Groups, we will be able to park those as well.

Updated Reporting

Since you can now manage your Auto Scaling Groups in ParkMyCloud, your downloadable reports will now be based on “resources” rather than “instances” – instances and Auto Scaling Groups will be considered resources. You’ll now be able to see parking savings for your Auto Scaling groups.

Detailed Information on Your Resources

You now have a much more detailed amount of information about each of your resources – whether instances or Auto Scaling Groups. Just click the “i” information button on the right side of the dashboard, and you’ll see a modal screen like the following:

Instance info

Plus, you now have access to our shiny new User Guide!

user guide link


Please let us know if you have any questions, and happy parking!

 

Current users can find more information about this release on our support site.


About Dale Wickizer

Dale brings over 30 years of technology and engineering experience to his role as co-founder and Chief Technology Office (CTO) at ParkMyCloud. After experiencing the problem of growing cloud spend first-hand, and discovering that there was no simple way to solve it, Dale teamed up with co-founder Jay Chapel to create ParkMyCloud to solve the problem of cloud waste. Before founding ParkMyCloud, Dale was the CTO of the U.S. Public Sector at NetApp, Inc. where he set the future technology and product direction and managed key customer relationships. Prior to NetApp, Dale was an Associate Partner and IT Infrastructure Architect at Accenture, where he helped large enterprises plan and execute IT transformations, data center consolidations, and application deployments. Dale holds both a Bachelor's and a Masters Degree in Electrical Engineering from the Georgia Institute of Technology. He and his wife, Barbara, reside in Springfield, VA.

One response to “ParkMyCloud Release: Parking Auto Scaling Groups & More”

  1. Rob says:

    Another idea of what costs a lot and so is ripe for parking are RDS instances. Particularly important as there is no way to do it through the AWS Console. The only method I have found to stop an RDS instance is to delete it! So I snapshot it first. Here are some details…

    I have a script to stop a database and a script to start it up
    Start does this:
    Snapshot a database instance to -stop, then delete the database instance.
    Checks that snapshot is properly created before deleting the instance and then checks that the instance is properly deleted.
    Waiting for the snapshot to be created may take more than 2 minutes. Whilst this is occurring, progress messages are displayed.
    Similarly when deleting the database.
    Perl Script is here: http://www.evernote.com/l/AA3ucAa4sf1HnYt8mCTo4X0DhTp3rOx1r68/

    Start does this:
    Start a database from a database snapshot called -stop.
    Database is created in the AZ where the database was originally running with a backup retention period of 1.
    The DB instance needs to be modified which may only occur when DB Instance is ‘available’, so the restoring of the database waits until its available.
    Perl Script is here: http://www.evernote.com/l/AA16HM6-WXtLXKm2Gwyy5P5Deq_xTurxFBM/

Leave a Reply

Your email address will not be published. Required fields are marked *

Copyright © ParkMyCloud 2016. All rights reserved|Privacy Policy