Thursday, 2019-01-03

openstackgerritMatt Riedemann proposed openstack/nova-specs master: Spec for cross-cell resize  https://review.openstack.org/61603701:24
*** mriedem has quit IRC01:25
*** ttsiouts has quit IRC01:40
*** efried has joined #openstack-placement01:47
*** efried has quit IRC01:50
*** ttsiouts has joined #openstack-placement02:18
*** ttsiouts has quit IRC02:23
openstackgerritYongli He proposed openstack/nova-specs master: add spec "show-server-numa-topology"  https://review.openstack.org/61225603:08
*** ttsiouts has joined #openstack-placement03:17
*** ttsiouts has quit IRC03:22
openstackgerritYongli He proposed openstack/nova-specs master: add spec "show-server-numa-topology"  https://review.openstack.org/61225603:22
*** tetsuro has joined #openstack-placement04:13
*** tetsuro has quit IRC04:16
*** tetsuro has joined #openstack-placement04:33
*** tetsuro has quit IRC05:17
*** tetsuro has joined #openstack-placement05:17
*** ttsiouts has joined #openstack-placement05:18
*** ttsiouts has quit IRC05:23
*** ttsiouts has joined #openstack-placement07:19
*** ttsiouts has quit IRC07:24
openstackgerritRui Zang proposed openstack/nova-specs master: support virtual persistent memory  https://review.openstack.org/60159608:28
*** tetsuro has quit IRC08:36
*** tetsuro has joined #openstack-placement08:45
*** dtantsur|afk is now known as dtantsur08:59
*** ttsiouts has joined #openstack-placement09:20
*** ttsiouts has quit IRC09:24
*** ttsiouts has joined #openstack-placement09:30
*** e0ne has joined #openstack-placement09:42
*** ttsiouts has quit IRC10:33
*** tetsuro has quit IRC10:34
*** cdent has joined #openstack-placement11:41
*** ttsiouts has joined #openstack-placement12:49
*** mriedem has joined #openstack-placement14:14
*** mriedem has quit IRC14:19
*** mriedem has joined #openstack-placement14:21
*** ttsiouts has quit IRC15:18
*** efried has joined #openstack-placement15:25
*** e0ne has quit IRC15:28
openstackgerritMerged openstack/nova-specs master: Add spec for libvirt driver launching AMD SEV-encrypted instances  https://review.openstack.org/60977916:07
openstackgerritChris Dent proposed openstack/placement master: WIP: Placement install documentation  https://review.openstack.org/62822016:46
openstackgerritMatt Riedemann proposed openstack/nova-specs master: add spec "show-server-numa-topology"  https://review.openstack.org/61225617:09
cdentmriedem, jaypipes, efried : can one or some of you have a look at https://review.openstack.org/#/c/623556/ and make it go if possible? In talks with smcginnis it seems wise to do an initial release of placement to pypi so that something working is there, rather than the current broken thing, and having the os-resource-classes stuff in would be good from a dependencies standpoint17:43
efriedcdent: looking...17:45
efriedcdent: So os-resource-classes is fully a thing now?17:45
cdentyes, released to pypi and everything17:45
efriedis there any packaging nonsense that needs to happen for this to work irl?17:45
efriedI guess that happens at the end of the release.17:45
* cdent nods17:46
efriedcdent: Where did the resource class sync code come from, save me looking around17:47
cdentit was originally in https://review.openstack.org/#/c/584084/17:47
efriedcdent: so it isn't in production anywhere yet?17:48
cdentwhich sync code do you mean? the stuff that makes the database have the right entries? No, it's not in production yet, because the code you are reviewing has to be merged in order for it to be in production...17:49
efriedpoint is, we weren't doing that (ensure_resource_classes_sync) when resource classes were hardcoded in the (nova/placement) project?17:49
cdentcorrect17:50
efriedIt's just, I'm seeing some stuffs, and need to know what level of alarm to raise.17:50
cdentthe cache code would first check standards and then go to db17:50
cdentnow the cache code always goes to the db17:50
*** ttsiouts has joined #openstack-placement18:04
openstackgerritAdam Spiers proposed openstack/nova-specs master: AMD SEV: address final feedback received prior to merge  https://review.openstack.org/62825218:21
efriedcdent: Sorry for the delay, lots of things going on at once. Left comments on that review. No vote yet.18:21
cdentthanks18:22
openstackgerritAdam Spiers proposed openstack/nova-specs master: AMD SEV: address final feedback received prior to merge  https://review.openstack.org/62825218:23
*** dtantsur is now known as dtantsur|afk18:43
*** mriedem has quit IRC19:22
*** mriedem has joined #openstack-placement19:24
*** sean-k-mooney1 has joined #openstack-placement19:25
openstackgerritsean mooney proposed openstack/nova-specs master: Add spec for sriov live migration  https://review.openstack.org/60511619:35
efriedcdent, jaypipes: I'm going to be MIA M-W next week for onboarding. Can one of you please take the sched mtg?19:43
cdentaye aye19:43
efriedthanks19:43
efriedcdent: Is create_incomplete_consumers something that should be done from the placement repo at this point?19:56
cdentI think we decided that by now (stein) it should be done19:59
cdentefried: If you're reviewing https://review.openstack.org/618215 you might give that a -2 to prevent it being merge before everyone agrees its time20:02
efriedI am, and will do.20:03
efriedcdent: what will constitute "it's time"?20:03
cdentefried: I thought it was time two years ago, so you probably want to refer to a different authority on that one. But if pressed, the agreements on governance are a good proxy20:04
cdenthowever, it would be good for the deletion to happen sooner than later because the canonical packagers are not able to package placement until the placement code is deleted from nova (for reasons unclear)20:05
cdentmriedem may have thoughts, so let's see what he says20:05
efriedcdent: Could the placement-in-nova code even work anymore at this point? Wouldn't we have to unwind a bunch of other stuff in various other projects?20:05
cdentyes, it would still work, but CI has already changed over (for devstack, grenade, tempest)20:06
efriedcdent: "governance are a good proxy" <= not sure I follow. We don't need to tie this action to placement being under independent governance surely20:08
mriedemre create_incomplete_consumers - if we drop that from nova and dont have it in placement,20:08
mriedemthen we should at least have some check for it before people upgrade to stein,20:09
cdentefried, no, we don't, but it is currently the only list of things we have: thus "proxy".20:09
efriedI would think "it's time" means "extracted placement repo works from everywhere we care about."20:09
mriedemwhich could be a blocker migration or at least a placement-status upgrade check20:09
efriedmriedem: would those things be in the nova repo or the placement repo or both?20:09
mriedemcreate_incomplete_consumers code relies on hitting the consumers objects directly, so that hits the nova_api/placement db20:09
mriedemso a blocker migration for that wouldn't be in nova20:10
mriedemi think it really only makes sense that placement would be checking for those20:10
efriedhits nova_api db? how so?20:10
mriedemit's not an api call,20:10
*** ttsiouts has quit IRC20:10
mriedemthere is no consumers endpoint20:10
efriedafaict it's just making sure consumer IDs in the allocations table have records in the consumer table.20:10
mriedemright20:11
mriedemwith placement split out, that's a different db20:11
mriedemwhich nova shouldn't have direct access to20:11
*** ttsiouts has joined #openstack-placement20:11
efriedyes, the call itself should definitely not be in the nova project anywhere. No doubt in my mind about that.20:11
efriedquestion is, is it safe to have no equivalent in the placement repo?20:11
mriedemequivalent to the create_incomplete_consumers CLI for the data migration?20:12
efriedright20:12
efriedum, not sure if this is the right question, but: is it possible for an independent placement db, operated by extracted placement package, to have incomplete consumers?20:13
mriedemsafe? maybe. if you're upgrading from rocky to stein and have deployed extracted placement, and run an upgrade check which fails, i'm assuming you haven't upgraded nova to stein yet20:13
mriedemyes20:13
efriedthen we probably need.20:13
mriedemif you ran the db data copy script to copy the nova_api db tables to the placement db,20:13
mriedemyou could have incomplete consumers in there if you didn't finish the online data migrations for rocky in nova yet20:14
mriedemlike i said, the alternative to having create_incomplete_consumers in placement is a blocker migration or at least an upgrade check20:14
mriedemthough the latter is not widely used at this point20:14
efriedblocker migration <= in placement20:15
mriedemby blocker migration, i mean, placement-manage db sync falis20:15
mriedem*fails20:15
efriedAnd the remedy for that would be...20:15
efriedrunning create_incomplete_consumers somehow20:15
mriedemright20:15
efriedi.e. we need a placement manage create_incomplete_consumers.20:15
mriedembut if you've already copied over the database...20:15
efriedthat would still work, no?20:15
*** ttsiouts has quit IRC20:16
cdentif we were willing to do data migrations, not just schema migrations, then we could just add fixing consumers as a migration and be done: it would correct or not correct without need for thought20:16
cdentan additional command line is overkill20:16
cdentwe should both check and fix in one go20:16
*** ttsiouts has joined #openstack-placement20:17
efriedokay, fine, but *something* needs to be done.20:17
efriedWe can't just forget about it.20:17
cdentwe're not, we're having this conversation20:17
cdentjust because _I_ haven't done it doesn't mean it isn't going to happen20:17
cdentI hope people aren't expecting me to remember everything20:17
mriedemdoing the data migration during db sync is a problem if that data migration could take a long time, which i'm not sure how bad that data migration would be if you're churning through several thousand RPs/allocations/consumers table joins20:18
mriedemin the CERN case is what i'm thinking of20:18
efriedcdent: yahyah, point of this conversation is, if we decide something is needed (which it sounds like we have), then we need to make some kind of an artifact (a WIP patch, a line in an etherpad, whatever) that is less forgettable than this chat.20:18
mriedemi guess it's the rps table isn't involved here20:19
cdentwe've got this: could add something there: https://etherpad.openstack.org/p/placement-extract-stein-420:19
efriedbut of note, this issue needn't block merging the delete-placement-from-nova patch, because the ship (the extracted placement repo itself) has already sailed.20:20
mriedemcern could have 100k+ allocations though...20:20
cdentefried: well yeah we've got two threads running right now, which are orthogonal:20:21
*** e0ne has joined #openstack-placement20:21
cdenta) what are the controls on when we can delete the code20:21
cdentb) how should we deal with allocations without consumers20:22
mriedemi don't know the definitive go/no-go decision on deleting placement for nova and relying on extracted placement for people upgrading to stein, i thought it was at least one deployment project having tested their upgrade support to make sure it's all working - grenade isn't really good enough20:22
mriedemi said a couple of weeks ago that i think we need to have a pow wow in january when people are back to figure that out because this can't go much longer than jan imo20:22
mriedemi'm out next week btw20:22
cdents/without consumers/withou consumer entries in consumers table/20:22
efriedcdent: Added b) to etherpad L35-6. We can stop talking about that now. Thanks for the convo.20:22
efriedcdent: Is "database migration" the right heading, or should it move somewhere else?20:23
cdentthanks efried20:23
cdentno, that's good20:23
efriedight20:23
efriedwrt a), probably need to figure out why packagers think they can't move forward20:23
mriedemyeah, lyarwood should know the story for red hat,20:24
cdentefried: as far as I know people aren't blocked, it's more a matter of being enqueued20:24
mriedemi don't know who to ask for suse20:24
mriedemcoreycb should know for canonical20:24
mriedemas a result, there might be a catch 22 here where OSA can't test upgrades until canonical packages extracted placement?20:25
mriedemunless they install placement from source?20:25
mriedemnot sure how OSA works20:25
cdentthey have a "from-tarballs" ode20:25
cdentmdoe20:25
cdentdamn20:25
cdentmode20:25
efriedcdent: So do you want that -2 on there? (Keeping in mind that I won't be here M-W to remove it.)20:25
mriedemi really don't think that is going to merge next week20:26
* cdent looks at mriedem 20:26
mriedemlike i said, need to have a meeting20:26
mriedemneed melwitt involved20:26
mriedemand i'm out next week20:26
mriedemdansmith: when do you head north?20:26
dansmithmriedem: east20:26
cdentis dansmith santa claus?20:26
dansmithmriedem: and, I'm out the entire week of the 21st20:27
mriedemisn't alaska north of portland?20:27
mriedemor was that a "head east" the band joke?20:27
dansmithalaska is north and west20:27
dansmiththe race is not in alaska though :)20:28
mriedemoh i thought it was the iditarod20:28
dansmithno, it's a qualifier for the iditarod20:28
efriedcdent: I put the -2. Otherwise I'm +2 on that bottom patch.20:28
cdentdansmith: are you participating in a dog race?20:28
mriedemefried: cdent: melwitt: dansmith: jaypipes: ok then i think plan for a go/no-go extracted placement meeting the week of the 14th20:28
dansmithcdent: I do every year20:28
cdentthat's awesome20:29
dansmithnot as a musher, in case it's not clear20:29
mriedemmushee20:29
cdentstill awesome20:29
dansmithI think the mushees are the dogs, no?20:29
efriedthat's what mriedem meant.20:29
mriedemheh20:29
jaypipesheh20:29
mriedemlike, in a kinky way20:29
jaypipesmriedem: works for me.20:29
efriedI missed you guys20:30
mriedemefried: btw, onboarding20:30
mriedemgo20:30
efriedokay.20:30
dansmithmriedem: I told you not to talk about my leather strap fetish20:30
mriedemefried: i mean, explain20:30
cdentI was in alaska at a b&b once upon a time that trained dogs for iditarod and was asked to over-winter to help run the dogs (the dogs liked me) but I didn't and I've regretted it ever since20:30
efriedTomorrow is my last day at IBM. As of Monday, I work for... a chip company that rhymes with Schmintel.20:30
dansmithefried: AMD?20:31
mriedemefried: so they found their cyborg integrator huh20:31
efriedjust so20:31
efriedChanging companies was my best shot at being able to keep my job.20:31
efriedby which I mean, keep doing what i'm doing.20:31
mriedemaye20:31
efriedmy actual employment was not at risk20:31
cdentcan we call the meeting something other than go/no-go. unwinding at this point would be sad and super painful. how about go-faster20:31
mriedemsame when i was at ibm20:31
efriedmriedem: nod, I recall.20:32
mriedemcdent: "aggressive checkpoint"20:32
cdentwfm20:32
*** takashin has joined #openstack-placement20:37
*** e0ne has quit IRC20:37
cdentefried: this stack will probably help on the consumer migration: https://review.openstack.org/#/c/624942/20:37
efriedack20:38
cdenti've left a pointer to the above chatter20:39
melwittmriedem: ack on meeting the week of jan 14 to discuss20:48
*** e0ne has joined #openstack-placement20:54
sean-k-mooney1efried: best of luck. let me know when the internal plotics start lol20:56
sean-k-mooney1efried: are you joining ssg/otc?20:57
efriedsean-k-mooney1: Thanks. I'll have to pick your brain at some point about all of that. Yes, OTC. On Sundar's team.20:57
efriedsean-k-mooney1: But I'm no stranger to big-company internal politics and other gorp.20:58
sean-k-mooney1efried: haha anytime. well at least you will be in the groupt that pocitcally is ment to drive opensouce contributions so you will be able to bypass several of the intnal issues20:58
*** e0ne has quit IRC21:50
*** e0ne has joined #openstack-placement21:52
*** cdent has quit IRC21:56
*** ttsiouts has quit IRC21:56
*** e0ne has quit IRC21:57
*** efried has quit IRC22:35
*** efried has joined #openstack-placement22:35
*** efried has quit IRC22:39
openstackgerritMerged openstack/placement master: Use os-resource-classes in placement  https://review.openstack.org/62355623:09
openstackgerritMatt Riedemann proposed openstack/nova-specs master: Spec for cross-cell resize  https://review.openstack.org/61603723:26
openstackgerritMerged openstack/nova-specs master: Remove doc about metadata from 'share-pci-between-numa-nodes'  https://review.openstack.org/61980723:48
*** mriedem has quit IRC23:58

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!