Thursday, 2023-02-02

opendevreviewPolina Gubina proposed openstack/ansible-collections-openstack master: The following modules will be added: - vpn service - vpn ike policy - vpn ipsec policy  https://review.opendev.org/c/openstack/ansible-collections-openstack/+/87251609:08
eestjust to report back for the people trying to help me with my openstacksdk code not doing version detection earlier, it turns out the servers were not patched for https://opendev.org/openstack/nova/commit/1e907602e37fb55bbe5a20164db6d074f87369af16:28
eestso this explains why i got some things to work by configuring compute_api_version: "2.79" etc16:29
eestbut things seems to work well now16:29
gtemaeest - this is a great facepalm. I am through billions of similar things. I feel you ;-)16:31
eest:)16:34
umbSublimeQuestion about `openstack.connect()`. I have a clouds.yaml file that defines a cloud names 'pci' in that cloud I have multiple regions(my_region1, my_region2. If I set my envvars to OS_CLOUD=pci OS_REGION_NAME=my_region2. And run openstack.connect(), it loads the cloud properly, but ignores my OS_REGION_NAME instead using the first from the clouds.yaml file. Is this expected17:09
umbSublimebehaviour? Should I explicitely connect(region_name='my_region2') ?17:09
umbSublimeFor reference using those 2 envvars work as expected with using the openstackclient17:09
gtemaumbSublime: it is always recommended to be explicit. afair once sdk finds entry in clouds.yaml it does not merge env vars into it17:11
umbSublimegtema: good to know, since the envvar OS_CLOUD would need to read the config, I was expecting OS_REGION_NAME to be merged after. This appears to be how the openstackclient works. Would there be additional logic in the osc to handle this ?17:12
umbSublimegtema: I agree explicit is always better, but having openstack.connect() work as I was expecting saves me from adding logic to handle those from argparse (or other). 17:14
gtemayes, OSC is doing things bit differently17:14
umbSublimegtema: thanks)17:22
umbSublimeSimple work around for my specific usecase: openstack.connect(region_name=os.environ.get('OS_REGION_NAME', None)); c.current_location.region_name 17:23
gtemaor duplicating entry in clouds.yaml - afaik there are some clouds not really sharing identity between regions so you anyway need to use different user17:25
umbSublimeagreed, that's another solution. In my case however there are 25+ regions all with same auth.17:25
gtemaok, convinced17:26

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!