Statusd -- deployment side status computation
Bug #843539 reported by
Benjamin Saller
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyjuju |
In Progress
|
Wishlist
|
Benjamin Saller |
Bug Description
This branch includes changes designed to allow for computing status on topology change and writing the output to a YAML node in ZK. The status of this node will always represent the current view and the lclient simply queries this value and does its normal filtering as post-processing.
Related branches
lp:~bcsaller/pyjuju/statusd
- Kapil Thangavelu (community): Needs Fixing
- Jim Baker (community): Needs Fixing
- Gustavo Niemeyer: Needs Fixing
-
Diff: 1330 lines (+738/-317)10 files modifiedjuju/agents/provision.py (+15/-2)
juju/agents/tests/test_provision.py (+51/-2)
juju/control/status.py (+30/-129)
juju/control/tests/test_status.py (+23/-179)
juju/environment/config.py (+1/-1)
juju/environment/tests/test_config.py (+0/-1)
juju/providers/common/tests/test_utils.py (+34/-3)
juju/providers/common/utils.py (+16/-0)
juju/state/status.py (+181/-0)
juju/state/tests/test_status.py (+387/-0)
Changed in ensemble: | |
milestone: | none → eureka |
assignee: | nobody → Benjamin Saller (bcsaller) |
status: | New → In Progress |
Changed in juju: | |
milestone: | eureka → florence |
Changed in juju: | |
milestone: | florence → honolulu |
Changed in juju: | |
milestone: | 0.6 → none |
Changed in juju: | |
milestone: | none → 0.8 |
To post a comment you must log in.
*cool*