Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 907765

Summary:	[RFE] 'IP address' column under Instances is confusing - presents both public and private IP of the VM (and the user cannot distinguish between them)
Product:	Red Hat OpenStack	Reporter:	Yaniv Kaul <ykaul>
Component:	python-django-horizon	Assignee:	Julie Pichon <jpichon>
Status:	CLOSED WONTFIX	QA Contact:	Nir Magnezi <nmagnezi>
Severity:	low	Docs Contact:
Priority:	low
Version:	2.1	CC:	aortega, athomas, jkt, jpichon, mrunge
Target Milestone:	---	Keywords:	FutureFeature, Improvement, Triaged
Target Release:	4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-08-19 08:51:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Yaniv Kaul 2013-02-05 08:34:24 UTC

Description of problem:
Seen on 'dropbear' (the internal OpenStack deployment).
My VM got an IP of 192.168.x.y (which was it's internal IP) and a public IP of 10.a.b.d - which is the IP you use to SSH to. However, a user who is not familiar with the network topology would not have known which IP to use when connecting via SSH.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 Julie Pichon 2013-02-14 18:04:45 UTC

Apparently, it is possible to get that information by doing "nova floating-ip-list". The "Fixed IP" column in that output indicates the "internal" IP. However at the moment it's not possible to get it from the instance information (Server() object) returned by the nova client (not sure if the information is available from nova at the instance level, or if they both need to be updated).

As far as I can tell though, this only applies to nova-network. When using quantum, the floating-ip-list returns empty. The user creates a network and associates it with the instance at launch time, and it's the only IP that is displayed on the list (unless they manually create and select multiple networks). Someone more experienced with Quantum might want to confirm this is the way it works.

Comment 3 Julie Pichon 2013-02-19 17:55:57 UTC

A new nova extension was added in grizzly to figure out the type of an IP: https://review.openstack.org/#/c/21453/

Comment 5 Julie Pichon 2013-08-06 07:45:47 UTC

Note that this is close to the default behaviour when using Quantum/Neutron (see comments 3 and 4 on bug 888995), which indicates the network name besides the IP. At the moment, there is no plans upstream to add the same functionality when using nova-network.

Comment 6 Julie Pichon 2013-08-19 08:51:19 UTC

If networks are named meaningfully, this is not an issue when using Neutron. Nova networking is on its way to deprecation ([0]) so it probably doesn't make much sense to spend time on integrating it better, when it's about to be removed.

[0] https://blueprints.launchpad.net/nova/+spec/deprecate-nova-network