Open Stack

On 20/04, Albert Shih wrote:
> Le 20/04/2021 à 00:35:46+0530, Rajat Dhasmana a écrit
> Hi Rajat,
>
> >
> > This might be something to look at with the wrong spelling causing mismatch.
> >  
> >
> >       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)
> >
> >
> > This log mentions that no host is valid to pass the 3 filters in the scheduler.
> >  
> >
> >       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....
> >
> >
> >
> > The cinder-volume service is responsible for communicating with the backend and
> > this create request fails on scheduler only, hence no sign of it.
>
> Absolutly. I didn't known I need to install the cinder-volume, inside the
> docs it's seem the cinder-volume is for LVM backend. My bad.
>
> After installing the cinder-volume and
> >
> > Looking at the scheduler logs, there are a few things you can check:
> >
> > 1) execute ``cinder-manage service list`` command and check the status of
> > cinder-volume service if it's active or not. If it shows an X sign then check
> > in cinder-volume logs for any startup failure.
> > 2) Check the volume type properties and see if ``volume_backend_name`` is set
> > to the right value i.e. Unitiy_ISCSI (which looks suspicious because the
> > spelling is wrong and there might be a mismatch somewhere)
>
> changing through openstack volume type I was able to create a volume on my
> Unity storage unit.
>
> I'm not sure it's working perfectly because I still don't have nova and
> neutron running.

Hi,

If you can create a volume in the array then you have confirmed that the
control plane connection works.

To do a preliminary check of the data plane connection without needing
nova, you can create a cinder volume from a glance image.

That operation will ensure that the volume can be exported an mapped
(control plane operation), that the host can connect via iSCSI to the
volume, that cinder connects to glance correctly, and that it can do I/O
on the connected volume.

Cheers,
Gorka.


>
> But now I'm going to configure nova and neutron.
>
> >
> > Also it's good to mention the openstack version you're using since the code
> > changes every cycle and it's hard to track the issues with every release.
>
> Sorry. I will do that next time.
>
> Thanks you very much.
> --
> Albert SHIH
> Observatoire de Paris
> xmpp: jas at obspm.fr
> Heure local/Local time:
> Tue Apr 20 03:32:01 PM CEST 2021
>