Re: [openstack-dev] [Openstack-operators] [Telco][NFV][infra] Review process of TelcoWG use cases
Hello everyone, We already got good feedback on my sandbox test review. So I would like to move forward. With review [1] we will get a stackforge repo called „telcowg-usecases“. Submitting a usecase will then follow the process of OpenStack development (see [2]). The is one thing currently open: Anita suggested to rename our IRC channel from #openstack-nfv to #openstack-telcowg which seems logical to me. If we agree to this I will register the channel and we can move forward. I won’t be able to participate in our meeting today, but feel free to discuss this topic there and let me know. Regards Marc [1]: https://review.openstack.org/#/c/155248/ [2]: https://wiki.openstack.org/wiki/How_To_Contribute Am 06.02.2015 um 12:11 schrieb Marc Koderer : > Hello everyone, > > we are currently facing the issue that we don’t know how to proceed with > our telco WG use cases. There are many of them already defined but the > reviews via Etherpad doesn’t seem to work. > > I suggest to do a review on them with the usual OpenStack tooling. > Therefore I uploaded one of them (Session Border Controller) to the > Gerrit system into the sandbox repo: > >https://review.openstack.org/#/c/152940/1 > > I would really like to see how many review we can get on it. > If this works out my idea is the following: > > - we create a project under Stackforge called telcowg-usecases > - we link blueprint related to this use case > - we build a core team and approve/prioritize them > > Regards > Marc > ___ > OpenStack-operators mailing list > openstack-operat...@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators __ 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] [Openstack-operators] [Telco][NFV][infra] Review process of TelcoWG use cases
- Original Message - > From: "Anthony Veiga" > To: "OpenStack Development Mailing List (not for usage questions)" > > > > On Feb 6, 2015, at 8:17 , Jeremy Stanley wrote: > > > > On 2015-02-06 12:11:40 +0100 (+0100), Marc Koderer wrote: > > [...] > >> Therefore I uploaded one of them (Session Border Controller) to > >> the Gerrit system into the sandbox repo: > >> > >>https://review.openstack.org/#/c/152940/1 > > [...] > > > > This looks a lot like the beginnings of a specification which has > > implications for multiple OpenStack projects. Would proposing a > > cross-project spec in the openstack/openstack-specs repository be an > > appropriate alternative?\ > > It does look like that. However, the intent here is to allow non-developer > members of a Telco provide the use cases they need to accomplish. This way > the Telco WG can identify gaps and file a proper spec into each of the > OpenStack projects. Indeed, what we're trying to do is help the non-developer members of the group articulate their use cases and tease them out to a level that is meaningful to someone who is not immersed in telecommunications themselves. In this way we hope to in turn be able to create meaningful specifications for the actual OpenStack projects impacted. It's possible that some of these will be truly cross-project and therefore head to openstack-specs but initial indications seem to be that most will either be specific to a project, or cross only a couple of projects (e.g. nova and neutron) - I am sure someone will come up with some more exceptions to this statement to prove me wrong :). Thanks, Steve __ 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] [Openstack-operators] [Telco][NFV][infra] Review process of TelcoWG use cases
> On Feb 6, 2015, at 8:17 , Jeremy Stanley wrote: > > On 2015-02-06 12:11:40 +0100 (+0100), Marc Koderer wrote: > [...] >> Therefore I uploaded one of them (Session Border Controller) to >> the Gerrit system into the sandbox repo: >> >>https://review.openstack.org/#/c/152940/1 > [...] > > This looks a lot like the beginnings of a specification which has > implications for multiple OpenStack projects. Would proposing a > cross-project spec in the openstack/openstack-specs repository be an > appropriate alternative?\ It does look like that. However, the intent here is to allow non-developer members of a Telco provide the use cases they need to accomplish. This way the Telco WG can identify gaps and file a proper spec into each of the OpenStack projects. > >> - we create a project under Stackforge called telcowg-usecases >> - we link blueprint related to this use case >> - we build a core team and approve/prioritize them > > I suppose this somewhat parallels how the API Working Group has > decided to operate, so perhaps you just need a dedicated repository > for Telco Working Group documents in general... some of which would > percolate to cross-project specs (or maybe just related per-project > specs) once sufficiently refined for a broader audience? We’re considering a proper repo. As Marc said, this is our first attempt at seeing if this can actually work. > -- > Jeremy Stanley > > __ > 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 > -Anthony __ 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] [Openstack-operators] [Telco][NFV][infra] Review process of TelcoWG use cases
On 2015-02-06 12:11:40 +0100 (+0100), Marc Koderer wrote: [...] > Therefore I uploaded one of them (Session Border Controller) to > the Gerrit system into the sandbox repo: > > https://review.openstack.org/#/c/152940/1 [...] This looks a lot like the beginnings of a specification which has implications for multiple OpenStack projects. Would proposing a cross-project spec in the openstack/openstack-specs repository be an appropriate alternative? > - we create a project under Stackforge called telcowg-usecases > - we link blueprint related to this use case > - we build a core team and approve/prioritize them I suppose this somewhat parallels how the API Working Group has decided to operate, so perhaps you just need a dedicated repository for Telco Working Group documents in general... some of which would percolate to cross-project specs (or maybe just related per-project specs) once sufficiently refined for a broader audience? -- Jeremy Stanley __ 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
