Hi Goutham,

Thanks for your response.

It is correct that I have volumes that are using the volume type I want to modify. If I understand correctly, modifying volumes types is not possible as long as there are volumes using the volume type.

Renaming the volume type and creating a new volume type won't work I guess. Since the backend name in the cinder configuration will be changed, the volumes that are using the renamed volume type won't able to find the backend and will fail, not?

I would have the backend named "ssdvolumes" in the cinder configuration. The new volume type would have the correct backend name (ssdvolumes) but the renamed volume type would still have "ssd" as its backend name.

Kind regards, Sinan

Op 7 november 2019 om 20:47 schreef Goutham Pacha Ravi gouthampravi@gmail.com:

Hey Sinat,

The error message suggests that you have volumes that use the volume type

you're modifying. If yes, with cinder API, since the Rocky release [1], you cannot modify volume types that are currently in use. The original design for cinder volume types was that they were always mutable - and changes to existing volume types didn't affect pre-existing volumes. However, this behavior was modified in the Ocata release [2], and finally removed in the Rocky release.

One of your options is to also rename the existing volume type and create

a new one if you'd like, with the original name.

[1]

https://docs.openstack.org/releasenotes/cinder/rocky.html#relnotes-13-0-0-st... [2] https://review.opendev.org/#/c/440680/

On Thu, Nov 7, 2019 at 12:33 AM Sinan Polat <sinan@turka.nl

mailto:sinan@turka.nl > wrote:

    > > 

...

    Hi,

    I am using Ceph as the backend for Cinder. Within Ceph we have

defined 2 RBD pools (ssdvolumes, sasvolumes). In OpenStack I created 2 Volume Types (ssd, sas). Each Volume Type has property "volume_backend_name='tripleo_ceph_<ssd|sas>'".

    In the Cinder configuration I have the following backends

configured:

    [tripleo_ceph_ssd]
    backend_host=hostgroup
    volume_backend_name=tripleo_ceph_ssd
    volume_driver=cinder.volume.drivers.rbd.RBDDriver
    rbd_ceph_conf=/etc/ceph/ceph.conf
    rbd_user=openstack
    rbd_pool=ssdvolumes

    [tripleo_ceph_sas]
    backend_host=hostgroup
    volume_backend_name=tripleo_ceph_sas
    volume_driver=cinder.volume.drivers.rbd.RBDDriver
    rbd_ceph_conf=/etc/ceph/ceph.conf
    rbd_user=openstack
    rbd_pool=sasvolumes

    As you might have noticed, the backend name (tripleo_ceph_ssd) and

the RBD pool name (ssdvolumes, not ssd) does not match. So far, we do not have any problems. But I want to correct the names and I do not want to have the mismatch anymore.

    So I want to change the value of key volume_backend_name for both

Volume Types (tripleo_ceph_ssd => tripleo_ceph_ssdvolumes).

    I tried the following:
    $ openstack volume type show 80cb25ff-376a-4483-b4f7-d8c75839e0ce
    +--------------------+----------------------------------------+
    | Field | Value |
    +--------------------+----------------------------------------+
    | access_project_ids | None |
    | description | |
    | id | 80cb25ff-376a-4483-b4f7-d8c75839e0ce |
    | is_public | True |
    | name | ssd |
    | properties | volume_backend_name='tripleo_ceph_ssd' |
    | qos_specs_id | None |
    +--------------------+----------------------------------------+
    $


    $ openstack volume type set --property

volume_backend_name='tripleo_ceph_ssdvolumes' 80cb25ff-376a-4483-b4f7-d8c75839e0ce Failed to set volume type property: Volume Type is currently in use. (HTTP 400) (Request-ID: req-5efaa5b7-910f-4802-8494-3115cfc4ab93) Command Failed: One or more of the operations failed $

    How to solve my problem?

    Thanks!

    Sinan

> 

Hi Sean,

Currently: Ceph RBD pool name = ssdvolumes. Volume Type name = ssd Volume Type metadata pointing to backend name ssd Backend name in Cinder conf = ssd

New situation: Backend name in Cinder conf will be ssdvolumes, and not ssd anymore.

Since it seems it is not possible to modify a Volume Type when in use by volumes, I do not see other options.

Sinan

Op 7 nov. 2019 om 23:48 heeft Sean McGinnis sean.mcginnis@gmx.com het volgende geschreven:

Hi Sinan,

Changing a backend name is generally not recommended. It is only an internal detail seen by administrators anyway, so I'm not sure it would be worth the effort to try to change it just to add "volumes" to the end.

Sean

Sent: Thursday, November 07, 2019 at 2:58 PM From: "Sinan Polat" sinan@turka.nl To: "Goutham Pacha Ravi" gouthampravi@gmail.com Cc: "OpenStack Discuss" openstack-discuss@lists.openstack.org Subject: Re: Change Volume Type, but in use Hi Goutham,

Thanks for your response.

It is correct that I have volumes that are using the volume type I want to modify. If I understand correctly, modifying volumes types is not possible as long as there are volumes using the volume type.

Renaming the volume type and creating a new volume type won't work I guess. Since the backend name in the cinder configuration will be changed, the volumes that are using the renamed volume type won't able to find the backend and will fail, not?

I would have the backend named "ssdvolumes" in the cinder configuration. The new volume type would have the correct backend name (ssdvolumes) but the renamed volume type would still have "ssd" as its backend name.

Kind regards, Sinan

Op 7 november 2019 om 20:47 schreef Goutham Pacha Ravi gouthampravi@gmail.com:

Hey Sinat,

The error message suggests that you have volumes that use the volume type you're modifying. If yes, with cinder API, since the Rocky release [1], you cannot modify volume types that are currently in use. The original design for cinder volume types was that they were always mutable - and changes to existing volume types didn't affect pre-existing volumes. However, this behavior was modified in the Ocata release [2], and finally removed in the Rocky release.

One of your options is to also rename the existing volume type and create a new one if you'd like, with the original name.

[1] https://docs.openstack.org/releasenotes/cinder/rocky.html#relnotes-13-0-0-st... [2] https://review.opendev.org/#/c/440680/

On Thu, Nov 7, 2019 at 12:33 AM Sinan Polat sinan@turka.nl wrote: Hi,

I am using Ceph as the backend for Cinder. Within Ceph we have defined 2 RBD pools (ssdvolumes, sasvolumes). In OpenStack I created 2 Volume Types (ssd, sas). Each Volume Type has property "volume_backend_name='tripleo_ceph_<ssd|sas>'".

In the Cinder configuration I have the following backends configured:

[tripleo_ceph_ssd] backend_host=hostgroup volume_backend_name=tripleo_ceph_ssd volume_driver=cinder.volume.drivers.rbd.RBDDriver rbd_ceph_conf=/etc/ceph/ceph.conf rbd_user=openstack rbd_pool=ssdvolumes

[tripleo_ceph_sas] backend_host=hostgroup volume_backend_name=tripleo_ceph_sas volume_driver=cinder.volume.drivers.rbd.RBDDriver rbd_ceph_conf=/etc/ceph/ceph.conf rbd_user=openstack rbd_pool=sasvolumes

As you might have noticed, the backend name (tripleo_ceph_ssd) and the RBD pool name (ssdvolumes, not ssd) does not match. So far, we do not have any problems. But I want to correct the names and I do not want to have the mismatch anymore.

So I want to change the value of key volume_backend_name for both Volume Types (tripleo_ceph_ssd => tripleo_ceph_ssdvolumes).

I tried the following: $ openstack volume type show 80cb25ff-376a-4483-b4f7-d8c75839e0ce +--------------------+----------------------------------------+ | Field | Value | +--------------------+----------------------------------------+ | access_project_ids | None | | description | | | id | 80cb25ff-376a-4483-b4f7-d8c75839e0ce | | is_public | True | | name | ssd | | properties | volume_backend_name='tripleo_ceph_ssd' | | qos_specs_id | None | +--------------------+----------------------------------------+ $

