[openstack-ansible] Installing Third-Party drivers into the Cinder-Volume container during playbook execution

Henry Bonath henry at thebonaths.com
Mon Jun 3 03:45:35 UTC 2019

I think the idea here, at least for me, would be to have it rolled
into the deployment automatically - in a similar fashion to how
horizon themes are deployed within Openstack-Ansible.
Obviously having this specific driver in the tree would solve my
specific issue, but I don't know how many more third party Cinder
drivers which are not packaged into the tree people are deploying
these days.

My question for the community is simply finding out if this mechanism
exists already.

On Thu, May 30, 2019 at 11:11 AM Jean-Philippe Evrard
<jean-philippe at evrard.me> wrote:
> On Tue, May 28, 2019, at 04:10, Henry Bonath wrote:
> > Hello, I asked this into IRC but I thought this might be a more
> > appropriate place to ask considering the IRC channel usage over the
> > weekend.
> >
> > If I wanted to deploy a third party driver along with my Cinder-Volume
> > container, is there a built-in mechanism for doing so? (I am
> > specifically wanting to use: https://github.com/iXsystems/cinder)
> >
> >   I am able to configure a cinder-backend in the
> > "openstack_user_config.yml" file which works perfectly if I let it
> > fail during the first run, then copy the driver into the containers
> > and run "os-cinder-install.yml" a second time.
> >
> > I've found that you guys have built similar stuff into the system
> > (e.g. Horizon custom Theme installation via .tgz) and was curious if
> > there is a similar mechanism for Cinder Drivers that may be
> > undocumented.
> >
> > http://paste.openstack.org/show/752132/
> > This is an example of my working config, which relies on the driver
> > being copied into the
> > /openstack/venvs/cinder-19.x.x.x/lib/python2.7/site-packages/cinder/volume/drivers/ixsystems/
> > folder.
> >
> > Thanks in advance!
> >
> >
> I suppose the community would be okay to have this in tree, so no need for a third party system here (and no need to maintain this on your own, separately). However... if it's just about copying the content of this repo, did you think of packaging this, and publish it to pypi ? This way you could just pip install the necessary package into your cinder venv...
> Regards,
> Jean-Philippe Evrard (evrardjp)

More information about the openstack-discuss mailing list