Merge lp:~thumper/juju-core/maas-lxc into lp:juju-core/1.16
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Tim Penhey | ||||
Approved revision: | no longer in the source branch. | ||||
Merged at revision: | 1980 | ||||
Proposed branch: | lp:~thumper/juju-core/maas-lxc | ||||
Merge into: | lp:juju-core/1.16 | ||||
Diff against target: |
491 lines (+142/-107) 12 files modified
container/lxc/lxc.go (+12/-47) container/lxc/lxc_test.go (+6/-8) environs/cloudinit.go (+20/-12) provider/local/environ.go (+7/-9) state/api/params/params.go (+8/-0) state/api/provisioner/provisioner.go (+14/-0) state/api/provisioner/provisioner_test.go (+8/-0) state/apiserver/provisioner/provisioner.go (+14/-0) state/apiserver/provisioner/provisioner_test.go (+8/-0) worker/provisioner/lxc-broker.go (+21/-7) worker/provisioner/lxc-broker_test.go (+7/-2) worker/provisioner/provisioner.go (+17/-22) |
||||
To merge this branch: | bzr merge lp:~thumper/juju-core/maas-lxc | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Juju Engineering | Pending | ||
Review via email: mp+193405@code.launchpad.net |
Commit message
Fix LXC containers on MAAS
We can't get a real CI framework soon enough.
When the provisioner was updated to use the API, this
accidentally broke LXC on MAAS, as the secret attributes
are stripped from the environment config for non-manager
nodes. This makes a completely invalid MAAS config, which
means the LCX provisioner task never starts.
There was no easy fix for this, so the correct one had
to do. That is to provide an API call to get what the
containers actually need, and not have them depend on
things they don't need.
I took this opportunity to also simplify the parameters
for the StartContainer call.
Description of the change
Fix LXC containers on MAAS
We can't get a real CI framework soon enough.
When the provisioner was updated to use the API, this
accidentally broke LXC on MAAS, as the secret attributes
are stripped from the environment config for non-manager
nodes. This makes a completely invalid MAAS config, which
means the LCX provisioner task never starts.
There was no easy fix for this, so the correct one had
to do. That is to provide an API call to get what the
containers actually need, and not have them depend on
things they don't need.
I took this opportunity to also simplify the parameters
for the StartContainer call.
Reviewers: mp+193405_ code.launchpad. net,
Message:
Please take a look.
Description:
Fix LXC containers on MAAS
We can't get a real CI framework soon enough.
When the provisioner was updated to use the API, this
accidentally broke LXC on MAAS, as the secret attributes
are stripped from the environment config for non-manager
nodes. This makes a completely invalid MAAS config, which
means the LCX provisioner task never starts.
There was no easy fix for this, so the correct one had
to do. That is to provide an API call to get what the
containers actually need, and not have them depend on
things they don't need.
I took this opportunity to also simplify the parameters
for the StartContainer call.
https:/ /code.launchpad .net/~thumper/ juju-core/ maas-lxc/ +merge/ 193405
(do not edit description out of merge proposal)
Please review this at https:/ /codereview. appspot. com/20220043/
Affected files (+143, -107 lines): lxc/lxc. go lxc/lxc_ test.go cloudinit. go local/environ. go params/ params. go provisioner/ provisioner. go provisioner/ provisioner_ test.go /provisioner/ provisioner. go /provisioner/ provisioner_ test.go provisioner/ lxc-broker. go provisioner/ lxc-broker_ test.go provisioner/ provisioner. go
A [revision details]
M container/
M container/
M environs/
M provider/
M state/api/
M state/api/
M state/api/
M state/apiserver
M state/apiserver
M worker/
M worker/
M worker/