$ openstack volume type set --property volume_backend_name='tripleo_ceph_ssdvolumes' 80cb25ff-376a-4483-b4f7-d8c75839e0ce Failed to set volume type property: Volume Type is currently in use. (HTTP 400) (Request-ID: req-5efaa5b7-910f-4802-8494-3115cfc4ab93) Command Failed: One or more of the operations failed $

How to solve my problem?

Thanks!

Sinan

Hi,

Sorry for not being totally clear. The cluster is managed by TripleO. After each deployment/update, the cinder configuration is updated with incorrect names. Currently we correct it manually in the cinder configuration. So it is not only aesthetic.

Sinan

Op 11 nov. 2019 om 14:48 heeft Gorka Eguileor geguileo@redhat.com het volgende geschreven:

...

On 07/11, Sinan Polat wrote: Hi,

I am using Ceph as the backend for Cinder. Within Ceph we have defined 2 RBD pools (ssdvolumes, sasvolumes). In OpenStack I created 2 Volume Types (ssd, sas). Each Volume Type has property "volume_backend_name='tripleo_ceph_<ssd|sas>'".

In the Cinder configuration I have the following backends configured:

[tripleo_ceph_ssd] backend_host=hostgroup volume_backend_name=tripleo_ceph_ssd volume_driver=cinder.volume.drivers.rbd.RBDDriver rbd_ceph_conf=/etc/ceph/ceph.conf rbd_user=openstack rbd_pool=ssdvolumes

[tripleo_ceph_sas] backend_host=hostgroup volume_backend_name=tripleo_ceph_sas volume_driver=cinder.volume.drivers.rbd.RBDDriver rbd_ceph_conf=/etc/ceph/ceph.conf rbd_user=openstack rbd_pool=sasvolumes

As you might have noticed, the backend name (tripleo_ceph_ssd) and the RBD pool name (ssdvolumes, not ssd) does not match. So far, we do not have any problems. But I want to correct the names and I do not want to have the mismatch anymore.

So I want to change the value of key volume_backend_name for both Volume Types (tripleo_ceph_ssd => tripleo_ceph_ssdvolumes).

Hi,

I agree with Sean, I wouldn't change it since this is only aesthetic.

Having said that, there's always a way to do most things, even if it's NOT RECOMMENDED:

• Update cinder.conf
• Get the volume type id for the 2 volume types to change
• Stop cinder services
• Go into the DB and manually update the volume types changes in the

"volume_type_extra_specs" table filtering by the volume_type_id and the key "volume_backend_name" and setting the new "value".

• Use the "cinder-manage volume update_host" to update existing volumes

to the new backend (you could also do this directly in the DB).

• Start cinder services
• Remove the old service from the DB (they appear as down now) using the

"cinder-manage service remove" command.

Cinder-manage docs: https://docs.openstack.org/cinder/latest/cli/cinder-manage.html

Regards, Gorka.

...

I tried the following: $ openstack volume type show 80cb25ff-376a-4483-b4f7-d8c75839e0ce +--------------------+----------------------------------------+ | Field | Value | +--------------------+----------------------------------------+ | access_project_ids | None | | description | | | id | 80cb25ff-376a-4483-b4f7-d8c75839e0ce | | is_public | True | | name | ssd | | properties | volume_backend_name='tripleo_ceph_ssd' | | qos_specs_id | None | +--------------------+----------------------------------------+ $

$ openstack volume type set --property volume_backend_name='tripleo_ceph_ssdvolumes' 80cb25ff-376a-4483-b4f7-d8c75839e0ce Failed to set volume type property: Volume Type is currently in use. (HTTP 400) (Request-ID: req-5efaa5b7-910f-4802-8494-3115cfc4ab93) Command Failed: One or more of the operations failed $

How to solve my problem?

Thanks!

Sinan