Re: [openstack-dev] Cinder multiple backends

[Fox, Kevin M]

In the mean time, the package list you have listed below is rather small. 
Easiest thing might be to just add them all to the docker/base/Dockerfile 

Thanks,
Kevin

From: Ryan Hallisey [rhall...@redhat.com]
Sent: Monday, June 20, 2016 6:47 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [kolla]  Cinder multiple backends

Hey Carlos,

The work to enable you to do this is in progress.  Kolla needs to refactor the 
way the Dockerfiles
are templated in order to create additional flexibility.

You can follow the work here: 
https://blueprints.launchpad.net/kolla/+spec/third-party-plugin-support

Thanks,
Ryan

- Original Message -
From: "Carlos Cesario" 
To: "OpenStack Development Mailing List (not for usage questions)" 

Sent: Monday, June 20, 2016 9:29:27 AM
Subject: [openstack-dev]  [kolla]  Cinder multiple backends

Hi folks,

It seems that Kolla does nos provide option to enable multiple backends in 
Cinder config.

Currently in my deploy/setup I needed enable the Storwize Cinder driver - 
http://docs.openstack.org/mitaka/config-reference/block-storage/drivers/ibm-storwize-svc-driver.html
 -
and to this I added into /etc/kolla/config/cinder.conf my configs

  [DEFAULT]
  default_volume_type = ibm

  [ibm]
  
volume_driver=cinder.volume.drivers.ibm.storwize_svc.storwize_svc_fc.StorwizeSVCFCDriver
  san_ip=xxx.xx.xx.xx
  san_login=superuser
  san_password=mypass
  san_ssh_port=22
  storwize_svc_volpool_name=myPool
  volume_backend_name=ibm
  verbose = True
  debug = True


And I changed manually the file 
/var/src/kolla-master/ansible/roles/cinder/templates/cinder.conf.j2 as well.

But for the driver works correctly, it was needed install manually some 
aditional packs.

$ apt-get install sysfsutils sg3-utils on cinder-volume container
$ apt-get install multipath-tools sysfsutils on nova-compute container

Is there any doc/spec to create a automatic process for this ? Could someone 
give us details how is the best way to make it "automatized" !?



Best regards,

- Carlos
__
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 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 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] [cinder]Multiple backends

[한승진]

You sould define the volume type related to volume backends.

For example, you set lvm backend driver in your cinder.conf like below.

enabled_backends=lvmdriver-1
[lvmdriver-1]
volume_group=cinder-volumes
volume_driver=cinder.volume.drivers.lvm.LVMISCSIDriver
volume_backend_name=LVM

you set your volume type in order to connect you lvmdriver-1 backend In
your cinder management.

# cinder type-create lvm
# cinder type-key volume_backend_name=LVM

For creating lvm type volume, you specify volume type when you create
volume.

# volume create 1 --volume-type lvm

Cinder can find volume backend using volume-type and backend connectivity.



2014-02-17 15:24 GMT+09:00 Subramanian subramanian.neelakan...@gmail.com:

 I think you should look at the cinder scheduler code that selects a host
 based on the volume type.
 https://github.com/openstack/cinder/tree/master/cinder/scheduler.

 BTW, cinder dev tend to hang out on #openstack-cinder channel.

 Thanks,
 Subbu


 On Mon, Feb 17, 2014 at 11:35 AM, iKhan ik.ibadk...@gmail.com wrote:

 Hi All,

 I'm just curious on how the manager.py is choosing backend while creating
 volume, I know volume type is set but where is this being processed?

 I am sorry if this is a basic question, but didn't got any help from
 #openstack-dev IRC channel so was left without option to post here.

 --
 Thanks,
 IK

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cinder]Multiple backends

[iKhan]

Hi All,

I'm just curious on how the manager.py is choosing backend while creating
volume, I know volume type is set but where is this being processed?

I am sorry if this is a basic question, but didn't got any help from
#openstack-dev IRC channel so was left without option to post here.

-- 
Thanks,
IK
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [cinder]Multiple backends

[Subramanian]

I think you should look at the cinder scheduler code that selects a host
based on the volume type.
https://github.com/openstack/cinder/tree/master/cinder/scheduler.

BTW, cinder dev tend to hang out on #openstack-cinder channel.

Thanks,
Subbu


On Mon, Feb 17, 2014 at 11:35 AM, iKhan ik.ibadk...@gmail.com wrote:

 Hi All,

 I'm just curious on how the manager.py is choosing backend while creating
 volume, I know volume type is set but where is this being processed?

 I am sorry if this is a basic question, but didn't got any help from
 #openstack-dev IRC channel so was left without option to post here.

 --
 Thanks,
 IK

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev