Open Stack

On Tue, Dec 1, 2015 at 5:08 PM, Boris Pavlovic <boris at pavlovic.me> wrote:

> Dina,
>
> Is it possible just to get for performance team official status?
>

Not that I can see... but it's a good question. We have all sorts of
working groups, such as the API working group, that has a repo for
guidelines[1], but doesn't sit anywhere in the projects.yaml file[2]. They
publish to specs.openstack.org. [3]

My hesitation to allow any project not under our governance umbrella lies
in the loss of quality and focus for the docs.openstack.org site. So far,
working groups have found other places to publish that meet their needs.
However, if rally would like to publish a relevant piece for their project,
of course the doc jobs can be set up. My thinking is that performance
information should couple tightly with the projects that help users
understand and tune performance.

I hope this explains my thinking a bit.

Thanks,
Anne

1. https://github.com/openstack/api-wg
2.
https://github.com/openstack/governance/blob/master/reference/projects.yaml
3. http://specs.openstack.org/openstack/api-wg/


>
> However, for now we can use "rally" namespace if you would like.
> Like OSprofiler is for part of Rally for now...
>
>
> Best regards,
> Boris Pavlovic
>
> On Tue, Dec 1, 2015 at 4:57 AM, Dina Belova <dbelova at mirantis.com> wrote:
>
>> Thierry,
>>
>> this can work, of course, but in that case we won't have, for instance,
>> ready reviewing mechanism for test plans. That is not the biggest deal I
>> suppose, feedback can be collected in various ways. So if wiki will be the
>> decision, I suppose it's ok.
>>
>> Probably some operators will comment as well, as i suspect they will be
>> one of the groups interesting in such docs source.
>>
>> Cheers
>> Dina
>>
>> On Tue, Dec 1, 2015 at 3:43 PM, Thierry Carrez <thierry at openstack.org>
>> wrote:
>>
>>> Dina Belova wrote:
>>> > I'm writing to find out where to place information that Performance
>>> Team
>>> > would like to share with community. We would like to share (and grab
>>> the
>>> > feedback on) test plans (for OpenStack itself - we can use and develop
>>> > Rally, for underlying layers like DB, MQ something else.), results of
>>> > those testing, results of various investigations, etc... I think it'll
>>> > be very useful to have some web page or whatever where we'll be able to
>>> > show all the progress.
>>> >
>>> > Although Performance Team is not (yet :)) official OpenStack team, so
>>> we
>>> > cannot simply use docs.openstack.org <http://docs.openstack.org> for
>>> > this purpose for just team's needs. I had a quick chat with Anne, she
>>> > suggested to use Rally as an umbrella for this potential docs
>>> > repository, but only part of the information will be related there to
>>> > Rally in fact.
>>> >
>>> > So please share your opinion on what can be done here :)
>>>
>>> In the past we've liberally used the wiki as a free publishing space...
>>> Would that be an option for you ?
>>>
>>> --
>>> Thierry Carrez (ttx)
>>>
>>> _______________________________________________
>>> OpenStack-TC mailing list
>>> OpenStack-TC at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc
>>>
>>
>>
>>
>> --
>>
>> Best regards,
>>
>> Dina Belova
>>
>> Software Engineer
>>
>> Mirantis Inc.
>>
>> _______________________________________________
>> OpenStack-operators mailing list
>> OpenStack-operators at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>


-- 
Anne Gentle
Rackspace
Principal Engineer
www.justwriteclick.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-tc/attachments/20151202/e6b44c09/attachment.html>