Bug 1067211
Summary: | [RFE][neutron]: nova-event-callback | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | RHOS Integration <rhos-integ> |
Component: | openstack-neutron | Assignee: | Mike Kolesnik <mkolesni> |
Status: | CLOSED ERRATA | QA Contact: | yfried |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | unspecified | CC: | chrisw, lpeer, markmc, mkolesni, mlopes, nyechiel, oblaut, yeylon |
Target Milestone: | rc | Keywords: | FutureFeature, Triaged |
Target Release: | 5.0 (RHEL 7) | Flags: | mkolesni:
needinfo-
|
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | https://blueprints.launchpad.net/neutron/+spec/nova-event-callback | ||
Whiteboard: | upstream_milestone_icehouse-rc1 upstream_definition_approved upstream_status_implemented | ||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: |
This enhancement adds callbacks that notify Compute when a VIF has been plugged in and is ready on the host. In addition, Compute is notified when a floating IP address has been assigned or removed from the VIF.
This was added to prevent occurrences where instances started before the VIF was ready, which resulted in no IP address allocation received from the DHCP server.
Compute receives the notifications from Networking by default. Compute will not boot the instance if the notification has not been received; this will also apply if the VIF was plugged, but the notification was not received.
Networking now contains configuration values to notify Compute using the API that a VIF was plugged in, and that a floating IP address was assigned, updated, or removed.
The default configuration is to notify Compute, however the settings for the Compute API are not set by default; operators need to ensure that the Compute parameters are correctly configured.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2014-07-08 15:35:11 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1090605, 1094444, 1094506 | ||
Bug Blocks: | 1003878 |
Description
RHOS Integration
2014-02-19 23:24:04 UTC
Nova configuration docs: http://docs.openstack.org/trunk/config-reference/content/list-of-compute-config-options.html Keys are called vif_plugging_* Neutron configuration docs: http://docs.openstack.org/trunk/config-reference/content/section_neutron.conf.html Keys are under neutron nova interactions section verified Ichehouse on rhel7 https://tcms.engineering.redhat.com/run/141090/report/ [root@puma45 ~(keystone_admin)]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.0 (Maipo) [root@puma45 ~(keystone_admin)]# rpm -qa | grep "neutron \|nova" openstack-nova-scheduler-2014.1-2.el7ost.noarch openstack-nova-conductor-2014.1-2.el7ost.noarch python-novaclient-2.17.0-1.el7ost.noarch openstack-nova-common-2014.1-2.el7ost.noarch openstack-nova-compute-2014.1-2.el7ost.noarch python-nova-2014.1-2.el7ost.noarch openstack-nova-novncproxy-2014.1-2.el7ost.noarch openstack-nova-console-2014.1-2.el7ost.noarch openstack-nova-cert-2014.1-2.el7ost.noarch openstack-nova-api-2014.1-2.el7ost.noarch Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-0848.html |