Open Stack

From: "Steven Dake (stdake)" <stdake at cisco.com<mailto:stdake at cisco.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Tuesday, April 28, 2015 at 7:52 AM
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: Re: [openstack-dev] [kolla] implement openvswitch container



From: FangFenghua <fang_fenghua at hotmail.com<mailto:fang_fenghua at hotmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Tuesday, April 28, 2015 at 7:02 AM
To: "openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: [openstack-dev] [kolla] implement openvswitch container

I want to enbale openvswitch container.  I tink i can do that like:

1 add a container that run ovs process

OVS is broken down into several daemons, so I suggest using supervisord to have these daemons run in a single container before breaking them apart. This is because these daemons communicate through sockets by default. The daemons can be configured to use tcp, but I don’t know the details for changing that config off hand.

2 add a container that run neutron-openvswitch-agent
3  share the db.sock in compose.yaml
I think this is where you want to use tcp instead of sockets
4 add configure script and check script for the 2 containers

As a first step, you may want to simply replicate the current neutron-agents container and swap linux bridge for ovs and get ovs/l3/meta/etc working in a single container first, then split the agents apart into individual containers.

that's all i need to do, right?

That should do it

You may need to configure the ovs process in the start.sh script and neutron-openvswitch-agent, which will be the most difficult part of the work.

Note our agents atm are a “fat container” but if you can get ovs in a separate container, that would be ideal. We are planning to redux the fat container we have to single-purpose containers.

Regards
-steve
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150428/6d9d43ab/attachment.html>