This isn't entirely correct. The --neutron-tunnel-types parameter only takes
[vxlan|gre], and should not be
required when --neutron-network-type is 'vlan'. However, a bug is making the CLI
require this parameter in error.
Nuno, there is a bug on this behavior, feel free to add your comments or more information:
On Tue, Oct 27, 2015 at 6:10 PM, Nuno Loureiro <
nuno.loureiro(a)itcenter.com.pt > wrote:
Hi all!
I'm deploying an HA overcloud with 3 controller nodes and 3 compute nodes.
I'm able to successfully deploy the overcloud in GRE-tunnel mode by issuing
the following command:
openstack overcloud deploy --control-scale 3 --compute-scale 3 --libvirt-type
kvm --ntp-server
pool.ntp.org --templates ~/the-cloud/ -e
~/the-cloud/environments/puppet-pacemaker.yaml -e
~/the-cloud/environments/network-isolation.yaml -e
~/the-cloud/environments/net-single-nic-with-vlans.yaml -e
~/the-cloud/environments/network-environment.yaml --control-flavor
controller --compute-flavor compute
Now I want to use VLAN in tenant networks, disabling the GRE-tunnels.
I ran the following command to deploy the overcloud in VLAN mode:
openstack overcloud deploy --control-scale 3 --compute-scale 3 --libvirt-type
kvm --ntp-server
pool.ntp.org --templates ~/the-cloud/ -e
~/the-cloud/environments/puppet-pacemaker.yaml -e
~/the-cloud/environments/network-isolation.yaml -e
~/the-cloud/environments/net-single-nic-with-vlans.yaml -e
~/the-cloud/environments/network-environment.yaml --control-flavor
controller --compute-flavor compute --neutron-network-type vlan
--neutron-bridge-mappings datacentre:br-ex --neutron-network-vlan-ranges
datacentre:1000:10009
However I always get the following error:
ERROR: openstack Neutron tunnel types must be specified when Neutron network
type is specified
I think this problem might be related to this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1244893
Yes, the error relates to that bug: you should pass both
--neutron-network-type vlan and --neutron-tunnel-types vlan to pass.
In addition to this you should also make sure that the network templates
match your physical environment, provide valid vlan range( 10009 is not a
valid vlan tag), switch configuration is in place.
Do you have any suggestions on how to solve this problem?
Thank you very much!
Regards,
--
Nuno Loureiro
Research & Development
Phone: +351 256 370 980
Email: nuno.loureiro(a)itcenter.com.pt
www.itcenter.com.pt
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com