Re: [openstack-dev] [juju charms] How to configure glance charm for specific cnider backend?
Hi Andrey On Wed, 3 Aug 2016 at 14:35 Andrey Pavlovwrote: > Instead of adding one more relation to glance, I can relate my charm to > new relation 'cinder-volume-service' > almost > > So there is no more changes in the glance charm. > And additional in my charm will be - > > metadata.yaml - > > > > > *subordinate: trueprovides: image-backend:interface: cinderscope: > container* > Almost - the interface type should be something like 'glance-backend' matching the type of the container scoped interface we'd need to add to the glance charm. provides: image-backend: interface: glance-backend scope: container The glance charm needs to interrogate the data presented by the subordinate charm - I'd suggest one of the data items is 'cinder-backend=True|False' in which case the glance charm can then set the required configuration option in the glance-api.conf file (instead of doing that via a relation to cinder as you proposed in your original changes to glance). > and then I can relate my charm to glance (and my charm will be installed > in the same container as glance, so I can configure OS) > *juju add-relation glance:cinder-volume-service > scaleio-openstack:image-backend* > > This option works for me - I don't need to add something to glance config. > I'm only need to add files to /etc/glance/rootwrap.d/ > and this option allows to do it. > I think the experience would be something like: *juju add-relation glance:image-backend scaleio-openstack:image-backend* based on my feedback above. A relation to cinder might not be required at-all if all glance needs to know is 'use cinder' rather than any other additional data such as the location of the cinder-api services etc.. As you state - the scaleio-openstack charm can install the required filters to /etc/glance/rootwrap.d - which is great as it moves the scaleio specific bits into a specific charm for scaleio (which I like), rather than overloading and increasing the complexity of the core glance charm. > I've made additional review - https://review.openstack.org/#/c/350565/ > Looking today - I think we can refine things via the review if the overall design intent is agreed here. Thanks for your work on this feature! James __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [juju charms] How to configure glance charm for specific cnider backend?
On Tue, 2 Aug 2016 at 16:54 Andrey Pavlovwrote: > James, thank you for your answer. > No problem. I'll file bug to glance - but in current releases glance-charm have to > do it himself, right? > We should be able to add the required bits using an Ubuntu SRU - lets raise the bug and see exactly what needs to be done, and then we can decide whether the charm workaround is still required. I'm not sure that I'm correctly understand your question. > I suppose that deployment will have glance and cinder on different > machines. > yes - principle charms should typically be deployed in their own units, as the assume ownership over the filesystem. > Also there will be one relation between cinder and glance to configure > glance to store images in cinder. > ack 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 > charm). > 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). > No - we'd need to add a container scoped 'image-backend' relation to glance, allowing a subordinate to be deployed with glance to install the required rootwrap configuration, dependencies etc... You next email covers that - so I'll respond on that there. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [juju charms] How to configure glance charm for specific cnider backend?
Hi, Maybe I understood this option - Instead of adding one more relation to glance, I can relate my charm to new relation 'cinder-volume-service' So there is no more changes in the glance charm. And additional in my charm will be - metadata.yaml - *subordinate: trueprovides: image-backend:interface: cinderscope: container* and then I can relate my charm to glance (and my charm will be installed in the same container as glance, so I can configure OS) *juju add-relation glance:cinder-volume-service scaleio-openstack:image-backend* This option works for me - I don't need to add something to glance config. I'm only need to add files to /etc/glance/rootwrap.d/ and this option allows to do it. I've made additional review - https://review.openstack.org/#/c/350565/ But I don't need it :) Should I abandon it or not? On Tue, Aug 2, 2016 at 6:15 PM, James Pagewrote: > Hi Andrey > > On Tue, 2 Aug 2016 at 15:59 Andrey Pavlov 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) >> > > OK > > >> First step I've made here - >> https://review.openstack.org/#/c/348336/ >> 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: > > https://bugs.launchpad.net/ubuntu/+source/glance/+filebug > > 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? > > Cheers > > James > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Kind regards, Andrey Pavlov. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [juju charms] How to configure glance charm for specific cnider backend?
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 charm). 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 Pagewrote: > Hi Andrey > > On Tue, 2 Aug 2016 at 15:59 Andrey Pavlov 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) > > > OK > >> >> First step I've made here - >> https://review.openstack.org/#/c/348336/ >> 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: > > https://bugs.launchpad.net/ubuntu/+source/glance/+filebug > > 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? > > Cheers > > James > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Kind regards, Andrey Pavlov. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [juju charms] How to configure glance charm for specific cnider backend?
Hi Andrey On Tue, 2 Aug 2016 at 15:59 Andrey Pavlovwrote: > 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) > OK > First step I've made here - > https://review.openstack.org/#/c/348336/ > 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: https://bugs.launchpad.net/ubuntu/+source/glance/+filebug 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? Cheers James __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [juju charms] How to configure glance charm for specific cnider backend?
Hi All, 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 - https://review.openstack.org/#/c/348336/ This patchset adds ability to relate glance-charm to cinder-charm (it's similar to ceph/swift relations) 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. ) 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. But I prefer to know community opinion before I start to implement this. -- Kind regards, Andrey Pavlov. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev