TripleO/TripleOCloud/MVP1and2Retrospective
< TripleO | TripleOCloud
This is a summary of the retrospective we did for MVP's 1 and two.
What went well
- Learned that the tools we've built work as expected on a realnetwork
- Fixed a bunch of key issues that were breaking things, including making the release of Havana nova-bm better
- Handled firedrills well: fixed quickly, and we all helped out
- Delivered quickly, immensely cool after one week to have a usable cloud any TripleO ATC can use, deployed with our tooling.
- Learnt (and tweaked things) to be more continuous in own development - handing things off, communicating across sunsets, helping out on patches to stop them stalling.
What went poorly
- we regressed devtest a couple of times
- toci showed the failures but was ignored
- lack of clarity around where to report toci issues
- lack of docs around debugging toci issues
- things stalled when we had a big backlog of reviews - peaked at about 20 - *just* for the CD overcloud.
What will we change
- We should communicate firedrills much more vigorously:
* TripleO folk should add a Firedrill card when a firedrill happens * Set the IRC channel topic too * Possibly send an email.
- Reviews for the overcloud can be +2'd by the author (if they are -core), retaining 2x +2, but not insisting that the +2's both be distinct from the author. We'll review this in a week and see how it went / if it's still needed.