Bug 1273409

Cloning for the OPM side

+++ This bug was initially created as a clone of Bug #1264740 +++

Description of problem:

Neutron is using nova event call-back to make sure neutron port is configured before VM is running

Both packstack and RHEL OSP installer are using it.

Configuration must be done on nova.conf and neutron.conf on contr


https://bugzilla.redhat.com/show_bug.cgi?id=1067211
https://blueprints.launchpad.net/neutron/+spec/nova-event-callback
https://blueprints.launchpad.net/nova/+spec/admin-event-callback-api


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Brent Eagles on 2015-09-21 13:30:15 EDT ---

Just a heads up that, if memory serves, that the nova part (vif_plugging_is_fatal = True) needs to be set to True on the compute nodes as well. The defaults would be preferable to what there is now. It seems that it might be being set to false in openstack-tripleo-heat-templates/puppet/hierdata/common.yaml - which might explain how this regression wheedled in.

The neutron config needs to have the appropriate entries to know "how to talk" to nova. The properties can be seen starting on line 331 or the sample neutron.conf on http://docs.openstack.org/kilo/config-reference/content/section_neutron.conf.html

I imagine that this stuff was configured in the installer version so it is probably just a matter of enabling it (openstack-puppet/modules/neutron/manifests/server/notifications.pp?) as long as nothing else gets in the way.

--- Additional comment from Brent Eagles on 2015-09-21 13:31:25 EDT ---

Forgot to mention that we probably should have an U/S bug on this once the details of the real culprits are figured out.

--- Additional comment from Emilien Macchi on 2015-09-21 13:53:03 EDT ---

Patch submitted upstream in TripleO Heat Templates: https://review.openstack.org/225962

--- Additional comment from James Slagle on 2015-10-07 16:03:31 EDT ---

note that vif_plugging_timeout also needs to use the default upstream value of 300 instead of the TripleO value of 30.

this has been pointed out on the above review as well

--- Additional comment from Nir Yechiel on 2015-10-08 02:50:59 EDT ---

Setting need-info on Emilien to get the team attention.

--- Additional comment from Emilien Macchi on 2015-10-13 12:29:13 EDT ---

Currently working on the undercloud part: https://review.openstack.org/234325
And also on the overcloud side: https://review.openstack.org/225962

--- Additional comment from Emilien Macchi on 2015-10-13 17:55:19 EDT ---

Undercloud: see the comment on https://review.openstack.org/234325 but we are blocked now without work in progress for the missing feature, I'm working on it with my team.

Overcloud: see the comment on https://review.openstack.org/225962 but we are also blocked, though there is some work in progress that we would depend on.

I'm not sure we can make it for Y2 but we will do our best.

--- Additional comment from Emilien Macchi on 2015-10-19 09:52:43 EDT ---

Just a quick update, I managed to unblock the situation.

If we have https://review.openstack.org/#/c/235316/ in OPM (should land soon upstream), we can configure nova-event-callback without managing Keystone resources with Puppet, which is a safer approach for Y2.

So:

* https://review.openstack.org/#/c/235316/ is about to be in OPM

* Undercloud patch: https://review.openstack.org/234325

* Overcloud patch: https://review.openstack.org/225962