Re: [openstack-dev] [devstack] A few questions on configuring DevStack for Neutron
On Thu, Oct 8, 2015 at 5:41 PM, Monty Taylor wrote: > On 10/08/2015 07:13 PM, Christopher Aedo wrote: >> >> On Thu, Oct 8, 2015 at 9:38 AM, Sean M. Collins >> wrote: >>> >>> Please see my response here: >>> >>> >>> http://lists.openstack.org/pipermail/openstack-dev/2015-October/076251.html >>> >>> In the future, do not create multiple threads since responses will get >>> lost >> >> >> Yep, thank you Sean - saw your response yesterday and was going to >> follow-up this thread with a "please ignore" and a link to the other >> thread. I opted not to in hopes of reducing the noise but I think >> your note here is correct and will close the loop for anyone who >> happens across only this thread. >> >> (Secretly though I hope this thread somehow becomes never-ending like >> the "don't -1 for a long commit message" thread!) > > > (I think punctuation should go outside the parenthetical)? Apologies for the late reply to this Monty but a response is required considering the importance of proper punctuation as regards parenthesis. According to the Internet[1] (which is widely regarded as the authority in such matters), the original usage of punctuation in this case is the appropriate usage when the entire sentence is inside the parenthesis. Hopefully this diversion from the topic does not warrant a new thread. [1]: http://www.grammarbook.com/punctuation/parens.asp -Christopher __ 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
Re: [openstack-dev] [devstack] A few questions on configuring DevStack for Neutron
Matt Riedemann wrote on 10/08/2015 09:48:33 PM: > On 10/8/2015 11:38 AM, Sean M. Collins wrote: > > Please see my response here: > > > > http://lists.openstack.org/pipermail/openstack-dev/2015-October/076251.html > > > > In the future, do not create multiple threads since responses will get > > lost > > > > Maybe a dumb question, but couldn't people copy the localrc from the > gate-tempest-dsvm-neutron-full job, i.e.: > > http://logs.openstack.org/20/231720/1/check/gate-tempest-dsvm- > neutron-full/f418dc8/logs/localrc.txt.gz Matt, thanks for the reminder. I was pointed at one of those once before, but do not remember how to find them in general. To be useful in http://docs.openstack.org/developer/devstack/guides/neutron.html we need to identify which section they illuminate, or add another section with appropriate explanation. Which would it be? Sean, you said that those URLs are tribal knowledge. Would you recommend documenting them and, if so, where? I see that the one Matt cited is part of a comprehensive archive from a tempest run, and there is even some explanatory material included within that run's archive. Would it be possible and appropriate for the DevStack Neutron guide to point to some documentation that describes these archives? 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
Re: [openstack-dev] [devstack] A few questions on configuring DevStack for Neutron
I believe that pulling a localrc off a CI result is tribal knowledge. It can be done, but most likely it's a trick that is only known by someone who has been involved in OpenStack for a long time. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.__ 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
Re: [openstack-dev] [devstack] A few questions on configuring DevStack for Neutron
On 10/8/2015 11:38 AM, Sean M. Collins wrote: Please see my response here: http://lists.openstack.org/pipermail/openstack-dev/2015-October/076251.html In the future, do not create multiple threads since responses will get lost Maybe a dumb question, but couldn't people copy the localrc from the gate-tempest-dsvm-neutron-full job, i.e.: http://logs.openstack.org/20/231720/1/check/gate-tempest-dsvm-neutron-full/f418dc8/logs/localrc.txt.gz -- Thanks, Matt Riedemann __ 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
Re: [openstack-dev] [devstack] A few questions on configuring DevStack for Neutron
On 10/08/2015 07:13 PM, Christopher Aedo wrote: On Thu, Oct 8, 2015 at 9:38 AM, Sean M. Collins wrote: Please see my response here: http://lists.openstack.org/pipermail/openstack-dev/2015-October/076251.html In the future, do not create multiple threads since responses will get lost Yep, thank you Sean - saw your response yesterday and was going to follow-up this thread with a "please ignore" and a link to the other thread. I opted not to in hopes of reducing the noise but I think your note here is correct and will close the loop for anyone who happens across only this thread. (Secretly though I hope this thread somehow becomes never-ending like the "don't -1 for a long commit message" thread!) (I think punctuation should go outside the parenthetical)? __ 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
Re: [openstack-dev] [devstack] A few questions on configuring DevStack for Neutron
On Thu, Oct 8, 2015 at 9:38 AM, Sean M. Collins wrote: > Please see my response here: > > http://lists.openstack.org/pipermail/openstack-dev/2015-October/076251.html > > In the future, do not create multiple threads since responses will get > lost Yep, thank you Sean - saw your response yesterday and was going to follow-up this thread with a "please ignore" and a link to the other thread. I opted not to in hopes of reducing the noise but I think your note here is correct and will close the loop for anyone who happens across only this thread. (Secretly though I hope this thread somehow becomes never-ending like the "don't -1 for a long commit message" thread!) -Christopher __ 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
Re: [openstack-dev] [devstack] A few questions on configuring DevStack for Neutron
Please see my response here: http://lists.openstack.org/pipermail/openstack-dev/2015-October/076251.html In the future, do not create multiple threads since responses will get lost -- Sean M. Collins __ 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
Re: [openstack-dev] [devstack] A few questions on configuring DevStack for Neutron
On Sun, Oct 4, 2015 at 9:16 PM, Mike Spreitzer wrote: > [Apologies for re-posting, but I botched the subject line the first time and > know that people use filters.] > > 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-interfacethere > 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-vswitchbuilds > on > http://docs.openstack.org/developer/devstack/guides/neutron.html#using-neutron-with-multiple-interfacesNOT > 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-interfaceinclude > 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_ENABLED and > Q_USE_PROVIDERNET_FOR_PUBLICto be True? I'd love to see a response from someone who can make sense of this too. With my evangelist hat on, I usually tell people who want to get started with OpenStack development to start with Devstack. More often than not, they have trouble with the networking side. As discussed and hoped for in the "just get me a network" spec, there's definitely a need for a less painful path for users. Likewise we should be able to share a devstack config that just works, but at the same time shows off some of the great capabilities of neutron (and all the other good bits of OpenStack). Can anyone weigh in here on this issue? -Christopher __ 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
[openstack-dev] [devstack] A few questions on configuring DevStack for Neutron
[Apologies for re-posting, but I botched the subject line the first time and know that people use filters.] I have been looking at http://docs.openstack.org/developer/devstack/guides/neutron.html and 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.html used 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? 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