Re: [openstack-dev] [all] [devstack] Adding example "local.conf" files for testing?
This is so great. Then you should also know that the combination you are trying in local.conf has worked and your problem is perhaps not that one. +1 Br, Tomi > -Original Message- > From: EXT Markus Zoeller [mailto:mzoel...@de.ibm.com] > Sent: Thursday, April 14, 2016 10:32 AM > To: openstack-dev > Subject: [openstack-dev] [all] [devstack] Adding example "local.conf" files > for testing? > > Sometimes (especially when I try to reproduce bugs) I have the need > to set up a local environment with devstack. Everytime I have to look > at my notes to check which option in the "local.conf" have to be set > for my needs. I'd like to add a folder in devstacks tree which hosts > multiple example local.conf files for different, often used setups. > Something like this: > > example-confs > --- newton > --- --- x86-ubuntu-1404 > --- --- --- minimum-setup > --- --- --- --- README.rst > --- --- --- --- local.conf > --- --- --- serial-console-setup > --- --- --- --- README.rst > --- --- --- --- local.conf > --- --- --- live-migration-setup > --- --- --- --- README.rst > --- --- --- --- local.conf.controller > --- --- --- --- local.conf.compute1 > --- --- --- --- local.conf.compute2 > --- --- --- minimal-neutron-setup > --- --- --- --- README.rst > --- --- --- --- local.conf > --- --- s390x-1.1.1-vulcan > --- --- --- minimum-setup > --- --- --- --- README.rst > --- --- --- --- local.conf > --- --- --- live-migration-setup > --- --- --- --- README.rst > --- --- --- --- local.conf.controller > --- --- --- --- local.conf.compute1 > --- --- --- --- local.conf.compute2 > --- mitaka > --- --- # same structure as master branch. omitted for brevity > --- liberty > --- --- # same structure as master branch. omitted for brevity > > Thoughts? > > Regards, Markus Zoeller (markus_z) > > > __ > 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 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] [all] [devstack] Adding example "local.conf" files for testing?
Excellent idea and good for any new users to get everything they need in devstack with example local.conf +1 Thanks & Regards, J. Venkata Mahesh [cid:image001.jpg@01D19CA8.C9008BB0] From: Murray, Paul (HP Cloud) [mailto:pmur...@hpe.com] Sent: Friday, April 22, 2016 3:01 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [all] [devstack] Adding example "local.conf" files for testing? Absolutely, yes +1 Paul From: ZhiQiang Fan [mailto:aji.zq...@gmail.com] Sent: 21 April 2016 12:34 To: OpenStack Development Mailing List (not for usage questions) mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [all] [devstack] Adding example "local.conf" files for testing? +1 more example and documentation are welcomed On Tue, Apr 19, 2016 at 3:10 AM, John Griffith mailto:john.griffi...@gmail.com>> wrote: On Thu, Apr 14, 2016 at 1:31 AM, Markus Zoeller mailto:mzoel...@de.ibm.com>> wrote: Sometimes (especially when I try to reproduce bugs) I have the need to set up a local environment with devstack. Everytime I have to look at my notes to check which option in the "local.conf" have to be set for my needs. I'd like to add a folder in devstacks tree which hosts multiple example local.conf files for different, often used setups. Something like this: example-confs --- newton --- --- x86-ubuntu-1404 --- --- --- minimum-setup --- --- --- --- README.rst --- --- --- --- local.conf --- --- --- serial-console-setup --- --- --- --- README.rst --- --- --- --- local.conf --- --- --- live-migration-setup --- --- --- --- README.rst --- --- --- --- local.conf.controller --- --- --- --- local.conf.compute1 --- --- --- --- local.conf.compute2 --- --- --- minimal-neutron-setup --- --- --- --- README.rst --- --- --- --- local.conf --- --- s390x-1.1.1-vulcan --- --- --- minimum-setup --- --- --- --- README.rst --- --- --- --- local.conf --- --- --- live-migration-setup --- --- --- --- README.rst --- --- --- --- local.conf.controller --- --- --- --- local.conf.compute1 --- --- --- --- local.conf.compute2 --- mitaka --- --- # same structure as master branch. omitted for brevity --- liberty --- --- # same structure as master branch. omitted for brevity Thoughts? Regards, Markus Zoeller (markus_z) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev Love the idea personally. Maybe we could start with a working Neutron multi node deployment!!! __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ 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] [all] [devstack] Adding example "local.conf" files for testing?
Absolutely, yes +1 Paul From: ZhiQiang Fan [mailto:aji.zq...@gmail.com] Sent: 21 April 2016 12:34 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [all] [devstack] Adding example "local.conf" files for testing? +1 more example and documentation are welcomed On Tue, Apr 19, 2016 at 3:10 AM, John Griffith mailto:john.griffi...@gmail.com>> wrote: On Thu, Apr 14, 2016 at 1:31 AM, Markus Zoeller mailto:mzoel...@de.ibm.com>> wrote: Sometimes (especially when I try to reproduce bugs) I have the need to set up a local environment with devstack. Everytime I have to look at my notes to check which option in the "local.conf" have to be set for my needs. I'd like to add a folder in devstacks tree which hosts multiple example local.conf files for different, often used setups. Something like this: example-confs --- newton --- --- x86-ubuntu-1404 --- --- --- minimum-setup --- --- --- --- README.rst --- --- --- --- local.conf --- --- --- serial-console-setup --- --- --- --- README.rst --- --- --- --- local.conf --- --- --- live-migration-setup --- --- --- --- README.rst --- --- --- --- local.conf.controller --- --- --- --- local.conf.compute1 --- --- --- --- local.conf.compute2 --- --- --- minimal-neutron-setup --- --- --- --- README.rst --- --- --- --- local.conf --- --- s390x-1.1.1-vulcan --- --- --- minimum-setup --- --- --- --- README.rst --- --- --- --- local.conf --- --- --- live-migration-setup --- --- --- --- README.rst --- --- --- --- local.conf.controller --- --- --- --- local.conf.compute1 --- --- --- --- local.conf.compute2 --- mitaka --- --- # same structure as master branch. omitted for brevity --- liberty --- --- # same structure as master branch. omitted for brevity Thoughts? Regards, Markus Zoeller (markus_z) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev Love the idea personally. Maybe we could start with a working Neutron multi node deployment!!! __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ 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] [all] [devstack] Adding example "local.conf" files for testing?
+1 more example and documentation are welcomed On Tue, Apr 19, 2016 at 3:10 AM, John Griffith wrote: > > > On Thu, Apr 14, 2016 at 1:31 AM, Markus Zoeller > wrote: > >> Sometimes (especially when I try to reproduce bugs) I have the need >> to set up a local environment with devstack. Everytime I have to look >> at my notes to check which option in the "local.conf" have to be set >> for my needs. I'd like to add a folder in devstacks tree which hosts >> multiple example local.conf files for different, often used setups. >> Something like this: >> >> example-confs >> --- newton >> --- --- x86-ubuntu-1404 >> --- --- --- minimum-setup >> --- --- --- --- README.rst >> --- --- --- --- local.conf >> --- --- --- serial-console-setup >> --- --- --- --- README.rst >> --- --- --- --- local.conf >> --- --- --- live-migration-setup >> --- --- --- --- README.rst >> --- --- --- --- local.conf.controller >> --- --- --- --- local.conf.compute1 >> --- --- --- --- local.conf.compute2 >> --- --- --- minimal-neutron-setup >> --- --- --- --- README.rst >> --- --- --- --- local.conf >> --- --- s390x-1.1.1-vulcan >> --- --- --- minimum-setup >> --- --- --- --- README.rst >> --- --- --- --- local.conf >> --- --- --- live-migration-setup >> --- --- --- --- README.rst >> --- --- --- --- local.conf.controller >> --- --- --- --- local.conf.compute1 >> --- --- --- --- local.conf.compute2 >> --- mitaka >> --- --- # same structure as master branch. omitted for brevity >> --- liberty >> --- --- # same structure as master branch. omitted for brevity >> >> Thoughts? >> >> Regards, Markus Zoeller (markus_z) >> >> >> __ >> 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 >> > Love the idea personally. Maybe we could start with a working Neutron > multi node deployment!!! > > > __ > 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 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] [all] [devstack] Adding example "local.conf" files for testing?
On Thu, Apr 14, 2016 at 1:31 AM, Markus Zoeller wrote: > Sometimes (especially when I try to reproduce bugs) I have the need > to set up a local environment with devstack. Everytime I have to look > at my notes to check which option in the "local.conf" have to be set > for my needs. I'd like to add a folder in devstacks tree which hosts > multiple example local.conf files for different, often used setups. > Something like this: > > example-confs > --- newton > --- --- x86-ubuntu-1404 > --- --- --- minimum-setup > --- --- --- --- README.rst > --- --- --- --- local.conf > --- --- --- serial-console-setup > --- --- --- --- README.rst > --- --- --- --- local.conf > --- --- --- live-migration-setup > --- --- --- --- README.rst > --- --- --- --- local.conf.controller > --- --- --- --- local.conf.compute1 > --- --- --- --- local.conf.compute2 > --- --- --- minimal-neutron-setup > --- --- --- --- README.rst > --- --- --- --- local.conf > --- --- s390x-1.1.1-vulcan > --- --- --- minimum-setup > --- --- --- --- README.rst > --- --- --- --- local.conf > --- --- --- live-migration-setup > --- --- --- --- README.rst > --- --- --- --- local.conf.controller > --- --- --- --- local.conf.compute1 > --- --- --- --- local.conf.compute2 > --- mitaka > --- --- # same structure as master branch. omitted for brevity > --- liberty > --- --- # same structure as master branch. omitted for brevity > > Thoughts? > > Regards, Markus Zoeller (markus_z) > > > __ > 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 > Love the idea personally. Maybe we could start with a working Neutron multi node deployment!!! __ 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] [all] [devstack] Adding example "local.conf" files for testing?
Markus Zoeller wrote: > I guess having an IF-ELSE block in a "local.conf" is > crazy talk? Yes, I think it is. local.conf is already a pretty big complex thing for someone starting out, as it is. -- 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] [all] [devstack] Adding example "local.conf" files for testing?
> From: Dean Troyer > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 04/14/2016 08:18 PM > Subject: Re: [openstack-dev] [all] [devstack] Adding example > "local.conf" files for testing? > > On Thu, Apr 14, 2016 at 11:58 AM, Markus Zoeller wrote: > Let me know what you think: https://review.openstack.org/#/c/305967/ > > My only real concern is you've implied a structure that will > potentially have many combinations of configurations and those will > bitrot. How different are x86 and s390 arch in local.conf? (I've > never seen an s390 local.conf!) I do know there are few, if any, > differences between most ubuntu and fedora configs, we abstract most > of that out in the scripts. > > I wonder if the grouping of configs might be better suited along usa- > case lines? nova-net vs neutron, single- vs multi-node, etc. > > Thanks for getting this started! > dt > > -- > > Dean Troyer > dtro...@gmail.com The main difference between x86 and s390x (system z) is that s390x doesn't support nova-network and VNC|RDP|SPICE. Which means s390x depends on Neutron and the "serial console". The rest should work like on x86. I guess having an IF-ELSE block in a "local.conf" is crazy talk? Regards, Markus Zoeller (markus_z) __ 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] [all] [devstack] Adding example "local.conf" files for testing?
On Thu, 14 Apr 2016 13:17:48 -0500, Dean Troyer wrote: My only real concern is you've implied a structure that will potentially have many combinations of configurations and those will bitrot. How different are x86 and s390 arch in local.conf? (I've never seen an s390 local.conf!) I do know there are few, if any, differences between most ubuntu and fedora configs, we abstract most of that out in the scripts. I wonder if the grouping of configs might be better suited along usa-case lines? nova-net vs neutron, single- vs multi-node, etc. +1. This already exists to some extent in the devstack documentation but it's a bit scattered [1][2] and I rummage around to find it when I need it. For multi-node I have also gone to find a recent multi-node tempest job run to copy some devstack local.conf settings before. So, I agree it would be helpful to have some use-case based samples in an easy to navigate place. -melanie [1] http://docs.openstack.org/developer/devstack/configuration.html#multi-node-setup [2] http://docs.openstack.org/developer/devstack/configuration.html#neutron __ 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] [all] [devstack] Adding example "local.conf" files for testing?
On Thu, Apr 14, 2016 at 11:58 AM, Markus Zoeller wrote: > Let me know what you think: https://review.openstack.org/#/c/305967/ My only real concern is you've implied a structure that will potentially have many combinations of configurations and those will bitrot. How different are x86 and s390 arch in local.conf? (I've never seen an s390 local.conf!) I do know there are few, if any, differences between most ubuntu and fedora configs, we abstract most of that out in the scripts. I wonder if the grouping of configs might be better suited along usa-case lines? nova-net vs neutron, single- vs multi-node, etc. Thanks for getting this started! dt -- Dean Troyer dtro...@gmail.com __ 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] [all] [devstack] Adding example "local.conf" files for testing?
> From: Matt Riedemann > To: openstack-dev@lists.openstack.org > Date: 04/14/2016 04:53 PM > Subject: Re: [openstack-dev] [all] [devstack] Adding example > "local.conf" files for testing? > > > > On 4/14/2016 6:09 AM, Sean Dague wrote: > > On 04/14/2016 05:19 AM, Markus Zoeller wrote: > >>> From: Neil Jerram > >>> To: "OpenStack Development Mailing List (not for usage questions)" > >>> > >>> Date: 04/14/2016 10:50 AM > >>> Subject: Re: [openstack-dev] [all] [devstack] Adding example > >>> "local.conf" files for testing? > >>> > >>> On 14/04/16 08:35, Markus Zoeller wrote: > >>>> Sometimes (especially when I try to reproduce bugs) I have the need > >>>> to set up a local environment with devstack. Everytime I have to look > >>>> at my notes to check which option in the "local.conf" have to be set > >>>> for my needs. I'd like to add a folder in devstacks tree which hosts > >>>> multiple example local.conf files for different, often used setups. > >>>> Something like this: > >>>> > >>>> example-confs > >>>> --- newton > >>>> --- --- x86-ubuntu-1404 > >>>> --- --- --- minimum-setup > >>>> --- --- --- --- README.rst > >>>> --- --- --- --- local.conf > >>>> --- --- --- serial-console-setup > >>>> --- --- --- --- README.rst > >>>> --- --- --- --- local.conf > >>>> --- --- --- live-migration-setup > >>>> --- --- --- --- README.rst > >>>> --- --- --- --- local.conf.controller > >>>> --- --- --- --- local.conf.compute1 > >>>> --- --- --- --- local.conf.compute2 > >>>> --- --- --- minimal-neutron-setup > >>>> --- --- --- --- README.rst > >>>> --- --- --- --- local.conf > >>>> --- --- s390x-1.1.1-vulcan > >>>> --- --- --- minimum-setup > >>>> --- --- --- --- README.rst > >>>> --- --- --- --- local.conf > >>>> --- --- --- live-migration-setup > >>>> --- --- --- --- README.rst > >>>> --- --- --- --- local.conf.controller > >>>> --- --- --- --- local.conf.compute1 > >>>> --- --- --- --- local.conf.compute2 > >>>> --- mitaka > >>>> --- --- # same structure as master branch. omitted for brevity > >>>> --- liberty > >>>> --- --- # same structure as master branch. omitted for brevity > >>>> > >>>> Thoughts? > >>> > >>> Yes, this looks useful to me. Only thing is that you shouldn't need the > >> > >>> per-release subtrees, though; the DevStack repository already has > >>> per-release stable/ branches, which you need to check out in > >>> order to do a DevStack setup of a past release. So I would expect the > >>> local.confs for each past release to live in the corresponding branch. > >>> > >>> Regards, > >>> Neil > >> > >> My intention was to avoid that there is a folder "current" or "trunk" > >> or similar, which doesn't get updated. That's the issue Steve talked > >> about. > >> > >> The workflow could be, at every new cycle: > >> * create a new "release folder" (Newton, Ocata, ...) > >> * copy the "setup folders" (minimum-setup, ...) to the new folder > >> * clean up the "local.conf" file(s) of deprecated options > >> * delete a "release folder" if the release is EOL > >> > >> I also assume that this would make potential backports easier. > > > > I think this would be useful, and accepted easily. > > > > I *don't* think we want per release directories. Because it confuses the > > issue on whether or not devstack master can install liberty (which it > > can't). > > > > Every local.conf should include a documentation page as well that > > describes the scenario, which means these would be easy to snag off the > > web docs. > > > >-Sean > > > > +1 to add example scenarios (I have a copy of a basic neutron + ovs that > I got from a co-worker) and -1 on release-specific directories, we don't > need them as pointed out already, that's what the branches are for in > the git repo. The trunk local.confs should be updated naturally as > people try to use them and hit issues. > > -- > > Thanks, > > Matt Riedemann > Let me know what you think: https://review.openstack.org/#/c/305967/ __ 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] [all] [devstack] Adding example "local.conf" files for testing?
On 4/14/2016 6:09 AM, Sean Dague wrote: On 04/14/2016 05:19 AM, Markus Zoeller wrote: From: Neil Jerram To: "OpenStack Development Mailing List (not for usage questions)" Date: 04/14/2016 10:50 AM Subject: Re: [openstack-dev] [all] [devstack] Adding example "local.conf" files for testing? On 14/04/16 08:35, Markus Zoeller wrote: Sometimes (especially when I try to reproduce bugs) I have the need to set up a local environment with devstack. Everytime I have to look at my notes to check which option in the "local.conf" have to be set for my needs. I'd like to add a folder in devstacks tree which hosts multiple example local.conf files for different, often used setups. Something like this: example-confs --- newton --- --- x86-ubuntu-1404 --- --- --- minimum-setup --- --- --- --- README.rst --- --- --- --- local.conf --- --- --- serial-console-setup --- --- --- --- README.rst --- --- --- --- local.conf --- --- --- live-migration-setup --- --- --- --- README.rst --- --- --- --- local.conf.controller --- --- --- --- local.conf.compute1 --- --- --- --- local.conf.compute2 --- --- --- minimal-neutron-setup --- --- --- --- README.rst --- --- --- --- local.conf --- --- s390x-1.1.1-vulcan --- --- --- minimum-setup --- --- --- --- README.rst --- --- --- --- local.conf --- --- --- live-migration-setup --- --- --- --- README.rst --- --- --- --- local.conf.controller --- --- --- --- local.conf.compute1 --- --- --- --- local.conf.compute2 --- mitaka --- --- # same structure as master branch. omitted for brevity --- liberty --- --- # same structure as master branch. omitted for brevity Thoughts? Yes, this looks useful to me. Only thing is that you shouldn't need the per-release subtrees, though; the DevStack repository already has per-release stable/ branches, which you need to check out in order to do a DevStack setup of a past release. So I would expect the local.confs for each past release to live in the corresponding branch. Regards, Neil My intention was to avoid that there is a folder "current" or "trunk" or similar, which doesn't get updated. That's the issue Steve talked about. The workflow could be, at every new cycle: * create a new "release folder" (Newton, Ocata, ...) * copy the "setup folders" (minimum-setup, ...) to the new folder * clean up the "local.conf" file(s) of deprecated options * delete a "release folder" if the release is EOL I also assume that this would make potential backports easier. I think this would be useful, and accepted easily. I *don't* think we want per release directories. Because it confuses the issue on whether or not devstack master can install liberty (which it can't). Every local.conf should include a documentation page as well that describes the scenario, which means these would be easy to snag off the web docs. -Sean +1 to add example scenarios (I have a copy of a basic neutron + ovs that I got from a co-worker) and -1 on release-specific directories, we don't need them as pointed out already, that's what the branches are for in the git repo. The trunk local.confs should be updated naturally as people try to use them and hit issues. -- 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] [all] [devstack] Adding example "local.conf" files for testing?
On 04/14/2016 05:19 AM, Markus Zoeller wrote: >> From: Neil Jerram >> To: "OpenStack Development Mailing List (not for usage questions)" >> >> Date: 04/14/2016 10:50 AM >> Subject: Re: [openstack-dev] [all] [devstack] Adding example >> "local.conf" files for testing? >> >> On 14/04/16 08:35, Markus Zoeller wrote: >>> Sometimes (especially when I try to reproduce bugs) I have the need >>> to set up a local environment with devstack. Everytime I have to look >>> at my notes to check which option in the "local.conf" have to be set >>> for my needs. I'd like to add a folder in devstacks tree which hosts >>> multiple example local.conf files for different, often used setups. >>> Something like this: >>> >>> example-confs >>> --- newton >>> --- --- x86-ubuntu-1404 >>> --- --- --- minimum-setup >>> --- --- --- --- README.rst >>> --- --- --- --- local.conf >>> --- --- --- serial-console-setup >>> --- --- --- --- README.rst >>> --- --- --- --- local.conf >>> --- --- --- live-migration-setup >>> --- --- --- --- README.rst >>> --- --- --- --- local.conf.controller >>> --- --- --- --- local.conf.compute1 >>> --- --- --- --- local.conf.compute2 >>> --- --- --- minimal-neutron-setup >>> --- --- --- --- README.rst >>> --- --- --- --- local.conf >>> --- --- s390x-1.1.1-vulcan >>> --- --- --- minimum-setup >>> --- --- --- --- README.rst >>> --- --- --- --- local.conf >>> --- --- --- live-migration-setup >>> --- --- --- --- README.rst >>> --- --- --- --- local.conf.controller >>> --- --- --- --- local.conf.compute1 >>> --- --- --- --- local.conf.compute2 >>> --- mitaka >>> --- --- # same structure as master branch. omitted for brevity >>> --- liberty >>> --- --- # same structure as master branch. omitted for brevity >>> >>> Thoughts? >> >> Yes, this looks useful to me. Only thing is that you shouldn't need the > >> per-release subtrees, though; the DevStack repository already has >> per-release stable/ branches, which you need to check out in >> order to do a DevStack setup of a past release. So I would expect the >> local.confs for each past release to live in the corresponding branch. >> >> Regards, >>Neil > > My intention was to avoid that there is a folder "current" or "trunk" > or similar, which doesn't get updated. That's the issue Steve talked > about. > > The workflow could be, at every new cycle: > * create a new "release folder" (Newton, Ocata, ...) > * copy the "setup folders" (minimum-setup, ...) to the new folder > * clean up the "local.conf" file(s) of deprecated options > * delete a "release folder" if the release is EOL > > I also assume that this would make potential backports easier. I think this would be useful, and accepted easily. I *don't* think we want per release directories. Because it confuses the issue on whether or not devstack master can install liberty (which it can't). Every local.conf should include a documentation page as well that describes the scenario, which means these would be easy to snag off the web docs. -Sean -- Sean Dague http://dague.net __ 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] [all] [devstack] Adding example "local.conf" files for testing?
> From: Neil Jerram > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 04/14/2016 10:50 AM > Subject: Re: [openstack-dev] [all] [devstack] Adding example > "local.conf" files for testing? > > On 14/04/16 08:35, Markus Zoeller wrote: > > Sometimes (especially when I try to reproduce bugs) I have the need > > to set up a local environment with devstack. Everytime I have to look > > at my notes to check which option in the "local.conf" have to be set > > for my needs. I'd like to add a folder in devstacks tree which hosts > > multiple example local.conf files for different, often used setups. > > Something like this: > > > > example-confs > > --- newton > > --- --- x86-ubuntu-1404 > > --- --- --- minimum-setup > > --- --- --- --- README.rst > > --- --- --- --- local.conf > > --- --- --- serial-console-setup > > --- --- --- --- README.rst > > --- --- --- --- local.conf > > --- --- --- live-migration-setup > > --- --- --- --- README.rst > > --- --- --- --- local.conf.controller > > --- --- --- --- local.conf.compute1 > > --- --- --- --- local.conf.compute2 > > --- --- --- minimal-neutron-setup > > --- --- --- --- README.rst > > --- --- --- --- local.conf > > --- --- s390x-1.1.1-vulcan > > --- --- --- minimum-setup > > --- --- --- --- README.rst > > --- --- --- --- local.conf > > --- --- --- live-migration-setup > > --- --- --- --- README.rst > > --- --- --- --- local.conf.controller > > --- --- --- --- local.conf.compute1 > > --- --- --- --- local.conf.compute2 > > --- mitaka > > --- --- # same structure as master branch. omitted for brevity > > --- liberty > > --- --- # same structure as master branch. omitted for brevity > > > > Thoughts? > > Yes, this looks useful to me. Only thing is that you shouldn't need the > per-release subtrees, though; the DevStack repository already has > per-release stable/ branches, which you need to check out in > order to do a DevStack setup of a past release. So I would expect the > local.confs for each past release to live in the corresponding branch. > > Regards, >Neil My intention was to avoid that there is a folder "current" or "trunk" or similar, which doesn't get updated. That's the issue Steve talked about. The workflow could be, at every new cycle: * create a new "release folder" (Newton, Ocata, ...) * copy the "setup folders" (minimum-setup, ...) to the new folder * clean up the "local.conf" file(s) of deprecated options * delete a "release folder" if the release is EOL I also assume that this would make potential backports easier. Regards, Markus Zoeller (markus_z) __ 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] [all] [devstack] Adding example "local.conf" files for testing?
On 14/04/16 08:35, Markus Zoeller wrote: > Sometimes (especially when I try to reproduce bugs) I have the need > to set up a local environment with devstack. Everytime I have to look > at my notes to check which option in the "local.conf" have to be set > for my needs. I'd like to add a folder in devstacks tree which hosts > multiple example local.conf files for different, often used setups. > Something like this: > > example-confs > --- newton > --- --- x86-ubuntu-1404 > --- --- --- minimum-setup > --- --- --- --- README.rst > --- --- --- --- local.conf > --- --- --- serial-console-setup > --- --- --- --- README.rst > --- --- --- --- local.conf > --- --- --- live-migration-setup > --- --- --- --- README.rst > --- --- --- --- local.conf.controller > --- --- --- --- local.conf.compute1 > --- --- --- --- local.conf.compute2 > --- --- --- minimal-neutron-setup > --- --- --- --- README.rst > --- --- --- --- local.conf > --- --- s390x-1.1.1-vulcan > --- --- --- minimum-setup > --- --- --- --- README.rst > --- --- --- --- local.conf > --- --- --- live-migration-setup > --- --- --- --- README.rst > --- --- --- --- local.conf.controller > --- --- --- --- local.conf.compute1 > --- --- --- --- local.conf.compute2 > --- mitaka > --- --- # same structure as master branch. omitted for brevity > --- liberty > --- --- # same structure as master branch. omitted for brevity > > Thoughts? Yes, this looks useful to me. Only thing is that you shouldn't need the per-release subtrees, though; the DevStack repository already has per-release stable/ branches, which you need to check out in order to do a DevStack setup of a past release. So I would expect the local.confs for each past release to live in the corresponding branch. Regards, Neil __ 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] [all] [devstack] Adding example "local.conf" files for testing?
+1, not sure if something that sophisticated is needed, but having a few
examples wouldn't hurt. I also go back to one that I have saved (
https://gist.github.com/stevemart/1f2a4e528606d178b7d1) and comment /
uncomment lines as needed.
The trouble with examples is that they have a tendency to bit rot.
stevemar
From: "Markus Zoeller"
To: openstack-dev
Date: 2016/04/14 03:34 AM
Subject: [openstack-dev] [all] [devstack] Adding example "local.conf"
files for testing?
Sometimes (especially when I try to reproduce bugs) I have the need
to set up a local environment with devstack. Everytime I have to look
at my notes to check which option in the "local.conf" have to be set
for my needs. I'd like to add a folder in devstacks tree which hosts
multiple example local.conf files for different, often used setups.
Something like this:
example-confs
--- newton
--- --- x86-ubuntu-1404
--- --- --- minimum-setup
--- --- --- --- README.rst
--- --- --- --- local.conf
--- --- --- serial-console-setup
--- --- --- --- README.rst
--- --- --- --- local.conf
--- --- --- live-migration-setup
--- --- --- --- README.rst
--- --- --- --- local.conf.controller
--- --- --- --- local.conf.compute1
--- --- --- --- local.conf.compute2
--- --- --- minimal-neutron-setup
--- --- --- --- README.rst
--- --- --- --- local.conf
--- --- s390x-1.1.1-vulcan
--- --- --- minimum-setup
--- --- --- --- README.rst
--- --- --- --- local.conf
--- --- --- live-migration-setup
--- --- --- --- README.rst
--- --- --- --- local.conf.controller
--- --- --- --- local.conf.compute1
--- --- --- --- local.conf.compute2
--- mitaka
--- --- # same structure as master branch. omitted for brevity
--- liberty
--- --- # same structure as master branch. omitted for brevity
Thoughts?
Regards, Markus Zoeller (markus_z)
__
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 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] [all] [devstack] Adding example "local.conf" files for testing?
Sometimes (especially when I try to reproduce bugs) I have the need to set up a local environment with devstack. Everytime I have to look at my notes to check which option in the "local.conf" have to be set for my needs. I'd like to add a folder in devstacks tree which hosts multiple example local.conf files for different, often used setups. Something like this: example-confs --- newton --- --- x86-ubuntu-1404 --- --- --- minimum-setup --- --- --- --- README.rst --- --- --- --- local.conf --- --- --- serial-console-setup --- --- --- --- README.rst --- --- --- --- local.conf --- --- --- live-migration-setup --- --- --- --- README.rst --- --- --- --- local.conf.controller --- --- --- --- local.conf.compute1 --- --- --- --- local.conf.compute2 --- --- --- minimal-neutron-setup --- --- --- --- README.rst --- --- --- --- local.conf --- --- s390x-1.1.1-vulcan --- --- --- minimum-setup --- --- --- --- README.rst --- --- --- --- local.conf --- --- --- live-migration-setup --- --- --- --- README.rst --- --- --- --- local.conf.controller --- --- --- --- local.conf.compute1 --- --- --- --- local.conf.compute2 --- mitaka --- --- # same structure as master branch. omitted for brevity --- liberty --- --- # same structure as master branch. omitted for brevity Thoughts? Regards, Markus Zoeller (markus_z) __ 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
