Open Stack

Thank you, Sudhakar.  I'll abandon testing ML2 for Havana and revisit it in my Icehouse testing.

Thanks,
Andrew Richards
Senior Systems Engineer
keepertechnology

On Apr 26, 2014, at 10:56 AM, Sudhakar Gariganti <sudhakar.gariganti at gmail.com> wrote:

> Hi Andrew, 
> 
> I have also encountered this error a couple of times. Per my understanding, in Havana, we need to continue to configure *ovs_neutron_plugin.ini* on the agent side. 
> Only from Icehouse, OVS agent expects/reads configuration from ml2_conf.ini. 
> 
> 
> Thanks,
> Sudhakar.
> 
> On Sat, Apr 26, 2014 at 2:53 AM, Andrew Richards <andrew.richards at keepertech.com> wrote:
> Hello all,
> 
> I'm attempting to migrate my Havana test cluster over to the ML2 plugin from the monolithic OVS plugin. I had been successfully using OVS in VLAN mode. I reset my core_plugin and service_plugins in neutron.conf, I followed the steps to reinitialize my Neutron databases, to upgrade their heads with neutron-db-manage, and transpose my configuration from /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini to /etc/neutron/plugins/ml2/ml2_conf.ini.  My neutron agent-list seems happy:
> 
> # neutron agent-list
> +--------------------------------------+--------------------+------------------------+-------+----------------+
> | id                                   | agent_type         | host                   | alive | admin_state_up |
> +--------------------------------------+--------------------+------------------------+-------+----------------+
> | 45de0ed9-a776-4a91-a841-8abec65652d2 | L3 agent           | host3.keepertech.com   | :-)   | True           |
> | 3242ea48-b607-40a7-86ed-4c101880fb96 | DHCP agent         | host3.keepertech.com   | :-)   | True           |
> | 64f2b250-c61f-4a27-8784-92146765f10d | Open vSwitch agent | host6.keepertech.com   | :-)   | True           |
> | f1b35d11-c501-4ae3-9462-9efd09c9400a | Open vSwitch agent | host5.keepertech.com   | :-)   | True           |
> | 2f0a50c5-3679-43f5-a3f5-3aa4fa67c768 | Open vSwitch agent | host3.keepertech.com   | :-)   | True           |
> +--------------------------------------+--------------------+------------------------+-------+----------------+
> 
> My ml2_conf.ini looks like this:
> 
> [ml2]
> type_drivers = vlan
> tenant_network_types = vlan
> mechanism_drivers = openvswitch
> [ml2_type_flat]
> 
> [ml2_type_vlan]
> network_vlan_ranges = physnet1:4:4,physnet1:101:104,physnet2:2:2
> [ml2_type_gre]
> 
> [ml2_type_vxlan]
> 
> [database]
> sql_connection = postgresql://neutron@dbhost/ovs_neutron
> [securitygroup]
> firewall_driver = neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver
> [ovs]
> bridge_mappings = physnet1:br-eth1,physnet2:br-ex
> 
> This is not reflected though when I do a neutron agent-show on that host:
> 
> +---------------------+--------------------------------------+
> | Field               | Value                                |
> +---------------------+--------------------------------------+
> | admin_state_up      | True                                 |
> | agent_type          | Open vSwitch agent                   |
> | alive               | True                                 |
> | binary              | neutron-openvswitch-agent            |
> | configurations      | {                                    |
> |                     |      "tunnel_types": [],             |
> |                     |      "tunneling_ip": "",             |
> |                     |      "bridge_mappings": {            |
> |                     |           "physnet2": "br-ex",       |
> |                     |           "physnet1": "br-eth1"      |
> |                     |      },                              |
> |                     |      "l2_population": false,         |
> |                     |      "devices": 0                    |
> |                     | }                                    |
> | created_at          | 2014-04-25 17:42:29.976072           |
> | description         |                                      |
> | heartbeat_timestamp | 2014-04-25 20:50:07.556754           |
> | host                | host3.keepertech.com                 |
> | id                  | 2f0a50c5-3679-43f5-a3f5-3aa4fa67c768 |
> | started_at          | 2014-04-25 20:50:03.828254           |
> | topic               | N/A                                  |
> +---------------------+--------------------------------------+
> 
> Shouldn't I be seeing VLAN configuration info there instead of empty tunneling info?
> 
> The net effect of all this is my VMs can't connect to their OVS switches and complain thusly in /var/log/neutron/server.log:
> 
> WARNING neutron.plugins.ml2.managers [-] Failed to bind port 4e3f10f5-b9c2-4502-99f4-d97608de2e08 on host host6
> WARNING neutron.plugins.ml2.managers [-] Failed to bind port f00aa773-7401-4d79-b31c-08291dff30ed on host host3
> WARNING neutron.plugins.ml2.managers [-] Failed to bind port 8f1ac067-8bb1-45bf-9556-5ba73334a1d4 on host host3
> WARNING neutron.plugins.ml2.managers [-] Failed to bind port e8c34586-4721-4271-aee4-2eb13f0707cc on host host6
> WARNING neutron.plugins.ml2.managers [-] Failed to bind port 2ac75e18-e4e4-4017-af45-01c375f50486 on host host5
> WARNING neutron.plugins.ml2.managers [-] Failed to bind port 9bfc3e62-8188-45f9-91c7-5ac53590ad3c on host host5
> WARNING neutron.plugins.ml2.rpc [-] Device 8f1ac067-8bb1-45bf-9556-5ba73334a1d4 requested by agent ovs0a2c22b41641 on network 18faee17-f972-45bf-a9fe-8be906a55055 not bound, vif_type: binding_failed
> WARNING neutron.plugins.ml2.rpc [-] Device f00aa773-7401-4d79-b31c-08291dff30ed requested by agent ovs0a2c22b41641 on network 18faee17-f972-45bf-a9fe-8be906a55055 not bound, vif_type: binding_failed
> WARNING neutron.plugins.ml2.rpc [-] Device 4e3f10f5-b9c2-4502-99f4-d97608de2e08 requested by agent ovsf60e61961e45 on network 18faee17-f972-45bf-a9fe-8be906a55055 not bound, vif_type: binding_failed
> WARNING neutron.plugins.ml2.rpc [-] Device e8c34586-4721-4271-aee4-2eb13f0707cc requested by agent ovsf60e61961e45 on network 18faee17-f972-45bf-a9fe-8be906a55055 not bound, vif_type: binding_failed
> WARNING neutron.plugins.ml2.rpc [-] Device 9bfc3e62-8188-45f9-91c7-5ac53590ad3c requested by agent ovs2a7b2230b64b on network 18faee17-f972-45bf-a9fe-8be906a55055 not bound, vif_type: binding_failed
> WARNING neutron.plugins.ml2.rpc [-] Device 2ac75e18-e4e4-4017-af45-01c375f50486 requested by agent ovs2a7b2230b64b on network 18faee17-f972-45bf-a9fe-8be906a55055 not bound, vif_type: binding_failed
> 
> Does ML2 even work for VLAN in Havana? The Havana ML2 documentation[1] does not list VLAN as a configuration option. I'm running all my nodes on CentOS 6.5 installing from the RDO Havana repo. 
> 
> Thanks,
> Andrew Richards
> Senior Systems Engineer
> keepertechnology
> 
> [1] http://docs.openstack.org/havana/config-reference/content/networking-options-plugins-ml2.html
> 
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> 
> 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20140426/739de3ad/attachment.html>