Advanced networking (VLAN, bonded NIC etc)

Registered by Julian Edwards on 2013-10-09

Users are starting to request advanced networking setups, we need to support VLANs, bonded NICs and anything else that comes up in discussion.

Blueprint information

Status:
Complete
Approver:
Daniel Westervelt
Priority:
Essential
Drafter:
Julian Edwards
Direction:
Approved
Assignee:
None
Definition:
Approved
Series goal:
Accepted for 1.5
Implementation:
Implemented
Milestone target:
milestone icon 14.04
Started by
Julian Edwards on 2014-02-05
Completed by
Julian Edwards on 2014-04-02

Whiteboard

MAAS Advanced networking
========================

Use cases:
- support multiple network interfaces for dhcp on a cluster
- pxe boot from one interface (management network), normal operations on another (prod network)
- bond network interfaces on node
- determine IP address and this DNS entry based on arbitrary interface, not necessarily one that was used to DHCP/PXE with.
- Cluster controllers need to know what VLANs exist, then juju can deploy using a vlan tag and MAAS will set a node to use that VLAN. Requires MAAS to push this into a preseed.
- Need to know what interfaces and VLANs are on a node. Use LLDP to detect VLANs (tagged or port switched) and fall back to manual input.

Ideas:
- use the MAC address instead of the interface name on MAAS' side
- get MAAS to manage more than one interface (and use one for enlisting/commissioning and one for all the rest): https://bugs.launchpad.net/maas/+bug/1052339 (select which one is used for DNS)

Estimates:
Multi-interfaces on clusters: 2 weeks
installer user data: 1 day
VLAN setup: 2-3 weeks

(?)

Work Items

Work items:
Handle multiple cluster controller network interfaces for DHCP: DONE
Network placement constraints: DONE
Have a way to mark which VLANs a node can access: DONE
Autodetect existing VLANs through LLDP: POSTPONED

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.