Merge lp:~wallyworld/juju-core/unit-agent-knows-assigned-machine into lp:~go-bot/juju-core/trunk
Status: | Rejected |
---|---|
Rejected by: | William Reade |
Proposed branch: | lp:~wallyworld/juju-core/unit-agent-knows-assigned-machine |
Merge into: | lp:~go-bot/juju-core/trunk |
Prerequisite: | lp:~wallyworld/juju-core/machiner-access-for-uniter |
Diff against target: |
411 lines (+147/-22) 8 files modified
agent/agent.go (+1/-0) state/api/uniter/unit.go (+43/-19) state/api/uniter/unit_test.go (+24/-0) state/api/uniter/uniter.go (+2/-2) state/apiserver/uniter/uniter.go (+38/-0) state/apiserver/uniter/uniter_test.go (+32/-0) worker/deployer/simple.go (+2/-0) worker/deployer/simple_test.go (+5/-1) |
To merge this branch: | bzr merge lp:~wallyworld/juju-core/unit-agent-knows-assigned-machine |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Juju Engineering | Pending | ||
Review via email: mp+205291@code.launchpad.net |
Description of the change
Unit agents know their assigned machine
The unit agent conf file has a new value called
MACHINE_TAG added when the unit is deployed. The
value is the tag of the machine on which the
unit is deployed.
To allow new tools to run on older deployments
without the updated agent conf file, a new Uniter
API is provided which allows the unit agent to
look up the assigned machine over the API.
The API will be removed when it is possible
to have all current unit agent config files
upgraded.
This functionality is used by a downstream
branch which reworks the uniter upgrade worker.
Unmerged revisions
- 2308. By Ian Booth
-
Add test
- 2307. By Ian Booth
-
Merged machiner-
access- for-uniter into unit-agent- knows-assigned- machine. - 2306. By Ian Booth
-
Merge trunk, resolve conflict
- 2305. By Ian Booth
-
Unit agents can find out their assigned machine
- 2304. By Ian Booth
-
Unit agents have read access to machines on which their units are deployed
Reviewers: mp+205291_ code.launchpad. net,
Message:
Please take a look.
Description:
Unit agents know their assigned machine
The unit agent conf file has a new value called
MACHINE_TAG added when the unit is deployed. The
value is the tag of the machine on which the
unit is deployed.
To allow new tools to run on older deployments
without the updated agent conf file, a new Uniter
API is provided which allows the unit agent to
look up the assigned machine over the API.
The API will be removed when it is possible
to have all current unit agent config files
upgraded.
This functionality is used by a downstream
branch which reworks the uniter upgrade worker.
https:/ /code.launchpad .net/~wallyworl d/juju- core/unit- agent-knows- assigned- machine/ +merge/ 205291
Requires: /code.launchpad .net/~wallyworl d/juju- core/machiner- access- for-uniter/ +merge/ 205290
https:/
(do not edit description out of merge proposal)
Please review this at https:/ /codereview. appspot. com/60930043/
Affected files (+126, -22 lines): uniter/ unit.go uniter/ unit_test. go uniter/ uniter. go /uniter/ uniter. go /uniter/ uniter_ test.go deployer/ simple. go deployer/ simple_ test.go
A [revision details]
M agent/agent.go
M state/api/
M state/api/
M state/api/
M state/apiserver
M state/apiserver
M worker/
M worker/