Juju and OS upgrades
Bug #1284734 reported by
Tom Haddon
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Won't Fix
|
Low
|
Unassigned |
Bug Description
We're currently in the final stages of bringing an openstack instance which will be deployed via Juju. We understand that we can upgrade to Icehouse and that Icehouse will be supported on both precise and trusty. So, presumably we'll be able to do OS upgrades of the Openstack components once we're on Icehouse, trusty is released (or trusty -> next LTS), and we're happy to go ahead with the upgrade.
The question I have is, how does Juju handle the OS being upgraded underneath it?
From discussions with Mark Ramm it seems Juju doesn't support this yet, so registering it as an issue so we have a way of tracking progress on it.
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: precise trusty |
Changed in juju-core: | |
milestone: | none → 2.0 |
tags: | added: canonical-is |
Changed in juju-core: | |
importance: | High → Medium |
Changed in juju-core: | |
importance: | Medium → Low |
Changed in juju-core: | |
status: | Triaged → Won't Fix |
To post a comment you must log in.
These are the factors we need to consider.
1. juju precise and trusty are statically linked, and booth created from the same compiler
2. Both use the cloud-archive, though trusty will pull packages from main/universe
3. Juju (as the the 1.17.4 release candidate I am testing now) supports
mongodb-server and juju-mongodb
The policy is to use the one that is present,
but the os upgrade may switch which on is present.
If the os upgrade keeps mongodb-server, and it is preferred over juju-mongodb,
not migration is needed,
but juju-mongodb will be preferred.