Merge lp:~thumper/juju-core/provisioner-reget-state-info into lp:~go-bot/juju-core/trunk
Status: | Merged |
---|---|
Approved by: | Tim Penhey |
Approved revision: | no longer in the source branch. |
Merged at revision: | 1292 |
Proposed branch: | lp:~thumper/juju-core/provisioner-reget-state-info |
Merge into: | lp:~go-bot/juju-core/trunk |
Diff against target: |
292 lines (+46/-112) 4 files modified
worker/provisioner/export_test.go (+2/-2) worker/provisioner/provisioner.go (+11/-15) worker/provisioner/provisioner_task.go (+33/-22) worker/provisioner/provisioner_test.go (+0/-73) |
To merge this branch: | bzr merge lp:~thumper/juju-core/provisioner-reget-state-info |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Juju Engineering | Pending | ||
Review via email:
|
This proposal supersedes a proposal from 2013-06-10.
Commit message
Provisioner gets addresses for each new machine.
The addresses are retrieved each time we attempt to start a machine. This
allows the provisioner to take advantage of any new api or state servers that
are started as part of a block of machines being provisioned at one time.
Description of the change
Provisioner gets addresses for each new machine.
The addresses are retrieved each time we attempt to start a machine. This
allows the provisioner to take advantage of any new api or state servers that
are started as part of a block of machines being provisioned at one time.
There is some saving of addresses at this stage to make the existing tests
pass, even though this goes a little against what William has mentioned
before. If we have invalid config, the tests assume that we continue with old
info, whereas William has suggested that we pause provisioning while the
config is broken.
One behavioural tweak in this branch. If we do fail to setup authentication,
we no longer kill the task, but instead log and continue. We will attempt to
start it again next time through the loop.
Reviewers: mp+168562_ code.launchpad. net,
Message:
Please take a look.
Description:
Provisioner gets addresses for each new machine.
The addresses are retrieved each time we attempt to start a machine.
This
allows the provisioner to take advantage of any new api or state servers
that
are started as part of a block of machines being provisioned at one
time.
There is some saving of addresses at this stage to make the existing
tests
pass, even though this goes a little against what William has mentioned
before. If we have invalid config, the tests assume that we continue
with old
info, whereas William has suggested that we pause provisioning while the
config is broken.
One behavioural tweak in this branch. If we do fail to setup
authentication,
we no longer kill the task, but instead log and continue. We will
attempt to
start it again next time through the loop.
https:/ /code.launchpad .net/~thumper/ juju-core/ provisioner- reget-state- info/+merge/ 168562
(do not edit description out of merge proposal)
Please review this at https:/ /codereview. appspot. com/9824047/
Affected files: provisioner/ export_ test.go provisioner/ provisioner. go provisioner/ provisioner_ task.go
A [revision details]
M worker/
M worker/
M worker/