Earlier  
Posted Nick Remark
#openstack-sdks - 2019-06-25
10:16:39 openstackgerrit Bogdan Dobrelya (bogdando) proposed openstack/openstacksdk master: DNM - Start building pdfs of docs https://review.opendev.org/601659
13:09:44 goldyfruit Hi guys
13:10:58 goldyfruit I would like to know if it's possible with the openstack client to have to required option but if one of them is used then the other one is not required anymore
13:11:02 goldyfruit I read this: https://docs.openstack.org/python-openstackclient/latest/contributor/command-options.html
13:11:46 goldyfruit I see the metavar/required but if I configure the two options with these two parameters then they are both required
13:26:36 efried goldyfruit: Pretty sure that kind of conditional requirement can't be handled at the argparse level - you would have to do a manual check.
13:27:19 efried but no idea if some kind of framework has been built into osc itself -- dtroyer?
13:28:40 goldyfruit efried, thanks :)
15:06:08 openstackgerrit Bogdan Dobrelya (bogdando) proposed openstack/openstacksdk master: DNM - Start building pdfs of docs https://review.opendev.org/601659
#openstack-sdks - 2019-06-26
02:18:41 openstackgerrit ZhaoBo proposed openstack/openstacksdk master: force specify project_id during create Sg_rule may cause issue https://review.opendev.org/667261
02:34:51 openstackgerrit pengyuesheng proposed openstack/openstacksdk master: Add Python 3 Train unit tests https://review.opendev.org/667494
14:59:07 edleafe Bonus! Today the API-SIG Office Hour will be an extra minute long, starting now!!
15:02:39 edleafe Doh! My calendar tricked me! It's not until tomorrow!
16:07:06 elmiko tsk tsk edleafe ...
16:07:17 elmiko XD
22:44:25 openstackgerrit Corey Bryant proposed openstack/keystoneauth master: Add Python 3 Train unit tests https://review.opendev.org/667747
#openstack-sdks - 2019-06-27
16:00:04 edleafe The API-SIG Office Hour is happening NOW!
16:04:40 elmiko \o/
16:50:03 edleafe Hey elmiko - don't know if you'll be around on the 4th, but I'll be on PTO all next week
16:51:09 elmiko edleafe: ack, yeah, i will be out thurs/fri. should we send an email about no hours next week?
16:51:24 elmiko i /think/ dmitry will be out as well
16:51:24 edleafe Sure - thanks for volunteering! :)
16:51:27 elmiko ++
16:53:18 elmiko done
17:00:08 elmiko have a nice pto next week edleafe o/
17:00:29 edleafe I sure will!
17:00:44 edleafe Don't misbehave while I'm not around
17:04:25 elmiko who... me? <.< >.>
17:18:59 openstackgerrit James E. Blair proposed openstack/openstacksdk master: Replace nodepool func jobs https://review.opendev.org/667992
18:28:57 mgariepy hello, i wonder if we can backport https://review.opendev.org/#/c/655889 to older branches (possibly down to queens) ?
#openstack-sdks - 2019-06-28
21:53:56 openstackgerrit melanie witt proposed openstack/python-openstackclient master: Fix BFV server list handling with --name-lookup-one-by-one https://review.opendev.org/668255
22:06:45 openstackgerrit melanie witt proposed openstack/python-openstackclient master: Fix BFV server list handling with --name-lookup-one-by-one https://review.opendev.org/668255
#openstack-sdks - 2019-06-29
13:29:07 openstackgerrit Artem Goncharov proposed openstack/openstacksdk master: Volume.Backup restore fixes https://review.opendev.org/665110
13:33:48 openstackgerrit Artem Goncharov proposed openstack/openstacksdk master: WIP Use resource layer for compute.server cloud methods https://review.opendev.org/664593
#openstack-sdks - 2019-07-01
03:03:06 openstackgerrit LIU Yulong proposed openstack/python-openstackclient master: Add floating IP Port Forwarding commands https://review.opendev.org/650062
03:16:09 openstackgerrit LIU Yulong proposed openstack/python-openstackclient master: Add floating IP Port Forwarding commands https://review.opendev.org/650062
07:08:25 openstackgerrit pengyuesheng proposed openstack/python-openstackclient master: Add Python 3 Train unit tests https://review.opendev.org/668364
07:13:35 openstackgerrit pengyuesheng proposed openstack/python-openstackclient master: Update the constraints url https://review.opendev.org/668366
11:23:21 openstackgerrit inspurericzhang proposed openstack/shade master: Mailing lists change openstack-dev to openstack-discuss https://review.opendev.org/668438
11:33:08 openstackgerrit inspurericzhang proposed openstack/js-openstack-lib master: Mailing lists change openstack-dev to openstack-discuss https://review.opendev.org/668444
13:22:19 openstackgerrit Merged openstack/openstacksdk master: Replace nodepool func jobs https://review.opendev.org/667992
19:09:10 openstackgerrit Matt Riedemann proposed openstack/python-openstackclient master: docs: clarify compute service --service option https://review.opendev.org/668550
20:12:21 openstackgerrit Merged openstack/keystoneauth master: Add Python 3 Train unit tests https://review.opendev.org/667747
20:23:54 corvus dtantsur, mordred: would you mind reviewing https://review.opendev.org/667993 (it's a backport which is identical to 667992 which you just approved/merged -- thanks!)
20:24:46 mordred corvus: looks great
20:25:18 mordred corvus: the new nodepool job we've approved - does it use openstacksdk from source in the nodepool installation?
20:25:49 corvus mordred: yes (the -src variants do)
20:26:11 mordred awesome
20:40:36 corvus don't think it's urgent?)
20:40:36 corvus mordred: i did cut corners on the dogpile cache -- i had a lot of trouble getting it set up for some reason (even though i was copying what was in the devstack plugin), so it's not currently enabled (though it is still installed from source). that was pretty early on though, it's possible things are better enough we can just turn it back on. that's worth another look now that you're back (but i
20:42:50 mordred corvus: yeah - I also don't think it's urgent - I think that whole layer needs a good amount of work
#openstack-sdks - 2019-07-02
15:08:43 openstackgerrit LIU Yulong proposed openstack/python-openstackclient master: Add floating IP Port Forwarding commands https://review.opendev.org/650062
#openstack-sdks - 2019-07-03
00:09:05 openstackgerrit Merged openstack/python-openstackclient master: Update the constraints url https://review.opendev.org/668366
04:03:31 openstackgerrit Merged openstack/python-openstackclient master: Add Python 3 Train unit tests https://review.opendev.org/668364
06:50:07 openstackgerrit zhufl proposed openstack/openstacksdk master: Fix invalid assert state https://review.opendev.org/668794
12:21:06 brtknr priteau: mordred gtema mnaser
12:22:23 priteau Hi folks. I submitted a patch to Ansible about a month ago to fix an error when no volume service is available. Would anyone be able to review it? https://github.com/ansible/ansible/pull/57364
12:46:00 mordred priteau: lgtm
12:50:47 priteau Thanks mordred
13:31:47 cdent dtroyer: if you have a moment to gaze on an osc-placement naming discussion, that would be helpful: https://review.opendev.org/666542
13:31:49 cdent also: hi
13:41:59 dtroyer cdent: oh that looks like a fun one, thanks ;)
13:42:13 cdent dtroyer: I'm all about fun for you
13:42:44 cdent I suspect placement's nature as "mostly admin" gives it a bit off leeway
13:43:09 dtroyer (just thinking out loud here) I am not much of a fan of complex queries build from CLI options, if you need a complex query, build a DSL for that?
13:43:21 dtroyer in OSC so far we have mostly gotten away with that
13:46:28 dtroyer using the options to detect/attempt specific API microversions in itself is fine with me, sometimes it can be obvious, but that in: magic doesn't sit well with me. I don't like options with values that contain keywords but that turned out to be unavoidable in some places, so there is a bit of precedent for how those should look
13:49:05 dtroyer so if I read that right the review is basically a straight port of the REST API semantics to the cli options?
14:13:55 mordred CLI arguments like "--member-of in:<uuid1>:<uuid>" give me hives
14:14:55 mordred passing complex need-to-be-parsed data structures is hard to deal with on the CLI (although makes sense in the REST API itself) - and invariably gets really brittle (see anything related to block_device_mapping)
14:15:14 mordred (which I think is me saying I agree with dtroyer :) )
14:17:11 mordred I'd rather see multiple options - like --member-of <uuid1> --member-of <uuid2> to make the && case like mentioned, but then maybe like --member-in <uuid> --member-in <uuid2> to construct member_of="in:uuid1:uuid2" ... but that's just off the top of my head, and I'm not sure how weird that woudl be to actually use
14:17:50 mordred or, heck - a --member-in <uuid1>,<uuid2> would bother me less than the in: prefix
14:18:28 mordred maybe I should say some of that in the review ...
14:19:05 cdent dtroyer: sorry, stepped away. the suggestion from gibi is to do a straight port of the new microversin
14:19:16 cdent and for the most part that's what's been doing in several places, but...not always
14:19:22 cdent thus leading to the current confusion
14:31:42 dtroyer cdent: in meeting now, part way writing a reply in the review. In short, the implicit AND/OR operators are confusing and I don't think OSC has a clear precedent there. Multiple —property options are effectively an AND in create/set commands for example…
14:32:34 cdent yes, that confusion is why I think explicitly copying the query structure (which is at least somewhat documented and familiar to people who will even care to use that specific microversion)
14:33:06 cdent I suspect we are overthinking this because we are trying to incrementally support microversions, rather than simply support use cases
14:33:29 cdent we can already filter resource providers by aggregate membership
14:33:41 cdent and the need to do complex booleans, I would think, is rather rare
14:33:57 cdent so I'd almost be inclined to say "we don't do what 1.24 supports"
14:34:43 cdent dtroyer: this keeps happening with osc-placement but I'm hard pressed to believe that it is actually necessary
14:35:13 cdent people who want advanced filtering functionality should perhaps be able to pass a raw filter query, exactly as it would be formed in the URL
14:35:36 cdent and there should also be simple things (as there already are)
14:45:48 dtroyer cdent: we outlined a basic method for passing in structured data for doing things like bulk create operations at PTG, using that (once it is written) for queries seems logical…
16:03:44 openstackgerrit Sergey Vilgelm proposed openstack/keystoneauth master: OIDC supports public clients https://review.opendev.org/668951
17:47:10 openstackgerrit Merged openstack/os-service-types master: Sync Sphinx requirement https://review.opendev.org/666384
#openstack-sdks - 2019-07-05
07:27:43 ITD27M01 Hi Guys. Who can help me with cache feature in OpenStack SDK? I did not understand how it works. If cache enabled in "clouds.yaml", then the list_servers always return an empty collection.
07:28:52 gtema ITD27M01 I recommend not to really use cache at the moment. We are thinking how to "fix" it. Basically currently you need to have also "memcached" running to be able to use it
07:29:01 gtema of cource file based works as well
07:29:17 gtema but it only works from the cloud layer, and not proxy/resource
07:30:51 ITD27M01 gtema: I tried different classes - memory, memcached and pylibmc but the behavior is the same.
07:31:51 gtema hmm, it works for me. But I prefer not to use it at all. From my POV as of now it make sense only for flavors
07:31:53 ITD27M01 gtema: connection.list_servers is a cloud layer ?
07:31:59 gtema yes, it is
07:33:38 gtema can you please share somehow your clouds.yaml cache section?
07:34:02 openstackgerrit zhangqing proposed openstack/python-openstackclient master: Fix cliff formattable columns in volume type https://review.opendev.org/669280
07:34:52 ITD27M01 gtema: Yes, few seconds please.

Earlier   Later