Merge lp:~jameinel/maas/1.2-node-get-effective-kernel-options into lp:maas/1.2
Proposed by
John A Meinel
Status: | Merged |
---|---|
Approved by: | John A Meinel |
Approved revision: | no longer in the source branch. |
Merged at revision: | 1287 |
Proposed branch: | lp:~jameinel/maas/1.2-node-get-effective-kernel-options |
Merge into: | lp:maas/1.2 |
Diff against target: |
44 lines (+23/-0) 2 files modified
src/maasserver/models/node.py (+12/-0) src/maasserver/tests/test_node.py (+11/-0) |
To merge this branch: | bzr merge lp:~jameinel/maas/1.2-node-get-effective-kernel-options |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Martin Packman (community) | Approve | ||
Review via email: mp+133205@code.launchpad.net |
Commit message
Add Node.get_
The first implementation only reads the global setting. Ones handling tags will come later.
Description of the change
This just provides the internal method, so that Dimiter can use it to continue forward on the UI level changes.
The next follow up will merge Martin's pending DB change, and expose values from tags.
To post a comment you must log in.
Looks good. Worth noting, is that if the first tuple item is not None, the second must be a string, as we should only match tags that have kernel parameters.