Hi Mohammed I'm trying to use the keystone of the region that magnum belongs to. I have Keystone in several regions and am using duplicate Keystone DB. 2024년 2월 9일 (금) 00:12, Mohammed Naser <mnaser@vexxhost.com>님이 작성:
Hey Seongsoo,
I don't think it's supported because most of the time, I believe users end up having a single keystone even in a multiple region environment.
Are you looking for this in order or Keystone to use the closer Keystone?
Thanks Mohammed ------------------------------ *From:* Seongsoo Cho <ppiyakk2@printf.kr> *Sent:* February 8, 2024 7:17 AM *To:* OpenStack Discuss <openstack-discuss@lists.openstack.org> *Cc:* dongjin.hong@nhn.com <dongjin.hong@nhn.com> *Subject:* [magnum] Is magnum support region_name in keystone auth config?
You don't often get email from ppiyakk2@printf.kr. Learn why this is important <https://aka.ms/LearnAboutSenderIdentification> Hi magnum team.
It seems that a magnum does not support region_name which is in the keystone_auth and keystone_authtoken section in magnum conf.
The internal keystone client of keystoneauth1 only uses the lowest UUID of endpoints for keystone url. [1]
And also KeystoneClientV3 's get_auth[2] and get_legacy_auth[3] also don't support region_name as an argument.
So, My question is how can I make magnum only use the keystone URL written in the config?
Best regards Seongsoo Cho
[1] https://github.com/openstack/keystoneauth/blob/master/keystoneauth1/access/s... [2] https://github.com/openstack/magnum/blob/master/magnum/common/keystone.py#L7... [3] https://github.com/openstack/magnum/blob/master/magnum/common/keystone.py#L1... -- Seongsoo Cho OpenStack Korea User Group / Community Leader IRC #seongsoocho