[2.2b3] 'deploy' API endpoint doesn't automatically allocate a machine
Bug #1672363 reported by
Andres Rodriguez
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Mike Pontillo | ||
Bug Description
The 'deploy' API endpoint requires an 'allocated' machines. This API endpoint should allow to automatically allocate a machine and deploy it, passing the same constraints as are passed to the 'allocate' API endpoint.
This would allow users to deploy RSD machines without first having to allocate them via the API (as the 'deploy' endpoint could allocate+deploy).
Related branches
lp:~mpontillo/maas/fix-deploy-auto-allocate--bug-1672363
- Blake Rouse (community): Approve
-
Diff: 232 lines (+150/-15)3 files modifiedsrc/maasserver/api/machines.py (+52/-14)
src/maasserver/api/tests/test_machine.py (+97/-0)
src/maasserver/models/node.py (+1/-1)
| Changed in maas: | |
| milestone: | none → 2.2.0 |
| importance: | Undecided → High |
| status: | New → Triaged |
| tags: | added: rsd |
| Changed in maas: | |
| milestone: | 2.2.0 → 2.2.0rc1 |
| Changed in maas: | |
| assignee: | nobody → LaMont Jones (lamont) |
| assignee: | LaMont Jones (lamont) → nobody |
| Changed in maas: | |
| milestone: | 2.2.0rc1 → 2.2.0rc2 |
| Changed in maas: | |
| milestone: | 2.2.0rc2 → 2.2.0rc3 |
| Changed in maas: | |
| assignee: | nobody → Mike Pontillo (mpontillo) |
Revision history for this message
| Mike Pontillo (mpontillo) wrote | #1 |
| Changed in maas: | |
| status: | Triaged → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
We discussed this as a team this week and decided that for MAAS 2.2, we would change the 'machine deploy' operation (which requires a system_id) to allow allocation *and* deployment, for consistency with the MAAS UI.
Adding an API to allow allocation plus deployment based on a set of constraints should be filed separately.