[openstack-dev] [juju charms] How to configure glance charm for specific cnider backend?
andrey.mp at gmail.com
Tue Aug 2 15:52:28 UTC 2016
James, thank you for your answer.
I'll file bug to glance - but in current releases glance-charm have to
do it himself, right?
I'm not sure that I'm correctly understand your question.
I suppose that deployment will have glance and cinder on different machines.
Also there will be one relation between cinder and glance to configure
glance to store images in cinder.
Other steps are optional -
If cinder is used specific backend that needs additional configuration
- then it can be done via storage-backend relation (from subordinate
If this backend needs to configure glances' filters or glance's config
- then it should be done via any subordinate charm to glance (but
glance doesn't have such relations now).
Due to these suggestions I think that additional relation needs to be
added to glance to allow connecting charms (with installation in the
same container as glance).
On Tue, Aug 2, 2016 at 6:15 PM, James Page <james.page at ubuntu.com> wrote:
> Hi Andrey
> 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
> specific comments.
>> 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:
> or use:
> ubuntu-bug glance-common
> 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?
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev