scope: container is too ambiguous and confusing

Bug #1499900 reported by Marco Ceppi on 2015-09-25
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju
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.

Aaron Bentley (abentley) on 2015-09-28
Changed in juju-core:
status: New → Triaged
importance: Undecided → Low
Changed in juju-core:
milestone: none → 1.26-alpha1
tags: added: bug-squad
Curtis Hovey (sinzui) on 2015-11-03
Changed in juju-core:
milestone: 1.26-alpha1 → 1.26-alpha2
Curtis Hovey (sinzui) on 2015-11-03
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
Marco Ceppi (marcoceppi) on 2017-01-25
tags: added: adoption
Anastasia (anastasia-macmood) wrote :

Removing 2.1 milestone as we will not be addressing this issue in 2.1.

Changed in juju:
milestone: 2.1.0 → none
tags: added: charmers
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers