Tuesday, 2018-11-06

*** tetsuro has joined #openstack-placement00:12
*** takashin has joined #openstack-placement00:16
openstackgerritChris Dent proposed openstack/placement master: Add a placement-manage CLI  https://review.openstack.org/60016101:22
cdentsmh01:23
efriedcdent: Why, oh why are you awake?01:28
cdentbecause that deep hole I've been in since last saturday with regard to the alembic stack is really really deep01:28
cdentbut I may have finally landed01:29
efriedcdent: Came across something really nice a couple hours ago.01:29
efriedStart zoomed into this: https://review.openstack.org/#/c/615705/1/nova/compute/resource_tracker.py01:29
efriedAnd then zoom out :)01:29
cdentif the landed thing is really landed than about 20 patches can finally merge (alembic migrations, devstack, grenade, integration jobs)01:30
* cdent clicks01:30
cdentoh nice, that is nice01:31
efriedIf I can pull this off, I'll be expecting a Harrods hamper from jaypipes01:31
cdentdepending on what you like, you may prefer Fortnum and Mason01:32
cdenta bit more specialised in the hamper direction01:32
efriedI'll settle for a Tesla.01:32
efriedanyway, I'm burned up for the night. ttfn01:33
cdentI too am all used up01:33
openstackgerritMerged openstack/nova-specs master: High Precision Event Timer (HPET) on x86 guests  https://review.openstack.org/60798901:34
cdentjaypipes: if you got cycles to drive through everything above https://review.openstack.org/#/c/614307/ (which you've already +2d) that would fantabulous. efried has already expressed a fair amount of "these things are not my ken"01:35
cdenttetsuro: you too ^01:35
cdentgood night all01:35
*** cdent has quit IRC01:35
*** tetsuro has quit IRC01:39
*** tetsuro has joined #openstack-placement01:40
openstackgerritChris Dent proposed openstack/placement master: Add a placement-manage CLI  https://review.openstack.org/60016101:44
*** e0ne has joined #openstack-placement06:24
*** e0ne has quit IRC06:44
*** e0ne has joined #openstack-placement06:48
*** e0ne has quit IRC07:07
*** tetsuro has quit IRC07:35
*** tetsuro has joined #openstack-placement08:13
*** helenafm has joined #openstack-placement08:15
*** tssurya has joined #openstack-placement08:18
*** lei-zh has joined #openstack-placement08:36
*** helenafm has quit IRC08:42
*** helenafm has joined #openstack-placement08:49
*** cdent has joined #openstack-placement09:22
*** lei-zh has quit IRC09:30
*** ttsiouts has joined #openstack-placement10:07
*** ttsiouts has quit IRC10:18
*** takashin has left #openstack-placement10:39
*** s10 has joined #openstack-placement10:57
*** e0ne has joined #openstack-placement11:11
openstackgerritBrin Zhang proposed openstack/nova-specs master: Support deleting data volume when destroy instance  https://review.openstack.org/58033611:49
cdentgibi: you have some cycles to explore https://review.openstack.org/#/c/614307/ and its children? Is all the database migration related stuff12:18
gibicdent: I will try. In the last week or so I was pretty lost in the preparation for my summit talk.12:19
cdentgibi: thank. no worries if you can't get to it. I was hoping to have it all merged before summit but if not it isn't a huge deal12:20
*** e0ne has quit IRC12:29
*** e0ne has joined #openstack-placement12:43
*** tetsuro has quit IRC12:55
openstackgerritMerged openstack/placement master: Move ensure_consumer to a new placement.handlers.util  https://review.openstack.org/61430713:09
gibicdent: I left some comment in https://review.openstack.org/#/c/612444 I won't block on it I just wanted to note that I feel this decorator does a lot more than what we need13:15
cdentgibi: if you look at some of the discussion on its original in nova it's trying to be forward thinking13:16
cdentand in a patch later on I use the reset functionality13:17
cdenthttps://review.openstack.org/#/c/614350/13/placement/tests/fixtures.py13:17
gibicdent: lookinh13:18
cdentthat ^ link is because we need to be able to reconfigure an engine facade from sqlite to mysql to postgresql in the same process13:19
gibicdent: OK, I see the usage of the reset now13:20
gibicdent: do you have a usage for cleanup as well?13:21
cdentIf I was feeling clever I could have used cleanup for the fixtures.reset() method but I decided not to be clever13:22
cdentbut something similar to that is the idea13:22
cdentthe end goals is that the tripleo people want it to be possible to reconfigure the app (including database settings) on a hup or something similar, with the cleanup function being able to reset the necessary globals and other state13:23
gibiso what is in the fixture.reset() is actually needs to always run together with the configure.reset() call?13:23
cdentI agree that it is probably overkill for the immediate case, but the dicussion on the nova review and the irc discussion associated with it was rather complete13:24
cdentI believe mdbooth may have more info if you're still concerned13:24
gibicdent: OK, I'm reading the nova review noq13:24
gibinow13:24
cdentthe stuff in the fixtures.reset() is not what would need to happen for any configure.reset(), because some of the globals there are related to just the fixture13:26
cdentbut things like the pool being disposed and resetting _started could have be in cleanup instead13:26
cdentbut I decided not to be clever, at least for now13:27
gibicdent: I see, thanks13:28
cdentI'm going to go find some lunch. thanks for looking at that stuff.13:30
*** cdent has quit IRC13:31
gibicdent: enjoy your lunch13:42
gibicdent: I left a real -1 on the nova patch due to not considering exceptions from func() https://review.openstack.org/#/c/61003413:43
openstackgerritsean mooney proposed openstack/nova-specs master: Add spec for sriov live migration  https://review.openstack.org/60511613:56
gibijaypipes: I'd like to ask a quick review from you on https://review.openstack.org/#/c/570847 about the resource class re-name to NET_BW_EGR_KILOBIT_PER_SEC13:59
gibiefried: from you too, please ^^14:03
*** mriedem has joined #openstack-placement14:11
openstackgerritJohn Garbutt proposed openstack/nova-specs master: Enable rebuild for instances in cell0  https://review.openstack.org/55421814:16
jaypipesgibi: done. +W.14:17
openstackgerritJohn Garbutt proposed openstack/nova-specs master: Add PENDING vm state  https://review.openstack.org/55421214:18
openstackgerritJohn Garbutt proposed openstack/nova-specs master: Add PENDING vm state  https://review.openstack.org/55421214:19
gibijaypipes: cool, thanks14:25
openstackgerritMerged openstack/nova-specs master: Add support for emulated virtual TPM  https://review.openstack.org/57111114:51
openstackgerritMerged openstack/nova-specs master: Switch to stestr  https://review.openstack.org/58128414:52
*** s10 has quit IRC15:04
*** e0ne has quit IRC15:06
tssuryaefried: I was looking into the tracker’s code to follow what improvisations you are doing in https://review.openstack.org/#/c/614886/ and had a question.15:08
tssuryaare we updating prov_tree’s inventory based on both placement and virt driver during every periodic update?15:08
efriedtssurya: Yes, but in an as-needed fashion. update_from_provider_tree sees if anything has changed, and only hits placement (and updates the cache) if something has.15:09
efriedtssurya: And only for the providers and aspects thereof that have changed15:10
efriedtssurya: So for example, if you had a whole tree and sharing provider setup, and you only changed an aggregate association on one provider, we would only do one call to placement.15:10
efriedtssurya: The vast majority of the time, nothing has changed, and we'll do zero calls to placement. (Currently we still do the initial rp GET with ?in_tree and the inventory GET every time, even if you have the interval set high. Those are going away with my patches.)15:11
tssuryaefried: okay.. so for me what's confusing is https://github.com/openstack/nova/blob/master/nova/compute/resource_tracker.py#L928 versus https://github.com/openstack/nova/blob/90b96170d3f269165f649e8b61739cf31ffb78b8/nova/scheduler/client/report.py#L99215:12
tssuryalike leaving the perforamance POV out of the discussion,15:12
tssuryawhat is the source of truth here ? we first compare the prov_tree's inventory cache with the GET result from placement and see if something has changed15:13
tssuryaand then we do the same with the virt driver ?15:13
efriedtssurya: The flow goes like this:15:15
efried1) The resource tracker uses get_provider_tree_and_ensure_root to make sure it has the latest and greatest representation of the provider data. (This is what my code series is looking to optimize to where it's almost always a no-op because we already had the right picture.)15:16
efried2) The resource tracker passes that information to the virt driver's update_provider_tree method. This is where the virt driver gets to decide if anything about it should change.15:16
tssuryaah okay so finally virt driver is the source of truth right ?15:17
efried3) The resource tracker passes the possibly-modified-by-virt provider tree object to update_from_provider_tree (confusing naming, but note the *from* in that one). ufpt is what compares that provider tree with what's in the cache (I should have mentioned that get_provider_tree_and_ensure_root is returning a *copy*, so ufpt still has the baseline to compare from) and flushes any changes back to placement.15:17
efriedtssurya: Yes, correct, the virt driver is the source of truth.15:18
tssuryaefried: okay so got it, and I also now udnerstand your improvisations..15:18
tssuryaI have something here: https://docs.google.com/document/d/1FWdwQK0gCdXt7LlDI52K5R2j8wbdUCYG8OdAn_h5FgU/edit?usp=sharing15:18
tssuryacan you verify this ?15:18
tssuryaits basically that we are trying to see what all syncs we can safely disable15:19
tssuryafor now15:19
efriedtssurya: I'm hoping to have this series in a place where you could just pull it down and try it soon, like by tomorrow. I may not have all the unit/func tests polished up, but if CI passes, we can be confident it at least doesn't break the world too badly.15:22
efriedreading...15:23
tssuryaalso is there anyway we could optimize doing both https://github.com/openstack/nova/blob/90b96170d3f269165f649e8b61739cf31ffb78b8/nova/scheduler/client/report.py#L698 and https://github.com/openstack/nova/blob/90b96170d3f269165f649e8b61739cf31ffb78b8/nova/scheduler/client/report.py#L1022 check15:23
efriedtssurya: Oh, you may also want to be looking at the new series where I'm trying to do all of this in pieces: https://review.openstack.org/#/c/615606/15:24
tssuryaprobably the lists of RP's for which you do these are different, and they must be necessary15:24
tssuryaefried: ack, looking15:24
*** ttsiouts has joined #openstack-placement15:25
*** cdent has joined #openstack-placement15:36
cdentstephenfin: this https://review.openstack.org/#/c/611719/ and this https://review.openstack.org/#/c/613118/ are potentially in your wheelhouse15:42
*** ttsiouts has quit IRC15:46
*** ttsiouts has joined #openstack-placement15:47
cdentmriedem: you have any ideas who might like to look at your grenade change?15:49
mriedemdansmith15:50
*** ttsiouts has quit IRC15:50
cdentDoes dansmith still exist? I thought he moved away to a comfortable island where nobody gets on his lawn.15:50
*** ttsiouts has joined #openstack-placement15:50
mriedemhe does15:51
mriedemalso probably busy preparing for summit talk and such15:51
cdentedleafe: you been able to catch up yet, or is other stuff holding you in its steely grasp?15:55
mriedemfwiw, i plan to go through the alembic series at some point here, but need to get my cross-cell resize spec wip started before the summit and need to wrap up some other stuff this week15:56
cdentmriedem: yeah, I think everybody is in that need/want to get X done before next week15:58
dansmithyeah I'm just overbooked with things16:00
stephenfincdent: done16:13
edleafecdent: sorry, was afk16:14
edleafecdent: yeah, I'm just catching up. Amazing that one day off puts you so far behind16:14
cdentstephenfin: thanks, don't feel bad about -1ing, that's what review is for16:14
edleafecdent: Anything in particular I need to know?16:14
cdentedleafe: well, I did work 8 hours on saturday and 17 hours yesterday on that stuff ...16:14
edleafeslacker16:14
cdentjust that it perhaps finally works, but you might want to compare with some ps version that you're familiar with and if there are changes that make no sense, ask me, so at least one more person than me has some insight16:16
openstackgerritChris Dent proposed openstack/placement master: Clean up and clarify tox.ini  https://review.openstack.org/61171916:19
edleafecdent: roger that16:20
openstackgerritChris Dent proposed openstack/placement master: Make tox -ereleasenotes work  https://review.openstack.org/61311816:36
*** ttsiouts has quit IRC16:50
*** helenafm has quit IRC16:53
cdentstephenfin: you probably gone now (good for you) but here's another tox-related thing that might intrigue: https://review.openstack.org/#/c/614559/17:23
cdentedleafe: did you get a chance to do/review https://review.openstack.org/#/c/613343/ ?17:25
cdentefried: you were previous +2 on https://review.openstack.org/#/c/611719/ and it needs a final kick and this one is nearby: https://review.openstack.org/#/c/613118/17:26
efriedcdent: Yeah, that one has changed a lot since my +2. I had intended to pull it down and try it again, just haven't gotten to it.17:27
efriedurgency?17:27
edleafecdent: not yet. I started trying to recreate your setup, but there were a bunch of requirements that I was missing, and never got to finish17:27
edleafecdent: that said, I'm always in favor of incremental improvements to docs rather than insisting that they be perfect from the start17:28
cdentefried: not so much urgency as it's been sat there for a long time and it would be nice to get some stuff  trundling in17:28
efriedyup, agree. A lot of stuff fits that description unfortunately.17:28
cdentedleafe: do you recall which requirements? things I didn't mention or stuff I did and you didn't have?17:29
cdentefried: true stories17:29
edleafecdent: no, which is why I wanted to start from scratch with a fresh VM and document them17:29
edleafeI tried it on my dev system, which didn't even have a database installed17:30
* cdent nods17:31
*** e0ne has joined #openstack-placement17:32
*** e0ne has quit IRC18:03
*** e0ne has joined #openstack-placement18:06
*** e0ne has quit IRC18:24
*** tssurya has quit IRC18:26
edleafecdent: kudos for unraveling the Opportunistic stuff. It was very much a black box of confusion.18:45
cdentstill is!18:46
edleafe:)18:46
cdentI'd get really close and then either find and edge case in local testing or in the gate18:46
cdentluckily it was saturday and the gate was fast18:47
openstackgerritChris Dent proposed openstack/placement master: Correct lower-constraints.txt and the related tox job  https://review.openstack.org/61455919:05
cdentmagic is my enemy, this time pbr19:06
cdentI've lost something like 20 hours in the last few days to openstack's predilection to make things more "convenient" for me without actually making it obvious19:07
*** mriedem is now known as mriedem_vote19:18
cdentbbl19:23
* cdent waves19:23
*** cdent has quit IRC19:23
*** mriedem_vote is now known as mriedem20:20
openstackgerritAdam Spiers proposed openstack/nova-specs master: Add spec for libvirt driver launching AMD SEV-encrypted instances  https://review.openstack.org/60977921:59
openstackgerritSundar Nadathur proposed openstack/nova-specs master: Nova Cyborg interaction specification.  https://review.openstack.org/60395523:14

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