Ask Your Question
0

Issues with extra spec capabilities:replication with volume types

asked 2014-12-14 15:31:35 -0600

harsh gravatar image

updated 2014-12-15 04:15:26 -0600

I think that this is a potential bug ,but I just wanted to confirm the below scenario :

I am facing the below error when I try to create a volume type with extra specs as capabilities:replication="<is> True" and create a volume of that type : 2014-12-14 21:16:39.552 2240 WARNING cinder.scheduler.filter_scheduler [req-2a663aee-b644-4610-be26-c797007d77f2 ae4ec04f42004f8ead92395b2f5cec36 58211a6f6af84395a46eff1551564eaa - - -] No weighed hosts found for volume with properties: {u'name': u'replication', u'qos_specs_id': None, u'deleted': False, u'created_at': u'2014-12-15T01:48:40.000000', u'updated_at': None, u'extra_specs': {u'volume_backend_name': u'ABCD_iSCSI_REP', u'capabilities:replication': u'<is>True'}, u'deleted_at': None, u'id': u'26dd8235-26df-4cf6-a5e4-b74b47bcd6cf'} 2014-12-14 21:16:39.561 2240 ERROR cinder.scheduler.flows.create_volume [req-2a663aee-b644-4610-be26-c797007d77f2 ae4ec04f42004f8ead92395b2f5cec36 58211a6f6af84395a46eff1551564eaa - - -] Failed to run task cinder.scheduler.flows.create_volume.ScheduleCreateVolumeTask;volume:create: No valid host was found. No weighed hosts available

Although I have two cinder host services running which are for two different backend configurations : [root@harsh cinder]# cinder-manage service list Binary Host Zone Status State Updated At cinder-scheduler harsh nova enabled :-) 2014-12-15 02:14:36 cinder-backup harsh nova enabled :-) 2014-12-15 02:14:35 cinder-volume harsh@abc-replica nova enabled :-) 2014-12-15 02:14:37 cinder-volume harsh@def-plain nova enabled :-) 2014-12-15 02:14:37

My cinder conf as per the backends :

Driver to use for volume creation (string value)

enabled_backends=abc-replica,def-plain [abc-replica] volume_driver=cinder.volume.drivers.xyz.iscsi.xyzISCSIDriver xyz_blocksize = 128K xyz_host = xxx.xxx.xxx.xxx xyz_iscsi_target_portal_port = 3260 xyz_password = xyz xyz_rest_port = xxxx xyz_rest_protocol = auto xyz_rrmgr_compression = 0 xyz_rrmgr_connections = 2 xyz_rrmgr_tcp_buf_size = 4096 xyz_sparse = True xyz_sparsed_volumes = True capabilities:replication='<is>True' volume_backend_name=xyz_iSCSI_REP

[def-plain] volume_driver=cinder.volume.drivers.xyz.iscsi.xyzISCSIDriver xyz_blocksize = 128K xyz_host = xxx.xxx.xxx.xxx xyz_iscsi_target_portal_port = 3260 xyz_password = xyz xyz_rest_port = xxxx xyz_rest_protocol = auto xyz_rrmgr_compression = 0 xyz_rrmgr_connections = 2 xyz_rrmgr_tcp_buf_size = 4096 xyz_sparse = True xyz_sparsed_volumes = True capabilities:replication='<is>True' volume_backend_name=xyz_iSCSI

I have two volume types configured with the following extra_specs : MariaDB [cinder]> select * from volume_types; +---------------------+------------+---------------------+---------+--------------------------------------+-------------+--------------+ | created_at | updated_at | deleted_at | deleted | id | name | qos_specs_id | +---------------------+------------+---------------------+---------+--------------------------------------+-------------+--------------+ | 2014-12-15 01:48:40 | NULL | NULL | 0 | 26dd8235-26df-4cf6-a5e4-b74b47bcd6cf | replication | NULL | | 2014-12-12 12:22:10 | NULL | NULL | 0 | fb192df7-27ea-43c7-9805-d3e81b53e5ac | replica2 | NULL | +---------------------+------------+---------------------+---------+--------------------------------------+-------------+--------------+

MariaDB [cinder]> select * from volume_type_extra_specs; +---------------------+---------------------+---------------------+---------+----+--------------------------------------+--------------------------+-------------------+ | created_at | updated_at | deleted_at | deleted | id | volume_type_id | key | value | +---------------------+---------------------+---------------------+---------+----+--------------------------------------+--------------------------+-------------------+ | 2014-12-12 12:22:46 | NULL | NULL | 0 | 13 | fb192df7-27ea-43c7-9805-d3e81b53e5ac | volume_backend_name | XYZ_iSCSI | | 2014-12-15 01:59:11 | NULL | NULL | 0 | 15 | 26dd8235-26df-4cf6-a5e4-b74b47bcd6cf | volume_backend_name | XYZ_iSCSI_REP | | 2014-12-15 02:11:09 | NULL | NULL | 0 | 17 | 26dd8235-26df-4cf6-a5e4-b74b47bcd6cf | capabilities:replication | <is>True | +---------------------+---------------------+---------------------+---------+----+--------------------------------------+--------------------------+-------------------+ 17 rows in set (0.00 sec)

MariaDB [cinder]>

I am unable to create a volume with volume type 'replication' but I can do it well with volume type 'replica2' and as per : https://bugs.launchpad.net/openstack-manuals/+bug/1360768 (https://bugs.launchpad.net/openstack-...) """ Cloud admin creates a volume type "replicated" with extra-specs: capabilities:replication=" True" Every volume created in type "replicated" has a copy on both backends. """

I should be able to create a volume with extra specs as capabilities:replication="<is> True" ,but as for me it is failing in the scheduler itself ,I understand it is too be handled by the backend driver but I think that scheduler ... (more)

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2014-12-15 00:46:13 -0600

Raj_Jadhav gravatar image

Can you update command used for volume replication support .

edit flag offensive delete link more

Comments

I am just trying to create a volume with volume types having extra specs :capabilities:replication=<is>True

harsh gravatar imageharsh ( 2014-12-15 07:14:10 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-12-14 15:31:35 -0600

Seen: 191 times

Last updated: Dec 15 '14