scope: container is too ambiguous and confusing
Bug #1499900 reported by
Marco Ceppi
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Expired
|
High
|
Unassigned | ||
Bug Description
Subordinates are declared using scope: container on one or more interfaces. However, with the popularization of containers in todays cloud world the scope key creates confusion. I'd propose to continue supporting scope container but shift the language for subordinates to "scope: unit" which embodies what container scope meant with the language of the current juju model.
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| Changed in juju-core: | |
| milestone: | none → 1.26-alpha1 |
| tags: | added: bug-squad |
| Changed in juju-core: | |
| milestone: | 1.26-alpha1 → 1.26-alpha2 |
| Changed in juju-core: | |
| milestone: | 1.26-alpha2 → 2.0-alpha1 |
| importance: | Low → High |
| Changed in juju-core: | |
| milestone: | 2.0-alpha1 → 2.0-alpha2 |
| Changed in juju-core: | |
| milestone: | 2.0-alpha2 → 2.0-alpha3 |
| Changed in juju-core: | |
| milestone: | 2.0-alpha3 → 2.0-beta4 |
| Changed in juju-core: | |
| milestone: | 2.0-beta4 → 2.1.0 |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.1.0 → none |
| milestone: | none → 2.1.0 |
| tags: | added: adoption |
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #1 |
| Changed in juju: | |
| milestone: | 2.1.0 → none |
| tags: | added: charmers |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #2 |
| Changed in juju: | |
| status: | Triaged → Expired |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
Removing 2.1 milestone as we will not be addressing this issue in 2.1.