Open Stack

Yamamoto has reviewed the changes for this, and has raised the following issue (among others).


  *   iirc mellanox uses mac address as port identifier. what happens on address change?

Can someone who knows mellanox please comment, either here or in the review?

Thanks,
Chuck


On Aug 5, 2014, at 1:22 PM, "Carlino, Chuck (OpenStack TripleO, Neutron)" <chuck.carlino at hp.com<mailto:chuck.carlino at hp.com>> wrote:

Thanks for the quick responses.

Here's the WIP review:

https://review.openstack.org/112129.

The base plugin doesn't contribute to the notification decision right now, so I've modified the actual plugin code.

Chuck


On Aug 5, 2014, at 12:51 PM, Amir Sadoughi <amir.sadoughi at RACKSPACE.COM<mailto:amir.sadoughi at RACKSPACE.COM><mailto:amir.sadoughi at RACKSPACE.COM>>
wrote:

I agree with Kevin here. Just a note, don't bother with openvswitch and linuxbridge plugins as they are marked for deletion this cycle, imminently (already deprecated)[0].

Amir

[0] http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-08-04-21.02.html Announcements 2e.
________________________________
From: Kevin Benton [blak111 at gmail.com<mailto:blak111 at gmail.com><mailto:blak111 at gmail.com>]
Sent: Tuesday, August 05, 2014 2:40 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] make mac address updatable: which plugins?

How are you implementing the change? It would be good to get to see some code in a review to get an idea of what needs to be updated.

If it's just a change in the DB base plugin, just let those changes propagate to the plugins that haven't overridden the inherited behavior.


On Tue, Aug 5, 2014 at 1:28 PM, Charles Carlino <chuckjcarlino at gmail.com<mailto:chuckjcarlino at gmail.com><mailto:chuckjcarlino at gmail.com>> wrote:
Hi all,

I need some help regarding a bug [1] I'm working on.

The bug is basically a request to make the mac address of a port updatable.  The use case is a baremetal (Ironic) node that has a bad NIC which must be replaced, resulting in a new mac address.  The bad NIC has an associated neutron port which of course holds the NIC's IP address.  The reason to make mac_address updatable (as opposed to having the user create a new port and delete the old one) is that during the recovery process the IP address must be retained and assigned to the new NIC/port, which is not guaranteed in the above work-around.

I'm coding the changes to do this in the ml2, openvswitch, and linuxbridge plugins but I'm not sure how to handle the the other plugins since I don't know if the associated backends are prepared to handle such updates.  My first thought is to disallow the update in the other plugins, but I would really appreciate your advice.

Kind regards,
Chuck Carlino

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

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org><mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




--
Kevin Benton
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev