Merge ~cjwatson/launchpad-mojo-specs:prod-containers into launchpad-mojo-specs:master
Proposed by
Colin Watson
Status: | Merged |
---|---|
Merged at revision: | 031498fdd09f87ae4dd510f4e240e3247b6cbb47 |
Proposed branch: | ~cjwatson/launchpad-mojo-specs:prod-containers |
Merge into: | launchpad-mojo-specs:master |
Diff against target: |
84 lines (+24/-0) 1 file modified
mojo-lp-git/services (+24/-0) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Colin Watson (community) | Approve | ||
Review via email: mp+372775@code.launchpad.net |
Commit message
Hardcode machine names for production deployment
On production, we want a carefully-arranged combination of VMs and LXD
containers. Setting this up requires hardcoding some machine names.
This assumes that four machines have been created prior to deployment:
we currently expect 2 and 3 to be manually-deployed VMs on 0 and 1
respectively.
To post a comment you must log in.
Self-approving this, as we need to get on with the production deployment and the worst case here is that that very deployment initially fails and needs to be adjusted.