| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-sdks - 2019-08-01 | |||
| 14:39:36 | mriedem | dtroyer: i think we can abandon https://review.opendev.org/#/c/667264/ in favor of https://review.opendev.org/#/c/672577/ now | |
| 15:12:11 | openstackgerrit | Merged openstack/os-client-config master: Fix broken link to openstacksdk https://review.opendev.org/673603 | |
| 16:00:06 | edleafe | Hear ye, hear ye! The API-SIG Office Hour will now come to order! | |
| 16:00:17 | elmiko | quick on the draw today edleafe | |
| 16:00:23 | elmiko | i was mid-sentence! | |
| 16:00:43 | edleafe | Finally! You've been quicker most of the last few weeks | |
| 16:00:55 | elmiko | haha, i dunno about that XD | |
| 16:01:16 | elmiko | i blame your robotic parts, you've been upgraded damint! | |
| 16:01:37 | edleafe | You think I type with my knee?? | |
| 16:01:59 | elmiko | i have my suspicions, that's all i'm saying | |
| 16:02:27 | elmiko | haha | |
| 16:02:36 | edleafe | You can't hide from my laser eyes!! | |
| 16:02:55 | elmiko | SEE! it's not just the knee, RUN !!! | |
| 16:03:30 | edleafe | Oh, now I'm typing with my eyes, eh? | |
| 16:03:49 | elmiko | all i'm saying is that you /could/ be | |
| 16:04:12 | edleafe | Paranoid much? | |
| 16:04:41 | elmiko | hey just because i'm paranoid /doesn't/ mean they aren't after me | |
| 16:05:36 | dtantsur | \o | |
| 16:05:54 | elmiko | o/ | |
| 16:06:19 | dtantsur | sorry, instincts | |
| 16:06:29 | edleafe | maybe switch to decaf? | |
| 16:06:34 | elmiko | haha | |
| 16:06:43 | dtantsur | may I shock you? | |
| 16:06:54 | dtantsur | I haven't drunk any coffee for more than a week! | |
| 16:06:59 | elmiko | wow | |
| 16:07:01 | dtantsur | kind of an experiment | |
| 16:07:35 | elmiko | trying to cut back on caffiene? | |
| 16:07:38 | dtantsur | yeah | |
| 16:07:41 | edleafe | dtantsur: https://www.youtube.com/watch?v=hd1ciPnTGKg | |
| 16:08:00 | elmiko | LOL edleafe | |
| 16:08:12 | elmiko | good luck dtantsur, hope the experiment is a success ;) | |
| 16:08:19 | dtantsur | :D | |
| 16:08:22 | elmiko | or at least produces good data | |
| 16:08:39 | dtantsur | do we actually have any API business for today? | |
| 16:09:00 | edleafe | wait, we do API stuff here? | |
| 16:09:35 | dtantsur | a legend tells that many centuries ago 4 sages met somewhere hear to discuss weird things about the universe | |
| 16:09:51 | dtantsur | then one sage decided he was sick of them, and everything went south | |
| 16:09:58 | dtantsur | true story | |
| 16:11:42 | elmiko | haha | |
| 16:11:46 | dtantsur | I don't mind not doing much in the near future, since we're planning a move for autumn (getting closer to gtema I guess :) | |
| 16:11:57 | elmiko | nice | |
| 16:12:03 | gtema | really? where to? | |
| 16:12:24 | dtantsur | gtema: Dusseldorf (RE distance from you, I think) | |
| 16:12:46 | gtema | yeah | |
| 16:13:02 | gtema | RH relocation? | |
| 16:13:10 | dtantsur | nope (I'm remotee), rather personal | |
| 16:13:18 | gtema | ok | |
| 16:16:27 | dtantsur | API related story: ironic is slowly (really slowly) starting a move to Flask. any tips and tricks are welcome! | |
| 16:16:56 | gtema | Flask for what? API serving? | |
| 16:17:22 | elmiko | i guess it depends on what kind of tips and tricks you are looking for, but my main tip is to use MethodView classes for routing | |
| 16:17:33 | edleafe | I don't see how using Flask would change the approach to API design | |
| 16:17:41 | elmiko | ++ | |
| 16:17:56 | gtema | me too, was having nice experience with Blueprints | |
| 16:18:12 | elmiko | yeah, ++ to blueprints as well | |
| 16:18:38 | elmiko | i think the flask docs get you up and running quickly, but the @route decorator pattern is sub-optimal imo | |
| 16:19:05 | gtema | ++ | |
| 16:19:29 | dtantsur | I'm not looking for anything specific, just a quick poll of opinions | |
| 16:20:12 | gtema | opinion - worth a try | |
| 16:20:49 | dtantsur | okay cool. next question: who could lend me a human cloning machine? | |
| 16:20:57 | edleafe | I love FLask, but only have a few simple apps that @route serves well | |
| 16:21:03 | elmiko | yeah, i'm ++ on flask. i love it | |
| 16:21:41 | dtantsur | same. and I don't like the wsme+pecan pair a lot | |
| 16:21:50 | gtema | I wish I had one - need it myself | |
| 16:21:57 | elmiko | yeah, i have very mixed feelings about pecan | |
| 16:22:03 | gtema | wrt to clone-maching | |
| 16:22:04 | edleafe | You could always use my insect cloning machine - just be sure to clean it well first | |
| 16:22:09 | dtantsur | lol | |
| 16:22:34 | dtantsur | my motivation to work on that is that I'm one of the two unfortunate people keeping wsme (barely) floating | |
| 16:23:14 | edleafe | I can give you a concrete block to help it sink faster! | |
| 16:25:23 | dtantsur | it does pretty good job sinking on its own :D | |
| 16:53:56 | mordred | dtantsur|afk: I also think kmalloc may have done something something flask something something over in keystone land - or at least started looking at it | |
| 16:54:09 | kmalloc | ohhai | |
| 16:54:18 | kmalloc | i'm here, let me read up. | |
| 16:54:57 | mordred | dtantsur|afk, gtema: I pushed up a couple of readme fixes - https://review.opendev.org/#/c/674045 and https://review.opendev.org/#/c/674041 if you get bored | |
| 16:55:12 | gtema | bored????????? | |
| 16:55:24 | gtema | there are not enough "?" signs on my keyboard | |
| 16:57:10 | mordred | gtema: :) | |
| 16:57:11 | kmalloc | magic in route/etc) | |
| 16:57:11 | kmalloc | dtantsur|afk, gtema: we moved 100% over to flask in Keystone from the home-brewed WSGI framework. We use blueprints and wired up a mechanism to auto-populate routes (now, we had another challenge, we also aimed for zero test changes to make the conversion, and mostly succeeded). I am really against @route, but you can directly call the underlying functions/methods to populate the routes. (I prefer explicit vs decorator | |
| 16:57:29 | edleafe | Take care everyone - gotta head out for a bit | |
| 17:00:22 | gtema | can we somewhen introduce something something like 'take this cloud configuration, but get a domain scoped token'? I am tired of doubling lots of my entries in clouds.yaml to differentiate between project and domain scope | |
| 17:01:13 | gtema | best would be that OSC knows itself which kind of token it need to obtain, but in the worst case "openstack --os-cloud my_cloud --scope domain user list" | |
| 17:01:25 | elmiko | later edleafe o/ | |
| 17:16:45 | dtroyer | gtema: I've pondered something related for a while, when creating otherwise-identical entries in clouds.yaml save for the username/password. Would a zuul-like inheritance mechanism solve your issue? | |
| 17:17:08 | dtroyer | I have not actually looked in to doing anything like that but it sounds like it might me useful in other cases | |
| 17:18:23 | gtema | honestly I would really love to avoid doubling entries in clouds.yaml. From the user perspective he should not even know why this is different | |
| 17:18:50 | gtema | best way really apps (SDK, OSK, etc) are able to figure out themselves what they need to achieve task | |
| 17:19:47 | gtema | so while inheritance works, I do not think it is easy to implement and would improve experience | |
| 17:22:00 | gtema | overall I think it should be sufficient for the customer to specify domain_name, project_name, user, pass. Everything else should be handled by tools themselves | |
| 17:22:47 | gtema | gophercloud also forces me to give IDs in some cases. I hate this also, since I need to figure out it first | |
| 17:26:25 | gtema | ok, need to finish for today. Will read back tomorrow if anyone have ideas | |
| 18:18:12 | openstackgerrit | Matt Riedemann proposed openstack/python-openstackclient master: Fix |
|
| 19:11:53 | openstackgerrit | Monty Taylor proposed openstack/openstacksdk master: Make swift proxy stop trying to version discover https://review.opendev.org/674110 | |
| 19:13:13 | mordred | kmalloc: ^^ | |
| 19:13:24 | openstackgerrit | Matt Riedemann proposed openstack/python-openstackclient master: Add openstack server create --boot-from-volume option https://review.opendev.org/674111 | |
| 19:13:36 | mriedem | mordred: dtroyer: as discussed at the forum ^ | |
| 19:13:40 | mriedem | wip until i test it in devstack | |
| 19:13:57 | mordred | kmalloc: we were too good in keystoneauth with the discovery and I cannot for the life of me figure out a better way to get things to not try to find another url for swift | |
| 19:14:13 | mordred | kmalloc: I mean - it's functional - it's just an additional roundtrip that we know is never going to work | |
| 19:14:23 | kmalloc | lol | |