(Note to program committee: feel free to combine this with any other Forum proposals about the Upgrade Checks.)
Cinder participated in the Stein community goal to add Upgrade Checks to Cinder, and we included new upgrade checks in the Train release. We see value in the upgrade checks, but are curious about how operators are actually using them. There are two primary issues. The first is logistical: you have to have the Train version of Cinder installed in order to run the upgrade check on your Stein deployment. Maybe the Train checks should be backported to Stein so you can run them on the system you intend to upgrade? How are you running the upgrade checks?
The second issue is the content of the upgrade checks for Cinder in Stein and Train. Have they been helpful? Are there items we missed that you wished had been included in the upgrade checks? We'd like to get your feedback.
Attendees will have an opportunity to share their experiences using the Cinder upgrade check mechanism so that we can improve it for future cycles.
