Skip to content

Latest commit

 

History

History
90 lines (64 loc) · 5.64 KB

README.md

File metadata and controls

90 lines (64 loc) · 5.64 KB
Raw

OCI-AutoScale

Welcome to the Scheduled Auto Scaling Script for OCI (Oracle Cloud Infrastructure).

The AutoScaleALL script: A single Auto Scaling script for all OCI resources that support scaling up/down and power on/off operations.

NEW

  • Support for MySQL service added
  • Support for GoldenGate service added
  • Bug fix for DB RAC instances, now both nodes are shutdown / started

Supported services

  • Compute VMs: On/Off
  • Instance Pools: On/Off and Scaling (# of instances)
  • Database VMs: On/Off
  • Database Baremetal Servers: Scaling (# of CPUs)
  • Database Exadata CS: Scaling (# of CPUs)*
  • Autonomous Databases: On/Off and Scaling (# of CPUs)
  • Oracle Digital Assistant: On/Off
  • Oracle Analytics Cloud: On/Off and Scaling (between 2-8 oCPU and 10-12 oCPU)
  • Oracle Integration Service: On/Off
  • Load Balancer: Scaling (between 10, 100, 400, 8000 Mbps)**
  • MySQL Service: On/Off***
  • GoldenGate: On/Off

*Supports the original DB System resource model and the newer Cloud VM Cluster resource model (introduced in Nov 2020)

**For the loadbalancer service, specify the number 10,100,400 or 8000 for each hour to set the correct shape. When changing shape, All existing connections to this load balancer will be reset during the update process and may take up to a minute, leading to potential connection loss. For non session persistent web based applications, I did not see any noticeable interruption or downtime in my own tests, but please test yourself!

***MySQL Instances are not found by the search function :-( So a special routine is run to query them. Also MySQL instances that are not running (Active state)) do not allow their tags to be changed/added/removed.

Features

  • Support for using the script with Instance Principle. Meaning you can run this script inside OCI and when configured properly, you do not need to provide any details or credentials.
  • Support for sending Notification after script is done. Thanks to Joel Nation for this! All you need to do is configure the Topic OCID in the script and make sure the user or instance principle has the correct permissions to publish Notifications.

Install script into (free-tier) Autonomous Linux Instance

Youtube demonstration video: https://youtu.be/veHbyvDB74A

  • Create a free-tier compute instance using the Autonomous Linux 7.8 image
  • Create a Dynamic Group called Autoscaling and add the OCID of your instance to the group, using this command:
    • ANY {instance.id = 'your_OCID_of_your_Compute_Instance'}
  • Create a root level policy, giving your dynamic group permission to manage all resources in tenancy:
    • allow dynamic-group Autoscaling to manage all-resources in tenancy
  • Login to your instance using an SSH connection
  • run the following commands:
  • If this is the first time you are using the Autoscaling script, go to the OCI-Autoscale directory and run the following command:
    • python3 CreateNameSpaces.py

The Install script will configure the time zone to European Central Time (CET). If you want to operate in a difference timezone, run the command:

  • sudo timedatectl set-timezone Europe/Amsterdam

The instance is now all setup and will run 2 minutes before the hour all scaling down/power down operations and 1 minute after the hour scaling up/power on operations.

How to use

To control what to scale up/down or power on/off, you need to create a predefined tag called Schedule. If you want to localize this, that is possible in the script. For the predefined tag, you need entries for the days of the week, weekdays, weekends and anyday. The tags names are case sensitive!

A single resource can contain multiple tags. A Weekend/Weekday tag overrules an AnyDay tag. A specific day of the week tag (ie. Monday) overrules all other tags.

The value of the tag needs to contain 24 numbers and/or wildcards (*) (else it is ignored), separated by commas. If the value is 0 it will power off the resource (if that is supported for that resource). Any number higher then 0 will re-scale the resource to that number. If the resource is powered off, it first will power-on the resource and then scale to the correct size.

When a wild card is used, the service will stay unmodified for that hour. For example, the below schedule will turn of a compute instance in the evening/night, but allows the user to manage the state during the day.

Schedule.AnyDay : 0,0,0,0,0,0,0,0,*,*,*,*,*,*,*,*,0,0,0,0,0,0,0,0

Scaling Example Instance Pool

Power Off Example DB VM

The script supports 3 running methods: All, Up, Down

  • All: This will execute any scaling and power on/off operation
  • Down: This will execute only power off and scaling down operations
  • Up: This will execute only power on and scaling up operations

The thinking behind this is that most OCI resources are charged per hour. So you likely want to run scale down / power off operations just before the end of the hour and run power on and scale up operations just after the hour.

To ensure the script runs as fast as possible, all blocking operations (power on, wait to be available and then re-scale) are executed in seperate threads. I would recommend you run scaling down actions 2 minutes before the end of the hour and run scaling up actions just after the hour.

You can deploy this script anywhere you like as long as the location has internet access to the OCI API services.

Disclaimer

Please test properly on test resources, before using it on production resources to prevent unwanted outages or very expensive bills.