Earlier  
Later
New Search
Posted Nick Remark
#openstack-sdks - 2019-07-24
18:14:30 openstackgerrit Artem Goncharov proposed openstack/openstacksdk master: Fix image deletion with tasks_api enabled https://review.opendev.org/672573
18:14:44 gtema Shrews: ^^^
18:44:01 openstackgerrit Matt Riedemann proposed openstack/python-openstackclient master: WIP: Fix compute service set handling for 2.53+ https://review.opendev.org/672577
19:12:47 openstackgerrit Artem Goncharov proposed openstack/openstacksdk master: Rework statistics reporting https://review.opendev.org/659841
19:15:53 Shrews mordred: gtema did a thing https://review.opendev.org/672573
19:16:20 Shrews thx gtema
19:17:01 gtema welcome. Hope it helps. If I can help debugging those image issues for nodepool - let me know, will try as much as time allows
19:24:21 mordred gtema: thanks! +A - looks solid
19:24:49 mordred gtema: I landed a few more of the reorg patches this morning - sorry that's taking so long
19:25:25 gtema no problem. I'm myself terribly busy last month with my "API-Monitoring" project :-)
19:34:32 mordred :)
19:35:55 openstackgerrit Artem Goncharov proposed openstack/openstacksdk master: Volume.Backup restore fixes https://review.opendev.org/665110
21:17:06 openstackgerrit Merged openstack/openstacksdk master: Fix image deletion with tasks_api enabled https://review.opendev.org/672573
22:46:57 openstackgerrit Riccardo Pittau proposed openstack/openstacksdk master: Add node traits support to baremetal https://review.opendev.org/672233
22:49:02 openstackgerrit Riccardo Pittau proposed openstack/openstacksdk master: Add node traits support to baremetal https://review.opendev.org/672233
#openstack-sdks - 2019-07-25
02:20:18 openstackgerrit Merged openstack/openstacksdk master: Add set-boot-device to baremetal https://review.opendev.org/672190
06:13:12 openstackgerrit Brin Zhang proposed openstack/python-openstackclient master: openstack port create support --extra-dhcp-option https://review.opendev.org/657519
09:50:27 openstackgerrit Artem Goncharov proposed openstack/openstacksdk master: Rework statistics reporting https://review.opendev.org/659841
09:57:42 openstackgerrit Artem Goncharov proposed openstack/openstacksdk master: Volume.Backup restore fixes https://review.opendev.org/665110
14:03:24 openstackgerrit Riccardo Pittau proposed openstack/openstacksdk master: Add node traits support to baremetal https://review.opendev.org/672233
14:30:32 openstackgerrit amolkahat proposed openstack/openstacksdk master: Added missing {user, project}_domain_name in Api https://review.opendev.org/672740
15:33:07 openstackgerrit LIU Yulong proposed openstack/python-openstackclient master: Add floating IP Port Forwarding commands https://review.opendev.org/650062
16:00:00 edleafe Have your tickets ready! The API-SIG Office Hour is starting now!
16:00:33 elmiko \o/
16:12:04 elmiko yay
16:17:50 cdent oh crikey
16:17:55 cdent i forgot all about saying that
16:18:09 edleafe cdent: that's what happens when you get old
16:18:21 elmiko haha
16:18:32 cdent so old
16:18:47 cdent I was privately invited to gaze upon https://review.opendev.org/#/c/658954/ as a wizend api person
16:19:01 cdent The solution was pretty straightforward, and I wrote thusly
16:19:18 cdent I thought about looking to see if there was existing guidance but never got around to it (c.f. old)
16:20:09 elmiko that doesn't sound familiar, but seems like a reasonable thing to add (guidance-wise)
16:21:22 edleafe cdent: good point. I had forgotten about ';'
16:23:00 cdent so yeah, there were are
16:34:46 dtantsur yeah, I remember discussions around this feature in another context
16:34:58 openstackgerrit Riccardo Pittau proposed openstack/openstacksdk master: Add node traits support to baremetal https://review.opendev.org/672233
17:00:23 elmiko edleafe, dtantsur|afk, stay cool out there, have a nice weekend =)
17:00:39 edleafe c ya, elmiko
18:15:56 openstackgerrit Matt Riedemann proposed openstack/python-openstackclient master: Fix compute service set handling for 2.53+ https://review.opendev.org/672577
18:30:38 openstackgerrit Matt Riedemann proposed openstack/python-openstackclient master: Document 2.53 behavior for compute service list/delete https://review.opendev.org/672807
#openstack-sdks - 2019-07-26
03:13:49 openstackgerrit yanpuqing proposed openstack/cliff master: Modify the help message of `-c`/`--column` parameter https://review.opendev.org/672852
08:26:29 openstackgerrit Artem Goncharov proposed openstack/openstacksdk master: Rework statistics reporting https://review.opendev.org/659841
08:38:31 openstackgerrit Akihiro Motoki proposed openstack/python-openstackclient master: Fix module paths for volumev3 volume backup commands https://review.opendev.org/672914
08:48:10 openstackgerrit Akihiro Motoki proposed openstack/openstackclient master: check-plugins job: Fix pbrx path https://review.opendev.org/672918
08:49:52 openstackgerrit Akihiro Motoki proposed openstack/openstackclient master: check-plugins job: Fix pbrx path https://review.opendev.org/672918
09:38:06 openstackgerrit Vishakha Agarwal proposed openstack/openstacksdk master: Add application credential CRUD support https://review.opendev.org/669331
09:39:32 openstackgerrit Dmitry Tantsur proposed openstack/keystoneauth master: Allow requesting fixed retry delay instead of exponential https://review.opendev.org/672930
09:39:41 dtantsur mordred, efried, something we discussed some time ago ^^
10:14:04 openstackgerrit Akihiro Motoki proposed openstack/openstackclient master: check-plugins job: convert the job to tox https://review.opendev.org/672942
10:58:56 openstackgerrit Akihiro Motoki proposed openstack/openstackclient master: check-plugins job: switch to python3 https://review.opendev.org/672949
11:37:51 efried dtantsur: a couple of notes, but +1. Nice and clean.
11:37:59 dtantsur thx!
11:50:15 mordred dtantsur: I agree with efried - but I think all of those are things that could be done in a followup
11:50:55 dtantsur cool, I'll see what other folks think
14:44:55 amotoki dtroyer: I just started to check python3 status in OSC. Is anyone checking it?
14:45:17 amotoki dtroyer: I started check-plugins job in the openstack/openstackclient repo https://review.opendev.org/#/q/project:openstack/openstackclient+topic:switch-to-py3+(status:open+OR+status:merged)
14:45:49 amotoki dtroyer: if someone is working on py3 stuff, I would like to sync with them.
15:14:32 dtroyer amotoki: we've been py3 clean for a long time, I use it locally only in py3. I saw those reviews, thanks for catching that, it was just missed
15:21:35 tosky dtroyer: talking about check-plugins... do you rememer our old discussion about openstackclient-check-plugins failing on older stable branches? Do you think that those changes may fix them?
15:29:29 dtroyer tosky: I vaguely recall that, but am fairly certain it will not make a difference unless amotoki did that in the stable branches too
15:30:11 tosky dtroyer: the problem is exactly that openstackclient.git has no stable branches
15:30:45 dtroyer oh, duh, I alwasy do that, right different repo…
15:32:11 tosky dtroyer: this is the last discussion about this: http://eavesdrop.openstack.org/irclogs/%23openstack-sdks/%23openstack-sdks.2019-03-04.log.html#t2019-03-04T21:23:09
15:32:28 tosky with the links to the previous discussions :)
15:44:57 amotoki dtroyer: thanks. I am using py3 by default locally these days. perhaps what we need to check is just about CI jobs (though most have been done perhaps)
15:46:20 amotoki dtroyer: tosky: regarding openstackclient-check-plugins, the main purpose of the job is to check command duplicates. Taking into account our stable policy, it looks like that the job needs to be run only in the master branch.
15:47:12 tosky amotoki: oh
15:47:41 tosky well, that would be a solution as well; what I see now is a set of red jobs and they should be either fixed or removed
15:48:49 amotoki tosky: this is what the current version of openstackclient-check-plugins checks, so it sounds reasonable to drop it from the stable branches up to stein.
15:49:14 amotoki tosky: our stable policy does not allow to add new commands :)
15:55:05 openstackgerrit Artem Goncharov proposed openstack/openstacksdk master: Rework statistics reporting https://review.opendev.org/659841
16:28:48 openstackgerrit Artem Goncharov proposed openstack/openstacksdk master: Rework statistics reporting https://review.opendev.org/659841
21:43:05 openstackgerrit Dean Troyer proposed openstack/python-openstackclient master: Make configuration show not require auth https://review.opendev.org/673110
#openstack-sdks - 2019-07-27
18:10:03 openstackgerrit Yuval Shalev proposed openstack/openstacksdk master: Added all-projects headers option to dns proxy. https://review.opendev.org/669547
20:42:56 openstackgerrit Dean Troyer proposed openstack/python-openstackclient master: Make configuration show not require auth https://review.opendev.org/673110
#openstack-sdks - 2019-07-28
10:31:31 openstackgerrit LIU Yulong proposed openstack/python-openstackclient master: Add floating IP Port Forwarding commands https://review.opendev.org/650062
#openstack-sdks - 2019-07-29
09:48:54 openstackgerrit Merged x/promstat master: Remove publishing to docs.openstack.org https://review.opendev.org/672058
11:07:51 openstackgerrit Dmitry Tantsur proposed openstack/keystoneauth master: Allow requesting fixed retry delay instead of exponential https://review.opendev.org/672930
16:13:27 mriedem dtroyer: mordred: following up (way later) on the osc compute api gaps forum discussion in denver, i've created a story for making boot-from-volume better in osc https://storyboard.openstack.org/#!/story/2006302,
16:13:33 mriedem the tasks are in order,
16:13:44 mriedem and i have questions on the implementation of the 2nd one that adds a --boot-from-volume option
16:14:15 mriedem tl;dr i want to just do: openstack server create --flavor $flavor --image $image --boot-from-volume $server-name
16:14:25 mriedem the problem is you have to pass a size for the volume that nova will create from the image,
16:14:39 mriedem i think the easiest solution is just make the --boot-from-volume option take a size value
16:14:48 mriedem so: openstack server create --flavor $flavor --image $image --boot-from-volume 1 $server-name
16:14:56 mriedem that would create a 1GB volume from the given image
16:16:02 mriedem the image has some properties which we could maybe use, like min_disk, but they are all optional so i don't have much confidence on relying on the image *size properties.
16:16:22 mordred mriedem: fwiw, the API in sdk is boot_from_volume=True, volume_size=1 - it's that way because it's also possible to do boot_from_volume=True, boot_volume=some_volume
16:16:41 mordred I would not rely on min_disk from the image
16:16:43 mriedem osc already has a --volume option which is in a mutex with --image
16:16:53 mordred nod
16:16:53 mriedem so i think the cli is already covered there
16:17:03 mriedem in that case nova doesn't create a volume since the user is providing it
16:17:16 mordred then sure - I think a number argument to boot_from_volume seems like a fine idea
16:17:25 mriedem ack, i'll start with that anyway
16:21:43 dtroyer mriedem: I think I am ok with that, but I don't have that all in my head at the moment… it seems to map to the API fine
16:24:24 mriedem oh also, i'm going to first add type=image as an option for --block-device-mapping; the question there is if --image is specified along with --block-device-mapping vda:$image_id:image:1:true - do we validate the --image id against the block device image id? fail if they are different? make --image optional if an image bdm is specified? make the bdm a non-root volume if --image is specified and the ids are different?
16:24:48 mriedem i can take this to the ML if you want wider input and/or time to mull the options

Earlier   Later