Thursday, 2019-07-18

*** ociuhandu has joined #openstack-nova00:03
*** Bidwe_jay has quit IRC00:03
*** slaweq has joined #openstack-nova00:11
*** IvensZambrano has quit IRC00:13
*** brinzhang has joined #openstack-nova00:14
*** slaweq has quit IRC00:16
*** ociuhandu has quit IRC00:17
openstackgerritArtom Lifshitz proposed openstack/nova master: [WIP-until-series-is-ready] Introduce live_migration_claim()  https://review.opendev.org/63566900:26
openstackgerritArtom Lifshitz proposed openstack/nova master: New objects for NUMA live migration  https://review.opendev.org/63482700:27
openstackgerritArtom Lifshitz proposed openstack/nova master: LM: add support for sending NUMAMigrateData to the source  https://review.opendev.org/63482800:27
openstackgerritArtom Lifshitz proposed openstack/nova master: LM: add support for updating NUMA-related XML on the source  https://review.opendev.org/63522900:27
openstackgerritArtom Lifshitz proposed openstack/nova master: RPC changes to prepare for NUMA live migration  https://review.opendev.org/63460500:27
openstackgerritArtom Lifshitz proposed openstack/nova master: NUMA live migration support  https://review.opendev.org/63460600:27
openstackgerritArtom Lifshitz proposed openstack/nova master: Deprecate CONF.workarounds.enable_numa_live_migration  https://review.opendev.org/64002100:27
*** gyee has quit IRC00:46
*** betherly has joined #openstack-nova00:55
*** betherly has quit IRC01:00
*** ociuhandu has joined #openstack-nova01:15
*** betherly has joined #openstack-nova01:15
*** imacdonn has quit IRC01:16
*** imacdonn has joined #openstack-nova01:17
*** betherly has quit IRC01:20
*** mlavalle has quit IRC01:24
*** tbachman has quit IRC01:27
*** ociuhandu has quit IRC01:28
*** _hemna has quit IRC01:30
*** whoami-rajat has joined #openstack-nova01:31
*** ileixe has quit IRC01:37
*** _hemna has joined #openstack-nova01:49
*** brinzhang55 has joined #openstack-nova01:53
*** _hemna has quit IRC01:54
*** betherly has joined #openstack-nova01:57
*** tetsuro has joined #openstack-nova01:57
*** betherly has quit IRC02:02
*** spatel has joined #openstack-nova02:09
*** slaweq has joined #openstack-nova02:11
*** spatel has quit IRC02:14
*** slaweq has quit IRC02:15
*** ociuhandu has joined #openstack-nova02:26
*** _hemna has joined #openstack-nova02:26
*** ociuhandu has quit IRC02:38
*** threestrands has joined #openstack-nova02:43
*** _hemna has quit IRC02:46
*** brinzhang55 has quit IRC02:50
*** hongda has joined #openstack-nova02:50
*** tetsuro has quit IRC03:00
*** JamesBenson has joined #openstack-nova03:02
*** betherly has joined #openstack-nova03:09
*** betherly has quit IRC03:14
openstackgerritAlex Xu proposed openstack/nova master: [WIP] Populate the existing mediated devices in the libvirt device manager  https://review.opendev.org/67078703:23
openstackgerritAlex Xu proposed openstack/nova master: [WIP] Using the claim/unclaim_for_instance for mdevs  https://review.opendev.org/67122203:23
openstackgerritAlex Xu proposed openstack/nova master: Add DeviceManager to the libvirt virt driver  https://review.opendev.org/67138803:23
*** redrobot has quit IRC03:32
*** psachin has joined #openstack-nova03:36
*** ociuhandu has joined #openstack-nova03:36
*** Guest99405 has joined #openstack-nova03:39
*** JamesBenson has quit IRC03:40
*** betherly has joined #openstack-nova03:40
*** betherly has quit IRC03:45
*** ociuhandu has quit IRC03:50
*** slaweq has joined #openstack-nova04:11
*** slaweq has quit IRC04:16
*** brinzhang has quit IRC04:30
*** brinzhang has joined #openstack-nova04:30
*** tetsuro has joined #openstack-nova04:37
*** udesale has joined #openstack-nova04:39
*** tetsuro has quit IRC04:42
*** ociuhandu has joined #openstack-nova04:48
*** tetsuro has joined #openstack-nova04:55
*** Bidwe_jay has joined #openstack-nova04:56
*** ociuhandu has quit IRC05:00
*** ganso has quit IRC05:05
*** Luzi has joined #openstack-nova05:09
*** Bidwe_jay has quit IRC05:10
*** slaweq has joined #openstack-nova05:11
*** tetsuro has quit IRC05:12
*** ratailor has joined #openstack-nova05:13
*** slaweq has quit IRC05:15
*** gokhani has quit IRC05:18
openstackgerritAlex Xu proposed openstack/nova master: Populates the existing mediated devices in the libvirt device manager  https://review.opendev.org/67078705:20
openstackgerritAlex Xu proposed openstack/nova master: Using the claim/unclaim_for_instance for mdevs  https://review.opendev.org/67122205:20
openstackgerritAlex Xu proposed openstack/nova master: Adds functional test for creating the instance with vgpus  https://review.opendev.org/67139805:20
alex_xubauzas: ^ need your review on those patches, I move the mdev into the new claim_for_instance interface05:22
*** gokhani has joined #openstack-nova05:22
*** maciejjozefczyk has joined #openstack-nova05:24
*** ccamacho has quit IRC05:33
*** pcaruana has joined #openstack-nova05:44
*** ociuhandu has joined #openstack-nova05:57
*** damien_r has joined #openstack-nova05:57
*** logan- has quit IRC06:00
*** logan_ has joined #openstack-nova06:01
*** logan_ is now known as logan-06:01
*** ociuhandu has quit IRC06:02
*** dpawlik has joined #openstack-nova06:04
*** igordc has quit IRC06:14
*** slaweq has joined #openstack-nova06:28
openstackgerritAlex Xu proposed openstack/nova master: Add DeviceManager to the libvirt virt driver  https://review.opendev.org/67138806:30
openstackgerritAlex Xu proposed openstack/nova master: Populates the existing mediated devices in the libvirt device manager  https://review.opendev.org/67078706:30
openstackgerritAlex Xu proposed openstack/nova master: Using the claim/unclaim_for_instance for mdevs  https://review.opendev.org/67122206:30
openstackgerritAlex Xu proposed openstack/nova master: Adds functional test for creating the instance with vgpus  https://review.opendev.org/67139806:30
*** gokhani has quit IRC06:31
*** tetsuro has joined #openstack-nova06:32
*** tetsuro has quit IRC06:36
*** sapd1 has quit IRC06:37
*** rcernin has quit IRC06:44
openstackgerritYongli He proposed openstack/python-novaclient master: Microversion 2.75 - show server topology  https://review.opendev.org/67079006:46
*** damien_r has quit IRC06:47
*** tbachman has joined #openstack-nova06:54
*** tbachman has quit IRC06:58
*** ociuhandu has joined #openstack-nova07:00
*** xek has joined #openstack-nova07:06
*** belmoreira has joined #openstack-nova07:07
*** ociuhandu has quit IRC07:08
*** rpittau|afk is now known as rpittau07:11
*** damien_r has joined #openstack-nova07:11
*** ttsiouts has joined #openstack-nova07:13
*** maciejjozefczyk has quit IRC07:17
*** tetsuro has joined #openstack-nova07:22
*** helenafm has joined #openstack-nova07:23
*** threestrands has quit IRC07:24
*** belmoreira has quit IRC07:31
*** ccamacho has joined #openstack-nova07:36
*** ttsiouts has quit IRC07:39
*** belmoreira has joined #openstack-nova07:39
*** ttsiouts has joined #openstack-nova07:39
*** tetsuro has quit IRC07:41
openstackgerritDakshina Ilangovan proposed openstack/nova-specs master: Spec: Provider config YAML file  https://review.opendev.org/61249707:43
*** ttsiouts has quit IRC07:44
*** ttsiouts has joined #openstack-nova07:46
*** ralonsoh has joined #openstack-nova07:56
*** ttsiouts has quit IRC08:00
*** ttsiouts has joined #openstack-nova08:01
*** ttsiouts has quit IRC08:06
*** ociuhandu has joined #openstack-nova08:07
*** ttsiouts has joined #openstack-nova08:09
*** ociuhandu has quit IRC08:11
*** cdent has joined #openstack-nova08:20
*** derekh has joined #openstack-nova08:20
stephenfinefried: Correct. We're doing that already and we've decided it's not an issue since operators should already have separate hosts for pinned and non-pinned instances08:22
stephenfinefried: and if they don't, they get pretty much what they had before, even if placement inventory will be kind of a lie08:23
cdentlying is bad, mmmkay?08:27
*** belmoreira has quit IRC08:33
*** tetsuro has joined #openstack-nova08:34
*** belmoreira has joined #openstack-nova08:35
*** tetsuro has quit IRC08:39
*** tkajinam has quit IRC08:40
*** xek has quit IRC08:42
*** xek has joined #openstack-nova08:43
openstackgerritQingFeng Hao proposed openstack/nova master: Add get_host_memory_stats in zvm driver  https://review.opendev.org/67143008:44
*** tetsuro has joined #openstack-nova08:46
*** xek has quit IRC08:47
gibisean-k-mooney: left comments in https://review.opendev.org/#/c/671338 overall direction looks good to me08:48
*** tetsuro has quit IRC08:50
*** xek has joined #openstack-nova08:51
*** tetsuro has joined #openstack-nova08:51
*** xek has quit IRC08:52
sean-k-mooneygibi: thanks, ya the unit test failures are valid i ran them locally with a regex of things i tought might break but i obviously missed some08:53
*** tetsuro has quit IRC08:53
*** tetsuro has joined #openstack-nova08:54
*** Bidwe_jay has joined #openstack-nova08:56
*** tssurya has joined #openstack-nova09:00
*** arxcruz|ruck is now known as arxcruz09:01
*** asmita_s has joined #openstack-nova09:08
*** asmita_s has quit IRC09:08
*** davidsha has joined #openstack-nova09:15
*** Bidwe_jay has quit IRC09:16
*** tssurya has quit IRC09:17
*** tetsuro has quit IRC09:20
*** xek has joined #openstack-nova09:26
*** belmoreira has quit IRC09:26
openstackgerritStephen Finucane proposed openstack/nova master: tox: Keeping going with docs  https://review.opendev.org/67033209:26
kashyapHeya, a random question: what else tooling do people use besides `git-review` to make life pleasant with Gerrit?09:26
kashyap(I'm asking because, I'm providing a data point for those who are mailing lists, and are considering web-based workflows, GitLab/GitHub; not Gerrit at this point)09:27
kashyapI think `gertty` would be another for those who like the offline caching and terminal-based reviews09:27
*** ttsiouts has quit IRC09:27
*** ttsiouts has joined #openstack-nova09:28
*** belmoreira has joined #openstack-nova09:29
sean-k-mooneyits mainly git review for me. with web for review. i strongly dislike mailing list based workflows to the point that unless that project also has patchwork i almost entirly avoid them09:29
sean-k-mooneyat least when it comes to code reviews09:29
sean-k-mooneygertty if fine for reviewing09:30
sean-k-mooneybut its offline asspect comes at the cost that it needs to build up an sql database of the open changes09:30
sean-k-mooneythat can be slow with large repos like nova09:30
gibiefried: I added comments to https://review.opendev.org/#/c/61249709:31
kashyapI maintain Gertty in Fedora, FWIW, because I enjoy the offline ability.  And the DB build-up is a negligible cost09:31
kashyapsean-k-mooney: It's not SQL; but Berkely09:31
sean-k-mooneykashyap: no is sqlight309:32
kashyapAh, right09:32
kashyapSorry09:32
*** ttsiouts has quit IRC09:33
* kashyap also appreciates the strenghts of mailing lists. Nothing beats their blazing fastness, if you are using proper tools (`mutt` or equivalent, plus OfflineIMAP, indexing like `notmuch`, etc).09:33
sean-k-mooneythere are allo tools like https://github.com/openstack-infra/git-restack or https://github.com/dhellmann/git-nit09:33
kashyapsean-k-mooney: Thanks; /me checks09:34
sean-k-mooneykashyap: personally i find mailing list much slower and harder to follow since you have to constuct all that tooling yourself09:34
kashyapAh, didn't know of them09:34
sean-k-mooneygit restack is old and not really uses much i think09:35
sean-k-mooneypersonally i found doing a interactive rebase manullay to the same base commit was just as quick09:36
kashyapsean-k-mooney: Nod.  (But the kernel and other systems folks still maintain mailing lists are the "best way" to manage large projects as kernel: https://lwn.net/Articles/702177/)09:36
kashyapsean-k-mooney: Okay, thanks for the opinion and notes :-)09:37
*** ttsiouts has joined #openstack-nova09:38
bauzasalex_xu: ack, will look09:39
alex_xubauzas: thanks09:40
*** tssurya has joined #openstack-nova09:40
bauzasalex_xu: wow, that's a massive refactoring, I'll do this this afternoon09:42
bauzasthanks for it09:42
bauzasalex_xu: FWIW, I'm also working on https://review.opendev.org/#/c/589085/09:43
alex_xubauzas: I guess it should works with your patch also, and you get the vgpu claim for dst host09:43
bauzasalex_xu: that's why I need to look at your series to exactly understand how it works09:44
*** tetsuro has joined #openstack-nova09:44
bauzasalex_xu: also, a nit, I wonder if we should have a specless bp for this09:46
*** tetsuro has quit IRC09:46
alex_xubauzas: yea, probably we can ask efried about that09:46
*** belmoreira has quit IRC09:51
*** ttsiouts has quit IRC10:15
*** tetsuro has joined #openstack-nova10:15
*** ttsiouts has joined #openstack-nova10:15
*** helenafm has quit IRC10:16
*** belmoreira has joined #openstack-nova10:19
*** ttsiouts has quit IRC10:20
*** bbowen has quit IRC10:27
openstackgerritStephen Finucane proposed openstack/nova master: bindep: Remove dead markers  https://review.opendev.org/67145210:28
*** helenafm has joined #openstack-nova10:29
stephenfinbauzas, alex_xu: Easiest +2 you'll ever have right here https://review.opendev.org/67145210:30
*** whoami-rajat has quit IRC10:30
bauzasstephenfin: hands on deck10:30
*** takamatsu has joined #openstack-nova10:37
*** tetsuro has quit IRC10:49
*** tetsuro has joined #openstack-nova10:50
*** tetsuro has quit IRC10:52
kashyapbauzas: Isn't it simple enough to just go ahead and +W it?11:06
kashyap(It being the 'bindep' one)11:06
bauzasno11:06
bauzasfast-approval seems right, but honestly people could have concerns11:07
*** maciejjozefczyk has joined #openstack-nova11:07
*** belmoreira has quit IRC11:07
kashyapIf there _can_ be concerns, okay, fair enough.11:08
sean-k-mooneykashyap: even if it was stephenfin wrote it so we shoul dnot have a redhat core +2+w without someone else looking at it11:08
kashyapWell, not that asinine reason again.  There are sensible exceptions11:08
sean-k-mooneykashyap: yep this is not one of them11:09
kashyapOn that point, see my extended point here: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006080.html11:09
kashyapsean-k-mooney: Okay.11:09
*** ttsiouts has joined #openstack-nova11:09
kashyapI don't care about this change particularly, BTW.  Just the simplicity of it is what prompted me to say it.11:09
cdentkashyap++ and *hugs*11:18
kashyap:-)11:18
kashyapsean-k-mooney: For argument's sake, why is this not one of them?  Precise is even EOL11:22
kashyapThis is definitely one of those dead-simple changes that doesn't require an completely unhinged process to interfere11:22
kashyapAnyway, not my circus, not my clowns.11:22
kashyaps/"an completely"/"a completely"/11:23
sean-k-mooneyignoring the same company aspect. one out of curtusy to other disto maintainer we shoudl not fast merge thing related to our competitor distro without any external reveiew, second we only use singel +2 in very limited cases like when you would have been the second +2 but you fix a minor nit in someone esle pathc or rebased a patch that went int merge confcit and you are proxing a previous +2 from a11:27
sean-k-mooneycore, third its not urgent, i.e. there is no bug associated wthi this stepen jsut noticed it and its not blocking the gate. put that to gether with the same company core thing and even though its trivial and it looks correct i dont think this has a stong case for bypassing our standard policy11:27
*** belmoreira has joined #openstack-nova11:28
* gibi resolved the controversy by +Aing the patch 11:29
kashyapSure, it is not about "urgency", but needless, grinding processes coming in the way.  Also on courtesy, who says it is being incourteous?  Assume good intent.11:29
*** bbowen has joined #openstack-nova11:29
kashyapgibi: :-) I was just "thinking (or arguing) out loud".11:30
sean-k-mooneyi am assuming good intent but i would assume you would like to see change to fedora requirement before they merged if i was droping support for a fedora version11:31
kashyapFor an EOL release?  I don't give a damn11:31
sean-k-mooneyanyway thanks gibi :)11:31
gibiwe an always revert such patches :)11:32
gibiwe can11:32
kashyapYes, exactly.11:32
kashyapThe "revert" hammer is always near by :D11:32
sean-k-mooneykeep it away from artom for a while11:32
kashyapHaha11:32
openstackgerritSurya Seetharaman proposed openstack/nova master: API microversion 2.75: Add 'power-update' external event  https://review.opendev.org/64561111:38
*** tesseract has joined #openstack-nova11:38
*** ganso has joined #openstack-nova11:39
* artom pops up like a meerkat11:39
artomWhat am I reverting?11:39
sean-k-mooneyhehe nothing i was just saying lets not hit you with the revert hammer for a while.11:40
sean-k-mooneyi think you have had enough heartache form it in the last week or two11:40
*** ratailor has quit IRC11:40
artomUgh11:40
*** eharney has quit IRC11:40
kashyapHe was teasing you :D11:41
sean-k-mooneymore his bad luck11:41
artomI know, the "ugh" was about the reverts, not the tease11:41
kashyapNod, figured as much.11:48
*** Bidwe_jay has joined #openstack-nova11:50
*** dpawlik has quit IRC12:16
openstackgerritArtom Lifshitz proposed openstack/nova master: migrations: libvirt: remove get_machine_ips()  https://review.opendev.org/67147112:26
artomsean-k-mooney, ^^12:26
*** eharney has joined #openstack-nova12:26
artomstephenfin, ^^ you might like the code removal aspect too :)12:26
*** udesale has quit IRC12:26
artomNot sure if I need a bug for that...12:26
*** udesale has joined #openstack-nova12:27
sean-k-mooneyya we proably should have a bug and mention the downstream one12:27
sean-k-mooney:) +0,-5512:27
sean-k-mooneyartom: actully we want to backport it so it need a bug12:31
stephenfinartom: Makes sense. Do you want to backport it?12:34
sean-k-mooneystephenfin: we need this on newton downstream12:34
sean-k-mooneyso yes12:34
stephenfinI assume so, given your comment in the bug. If so, what sean-k-mooney said12:34
stephenfinack12:34
artomstephenfin, it's for an internal escalation, so yeah12:34
artomBusy with household'y stuff, will file bug12:35
artomIn a few12:35
stephenfinThat's going to be an ugly backport. You've been warned12:35
artomI... I can't tell if you're being serious12:35
stephenfin(look at the "Conflicts With" for an idea of the amount of _unmerged_ patches this touches)12:35
stephenfinOh, I'm always very serious12:35
sean-k-mooneyreally? why12:35
stephenfinSerious Steve, I've been called12:35
sean-k-mooneyi think that is likely jsut change to the module import in most cases12:36
artomI would think most of those are just whitespace-type things12:36
artomIe, the excision itself is clean, but git is having trouble because what's around it changed12:36
stephenfinQuite possibly. I didn't check. It doesn't matter much either. If it's got to be done, it's got to be done.12:36
sean-k-mooneystephenfin: also if artom going to be the one doing it ... :)12:36
artomSheesh guys, team spirit and all that12:37
sean-k-mooneywe will review it for you down stream too :P12:37
stephenfinGo team?12:38
artomAnd I'm sure it'll be done most professionally12:38
stephenfinAnd that's all the team spirit I have for one day.12:38
sean-k-mooneystephenfin: maybe an infution of teen sprit will help https://www.youtube.com/watch?v=hTWKbfoikeg12:40
artomsean-k-mooney, *fist bump*12:45
artomNoice.12:45
*** mvkr_ has quit IRC12:56
kashyapalex_xu: When you're awake: Mind giving an opinion on the Intel CMT thing? -- https://review.opendev.org/#/c/669129/12:58
*** damien_r has quit IRC13:03
*** Guest99405 is now known as redrobot13:13
*** dpawlik has joined #openstack-nova13:15
*** ag-47 has joined #openstack-nova13:17
*** boxiang has joined #openstack-nova13:18
alex_xukashyap: thanks, I will check that13:19
kashyapThanks!13:23
*** hoonetorg has quit IRC13:28
*** damien_r has joined #openstack-nova13:30
*** damien_r has quit IRC13:30
*** damien_r has joined #openstack-nova13:30
*** ag-47 has quit IRC13:32
*** jovial[m] has joined #openstack-nova13:33
*** tbachman has joined #openstack-nova13:34
alex_xukashyap: I will send an email double check with team, the last time(after the dublin ptg) I check with team, it said ok to remove it. so just wait few more sec, I will get that back to you.13:35
kashyapalex_xu: Sure, no rush.  By "remove it", are you suggesting to remove entire support for it, yeah?13:36
alex_xukashyap: the entire perf feature, right? I didn't heard any requirement from intel for it now.13:36
kashyapRight, indeed13:36
*** beekneemech has joined #openstack-nova13:36
kashyapAs we know, the kernel itself has completely nuked it13:37
*** bnemec has quit IRC13:37
*** tbachman has quit IRC13:39
*** tbachman has joined #openstack-nova13:40
openstackgerritLee Yarwood proposed openstack/nova master: WIP nova-next: Deploy noVNC from source  https://review.opendev.org/67149013:42
lyarwoodmelwitt: ^ as discussed, hopefully that's enough to make this work.13:42
*** Luzi has quit IRC13:52
*** TxGirlGeek has joined #openstack-nova13:52
*** whoami-rajat has joined #openstack-nova13:55
*** artom has quit IRC13:56
*** boxiang has quit IRC13:56
*** ttsiouts has quit IRC14:01
*** tbachman has quit IRC14:01
*** ttsiouts has joined #openstack-nova14:02
openstackgerritBalazs Gibizer proposed openstack/nova master: Allow migrating server with port resource request  https://review.opendev.org/67149714:04
*** ttsiouts has quit IRC14:05
*** ttsiouts has joined #openstack-nova14:06
*** JamesBenson has joined #openstack-nova14:06
*** JamesBenson has quit IRC14:10
*** JamesBenson has joined #openstack-nova14:13
stephenfindansmith: Off the top of your head, any idea what would cause this? http://paste.openstack.org/show/754546/14:13
dansmithyes?14:14
dansmithyou named the things different in the model and the migration14:14
dansmithpcpus vs pcpus_used apparently14:14
efriedkashyap: I use git-restack regularly to manage series14:14
dansmithstephenfin: ^14:14
*** JamesBenson has quit IRC14:15
stephenfindansmith: I don't see how though http://paste.openstack.org/show/754547/14:15
*** JamesBenson has joined #openstack-nova14:15
*** ccamacho has quit IRC14:15
dansmithhmm, so it must be claiming that both of those are missing from one or the other14:16
dansmithoh14:17
dansmithstephenfin: aren't you creat5ing them as nullable=True,14:17
dansmithbut they're =false in the model14:17
stephenfingod damn it, yup14:17
dansmiththat output from the test looks different than I remember for some reason, but .. yeah14:18
stephenfinThanks. I've been looking at that for at least 30 minutes 😅14:18
dansmithnp, blinders.. it's a thing14:18
*** tbachman has joined #openstack-nova14:19
*** ccamacho has joined #openstack-nova14:20
kashyapefried: Good to know.  Thanks for the view14:21
*** mlavalle has joined #openstack-nova14:22
efriedkashyap: in fact, if you're trying to convince people that gerrit is awesomer than other things, how do other things manage series? Cause gerrit does it awesomely.14:22
* kashyap on a call; back in a min14:24
efriedkashyap: I wrote a tutorial, which might be handy: https://docs.openstack.org/contributors/de/code-and-documentation/patch-series-tutorial.html14:24
efriedhttps://docs.openstack.org/contributors/code-and-documentation/patch-series-tutorial.html14:25
* kashyap is back here. 14:29
kashyapExcellent; I saw that before!14:30
kashyapefried: I don't think this group might consider Gerrit.  I wanted to present where Gerrit shines14:30
kashyaps/!//14:30
efriedcool14:31
*** TxGirlGeek has quit IRC14:33
kashyapefried: So 'git-restack' is not exactly "abandonware" is it?14:33
efriedwhat does that mean?14:33
kashyapSorry, meanining, nobody has time to tend to it14:34
*** ricolin_ is now known as ricolin14:34
kashyap[Last commit was from 4 years ago.]14:34
efriedoh, it's maintained, insofar as that's necessary. I think someone like fungi or dhellmann owns it.14:34
kashyapIt might well be that the project is "done", though.  Which is perfectly acceptable14:34
kashyapRight, noted.14:34
efriedyeah, it doesn't need much. It's just a thin wrapper around `git rebase -i commit-before-wherever-my-current-series-meets-up-with-master`14:34
efriedjust saves you figuring out that last piece.14:35
fungiefried: it's a side-project of corvus14:36
fungi(like gertty)14:36
efriedah, k14:36
*** lbragstad has joined #openstack-nova14:36
sean-k-mooneyefried: i think its a little smarter tehn that and looks for the parent commit where my current series meets up with its parent branch. but i might be mistaken14:36
fungiahh, nope, it's official opendev. i forgot14:36
fungihe just initially developed it14:36
sean-k-mooneye.g. i think if you were on stable/stien origically it look for where your feature branch meets stable/stine instead of master14:37
*** belmoreira has quit IRC14:37
efriedkashyap: If you wanted to break that 4-year streak, we did recently discuss adding a feature where you could say `git restack --continue` and it determines whether you need a `commit --amend` or just a `rebase --continue`, which is one place I've gotten bitten in the restack workflow from time to time.14:37
fungihttps://review.opendev.org/#/admin/groups/git-restack-core14:37
fungiinfra-core approves changes for it14:37
kashyapefried: Hehe, noted.14:37
efriedsean-k-mooney: yes, "meets up with its parent branch" is more correct. My hyphenated thingy wasn't long enough already.14:38
sean-k-mooney:)14:38
fungino pending changes for review on opendev/git-restack that i can see14:38
fungiwas someone having problems using it?14:38
sean-k-mooneythe tool extention i personly want to write at some point is "git review --quad-diff <gerrit id>" or "git-review -Q" if that is free14:39
sean-k-mooneyit would print the diff of the current reve to its base difed againt the previs revies to that revions base14:40
fungisean-k-mooney: maybe better to just make a separate git subcommand for whatever that does? (doesn't sound like it's related to fetching and pushing changes for review)14:40
sean-k-mooneyso if you have don rebase it would remove them and show you only what changed14:40
fungioh, i see, you want to compare against content on gerrit... hmmm14:40
sean-k-mooneyfungi: ya i actully want it in gerrit itself but i dont want to write java or javscript14:41
*** mlavalle has quit IRC14:41
sean-k-mooneyso ill settle for a little tool or an extention to git review.14:41
*** belmoreira has joined #openstack-nova14:41
sean-k-mooneyits on my todo list for the next weekend i feel like hacking on something14:42
fungigertty has a couple of diff options already, maybe a third would fit in nicely?14:42
sean-k-mooneyya maybe14:42
sean-k-mooneyi have been meaning to look at the db opertion in gerrty to see if i can speed up the intial data base builing14:43
sean-k-mooneybut the diff feature would be simpler to start with14:43
*** goldenfri has quit IRC14:45
efriedfungi: "no pending changes" "having problems" -- no, I was just mentioning its existence to kashyap, and he asked if it was abandoned because it hasn't seen a commit in 4y, and I said nay because it doesn't need any because it's so simple, but we talked recently about a feature that could be added to it.14:45
efriedand now you're up to date14:45
sean-k-mooneyfungi: efried does it work on python3?14:45
kashyapYeah, that's completely fair.  I shouldn't confuse "activity" with "improvements".14:45
sean-k-mooneyif its been 4 years...14:45
kashyapsean-k-mooney: So?  Maybe it does one thing and does it well? :-)14:46
efriedsean-k-mooney: um, it's possible it's sh, not python, though I haven't looked.14:46
efriedbecause technically all it would need to do is invoke a few git commands14:46
*** mlavalle has joined #openstack-nova14:46
sean-k-mooneyits got some python 3 checking code https://github.com/openstack-infra/git-restack/blob/master/git_restack/cmd.py#L30-L4614:47
sean-k-mooneyso ill assume its fine14:47
*** priteau has joined #openstack-nova14:48
fungiefried: kashyap: thanks! and yeah, happy to discuss features that might be in-scope, but also as you say it's a great example of a very simple git subcommand, and it's easy to add more subcommands to git... the opendev/git-restack is nearly all boilerplate14:50
fungier, the opendev/git-restack repo is i mean14:50
kashyapNoted :-)14:51
fungiand yeah, it's python-based, and yeah i run it installed into a python3 (.8 beta) venv14:51
sean-k-mooneygibi: do you mind if i reverse the direction fo the depend on for the vpmu patch. e.g. make the glance change to the metadef depend on the nova one.14:54
*** belmoreira has quit IRC14:54
sean-k-mooneythe glance change is not really needed for it to work its just documentation which ill write but i dont know how long that will take to merge14:54
*** ratailor has joined #openstack-nova14:58
*** TxGirlGeek has joined #openstack-nova15:00
gibisean-k-mooney: ohh, so the new glance image property doesn't need any code on glance side?15:01
sean-k-mooneycorrect15:02
sean-k-mooneywe just need to extend the nova image meta object15:02
sean-k-mooneyglance does no validation15:02
sean-k-mooneywhat the metadefs are fro aare auto generating client e.g. the horizon dashboard for setting image metadata15:03
gibisean-k-mooney: thanks, then I'm OK to have the dependency in the other way15:04
sean-k-mooneyim currently fixing the other issue but i should get a new version up today.15:05
sean-k-mooneyill start on the glance patch once that is done15:05
*** belmoreira has joined #openstack-nova15:08
*** nicholas has joined #openstack-nova15:08
*** artom has joined #openstack-nova15:08
efriedgibi: responded in https://review.opendev.org/#/c/612497/ -- please let's resolve the discussion about $COMPUTE_HOST if you're still around.15:08
cdentheh: "this is obviously by design"15:12
*** eharney_ has joined #openstack-nova15:12
dansmithefried: your comment about $COMPUTE_HOST for ironic makes this basically unusable by any real ironic deployment, AFAICT15:14
*** eharney has quit IRC15:15
efrieddansmith: on the contrary, $COMPUTE_HOST is really a convenience to un-awkward the chicken/egg of having to bring up the compute so it creates the provider so you can glean its UUID and create your file and restart compute.15:15
efriedfor ironic, don't you already know the UUIDs of the nodes before you bring up the compute service?15:15
dansmithefried: except that ironic computes rebalance their nodes in ways you don15:15
dansmithdon't control15:15
efriedmeaning putting them under different computes?15:16
dansmiththe ownership of nodes by comptues I mean15:16
efriedgot it15:16
efriedwell15:16
dansmithpoint being,15:16
dansmiththe node is the thing with the inventory, be it the one single node for a libvirt system,15:16
dansmithor the ironic nodes managed by a compute *service*15:16
efriedIf we want to add a "template multiple providers" feature in the future, that's certainly a possibility.15:17
dansmithfurther,15:17
*** eharney_ is now known as eharney15:17
dansmithon something like xen or vmware where the compute *service* may be running on a different host than the actual thing providing the resource,15:17
dansmithit's the node that has the inventory and they don't even share a name15:17
efriedOkay, so you're suggesting a) $COMPUTE_NODE is the more proper term regardless; and b) we should apply whatever changes to all "nodes", which is only >1 for ironic15:18
dansmithif you make it $COMPUTE_NODE, then I think it would be natural to apply the contents below that to any compute node the compute service manages,15:18
dansmithwhich is basically the templating thing done15:18
dansmithyes15:18
efriedokay, I can buy that.15:18
dansmithevery time I look at this spec it has been rev'd or rebased, which makes back-and-forth discussion on individual points kinda hard,15:19
dansmithso I'm going to reply to your reply to my comments on three patch revisions ago to capture this15:19
efrieddansmith: thanks.15:19
*** hoonetorg has joined #openstack-nova15:26
stephenfindansmith: Turns out adding a new column to an existing table with 'nullable=False, default=0' doesn't do what you'd think it does. We need 'server_default="0"' instead, for some reason15:28
stephenfinThe more you know15:28
stephenfinDjango's ORM _does_ work as expected15:28
efriedI remember something about this from a couple years ago15:28
dansmithstephenfin: yep, knew that15:28
dansmithstephenfin: however, you don't need a default either15:29
dansmithstephenfin: your object should handle all of that15:29
stephenfinFigured you might, but I mentioned it cos that also took me some time to handle that15:29
stephenfinHmm, without that SQLite complained about adding a non-nullable field without a default value15:29
dansmithstephenfin: you can't make it non-nullable15:29
stephenfinRight, that's what I ended up doing instead15:30
dansmithit needs to be nullable in the model and the schema, but the object can/should be non-nullable and just handle the translation across the upgrade boundary15:30
stephenfinOh, I assumed the DB model had to match the object15:31
stephenfinI'll tweak that, in that case15:31
dansmithno,15:32
dansmiththat's kind of the point of the object is to hide the differences in the model and the upgrade minutia from the above layers15:32
dansmithefried: I just realized I somehow didn't commit a comment on the spec from yesterday, relating to the version thing15:33
dansmithefried: what I was going to say is that I think that the file should be forwards and backwards compatible within a minor version,15:33
dansmither, within a major15:33
dansmithsuch that 1.0 should be parseable by a 1.9-knowing bit of code15:33
dansmithand similarly,  1.9 file should work for a 1.0-knowing old piece of code15:34
dansmiththe reason the minor is there is just as an early key for newer code to know if it should even look for new things, not to know if it should use the stricter or looser schecma15:34
dansmithand that the schema(s) should have additionalProperties:true in them15:34
dansmithsuch that we're always purely additive within a major, and the new stuff is ignore-able by old things15:35
dansmithi.e. less pedantic than our external API15:35
dansmithI say this because in reality people will be rolling multiple versions of compute code with a single version of a deployment tool, and having to know the precise minor expected by a particular RPM revision on a single node is going to be super annoying15:36
dansmithconfig files are supposed to be uuber stable and our handling of them across versions super gracious15:37
*** ttsiouts has quit IRC15:44
*** ttsiouts has joined #openstack-nova15:45
*** tssurya has quit IRC15:47
*** ag-47 has joined #openstack-nova15:48
*** ttsiouts has quit IRC15:49
gibiefried: I replyied to the $COMPUTE_HOST part of the spec and removed my -1. Besides this COMPUTE_HOSt identification thing I'm OK with the spec15:50
gibiefried: and I have to leave now (was no a meeting since you pinged)15:50
*** helenafm has quit IRC15:53
openstackgerritStephen Finucane proposed openstack/nova master: conf: Deprecate 'devname' field of '[pci] passthrough_whitelist'  https://review.opendev.org/67058515:55
*** davidsha has quit IRC15:56
*** beekneemech has quit IRC15:57
*** belmoreira has quit IRC15:58
*** bnemec has joined #openstack-nova15:58
openstackgerritArtom Lifshitz proposed openstack/nova master: migrations: libvirt: remove get_machine_ips()  https://review.opendev.org/67147115:59
artomsean-k-mooney, stephenfin ^^16:00
openstackgerritMerged openstack/nova master: bindep: Remove dead markers  https://review.opendev.org/67145216:00
*** eharney has quit IRC16:02
* stephenfin clicks16:02
*** rpittau is now known as rpittau|afk16:05
*** ratailor has quit IRC16:05
artomstephenfin, cheers!16:06
* artom wonders if another core could be recruited. gibi, efried?16:07
efrieddansmith: I don't see how you could expect 1.4-level code to be able to handle 1.5-level config16:08
efriedartom: we talking about remove get_machine_ips?16:10
artomefried, we are16:10
efriedlooking.16:10
artomThank you, appreciated :)16:10
dansmithefried: because the rule would be additive only16:11
dansmithefried: it works today with our nova.conf, we just have no version so we don't know anything about it16:11
efrieddansmith: wait, you mean 1.4 code would be able to load up 1.5 conf, but it would ignore any 1.5-isms?16:12
efriedSo schema-wise, the only difference is additionalProperties:true everywhere. But usage-wise, the deployer has to make sure their compute version is at 1.5 to use 1.5-isms -- which they had to do anyway, except now they have to do it explicitly instead of the code enforcing it.16:14
efrieds/explicitly/preemptively? or something/16:15
dansmithI'm not sure what you mean about the explicit operator tasks16:16
sean-k-mooneyefried: in v1 of this are we going to allow the provider yaml to modify any RP create by the virt dirver. i read the last version fo the spec as no. we would only beable to add new rps  as childern of the copute node16:16
efriedI get the parallel with nova.conf, where you can put in all the [foo]bar=baz you want and it'll get ignored by the code. But that's an artifact of oslo.config - we couldn't do anything about that if we tried.16:16
dansmithyou mean because you made them put the minor in there?16:16
sean-k-mooneyefried: well we could16:16
sean-k-mooneywe know all the valid filed we coudl check for any that are not registered16:16
sean-k-mooneyand raise an error16:17
sean-k-mooneywe just dont16:17
efrieddansmith: In both cases I'm assuming a file with schema_version:1.5 and some 1.5-specific values therein.16:17
dansmithsean-k-mooney: we're talking about the opposite thing, and he's right we can't check for that16:17
sean-k-mooneywe cant check for fileds and section in the config we dont have a config option registered for?16:18
sean-k-mooneythat seams like ti would be pretty trivail to do16:18
efrieddansmith: in the stricter impl (as proposed), if compute is at 1.4, it will fail.16:18
efriedin the looser impl (what you're suggesting), if compute is at 1.4, it will successfully load up the config, but only process the >=1.4-isms, ignoring the 1.5-isms.16:18
dansmithsean-k-mooney: can you hold on a sec, we're not even talking about the actual config file16:18
sean-k-mooneysure sorry to interupt16:18
dansmithefried: the operator should declare which "version of the docs" they're reading when they write the file, nova should not freak out about things it doesn't know about and not expect things to be present if the operator has clearly indicated they wrote the config file four versions ago16:19
dansmithefried: the alternative is just to look at what is present in the file and not worry about the minor, and only use the major to control large changes, which I think we've already discussed16:19
sean-k-mooneylike the version in heat templates?16:19
dansmithefried: but yes, all I'm saying is add additionalProperties:true, and just require the 1.5isms to not break the 1.4isms, and also not have compute fail if it expects 1.5 and only 1.4 is provided (which would break our upgrade promise, which has been in place since forever)16:20
dansmithsean-k-mooney: is the heat template version a format version? I thought that was a self-assigned revision so heat can tell when you've modified it16:20
sean-k-mooneyyes16:20
sean-k-mooneyits the schema version16:20
dansmithokay, then yes probably similar but I dunno what their semantics are16:21
sean-k-mooneyhttps://docs.openstack.org/heat/latest/template_guide/hot_spec.html16:21
sean-k-mooneyheat_template_version16:22
sean-k-mooney    This key with value 2013-05-23 (or a later date) indicates that the YAML document is a HOT template of the specified version.16:22
efrieddansmith: "1.5 schema and compute always accepts 1.4 config" -- absolutely16:22
efriedstill don't agree with the other direction.16:22
dansmiththat 1.4 should be able to read a 1.5 file?16:22
efriedright. If I lay down a 1.5 file, I expect the 1.5-isms to be observed, not ignored.16:23
dansmithso, here's how an upgrade has to go then:16:23
efriednoting that the file declares itself as 1.516:23
dansmith1. Start with 1.4 code and config everywhere16:23
dansmith2. Upgrade to 1.5 code over time16:23
dansmith3. Once all the 1.5 is deployed, then deploy 1.5 config everywhere, revisiting all nodes and restarting them again16:23
*** sapd1_x has joined #openstack-nova16:24
sean-k-mooneyIgnoring FFU is that not what we are ment to do in general16:24
efriedI see your point, you save the last restart if you do the loose way16:24
sean-k-mooneye.g. upgade code then modify config after16:24
dansmithor else you have to have two versions of all your ansible modules, or they have to embed the version awareness into the ansible modules16:24
dansmithso you're generating the right version for the *Exact* code version you're deploying16:24
efriedI'm trying to convince myself that the extra restart is worse than my new fields being ignored, and I don't know why until I go figure out the version diff between the code and the config and which fields were added in that span.16:27
*** gyee has joined #openstack-nova16:27
dansmithit's not just the extra restart,16:27
dansmithit's also the embedding of this knowledge into the ansible/puppet/whatever16:27
sean-k-mooneywe also might need to do reshapes right?16:27
*** brinzhang has quit IRC16:28
dansmithwell, I guess I'd hope we don't, which is another reason for my other comment,16:28
dansmithwhich is not allowing operators to randomly change/subtract inventory from what the virt driver is providing16:28
*** brinzhang has joined #openstack-nova16:28
sean-k-mooneyim just thinking about FFU whould you have to start the compute agent for each version16:28
sean-k-mooneyor just do one config update at the end16:29
efriedwe've removed all possibilities of reshape and affecting existing inventories from this version of the spec16:29
*** brinzhang has quit IRC16:29
sean-k-mooneye.g keep 1.2 all the way up to 1.5 cond and then update to 1.5 template or do you have to go lockstepp16:29
sean-k-mooneyefried: are you still allowing effect exiting RP16:29
efriedyes, but not existing *inventory*16:29
sean-k-mooneyby modifying tratis or adding new inventories16:30
efriedyou can't muck with VCPU16:30
efriedand by "existing" I mean "inventories the virt driver deals with explicitly".16:30
sean-k-mooneyim not conviced we shoudl allow creating inventories or modifying tratis on the RPs created by the virt driver16:30
sean-k-mooneyat least in v116:30
efriedwait, what??16:30
efriedThat's the entire point16:30
sean-k-mooneyi was suggesting only allow creating child RP of the compute node16:31
efriedNo16:31
sean-k-mooneyand giving you full contol of the RP16:31
efriedno child RPs16:31
efriedthat is way more complex16:31
efriedand will be harder to "fix" in the future.16:31
sean-k-mooneyhow have we solved the multi writer issue for the traits16:32
sean-k-mooneye.g. traits taht are set to be ensured in the provider yaml vs auto discovered16:32
dansmithsean-k-mooney: I mostly agree, but I understand why adding (and sometimes removing) traits will be necessary16:32
efriedAs currently suggested, auto traits would still take precedence. Let me get you the spot where I explained that...16:32
dansmithbut totes agree on inventory16:32
efriedhttps://review.opendev.org/#/c/612497/12/specs/train/approved/provider-config-file.rst@15916:33
dansmithit's a slippery slope,16:33
dansmithbecause you want them to be able to add/remove processor flag traits,16:33
dansmithbut if you let them remove things like the disabled trait, or something critical to the rest of nova, then they've broken the internals and don't know why16:33
dansmithwhich is why I commented as such on the spec16:33
cdenttrait mgt is the part that has me most concerned/confused16:34
sean-k-mooney right i was suggesting a seperate rp to avoid any possible conflcit with the virt driver16:34
efriedbut this is why we've taken all that stuff out16:34
* cdent nods16:34
efriedthe only thing that remains is the levels of hierarchy that would allow us to consider adding it back in the future without a major schema bump (or ugliness in the schema to work around that)16:35
efriedwhich (I think - I'm still trying to grok) is even more important if we want to ensure forward-compat of minor versions.16:35
efriedbut16:36
efriedif it's going to be the difference between getting this moving and having it stuck16:36
efriedwe can pare the schema down to only what's needed in v1.0 -- YAGNI+KISS16:36
dansmithsean-k-mooney: so, I'm really glad to hear you object to the random editing of the inventory by this file, which energizes me to take a more rigid stand on that point16:37
efrieddansmith: we've already declared that you're not allowed to edit inventory of resources that the virt driver knows about.16:37
*** ccamacho has quit IRC16:37
efried(while noting that at some point in the future we want this file to be able to do just that for things like allocation ratios and reserved values)16:38
dansmithefried: so then you can remove the "ensure" hierarchy level16:38
dansmithI totally do not think this is the place to be controlling allocation ratios, and if it's in this file, it shouldn't be in the place where you expose other non-virt inventory16:39
dansmithor change "ensure" to "add" or "additional" to make it clear that it's appending stuff16:39
dansmithbecause I don't know how you're going to explain or communicate to people that try to override inventory in that section otherwise16:40
efriedwe had "add" originally.16:40
dansmiththey're going to be like "dammit, I want to ENSURE that the VCPU inventory is 3"16:40
sean-k-mooneyright i was about to ask what does https://review.opendev.org/#/c/612497/12/specs/train/approved/provider-config-file.rst@197 actully do16:40
efriedgibi objected to that as being a verb and not idempotent16:40
dansmithI think I did too, so... additional16:40
sean-k-mooneyi read that as only that trait will be reported16:40
sean-k-mooneynot ensure that trait is appended to the virt dirver set16:41
dansmithyeah16:41
efriedokay, so:16:42
efried- s/ensure/additional/g16:42
efried- forward compat for $minor version (additionalProperties:true)16:42
efried- $COMPUTE_NODE with explanation that includes "all ironic nodes"16:42
efriedwhat else?16:42
dansmithnot all ironic nodes, but all nodes16:42
dansmithor "all nodes managed by this compute" or something like that16:42
sean-k-mooneymaybe call it $compute_service16:42
dansmithGOD16:43
dansmithno16:43
*** sapd1_x has quit IRC16:43
dansmithhave you read the comments from the last 24 hours?16:43
dansmithit's *not* the service, it's the node that provides inventory16:43
sean-k-mooneyok16:43
dansmiththat's the point :)16:43
* dansmith puts down his nerf gun16:43
sean-k-mooneyoh right16:43
sean-k-mooneyyes i was trying to say that i map node to a singel RP for a since server in my head. and that each ironci compute sevicce manage mulitpl phyical server each of which is a seper compute node but i think we mean the same thing and im jsut saying it badly16:44
openstackgerritLee Yarwood proposed openstack/nova master: WIP nova-next: Deploy noVNC from source  https://review.opendev.org/67149016:45
*** gibi has quit IRC16:45
dansmithsean-k-mooney: right, it's the terminology that is important I think, but obviously we're on the same page for mechanics16:45
dansmithit would be wrong to apply something that is declared to be "for the compute service" to the "compute nodes"16:45
sean-k-mooneyyes16:46
dansmithbut making the terminology match makes it clear that it's for the node, 1, 2, or 20 of them as managed by this service16:46
efriedexcept we're conflating that a bit with things like the DISABLED trait...16:46
efriedperhaps that's not the best example, but we've got traits on the RP that are really capabilities of the compute service...16:46
dansmithwe're headed in the right direction with that though16:47
dansmithdisabled predates nodes as a concept16:47
dansmiththis moves it closer to the right thing, which is move it to the schedulable entity16:47
sean-k-mooneywell if a compute service was disabled. all the compute nodes it managed would be unavailable until ironci moved them to be managed by another compute service16:48
dansmiththat's my point16:48
dansmithit used to be right, now it's wrong, disabled traits on compute nodes is making it right-er16:48
efriedalso, do you feel as though the virt driver should or should *not* be involved in the processing here?16:49
efriedcdent: this plays into whether auto traits can be added or not16:49
efriedIf we cut the virt driver out entirely, we can do the providers.yaml processing after update_provider_tree+update_traits without reorganizing the rt flow.16:50
sean-k-mooneyefried: we breifly discussed if the generic code should live in teh Resouce tracker or in the driver base class16:50
efriedYeah, I'm less concerned about which module the generic code lives in and more about where it's invoked from in the flow.16:50
sean-k-mooneyright i have a prefence but im wondering what dansmith thinks16:51
*** panda is now known as panda|off16:51
efriedI've been proposing (https://review.opendev.org/#/c/612497/10/specs/train/approved/provider-config-file.rst@205) that it be invoked from within update_provider_tree itself, giving the driver a certain amount of control16:52
sean-k-mooneyalso my perference change depening on what we allow in the current version and in the future16:52
dansmithefried: remember, I was mostly concerned about the optics of how it's viewed from reading the spec,16:52
dansmithbut I do think that making it as absolutely uniform as possible is important,16:52
dansmithand having it fully within the RT so that the RT refuses to update/replace anything the virt driver has done across the board would be the most consistent I think16:53
*** damien_r has quit IRC16:53
efriedincluding automatic traits?16:53
dansmithwell, I really think allowing them to remove traits by this mechanism is dangerous, as I said16:53
sean-k-mooneyefried: my perfernce would be that the behavior would be the same regardless of the virt driver if at all possible16:53
dansmithyes ^16:54
*** igordc has joined #openstack-nova16:54
cdentis there any mechanism to remove traits?16:54
efriedIn this iteration only adding traits is allowed, so the difference is whether, when I try to add a trait that's otherwise dealt with by the compute manager, it sticks or not.16:54
efriedcdent: not yet, but we've been trying to leave it open for that possibility (in some form) in the future.16:54
dansmithdefinitely should not16:54
efriedokay.16:54
efriedso16:54
sean-k-mooneyif we allw modifcation of inventores/traits creted by  the virt driver i also conceed we might want to delgate processign to the virt driver at that point16:54
dansmithefried: don't we have a declaration of which traits are owned by the compute and virt, so that we can wholly box off those anyway?16:55
efriedtoday: update_provider_tree => update_auto_traits16:55
efriedtomorrow: update_provider_tree => process_providers_yaml => update_auto_traits16:55
efrieddansmith: no, unfortunately not16:55
efriedand in fact, the above mixes poorly16:55
sean-k-mooneydansmith: not really. unless we say provdier.yaml can only use CUSTOM_16:55
dansmithefried: well, maybe we should do that as part of this.. I know we discussed it before16:55
sean-k-mooneywhich i think is too restrictive16:55
dansmithsean-k-mooney: well, that would probably not be too bad, IMHO16:55
efriedbecause update_provider_tree may have some traits it enforces16:55
dansmithit would clearly draw a box around the things you're doing as being purely localized customization and not mucking with internal features16:56
efriedbut then update_auto_traits (which is not under control of the virt driver -- except as declared by the compute capabilities dict) has others16:56
sean-k-mooneyit would be nice to be able to use a standard hyper treading treat or secure boot trait16:56
sean-k-mooneyand use the file to add them if its supported16:56
efrieddansmith: unfortunately it's not easy to do. See venn diagram here https://docs.openstack.org/nova/latest/reference/update-provider-tree.html#taxonomy-of-traits-and-capabilities16:56
dansmithsean-k-mooney: but why would that not be exposed by the driver if it's available and enabled? making operators track that is dumb16:56
sean-k-mooneyim not sure if those are actully good examples16:57
efriedthat is, we've identified the problem before, but punted on trying to solve it because it's too hard.16:57
dansmithefried: CUSTOM_ would make it pretty easy16:57
sean-k-mooneydansmith: well the hypertreading tread is explcitly not owned by the virt driver16:57
efriedhum16:57
dansmithsean-k-mooney: why?16:57
sean-k-mooneyits stated that way to allow the cpu tread polices to work16:57
dansmithsean-k-mooney: give me a reason that makes sense, not one that is tied to how things work today :)16:58
sean-k-mooneythis is why i said that might not be a good example but its in che CPU standaisation in placement spec16:58
dansmithack16:59
sean-k-mooneylast paragrh in https://github.com/openstack/nova-specs/blob/master/specs/train/approved/cpu-resources.rst#add-hw_cpu_hyperthreading-trait16:59
sean-k-mooneywell that section in general.16:59
sean-k-mooneyim not sure if there are standard traits you would want to manage this  way16:59
sean-k-mooneyi just didnt want to assuem there wasnt17:00
*** derekh has quit IRC17:00
dansmithI think saying that these things are all restricted to the CUSTOM_ realm is a good line, IMHO17:00
efriedI think I can buy CUSTOM_ only.17:00
sean-k-mooneyagain for v1 we could say just CUSTOM_ untill we have a usecase that requires standard traits17:00
*** udesale has quit IRC17:00
dansmithefried: you willing to say that for traits and inventory or just the former?17:01
sean-k-mooneye.g. you can only have CUSTOM_ resouce classes too?17:01
dansmithI'm less sure about it for inventory, but it does eliminate a lot of my concern over overriding virt inventory17:01
efriedwell, in both cases it would be nice to be able to propose standard so that, if/when those features become native, you don't have to reshape.17:01
sean-k-mooneyi think invntories are less of an issue17:01
efriedbut17:01
efriedI can see where it simplifies things to say CUSTOM_ only for now.17:02
dansmithefried: seems like a clearer line though17:02
efriedyes17:02
dansmithefried: do you actually expect people to define their own non-custom classes in placement? if they do they run up against id conflict right?17:02
sean-k-mooneywe have previosly agreed that that virt divers should not use CUSTOM_ stuff in general right17:02
efrieddansmith: no, they would have to propose them in the actual repos17:02
dansmithsean-k-mooney: except for ironic which *relies* on it17:03
dansmithefried: right, so then they have to reshape anyway17:03
sean-k-mooneyand i gues the vPMEM stuff17:03
sean-k-mooneyok ignore the virt driver wont use it thing17:03
efriedI'm saying if they propose the standard ones before they start customizing, they don't need to reshape.17:03
dansmithefried: that's a big if, but okay :)17:03
efriedanyway, I think trying to anticipate how reshapes play in here is a fool's errand17:03
cdentIt's an important question though17:04
dansmithI'm massively happier about all this if it's restricted to CUSTOM_17:04
efriedso yeah, CUSTOM only for both traits and resource classes is okay for this rev17:04
cdentif the point of the yaml file is to allow people to experiment on thing that they  then expect to some day become "normal"17:04
efriedcdent: yeah, that's where I was leaning17:04
dansmithcdent: that may be one use of it, but not the primary use I expect17:04
cdentI was going on what the spec says, because I _still_ have trouble comprehending who the user is here17:05
*** ag-47 has quit IRC17:05
sean-k-mooneythere may be some things we never want nova to own on the comptue node like the cyborg aclleartos so something may move out of the provdier.yaml to other service or jsut stay there17:05
dansmithcdent: the user is intel :/17:05
cdentit reads as "some hardware vendors want to get some stuff in faster than nova can do it,but still want nova to do it"17:05
dansmithcdent: pretty much :)17:06
cdenthawt17:06
*** xek has quit IRC17:06
sean-k-mooneywell RMD is one usecase17:06
sean-k-mooneythere are others17:06
sean-k-mooneyprobably17:06
cdentwhereas when it was coming in from the jay angle, I understood more as "sometimes we want to shape the hardware that is present to make it look different from what it says"17:07
dansmithI don't think that's jay's angle but I could be wrong17:07
sean-k-mooneywell jay would like to abstract where it makes sense too17:07
sean-k-mooneyto not expose every faset of the hardware topology17:07
dansmithand in his absence, I would claim that his angle is my angle, which is that this is for custom stuff, like accounting for fan capacity in aisles, etc17:07
sean-k-mooneyjust the bits that we need17:08
openstackgerritArtom Lifshitz proposed openstack/nova stable/rocky: [DNM] testing bug/1813789 revert resize events  https://review.opendev.org/67130317:08
sean-k-mooneydansmith: ya one of the usecase i was thinking of was power and termal cpasity17:08
cdentfans in aisles are so cool17:08
dansmithsean-k-mooney: yeah17:08
efriedSo then this suggests a flow like:17:08
efried0) parse and schema-validate the file. (This happens just once, on startup, and fails the compute service if something is wrong)17:08
efriedThen in the RT _update flow:17:08
efried1) update_provider_tree (as today). (If we ever decide we want to give the driver direct pre/post processing control over the providers.yaml content, we could pass the json blob as a kwarg here. But not now.)17:08
efried2) automatic traits (as today)17:08
efried3) merge in providers.yaml stuff. (I think a second level of validation happens here, and fails the compute service if something is wrong -- that should only be possible the first time through, so we're not worried about the service dying after having been running for a while)17:08
efried4) update_from_provider_tree (flush to placement) (as today)17:08
* cdent thinks it probably time to say goodnight17:08
efriedI'm not sure how to detect a conflict between a custom RC from upt and one from providers.yaml.17:10
sean-k-mooneythe validation of 3 might be as simple as make sure the intersection between the inventoires form each part of the merger is 017:11
efriedyeah, that's what I'm noodling17:11
sean-k-mooneye.g. an invenotry is not defiend both the provider and virt driver trees17:11
efriedthat puts a bit of extra onus on upt to make sure it doesn't "ignore resource classes it doesn't know about"17:11
efriedcause today we're careful to tell upt it must "ignore child providers it doesn't know about"17:12
sean-k-mooneyya that is related to the general problem of shareign RP between service.17:12
efriedbut I think that doesn't conflict.17:12
sean-k-mooneywhich for now we have punted17:12
efriedyes17:12
cdentwe keep having discussions about things knowing about things, and that makes me anxious. how does anything know?17:12
efriedit's the virt driver's job to know about the hardware resources it has the ability to assign to VMs.17:13
sean-k-mooneyright ad the provider.yamls would know about resoce that are not assinged to the vm but are indrecly consumed by it17:13
sean-k-mooneye.g  power17:13
*** eharney has joined #openstack-nova17:13
sean-k-mooneyor cache if the cache is affiend outside the virt dirver17:14
dansmithefried: the validation becomes "is CUSTOM_ and not already in the stuff I got from the virt driver" right?17:14
sean-k-mooneywhich you can do with rmd or sysfs and a crons script17:14
sean-k-mooneydansmith: i would hope so. or at least not signifcatly more complex17:14
sean-k-mooneythe majority fo the validate would be done when parsing the file17:15
dansmithyeah17:15
dansmithyeah17:15
efrieddansmith: yes, the concern I had was with idempotency. The second time through, the provider_tree we hand to upt will already contain the CUSTOM_ RCs from the last iteration when we processed providers.yaml. So upt has to *remove* those, or we'll blow up when we process the providers.yaml blob the second time.17:15
*** igordc has quit IRC17:15
dansmithah I see17:16
efriedif we think of upt's responsibility as simply "completely overwite the inventories for the providers I own" then it works.17:16
dansmithmaybe just not fail if they're identical?17:16
*** igordc has joined #openstack-nova17:16
efriedyeah, or that, that could work.17:16
efriedum17:16
dansmithjust "isn't already defined or is exactly the same"17:16
efriedexcept "identical" needs to be forgiving of defaults17:16
efriedbecause my providers.yaml is allowed to give only "total" and let the other fields default.17:16
* cdent smhs17:17
dansmithit's already limited to CUSTOM_ so there wouldn't be any of those right?17:17
sean-k-mooneyis identical would require the virt driver to have the infor from the yaml to compare agaisnt17:17
efrieddefault inventory values, like min_unit etc.17:17
cdentgood luck, gotta make dinner17:17
dansmithefried: oh I see,17:17
efriedo/ cdent17:17
* cdent goodnights17:17
sean-k-mooneyunless the virt driver kept a list of the invetores it managed and only looked at those17:17
dansmithwell, I'm sure you can work that out17:17
sean-k-mooneycdent: o/17:17
efriedsean-k-mooney: the virt driver does that17:17
dansmithsean-k-mooney: I think what you mean is just mark in the provider tree where each thing came from17:17
sean-k-mooneyright so if it igores inventories not in that list17:17
dansmithso we can check the origin17:17
*** cdent has quit IRC17:18
efriedexcept "only looked at those" is what I'm saying *doesn't* work.17:18
sean-k-mooneyya but we dont have an owner on the inventory to do that currently17:18
sean-k-mooneyor ever17:18
efriedbecause we're enforcing that providers.yaml is not allowed to muck with resources upt controls.17:18
sean-k-mooneyso we would have to determin that in the RT17:18
efriedyes17:18
sean-k-mooneywhci we could do if we updated form teh provder.yaml first17:18
sean-k-mooneythen called the virt dirver17:19
efriednot the second time around.17:19
sean-k-mooneythen added the auto tratis17:19
*** panda|off has quit IRC17:19
sean-k-mooneywe should be able to mark them second time around17:19
efried"mark" how?17:19
efriedYou're talking about adding a metadata field to the ProviderTree object or something?17:19
dansmithefried: that's what I meant, but I'll leave it to you about what approach is best for that conflict resolution17:20
sean-k-mooneywe woudl still get the set form teh file and then the tree we pass into upt we embed a flag in each inventory17:20
efriedugh, that seems overly complicated to me.17:20
sean-k-mooneyefried: yes but not one that need to ever leave nova17:20
efriedyeah, I get that17:20
efriedI would just hate to explode the compute service because of a cache bug.17:20
efriedmaybe we take advantage of the init kwarg17:21
efriedand only do that check the first time through.17:21
efriedbecause that's the only time we're worried about it anyway.17:21
dansmithas long as we don't re-load the yaml, that would be reasonable It hink17:21
sean-k-mooneywell the work flwo would be. get prov_tree from placement. generate tree from file. merge them and mark any that are common as from the file then pass it to the driver upt meethod17:21
*** panda has joined #openstack-nova17:21
efriedyeah, we're definitely only loading the yaml once.17:21
efriedotherwise the admin can blow up the compute service with a typo.17:22
sean-k-mooneywe would have to load it one each agent start17:22
efriedyes17:22
sean-k-mooneywe can keep the file in memroy bettwen update_resouce calls in the RT17:23
efriedyes17:23
efriedas an attr on the rt17:23
sean-k-mooneysure17:23
dansmithefried: yep17:23
sean-k-mooneyso on the second iterate we just mark anny inventory we get from placement that is in that cached tree as form_file17:23
sean-k-mooneyor whatever17:23
sean-k-mooneyif we did not want to blow up the virt drivers17:24
sean-k-mooneywe could actully remove thos nodes tepmproally before we pass the tree to the driver17:25
sean-k-mooneyand add them back after17:25
sean-k-mooneythat a liitle more complext then i would like but you would hate my other idea more17:26
efriedanyway, we're in implementation weeds here. Do y'all want to see this flow explicitly described in the spec or can we leave it vague-ish and sort it out in code?17:26
dansmithI think some of it in the spec would be good so we don't re-have this convo17:26
sean-k-mooneyit would be nice to see it in the spec but ill leave that up to dan.17:26
efriedack17:27
sean-k-mooneyefried: you could also summerise it to the mailing list? and then put the high level flow in the spec17:27
sean-k-mooneydansmith: efried on a different topic are ye ok with backport this to stien. the low constratit for sqlalchemy on stable/stine is above teh version wehre that was depercated17:42
sean-k-mooneyhttps://review.opendev.org/#/c/664193/217:42
efriedsean-k-mooney: I'm not stable fwiw17:42
sean-k-mooneyits not?17:43
efriedI'm saying, I can't +2 a backport17:43
sean-k-mooneyoh17:43
efriedWhat would the motivation be for backporting that?17:43
sean-k-mooneyno i just wanted to know if ye are ok with me proposing ths17:43
efriedjust to reduce log noise?17:44
sean-k-mooneywell we backported it down stream becasue rhel8 uses a version of sqlacamy that is new the the upper constatine on stable/stine17:44
sean-k-mooneyso it was causing helping to cause the subunit parser explotion17:44
sean-k-mooneyin our downstream functional job17:45
*** hogepodge has quit IRC17:45
sean-k-mooneythat was not enought to fix the job donwstream but was one of the noiser things17:45
efriedI confirm that sqla l-c in stein is above 0.8.0, so procedurally there's no reason not to do it.17:45
efriedhttps://opendev.org/openstack/nova/src/branch/stable/stein/lower-constraints.txt#L15017:45
*** seyeongkim has quit IRC17:45
efriedso sure, if it helps ya, I don't object.17:45
efriedBut again, I can't +2 it.17:45
*** guilhermesp has quit IRC17:46
sean-k-mooneysure but you are ptl so its still good to check with you.17:46
efried:) thank you17:46
openstackgerritsean mooney proposed openstack/nova stable/stein: Replace joinedload_all with joinedload  https://review.opendev.org/67153217:47
sean-k-mooneyill leave it up to the stable cores to weight in ^17:47
*** hogepodge has joined #openstack-nova17:47
sean-k-mooneyi can always abandon it17:47
openstackgerritJim Rollenhagen proposed openstack/nova master: ironic: take over instances from down compute services  https://review.opendev.org/67153417:48
*** seyeongkim has joined #openstack-nova17:48
*** guilhermesp has joined #openstack-nova17:48
sean-k-mooneycurrently im hoping adding --suppress-attachments to our downstream tox job will fix the sub unit issue at least for now17:48
sean-k-mooneythat will skip the stdout and stderror for succesfful tests which grealy reduces the test output17:49
sean-k-mooneybut still give you all the output if a test fails17:49
sean-k-mooneybtu we dont know if that will be enough so suppressing deprecation warnings also helps17:49
*** ralonsoh has quit IRC17:51
*** mgariepy has quit IRC17:53
*** gibi has joined #openstack-nova17:53
*** mgariepy has joined #openstack-nova17:57
*** psachin has quit IRC18:04
*** irclogbot_1 has quit IRC18:07
*** altlogbot_1 has quit IRC18:07
*** irclogbot_3 has joined #openstack-nova18:08
*** altlogbot_3 has joined #openstack-nova18:09
efrieddansmith: does ironic hash ring reshuffle require compute restart?18:45
dansmithefried: no18:45
efriedI guess that still works, though, since you've already parsed the file.18:45
efriedthx18:45
dansmithyeah18:45
efriedbut means we can't rely on the 'startup' arg18:46
*** Bidwe_jay has quit IRC18:46
efriedexcept19:00
efriedif one of the new ironic nodes has inventory in a RC we've been happily adding on at the behest of the providers.yaml19:00
efriedthen we'll blow up the compute service.19:00
*** luksky11 has joined #openstack-nova19:00
dansmithmeaning if someone provides CUSTOM_IRONIC_GOLD in providers.yaml?19:01
efriedyeah19:01
efriedwell, isn't that a trait? Not worried about traits19:01
efriedRC is what we blow up on19:01
dansmithyeah, that's going to be a hard case to reason about I guess, because ironic is re-using customs19:01
dansmithno, it's an RC19:02
openstackgerritGhanshyam Mann proposed openstack/nova master: Replace "integrated-gate-py3" template with new "integrated-gate-storage"  https://review.opendev.org/67155119:02
efriedokay19:02
dansmiththat's the whole point19:02
dansmithso what about this:19:02
dansmithif we're on init=true, we set any providers inventory that isn't already in the tree, and explode otherwise19:02
efriedI think I can swing the "don't error if identical" thing, it's just going to be a bit tricky because I have to ignore fields (like min_unit) that weren't in the config.19:02
dansmithif we're init=false, we set any inventory that isn't already in the tree, but ignore/warn otherwise19:02
*** lbragstad has quit IRC19:02
efriedthat seems safer, anyway.19:03
efriedcould do that regardless19:03
*** ricolin_ has joined #openstack-nova19:03
*** ricolin has quit IRC19:05
*** gibi has quit IRC19:15
*** _erlon_ has joined #openstack-nova19:23
*** gibi has joined #openstack-nova19:28
*** maciejjozefczyk has quit IRC19:31
*** whoami-rajat has quit IRC19:44
*** bbowen has quit IRC19:51
*** pcaruana has quit IRC20:01
*** tesseract has quit IRC20:05
*** mvkr_ has joined #openstack-nova20:05
openstackgerritEric Fried proposed openstack/nova-specs master: Spec: Provider config YAML file  https://review.opendev.org/61249720:13
efrieddansmith, sean-k-mooney: ^20:13
*** dakshina-ilangov has joined #openstack-nova20:15
efriedartom: that took me a while, but reviewed (CONF.my_ip warning)20:27
artomefried, aha, thanks!20:28
artomI did feel a bit weird about taking out a warning, I mean, it was added for a reason, right?20:30
efriedartom: I linked the reason20:31
efriedwhich looks like it was a legit reason... when it was an exception.20:31
artomExactly20:32
efriedBut as a warning, not sure if it's really worthwhile or not.20:32
artomWhen it turned into a warning, is it really useful?20:32
efriedI'm not sure20:32
efriedit depends how the cold migration failure manifests20:32
*** eharney has quit IRC20:32
efriedif it's one of those things where it's really hard to figure out why it happened, unless you have this warning, then we might want to keep it around.20:32
efriedthen again, are you really going to notice this warning waaay back in the logs while you're investigating your cold mig failure.20:33
* artom tries to see where get_host_ip_addr is used20:36
artomTo set migration.dest_host20:36
artom(Which AFAICT isn't actually used for anything)20:36
artomAh, no, it's passed to migrate_disk_and_power_off20:36
artomAnd then is used in the actual cleanup catch-all Exception handler20:38
artomSo yeah, problems20:38
*** takashin has joined #openstack-nova20:49
*** dpawlik has quit IRC20:53
efriednova meeting in 4 minutes in #openstack-meeting20:56
*** priteau has quit IRC21:05
*** eharney has joined #openstack-nova21:08
*** belmoreira has joined #openstack-nova21:20
*** bbowen has joined #openstack-nova21:26
*** igordc has quit IRC21:27
*** igordc has joined #openstack-nova21:28
*** beekneemech has joined #openstack-nova21:38
*** beekneemech has quit IRC21:38
*** belmoreira has quit IRC21:44
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (13)  https://review.opendev.org/57602021:49
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (14)  https://review.opendev.org/57602721:49
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (15)  https://review.opendev.org/57603121:50
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (16)  https://review.opendev.org/57629921:50
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (17)  https://review.opendev.org/57634421:50
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (18)  https://review.opendev.org/57667321:51
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (19)  https://review.opendev.org/57667621:51
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (20)  https://review.opendev.org/57668921:51
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (21)  https://review.opendev.org/57670921:52
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (22)  https://review.opendev.org/57671221:52
openstackgerritTakashi NATSUME proposed openstack/nova master: Add database schema upgrade check  https://review.opendev.org/66704721:54
openstackgerritTakashi NATSUME proposed openstack/nova master: Add a live migration regression test  https://review.opendev.org/64120021:54
openstackgerritTakashi NATSUME proposed openstack/nova master: Fix cleaning up console tokens  https://review.opendev.org/63771621:54
*** JamesBenson has quit IRC22:00
*** bnemec has quit IRC22:03
*** alex_xu has quit IRC22:05
*** alex_xu has joined #openstack-nova22:09
*** slaweq has quit IRC22:09
*** bnemec has joined #openstack-nova22:13
*** eharney has quit IRC22:16
*** artom has quit IRC22:23
dustinc_OSCONAnyone use any tools for reviewing local diffs before pushing other than ‘git diff’?22:36
*** bnemec has quit IRC22:42
*** bnemec has joined #openstack-nova22:43
*** bbowen has quit IRC22:45
*** ivve has quit IRC22:54
*** luksky11 has quit IRC22:58
*** tkajinam has joined #openstack-nova22:58
*** TxGirlGeek has quit IRC23:01
*** TxGirlGeek has joined #openstack-nova23:03
*** rcernin has joined #openstack-nova23:15
*** artom has joined #openstack-nova23:16
efrieddustinc_OSCON: I have in the past, don't really anymore. Long ago I used one called beyond compare. But I don't remember whether it worked with diffs (à la git) or with two actual copies of the file, probably the latter.23:17
efriedIf I'm really having trouble seeing what I want to see via git diff, I'll actually just push the change to gerrit and review it there.23:18
*** JamesBenson has joined #openstack-nova23:33
*** JamesBenson has quit IRC23:37
*** yaawang has quit IRC23:53
*** tbachman has quit IRC23:53
*** yaawang has joined #openstack-nova23:53
*** TxGirlGeek has quit IRC23:55

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