Merge lp:~jtv/maas/identify-auto-interfaces into lp:~maas-committers/maas/trunk
Status: | Merged |
---|---|
Approved by: | Jeroen T. Vermeulen |
Approved revision: | no longer in the source branch. |
Merged at revision: | 3158 |
Proposed branch: | lp:~jtv/maas/identify-auto-interfaces |
Merge into: | lp:~maas-committers/maas/trunk |
Diff against target: |
76 lines (+54/-0) 2 files modified
src/maasserver/networking_preseed.py (+17/-0) src/maasserver/tests/test_networking_preseed.py (+37/-0) |
To merge this branch: | bzr merge lp:~jtv/maas/identify-auto-interfaces |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Graham Binns (community) | Approve | ||
Review via email: mp+236688@code.launchpad.net |
Commit message
Select network interfaces on a node that should be brought up automatically on boot. This is part of the work for writing its /etc/network/
We chose the selection behaviour as being the closest to existing behaviour, not as the ideal behaviour as we would without the time constraints. In the normal situation where a node has one network interface on a network where MAAS manages DHCP, it is identical to what happens in the current code. If the node has multiple network interfaces on one or more MAAS-managed networks, they will all come up; the existing code will only bring up the interface from which the node netbooted, and some people seem to run into problems in this situation. And finally, if the node is not connected to any MAAS-managed DHCP, we have no knowledge of how the machine netbooted, so we bring up all interfaces.
Description of the change
Dimiter agrees that this seems like a sensible approach. In the future we'll work on ways for users to customise nodes' networking setup in more detail, not as an excuse for avoiding this question ourselves, but to extend the portion of networking that MAAS can manage for you.
Jeroen
Approved with one minor comment. Nice work :).