Merge lp:~rvb/maas/rm-cluster-interf-connexion into lp:~maas-committers/maas/trunk
Status: | Merged |
---|---|
Approved by: | Raphaël Badin |
Approved revision: | no longer in the source branch. |
Merged at revision: | 3611 |
Proposed branch: | lp:~rvb/maas/rm-cluster-interf-connexion |
Merge into: | lp:~maas-committers/maas/trunk |
Prerequisite: | lp:~rvb/maas/no-nodegroup-for-devices |
Diff against target: |
150 lines (+1/-105) 2 files modified
src/maasserver/api/devices.py (+1/-42) src/maasserver/api/tests/test_devices.py (+0/-63) |
To merge this branch: | bzr merge lp:~rvb/maas/rm-cluster-interf-connexion |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Blake Rouse (community) | Approve | ||
Review via email: mp+251880@code.launchpad.net |
Commit message
Remove the API that gives the user the ability to link a device's MAC to a cluster interface. This isn't an API endpoint we want to have to maintain in 1.8 when networks and cluster interface will be more strictly tied together.
Description of the change
Although we still internally use the connection between a cluster interface and a MAC to figure out to which network a MAC is connected to, we don't want to expose this to the user as this will be refactored heavily in 1.8.
The ways to connect a MAC to a cluster interface are:
- set a parent for the device: the device primary MAC will be connected to the same cluster interface the parent is PXE booting from
- have the device DHCP off MAAS. Then MAAS will make the connection between the MAC and the cluster interface (this is done in a follow-up branch).
- explicitly claim a particular IP address for a MAC address: if this IP is part of a network MAAS manages, it will create the connection with the right cluster interface.