Merge lp:~gmb/maas/start-and-allocate-bug-1365591 into lp:~maas-committers/maas/trunk
Proposed by
Graham Binns
Status: | Merged |
---|---|
Approved by: | Graham Binns |
Approved revision: | no longer in the source branch. |
Merged at revision: | 3243 |
Proposed branch: | lp:~gmb/maas/start-and-allocate-bug-1365591 |
Merge into: | lp:~maas-committers/maas/trunk |
Diff against target: |
70 lines (+37/-2) 2 files modified
src/maasserver/node_action.py (+12/-2) src/maasserver/tests/test_node_action.py (+25/-0) |
To merge this branch: | bzr merge lp:~gmb/maas/start-and-allocate-bug-1365591 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Raphaël Badin (community) | Approve | ||
Gavin Panella (community) | Approve | ||
Review via email: mp+238130@code.launchpad.net |
Commit message
The "Start node" button in the UI now:
- Also acquires the node for the user if it hasn't already been acquired.
- Displays "Acquire and start node" if the node isn't allocated to the user, and "Start node" if it is.
Per comments on bug 1365591, I considered adding "(with default options)" to the button label, but until bug 1379187 is fixed, this is kind of meaningless and confusing.
To post a comment you must log in.
I think there is a small problem with this branch: you've implemented this in the UI code and thus if you try to 'start' a non-allocated from the API, it will fail. I think this difference is bad because you'll get two different behavior depending on where you perform the same action (UI vs. API).
Maybe you can salvage something from this: https:/ /code.launchpad .net/~rvb/ maas/bug- 1365591- transparent- allocation/ +merge/ 237778 (complete WIP that I started last week but didn't finish yet)