Earlier  
Posted Nick Remark
#openstack-nova - 2019-10-14
11:11:17 openstackgerrit Merged openstack/nova master: setup.cfg: Cleanup https://review.opendev.org/677969
11:15:00 SonPham gibi what is his nick's name in IRC chat?
11:15:24 gibi SonPham: 'efried_pto' now, 'efried' when he is not on vacation
11:16:16 SonPham ok thanks
11:25:57 openstackgerrit Balazs Gibizer proposed openstack/nova master: Allow evacuating server with port resource request https://review.opendev.org/688387
11:34:25 openstackgerrit Balazs Gibizer proposed openstack/nova master: Allow evacuating server with port resource request https://review.opendev.org/688387
11:35:39 openstackgerrit Stephen Finucane proposed openstack/nova master: Stop testing Python 2 https://review.opendev.org/687954
11:35:40 openstackgerrit Stephen Finucane proposed openstack/nova master: Remove unused 'nova-dsvm-base' job https://review.opendev.org/688389
11:37:51 sean-k-mooney stephenfin: i think your topic is incorrect on https://review.opendev.org/#/c/687954/5
11:38:11 stephenfin Yes. Yes it is :D
11:38:37 stephenfin fixed
11:38:46 sean-k-mooney you need to fix the follow up patch too
11:38:59 sean-k-mooney but cool
11:40:13 bauzas kashyap: /me clicks on the stable change
11:41:00 openstackgerrit Stephen Finucane proposed openstack/nova master: Remove unused 'nova-dsvm-base' job https://review.opendev.org/688389
11:41:21 bauzas hah, queens backport
11:44:09 bauzas https://releases.openstack.org/
11:44:09 bauzas kashyap: FWIW, the queens branch will become on Extended Maintenance in around 3 weeks :)
11:44:26 bauzas Queens Maintained 2018-02-28 Extended Maintenance estimated 2019-10-25
11:47:57 openstackgerrit Arthur Dayne proposed openstack/nova master: libvirt:volume:Disallow AIO=native when no 'O_DIRECT' is available https://review.opendev.org/682772
11:55:50 kashyap bauzas: Yeah, I'm aware of that. And thank you! :-)
12:49:05 alex_xu stephenfin: gibi efried_pto, just try to kick off the work https://etherpad.openstack.org/p/nova-train-release-project-update
12:50:37 gibi alex_xu: good initiative! I will check the etherpad out
12:50:46 alex_xu gibi: thanks
13:32:51 openstackgerrit Sundar Nadathur proposed openstack/nova-specs master: Updated Nova-Cyborg interaction spec. https://review.opendev.org/684151
13:38:40 openstackgerrit Balazs Gibizer proposed openstack/nova master: Allow evacuating server with port resource request https://review.opendev.org/688387
14:06:38 openstackgerrit Merged openstack/nova stable/queens: libvirt: Rework 'EBUSY' (SIGKILL) error handling code path https://review.opendev.org/668111
14:09:09 dansmith mriedem: https://review.opendev.org/#/c/633293 needs a rebase and compute rpc bump because of me... sorry :(
14:09:49 mriedem just replied on that one and noticed
14:10:04 mriedem don't worry, not my first rodeo chasing compute rpc version bumps on that series
14:10:21 mriedem you also have to rebase your api change and address some stuff in it :)
14:11:46 mriedem i misunderstood your question about the long rpc call
14:11:55 mriedem thought you were asking why it was a call and not a cast
14:12:53 openstackgerrit Stephen Finucane proposed openstack/nova master: Remove compute compat checks for aborting queued live migrations https://review.opendev.org/688409
14:12:55 dansmith mriedem: no, I was asking why a long call and not a regular call
14:13:02 mriedem yeah i realized
14:13:15 mriedem i don't have a good answer except it's what i did in all the new compute methods in this series
14:13:51 dansmith heh okay, like I said, I'm not sure there's a reason *not* to do it really, other than just signaling that some of them are expected to run *really* long
14:14:01 dansmith well, and I guess there's a teensy bit of messaging overhead
14:14:23 bauzas mriedem: just saw this morning that Queens will be on Extended Maintenance in 3 weeks, so maybe we should look at https://review.opendev.org/#/q/status:open+project:openstack/nova+branch:stable/queens ?
14:15:09 dansmith mriedem: I guess I thought the point of the schema was so we didn't have to test for things that the schema would reject for us
14:15:15 dansmith well, one of the points of the schema
14:15:37 mriedem we still have to test that we defined the schema correctly
14:15:38 dansmith isn't that like kinda like silly tests that are actually only testing that mock is working?
14:15:46 dansmith okay
14:16:03 mriedem and i'd say to prevent regressions in later microversions on the same api
14:16:53 dansmith okay, that's fine it just seems inconsistent with what we do elsewhere, like we don't check that when you define an object field as int that a string will blow it up :)
14:17:54 mriedem i've seen and i'm pretty used invalid schema before adding tests to validate it so it's a more complicated thing than type checking
14:17:59 mriedem *pretty sure
14:18:06 dansmith ah dammit, I really wanted 2.80
14:18:44 dansmith also, I haven't had to write one of these in a long time, but it really sucks to have to do so much work if you miss your microversion
14:18:45 mriedem bauzas: join the party i guess, it's usually a party of 1
14:19:12 dansmith I wish we could do something better there
14:20:10 mriedem i don't thinking the microversion stuff can be reasonably automated
14:20:12 mriedem *think
14:20:23 mriedem coffee hasn't kicked into my brain yet
14:20:34 dansmith well, it would take some changes in our workflow I think
14:20:39 dansmith I know it's not trivial
14:29:21 efried o/ nova
14:30:12 efried alex_xu, stephenfin, gibi: I copied the Denver proj update to a new google slide thingy. PM me whatever email address you have a google account for and I'll add you to editors.
14:35:22 dansmith gmann: can you help me decipher mriedem's request here? or point me at what something new looks like that I can copy? https://review.opendev.org/#/c/687140/5/nova/tests/unit/test_policy.py@312
14:39:03 gmann dansmith: yeah, we can use the new naming standard for new policy. EX -https://github.com/openstack/nova/blob/master/nova/policies/server_topology.py#L19
14:39:45 dansmith gmann: oh meaning just s/os-// ?
14:40:13 mriedem decipher :/
14:40:26 mriedem i said "compute:aggregates:images" or "compute:aggregates:images:cache"
14:40:37 dansmith okay, I dunno what I was thinking last week, but reading it this morning he *did* tell me what to type
14:40:52 gmann "compute:aggregates:images:cache" seems perfect
14:41:01 dansmith mriedem: yeah I dunno, sorry I read that a couple times last week and it seemed like you were waffling on what you thought it should be and my eyes glazed over
14:41:34 mriedem i was only waffling on making it specific to the cache action for future actions like purge
14:42:10 dansmith I probably didn't see that the os- was removed, so it looked like what I had and I assumed I was missing something bigger
14:42:31 bauzas mriedem: sure, will do
14:42:32 openstack Launchpad bug 1847759 in tempest "reboot_server_hard can trigger corrupted file system" [Undecided,New]
14:42:32 frickler mriedem: did you see the thing I noticed last week? I'm assuming you might like that one, too ;) https://bugs.launchpad.net/tempest/+bug/1847759
14:42:51 dansmith having one operation in aggregates be different from the rest seems unhelpful to admins, but I'm more than happy to just do whatever as I don't know anything about this stuff
14:43:22 mriedem dansmith: i believe gmann has an approved blueprint to re-write all of those policy rules so it's just less work when he does
14:43:30 dansmith ack
14:43:36 mriedem frickler: i didn't
14:44:16 gmann naming change for existing policy we dropped from policy improvement spec but for new one we can follow the new naming standard
14:44:58 gmann at least not part of scope+new read-only defaults spec
14:45:03 mriedem frickler: i've definitely seen this in the gate jobs that have ssh failures "cp: write error: No space left on device"
14:45:17 mriedem frickler: http://status.openstack.org/elastic-recheck/#1808010
14:47:22 frickler mriedem: yes, the "no space left" is pretty generic, though, this one seems directly tied to hard reboots and the resulting corruption causing kernel panics
14:47:46 gmann but yes, i wanted to change all old name but that is something needs to be discussed if worth to do or not from operator perspective. this will be separate spec
14:48:18 mriedem dansmith: so we haven't done this for train yet - https://review.opendev.org/#/c/642599/ - does that need to be in train?
14:48:26 mriedem or is ok for just ussuri?
14:48:28 mriedem *is it
14:49:02 frickler mriedem: so I'd say it is not a duplicate, but a specific subset of it, tied to a single test scenario
14:49:03 mriedem gmann: renaming all of the old policy rules seems like a ton of churn for not much gain
14:49:09 mriedem frickler: ack
14:50:16 dansmith mriedem: it'd be nice for it to be in train eventually in case anyone sets their train level to train in an attempt to bump to current
14:50:37 dansmith mriedem: really they should unpin or use auto, but you can imagine setting train to train meaning current making sense to people
14:50:39 mriedem https://wiki.openstack.org/wiki/Nova/ReleaseChecklist says "Ideally add the RPC version alias just before opening the next release"
14:50:59 mriedem i noticed that the rocky one was added in stein https://review.opendev.org/#/c/589972/
14:51:33 dansmith mriedem: right, that wiki link means like "in rc2 when we know we're not going to be adding anything else to the rpc api"
14:51:43 gmann mriedem: true. initially i added name change as part of other policy changes but then we dropped that as it was changing every policies. i agree that doing it separately is not so much gain.
14:51:51 dansmith mriedem: I think after auto came on the scene we got a little lax about that
14:52:16 dansmith mriedem: and certainly people using a numbered version that has nothing to do with "train", that word means not very much to them
14:52:28 openstackgerrit Nicolas Belouin proposed openstack/nova master: Add support for Xen PVH VM Mode in libvirt driver https://review.opendev.org/687827
14:54:38 mriedem ok i'd push the patch but i'm rebasing this cross-cell series which will take awhile,
14:54:42 mriedem if someone else wants to push it i'd +2

Earlier   Later