Thursday, 2016-04-07

*** amrith is now known as _amrith_00:21
*** ebalduf has quit IRC00:22
*** _amrith_ is now known as amrith00:40
*** vilobhmm111 has quit IRC00:41
*** vilobhmm11 has joined #openstack-meeting-cp00:46
*** annegentle has joined #openstack-meeting-cp00:49
*** annegentle has quit IRC00:54
*** harlowja has quit IRC01:00
*** harlowja has joined #openstack-meeting-cp01:03
*** sdake has quit IRC01:28
*** sdake has joined #openstack-meeting-cp01:32
*** amrith is now known as _amrith_01:59
*** sdake_ has joined #openstack-meeting-cp02:20
*** sdake has quit IRC02:22
*** openstackstatus has quit IRC03:01
*** sdake_ has quit IRC03:06
*** sdake has joined #openstack-meeting-cp03:07
*** ebalduf has joined #openstack-meeting-cp03:16
*** sdake has quit IRC03:17
*** sdake has joined #openstack-meeting-cp03:18
*** sdake has quit IRC03:28
*** sheel has joined #openstack-meeting-cp03:41
*** sekrit has quit IRC03:51
*** sekrit has joined #openstack-meeting-cp04:05
*** persia has quit IRC04:31
*** persia has joined #openstack-meeting-cp04:33
*** askb has joined #openstack-meeting-cp04:38
*** xyang1 has quit IRC04:48
*** askb has quit IRC06:23
*** ebalduf has quit IRC06:37
*** vgridnev has joined #openstack-meeting-cp06:47
*** vgridnev has quit IRC08:02
*** openstackstatus has joined #openstack-meeting-cp08:29
*** ChanServ sets mode: +v openstackstatus08:29
-openstackstatus- NOTICE: jobs depending on npm are now working again08:33
*** vilobhmm11 has quit IRC09:09
*** vgridnev has joined #openstack-meeting-cp09:17
*** Kiall has quit IRC10:14
*** Kiall has joined #openstack-meeting-cp10:14
*** sdague has joined #openstack-meeting-cp10:20
*** kmartin has quit IRC10:28
*** vgridnev has quit IRC11:39
*** _amrith_ is now known as amrith11:44
*** ChanServ changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"11:45
*** vgridnev has joined #openstack-meeting-cp12:03
*** jhesketh has quit IRC12:07
*** jhesketh has joined #openstack-meeting-cp12:07
*** raildo-afk is now known as raildo12:18
*** sigmavirus24_awa is now known as sigmavirus2412:47
*** annegentle has joined #openstack-meeting-cp12:51
*** xyang1 has joined #openstack-meeting-cp13:26
samueldmqthingee: fyi I updated patch 295940 to fix oslo reference, as per dhellmann's review13:27
*** annegentle has quit IRC13:38
*** ebalduf has joined #openstack-meeting-cp13:59
*** rpjr_ has joined #openstack-meeting-cp14:05
*** sdake has joined #openstack-meeting-cp14:07
*** sdake has quit IRC14:12
*** sdake has joined #openstack-meeting-cp14:21
*** sigmavirus24 is now known as sigmavirus24_awa14:55
*** sigmavirus24_awa is now known as sigmavirus2414:55
thingeesamueldmq: thank you!15:49
*** angdraug has joined #openstack-meeting-cp16:04
*** annegent_ has joined #openstack-meeting-cp16:08
*** vgridnev has quit IRC16:21
*** vgridnev has joined #openstack-meeting-cp16:21
*** david-lyle has quit IRC16:36
*** xyang1 has quit IRC16:47
*** annegent_ has quit IRC16:49
*** annegentle has joined #openstack-meeting-cp16:49
*** angdraug has quit IRC16:58
*** xyang1 has joined #openstack-meeting-cp17:02
*** vgridnev has quit IRC17:04
*** david-lyle has joined #openstack-meeting-cp17:06
*** david-lyle has quit IRC17:11
*** annegentle has quit IRC17:14
*** annegentle has joined #openstack-meeting-cp17:14
*** annegentle has quit IRC17:15
*** annegentle has joined #openstack-meeting-cp17:15
*** david-lyle has joined #openstack-meeting-cp17:17
*** david-lyle has quit IRC17:23
*** david-lyle has joined #openstack-meeting-cp17:56
*** david-lyle has quit IRC17:56
*** david-lyle has joined #openstack-meeting-cp17:58
*** vgridnev has joined #openstack-meeting-cp17:58
*** vilobhmm11 has joined #openstack-meeting-cp18:13
*** vilobhmm111 has joined #openstack-meeting-cp18:14
*** annegentle has quit IRC18:16
*** annegentle has joined #openstack-meeting-cp18:16
*** vilobhmm11 has quit IRC18:18
*** sdake_ has joined #openstack-meeting-cp18:26
*** sdake has quit IRC18:26
*** vilobhmm111 has quit IRC18:39
*** angdraug has joined #openstack-meeting-cp18:44
*** hemna is now known as hemnafk18:48
*** annegentle has quit IRC18:49
*** annegentle has joined #openstack-meeting-cp18:50
*** annegentle has quit IRC18:52
*** nikhil has quit IRC19:07
*** nikhil has joined #openstack-meeting-cp19:11
*** david-lyle_ has joined #openstack-meeting-cp19:13
*** vgridnev has quit IRC19:14
*** david-lyle has quit IRC19:15
*** sigmavirus24 is now known as sigmavirus24_awa19:17
*** david-lyle_ has quit IRC19:19
*** david-lyle has joined #openstack-meeting-cp19:29
*** vilobhmm11 has joined #openstack-meeting-cp19:30
*** david-lyle has quit IRC19:31
*** david-lyle has joined #openstack-meeting-cp19:31
*** david-lyle has quit IRC19:37
*** dtroyer_zz has joined #openstack-meeting-cp20:00
sdagueok, who is around to help with session scheduling?20:01
ttxo/20:01
dimso/20:01
sdague#startmeeting newton-cross-project-session-scheduling20:01
openstackMeeting started Thu Apr  7 20:01:51 2016 UTC and is due to finish in 60 minutes.  The chair is sdague. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: newton-cross-project-session-scheduling)"20:01
openstackThe meeting name has been set to 'newton_cross_project_session_scheduling'20:01
sdagueok, potentially useful for logging20:02
* mtreinish lurks20:02
* harlowja sorta lurks20:02
sdague#link https://etherpad.openstack.org/p/newton-cross-project-sessions20:02
dimshmm, won't add my nick at the top :)20:02
sdagueI added up all the scores earlier, and the results of the top 21 sessions were sent out to the tc ML20:02
sdague#link http://lists.openstack.org/pipermail/openstack-tc/2016-April/001159.html20:03
*** shamail has joined #openstack-meeting-cp20:03
sdaguefirst order of business, do we think any sessions should be 2x ?20:03
sdague#topic any 2x sessions20:03
*** openstack changes topic to "any 2x sessions (Meeting topic: newton-cross-project-session-scheduling)"20:03
ttxI don't think there is a session that really needs everyone and therefore would justify a more complex setup than 3x720:03
sdaguettx: oh, sorry, different question20:04
sdaguethough that's a good one20:04
ttxlet me see if there is anything really too short20:04
dtroyer_zzo/20:04
sdagueshould any session be a double block20:04
sdagueas in run long20:04
ttxyeah, I started typing before you topiced20:04
sdaguebut I agree we should look to do a 3 track by default and only do something diffferent if we have to20:04
ttxsdague: not sure any of the big topics is advanced enough that a double session would make it make progress a lot more than a single-session20:05
dimssdague : does not seem so20:05
dimsi mean don't see anything running too long20:05
sdagueok, fair enough, I'm fine with that20:05
ttxCo-installability is a long topic, but we are just breaking the subject20:05
sdaguethe deployment tools one was the only thing I was wondering about20:05
ttxsingle CLI maybe20:06
sdaguebut maybe if we stick that early in the day it will let those folks continue to discuss later20:06
ttxdeployment, they can decide to continue it on Friday20:06
ttxor even Tuesday yes20:06
sdagueok, so I also thought there were a few natural pairings like deployment & coinstall20:06
sdagueI stuck those in there20:07
ttxsdague: Maybe we should be clear that those are long topics that will surely not be solved in 40min and encourage people to meet afterwards20:07
sdagueyep20:07
dtroyer_zzthe continue on Friday is good, with some time inbetween to dig in small groups maybe20:07
sdagueok, should we start proposing things into slots and see where we get to?20:07
ttxRoom sizes will be roughly equivalent so no need to prioritize by popularity20:07
ttxLet me see if we group them by themes20:08
harlowjadef some kind of 'tech tebt theme'20:08
dtroyer_zz23 might follow the 13 then 6 chain well20:08
dims"API/CLI" is probably a theme20:09
dims9 and 23 are non-technical (community)20:10
ttxI think there are three big themes20:11
ttxGeneral policy/community decisions, like the EOL20:12
ttxImplementation of things that are already there or in progress, like CLI20:12
ttxAnd more... long-term technical design discussion20:12
dtroyer_zzI like 9 and 24 being together, there is some connection between them20:13
ttxThat makes 3x720:13
dtroyer_zzI think 9 should be ahead of 24, it might inform it somewhat20:13
ttxThough I did have to shoehorn 4 into the first category20:13
sdagueright 9 & 24 pair20:13
dimssorry i typoed before. yes 9/2420:13
sdagueso, I want to tweak this a little because I think we have audience overlap as well, let me propose a thing20:14
ttxsdague: saw my categorization on the etherpad ? makes sense for room split ?20:14
sdaguewell, except I think deploy & coinstall should go back to back20:14
ttxok20:15
sdaguebecause coinstallability is basically held back by the deploy folks20:15
dimsttx : 4 is borderline between practical and astroturf :)20:15
sdaguethey are the stake holders20:15
ttxLet's move Quto to room C then20:15
ttxQuota20:15
sdaguesure20:15
ttxand/or policy20:15
sdaguethe 2 policy should go back to back20:15
ttx4/20 is a bit in-between room B and C20:16
*** annegentle has joined #openstack-meeting-cp20:16
dims13 and 6, which one do we want to talk about first?20:16
dtroyer_zz13 I think?20:17
sdagueyeh, I'd rather make sure the pairings land together, and not across a break20:17
dimssure20:17
ttxmaybe swapping 22 and 23 ?20:17
sdaguesure, I'd be fine with that20:17
dtroyer_zzthose two may have a similar audience20:18
ttx22 sounds more practical/immediate than 2320:18
dimsagree20:18
ttxI like the split20:18
sdagueok, let me stare at this for a second and make sure I'm not screwed in my time blocks20:18
dtroyer_zzWe should swap 9 and 2420:19
* ttx adds too20:19
dims26 and 11 probably should be back to back20:19
dimsgood20:19
ttxI think I'm not screwed20:20
sdagueok, so we ruined dtroyer_zz20:20
dtroyer_zzswap the devstack pair with the policy pair?20:21
ttxideally we'd put the design summit split discussion at the end of the day, to limit bikeshedding20:21
sdagueyeh20:21
ttxand move the CLI discussion earlier20:21
sdaguedtroyer_zz: what about move CLI early?20:21
ttxso that we unscrew dtroyer20:21
dtroyer_zzI think the split discussion that has consequences for 2420:21
dtroyer_zzCLi early is good20:22
ttxlike swap with discovery20:22
sdaguettx I pushed it 2 blocks earlier20:22
sdaguebefore the coffee break20:22
ttxlet me see if we spread out the popular ones enough20:22
*** sdake_ is now known as sdake20:23
dtroyer_zzcan we swap (14,20) with (26,11)?20:23
ttxgood for me20:23
ttxbut maybe sdague wanted to be at the cross-project one20:24
sdagueok, that completely eliminates me from the room A meta discussions20:24
sdaguewhich might be fine20:24
dimsttx is all day in room A except for one20:24
sdagueyeh, that's fine20:25
dimswe don't let him out :)20:25
sdagueso, I would invert 26,11 if we keep them there anyway20:25
ttxsdague: ok move them and let's see how it works20:26
sdaguebut, yeh, I can live with the jump20:26
dtroyer_zzso B: 22, 1 11, 26, 16, 14, 2020:26
dtroyer_zzhowzzat?20:27
sdagueactually can we stick policy in C20:27
sdaguein the midblock20:27
ttxsdague: we could swap 24 and 9 (or 14 with 20) depending on which discussion from room A you prefer to be around for20:27
sdaguehow about that?20:28
dtroyer_zzworks for me20:28
sdagueit moves policy to the C room, and I inverted the order on the devstack ones so I can be in the service one20:28
sdaguethe v3 one I'm still not a huge fan of20:28
dimslgtm20:29
dtroyer_zzmaybe that's the one you need to be in then?20:29
*** shamail has quit IRC20:29
ttxlet's check moderators quickly20:29
sdaguedtroyer_zz: I'm not a huge fan of it on the schedule, because I don't see what is going to happen there that wouldn't happen in an email :)20:29
sdagueit's not like anything is controversial there, it just needs to be written down20:30
dtroyer_zzah, gotcha.20:30
sdagueright, there is definitely a mordred conflict20:31
sdague23 <-> 25?20:32
sdaguedtroyer_zz: that would put CLI in the first block20:32
ttx19/25 ?20:33
ttxhmm, or 12<->2520:33
sdaguesure, I think 19 <-> 25, 23 <-> 25, or 12 <-> 25 would all be fine20:34
ttxarh no20:34
sdaguewhat does 12 - 25 break?20:34
ttxwe need thingee in that cross-project one20:34
sdagueoh, right20:34
ttxconflict with 2420:34
ttxrevert20:35
sdagueyep20:35
dtroyer_zz19<->25?20:35
ttxI think mordred would want to be in co-installability20:35
sdaguesure, or 23 <-> 25?20:35
ttxworks for me20:35
dtroyer_zzI can live with it, but those two probably have some audience overlap20:36
dtroyer_zzer, 23 and 2220:36
sdaguedtroyer_zz: possibly20:36
ttxdtroyer_zz: how about we swap 19 and 23 now then20:36
dtroyer_zzsure20:37
sdagueok, ttx you c/p20:37
sdagueso we don't collide again20:37
sdaguethe joys of bubble sort on schedule20:37
dimsy20:37
dims:)20:37
ttxbeen off the wheel for the last 5 min, so taht was not me :)20:37
sdagueah, ok20:37
sdagueok, done20:37
sdaguethat looks about as sane a first pass as I can imagine20:38
ttxI think I preferred 19/23 the other way, but that may be a bit selfish20:38
sdagueI can take that and propose it to the dev list, and ask for feedback20:38
ttx(I would rather attend CLI on my last free slot)20:38
sdagueso, we could20:39
dtroyer_zzI'd prefer to be in 10 over 17, so ya, it can go back20:39
sdague19<->23 and 1<->2220:39
ttxsdague: that is a risky recipe, note that there is no way to please everyone20:39
sdaguettx: well, not so much feedback as hard conflicts at this point20:39
sdaguebecause who knows who is on the conf schedule20:39
ttxsdague: 19<->23 and 1<->22 +120:39
sdaguedtroyer_zz: ?20:40
dtroyer_zz+120:40
thingeeo/20:40
sdagueok20:40
sdaguepeople generally good with this as a draft?20:40
ttxsdague: it's fine posting it as a strawman and ask for conflicts, just say that it is already the result of an optimization, so we won't likely be able to accommodate every request20:41
dimssdague : LGTM20:41
ttxLGTM20:41
dtroyer_zzLGTM220:41
sdaguettx: yeh, I will word it correctly to only ask for resolution if you have a hard conflict20:41
sdagueok, I'll send that out in the morning20:42
ttxhmm, let me check something else quickly20:42
sdagueoh no20:42
ttxconference talks20:42
ttxI have the list of conflicts there pre-canned for DS planning20:42
ttxMonty has talks at 11:15 and 4:4020:43
ttx+ robclark at 4:4020:43
dimshe looks clear for those 2 slots20:43
dtroyer_zzthat may be ok, modulo distance?20:43
ttxI don't care about distance. Run20:43
dimshaha20:43
* dtroyer_zz makes note to bring roller blades20:44
dimsthis is texas :)20:44
ttxyes, looks good20:44
sdaguewhew20:44
sdagueok, thanks all.20:44
ttxfun uh20:45
sdague#action sdague to send email with schedule to list20:45
dtroyer_zzcool20:45
dimsnice20:45
sdague#action ttx to carve out 3x7 schedule block20:45
sdagueI can fill out details once you put the blocks there20:45
ttxmind you, that talk conflict data was lifted off the schedule a few weeks ago so likely to be corrupt by now20:45
sdaguesure20:45
dtroyer_zzgotta start somewhere20:46
ttxsdague: alright, will create that tomorrow morning20:46
sdaguesounds good20:46
sdaguethanks all20:46
ttxIt's pretty solid I think20:46
sdagueyeh, me too20:46
ttxsdague: thx a lot for driving20:46
sdagueno prob20:46
sdague#endmeeting20:46
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:46
openstackMeeting ended Thu Apr  7 20:46:28 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/newton_cross_project_session_scheduling/2016/newton_cross_project_session_scheduling.2016-04-07-20.01.html20:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/newton_cross_project_session_scheduling/2016/newton_cross_project_session_scheduling.2016-04-07-20.01.txt20:46
openstackLog:            http://eavesdrop.openstack.org/meetings/newton_cross_project_session_scheduling/2016/newton_cross_project_session_scheduling.2016-04-07-20.01.log.html20:46
*** rpjr__ has joined #openstack-meeting-cp20:56
*** david-lyle has joined #openstack-meeting-cp20:56
*** rpjr_ has quit IRC20:57
*** raildo is now known as raildo-afk21:11
*** rpjr_ has joined #openstack-meeting-cp21:57
*** rpjr__ has quit IRC22:00
*** xyang1 has quit IRC22:00
*** rpjr_ has quit IRC22:14
*** rpjr_ has joined #openstack-meeting-cp22:28
*** rpjr__ has joined #openstack-meeting-cp22:32
*** angdraug has quit IRC22:32
*** rpjr___ has joined #openstack-meeting-cp22:32
*** rpjr_ has quit IRC22:35
*** annegentle has quit IRC22:35
*** rpjr__ has quit IRC22:36
*** rpjr___ has quit IRC22:48
*** rpjr_ has joined #openstack-meeting-cp22:54
*** sdake has quit IRC22:54
*** sdague has quit IRC22:57
*** dtroyer_zz has left #openstack-meeting-cp22:57
*** sdake has joined #openstack-meeting-cp22:58
*** rpjr_ has quit IRC23:06
*** sdake has quit IRC23:12
*** vilobhmm111 has joined #openstack-meeting-cp23:15
*** vilobhmm11 has quit IRC23:17
*** markvoelker has quit IRC23:29
*** vilobhmm111 has quit IRC23:46
*** markvoelker has joined #openstack-meeting-cp23:59

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