cross-model relations
Bug #1049340 reported by
James Troup
This bug affects 28 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Ian Booth | ||
| juju-core |
Won't Fix
|
Medium
|
Unassigned | ||
| pyjuju |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
It's fairly well accepted best common practice to run services in
multiple regions in any given cloud (AWS or OpenStack) for maximum
availability.
Unfortunately juju doesn't support this model as relations can't span
across environments and each region is its own environment.
This also makes it hard to e.g. run a multi-DC swift as deployed by
MAAS and Juju.
Revision history for this message
| Clint Byrum (clint-fewbar) wrote | #1 |
| Changed in juju: | |
| status: | New → Confirmed |
| importance: | Undecided → Wishlist |
| tags: | added: production |
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| summary: |
- juju relations can not be used across regions + cross-environment relations |
| tags: | added: cts |
| tags: | added: story-cross-env-relations |
| tags: | added: cts-cloud-review |
| tags: |
added: canonistack removed: cts-cloud-review production |
| tags: | added: feature |
| tags: | removed: story-cross-env-relations |
| tags: |
added: cts-cloud-review removed: cts |
| tags: | added: canonical-is |
| Changed in juju-core: | |
| importance: | High → Medium |
| tags: | added: ubuntu-engineering |
| tags: | added: cts |
| tags: | removed: cts cts-cloud-review |
Revision history for this message
| Nick Moffitt (nick-moffitt) wrote Re: cross-environment relations | #2 |
| summary: |
- cross-environment relations + cross-model relations |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| milestone: | none → 2.1.0 |
| Changed in juju-core: | |
| status: | Triaged → Won't Fix |
| Changed in juju: | |
| milestone: | 2.1.0 → 2.2.0-beta1 |
| Changed in juju: | |
| milestone: | 2.2.0-beta1 → 2.2.0 |
| Changed in juju: | |
| milestone: | 2.2-beta1 → 2.3-alpha1 |
| Changed in juju: | |
| milestone: | 2.3-beta1 → 2.3-beta2 |
| Changed in juju: | |
| assignee: | nobody → Ian Booth (wallyworld) |
| status: | Triaged → Fix Committed |
| Changed in juju: | |
| milestone: | 2.3-beta2 → 2.3-beta1 |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
There are a number of workarounds, but none of them are attractive. Users will absolutely need a clear way to have service orchestration cross from one environment to another.