Policy charms should be able to be deployed along side other charms inside the same machine/container.
Bug #805585 reported by
Ahmed Kamal
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| pyjuju |
Fix Released
|
High
|
Benjamin Saller | ||
Bug Description
Multiple charms should be allowed to co-exist on a single instance. The use case for that would be running machine policy charms.
Related branches
lp:~bcsaller/pyjuju/subordinate-unit-agent-deploy
- Kapil Thangavelu (community): Approve
-
Diff: 6987 lines (+3444/-2964)27 files modifiedexamples/precise/recorder/hooks/juju-info-relation-changed (+5/-0)
examples/precise/recorder/hooks/juju-info-relation-departed (+3/-0)
examples/precise/recorder/hooks/juju-info-relation-joined (+6/-0)
examples/precise/recorder/metadata.yaml (+9/-0)
examples/precise/recorder/revision (+1/-0)
juju/agents/tests/test_machine.py (+2/-2)
juju/control/destroy_service.py (+29/-0)
juju/control/remove_relation.py (+24/-1)
juju/control/remove_unit.py (+6/-3)
juju/control/tests/test_destroy_service.py (+94/-0)
juju/control/tests/test_remove_relation.py (+21/-1)
juju/control/tests/test_remove_unit.py (+16/-2)
juju/environment/config.py (+4/-3)
juju/lib/lxc/__init__.py (+8/-4)
juju/lib/lxc/tests/test_lxc.py (+12/-6)
juju/machine/unit.py (+22/-0)
juju/state/errors.py (+29/-5)
juju/state/hook.py (+1/-0)
juju/state/relation.py (+14/-5)
juju/state/tests/test_errors.py (+29/-4)
juju/state/tests/test_hook.py (+61/-14)
juju/state/tests/test_relation.py (+5/-5)
juju/state/tests/test_service.py (+2868/-2890)
juju/unit/charm.py (+1/-0)
juju/unit/deploy.py (+13/-12)
juju/unit/lifecycle.py (+53/-2)
juju/unit/tests/test_lifecycle.py (+108/-5)
Revision history for this message
| Gustavo Niemeyer (niemeyer) wrote | #1 |
Revision history for this message
| Clint Byrum (clint-fewbar) wrote | #2 |
| Changed in juju: | |
| status: | New → In Progress |
| importance: | Undecided → High |
| assignee: | nobody → Benjamin Saller (bcsaller) |
| description: | updated |
| summary: |
- Break the one service-unit per instance assumption + Policy charms should be able to be deployed along side other charms + inside the same machine/container. |
| Changed in juju: | |
| milestone: | none → florence |
| Changed in juju: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
There are several separate use cases baked into that description, and we'll have to tweak it to refer to a single one of these:
1) Running multiple unrelated service units on one machine
2) Running multiple service units on the same root with the purpose of interaction between the formulas
3) Running a formula at machine level, outside of any containment, with the purpose of controlling the machine itself
(1) is about LXC support, (2) is about the co-location feature we debated in Dublin and being speced by Ben, and (3) has not been covered in any conversation.