Thursday, 2018-11-08

*** dhellmann has joined #openstack-sdks00:07
*** bobh has joined #openstack-sdks01:12
*** bobh has quit IRC01:28
openstackgerritMerged openstack/python-openstackclient master: Handle multiple ports in AddFloatingIP  https://review.openstack.org/61535301:45
*** mriedem has quit IRC01:50
openstackgerritwangqi proposed openstack/python-openstackclient master: Trivial: Fix the pep8 warning  https://review.openstack.org/61639502:44
*** markvoelker has joined #openstack-sdks02:45
*** bobh has joined #openstack-sdks02:49
*** markvoelker has quit IRC02:50
*** markvoelker has joined #openstack-sdks02:52
*** markvoelker has quit IRC02:52
*** markvoelker has joined #openstack-sdks02:55
*** fungi has quit IRC03:06
*** mrhillsman has joined #openstack-sdks03:19
*** bobh has quit IRC03:55
*** bobh has joined #openstack-sdks04:08
*** bobh has quit IRC04:10
openstackgerritMerged openstack/python-openstackclient master: image/v2: support multiple property filters  https://review.openstack.org/61585005:40
openstackgerritVishakha Agarwal proposed openstack/python-openstackclient master: Modify the help message for 'registered limit set'  https://review.openstack.org/60998506:21
*** slaweq has joined #openstack-sdks07:39
*** gtema has joined #openstack-sdks07:49
*** Luzi has joined #openstack-sdks08:30
*** jpena|off is now known as jpena08:36
*** noama has joined #openstack-sdks08:38
*** jpich has joined #openstack-sdks09:14
*** e0ne has joined #openstack-sdks09:50
*** ttsiouts has joined #openstack-sdks09:54
*** dtantsur|afk is now known as dtantsur09:55
*** ttsiouts has quit IRC09:56
*** ttsiouts has joined #openstack-sdks09:57
*** ttsiouts_ has joined #openstack-sdks09:59
*** ttsiouts has quit IRC09:59
*** ttsiouts_ has quit IRC10:19
*** ttsiouts has joined #openstack-sdks10:20
*** ttsiouts has quit IRC10:24
*** ttsiouts has joined #openstack-sdks10:34
openstackgerritmelissaml proposed openstack-infra/shade master: fix the word 'bandwith'  https://review.openstack.org/61651311:12
*** ttsiouts has quit IRC11:35
*** ttsiouts has joined #openstack-sdks11:35
*** ttsiouts has quit IRC11:38
*** ttsiouts_ has joined #openstack-sdks11:38
*** jpena is now known as jpena|lunch12:03
*** Luzi has quit IRC12:05
*** ttsiouts_ has quit IRC12:14
*** ttsiouts has joined #openstack-sdks12:14
*** ttsiouts has quit IRC12:19
*** Luzi has joined #openstack-sdks12:20
*** dtantsur is now known as dtantsur|brb12:32
*** gtema has quit IRC12:49
*** ttsiouts has joined #openstack-sdks12:52
*** ttsiouts has quit IRC12:56
*** ttsiouts has joined #openstack-sdks12:57
mordredmnaser: you are amazing12:57
*** e0ne has quit IRC13:03
*** jpena|lunch is now known as jpena13:24
*** e0ne has joined #openstack-sdks13:37
openstackgerritMonty Taylor proposed openstack/openstacksdk master: WIP Support remote vendor profiles  https://review.openstack.org/61622813:55
*** jpich has quit IRC14:02
*** irclogbot_2 has quit IRC14:02
*** tonyb has quit IRC14:02
*** dmellado has quit IRC14:02
*** eandersson has quit IRC14:02
*** elmiko has quit IRC14:02
*** tobiash has quit IRC14:02
*** dmellado has joined #openstack-sdks14:04
*** jpich has joined #openstack-sdks14:04
*** christi3k has quit IRC14:04
*** tobiash has joined #openstack-sdks14:05
*** tonyb has joined #openstack-sdks14:07
*** christi3k has joined #openstack-sdks14:07
*** mriedem has joined #openstack-sdks14:13
*** bobh has joined #openstack-sdks14:16
*** ttsiouts has quit IRC14:16
*** ttsiouts has joined #openstack-sdks14:17
*** ttsiouts has quit IRC14:19
*** ttsiouts has joined #openstack-sdks14:20
samueldmqmorning14:26
samueldmqis it correcto to say "At the service level, OpenStack has native support for API level interoperability, certifying clouds via the RefStack program."14:27
samueldmqthis allows heterogeneous clouds running the same service API versions to fully interoperate14:29
openstackgerritMonty Taylor proposed openstack/openstacksdk master: WIP Collect request stats  https://review.openstack.org/61483414:29
samueldmqand then it comes to sdk providing an upper abstraction layer for supporting multiple service (nova-net vs neutron) and versions of the smae service (keystone v2 and v3)14:29
mordredsamueldmq: it's ... the optimistic way of saying it, yes14:35
samueldmqmordred: but that's what refstack does, correct?14:36
samueldmqyou mean optimistic because I am putting so much of the glory in sdk I guess14:37
mordredsamueldmq: no - I mean optimistic about RefStack :)14:50
samueldmqmordred: oh14:50
mordredsamueldmq: but I think what you're saying is the intent - and my pessimistic side just sees the bugs14:51
samueldmqwhat does it do in practice? just run tempest tests against clouds and reports results?14:51
samueldmqmordred: bugs.. for example? I need to know more downsides of it14:52
mordredsamueldmq: so you could say all of the above, but then also that sdk's abstraciton layer does what you say it does - and also works around bugs/holes in the interoperability that refstack aims to provide14:52
mordredsamueldmq: well - places where refstack doesn't have a story for something yet - or where people can't agree that a given feature should be covered by refstack certification14:52
mordredsamueldmq: at the sdk level we can provide a consistency quickly - while aligning different operating clouds might take a bit longer14:53
samueldmqhmmm14:54
samueldmqso refstack's intent was to standardize?14:54
samueldmqis*14:54
samueldmqmordred: that's very interesting... standardizing things that are already alive don't work well. literature and experience shows that14:55
samueldmqalso - standards translates into cutting some use cases, and flexibility :-)14:56
mordredsamueldmq: yes - that's right - and you're exactly right14:58
mordredsamueldmq: refstack started well after there were already many production deployments14:59
mordredso it has to take a conservative approach14:59
samueldmqoh well, that's a good story to be written... thanks!!15:00
mordredsdk also started after many production deployments - so it was able to look at what reality was, and then provide an abstraction on top of that to hide differences that exist due to refstack not existing in the beginning15:00
mordredsamueldmq: \o/15:00
samueldmq\o/15:00
*** dtantsur|brb is now known as dtantsur15:02
*** ttsiouts has quit IRC15:15
*** ttsiouts has joined #openstack-sdks15:15
*** ttsiouts has quit IRC15:19
*** ttsiouts has joined #openstack-sdks15:22
*** ttsiouts has quit IRC15:46
*** ttsiouts has joined #openstack-sdks15:47
*** ttsiouts has quit IRC15:49
*** ttsiouts has joined #openstack-sdks15:49
*** elmiko has joined #openstack-sdks15:51
elmikoedleafe: i will be around here, but i have a call to listen in on at the same time. just a heads up15:51
* dtantsur ditto15:54
edleafeelmiko: dtantsur: no problem15:55
edleafeI'll try to handle the crowds all by myself :)15:55
* mordred crowds edleafe15:55
* edleafe reaches for his mace15:55
* mordred equips face mask15:56
edleafeThe API-SIG Office Hour has officially begun.16:00
elmikolol16:01
edleafeWell, we don't use #startmeeting, so I gotta write something :)16:02
elmiko#putsfeetondesk16:02
elmikoand i wasn't lol'ing at your announcement (i like it), i was laughing at the exchange between you and mordred =)16:03
edleafeThat mordred thinks he's so tough16:04
elmikoindeed16:05
*** noama has quit IRC16:06
*** ttsiouts has quit IRC16:07
*** ttsiouts has joined #openstack-sdks16:08
*** Luzi has quit IRC16:22
openstackgerritEd Leafe proposed openstack/api-sig master: Add idempotent DELETE guidance  https://review.openstack.org/61661016:36
edleafeelmiko: dtantsur: finally got around to writing this ^^16:36
elmiko\o/16:37
dtantsurw00t16:38
*** slaweq has quit IRC16:40
*** e0ne has quit IRC16:48
*** slaweq has joined #openstack-sdks16:58
edleafewow, another busy office hour17:01
elmikolol17:02
elmikohey, you posted a PR!17:02
elmikoedleafe: just a heads up, i won't be around next week. gonna be at a conference17:03
elmikoalthough, isn't next week the forum too?17:04
edleafeelmiko: Unfortunately, next week I *won't* be at a conference17:04
elmiko=(17:04
* edleafe grumbles about IBM bean counters17:04
elmiko++17:04
elmikojust running around all willy-nilly dropping 34B here and there XD17:05
edleafeThey just wanted to get you working for them17:05
elmikolol17:05
*** ttsiouts has quit IRC17:16
openstackgerritDean Troyer proposed openstack/python-openstackclient master: Add project param in LimitList parser  https://review.openstack.org/61178917:20
*** Leo_m has joined #openstack-sdks17:27
*** jpich has quit IRC17:34
*** gtmanfred is now known as yaml17:36
*** yaml is now known as gtmanfred17:36
*** jpena is now known as jpena|off17:51
*** irclogbot_2 has joined #openstack-sdks18:01
mordredShrews: incidentally, in writing tests for the statsd patch, I actually discovered a bug that was lurking in the existing code18:07
mordredShrews: also - I have tests now18:07
openstackgerritMonty Taylor proposed openstack/openstacksdk master: WIP Collect request stats  https://review.openstack.org/61483418:10
mordredShrews, tobiash: ^^ it still needs docs added ... and tobiash, I'd love feedback on the metric names and labels (obviously it's not immediately useful if we don't decided to expose that directly in nodepool - but since you're using things already, I figureyou've got good context)18:12
tobiashmordred: what is the openstack_http_requests supposed to be?18:27
mordredtobiash: the equiv of the task counter18:27
mordredtobiash: so what you're translating to nodepool_task now18:28
tobiashmordred: then I think it should be a counter, not a gauge18:28
mordredtobiash: ok - the counter docs said something about resetting on restarts - was I just understanding that wrong?18:28
mordredtobiash: ah - I see! (found better docs)18:29
mordredand I agre18:29
tobiashmordred: https://prometheus.io/docs/concepts/metric_types/18:29
mordredand good - because I find spelling gauge very hard18:29
*** bobh has quit IRC18:29
tobiashthat's the reference of the prometheus metric types18:30
tobiashmordred: in statsd this is probably a counter too?18:30
mordredtobiash: yah18:31
tobiashgauge is not very useful for aggregating stuff, it should only be used if you are interested in the current value of something like current quota usage18:31
mordredyah - makes sense18:32
tobiashwith counters instead you can do things like calculating rates per any time interval18:32
tobiashmordred: I think using a histogram however is a good choice18:34
tobiashfor the timers18:34
mordredwoot!18:35
tobiashespecially if you want to aggregate and calculate quantiles of more than one series you *need* historgrams instead of summaries18:36
tobiashsome background info on that: https://prometheus.io/docs/practices/histograms/18:36
tobiashit's really interesting18:37
Shrewsya know, i was thinking about stats stuff (since it seems to be all the rage this week)... we could just let folks configure the statsd keys themselves via config file (at least in nodepool).18:38
Shrewsthat probably makes less sense in sdk18:39
Shrewswhere there can be lots of them18:39
Shrewsbah, silly thinking18:39
Shrewsmordred: can we please not add both statsd and the prometheus stuff in a single review?18:41
openstackgerritMonty Taylor proposed openstack/openstacksdk master: WIP Collect request stats  https://review.openstack.org/61483418:44
mordredtobiash: updated to counter18:45
mordredShrews: sure - once I get the docs written, I'll split it up18:45
Shrewsmordred: actually, it's not that overly burdonsome here18:45
mordred*phew18:45
mordredShrews: I tink that test file should have all the things we need to do further tests - I put in things to add the statsd and prometheus content to details on failure - cause otherwise it's like "1 doesn't match None" and you're like WTF???18:46
mordredShrews: that said - the stastd fixture starts a thread - and when I added it just to the base test case I wound up hitting too many open files :)18:47
mordredwhich - might be a thing we want to look in to in general, as that tells me something isn't properly getting shut down - but it only shows up when you've got a bazillion tests like we do in sdk18:47
Shrewsmordred: weird18:50
tobiashmordred: regarding openstack_http_requests I'd even add the response code as a label19:04
kmallocmordred: so.. about to land some pymemcache awesomeness to oslo.cache19:06
kmallocmordred: erm dogpile.cache19:06
kmalloc:)19:06
openstackgerritMerged openstack/python-openstackclient master: Add --name-lookup-one-by-one option to server list  https://review.openstack.org/56834519:07
openstackgerritMerged openstack/python-openstackclient master: Remove invalid 'unlock-volume' migration arg  https://review.openstack.org/55891019:11
*** mriedem has quit IRC19:32
*** dave-mccowan has joined #openstack-sdks19:56
mgagneI'm currently using python-openstackclient and performing "openstack port show <UUID>" on a non-existing port. I found with --debug that if GET /v2.0/ports/<UUID> returns a 404, GET /v2.0/ports is performed instead which can be *very* costly if you happen to have a LOT of ports or are an admin. Is there anyway to improve that?19:58
*** mriedem has joined #openstack-sdks19:59
kmallocmgagne: it would require a flag or something to not perform a list to "find" a port. this is a behavior for "get name or id" type thing that we typically do20:07
kmallocmgagne: it's to handle the case of passing a name instead of an id and having it magically work20:07
mgagnekmalloc: yes, if a UUID like name is found, would it be reasonable to not perform a full list?20:07
kmallocso something like --id <uuid> might need to be implemented so it doesn't do an id then name20:07
mgagneor are people crazy to name their ports with UUID?20:07
kmallocyes20:07
kmallocpeople name everything with uuids because operators often dynamically generate that stuff20:08
kmalloci see it all the time with projects/users20:08
kmallocID is UUID X, name is UUID Y20:08
mgagneso you have port.id != port.name but both are UUIDs? crazy stuff20:08
kmalloci wouldn't be surprised in ports or servers or anything20:08
kmallocwelcome to insanity20:09
kmallocit's unfortuantely the norm20:09
mgagnecan we have OS_INSANE=0 then? :D20:09
* kmalloc would rather just do a --id and --name explicit flags20:09
kmallocand throw a warning "hey, the get_name_or_id functionality is going away"20:10
kmallocbut i don't have a lot of say in that part20:10
mgagneok, at least I got an explanation20:10
kmallocthat is a guess fwiw20:11
kmalloci didn't look at the code20:11
kmallocbut it sure sounds like what we do elsewhere20:11
mgagneyea... I'm sure it's nothing like that because it uses find_port which I guess support both id and name at the same time.20:12
kmallocyep, so basically the same concept though20:13
mgagnesomething*20:16
*** e0ne has joined #openstack-sdks20:19
*** e0ne has quit IRC20:22
*** dave-mccowan has quit IRC20:33
dtroyermelwitt: do you want to backport the add floating ip fix past rocky?20:40
dtroyerI was preparing a set of stable releases, if so I'll wait for that…20:41
melwittdtroyer: yes, I was hoping for queens (where my downstream bug was reported). ah, ok20:41
melwittsure20:41
*** mriedem has quit IRC20:41
dtroyergo ahead and propose that then20:42
melwittk20:42
melwittavailable at https://review.openstack.org/61669020:45
*** mriedem has joined #openstack-sdks20:45
melwittdtroyer ^20:55
*** mriedem has left #openstack-sdks21:18
openstackgerritMonty Taylor proposed openstack/openstacksdk master: WIP Collect request stats  https://review.openstack.org/61483421:45
openstackgerritMonty Taylor proposed openstack/openstacksdk master: WIP Collect request stats  https://review.openstack.org/61483422:03
mordredmgagne: fwiw - sdk by default ALWAYS does a list and filters for name or id client-side :)22:16
*** mriedem has joined #openstack-sdks22:36
*** mriedem has quit IRC22:46
openstackgerritSlawek Kaplonski proposed openstack/openstacksdk master: Add CRUD methods for Neutron Port Forwarding  https://review.openstack.org/61671022:52
*** Leo_m has quit IRC23:14
*** slaweq has quit IRC23:15
openstackgerritMerged openstack/python-openstackclient master: Add project param in LimitList parser  https://review.openstack.org/61178923:27

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