On Tue, Jul 19, 2016 at 2:58 PM, Cory Johns <[email protected]> wrote: > In the Juju charms we are adding to Apache Bigtop, one of the scenarios we > want to handle is upgrading from one Bigtop release to another. I tried to > find documentation on how to upgrade a Bigtop release, but my google-fu > failed me.
That's because I don't think it exists ;-) The biggest hurdle is the fact that you can really only upgrade at stack-level, not individual component's level (the dependencies seep into the implementation). > What is the recommended way to upgrade a deployment of Apache Bigtop to a > new Bigtop release? Does Bigtop support in-place upgrades, or is it > designed to do a side-by-side deployment of the new version and transition > to that? Actually, that's a great question for you, Canonical guys. Isn't part of the reason you came up with the new packaging format (snap) the fact that traditional DEBs make side-by-side installs of different versions of the same stack next to impossible? So let me flip that question on you: what's Ubuntu's guidance on that? With RPM you can at least try to do relocatable RPMs and install them under the stack trees to facilitate rolling upgrades, with DEB, I don't think it is possible. Thanks, Roman.
