Merge lp:~gandelman-a/charms/precise/cinder/upgrade into lp:~openstack-charmers/charms/precise/cinder/ha-support
Proposed by
Adam Gandelman
Status: | Merged |
---|---|
Merged at revision: | 48 |
Proposed branch: | lp:~gandelman-a/charms/precise/cinder/upgrade |
Merge into: | lp:~openstack-charmers/charms/precise/cinder/ha-support |
Diff against target: |
183 lines (+88/-20) 3 files modified
hooks/cinder-common (+43/-0) hooks/cinder-hooks (+44/-19) revision (+1/-1) |
To merge this branch: | bzr merge lp:~gandelman-a/charms/precise/cinder/upgrade |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
James Page | Approve | ||
Adam Gandelman (community) | Needs Resubmitting | ||
Review via email: mp+164995@code.launchpad.net |
Description of the change
This adds the charm bits around upgrading Openstack releases.
Upgrading /w ceph relations still needs some testing / isn't perfect:
- When upgrading OS release, librbd1 needs upgrading as well (cinders use of the library isn't backward compatable)
- After upgrading librdb1, the remote ceph cluster may need upgrading as well?
Testing fine with local storage/iscsi.
To post a comment you must log in.
Borked syntax:
+ [[ -n "$ceph_ids"] && apt-get -y install librbd1
I'd also recommend that you upgrade ceph-common; it has a hard dependency on the newer version of librdb1 so will do the same thing (thats what we install in the _joined hook).
The problem you are hitting is that cinder determines ceph backend features by looking at the options from the rbd and ceph command line tools; if the backend is not upgraded first, then cinder will try to use features which are not supported by the backend ceph.
This sucks.