Wednesday, 2017-08-30

*** rods has quit IRC00:18
openstackgerritSam Yaple proposed openstack-infra/shade master: Allow domain_id for roles  https://review.openstack.org/49699200:32
*** olaph1 has joined #openstack-shade00:38
*** olaph has quit IRC00:38
SamYaplemordred: ok. patches are now passing the gate. the highest priority ones for me are https://review.openstack.org/#/c/497483/ https://review.openstack.org/#/c/497537/00:38
SamYaplei abandonded that user_domain/project_domain/group_domain patch for now, ill also have to include role_domain and i dont absolutely need it right this second. ill circle back around to it00:39
*** olaph1 is now known as olaf00:45
*** olaf is now known as olaph00:45
htaccesshaving only used shade via ansible (a lot) and using per project libs or the unified client from python01:56
htaccessi am now using shade directly in python01:56
htaccessand i have to say I'm liking it a _lot_01:57
htaccesswould be nice if list_keypairs() supported filters to be consistent with other list_ methods02:02
openstackgerritMerged openstack-infra/shade master: Fix switched params  https://review.openstack.org/49813202:16
*** gouthamr has quit IRC02:46
*** gkadam_ has joined #openstack-shade03:33
openstackgerritMerged openstack-infra/shade master: De-client-ify Service Delete  https://review.openstack.org/48219705:01
*** yolanda has quit IRC05:21
*** yfried has joined #openstack-shade06:44
*** slaweq has joined #openstack-shade06:50
*** slaweq has quit IRC06:55
*** yolanda has joined #openstack-shade06:57
*** jamielennox has quit IRC07:09
*** jamielennox has joined #openstack-shade07:14
*** ioggstream has joined #openstack-shade07:44
*** thrash|g0ne is now known as thrash10:42
*** rods_ has joined #openstack-shade11:50
*** gkadam_ has quit IRC11:54
*** olaph has quit IRC12:07
*** Shrews has quit IRC12:07
*** thrash has quit IRC12:07
*** mrhillsman has quit IRC12:07
*** olaph has joined #openstack-shade12:22
*** Shrews has joined #openstack-shade12:22
*** thrash has joined #openstack-shade12:22
*** mrhillsman has joined #openstack-shade12:22
openstackgerritMonty Taylor proposed openstack/oaktree master: Add zuul v3 job to trigger readthedocs  https://review.openstack.org/49890512:37
mordredhtaccess: yay glad to hear that!12:38
mordredhtaccess: give search_keypairs a shot12:39
*** slaweq has joined #openstack-shade12:41
*** gouthamr has joined #openstack-shade13:19
openstackgerritMerged openstack-infra/shade master: Support domain_id for user operations  https://review.openstack.org/49748313:27
openstackgerritMerged openstack-infra/shade master: Add domain_id to groups  https://review.openstack.org/49753713:28
*** rods_ has quit IRC14:21
*** rods has joined #openstack-shade14:21
*** rods has quit IRC14:22
*** rods has joined #openstack-shade14:22
*** rods has quit IRC14:31
*** olaph1 has joined #openstack-shade14:31
*** olaph has quit IRC14:32
*** rods has joined #openstack-shade14:32
*** rods has quit IRC14:41
*** slaweq has quit IRC14:55
*** slaweq has joined #openstack-shade14:55
*** slaweq has quit IRC15:00
SamYaplew00t. mordred im ready for a tag on shade if you are. the search users in domains was the biggest blocker15:07
*** slaweq has joined #openstack-shade15:19
*** slaweq has quit IRC15:23
*** olaph has joined #openstack-shade15:26
*** olaph1 has quit IRC15:27
*** gouthamr has quit IRC15:53
*** gouthamr has joined #openstack-shade16:16
*** rods has joined #openstack-shade16:35
*** gkadam_ has joined #openstack-shade16:57
openstackgerritMerged openstack-infra/shade master: Switch to _is_client_version in list_services  https://review.openstack.org/49717117:17
SamYaplew00t17:17
*** ioggstream has quit IRC17:28
*** gkadam_ has quit IRC18:01
*** gouthamr has quit IRC18:28
*** yfried has quit IRC18:32
*** gouthamr has joined #openstack-shade18:44
*** slaweq has joined #openstack-shade19:31
*** slaweq has quit IRC19:31
*** slaweq has joined #openstack-shade19:32
openstackgerritSamuel de Medeiros Queiroz proposed openstack-infra/shade master: De-client-ify User Update  https://review.openstack.org/49928419:55
openstackgerritSamuel de Medeiros Queiroz proposed openstack-infra/shade master: De-client-ify User Update  https://review.openstack.org/49928419:57
*** slaweq has quit IRC20:50
*** slaweq has joined #openstack-shade20:52
*** gouthamr has quit IRC20:54
slaweqmordred: hello21:10
slaweqmordred: how are You?21:10
slaweqmordred: can You maybe take a look on https://review.openstack.org/#/c/498918/ and https://review.openstack.org/#/c/498925/ and check if those patches makes sense for You?21:10
*** gouthamr has joined #openstack-shade21:10
mordredslaweq: hello! yes - those both look great - although the gate is unhappy with the compute one21:12
slaweqyes, I'm rechecking it now21:13
slaweqyesterday it failed because some volume was not removed but it was in test, not in cleanup so I can't do anything with that21:13
slaweqand now it failed because of reason which should be fixed by second patch :)21:13
mordred:)21:14
slaweqmordred: but I will try to keep looking on such errors and fix some of them if it will be possible21:15
mordredsweet - I appreciate that a lot - flaky test runs that are just due to the cloud not being able to delete a volume are no good21:17
slaweqyes, I agree :)21:18
openstackgerritSamuel de Medeiros Queiroz proposed openstack-infra/shade master: De-client-ify Add User to Group  https://review.openstack.org/49934521:28
mordredsamueldmq: ksa 3.2.0 has been released and is working its way through requirements/constraints - as soon as that lands, we should be able to land the 'use ksa 3.2 version discovery' patch21:38
samueldmqmordred: that's great!!21:39
samueldmqmeanwhile I am working on the rest of those keystone patches (restification)21:39
samueldmqI'm pretty sure those are finite :-)21:40
openstackgerritSamuel de Medeiros Queiroz proposed openstack-infra/shade master: De-client-ify Check User in Group  https://review.openstack.org/49935721:47
openstackgerritSamuel de Medeiros Queiroz proposed openstack-infra/shade master: De-client-ify Remove User from Group  https://review.openstack.org/49936021:50
openstackgerritMerged openstack-infra/shade master: Fix handling timeouts in volume functional tests cleanup  https://review.openstack.org/49891821:55
samueldmqmordred: I'm having a hard time understanding the endpoint crud in shade22:03
samueldmq:(22:03
slaweqmordred: https://review.openstack.org/#/c/498925/ <-- not jenkins is happy with it :)22:04
slaweq*now22:04
mordredsamueldmq: oh. yeah. ... I think you can blame SamYaple forthat, but it's actually my fault - at this point I believe that the decision to try to make endpoints look the same between v2 and v3 was a mistake, but it's one we're stuck with22:05
mordredslaweq: woot122:05
mordredsamueldmq: the short version is - because we want to keep the interface the same, we accept both v2 and v3 style arguments22:06
mordredsamueldmq: if you give us v2 style arguments but the cloud is v3, we will make 3 calls to keystone one for each type of endpoint22:06
samueldmqmordred: and what if I give v3 args and cloud is v2?22:07
mordredsamueldmq: if you use v3 style arguments on a v2 cloud for anyhting other than public url you get an error22:07
mordredbecause v2 can't update an endpoint22:07
mordredso you need to use all three arguments at one time22:07
samueldmqmordred: since v2 doesn't have interface, you assume public for that?22:08
SamYaplesamueldmq: keystone requires public22:08
SamYapleadmin and internal are optional22:08
SamYaplea single endpoint id can have all three22:08
SamYaple(in v2)22:08
mordredwell - if you want to use v3 arguments on a v2 cloud, you basically must pass 'public' to the interface argument22:08
mordredhttps://github.com/openstack-infra/shade/blob/master/shade/operatorcloud.py#L92322:08
mordredSamYaple: yah22:08
mordredthe short version is - as a user you should really use the arguments for your keystone version - which is MUCH more reasonable for endpoint because as an operator it's totally reasonable to know which version you are running22:09
SamYapleyea i regret the endpoint stuff22:09
mordred(this is an area where I pushed too far for consistency and the end result was, I think, not good)22:09
SamYaplebut meh22:09
mordredyup22:10
mordredI believe I have learned something from it22:10
SamYapleits the reason we still dont have an ansible_endpoint module22:10
SamYapleplus im kinda lazy22:10
mordredyah22:10
mordredSamYaple: you know - what we should do is make an os_keystone_endpoint and an os_keystone_v2_endpoint module22:11
mordredSamYaple: and NOT expose this interface through to ansible22:11
samueldmqkeystone v2 endpoint create already does "Create three v3 endpoint refs based on a legacy ref."22:11
mordredSamYaple: and you should either do the same in salt, or just ignore v2 altogether22:11
SamYaplemordred: salt is **kwargs heavy, they get everything!22:12
mordredSamYaple: nice22:12
SamYaplebut i only plan on documenting v322:12
mordredsamueldmq: yes- the complexity here comes from shade allowing both styles of arguments no matter which version you have on the backend22:12
mordredSamYaple: yes please22:12
mordredsamueldmq: so you can have a v2 service, and pass url=example.com, interface=public and it will work22:13
mordredsamueldmq: you can have a v2 service and pass public_url, internal_url and admin_url and it will work22:13
mordredSamYaple: you can hav ea v3 service and pass public_url, internal_url and admin_url and it will work by making three calls to keystone service for interface=public, interface=internal and interface=admin22:14
mordredgah22:14
samueldmq:-)22:14
mordredsamueldmq: andyou can have a v3 service and use url, interface and it will work22:14
mordredthe only uthing you cannot do is have a v2 service and make multiple calls to create_endpoint with the url, interface syntax22:14
samueldmqmordred: why?22:15
samueldmqno updates? for the other *_url?22:16
samueldmqthe endpoint compatibility code in keystone itself is not easy either22:19
SamYaplesamueldmq: because using interface= url= can only specify a single type at a time, and v2 requires public22:23
SamYapleso you can only create the public endpoint on v2 with the v3 syntax22:23
samueldmqSamYaple: ah, and if you do call it agai nwith interface=another_one url=the_same22:24
SamYaplethe keystone v2.0 api will yell at you in that case22:25
samueldmqit wouldnt  know if you want to create another endpoint or add info to the existing one22:25
samueldmqhmm ok22:25
SamYaplesamueldmq: you can't update keystone v2 enpoints at all22:25
SamYaplei dont think there were any 'updates' to anything in v2 keystone (but i could be wrong)22:26
samueldmqSamYaple: aha, that's what I thought. otherwise you could update and just add the other *_url22:26
samueldmqinterface=public url=xpto; interface=admin url=xpto; interface=internal url=xpto22:27
samueldmqthose 3 calls could result in a single v2 endpoint, but that's not possible at all (without updates)22:27
SamYaplei think we are on the same page, yes22:28
samueldmqkk nice thanks22:28
SamYaplei almost want a create_endpoint_2() shade function :(22:29
*** slaweq has quit IRC22:30
*** rods has quit IRC22:31
SamYapleactually. you know its not that bad.22:32
SamYapleif using it with v3, you get a list with one element22:32
SamYaplethats ok22:32
*** rods has joined #openstack-shade22:34
openstackgerritMerged openstack-infra/shade master: Add handling timeout in servers cleanup function  https://review.openstack.org/49892522:49
*** thrash is now known as thrash|g0ne23:11

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!