Public bug reported: Non-agent based (eg Opendaylight) controllers need to attach interfaces, such as that created by DNSMasq/dhcp agent, to devices they control. Currently this is not possible because, apart from the Null driver, which as the name says is Null in its intent, there is no driver that initializes the network namespaces.
Proposed fix in: https://review.openstack.org/#/c/337263/ ** Affects: neutron Importance: Undecided Status: New ** Description changed: - Non-agent based (eg Opendaylight) controllers need to attach interfaces, such as that created by DNSMasq) to devices they control. + Non-agent based (eg Opendaylight) controllers need to attach interfaces, such as that created by DNSMasq/dhcp agent, to devices they control. Currently this is not possible because, apart from the Null driver, which as the name says is Null in its intent, there is no driver that initializes the network namespaces. - Proposed fix in: + Proposed fix in: https://review.openstack.org/#/c/337263/ -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1602798 Title: No namespaces initializing device independent interface driver Status in neutron: New Bug description: Non-agent based (eg Opendaylight) controllers need to attach interfaces, such as that created by DNSMasq/dhcp agent, to devices they control. Currently this is not possible because, apart from the Null driver, which as the name says is Null in its intent, there is no driver that initializes the network namespaces. Proposed fix in: https://review.openstack.org/#/c/337263/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1602798/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
