Sanjeev N created CLOUDSTACK-6430:
-------------------------------------
Summary: [SDN] CS asks for vlan range even we create physical
network with GRE isolation and uses those ranges as GRE keys in creating tunnels
Key: CLOUDSTACK-6430
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6430
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Network Controller
Affects Versions: 4.4.0
Environment: Latest build from 4.4 with commit
80d82106dcc701e9569dde16161b24ff3abfa67f
Reporter: Sanjeev N
Priority: Critical
Fix For: 4.4.0
[SDN] CS asks for vlan range even-though we create physical network with GRE
isolation and uses those ranges as GRE keys in creating tunnels
Steps to reproduce:
================
1.Install CS with latest build from 4.4
2.During zone creation choose GRE as the isolation method and proceed further
3.Zone creation wizard asks to specify vlan range so give some range there
4.Proceed to complete zone creation
5.Create an isolated network with stretched-l2 service.
6.Deploy guest vms in the network and make sure that vms in that network are
spanned across the hosts in the cluster
Observations:
===========
When the vms are created on more than one host in the cluster CS programs GRE
ports on the ovsswitch on all the hypervisors on which the vms are running and
it uses the one of the vlan from the vlan range given during zone creation.
Expected Result:
==============
1.When physical network is created based on GRE isolation CS should not ask for
the vlan range
2.GRE key should be picked up randomly so that user does not have to provide
any range even for the GRE keys.
In my setup I had provided vlan range as 981-1000 and the following are the GRE
tunnels info from the hypervisor:
Bridge "xapi3"
fail_mode: standalone
Port "t983-1-5"
Interface "t983-1-5"
type: gre
options: {key="983", remote_ip="10.147.40.31"}
Port "vif5.0"
Interface "vif5.0"
Port "t983-1-4"
Interface "t983-1-4"
type: gre
options: {key="983", remote_ip="10.147.40.14"}
Port "xapi3"
Interface "xapi3"
type: internal
ovs_version: "1.4.6"
--
This message was sent by Atlassian JIRA
(v6.2#6252)
