Bug 978543 - [RFE] Nova support to pass instance hostname to Quantum
Summary: [RFE] Nova support to pass instance hostname to Quantum
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 4.0
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: Upstream M2
: 4.0
Assignee: Brent Eagles
QA Contact: David Ripton
URL: https://blueprints.launchpad.net/nova...
Whiteboard:
Depends On:
Blocks: RHOS40RFE
TreeView+ depends on / blocked
 
Reported: 2013-06-26 18:32 UTC by Russell Bryant
Modified: 2019-09-09 13:53 UTC (History)
9 users (show)

Fixed In Version: openstack-nova-2013.2-0.8.b2.el6ost
Doc Type: Enhancement
Doc Text:
A feature has been added to propagate the hostname information to OpenStack Networking when allocating the network. Previously, where required, OpenStack Networking would generate hostnames that were a "hash" of available information. Using a different hostname than the information provided prevented the potential of using that information to provide typical network services (e.g. DNS) Now, hostname information for an instance is used whenever relevant in OpenStack Networking
Clone Of:
Environment:
Last Closed: 2013-12-20 00:11:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2013:1859 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement Advisory 2013-12-21 00:01:48 UTC

Description Russell Bryant 2013-06-26 18:32:28 UTC 
https://blueprints.launchpad.net/nova/+spec/vm-host-quantum
Comment 7 errata-xmlrpc 2013-12-20 00:11:42 UTC 
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-2013-1859.html
Note You need to log in before you can comment on or make changes to this bug.