Missing volume encryption type create

[Jesse Keating]

python-cinderclient has encryption-type-create

usage: cinder encryption-type-create [--cipher <cipher>]
                                     [--key_size <key_size>]
                                     [--control_location <control_location>]
                                     <volume_type> <provider>

Creates encryption type for a volume type. Admin only.

Positional arguments:
  <volume_type> Name or ID of volume type.
  <provider> The class that provides encryption support. For
                        example, a volume driver class path.

Optional arguments:
  --cipher <cipher> The encryption algorithm and mode. For example, aes-
                        xts-plain64. Default=None.
  --key_size <key_size>
                        Size of encryption key, in bits. For example, 128 or
                        256. Default=None.
  --control_location <control_location>
                        Notional service where encryption is performed. Valid
                        values are "front-end" or "back-end." For example,
                        front-end=Nova. Default is "front-end."

[Dean Troyer (dtroyer)]

Wait. What? The REST API has an endpoint that takes a Python class path as an argument? That is config and is just broken. Unless this is config API in which case maybe an OSC plugin for config commands makes sense I'd rather not have users seeing things they will _never_use and admins will use once or twice.

[Jesse Keating (jesse-keating)]

Yeah, unfortunately there doesn't seem to be a way to express this in a configuration file for Cinder, it can only be done by using a call to the API. I could see this going the way of cinder_manage or something like that.

I want to move our stack over to openstackclient for all the things we do to interact with the stack, this is just one of the barriers, for the clusters where we do implement encryption of clusters.

Is openstackclient never meant to be useful for cloud Admins?

[Dean Troyer (dtroyer)]

It is meant to be useful for admins (90% of Identity is admin-only after all), but this is a bit different in my mind. This is a cinder-manage command or a config file edit. If we're moving to API-driven config, well, ok, but I still think this particular bit is broken.

We have not come up with a usable method to test for admin-ness in the client to hide things like this. Imagine moving all of cinder-manage to OSC, doesn't really make sense as an integrated part IMHO but maybe an admin plugin.

Conceptually 'volume type create' is very similar so I suppose these should go together...

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/263254

[Steve Martinelli (stevemar)]

Automatically unassigning due to inactivity.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Steve Martinelli (<email address hidden>) on branch: master
Review: https://review.openstack.org/263254
Reason: abandoning due to inactivity

[David Rabel (rabel-b1)]

Should be fixed by https://review.openstack.org/#/c/414197/