Dev deployment, production deployment
Bug #1287816 reported by
Evan
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu CI Engine |
Confirmed
|
Undecided
|
Evan | ||
Bug Description
Create a minimal deployer config that puts multiple services on the same instance. Use --to (to: in juju-deployer) and different tcp ports for each service to accomplish this.
We can significantly reduce the number of nodes we need for a dev deployment. Ensuring that all of the data for a charm is sufficiently isolated from other charms will be key. https:/
| tags: | added: airline |
| Changed in ubuntu-ci-services-itself: | |
| assignee: | nobody → Evan Dandrea (ev) |
| milestone: | none → backlog |
Revision history for this message
| Vincent Ladeuil (vila) wrote | #1 |
| Changed in ubuntu-ci-services-itself: | |
| status: | New → Confirmed |
| summary: |
- Dev development, production deployment + Dev deployment, production deployment |
| Changed in uci-engine: | |
| assignee: | nobody → Evan Dandrea (ev) |
| milestone: | none → backlog |
| status: | New → Confirmed |
| no longer affects: | ubuntu-ci-services-itself |
To post a comment you must log in.
In the same vein, I've been wondering if we could reduce our whole deployment to use fewer instances. If 6 of us do deploy 15 instances at the same time, we're using nearly half of the 197 instances mentioned recently when lcy02 was almost dead...