Skip to content

Instantly share code, notes, and snippets.

@aspen-roller
Created March 30, 2021 17:16
Show Gist options
  • Save aspen-roller/e065c67a1326ad8b638e54000c2a35bc to your computer and use it in GitHub Desktop.
Save aspen-roller/e065c67a1326ad8b638e54000c2a35bc to your computer and use it in GitHub Desktop.
reactivate preprod (deallocated)

These are the steps I run to turn preprod back on and verify. Once oidc is up, you can run the node.js, springboot, and ui playbooks in parallel (I've fixed the overwriting problem with generating .env files).

ap-preprod azure-start.yml
ap-preprod services-nodejs.yml -l oidc
ap-preprod services-nodejs.yml -l oidc -t init_pm2
ap-preprod services-nodejs.yml -l non_oidc
ap-preprod services-nodejs.yml -l non_oidc -t init_pm2
ap-preprod services-spring.yml
ap-preprod ui.yml
ap-preprod marsnet-status.yml

Troubleshooting

azure-start

Sometimes Azure is super slow with turning the vm's back on and you will get a failure with the playbook. Just re-run the azure-start.yml playbook until everything is up and it completes without error.

init_pm2

I don't believe this should be necessary, but for some reason Node.js services have not been turning back on without running this additional step.

Optimization

Run 3 playbooks in parallel after oidc is up.

# terminal 1
ap-preprod services-nodejs.yml -l non_oidc
ap-preprod services-nodejs.yml -l non_oidc -t init_pm2
# terminal 2
ap-preprod services-spring.yml2
# terminal 3
ap-preprod ui.yml2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment