Open Stack

Sean, David

So seems like I am better in writing code then english, sorry for that=)

Let me try to explain my position and try to make this situation clear.

We have the great program "QA" that helps to keep OpenStack working
(automation of testing, unit/function/integration tests, log analyze,
elastic recheck, dsvm jobs and so on).
I really appreciate what you guys are doing, and thank you for that!

But the scope of what Rally team is working on is quite different.
It's more about Operations cases e.g. making it simple to understand what
is happening inside
production OpenStack clouds (especially under load). To do that, it's not
enough just to write tools
(like Rally), it requires extending OpenStack API, to make it simple to
retrieve via OpenStack API audit information (profiling data - OSprofiler,
querying logs - LogaaS, configuration discovery - Satori), which is really
out of scope of QA (it should be done inside OpenStack projects, not on top
of them).

And to coordinate this job we should have Program "Operations" for that.

The reason why this program is called "Performance & Scalability" and not
"Operations" is that current Rally team scope is "Performance &
Scalability". But as I see Rally team really would like to extend it's
scope to "Operations". So "Performance & Scalability" should be the first
piece of big "Operation" program (that includes such projects like: rally,
osprofiler, logaas, satori, rubick and probably some others)

So let's move to the Operation program with "baby steps".


Best regards,
Boris Pavlovic


On Tue, Jul 22, 2014 at 8:18 PM, Sean Dague <sean at dague.net> wrote:

> On 07/22/2014 11:58 AM, David Kranz wrote:
> > On 07/22/2014 10:44 AM, Sean Dague wrote:
> >> Honestly, I'm really not sure I see this as a different program, but is
> >> really something that should be folded into the QA program. I feel like
> >> a top level effort like this is going to lead to a lot of duplication in
> >> the data analysis that's currently going on, as well as functionality
> >> for better load driver UX.
> >>
> >>      -Sean
> > +1
> > It will also lead to pointless discussions/arguments about which
> > activities are part of "QA" and which are part of
> > "Performance and Scalability Testing".
> >
> > QA Program mission:
> >
> > " 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."
> >
> > It is hard to see how $subj falls outside of that mission. Of course
> > rally would continue to have its own repo, review team, etc. as do
> > tempest and grenade.
>
> Right, 100% agreed. Rally would remain with it's own repo + review team,
> just like grenade.
>
>         -Sean
>
> --
> Sean Dague
> http://dague.net
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140723/16ea6477/attachment.html>