The following tutorial covers importing any existing Elastigroup/s running an ECS cluster to Ocean.
Use case 1 – a Single Elastigroup
In case you have one Elastigroup for your ECS cluster, simply click the “Upgrade to Ocean” button at the top-right of the EG.
Use case 2 – Multiple Elastigroups for the same cluster
In case you have multiple Elastigroups for the same ECS cluster, you will need to follow the below instructions:
- Ocean manages the entirety of the ECS cluster’s container-instances. If the instances are distributed across multiple Elastigroups, all of these Elastigroups should be migrated at once.
To complete this tutorial, gather the following information:
- List the Elastigroups connected with the target ECS Cluster.
- For each of the Elastigroups, save the following data for future use:
- Autoscaler Custom Attributes.
- User-data scripts.
- AMI ID.
Step 1: Disable Autoscaling On The Imported Elastigroups
The first step is to disable the autoscaling in the migrated Elastigroups to allow Ocean to take over.
- Navigate to the Elastigroups configured for your ECS cluster.
- For each of the groups, perform the following steps:
- Click Edit Configuration under the Actions menu.
- Scroll down to the Advanced section.
- Remove the Autoscaler selection.
- Continue to the review page and click Update to commit the changes.
Step 2: Create An Ocean Cluster
- Choose one of your ECS Elastigroups and click the “Upgrade to Ocean” button on the top right corner. This will be your source Elastigroup and Ocean will take control over its management.
Step 3: Configure Ocean Custom Launch Specifications
The next step is to configure the Ocean cluster to handle all the different attribute sets configured on the current Elastigroups.
- Navigate to the Ocean cluster you created in step 2.
- Click on the Actions menu and select Launch Specifications.
- For each of the Elastigroups running container instances:
- Click “Add Launch Specification”.
- Add the Attribute sets gathered as part of the prerequisites.
- Set the matching User-Data and AMI.
- Click Update to commit changes.
Step 4: Downscale any secondary Elastigroups converted to Launch Specifications
The last step is to downscale the container instances in any secondary Elastigroups (not the source Elastigroup which was used in step 2) and allow Ocean to launch the proper instances to fit the cluster needs.
- Navigate to the Elastigroups configured for your ECS cluster that were converted to matching Launch Specifications (other than the main one).
- On the Actions menu, Click Manage Capacity.
- Reduce the target capacity.
- Note: It is highly recommended to reduce the target capacity in batches of 10-20% and repeat this step until complete downscale.
- Navigate to your Ocean Cluster and verify that it is spinning up the required resources and handles the cluster tasks.