Interim plan to move away from the mongo tarball

[Gustavo Niemeyer]

Hey Dave, James,

On Wed, Mar 20, 2013 at 1:31 AM, David Cheney
<david.cheney at canonical.com> wrote:
> The short version (email me if you really want the whole story).
>
> By Raring we hope to have mongo 2.2+ssl in a package for P, Q and R and a
> large amount of resources have been mobilised to making this happen, but
> that is only 1/2 the story.

That's a nice advancement, and a major undertaking at this point.

One of the reasons for the out-of-band tarball was that it gave us an
easy way to have the same MongoDB version running on all past
releases, and to have fine-grained control of exactly when and how to
upgrade it.

Keep in mind that we can't take over the stock MongoDB configuration
for the machine as it is today, since otherwise we're blocking charms
from using the package for their own needs, which means that in theory
any knowledge inserted into the package upgrading procedure will not
affect the data that is manipulated by juju itself.

The long term maintenance also feels tricky. We won't be able to use a
new MongoDB release without retrofitting the package into all
supported releases, which extends for a period of 5 years in LTSes.

Is there a plan for those topics?

(hoping this isn't as controversial as the last question I made)


gustavo @ http://niemeyer.net