Controller Migration in AWS¶
- This feature is released in 5.3. It consists of 2 sub-features:
- This feature mainly is to perform one click “Migrate” operation under “Settings->Maintenance->Migration” tab to migrate the current Aviatrix controller to a new one.
- The EIP will be migrated from old controller to the new one.
- The whole migration process will take around 10 to 15 minutes.
- The feature only supports AWS and AWS-Gov at the moment. (Only AWS products/AMIs, “BYOL” and “Metered” are supported)
- User needs to enable controller backup using an AWS based access-account.
- User must disable controller HA. (User can enable HA again on the new controller once migration is fully completed)
- User should not make any config change during the migration as these config will be lost once new controller takes over.
Controller Migration feature does the following in sequence¶
- User executes the “Migrate” feature on old controller
- Old controller enables controller “BackUp Now” feature to make sure the backup config file is up-to-date
- Old controller creates a new cloud virtual machine which has the latest Aviatrix controller image
- New controller extends disk partition to the max of the disk space available
- New controller initialize itself to match the version of old controller
- New controller restores configuration file from backup of step 2
- New controller invokes cloud API to transfer its old controller’s EIP to itself
- New controller invokes cloud API to stop old controller
- The migration status will be displayed in a tag named “MigrationStatus” of the new controller instance. Sample status messages are “Initializing”, “Migrating”, “Successful”.
- This feature is being performed in the new controller.
- This feature mainly is to perform one click “Restore” operation under “Settings->Maintenance->Migration” tab to restore EIP from new controller back to the old controller if user decides to revert the “Migration” process.
- New controller invokes cloud API to “Start” the old controller from “STOP” state
- New controller waits until old controller virtual machine is ready
- New controller invokes cloud API to transfer EIP back to old controller
- New controller invokes cloud API to stop itself