roduce it
> on devstack, will report you back.
>
> Regards..
> Salman
>
>
>
>
> --
> *From:* Joe Topjian [j...@topjian.net]
> *Sent:* Friday, December 11, 2015 7:16 PM
> *To:* Salman Toor
> *Cc:* openstack-operators@lists.open
: openstack-operators@lists.openstack.org
Subject: Re: [Openstack-operators] Cinder API with multiple regions not working.
Hi Salman,
I'm stumped.
I was able to confirm that Keystone acts a little differently when you have
multiple regional endpoints connected to the same "service
Hi Salman,
I'm stumped.
I was able to confirm that Keystone acts a little differently when you have
multiple regional endpoints connected to the same "service_name" and
"service_type" than if you have multiple regional endpoints, each with
their own "service_name" but same "service_type"'s.
For
Hi,
Still no luck. I have remove the “-“ from the names.
[root@controller: ~/openstack] # openstack service list
+--+---+--+
| ID | Name | Type |
+--+
Hi Salman,
This has turned into a bit of fun -- I'm seeing a lot of wacky things.
First, I'm pretty this issue is local to multi-regions and doesn't have to
do with having both Cinder v1 and v2 in the Keystone catalog. I changed my
catalog to only have Cinder v2 and I still see multi-region issue
Hi Joe,
Thanks for your reply, yes Me and Marco are working together.
I have tried to used
os_region_name = RegionOne
both in cinder.conf and nova.conf but no luck so far. But the error message is
a bit different. It seems like now the system is recognising the region.
2015-12-10 09:32:54.6
Hi Salman,
Someone mentioned this same issue yesterday in relation to Terraform (maybe
a colleague of yours?), so given the two occurrences, I thought I'd look
into this.
I have a Liberty environment readily available, so I created a second set
of volume and volumev2 endpoints for a fictional reg
Hi,
I am using Kilo release on CentOS. We have recently enabled multiple regions
and it seems that Cinder have some problems with multiple endpoints.
Thinks are working fine with nova but cinder is behaving strange. Here are my
endpoints
[root@controller: ~] # openstack service list
+--
