[Sorry, but I do not know if the thundering silence is because these questions are too hard, too easy, grossly off-topic, or simply because nobody cares.]
I have been looking at http://docs.openstack.org/developer/devstack/guides/neutron.htmland wonder about a few things. In the section http://docs.openstack.org/developer/devstack/guides/neutron.html#using-neutron-with-a-single-interface there is a helpful display of localrc contents. It says, among other things, OVS_PHYSICAL_BRIDGE=br-ex PUBLIC_BRIDGE=br-ex In the next top-level section, http://docs.openstack.org/developer/devstack/guides/neutron.html#using-neutron-with-multiple-interfaces , there is no display of revised localrc contents and no mention of changing either bridge setting. That is an oversight, right? I am guessing I need to set OVS_PHYSICAL_BRIDGEand PUBLIC_BRIDGEto different values, and the exhibited `ovs-vsctl` commands in this section apply to $OVS_PHYSICAL_BRIDGE. Is that right? Are there other revisions I need to make to localrc? Looking at http://docs.openstack.org/networking-guide/scenario_legacy_ovs.html(or, in former days, the doc now preserved at http://docs.ocselected.org/openstack-manuals/kilo/networking-guide/content/under_the_hood_openvswitch.html ) I see the name br-ex used for $PUBLIC_BRIDGE--- not $OVS_PHYSICAL_BRIDGE , right? Wouldn't it be less confusing if http://docs.openstack.org/developer/devstack/guides/neutron.htmlused a name other than "br-ex" for the exhibited commands that apply to $OVS_PHYSICAL_BRIDGE? The section http://docs.openstack.org/developer/devstack/guides/neutron.html#neutron-networking-with-open-vswitch builds on http://docs.openstack.org/developer/devstack/guides/neutron.html#using-neutron-with-multiple-interfaces NOT http://docs.openstack.org/developer/devstack/guides/neutron.html#using-neutron-with-a-single-interface --- right? Could I stop after reading that section, or must I go on to http://docs.openstack.org/developer/devstack/guides/neutron.html#neutron-networking-with-open-vswitch-and-provider-networks ? The exhibited localrc contents in section http://docs.openstack.org/developer/devstack/guides/neutron.html#using-neutron-with-a-single-interface include both of these: Q_L3_ENABLED=True Q_USE_PROVIDERNET_FOR_PUBLIC=True and nothing gainsays either of them until section http://docs.openstack.org/developer/devstack/guides/neutron.html#neutron-networking-with-open-vswitch-and-provider-networks --- where we first see Q_L3_ENABLED=False Is it true that all the other sections want both Q_L3_ENABLEDand Q_USE_PROVIDERNET_FOR_PUBLICto be True? I tried adding IPv6 support to the recipe of the first section ( http://docs.openstack.org/developer/devstack/guides/neutron.html#using-neutron-with-a-single-interface ). I added this to my localrc: IP_VERSION=4+6 IPV6_PUBLIC_RANGE=fddf:2::/64 IPV6_PUBLIC_NETWORK_GATEWAY=fddf:2::1 IPV6_ROUTER_GW_IP=fddf:2::231 At first I had tried setting a different set of IPv6 variables (having only IP_VERSION in common with what I exhibit here), but found those: (a) duplicated the defaults and (b) caused problems due to lack of the ones I mention here. Even the ones mentioned here led to a problem. There is a bit of scripging that replaces my setting for IPV6_ROUTER_GW_IP with something dug out of Neutron. That went wrong. It replaced my setting with fddf:2::2, but that address was already in use by something else. Thanks, Mike Thanks, Mike
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev