Re: [openstack-dev] Program Description for OpenStack QA
Sean Dague wrote: Official Program Name: OpenStack Quality Assurance PTL: Sean Dague Mission Statement: Develop, maintain, and initiate tools and plans to ensure the upstream stability and quality of OpenStack, and its release readiness at any point during the release cycle. The OpenStack QA program starts with 2 git trees * tempest - https://github.com/openstack/tempest * grenade - https://github.com/openstack-dev/grenade Sounds good, please fill out wiki landing page at: https://wiki.openstack.org/wiki/QA Cheers, -- Thierry Carrez (ttx) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Program Description for OpenStack QA
On 07/15/2013 07:46 AM, Thierry Carrez wrote: Chmouel Boudjnah wrote: The OpenStack QA program starts with 2 git trees * tempest - https://github.com/openstack/tempest * grenade - https://github.com/openstack-dev/grenade I haven't read the full discussion on this so apologies if I am missing something, but why devstack is no part of this? Devstack falls somewhere between QA and Infrastructure... We raised briefly the subject of where we should attach it during the initial discussion on programs, then punted for later discussion. It falls in the same bucket as other central repositories like openstack/requirements -- everyone ends up contributing to those so it's difficult to attach them to any given program/team. Right, devstack's primary mission is still providing development environments to developers. We reuse it in QA and Infra, but it's kind of a different beast. So for now it just remains what it is, which I think is fine. I think it's good to be pragmatic about Programs and only fit the git trees that naturally fit into them, and just be really concerned that every git tree we carry has to be owned by a program. Sometimes we have useful code just because people are useful and doing good things for the community. I'd much rather let that bloom as is then spend a lot of time ensuring it fits into an existing program. -Sean -- Sean Dague http://dague.net ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Program Description for OpenStack QA
Sean Dague wrote: On 07/15/2013 07:46 AM, Thierry Carrez wrote: Chmouel Boudjnah wrote: The OpenStack QA program starts with 2 git trees * tempest - https://github.com/openstack/tempest * grenade - https://github.com/openstack-dev/grenade I haven't read the full discussion on this so apologies if I am missing something, but why devstack is no part of this? Devstack falls somewhere between QA and Infrastructure... We raised briefly the subject of where we should attach it during the initial discussion on programs, then punted for later discussion. It falls in the same bucket as other central repositories like openstack/requirements -- everyone ends up contributing to those so it's difficult to attach them to any given program/team. Right, devstack's primary mission is still providing development environments to developers. We reuse it in QA and Infra, but it's kind of a different beast. So for now it just remains what it is, which I think is fine. I think it's good to be pragmatic about Programs and only fit the git trees that naturally fit into them, and just be really concerned that every git tree we carry has to be owned by a program. Sometimes we have useful code just because people are useful and doing good things for the community. I'd much rather let that bloom as is then spend a lot of time ensuring it fits into an existing program. I'd generally agree with that. The only issue with devstack is that under the old project-based taxonomy it was classified as a gating project and therefore granted ATC status to its contributors. Under the new program-based taxonomy, if it's not adopted by a program then it would fall off the official ATC scope. That said, if nobody specific wants to own it it could also be co-adopted by multiple programs (I'd say QA and Infra). That would close that taxonomy change loophole as far as I am concerned... -- Thierry Carrez (ttx) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Program Description for OpenStack QA
Dolph Mathews wrote: On Monday, July 15, 2013, Thierry Carrez wrote: I'd generally agree with that. The only issue with devstack is that under the old project-based taxonomy it was classified as a gating project and therefore granted ATC status to its contributors. Under the new program-based taxonomy, if it's not adopted by a program then it would fall off the official ATC scope. How many people contribute to devstack that don't also contribute to some other ATC-granting project? Hopefully none :) But it's not just a question of falling off the ATC-granting scope... it's also that devstack is a critical piece of our CI system and I'd therefore prefer if it was taken care of by a team (or set of teams) under the Technical Committee authority. It used to be a project separate from OpenStack but we brought it to the fold for that precise reason. -- Thierry Carrez (ttx) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Program Description for OpenStack QA
On Mon, Jul 15, 2013 at 9:59 AM, Thierry Carrez thie...@openstack.org wrote: Hopefully none :) But it's not just a question of falling off the ATC-granting scope... it's also that devstack is a critical piece of our CI system and I'd therefore prefer if it was taken care of by a team (or set of teams) under the Technical Committee authority. It used to be a project separate from OpenStack but we brought it to the fold for that precise reason. I was reluctant to contribute to a plethora of programs if it was not necessary but it does not feel like there is a good fit for DevStack's multiple purposes. In my mind it is still first and foremost a development tool and quick way to build an OpenStack implementation for multiple other uses such as CI gating, Grenade, POC demos, whatever. Program proposal forthcoming... dt -- Dean Troyer dtro...@gmail.com ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Program Description for OpenStack QA
On 07/15/2013 08:07 AM, Sean Dague wrote: On 07/15/2013 07:46 AM, Thierry Carrez wrote: Chmouel Boudjnah wrote: The OpenStack QA program starts with 2 git trees * tempest - https://github.com/openstack/tempest * grenade - https://github.com/openstack-dev/grenade I haven't read the full discussion on this so apologies if I am missing something, but why devstack is no part of this? Devstack falls somewhere between QA and Infrastructure... We raised briefly the subject of where we should attach it during the initial discussion on programs, then punted for later discussion. It falls in the same bucket as other central repositories like openstack/requirements -- everyone ends up contributing to those so it's difficult to attach them to any given program/team. Right, devstack's primary mission is still providing development environments to developers. We reuse it in QA and Infra, but it's kind of a different beast. So for now it just remains what it is, which I think is fine. I think it's good to be pragmatic about Programs and only fit the git trees that naturally fit into them, and just be really concerned that every git tree we carry has to be owned by a program. I actually think it fits well into the QA umbrella. Yes, it's for dev environments, but what it provides is the ability to easily test your changes while developing. And as a result, it works great for QA/Infra needs. An easy OpenStack test environment is what devstack really provides, IMO. -- Russell Bryant ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Program Description for OpenStack QA
For general review (took us a little longer, we needed to elected a PTL first). Official Program Name: OpenStack Quality Assurance PTL: Sean Dague Mission Statement: Develop, maintain, and initiate tools and plans to ensure the upstream stability and quality of OpenStack, and its release readiness at any point during the release cycle. The OpenStack QA program starts with 2 git trees * tempest - https://github.com/openstack/tempest * grenade - https://github.com/openstack-dev/grenade We'll get more info up on the wiki over the coming weeks to fill out full description. -Sean -- Sean Dague http://dague.net ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
