I agree that this is not very delightful. I suppose the reason that we
have not dedicated a lot of time to this is because the steps that are
normally outlined are pretty hairy.
Upgrading openstack seems to slightly differ everytime, so I think each
release would need a separate customized set of recipes for upgrading.
I suppose the hardest problems would be: how do I make sure that custom
sql queries are only run once, should I create a separate recipe for
each component called upgrade and how do I remove that from my runlist
immediately after performed, should this be it's own upgrade cookbook?
We also need to consider how we will support upgrading since things can
and probably will fail. In this case how can we get to a good state if
the upgrade is unsuccessful.
I think we can definitely bring this up during a weekly meeting in order
to "trioratize" if properly. That said I am interested how other CM
systems deal with upgrades and I have a couple of contacts that I can
reach out to.
I may also run icehouse and then try to run Junoon top of it to see what
happens just for a POC start.
> --
> You received this message because you are subscribed to the Google Groups
> "opscode-chef-openstack" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
opscode-chef-open...@googlegroups.com.
> To post to this group, send email to
>
opscode-che...@googlegroups.com.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/opscode-chef-openstack/CAOqvHK_m%3DKFhii7XY2HoNB9SyLBOk-%2Bi%2BSxVbMYr%2B4QgGVX7qA%40mail.gmail.com.
> For more options, visit
https://groups.google.com/d/optout.