[openstack-dev] [juju charms] How to configure glance charm for specific cnider backend?
james.page at ubuntu.com
Tue Aug 2 15:15:33 UTC 2016
On Tue, 2 Aug 2016 at 15:59 Andrey Pavlov <andrey.mp at gmail.com> wrote:
> I need to add glance support via storing images in cinder instead of
> local files.
> (This works only from Mitaka version due to glance-store package)
> First step I've made here -
> This patchset adds ability to relate glance-charm to cinder-charm
> (it's similar to ceph/swift relations)
Looks like a good start, I'll comment directly on the review with any
> And also it configures glance's rootwrap - original glance package
> doesn't have such code
> I think that this is a bug in glance-common package - cinder and
> nova can do it themselves.
> And if someone point me to bugtracker - I will file the bug there.
Sounds like this should be in the glance package:
on an installed system.
> But main question is about additional configurations' steps -
> Some cinder backends need to store additional files in
> /etc/glance/rootwrap.d/ folder.
> I have two options to implement this -
> 1) relate my charm to glance:juju-info (it will be run on the same
> machine as glance)
> and do all work in this hook in my charm.
> 2) add one more relation to glance - like
> 'storage-backend:cinder-backend' in cinder.
> And write code in a same way - with ability to pass config options.
> I prefer option 2. It's more logical and more general. It will allow
> to configure any cinder's backend.
+1 the subordinate approach in cinder (and nova) works well; lets ensure
the semantics on the relation data mean its easy to restart the glance
services from the subordinate service if need be.
Taking this a step further, it might also make sense to have the relation
to cinder on the subordinate charm and pass up the data item to configure
glance to use cinder from the sub - does that make sense in this context?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev