-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MIgrate Micromasters resources into management by Pulumi #1090
Comments
Re-opening because we still need to transition the actual production Heroku app. |
Necessary steps to finish migration in production:
|
To help determine when to schedule the cutover @feoh will be doing a trial run of the dump/load of Postgres in the production environment so that we can collect timing information and identify any variance from the RC process. |
Exact steps for migration with timings and rollback sequence: @2:30 PM EDT@feoh will put the micromasters production app into maint. mode and trigger the database transfer.
@2:40 PM EDT@shaidar will trigger the Salt proxy update:
@feoh will trigger a catch-up s3 sync and upon ack. of completion from @shaidur take the app out of maint. mode:
@2:50 PM EDT@pdpinch @feoh and @annagav will spot check and 'smoke test' micromasters production and declare success or need for rollback. Rollback@shaidar will revert the Salt proxy configuration to prior values using saved data.
|
I would say that you can actually take it out of maintenance mode prior to finalizing the S3 sync |
Current status:The database transfer and migration were successful. However, we are having problems transitioning the CDN to the new CloudFront distribution we created, so we're still using the old S3 bucket. The team will reconvene tomorrow and troubleshoot this remaining issue, but as of now production is up and all tests look good. |
All set as of yesterday evening! \o/ |
Post-work resource clean-up list:
|
User Story
As a platform engineer I want to make sure that the Micromasters application and its infrastructure resources are being managed in the same way as all of our other systems.
Description/Context
The Micromasters application was set up before our current usage of Pulumi and before we had established some of the patterns that led to the creation of the
apps
VPC. The result is that the RDS instance used in production was created in its own VPC and the Vault policies are managed via Salt code which is being actively deprecated. There are also associated S3 buckets that were created either manually or via Salt and are not being actively managed by Pulumi.Acceptance Criteria
The text was updated successfully, but these errors were encountered: