Bug 1270896

Summary:	No possibility to specify network_type as nexus_vxlan
Product:	Red Hat OpenStack	Reporter:	Evgeny <ebagdasa>
Component:	python-rdomanager-oscplugin	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED NOTABUG	QA Contact:	yeylon <yeylon>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	7.0 (Kilo)	CC:	amuller, brad, brbowen, calfonso, chrisw, ebagdasa, jcoufal, jslagle, mburns, nyechiel, ohochman, rhel-osp-director-maint, srevivo, tiswanso, yeylon, ymorkovn
Target Milestone:	y2	Keywords:	OtherQA, Triaged
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-06 14:44:47 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:
Bug Blocks:	1191185

Description Evgeny 2015-10-12 15:47:52 UTC

Description of problem:
There are only flat,vlan,gre and vxlan types availble. Specifying nexus_vxlan in --neutron-network-type when deploying overcloud fails to deploy.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Timothy Swanson 2015-10-12 16:56:35 UTC

Moving component to rhel-osp-director--This param is blocked at the "openstack overcloud deploy" script level.

The need for the Cisco Nexus ML2 mechanism driver's ability to utilize N9K VXLAN endpoint support for openstack neutron VLAN network segments.

Reference: 
http://docwiki.cisco.com/wiki/OpenStack/ML2NexusMechanismDriver#VXLAN_Overlay_Configuration_in_DevStack

Comment 3 Brad P. Crochet 2015-10-20 17:18:17 UTC

There is nothing in the client that is preventing this.

What error do you see? Have you tried '--neutron-tunnel-types nexus_vxlan --neutron-network-type nexus_vxlan'?

Comment 4 Brad P. Crochet 2015-10-20 18:40:44 UTC

You will also need to create an environment file that specifies:

parameter_defaults:
    NeutronTypeDrivers: vxlan,vlan,flat,gre,nexus_vxlan


and then pass that file with a -e

Comment 5 Timothy Swanson 2015-10-20 20:49:22 UTC

Thanks, Brad... I added my comment based on a meeting discussion with Eugene (the original bug creator).  I think the specifics were misunderstood by me there so I'll get with him and get clarification and help him retest it.

My understanding the things we need to set:
   NeutronTypeDrivers: 'nexus_vxlan,vxlan'
   --neutron-network-type nexus_vxlan OR NeutronNetworkType: 'nexus_vxlan'
   --neutron-disable-tunneling
   --neutron-tunnel-type nexus_vxlan


I just ran redeploy like this and heiradata seems ok but some failures on neutron restart: 

  in openstack overcloud deploy
    --neutron-network-type nexus_vxlan
    --neutron-disable-tunneling
 
  parameter_defaults:
    NeutronMechanismDrivers: 'openvswitch,cisco_nexus,cisco_ucsm'

  parameters:
    NeutronTypeDrivers:  'nexus_vxlan,vlan'

So, I think this BZ is either not valid or would apply to something in heat or puppet.

Comment 6 Evgeny 2015-11-06 14:44:14 UTC

it's not valid. I agree now