[DOC] Document subport/parent MAC address relationship

Bug #1689300 reported by Alex Stafeyev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Invalid
Wishlist
Unassigned

Bug Description

Description of problem:
We need to documents that while create sub-port it should be created with --mac-address PARENT_PORT_MAC_ADDERSS.

This is the correct networking config- on VM subIF and IF should have the same mac and it is the default option. We need to match neutron port creation with same concept- parent and subport should have same mac address.

Openstack Ocata

Tags: doc trunk
James Anziano (janzian)
tags: added: doc
Revision history for this message
Boden R (boden) wrote :

It looks like perhaps we could update neutron/doc/source/admin/config-trunking.rst with this info, but I want to confirm with someone who's more vested in this functionality first.

tags: added: trunk
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

I suppose you can make the extra recommendation in the docs, but it is not necessary for the MACs to match. In fact up until [1] was resolved you couldn't even do it with security groups involved. So, while this is a legit request, we need to be careful about the wording.

Personally, I don't feel like the documentation requires any tweaking, in the end, the way the guest is configured is up to the user and if she needs for the subinterfaces MACs to match, the model and API allows that to happen.

[1] https://bugs.launchpad.net/neutron/+bug/1626010

Changed in neutron:
importance: Undecided → Wishlist
summary: - [DOC] Sub-port MAC address needs to be the same as Parent port MAC
+ [DOC] Document subport/parent MAC address relationship
Changed in neutron:
status: New → Confirmed
Revision history for this message
Boden R (boden) wrote :

Based on Armando's comment #2 moving this to invalid.
Given comment#2, if folks still feel doc tweaking is necessary, please reopen.

Changed in neutron:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.