tthias,
Did you try to use OS_AUTH_TYPE=noauth environment variable or add
'--os-auth-type=noauth' option to the cinderclient?
auth_strategy option should be set in cinder.con for API access too
Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/
On Fri, Oct 12, 20
OS_AUTH_TYPE=noauth environment variable or add
'--os-auth-type=noauth' option to the cinderclient?
auth_strategy option should be set in cinder.con for API access too
Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/
On Fri, Oct 12, 2018 at 3:32 PM Matthias Leopold
<mailto:
Hi,
my standalone Pike Cinder installation works perfectly with
"auth_strategy = keystone" and i can use cinderclient CLI to interact
with it.
Now i want to temporarily test it with "auth_strategy = noauth".
I followed
https://docs.openstack.org/python-cinderclient/pike/user/no_auth.html,
b
Hi,
I'm trying to setup Cinder as a standalone service with Docker using the
blockbox system (contrib/blockbox in the Cinder source distribution). I
was inspired by this manual:
https://thenewstack.io/deploying-cinder-stand-alone-storage-service/.
This works quite well with Cinder’s noauth o
On 17 Nov 2017, at 13:55, Matthias Leopold
wrote:
Hi,
we are running a Cinder Pike instance with Ceph (luminous) backend for use with oVirt (not
openstack). We are experiencing the "cinder-volume causes high CPU load" issue. In Cinder
11.0.0 we could successfully apply the fix me
Hi,
we are running a Cinder Pike instance with Ceph (luminous) backend for
use with oVirt (not openstack). We are experiencing the "cinder-volume
causes high CPU load" issue. In Cinder 11.0.0 we could successfully
apply the fix mentioned in
https://ask.openstack.org/en/question/110709/ocata-c