cinder + Unity
Albert Shih
Albert.Shih at obspm.fr
Mon Apr 19 18:12:56 UTC 2021
Hi everyone,
I'm a total newbie with openstack, currently I'm trying to put a POC with a
Unity storage element, 4 computes, and few servers (cinder, keystone,
glance, neutron, nova, placement and horizon).
I think my keystone, glance, placement are working (at least they past the
test).
Currently I'm trying to make cinder working with my Unity (480), the
objectif are to use iSCSI.
Here the configuration of my /etc/cinder/cinder.conf
[DEFAULT]
rootwrap_config = /etc/cinder/rootwrap.conf
api_paste_confg = /etc/cinder/api-paste.ini
iscsi_helper = tgtadm
volume_name_template = volume-%s
volume_group = cinder-volumes
verbose = True
auth_strategy = keystone
state_path = /var/lib/cinder
lock_path = /var/lock/cinder
volumes_dir = /var/lib/cinder/volumes
enabled_backends = unity
transport_url = rabbit://openstack:XXXXXX@amqp-cloud.private.FQDN/openstack
auth_strategy = keystone
debug = True
verbose = True
[database]
connection = mysql+pymysql://cinder:XXXXXXX@mariadb-cloud.private.FQDN/cinder
[keystone_authtoken]
www_authenticate_uri = http://keystone.private.FQDN:5000/v3
auth_url = http://keystone.private.FQDN:5000
identity_uri = http://keystone.private.FQDN:5000
memcached_servers = memcached-cloud.private.FQDN:11211
auth_type = password
project_domain_name = default
user_domain_name = default
project_name = service
username = cinder
password = XXXXXX
[oslo_concurrency]
lock_path = /var/lib/cinder/tmp
[unity]
# Storage protocol
storage_protocol = iSCSI
# Unisphere IP
san_ip = onering-remote.FQDN
# Unisphere username and password
san_login = openstack
san_password = "XXXXX"
# Volume driver name
volume_driver = cinder.volume.drivers.dell_emc.unity.Driver
# backend's name
volume_backend_name = Unitiy_ISCSI
unity_io_ports = *_enp1s0
unity_storage_pool_names = onering
When I'm trying to create a storage through a
openstack volume create volumetest --type thick_volume_type --size 100
I don't even see (with tcpdump) the cinder server trying to connect to
onering-remote.FQDN
Inside my /var/log/cinder/cinder-scheduler.log I have
2021-04-19 18:06:56.805 21315 INFO cinder.scheduler.base_filter [req-4808cc9d-b9c3-44cb-8cae-7503db0b0256 f5e5c9ea20064b17851f07c276d71aee b1d58ebae6b84f7586ad63b94203d7ae - - -] Filtering removed all hosts for the request with volume ID '06e5f07d-766f-4d07-b3bf-6153a2cf6abd'. Filter results: AvailabilityZoneFilter: (start: 0, end: 0), CapacityFilter: (start: 0, end: 0), CapabilitiesFilter: (start: 0, end: 0)
2021-04-19 18:06:56.806 21315 WARNING cinder.scheduler.filter_scheduler [req-4808cc9d-b9c3-44cb-8cae-7503db0b0256 f5e5c9ea20064b17851f07c276d71aee b1d58ebae6b84f7586ad63b94203d7ae - - -] No weighed backend found for volume with properties: {'id': '5f16fc1f-76ff-41ee-8927-56925cf7b00f', 'name': 'thick_volume_type', 'description': None, 'is_public': True, 'projects': [], 'extra_specs': {'provisioning:type': 'thick', 'thick_provisioning_support': 'True'}, 'qos_specs_id': None, 'created_at': '2021-04-19T15:07:09.000000', 'updated_at': None, 'deleted_at': None, 'deleted': False}
2021-04-19 18:06:56.806 21315 INFO cinder.message.api [req-4808cc9d-b9c3-44cb-8cae-7503db0b0256 f5e5c9ea20064b17851f07c276d71aee b1d58ebae6b84f7586ad63b94203d7ae - - -] Creating message record for request_id = req-4808cc9d-b9c3-44cb-8cae-7503db0b0256
2021-04-19 18:06:56.811 21315 ERROR cinder.scheduler.flows.create_volume [req-4808cc9d-b9c3-44cb-8cae-7503db0b0256 f5e5c9ea20064b17851f07c276d71aee b1d58ebae6b84f7586ad63b94203d7ae - - -] Failed to run task cinder.scheduler.flows.create_volume.ScheduleCreateVolumeTask;volume:create: No valid backend was found. No weighed backends available: cinder.exception.NoValidBackend: No valid backend was found. No weighed backends available
It seem (for me) cinder don't try to use unity....
Any help ?
Regards
--
Albert SHIH
Observatoire de Paris
Heure local/Local time:
Mon Apr 19 08:01:37 PM CEST 2021
More information about the openstack-discuss
mailing list