Earlier  
Posted Nick Remark
#openstack-nova - 2019-08-08
17:14:40 mriedem there is no series goal in launchpad b/c we don't know what the name of the release is going to be
17:14:55 sean-k-mooney but i was wondering if the openstack Next milstone means next milsteon or next release
17:14:57 mriedem see the shenanigans in the ml
17:15:53 sean-k-mooney mriedem: ya i know i was wondering what "milestone target" was. anyway its in the whiteboard but that is the bluepint for the sriov numa stuff we talked about yesterday
17:16:02 openstackgerrit Artom Lifshitz proposed openstack/nova master: [WIP] Move port ID verification to REST API https://review.opendev.org/675418
17:16:04 mriedem ack
17:16:05 efried mriedem: would the right thing be to kill the sleeping thread?
17:16:16 mriedem efried: yeah something like that
17:16:22 artom Bleah, took forever because I forgot I was in the middle of a rebase, but there ^^
17:16:25 mriedem rather than time.sleep, do a wait/notify or something
17:16:29 artom I'll let CI tell me which unit tests I broke
17:18:38 mriedem easy -1
17:18:40 mriedem :)
17:19:03 artom Dammi, I said [WIP] and everything :P
17:19:17 mriedem i need the stackalytics points
17:20:17 artom What's their exchange rate for real currencies?
17:21:01 sean-k-mooney if review were a crypto currancy mriedem would never need to work again
17:21:05 mriedem half a looney
17:21:48 mriedem i don't review much anymore b/c all anyone pushes up for review these days is low level hw optimizations
17:21:51 sean-k-mooney untill the gpu powered review bot take over and +1 everaything and make the crypto currancy collapes
17:21:56 artom We don't have those, that'd be two caribous
17:22:40 artom mriedem, that's where the money is :/
17:24:10 sean-k-mooney mriedem: given you still the numer 2 reivewer in nova this cycle what would you consider reviewing a lot lol
17:24:40 artom ...
17:24:46 artom Who's number 1 o_O
17:24:59 sean-k-mooney artom: efried currenlty
17:25:13 artom Damn mriedem dude, you're slackin'
17:25:23 artom (You're not, don't worry)
17:25:30 efried yeah, now look at how much code
17:34:24 sean-k-mooney how would peopel feel about using a [U Release] tag in commit title for stuff that is for next cycle
17:35:02 sean-k-mooney e.g. i want to push up some patches but dont really need/want them to be review until we get to U
17:35:41 sean-k-mooney or maybe [next-release]
17:36:00 dansmith how about [WIP] ? :D
17:36:02 sean-k-mooney kindo of like th [WIP] and [DNM] tags we use
17:36:16 dansmith if it's not to be merged right away, then WIP or DNM fit pretty well
17:36:20 sean-k-mooney well [WIP] does not signel its not for train
17:36:26 dansmith no?
17:36:36 dansmith WIP signals to me "you can review this right now, but it's not ready"
17:36:43 dansmith which seems about the same AFAICT
17:36:58 sean-k-mooney ok
17:37:11 sean-k-mooney i can use [WIP] and [DNM]
17:38:46 sean-k-mooney but ya that was the intent. "you can review if you want but this is not planned to be merged soon"
17:39:15 dansmith yup
17:44:01 efried It's not like we have any automation on the tags
17:44:13 efried [WIP:U] would be fine as well
17:44:15 mriedem sean-k-mooney: or just push it up tied to the blueprint and i'll procedurally -2 it
17:44:20 mriedem like we do sometimes for unapproved blueprints
17:44:32 sean-k-mooney sure its just nice to have a convention
17:44:51 sean-k-mooney :) yes that is always an option
17:45:17 openstackgerrit Ghanshyam Mann proposed openstack/nova master: Add test coverage of existing admin_actions policies https://review.opendev.org/657698
18:25:22 sean-k-mooney by the way anyone recognise what package these deprecation warning come from
18:25:24 sean-k-mooney http://paste.openstack.org/show/755668/
18:25:41 sean-k-mooney im guessing oslo somthing
18:26:35 sean-k-mooney https://github.com/openstack/oslo.service maybe
18:28:49 sean-k-mooney oh its form the openstack sdk
18:29:53 sean-k-mooney and mriedem fixed it 6 days ago https://github.com/openstack/openstacksdk/commit/799bd0a773fb082c1a45262922d87630abc9bd30
18:48:06 mriedem yeah, would be nice to get that released, mordred ^
18:48:18 mriedem otherwise we should add a warnings filter to squash that noise from our test logs
18:49:05 mordred mriedem: I have a release request in the releaseteam queue
18:49:17 mriedem cool
18:49:17 mordred mriedem: https://review.opendev.org/#/c/674660/
18:56:50 efried mriedem: gate failures are killinme, any problem if I fast approve those two patches to add logs and skip the test?
18:59:02 mriedem efried: i'm assuming dansmith or melwitt could hit these? https://review.opendev.org/#/q/topic:bug/1839515+status:open
19:00:11 dansmith it hath been done
19:00:16 mriedem danke
19:00:39 efried thanks dansmith
19:03:53 mriedem should see this drop off once that skip merges http://status.openstack.org/elastic-recheck/#1839515
19:06:09 mriedem mordred: +1 on that release request - could have probably been 0.32.1 given the contents but not a big deal when you're <1.0.0
19:08:10 mordred mriedem: yeah - but numbers are cheap too :)
19:15:32 openstackgerrit sean mooney proposed openstack/nova master: [WIP:U] support pci numa affinity policies in flavor and image https://review.opendev.org/674072
19:17:06 tbachman mriedem: Ben Affleck in “The Accountant”
19:17:56 dansmith hah
19:19:09 mriedem tbachman: i thought of that movie too
19:19:13 tbachman heh
19:19:20 mriedem and my neighbor who won't make eye contact
19:19:21 mriedem and is a CPA
19:19:30 tbachman steer clear of them
19:56:51 mriedem lordy test_verify_created_server_ephemeral_disk sometimes takes 5 minutes
19:57:43 sean-k-mooney is that a functional test?
19:58:13 sean-k-mooney or i guess proably a tempest senario test given the lenght
19:58:15 mriedem tempest
19:58:19 mriedem it's not a scenario test, api test
19:58:29 mriedem should probably be a scenario test
19:58:38 sean-k-mooney or at least in the slow set
19:58:43 mriedem gmann: what do you think about dropping the --serial for running scenario tests serially in tempest-integrated-compute ?
19:58:57 mriedem looking at https://logs.opendev.org/78/658478/16/check/tempest-integrated-compute/33847ea/controller/logs/stackviz/#/stdin/timeline?test=tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_hotplug_nic there are only 2 scenario tests that get run
19:59:53 mriedem hmm, why aren't things like test_stamp_pattern and test_volume_boot_pattern running in there?
20:00:13 mriedem oh b/c it's marked slow
20:00:13 mriedem nvm
20:01:27 sean-k-mooney any tests that ssh into a vm shoudl be grouped under senario but ya i guess it could be filtered out
20:01:47 mriedem sean-k-mooney: that's the way things used to be long ago,
20:01:56 mriedem qa team enabled run_validation in api tests quite awhile ago,
20:02:02 mriedem so a lot of the api tests are also ssh'ing into guests
20:02:14 sean-k-mooney well run validation is different
20:02:23 mriedem run_validation == enable ssh
20:02:23 sean-k-mooney in that its optional
20:02:39 mriedem sure, but it's basically on by default in tempest runs in the gate
20:02:41 sean-k-mooney e.g the test shoudl still be runale without it
20:02:47 sean-k-mooney ya
20:04:28 mriedem we should probably disable ssh validation in the nova-next job

Earlier   Later