include maas resetMachine() API primitive
Bug #1536346 reported by
David Britton
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Critical
|
Unassigned | ||
| 1.9 |
Won't Fix
|
Critical
|
Unassigned | ||
Bug Description
As discussed/agreed to, when you get a handle on a machine (or node, or whatever it will be called in the new API), please include a 'reset()' method that will:
* iterate through all NICs and reset to an as-commissioned state
* iterate through all disks and reset to an as-commissioned state
* more-or-less set the machine back to how it looked after commissioning.
Related branches
lp:~ltrager/maas/reset_node
- Andres Rodriguez (community): Approve
- Gavin Panella (community): Approve
-
Diff: 457 lines (+286/-2)7 files modifiedsrc/maasserver/api/devices.py (+28/-0)
src/maasserver/api/machines.py (+44/-2)
src/maasserver/api/tests/test_devices.py (+44/-0)
src/maasserver/api/tests/test_machine.py (+91/-0)
src/maasserver/models/node.py (+22/-0)
src/maasserver/models/tests/test_node.py (+47/-0)
src/maasserver/testing/factory.py (+10/-0)
| tags: | added: api |
| Changed in maas: | |
| milestone: | none → 1.9.1 |
| status: | New → Triaged |
| importance: | Undecided → High |
| Changed in maas: | |
| importance: | High → Critical |
| Changed in maas: | |
| milestone: | 1.9.1 → 2.0.0 |
| Changed in maas: | |
| status: | Triaged → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
