[Rdo-list] HA Overcloud deployment with network isolation in VLAN mode

Marius Cornea marius at remote-lab.net
Wed Oct 28 15:08:53 UTC 2015 

I believe this is exactly what Dan was referring to (valid tunnel types are
only gre or vxlan). Could you try setting tunnel_types in
/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini to gre or vxlan and
run pcs resource restart neutron-openvswitch-agent? This should get the ovs
agent started but please note that on a subsequent run of the deploy
command the tunnel_types will get overwritten.

On Wed, Oct 28, 2015 at 12:45 PM, Nuno Loureiro <
nuno.loureiro at itcenter.com.pt> wrote:

> Hi all!
>
> Thank you for your replies.
>
> The VLAN range I posted on my email was a typo. The command I used had the
> correct range 1000:1009. The network templates were configured according to
> my physical network.
>
>
> I followed Marius suggestion and used the following command to deploy the
> overcloud stack:
>
> 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:1009 --neutron-tunnel-types vlan
>
>
> The overcloud stack was deployed in VLAN mode without the GRE-tunnels.
>
> However, it doesn't work correctly because the neutron-openvswitch-agent
> is unable to start as it doesn't recognize "vlan" as a tunnel mode.
>
> I captured the followinfg error in /var/log/neutron/openvswitch-agent.log
>
> 2015-10-28 11:35:53.057 160431 WARNING oslo_config.cfg [-] Option
> "lock_path" from group "DEFAULT" is deprecated. Use option "lock_path" from
> group "oslo_concurrency".
> 2015-10-28 11:35:53.058 160431 ERROR
> neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [-] Agent
> failed to create agent config map
> 2015-10-28 11:35:53.058 160431 ERROR
> neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent Traceback
> (most recent call last):
> 2015-10-28 11:35:53.058 160431 ERROR
> neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent   File
> "/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py",
> line 1894, in main
> 2015-10-28 11:35:53.058 160431 ERROR
> neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent
> agent_config = create_agent_config_map(cfg.CONF)
> 2015-10-28 11:35:53.058 160431 ERROR
> neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent   File
> "/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py",
> line 1863, in create_agent_config_map
> 2015-10-28 11:35:53.058 160431 ERROR
> neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent     raise
> ValueError(msg)
> 2015-10-28 11:35:53.058 160431 ERROR
> neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent ValueError:
> (u'Invalid tunnel type specified: %s', 'vlan')
> 2015-10-28 11:35:53.058 160431 ERROR
> neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent
> 2015-10-28 11:36:19.023 161519 WARNING oslo_config.cfg [-] Option
> "lock_path" from group "DEFAULT" is deprecated. Use option "lock_path" from
> group "oslo_concurrency".
> 2015-10-28 11:36:19.024 161519 ERROR
> neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [-] Agent
> failed to create agent config map
> 2015-10-28 11:36:19.024 161519 ERROR
> neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent Traceback
> (most recent call last):
> 2015-10-28 11:36:19.024 161519 ERROR
> neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent   File
> "/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py",
> line 1894, in main
> 2015-10-28 11:36:19.024 161519 ERROR
> neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent
> agent_config = create_agent_config_map(cfg.CONF)
> 2015-10-28 11:36:19.024 161519 ERROR
> neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent   File
> "/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py",
> line 1863, in create_agent_config_map
> 2015-10-28 11:36:19.024 161519 ERROR
> neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent     raise
> ValueError(msg)
> 2015-10-28 11:36:19.024 161519 ERROR
> neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent ValueError:
> (u'Invalid tunnel type specified: %s', 'vlan')
> 2015-10-28 11:36:19.024 161519 ERROR
> neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent
>
>
> So the --neutron-tunnel-types vlan command allows the deployment to pass
> the CLI bug but creates a problem in neutron configuration.
>
> Do you have any other suggestions?
>
> Thank you very much!
> Regards,
>
>
> On Wed, Oct 28, 2015 at 3:03 AM, Dan Sneddon <dsneddon at redhat.com> wrote:
>
>> 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:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1244893
>>
>> -Dan Sneddon
>>
>> ----- Original Message -----
>> >
>> > On Tue, Oct 27, 2015 at 6:10 PM, Nuno Loureiro <
>> > nuno.loureiro at 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 at itcenter.com.pt
>> >
>> >                       www.itcenter.com.pt
>> >
>> >
>> >
>> > _______________________________________________
>> > Rdo-list mailing list
>> > Rdo-list at redhat.com
>> > https://www.redhat.com/mailman/listinfo/rdo-list
>> >
>> > To unsubscribe: rdo-list-unsubscribe at redhat.com
>> >
>> >
>> > _______________________________________________
>> > Rdo-list mailing list
>> > Rdo-list at redhat.com
>> > https://www.redhat.com/mailman/listinfo/rdo-list
>> >
>> > To unsubscribe: rdo-list-unsubscribe at redhat.com
>>
>
>
>
> --
> Nuno Loureiro
> Research & Development
> Phone: +351 256 370 980
> Email: nuno.loureiro at itcenter.com.pt <http://www.itcenter.com.pt/>
> <http://www.itcenter.com.pt/> <http://www.itcenter.com.pt/> www.itcenter.com.pt
> [image: ITCENTER Store] <http://store.itcenter.com.pt/> [image: ITCENTER
> Helpdesk]
> <http://www.itcenter.com.pt/email/assinatura-email-itcenter.html#>
> [image: ITCENTER Facebook] <https://www.facebook.com/itcenterpt> [image:
> ITCENTER Linkedin] <https://www.linkedin.com/company/itcenter> [image:
> ITCENTER Twitter] <https://twitter.com/ITCenter_PT>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rdoproject.org/pipermail/dev/attachments/20151028/aeff3f7a/attachment.html>

More information about the dev mailing list