NodeGroupInterface is not linked to Network

Bug #1341619 reported by Gavin Panella on 2014-07-14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Julian Edwards
Julian Edwards

Bug Description

NodeGroupInterface's docstring notes:

    This class duplicates some of :class:`Network`, and adds settings for
    managing DHCP. Some day we hope to delegate the duplicated fields, and
    have auto-discovery populate the :class:`Network` model along the way.

The introduction of the latter of NodeGroupInterface or Network should not have been done without linking NGI to Network. MAAS now has two models of the networks it interacts with.

Related branches

Julian Edwards (julian-edwards) wrote :

I thought about and suggested a model change in my DHCP work to handle this, so it should be relatively straightforward.

Changed in maas:
assignee: nobody → Julian Edwards (julian-edwards)
Changed in maas:
status: Triaged → In Progress
Julian Edwards (julian-edwards) wrote :

The linked branches auto-link MACs to networks which themselves are auto-populated from cluster interfaces.

The next step is to migrate code away from using NodeGroupInterface network settings, and then once complete, remove those settings from NGI completely and this bug will be fixed.

Changed in maas:
milestone: none → 1.6.1
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers