Monday, 2019-03-04

*** jamesmcarthur has quit IRC00:00
*** jamesmcarthur has joined #openstack-meeting-alt00:00
*** jamesmcarthur has quit IRC00:02
*** ijw has joined #openstack-meeting-alt00:08
*** jamesmcarthur has joined #openstack-meeting-alt00:32
*** jamesmcarthur has quit IRC01:01
*** markvoelker has joined #openstack-meeting-alt01:02
*** sdake has joined #openstack-meeting-alt01:06
*** markvoelker has quit IRC01:07
*** cloudrancher has quit IRC01:09
*** cloudrancher has joined #openstack-meeting-alt01:10
*** cloudrancher has quit IRC01:14
*** cloudrancher has joined #openstack-meeting-alt01:15
*** jesusaur has quit IRC01:19
*** jesusaur has joined #openstack-meeting-alt01:25
*** ijw has quit IRC01:27
*** ijw_ has joined #openstack-meeting-alt01:27
*** ijw_ has quit IRC01:28
*** ijw has joined #openstack-meeting-alt01:29
*** ijw has quit IRC01:30
*** ijw_ has joined #openstack-meeting-alt01:30
*** sdake has quit IRC01:44
*** sdake has joined #openstack-meeting-alt01:48
*** diablo_rojo has joined #openstack-meeting-alt01:48
*** sdake has quit IRC01:59
*** markvoelker has joined #openstack-meeting-alt02:03
*** sdake has joined #openstack-meeting-alt02:05
*** diablo_rojo has quit IRC02:06
*** erus has quit IRC02:06
*** markvoelker has quit IRC02:06
*** erus has joined #openstack-meeting-alt02:07
*** sdake has quit IRC02:08
*** erus has quit IRC02:31
*** erus has joined #openstack-meeting-alt02:32
*** chason has quit IRC02:36
*** chason has joined #openstack-meeting-alt02:38
*** sdake has joined #openstack-meeting-alt02:41
*** sdake has quit IRC02:44
*** sdake has joined #openstack-meeting-alt02:51
*** ijw_ has quit IRC02:58
*** ijw has joined #openstack-meeting-alt02:59
*** jamesmcarthur has joined #openstack-meeting-alt03:01
*** jamesmcarthur has quit IRC03:05
*** ijw has quit IRC03:08
*** erus has quit IRC03:08
*** erus has joined #openstack-meeting-alt03:09
*** ijw has joined #openstack-meeting-alt03:09
*** sridharg has joined #openstack-meeting-alt03:14
*** yamamoto has joined #openstack-meeting-alt03:16
*** sdake has quit IRC03:24
*** sdake has joined #openstack-meeting-alt03:26
*** jamesmcarthur has joined #openstack-meeting-alt03:27
*** sdake has quit IRC03:41
*** jamesmcarthur has quit IRC03:41
*** janki has joined #openstack-meeting-alt03:52
*** yamamoto has quit IRC04:18
*** diablo_rojo has joined #openstack-meeting-alt04:32
*** yamamoto has joined #openstack-meeting-alt04:36
*** ijw has quit IRC04:37
*** ijw has joined #openstack-meeting-alt04:39
*** lbragstad has quit IRC04:44
*** ijw has quit IRC04:45
*** lbragstad has joined #openstack-meeting-alt04:54
*** sdake has joined #openstack-meeting-alt05:09
*** ijw has joined #openstack-meeting-alt05:15
*** sdake has quit IRC05:48
*** sdake has joined #openstack-meeting-alt05:53
*** sdake has quit IRC06:01
*** sdake has joined #openstack-meeting-alt06:02
*** sdake has quit IRC06:03
*** diablo_rojo has quit IRC06:04
*** apetrich has joined #openstack-meeting-alt06:30
*** igordc has quit IRC06:47
*** markvoelker has joined #openstack-meeting-alt06:48
*** slaweq has joined #openstack-meeting-alt07:15
*** markvoelker has quit IRC07:21
*** ircuser-1 has quit IRC07:22
*** jtomasek has joined #openstack-meeting-alt07:30
*** jrbalderrama has joined #openstack-meeting-alt07:33
*** yamamoto has quit IRC07:40
*** yamamoto has joined #openstack-meeting-alt07:41
*** rdopiera has joined #openstack-meeting-alt07:54
*** kopecmartin|off is now known as kopecmartin08:04
*** jesusaur has quit IRC08:06
*** jesusaur has joined #openstack-meeting-alt08:10
*** panda|ruck|off is now known as panda|ruck08:12
*** rdopiera has quit IRC08:13
*** rdopiera has joined #openstack-meeting-alt08:13
*** markvoelker has joined #openstack-meeting-alt08:18
*** tetsuro has joined #openstack-meeting-alt08:18
*** sridharg has quit IRC08:20
*** giblet is now known as gibi08:33
*** e0ne has joined #openstack-meeting-alt08:34
*** lbragstad has quit IRC08:46
*** tssurya has joined #openstack-meeting-alt08:47
*** markvoelker has quit IRC08:50
*** janki has quit IRC09:00
*** janki has joined #openstack-meeting-alt09:00
*** ttsiouts has joined #openstack-meeting-alt09:11
*** derekh has joined #openstack-meeting-alt09:34
*** e0ne has quit IRC09:40
*** markvoelker has joined #openstack-meeting-alt09:47
*** masahito has joined #openstack-meeting-alt09:57
*** masahito has quit IRC10:03
*** tetsuro has quit IRC10:15
*** e0ne has joined #openstack-meeting-alt10:16
*** erus has quit IRC10:16
*** erus has joined #openstack-meeting-alt10:17
*** yamamoto has quit IRC10:18
*** markvoelker has quit IRC10:21
*** yamamoto has joined #openstack-meeting-alt10:36
*** yamamoto has quit IRC10:36
*** yamamoto has joined #openstack-meeting-alt10:37
*** yamamoto has quit IRC10:41
*** erus has quit IRC10:41
*** erus has joined #openstack-meeting-alt10:42
*** ttsiouts has quit IRC11:04
*** ttsiouts has joined #openstack-meeting-alt11:05
*** ttsiouts has quit IRC11:09
*** e0ne has quit IRC11:10
*** e0ne has joined #openstack-meeting-alt11:11
*** yamamoto has joined #openstack-meeting-alt11:14
*** markvoelker has joined #openstack-meeting-alt11:18
*** erus has quit IRC11:19
*** erus has joined #openstack-meeting-alt11:20
*** thgcorrea has joined #openstack-meeting-alt11:43
*** markvoelker has quit IRC11:50
*** erus has quit IRC11:50
*** erus has joined #openstack-meeting-alt11:51
*** ttsiouts has joined #openstack-meeting-alt11:59
*** e0ne has quit IRC12:00
*** e0ne has joined #openstack-meeting-alt12:08
*** carlos_silva has joined #openstack-meeting-alt12:10
*** janki has quit IRC12:16
*** janki has joined #openstack-meeting-alt12:16
*** priteau has joined #openstack-meeting-alt12:30
*** jcoufal has joined #openstack-meeting-alt12:34
*** erus has quit IRC12:34
*** erus has joined #openstack-meeting-alt12:34
*** ttsiouts_ has joined #openstack-meeting-alt12:36
*** ttsiouts has quit IRC12:40
*** markvoelker has joined #openstack-meeting-alt12:48
*** yamamoto has quit IRC12:48
*** e0ne has quit IRC13:04
*** yamamoto has joined #openstack-meeting-alt13:16
*** markvoelker has quit IRC13:21
*** sdake has joined #openstack-meeting-alt13:23
*** jamesmcarthur has joined #openstack-meeting-alt13:24
*** jamesmcarthur has quit IRC13:32
*** jamesmcarthur has joined #openstack-meeting-alt13:33
*** yamamoto has quit IRC13:37
*** jamesmcarthur has quit IRC13:38
*** yamamoto has joined #openstack-meeting-alt13:39
*** takashin has joined #openstack-meeting-alt13:41
*** erus has quit IRC13:42
*** erus has joined #openstack-meeting-alt13:43
*** cloudrancher has quit IRC13:44
*** lbragstad has joined #openstack-meeting-alt13:49
*** rfolco is now known as rfolco|pto13:50
*** alex_xu has joined #openstack-meeting-alt13:52
*** tetsuro has joined #openstack-meeting-alt13:55
*** cdent has joined #openstack-meeting-alt13:59
efried#startmeeting nova-scheduler14:00
openstackMeeting started Mon Mar  4 14:00:24 2019 UTC and is due to finish in 60 minutes.  The chair is efried. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: nova-scheduler)"14:00
openstackThe meeting name has been set to 'nova_scheduler'14:00
takashino/14:00
alex_xu\o14:00
tetsuroo/14:00
edleafe\o14:01
gibio/14:01
cdento/14:02
efried#link agenda (just updated, please refresh) https://wiki.openstack.org/wiki/Meetings/NovaScheduler#Agenda_for_next_meeting14:02
bauzas\o14:02
efried#topic last meeting14:02
efried#link last minutes http://eavesdrop.openstack.org/meetings/nova_scheduler/2019/nova_scheduler.2019-02-25-14.00.html14:02
*** openstack changes topic to "last meeting (Meeting topic: nova-scheduler)"14:02
*** jamesmcarthur has joined #openstack-meeting-alt14:03
efriedold business:14:03
efried#link alloc cands in_tree series starting at https://review.openstack.org/#/c/638929/14:03
efriedmerged \o/14:03
cdenthuzzah14:03
efried#link the OVO-ectomy https://review.openstack.org/#/q/topic:cd/less-ovo+(status:open+OR+status:merged)14:04
efriedmerged \o/14:04
efriedthe rest we'll get to in new bizniss.14:04
efriedanything else from last week?14:04
efried#topic specs and review14:04
efried#link latest pupdate http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003385.html14:04
efriedpupdates are back \o/14:04
*** openstack changes topic to "specs and review (Meeting topic: nova-scheduler)"14:04
efried#link blueprint tracking https://etherpad.openstack.org/p/nova-stein-blueprint-status14:05
efried#link libvirt reshaper https://review.openstack.org/#/c/599208/14:05
efriedbauzas, what news?14:05
bauzasefried: I just provided a comment14:05
bauzasgiven the concern of alex_xu14:06
bauzasbut tbc, the series is done14:06
bauzaswe need reviews14:06
*** jamesmcarthur has quit IRC14:06
efriedo right, alex_xu would you please have a look?14:06
*** jamesmcarthur has joined #openstack-meeting-alt14:06
efriedSince you're here - if you still have concerns, we can discuss them in #opens14:06
alex_xuyea, sorry just saw the reply14:07
efriedor, uh, now I guess would also be fine.14:07
alex_xuno, my reading is slow, please go through other item first14:07
efriedsure thing.14:07
efried#link DRY/clean up placement objects starting at https://review.openstack.org/#/c/637325/14:08
*** helenafm has joined #openstack-meeting-alt14:08
efriedThis is getting tall. Much work is being done here. jaypipes has a -1 on the bottom, cdent has responded (TLDR: what jaypipes suggests is happening, just further up the chain)14:08
cdentI rebased that this morning, more than I initially intended14:08
efriedheh, I noticed14:08
cdentmy local tree had something already merged in it and I got confused14:09
efriedwhite belt mistake14:09
* cdent has never liked rebasing14:09
efriedanyway, most of those 15 reviews are pretty easy, more eyes would be most welcome.14:10
*** cloudrancher has joined #openstack-meeting-alt14:10
efried14 (/me can't count)14:10
cdentyeah, if we could get more of that merged, it would make the tallness less of a challenge14:10
efried#topic Extraction14:11
efried#link Extraction https://etherpad.openstack.org/p/placement-extract-stein-514:11
*** openstack changes topic to "Extraction (Meeting topic: nova-scheduler)"14:11
efriedwhoops, I put a link in the wrong place on the agenda...14:11
efried#link Placement is set up to use storyboard https://review.openstack.org/#/c/639445/14:11
efried^ is merged14:11
cdent#link storyboard: https://storyboard.openstack.org/#!/project_group/placement14:11
efriedwhat does this mean, that we've officially got a storyboard presence?14:11
efriedthanks cdent14:11
efriedI've never used storyboard before, will need to find the storyboard-for-dummies reference14:11
cdentyes, but we haven't yet solidified plans of how to use it14:11
cdentditto14:12
cdentI think they have some test projects too where it is possible to play around14:12
cdentrelated to storyboard: I marked as "fix committed" a bunch of bugs that were committed but hadn't been auto updated. there are a few left I'm not sure about:14:12
cdentwhich I suppose we can talk about during the bugs topic14:13
SotKhttps://storyboard-dev.openstack.org/ is the sandbox for storyboard14:13
SotKfor playing around in14:13
efriedThanks SotK14:13
bauzasto make it clear, you want to use storyboard for what ? blueprints only or bugs ?N14:13
efried#link storyboard sandbox https://storyboard-dev.openstack.org/14:13
*** sdake has quit IRC14:14
cdentbauzas: nothing yet, because we haven't yet made a plan and it seemed weird to try to make a plan at this stage in the cycle14:14
efriedwhy?14:14
bauzasok14:14
bauzaswhy to who ?14:14
bauzasme or cdent?14:14
efriedwhy shouldn't we try to figure out how we're going to use sb?14:15
bauzasme : because I'd like to know what to do when you want to provide some feature for placement14:15
bauzasthat's it14:15
efriedwhat are the options on the table?14:15
cdentwe should figure it out, but we don't need to rush to change anything because we don't want to confuse end users who might be wanting to report bugs _now_14:15
cdentand are not party to our meanderings14:15
cdentfor train related features I would think that creating stories in storyboard will be the way to go14:15
edleafeSome time at the PTG for SB discussion/education would be a help14:16
bauzasagreed with edleafe14:16
efriedWhat does it take to get, um, "subscribed" to new things that are put into sb against our project?14:16
bauzasor wait for the new PTL to decide :)14:16
cdentbut since we're not in a hurry in that direction, and people are focused on feature freeze and other things, I assumed we could put the SB planning on the back burner14:16
cdentefried: go to preferences under your name14:16
cdentwhere there are email settings you can choose14:17
edleafeYeah, let's not do StoryBoard 101 now14:17
efriedfigured it out.14:17
efriedIt was fairly intuitive, once I had realized I needed to log in.14:17
efriedso14:17
efriedIt's probably fairly obvious, having decided to use this thing at all, what should happen in the Train cycle.14:17
SotKfeel free to come and ask questions in #storyboard when you start trying to figure things out14:18
*** ttsiouts_ has quit IRC14:18
*** markvoelker has joined #openstack-meeting-alt14:18
efriedNamely: new features and long-term wishlist items should get a, um, "story". And bugs should be reported there too.14:18
efriedI think it's the interim between now and then that's not cut and dried14:18
efriedis that a reasonable assessment?14:18
*** ttsiouts has joined #openstack-meeting-alt14:19
cdentyes14:19
*** janki has quit IRC14:19
edleafeBe prepared for a "moving to git from svn" brain reshuffling. The workflow is not 1:1 to launchpad14:20
efriedso it seems to me as though we do need to figure out that interim, precisely so that people are not confused about where and how to report bugs14:20
cdentI think for "us" we can manage to use both launchpad and storyboard for the rest of the cycle, and in train it will be only storyboard. But for "them" I think asking people to switch not on a cycle boundardy is weird14:20
efriedthen this seems like an ideal transition period.14:20
efriedSend an email announcing we're migrating to SB14:20
efriedand that we'll continue accepting lp bugs until train opens14:20
* bauzas just loves the SB acronym14:21
efriedbut at that point we'll shut down lp (which I guess we won't/can't really do, but we can say it) and all bugs need to be reported in sb.14:21
*** ttsiouts has quit IRC14:21
bauzasAFAIK, there are some tools for migrating bugs from LP to SB14:21
efriedand meanwhile train specs should be opened in sb exclusively.14:21
*** ttsiouts has joined #openstack-meeting-alt14:21
jaypipesefried: sorry, was etherpadding about cyborg... yes, will try to get to that series today.14:21
efriedbauzas: I think that's the part we're planning to wait on, until train officially opens.14:21
cdentright: the main stickler here is that people will _always_ continue reporting bugs in launchpad, so we can't simply forget about it because nova isn't getting shut down14:21
efriedjaypipes: ack, thx14:22
bauzasyou should poke some folks in #storyboard that'd be happy to help you, incl. but not exhaustively fungi (IIRC)14:22
fungidefinitely not exhaustively ;)14:22
efriedyup, I get it cdent. When we officially cut over, we would I guess start marking placement bugs as Invalid in lp, requesting they be opened in sb instead.14:22
cdentsomething like that14:22
bauzasthere is an upgrade path14:22
bauzasagain, you should get info first14:22
cdentI really don't think we need to over analyzse this. there is a very small number of bugs that get reported on placement itself14:23
bauzasbut some projects already made the leap14:23
efriedand in the interim, we would respond to all such bugs with a message like, "Okay, we're dealing with this here now, but on such-and-such a date we're transitioning..."14:23
cdentwe just need to pay some attention and it will be fine14:23
efriedOkay, but in terms of immediate action, IMO somebody should send an email.14:23
cdentto which audience?14:23
cdentbecause we already did to "us"14:24
efriedML14:24
bauzasagain, before taking any action, just consider the migration path *first* :)14:24
*** janki has joined #openstack-meeting-alt14:24
cdentefried: I mean which audience within the ML14:24
bauzasunless you only wanna features14:24
efriedI can volunteer for that, though it'll have to be exclusively "what" since I have no idea on the "how".14:24
efried[placement] ought to suffice, no?14:24
*** jamesmcarthur has quit IRC14:24
efriedbecause we only care about people opening bugs/features against placement14:24
cdentefried: I'm asking if you mean end users/operators or devs? Because that changes the pitch of the message14:25
efriedit does?14:25
cdentIn any case:14:25
efriedLemme draft something14:25
efriedand I'll show it to you14:25
efriedand we can go from there14:25
cdent#action: cdent send a message about storyboard14:25
cdenti'll do it14:25
efriedI don't think this is rocket science14:25
efriedokay.14:25
efriedmoving on14:25
*** sdake has joined #openstack-meeting-alt14:25
cdentIt's not rocket science is what I've been trying to say for the last 10 minutes14:25
efriedanything else extraction?14:25
*** sdake has quit IRC14:25
cdentsome of the puppet stuff merged, which is cool14:26
cdentother than that, I think extraction is pretty much done for this cycle14:27
cdentit's next cycle when nova deletes placement that things get exciting again14:27
efriedcool14:28
efried#topic bugs14:28
efried#link Placement bugs https://bugs.launchpad.net/nova/+bugs?field.tag=placement14:28
*** openstack changes topic to "bugs (Meeting topic: nova-scheduler)"14:28
efriedcdent: you wanted to talk about some possibly-done bugs needing to be marked in lp?14:28
cdentyeah, one sec14:28
cdent#link https://bugs.launchpad.net/nova/+bug/169683014:29
openstackLaunchpad bug 1696830 in OpenStack Compute (nova) "nova-placement-api default config files is too strict" [Low,In progress] - Assigned to Corey Bryant (corey.bryant)14:29
cdent#link https://bugs.launchpad.net/nova/+bug/177859114:29
openstackLaunchpad bug 1778591 in OpenStack Compute (nova) "GET /allocations/{uuid} on a consumer with no allocations provides no generation" [Medium,In progress]14:29
cdentare either done or stuck, I'm not sure which14:29
cdentI dropped https://goo.gl/vzGGDQ from 17 to 6 earlier today14:30
cdentmostly because we no longer have auto reporting of "fix committed"14:30
efried\o/14:30
cdentI assuming we have a similar problem with bugs not yet marked as in progress:14:31
cdent#link https://goo.gl/TgiPXb14:31
cdentbut i haven't checked that and probably won't get to it today14:31
efriedso what needs to be done to move things along? Or is it necessary to move things along with any urgency?14:32
*** erus has quit IRC14:32
*** jrbalderrama has quit IRC14:33
*** beekneemech is now known as bnemec14:33
*** erus has joined #openstack-meeting-alt14:33
cdentno immediate urgency, but if any of those are "done" or "dead" they can be made to not cloud the storyboard waters14:33
cdentand just as a matter of principle a bug that hasn't had attention in a while isn't really real14:33
efriedokay.14:35
efried#topic opens14:35
efried(From last last week) Format of this meeting - new PTL to query ML14:35
efried(From last last week) Placement team logistics at PTG - new PTL to query ML14:35
efried#link post-extraction plans for placement specs/bps/stories http://lists.openstack.org/pipermail/openstack-discuss/2019-February/003102.html14:35
*** openstack changes topic to "opens (Meeting topic: nova-scheduler)"14:35
efriedlibvirt reshaper fup - alex_xu, ready to discuss?14:35
alex_xuyea14:35
efriedbauzas: ^14:36
bauzasyup14:36
alex_xumay i ask why we have this middle step https://review.openstack.org/#/c/599208/18? before we have multiple types14:36
bauzasbecause if not, we need to reshape once more14:36
efriedPerhaps alex_xu is suggesting we go straight to multiple type support14:36
bauzasthe original PS was only providing a single inventory per *type14:37
efriedalex_xu: I think we agreed to do it in stages just to keep the surface area manageable for stein.14:37
bauzasbut for NUMA awareness, that couldn't make it14:37
alex_xuoh...that is what i thought when I read the spec14:37
bauzasso, we decided to not just take only one aspect at once14:37
bauzasbut rather model the resources as the best for both affinity and type check14:37
bauzaseven if both affinity and type check features aren't there yet14:38
bauzas- just to prevent extra reshapes that are costly -14:38
bauzasHTH ?14:38
*** sdake has joined #openstack-meeting-alt14:38
*** jamesmcarthur has joined #openstack-meeting-alt14:38
alex_xuyea, i see the reason now14:39
alex_xubut in the end, when we have numa and multiple type, then we will put same type in the same RP, right?14:39
efriedI don't think so.14:39
efriedI think we would still split along pGPU lines.14:40
alex_xuwhat is the reason behind that ?14:40
efriedbecause it's still important to be able to map inventory units (placement) to PCI addresses (libvirt/linux)14:40
efriedand a given pGPU has a given number of VGPU units available14:41
efriedthat's assuming we keep the traits of all the pGPUs the same, which isn't necessarily going to happe14:41
efriedn14:41
efriedand if we were to change the config of a pGPU that had been consolidated with another of the previously-same type, we would have to reshape.14:41
bauzasyup, correct14:41
efriedwhereas if we keep them separate, we can just do the change.14:41
alex_xuyea, agree with that, at least a vm needn't a lot of vGPU14:41
bauzaswe will still provide inventories per physical GPUs14:41
alex_xuthen we simple the code a little since RP mapping to the PCI address14:42
bauzasif two pGPUs share same type, that's good, but that's still two RPs14:42
bauzasalex_xu: there is a spec on it14:42
*** cloudrancher has quit IRC14:42
bauzasthat basically says that yes14:42
alex_xucool, thanks, i got it14:42
*** cloudrancher has joined #openstack-meeting-alt14:43
*** cloudrancher has quit IRC14:43
bauzasalex_xu: fyk https://specs.openstack.org/openstack/nova-specs/specs/rocky/approved/vgpu-rocky.html14:43
efriedDo any of the other reviewers who have participated along the way want the opportunity to give it a nod before we +W it?14:43
bauzashonestly, except you and alex_xu... :p14:43
*** cloudrancher has joined #openstack-meeting-alt14:43
bauzasand matt co-authored, so he can't really argue14:44
alex_xubut at the edge case, like each two of PGPU only left 1 VGPU, and a VM is asking 2 VGPUs?14:44
efriedmriedem jaypipes cdent artom melwitt gibi14:44
efriedalex_xu: If requested in the same request group, fail. If requested separately, that request can be fulfilled.14:44
alex_xuor actually pGPU can provide enough number of VGPUs? that isn't the case worry about?14:44
alex_xuefried: but that required a different flavor14:45
gibiefried: I followed a bit. and I'm for representing separate PGPUs as separate RPs14:45
cdentI think the implementation is what we said it should be, and in general a different "physical" thing should be a different rp14:45
efriedif I were designing a flavor, and it had multiple vgpus in it, and I wanted to assure most-likely-to-fit, I would request resources1:VGPU=1&resources2:VGPU=1&...&resourcesN:VGPU=1&group_policy=none14:46
gibiat some point somebody will ask for the numa awareness of the vgpu-s and then we need to know which vgpu is coming from which PGPU which close to which numa node14:46
jaypipesefried: I'd like the opportunity.14:46
jaypipesplease14:46
efriedif I were being lazy and didn't care so much about most-likely-to-fit, I would request resources:VGPU=N14:46
alex_xuoh....request group can use like that14:46
efriedbut that would bounce in scenarios of high saturation as alex_xu mentions14:46
efriedjaypipes:  ack. So alex_xu if you approve, please don't +W14:47
bauzasyou lost me14:47
bauzasI was dragged from two mins14:47
alex_xuno, I will leave that to jaypipes, I'm not follow this series enough14:47
efriedokay14:48
efriedbauzas: I think we're clear.14:48
bauzasare we drawing something ?14:48
efrieda conclusion?14:48
alex_xuyes, I'm clean :)14:48
bauzasjust to make it clear, the reshape is just modeling resources14:48
* efried rolls out his Jump To Conclusions Mat.14:48
bauzasnot how you query them :)14:48
bauzasgiven you can't allocate more than a single vGPU atm, it's a no-brainer :)14:48
jaypipesfor the record, I've reviewed that series a number of times now. I think half my reviews are sitting in draft state because various others bring up identical points I was raising.14:49
jaypipesjust would like to do a once over on it.14:49
jaypipesfor peace of mind14:49
efriedthat would be helpful in any case jaypipes, thank you.14:49
*** sdake has quit IRC14:49
bauzastbh, the reshape change is hairy14:49
bauzashence why I'm very reluctant to have more than a single reshape :)14:49
*** markvoelker has quit IRC14:50
efriedyeah, it's not that it's a resource drain on the system or anything; it's just pretty complicated to code up. And a special-purpose chunk of code that's going to get run at most once in a deployment and then never used again.14:50
efriedso good to minimize how many reshapers we write overall.14:51
efriedanything else on this topic before we move on?14:51
efriedokay, other topics for open discussion before we close?14:51
efriedThanks everyone.14:52
efriedo/14:52
efried#endmeeting14:52
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:52
openstackMeeting ended Mon Mar  4 14:52:45 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_scheduler/2019/nova_scheduler.2019-03-04-14.00.html14:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2019/nova_scheduler.2019-03-04-14.00.txt14:52
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2019/nova_scheduler.2019-03-04-14.00.log.html14:52
*** helenafm has left #openstack-meeting-alt14:52
*** takashin has left #openstack-meeting-alt14:52
*** tetsuro has quit IRC14:53
cdentthanks efried14:53
*** sdake has joined #openstack-meeting-alt14:56
*** e0ne has joined #openstack-meeting-alt14:59
*** cloudrancher has quit IRC15:00
*** cloudrancher has joined #openstack-meeting-alt15:01
*** e0ne has quit IRC15:02
*** e0ne has joined #openstack-meeting-alt15:04
*** ttsiouts has quit IRC15:06
*** ttsiouts has joined #openstack-meeting-alt15:07
*** ttsiouts has quit IRC15:11
*** sdake has quit IRC15:11
*** priteau has quit IRC15:11
*** sdake has joined #openstack-meeting-alt15:16
*** erus has quit IRC15:34
*** erus has joined #openstack-meeting-alt15:34
*** cloudrancher has quit IRC15:39
*** cloudrancher has joined #openstack-meeting-alt15:41
*** janki has quit IRC15:42
*** cloudrancher has quit IRC15:47
*** markvoelker has joined #openstack-meeting-alt15:48
*** cdent has quit IRC15:48
*** cloudrancher has joined #openstack-meeting-alt15:55
*** sdake has quit IRC16:00
*** cloudrancher has quit IRC16:04
*** e0ne has quit IRC16:06
*** macza has joined #openstack-meeting-alt16:07
*** e0ne has joined #openstack-meeting-alt16:12
*** erus has quit IRC16:12
*** erus has joined #openstack-meeting-alt16:12
*** cloudrancher has joined #openstack-meeting-alt16:18
*** e0ne has quit IRC16:20
*** markvoelker has quit IRC16:21
*** e0ne has joined #openstack-meeting-alt16:22
*** e0ne has quit IRC16:23
*** gyee has joined #openstack-meeting-alt16:32
*** cdent has joined #openstack-meeting-alt16:34
*** yamamoto has quit IRC16:41
*** yamamoto has joined #openstack-meeting-alt16:52
*** yamamoto has quit IRC16:57
*** kopecmartin is now known as kopecmartin|off17:04
*** markvoelker has joined #openstack-meeting-alt17:18
*** erus has quit IRC17:18
*** erus has joined #openstack-meeting-alt17:19
*** sdake has joined #openstack-meeting-alt17:22
*** ijw has quit IRC17:41
*** erus has quit IRC17:41
*** erus has joined #openstack-meeting-alt17:41
*** markvoelker has quit IRC17:51
*** cloudrancher has quit IRC17:56
*** tssurya has quit IRC17:58
*** e0ne has joined #openstack-meeting-alt17:59
*** derekh has quit IRC18:05
*** e0ne has quit IRC18:17
*** diablo_rojo has joined #openstack-meeting-alt18:18
*** whoami-rajat has quit IRC18:24
*** jamesmcarthur_ has joined #openstack-meeting-alt18:32
*** jamesmcarthur has quit IRC18:35
*** jamesmcarthur_ has quit IRC18:41
*** panda|ruck is now known as panda|ruck|off18:41
*** markvoelker has joined #openstack-meeting-alt18:48
*** jamesmcarthur has joined #openstack-meeting-alt18:53
*** whoami-rajat has joined #openstack-meeting-alt18:58
*** jamesmcarthur has quit IRC18:59
*** jamesmcarthur has joined #openstack-meeting-alt18:59
*** ijw has joined #openstack-meeting-alt19:03
*** cloudrancher has joined #openstack-meeting-alt19:03
*** jamesmcarthur has quit IRC19:04
*** sdake has quit IRC19:07
*** ijw has quit IRC19:10
*** ijw has joined #openstack-meeting-alt19:12
*** e0ne has joined #openstack-meeting-alt19:13
*** ijw has quit IRC19:16
*** erus has quit IRC19:20
*** ijw has joined #openstack-meeting-alt19:20
*** erus has joined #openstack-meeting-alt19:20
*** markvoelker has quit IRC19:21
*** jamesmcarthur has joined #openstack-meeting-alt19:22
*** cloudrancher has quit IRC19:25
*** cloudrancher has joined #openstack-meeting-alt19:25
*** ijw has quit IRC19:27
*** ijw has joined #openstack-meeting-alt19:27
*** cloudrancher has quit IRC19:38
*** cloudrancher has joined #openstack-meeting-alt19:39
*** thgcorrea has quit IRC20:00
*** cloudrancher has quit IRC20:06
*** ijw has quit IRC20:08
*** markvoelker has joined #openstack-meeting-alt20:18
*** jamesmcarthur has quit IRC20:19
*** jamesmcarthur has joined #openstack-meeting-alt20:19
*** erus has quit IRC20:19
*** erus has joined #openstack-meeting-alt20:20
*** e0ne has quit IRC20:22
*** ijw has joined #openstack-meeting-alt20:45
*** jtomasek has quit IRC20:48
*** markvoelker has quit IRC20:51
*** sdake has joined #openstack-meeting-alt20:52
*** jamesmcarthur has quit IRC20:58
*** jamesmcarthur has joined #openstack-meeting-alt20:59
*** jamesmcarthur has quit IRC20:59
*** jamesmcarthur has joined #openstack-meeting-alt20:59
*** haleyb has left #openstack-meeting-alt21:01
*** haleyb has joined #openstack-meeting-alt21:01
*** whoami-rajat has quit IRC21:04
*** jamesmcarthur has quit IRC21:06
*** cdent has quit IRC21:25
*** jcoufal has quit IRC21:28
*** yamamoto has joined #openstack-meeting-alt21:33
*** ijw has quit IRC21:36
*** jcoufal has joined #openstack-meeting-alt21:37
*** jamesmcarthur has joined #openstack-meeting-alt21:37
*** yamamoto has quit IRC21:38
*** sdake has quit IRC21:41
*** sdake has joined #openstack-meeting-alt21:43
*** markvoelker has joined #openstack-meeting-alt21:49
*** ijw has joined #openstack-meeting-alt21:49
*** rnoriega has quit IRC21:52
*** rnoriega has joined #openstack-meeting-alt21:52
*** zzzeek has quit IRC21:54
*** zzzeek has joined #openstack-meeting-alt21:54
*** jamesmcarthur has quit IRC21:57
*** jamesmcarthur has joined #openstack-meeting-alt21:58
*** jcoufal has quit IRC22:02
*** ijw has quit IRC22:02
*** betherly has joined #openstack-meeting-alt22:07
*** carlos_silva has quit IRC22:07
*** betherly has quit IRC22:12
*** jamesmcarthur has quit IRC22:12
*** jamesmcarthur has joined #openstack-meeting-alt22:13
*** markvoelker has quit IRC22:21
*** cloudrancher has joined #openstack-meeting-alt22:33
*** cloudrancher has quit IRC22:38
*** sdake has quit IRC22:50
*** slaweq has quit IRC22:53
*** jamesmcarthur has quit IRC22:57
*** jamesmcarthur has joined #openstack-meeting-alt22:58
*** jamesmcarthur has quit IRC23:00
*** erus has quit IRC23:00
*** erus has joined #openstack-meeting-alt23:01
*** slaweq has joined #openstack-meeting-alt23:01
*** slaweq has quit IRC23:05
*** sdake has joined #openstack-meeting-alt23:12
*** betherly has joined #openstack-meeting-alt23:16
*** markvoelker has joined #openstack-meeting-alt23:18
*** betherly has quit IRC23:20
*** masahito has joined #openstack-meeting-alt23:21
*** masahito has quit IRC23:26
*** erus has quit IRC23:26
*** erus has joined #openstack-meeting-alt23:27
*** sdake has quit IRC23:35
*** dklyle has quit IRC23:39
*** macza has quit IRC23:48
*** markvoelker has quit IRC23:51

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