| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-sdks - 2018-11-07 | |||
| 20:05:32 | mordred | cdent: it's a filename | |
| 20:05:56 | mordred | cdent: and yeah - I think that's what I'm thinking re: api vs. client | |
| 20:06:12 | mordred | the json contents returned from that url contain informatoin _about_ the openstack api | |
| 20:06:41 | cdent | yes | |
| 20:08:07 | edleafe | I concur with api | |
| 20:09:43 | mordred | mnaser: if you get a sec, would you mind moving that test file to .well-known/openstack/api instead of .well-known/openstack/client ? | |
| 20:10:19 | mordred | mnaser: also - thank you for putting it there - it made verifying the new consumption code very nice | |
| 20:20:48 | openstackgerrit | Merged openstack/openstacksdk master: Shift swift segment async code out of adapter https://review.openstack.org/614832 | |
| 21:00:29 | openstackgerrit | Merged openstack/openstacksdk master: Remove unused Task classes https://review.openstack.org/614833 | |
| 21:12:09 | elmiko | mordred: sorry, just saw the ping | |
| 21:12:28 | elmiko | i agree with edleafe and cdent though (no surprise) | |
| 21:16:05 | mordred | elmiko: \o/ | |
| 21:16:33 | cdent | elmiko: I'm sorry to report we _still_ haven't used that syrup. We keep saying we'll make pancakes and then forget. But we are very pleased to see it in the cupboard every time we look. | |
| 23:16:22 | mnaser | mordred: https://vexxhost.com/.well-known/openstack/api | |
| #openstack-sdks - 2018-11-08 | |||
| 01:45:22 | openstackgerrit | Merged openstack/python-openstackclient master: Handle multiple ports in AddFloatingIP https://review.openstack.org/615353 | |
| 02:44:01 | openstackgerrit | wangqi proposed openstack/python-openstackclient master: Trivial: Fix the pep8 warning https://review.openstack.org/616395 | |
| 05:40:17 | openstackgerrit | Merged openstack/python-openstackclient master: image/v2: support multiple property filters https://review.openstack.org/615850 | |
| 06:21:04 | openstackgerrit | Vishakha Agarwal proposed openstack/python-openstackclient master: Modify the help message for 'registered limit set' https://review.openstack.org/609985 | |
| 11:12:33 | openstackgerrit | melissaml proposed openstack-infra/shade master: fix the word 'bandwith' https://review.openstack.org/616513 | |
| 12:57:17 | mordred | mnaser: you are amazing | |
| 13:55:18 | openstackgerrit | Monty Taylor proposed openstack/openstacksdk master: WIP Support remote vendor profiles https://review.openstack.org/616228 | |
| 14:26:35 | samueldmq | morning | |
| 14:27:43 | samueldmq | is it correcto to say "At the service level, OpenStack has native support for API level interoperability, certifying clouds via the RefStack program." | |
| 14:29:25 | samueldmq | this allows heterogeneous clouds running the same service API versions to fully interoperate | |
| 14:29:34 | openstackgerrit | Monty Taylor proposed openstack/openstacksdk master: WIP Collect request stats https://review.openstack.org/614834 | |
| 14:29:58 | samueldmq | and 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:35:08 | mordred | samueldmq: it's ... the optimistic way of saying it, yes | |
| 14:36:52 | samueldmq | mordred: but that's what refstack does, correct? | |
| 14:37:22 | samueldmq | you mean optimistic because I am putting so much of the glory in sdk I guess | |
| 14:50:35 | mordred | samueldmq: no - I mean optimistic about RefStack :) | |
| 14:50:49 | samueldmq | mordred: oh | |
| 14:51:35 | mordred | samueldmq: but I think what you're saying is the intent - and my pessimistic side just sees the bugs | |
| 14:51:37 | samueldmq | what does it do in practice? just run tempest tests against clouds and reports results? | |
| 14:52:00 | samueldmq | mordred: bugs.. for example? I need to know more downsides of it | |
| 14:52:12 | mordred | samueldmq: 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 provide | |
| 14:52:47 | mordred | samueldmq: 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 certification | |
| 14:53:30 | mordred | samueldmq: at the sdk level we can provide a consistency quickly - while aligning different operating clouds might take a bit longer | |
| 14:54:04 | samueldmq | hmmm | |
| 14:54:12 | samueldmq | so refstack's intent was to standardize? | |
| 14:54:15 | samueldmq | is* | |
| 14:55:49 | samueldmq | mordred: that's very interesting... standardizing things that are already alive don't work well. literature and experience shows that | |
| 14:56:07 | samueldmq | also - standards translates into cutting some use cases, and flexibility :-) | |
| 14:58:59 | mordred | samueldmq: yes - that's right - and you're exactly right | |
| 14:59:09 | mordred | samueldmq: refstack started well after there were already many production deployments | |
| 14:59:15 | mordred | so it has to take a conservative approach | |
| 15:00:01 | samueldmq | oh well, that's a good story to be written... thanks!! | |
| 15:00:08 | mordred | sdk 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 beginning | |
| 15:00:12 | mordred | samueldmq: \o/ | |
| 15:00:39 | samueldmq | \o/ | |
| 15:51:46 | elmiko | edleafe: i will be around here, but i have a call to listen in on at the same time. just a heads up | |
| 15:55:21 | edleafe | elmiko: dtantsur: no problem | |
| 15:55:33 | edleafe | I'll try to handle the crowds all by myself :) | |
| 16:00:07 | edleafe | The API-SIG Office Hour has officially begun. | |
| 16:01:08 | elmiko | lol | |
| 16:02:06 | edleafe | Well, we don't use #startmeeting, so I gotta write something :) | |
| 16:02:22 | elmiko | #putsfeetondesk | |
| 16:03:09 | elmiko | and i wasn't lol'ing at your announcement (i like it), i was laughing at the exchange between you and mordred =) | |
| 16:04:37 | edleafe | That mordred thinks he's so tough | |
| 16:05:01 | elmiko | indeed | |
| 16:36:50 | openstackgerrit | Ed Leafe proposed openstack/api-sig master: Add idempotent DELETE guidance https://review.openstack.org/616610 | |
| 16:36:55 | edleafe | elmiko: dtantsur: finally got around to writing this ^^ | |
| 16:37:05 | elmiko | \o/ | |
| 16:38:18 | dtantsur | w00t | |
| 17:01:05 | edleafe | wow, another busy office hour | |
| 17:02:44 | elmiko | lol | |
| 17:02:51 | elmiko | hey, you posted a PR! | |
| 17:03:59 | elmiko | edleafe: just a heads up, i won't be around next week. gonna be at a conference | |
| 17:04:21 | elmiko | although, isn't next week the forum too? | |
| 17:04:35 | edleafe | elmiko: Unfortunately, next week I *won't* be at a conference | |
| 17:04:41 | elmiko | =( | |
| 17:04:53 | elmiko | ++ | |
| 17:05:11 | elmiko | just running around all willy-nilly dropping 34B here and there XD | |
| 17:05:40 | edleafe | They just wanted to get you working for them | |
| 17:05:51 | elmiko | lol | |
| 17:20:21 | openstackgerrit | Dean Troyer proposed openstack/python-openstackclient master: Add project param in LimitList parser https://review.openstack.org/611789 | |
| 18:07:02 | mordred | Shrews: incidentally, in writing tests for the statsd patch, I actually discovered a bug that was lurking in the existing code | |
| 18:07:10 | mordred | Shrews: also - I have tests now | |
| 18:10:36 | openstackgerrit | Monty Taylor proposed openstack/openstacksdk master: WIP Collect request stats https://review.openstack.org/614834 | |
| 18:12:15 | mordred | Shrews, 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:27:18 | tobiash | mordred: what is the openstack_http_requests supposed to be? | |
| 18:27:37 | mordred | tobiash: the equiv of the task counter | |
| 18:28:07 | mordred | tobiash: so what you're translating to nodepool_task now | |
| 18:28:11 | tobiash | mordred: then I think it should be a counter, not a gauge | |
| 18:28:59 | mordred | tobiash: ok - the counter docs said something about resetting on restarts - was I just understanding that wrong? | |
| 18:29:32 | mordred | tobiash: ah - I see! (found better docs) | |
| 18:29:34 | mordred | and I agre | |
| 18:29:52 | mordred | and good - because I find spelling gauge very hard | |
| 18:29:52 | tobiash | mordred: https://prometheus.io/docs/concepts/metric_types/ | |
| 18:30:09 | tobiash | that's the reference of the prometheus metric types | |
| 18:30:21 | tobiash | mordred: in statsd this is probably a counter too? | |
| 18:31:37 | mordred | tobiash: yah | |
| 18:31:44 | tobiash | gauge 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 usage | |
| 18:32:07 | mordred | yah - makes sense | |
| 18:32:16 | tobiash | with counters instead you can do things like calculating rates per any time interval | |
| 18:34:39 | tobiash | mordred: I think using a histogram however is a good choice | |
| 18:34:48 | tobiash | for the timers | |
| 18:35:16 | mordred | woot! | |
| 18:36:26 | tobiash | especially if you want to aggregate and calculate quantiles of more than one series you *need* historgrams instead of summaries | |
| 18:36:50 | tobiash | some background info on that: https://prometheus.io/docs/practices/histograms/ | |
| 18:37:00 | tobiash | it's really interesting | |