MachineConfig client API is too low-level
Bug #1270043 reported by
Andrew Wilkins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
High
|
Andrew Wilkins | ||
Bug Description
The MachineConfig API was introduced in 1.17.0 to enable manual provisioning without using a state connection. This API is used to obtain enough information to generate cloud-config, which is then converted to a shell script to be run on a machine.
I have just had to introduce a new API, ProvisioningScript, that wraps all of that up (sans execution), so that manual provisioning can be done without requiring SSH access. We should use this API in manual provisioning as well.
This should be done before 1.18 is released, so the MachineConfig API can be removed without backwards-
Related branches
lp://staging/~axwalk/juju-core/lp1270043-drop-machineconfig-api
- Juju Engineering: Pending requested
-
Diff: 562 lines (+157/-189)10 files modifiedcloudinit/sshinit/configure.go (+12/-4)
environs/manual/provisioner.go (+32/-19)
environs/manual/provisioner_test.go (+1/-4)
provider/common/bootstrap.go (+4/-4)
state/api/client.go (+0/-10)
state/api/params/params.go (+0/-18)
state/apiserver/client/client.go (+1/-11)
state/apiserver/client/client_test.go (+1/-71)
state/statecmd/machineconfig.go (+16/-48)
state/statecmd/machineconfig_test.go (+90/-0)
| Changed in juju-core: | |
| status: | New → Triaged |
| Changed in juju-core: | |
| status: | Triaged → In Progress |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| milestone: | 1.17.1 → 1.17.2 |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
