Loading…
This event has ended. View the official site or create your own event → Check it out
This event has ended. Create your own
View analytic
Friday, May 16 • 1:20pm - 2:00pm
Grenade current status and next steps

Sign up or log in to save this to your schedule and see who's attending!

Grenade is the upgrade testing framework for OpenStack that runs in
the gate. While it doesn't catch all upgrade issues, it does prevent a
large number of upgrade issues that would slip by otherwise.

In this session we plan to discuss major changes in Grenade that
happened in Icehouse cycle, like partial testing, and a more modular
framework moving foward.

The bulk of the session will look at the things we should do in the
next cycle, and prioritize some of the work, and hopefully recruit new
volunteers. This includes (but may not be limitted to):

* Forward upgrading (nearly done)
* Partial upgrade beyond n-cpu?
* Using grenade outside of the gate (it is often broken, we need a
better model for testing that)
* Documenting Grenade - very few people understand it, would be nice
to change
* Growing grenade contributors. Sean, Dean, Mauro, Joe is a very
small number of folks that understand this enough for the level
that we rely on it.
* Gate job formatting, grenade is still a big ugly dump like devstack
used to be, we should probably change that.
* Enhancing javelin (carry forward more resources)
* How to track TODO / bugs in grenade (we do this very poorly today)


(Session proposed by Sean Dague)


Friday May 16, 2014 1:20pm - 2:00pm
B301

Attendees (21)