Bug 1223054

Summary:	Overcloud: There is no way to know how to map Interface where external network is attached to controller.
Product:	Red Hat OpenStack	Reporter:	Leonid Natapov <lnatapov>
Component:	rhosp-director	Assignee:	Dan Sneddon <dsneddon>
Status:	CLOSED NOTABUG	QA Contact:	Leonid Natapov <lnatapov>
Severity:	high	Docs Contact:
Priority:	medium
Version:	Director	CC:	hbrock, jason.dobies, jcoufal, kbasil, mburns, mcornea, oblaut, rhel-osp-director-maint, tvignaud, ykawada
Target Milestone:	---	Keywords:	UserExperience
Target Release:	10.0 (Newton)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-10-10 16:56:22 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:
Bug Depends On:	1266597
Bug Blocks:	1241148

Description Leonid Natapov 2015-05-19 17:19:42 UTC

openstack-tripleo-0.0.6-dev1717.el7.centos.noarch
openstack-tripleo-heat-templates-0.8.6-dev5.el7.centos.noarch
openstack-tripleo-puppet-elements-0.0.1-dev63.el7.centos.noarch
tripleo-common-0.0.0-post4.el7.centos.noarch
openstack-tripleo-image-elements-0.9.5-post1.el7.centos.noarch

Overcloud: There is no way to know how to map Interface where external network is attached to controller.

Before running overcloud deployment on bare metal user have to edit deployment-overcloudrc file to reflect his/her actual environment.

The file has the following line:

# Interface where external network is attached to controller(s).
export NeutronPublicInterface=nic1

But there is no explanation what is nic1 refers to.

When deployment runs I can see from the log file the following:

May 19 10:23:12 localhost os-collect-config: [2015/05/19 10:23:12 AM] [INFO] nic1 mapped to: em1
May 19 10:23:12 localhost os-collect-config: [2015/05/19 10:23:12 AM] [INFO] nic2 mapped to: p1p1
May 19 10:23:12 localhost os-collect-config: [2015/05/19 10:23:12 AM] [INFO] nic3 mapped to: p1p2

But there is no way to know before the installation that nic1 mapped to em1,nic2 to p1p1,nic3 p1p2.


If user wants neutron public network to be on p1p1 how he suppose to know that p1p1 is mapped to nic2 in order to specify nic2 in the deploy-overcloudrc?

Comment 4 chris alfonso 2015-05-20 17:50:30 UTC

This could use comments in the file as well as more documentation.

Comment 5 Ofer Blaut 2015-07-07 09:15:52 UTC


In order to configure network isolation i need information on each role, what are the interfaces i have on each hosts and their properties

Otherwise   i can't tell how to configure yaml files in ~/nic-configs

Comment 6 James Slagle 2015-07-07 18:10:01 UTC

(In reply to Ofer Blaut from comment #5)
> 
> In order to configure network isolation i need information on each role,
> what are the interfaces i have on each hosts and their properties
> 
> Otherwise   i can't tell how to configure yaml files in ~/nic-configs

Ofer, I don't think this needs to be tracked as a blocker, so we've removed the flag. The original question proposed by the bug was how to understand the mapping of nic1, nic2, nic3, etc to the actual interfaces on the box.

If I recall, that was answered on the mailing list as well and the mapping is based on the bios ordering of active nics.

It seems like you're asking for much more information (role, all known interfaces, and properties). You may like to consider filing this as a new bug or an RFE with some more details on what you're looking for and what problems it would solve.

Comment 9 Dan Sneddon 2016-10-10 16:57:00 UTC

Addressed by:
https://blueprints.launchpad.net/tripleo/+spec/tripleo-lldp-validation