Tuesday, 2017-11-14

openstackgerritMonty Taylor proposed openstack-infra/shade master: Add ability to work in other auth contexts  https://review.openstack.org/51939400:13
openstackgerritMonty Taylor proposed openstack-infra/shade master: Add helper property to get the current user id  https://review.openstack.org/51951100:13
*** ioggstream has joined #openstack-shade07:35
*** slaweq has joined #openstack-shade09:31
*** ioggstream has quit IRC10:32
*** gouthamr has joined #openstack-shade11:10
*** gouthamr has quit IRC12:05
*** gouthamr has joined #openstack-shade12:20
openstackgerritMonty Taylor proposed openstack-infra/shade master: Add ability to work in other auth contexts  https://review.openstack.org/51939412:31
*** gouthamr has quit IRC12:53
*** gouthamr has joined #openstack-shade13:02
openstackgerritMonty Taylor proposed openstack-infra/shade master: Add helper property to get the current user id  https://review.openstack.org/51951113:19
*** gouthamr has quit IRC13:38
*** gouthamr has joined #openstack-shade13:54
openstackgerritMerged openstack/os-client-config master: Add shade-functional-tips jobs  https://review.openstack.org/51406714:43
*** gouthamr has quit IRC15:13
*** gouthamr has joined #openstack-shade15:15
*** slaweq has quit IRC17:02
openstackgerritChristian Groschupp proposed openstack-infra/shade master: Creating a server and specifying scheduler_hints fails  https://review.openstack.org/51970517:20
openstackgerritChristian Groschupp proposed openstack-infra/shade master: Fix creating a server with specifying scheduler_hints  https://review.openstack.org/51970517:40
Shrewsmordred: Is the old 'internal_network' value on the fip object supposed to be the same as the 'network_id' we now have?17:59
ShrewsFIPs give me such headaches17:59
Shrewsi guess we just return 'network', not 'network_id'18:00
Shrewshrm, i wonder if that was coming back from neutron as part of 'properties' dict18:01
Shrewsdon't see that in the api docs18:06
Shrewsok, so 'network' is the external network the fip is on18:10
Shrewsi guess we'll have to use the port or the fixed IP to identify the internal net? don't see any direct path to it18:12
mordredShrews: yah- I believe you have to get the fixed ip from the fip object, then look for a port with that fixed ip, then see what network the port is on18:15
mordredShrews: grabbing a vm with fip real quick18:16
Shrews(nat_destination and f_ip.internal_network == fixed_address)18:19
Shrewswth was that doing?18:19
mordredShrews: the port entry on the fip is the port for the fixed address18:19
Shrewscomparing a network name to an IP?18:19
mordredgod only konws - it certainly doesn't seem like a thing that would have ever worked18:19
Shrewsthat makes me think that internal_network is not a name18:20
Shrewsjeebus18:20
Shrewsi'm a bit confused on what the fix is18:20
mordredShrews: fip dicts shouldn't even have an internal_network property18:23
mordredShrews: I have no clue how that EVER worked18:24
mordredShrews: it's not a part of the neutron api, nor the old nova fip api - nor is it a thing we add in normalize18:26
Shrewsok, so the fix should be ansible module side then.18:26
mordredShrews: so I think that code has just quite literally never worked18:26
Shrewsmordred: that at least explains a few things18:26
Shrewsbut adds more questions about what we must have been drinking18:26
mordredShrews: yah18:28
Shrewsmordred: so maybe the propose fix is ok?18:29
Shrewsproposed*18:29
mordredShrews: yah- I think so. it's at the very least certianly not worse18:29
mordredShrews: I left a shipit - it seems more correct than what's there now at least18:32
Shrewsmordred: agreed18:33
Shrewsi left a second shipit18:34
mordredShrews: should we just merge it? or does the bot merge it now?18:38
Shrewsmordred: i think the bot does with 2 shipits18:38
Shrewsnot sure about the backporting18:38
mordrednod18:39
Shrewsmordred: https://github.com/ansible/ansibullbot/blob/master/ISSUE_HELP.md#when-will-your-pull-request-be-merged18:39
mordredShrews: cool18:40
SamYapleit turns out i have shipit abilities too18:42
SamYaplelooks like the opened it up to anyone thats authored a module inthe same sphere ofmodules18:42
*** gouthamr has quit IRC20:53
*** gouthamr has joined #openstack-shade21:23
*** slaweq has joined #openstack-shade21:25
*** gouthamr has quit IRC21:49
*** zigo has quit IRC21:59
*** zigo has joined #openstack-shade22:01
mordredShrews: btw - https://review.openstack.org/#/c/519394/ and https://review.openstack.org/#/c/519511/2 are green now22:21
mordredoh - piddle. the release note is bong - I'm just going to do a followup22:22
mordredShrews: remote:   https://review.openstack.org/519784 Remove reference to context-managers from release note22:23
*** gouthamr has joined #openstack-shade22:26
*** thrash is now known as thrash|g0ne22:34
*** slaweq has quit IRC23:41
*** slaweq has joined #openstack-shade23:42
*** slaweq has quit IRC23:46
*** gouthamr has quit IRC23:52
openstackgerritMerged openstack-infra/shade master: Updated from global requirements  https://review.openstack.org/51978523:57

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