Network configuration - Linux bridging, OVS, Multi-nic not well documented

Hi Walter,

Any progress on this one?

Hello,

I strongly agree with the bug reported here: networking configuration is really hard to understand and - consequently - configure.

On the other hand, in my humble opinion, in order to address this point, it would be very beneficial to report very specific points like "this sentence is not clear", "this sentence is in contradiction with that", "this term is not defined", etc...
In this way, bug fixing could be simplified somehow.

Anyway, as I said, I find this section very difficult to understand. Very likely the topic is intrinsically complex but the document doesn't help much.
Only my opinion.

I am getting some additional feedback on this and hope to have a plan of action on how best to address this issue.

Multiple nics was addressed with this addition:
http://docs.openstack.org/trunk/openstack-compute/admin/content/using-multi-nics.html

So this bug is 2/3rds done.

I'd like to see "Using OVS" as another added section and "Using Linux Bridging" as another section with diagrams and the corresponding nova-manage or nova commands added for how to connect these networks - think "concept: What is OVS, how is it used in OpenStack Compute, diagrams that show routing" "task:How do I configure Compute to use OVS, How do I ensure VMs are using OVS" and "reference: what are the config options that enable this? what are the corresponding nova or nova-manage commands?"

Yes, this is a very complex topic, only getting more complex with Quantum integration. I'd like to tackle it with:
concept
task
reference

If you can think of what users need you can write new sections addressing OVS and Linux Bridging.

Er, 1/3rds done. :)

Hi Walter, you can certainly ask on the mailing list to get more information.

You can create a new XML file then do an xi:include in the networking.xml file to get it to display/publish.

One additional thought after searching through old mailing list posts at http://openstack.markmail.org, much of the OVS and bridge networking is explained in the openstack-network-connectivity-admin book.

https://github.com/openstack/openstack-manuals/tree/master/doc/src/docbkx/openstack-network-connectivity-admin

So the work on this bug is figuring out what is already written in the above guide and how to integrate it into the Compute admin guide.

Hi,

There is some great content at :
http://openvswitch.org/openstack/2011/07/25/openstack-quantum-and-open-vswitch-part-1/
http://openvswitch.org/openstack/2011/08/01/openstack-quantum-and-open-vswitch-part-ii/

Think you can work with that Walter?

In yesterday's doc meeting Walter indicated he could more easily work on storage doc bugs rather that networking ones, so freeing up for others to take.

Tom, how can we reach out to the authors of the openvswitch.org content to ask permission to bring it in? I didn't see a way to comment on the site, maybe I'm just missing it.

Indeed :s

According to WHOIS data, the site is run by Martin Casado. His email is his surname @nicira.com

Failing that:

#openvswitch on irc.freenode.net.

http://mail.openvswitch.org/mailman/listinfo/discuss

I will be updating the Quantum Admin Guide content on configuring the openvswitch and linuxbridge plugins under https://bugs.launchpad.net/openstack-manuals/+bug/1058272. That fix will be limited in scope to completing and correcting the details on the configuration variables, so this bug may still be needed.

I think we can close this bug. We have:

multi-nic:
http://docs.openstack.org/trunk/openstack-compute/admin/content/using-multi-nics.html
Linux bridging:
http://docs.openstack.org/folsom/openstack-network/admin/content/quantum_server.html
OVS:
http://docs.openstack.org/folsom/openstack-network/admin/content/quantum_server.html

I'll close if if there are no objections to this being covered. We can always keep improving with more specific suggestions.