Tuesday, 2013-11-12

*** aignatov has quit IRC00:05
*** amytron has joined #openstack-meeting-alt00:05
*** julim has quit IRC00:11
*** wdennis has joined #openstack-meeting-alt00:12
*** amytron has quit IRC00:13
*** wdennis has quit IRC00:16
*** jcooley_ has joined #openstack-meeting-alt00:29
*** markwash has quit IRC00:29
*** jcooley_ has quit IRC00:32
*** jcooley_ has joined #openstack-meeting-alt00:34
*** sarob has joined #openstack-meeting-alt00:38
*** alazarev has quit IRC00:41
*** sarob has quit IRC00:43
*** eankutse has joined #openstack-meeting-alt00:49
*** sacharya has joined #openstack-meeting-alt00:50
*** wdennis has joined #openstack-meeting-alt00:56
*** yamahata has joined #openstack-meeting-alt00:56
*** sacharya has quit IRC00:57
*** dguitarbite has quit IRC01:01
*** gokrokve has quit IRC01:08
*** gokrokve has joined #openstack-meeting-alt01:08
*** nosnos has joined #openstack-meeting-alt01:12
*** gokrokve has quit IRC01:13
*** jcooley_ has quit IRC01:22
*** coolsvap has quit IRC01:28
*** tanisdl has quit IRC01:30
*** gokrokve has joined #openstack-meeting-alt01:39
*** eankutse has quit IRC01:40
*** bdpayne has quit IRC01:41
*** gokrokve has quit IRC01:48
*** nosnos_ has joined #openstack-meeting-alt02:01
*** gokrokve has joined #openstack-meeting-alt02:02
*** nosnos has quit IRC02:04
*** wdennis has quit IRC02:10
*** nosnos_ has quit IRC02:30
*** nosnos has joined #openstack-meeting-alt02:31
*** twoputt_ has quit IRC02:39
*** twoputt has quit IRC02:39
*** Barker has joined #openstack-meeting-alt02:40
*** jcooley_ has joined #openstack-meeting-alt02:42
*** tanisdl has joined #openstack-meeting-alt02:44
*** coolsvap has joined #openstack-meeting-alt03:05
*** ian_ott has quit IRC03:08
*** wdennis has joined #openstack-meeting-alt03:16
*** zane has quit IRC03:27
*** yamahata has quit IRC03:32
*** jcooley_ has quit IRC03:38
*** jcooley_ has joined #openstack-meeting-alt03:39
*** jcooley_ has quit IRC03:43
*** zane has joined #openstack-meeting-alt03:49
*** alazarev has joined #openstack-meeting-alt03:52
*** markwash has joined #openstack-meeting-alt04:00
*** alazarev has quit IRC04:04
*** alazarev has joined #openstack-meeting-alt04:08
*** Barker has quit IRC04:12
*** markwash has quit IRC04:20
*** jcooley_ has joined #openstack-meeting-alt04:26
*** yamahata has joined #openstack-meeting-alt04:30
*** jcooley_ has quit IRC04:32
*** akuznetsov has joined #openstack-meeting-alt04:33
*** jcooley_ has joined #openstack-meeting-alt04:33
*** fungi has quit IRC04:53
*** aignatov has joined #openstack-meeting-alt05:10
*** zane has quit IRC05:26
*** tanisdl has quit IRC05:30
*** zane has joined #openstack-meeting-alt05:30
*** akuznetsov has quit IRC05:34
*** wdennis has quit IRC05:34
*** akuznetsov has joined #openstack-meeting-alt05:35
*** wdennis has joined #openstack-meeting-alt05:40
*** sarob has joined #openstack-meeting-alt05:43
*** wdennis has quit IRC05:45
*** alazarev has quit IRC05:50
*** yogeshmehra has joined #openstack-meeting-alt05:56
*** alazarev has joined #openstack-meeting-alt05:57
*** markwash has joined #openstack-meeting-alt06:03
*** wdennis has joined #openstack-meeting-alt06:05
*** nati_ueno has joined #openstack-meeting-alt06:07
*** wdennis has quit IRC06:10
*** coolsvap has quit IRC06:10
*** EmilienM has quit IRC06:13
*** sdague has quit IRC06:13
*** kebray has quit IRC06:14
*** sdague has joined #openstack-meeting-alt06:18
*** EmilienM has joined #openstack-meeting-alt06:18
*** alazarev has quit IRC06:23
*** nati_uen_ has joined #openstack-meeting-alt06:28
*** yogeshmehra has quit IRC06:29
*** yogeshmehra has joined #openstack-meeting-alt06:30
*** nati_ueno has quit IRC06:31
*** sarob has quit IRC06:35
*** sarob has joined #openstack-meeting-alt06:35
*** sarob has quit IRC06:40
*** yogeshme_ has joined #openstack-meeting-alt06:41
*** yogeshmehra has quit IRC06:43
*** aignatov has quit IRC06:46
*** nati_ueno has joined #openstack-meeting-alt06:48
*** aignatov has joined #openstack-meeting-alt06:48
*** nati_uen_ has quit IRC06:49
*** fungi has joined #openstack-meeting-alt06:55
*** yogeshme_ has quit IRC06:57
*** nati_ueno has quit IRC06:57
*** nati_ueno has joined #openstack-meeting-alt06:58
*** aignatov has quit IRC07:02
*** nati_ueno has quit IRC07:03
*** nati_ueno has joined #openstack-meeting-alt07:04
*** wdennis has joined #openstack-meeting-alt07:06
*** aignatov has joined #openstack-meeting-alt07:06
*** nati_ueno has quit IRC07:09
*** nati_ueno has joined #openstack-meeting-alt07:10
*** wdennis has quit IRC07:10
*** sarob has joined #openstack-meeting-alt07:36
*** akuznetsov has quit IRC07:38
*** sarob has quit IRC07:40
*** aignatov has quit IRC07:49
*** zane has quit IRC07:51
*** nati_uen_ has joined #openstack-meeting-alt07:58
*** nati_uen_ has quit IRC07:58
*** nati_uen_ has joined #openstack-meeting-alt07:59
*** nati_ueno has quit IRC08:01
*** kebray has joined #openstack-meeting-alt08:03
*** wdennis has joined #openstack-meeting-alt08:06
*** jorisroovers has joined #openstack-meeting-alt08:10
*** wdennis has quit IRC08:11
*** jroovers has joined #openstack-meeting-alt08:12
*** jcooley_ has quit IRC08:14
*** jorisroovers has quit IRC08:15
*** tsufiev has quit IRC08:19
*** akuznetsov has joined #openstack-meeting-alt08:24
*** yamahata has quit IRC08:25
*** nati_uen_ has quit IRC08:36
*** sarob has joined #openstack-meeting-alt08:36
*** nati_uen_ has joined #openstack-meeting-alt08:37
*** nati_uen_ has quit IRC08:38
*** nati_uen_ has joined #openstack-meeting-alt08:38
*** gokrokve has quit IRC08:39
*** gokrokve has joined #openstack-meeting-alt08:39
*** sarob has quit IRC08:41
*** nati_uen_ has quit IRC08:43
*** gokrokve has quit IRC08:44
*** aignatov has joined #openstack-meeting-alt08:55
*** briancline has quit IRC08:56
*** EmilienM has quit IRC08:56
*** briancline has joined #openstack-meeting-alt08:56
*** EmilienM has joined #openstack-meeting-alt08:56
*** akuznetsov has quit IRC08:57
*** nosnos_ has joined #openstack-meeting-alt08:57
*** akuznetsov has joined #openstack-meeting-alt09:01
*** nosnos has quit IRC09:01
*** wdennis has joined #openstack-meeting-alt09:07
*** wdennis has quit IRC09:08
*** yogeshmehra has joined #openstack-meeting-alt09:09
*** jroovers has quit IRC09:10
*** derekh has joined #openstack-meeting-alt09:12
*** nati_ueno has joined #openstack-meeting-alt09:14
*** ben_duyujie has joined #openstack-meeting-alt09:18
*** yogeshme_ has joined #openstack-meeting-alt09:20
*** yogeshmehra has quit IRC09:22
*** plomakin has quit IRC09:36
*** nati_ueno has quit IRC09:36
*** plomakin has joined #openstack-meeting-alt09:37
*** sarob has joined #openstack-meeting-alt09:37
*** nati_ueno has joined #openstack-meeting-alt09:37
*** sarob has quit IRC09:41
*** nati_ueno has quit IRC09:42
*** jorisroovers has joined #openstack-meeting-alt09:49
*** jroovers has joined #openstack-meeting-alt09:51
*** jorisroovers has quit IRC09:53
*** coolsvap has joined #openstack-meeting-alt09:54
*** coolsvap has quit IRC09:58
*** pleia2 has quit IRC10:02
*** pleia2 has joined #openstack-meeting-alt10:03
*** yamahata has joined #openstack-meeting-alt10:10
*** wdennis has joined #openstack-meeting-alt10:10
*** gokrokve has joined #openstack-meeting-alt10:11
*** wdennis has quit IRC10:14
*** gokrokve has quit IRC10:16
*** ekarlso has quit IRC10:20
*** ekarlso has joined #openstack-meeting-alt10:21
*** yogeshme_ has quit IRC10:24
*** jroovers has quit IRC10:25
*** yogeshmehra has joined #openstack-meeting-alt10:26
*** jorisroovers has joined #openstack-meeting-alt10:27
*** yogeshmehra has quit IRC10:30
*** jorisroovers has quit IRC10:31
*** jorisroovers has joined #openstack-meeting-alt10:32
*** jorisroovers has quit IRC10:35
*** sarob has joined #openstack-meeting-alt10:37
*** aignatov has quit IRC10:38
*** yamahata has quit IRC10:42
*** sarob has quit IRC10:42
*** nati_ueno has joined #openstack-meeting-alt10:47
*** noslzzp has joined #openstack-meeting-alt10:50
*** nati_ueno has quit IRC10:52
*** nosnos_ has quit IRC11:08
*** nosnos has joined #openstack-meeting-alt11:09
*** wdennis has joined #openstack-meeting-alt11:11
*** gokrokve has joined #openstack-meeting-alt11:12
*** aignatov has joined #openstack-meeting-alt11:14
*** wdennis has quit IRC11:15
*** gokrokve has quit IRC11:16
*** sarob has joined #openstack-meeting-alt11:38
*** yamahata has joined #openstack-meeting-alt11:41
*** yamahata has quit IRC11:42
*** sarob has quit IRC11:42
*** yamahata has joined #openstack-meeting-alt11:43
*** pcm_ has joined #openstack-meeting-alt11:45
*** pcm_ has quit IRC11:48
*** pcm_ has joined #openstack-meeting-alt11:49
*** demorris has quit IRC11:52
*** nosnos_ has joined #openstack-meeting-alt12:07
*** nosnos has quit IRC12:10
*** nosnos_ has quit IRC12:11
*** wdennis has joined #openstack-meeting-alt12:11
*** gokrokve has joined #openstack-meeting-alt12:13
*** noslzzp has quit IRC12:14
*** wdennis has quit IRC12:16
*** gokrokve has quit IRC12:17
*** aignatov has quit IRC12:18
*** sarob has joined #openstack-meeting-alt12:38
*** sarob has quit IRC12:43
*** jorisroovers has joined #openstack-meeting-alt12:49
*** stanlagun has quit IRC13:03
*** pdmars has joined #openstack-meeting-alt13:03
*** aignatov has joined #openstack-meeting-alt13:07
*** wdennis has joined #openstack-meeting-alt13:12
*** gokrokve has joined #openstack-meeting-alt13:13
*** gokrokve_ has joined #openstack-meeting-alt13:15
*** wdennis has quit IRC13:16
*** gokrokve has quit IRC13:18
*** gokrokve_ has quit IRC13:20
*** flaper87|afk is now known as flaper8713:23
*** Barker has joined #openstack-meeting-alt13:26
*** mjbright__ has joined #openstack-meeting-alt13:33
*** alagalah has joined #openstack-meeting-alt13:48
*** betsy has joined #openstack-meeting-alt13:49
*** dprince has joined #openstack-meeting-alt14:01
*** dguitarbite has joined #openstack-meeting-alt14:02
*** sarob has joined #openstack-meeting-alt14:09
*** julim has joined #openstack-meeting-alt14:13
*** wdennis has joined #openstack-meeting-alt14:13
*** flaper87 is now known as flaper87|afk14:13
*** sarob has quit IRC14:13
*** gokrokve has joined #openstack-meeting-alt14:16
*** wdennis has quit IRC14:17
*** eankutse has joined #openstack-meeting-alt14:19
*** eankutse has quit IRC14:19
*** eankutse has joined #openstack-meeting-alt14:20
*** gokrokve has quit IRC14:20
*** wdennis has joined #openstack-meeting-alt14:22
*** yogeshmehra has joined #openstack-meeting-alt14:26
*** lblanchard has joined #openstack-meeting-alt14:27
*** ben_duyujie has quit IRC14:29
*** yogeshmehra has quit IRC14:32
*** demorris has joined #openstack-meeting-alt14:33
*** jroovers has joined #openstack-meeting-alt14:38
*** jorisroovers has quit IRC14:41
*** sarob has joined #openstack-meeting-alt15:00
sarob#startmeeting training-manuals15:01
openstackMeeting started Tue Nov 12 15:01:46 2013 UTC and is due to finish in 60 minutes.  The chair is sarob. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: training-manuals)"15:01
openstackThe meeting name has been set to 'training_manuals'15:01
sarobwho do we have this morning/evening?15:02
alagalahhey15:03
sarobmorning15:03
sarobi was up late with pranav chatting, so he is prob sleeping15:04
sarob#topic training guides restructuring15:04
*** openstack changes topic to "training guides restructuring (Meeting topic: training-manuals)"15:05
sarob#link https://docs.google.com/a/yahoo-inc.com/drawings/d/1ju78O-PjkZIeSbpGkUndIohQeQy06QXseRPbCy2F6F8/edit?usp=sharing15:05
alagalahNo access, I requested15:06
*** demorris has quit IRC15:06
*** Barker has quit IRC15:07
sarobaccess granted15:07
alagalahgot it15:08
sarobi whiteboarded the conversion of install guides and aptira content15:08
sarobalong with the actual training schedule15:09
alagalahLooks good15:09
sarobi realized we were trying to do too much with the associate guide15:09
alagalahThis gives some nice context around the actual objective of a class15:10
sarobyeah, i think this is on the right track15:10
alagalahHow does this change the structure? Does this mean cards need to be refactored to diffferent guides or is it a major re-write ?15:10
*** boris-42 has joined #openstack-meeting-alt15:11
sarobi think so15:11
alagalahWhich ?15:11
alagalahBoth ?15:11
alagalah:)15:11
sarobthe content is the same but needs to be across two guides15:11
sarobtwo days of training15:11
sarobplus quizes and test15:12
sarobmeans very focused material15:12
alagalahThat makes sense15:12
sarobwe had more like two weeks15:12
sarobto teach15:12
alagalahHmmm yeah the intro course needs to be short15:12
sarobonce i wrote out the schedule, it was a head slap15:13
*** Barker has joined #openstack-meeting-alt15:13
sarobbreaks, lunch, quizes, test15:13
saroball eat into two days15:13
*** rnirmal has joined #openstack-meeting-alt15:14
alagalahOk so what's next then?15:14
alagalahYou need validation of your whiteboard?>15:14
sarobyeah15:14
sarobpranav liked it15:14
alagalahIs there a reason we only use one compute node?15:14
sarobit turns out to be very close to what aptira has structured for their training this week15:15
sarobdo we need more than one?15:15
*** coolsvap has joined #openstack-meeting-alt15:16
*** gokrokve has joined #openstack-meeting-alt15:17
sarobalagalah if you can double check and tweak the gdraw15:17
sarobill feel like we can more forward15:17
sarobid really like to get colin's input too15:17
alagalahI shall15:18
sarobi was hoping he'd pop in, but vacation and all15:18
alagalahYeah totally understandable, nfi what the time diff is15:18
sarobvery selfish15:18
sarobits in the evening15:18
sarobhis time15:18
*** gokrokve_ has joined #openstack-meeting-alt15:19
sarobthats all i have15:19
alagalahWell, I guess the real question is what would we gain out of 2 compute nodes?15:19
alagalahlive migration ?15:19
alagalahOr is that out of scope?15:19
sarobim game if you think we them15:19
sarobwe need them15:20
alagalahWell... I'm just thinking about the sorts of things a VMWare admin might want to see in a course15:20
sarobsure that would be a reason15:20
sarobhmm, right15:20
alagalahI mean you can take the stand point of "I know nothing about virtualisation, openstack me" or "We have vmware but want to investigate this openstack stuff"15:20
sarobkeeping noodling on it15:20
sarobyeah, we need to service both15:21
alagalahI guess the real thing would be to just bang it out as is and then get a final version and market test it15:21
*** gokrokve has quit IRC15:21
sarobmember that the assoc guide is very intro15:21
alagalahOk that's a fair answer should it come up15:22
alagalahSo I guess that falls under "duly noted"15:22
sarobexperienced vmware eng could breeze through assoc, then focus on oper15:22
alagalahThere ya go!15:22
alagalahhold 115:22
alagalahDo we call out pre-reqs for the courses?15:22
sarobah, right you are15:23
sarobwant to add that to the gdraw?15:23
alagalahI shall15:24
alagalahBut I don't want to mess it up15:24
*** wdennis has quit IRC15:24
alagalahAny thoughts on changing this meeting to a ghangout so we can share information?15:24
sarobit needs to be at least irc15:25
sarobfor logging on easedrop15:25
sarobwe could add hangout too if you think it has value15:25
sarobshare information how?15:26
alagalahdiagrams, trello etc15:26
alagalahI know these things are "real time" and you can follow along if directed but it's easier to see people edit stuff in realtime if they are sharing their screen15:26
alagalahAnyway, just a thought.15:27
alagalahSo I'm working on adding pre-reqs15:27
alagalahSo far I have:15:27
alagalahpre-requisites:15:27
alagalah- working knowledge of Linux CLI15:27
alagalah- basic networking knowledge (Ethernets, VLAN, IP addressing)15:27
alagalah- mysql ?????15:28
alagalahThat's a stretch15:28
sarobyeah15:28
alagalahVirtualisation concepts ?15:28
alagalahCan you see my edits?15:29
sarobits off the page15:29
*** david-lyle has joined #openstack-meeting-alt15:30
alagalahI know that, I didn't want to mess up your formatting15:30
alagalahBut I wanted to capture it15:30
sarobno formatting here15:30
*** alazarev has joined #openstack-meeting-alt15:30
sarobdig in my son15:31
*** rudrajit has joined #openstack-meeting-alt15:31
alagalahOk what else should go in there?15:33
alagalahThe basic linux sysadmin is very subjective15:34
sarobyeah, i think ability to use vi, ssh,15:35
sarobprob the req15:35
alagalahsudo apt-get :)15:36
alagalahDo we need to call out what OS it is? Ubuntu I imagine is the leading candidate15:36
sarobi think we need to give them those15:36
alagalahSeems to have the highest distribution from the survey15:36
sarobthey will be running everything in virtualbox15:37
sarobso ubuntu is the os15:37
alagalahRight.15:37
saroblaptop that can run virtualbox15:37
*** markmcclain has joined #openstack-meeting-alt15:37
alagalahOr just say Virtual box?15:37
alagalahI changed it15:38
alagalahNormally I just tell people to bring their type2 hypervisor15:38
alagalahWhen doing labs and such but ... if we are doing virtual box that simplifies it, consistent15:38
sarobwe should have ubuntu on a stick15:38
sarobas well to minimize overloading the remotes15:39
alagalahOk that would be instructor resources required... right?15:39
*** tanisdl has joined #openstack-meeting-alt15:39
sarobhmm, sure15:39
alagalahHack away son, going AFK, saying good bye to daughter15:40
alagalahback in 515:40
sarobrighto15:40
*** noorul has joined #openstack-meeting-alt15:42
alagalahback15:45
alagalahSo we need a gdraw -> trello compiler15:45
sarobhmm, ill get right on that15:49
alagalahmade change to pre-req15:49
sarobi have a hard stop at 815:49
alagalahfor op guide15:49
alagalahSame here15:49
alagalahin fact I'm doing double duty15:49
alagalahOTP working on a report for a client :D15:49
sarobdouble pay, awesome15:50
sarobif you can double check the ideas, tweak at will15:51
*** uri1803_ has joined #openstack-meeting-alt15:52
sarobi also need to finalize which online service we use for quizzes and tests15:52
*** uri1803_ has quit IRC15:52
alagalahsurveymonkey is simplest I think15:52
*** uri1803 has joined #openstack-meeting-alt15:53
sarobfor quiz?15:53
alagalahyeah15:53
alagalahWhy not?15:53
sarobhmm, i didnt think of that15:54
alagalahYou could make it faux timed by making the test at the end of the class?15:54
alagalahLimit internet access to survey monkey? stop googlefu ? Don't know15:54
sarobwell lets bang it around15:55
alagalahAction item for discussion15:55
alagalahIt needs to be documented... you archiving this chat?15:55
sarobmoodle.org is another15:55
alagalahNever heard of it, I'll check it out15:55
*** jroovers has quit IRC15:55
alagalahOk, I have to split and jump on a call15:56
alagalahThis is great, btw, Sean15:56
saroblater15:56
sarob:)15:56
sarob#endmeeting15:56
*** alagalah has left #openstack-meeting-alt15:56
*** openstack changes topic to "Action items from the last meeting (Meeting topic: savanna)"15:56
openstackMeeting ended Tue Nov 12 15:56:49 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/training_manuals/2013/training_manuals.2013-11-12-15.01.html15:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/training_manuals/2013/training_manuals.2013-11-12-15.01.txt15:56
openstackLog:            http://eavesdrop.openstack.org/meetings/training_manuals/2013/training_manuals.2013-11-12-15.01.log.html15:56
*** sarob has quit IRC15:57
*** sarob has joined #openstack-meeting-alt15:57
*** adrian_otto has joined #openstack-meeting-alt15:59
*** jwforres has joined #openstack-meeting-alt15:59
*** aignatov has quit IRC15:59
adrian_otto#startmeeting Solum Team Meeting16:00
openstackMeeting started Tue Nov 12 16:00:12 2013 UTC and is due to finish in 60 minutes.  The chair is adrian_otto. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: Solum Team Meeting)"16:00
openstackThe meeting name has been set to 'solum_team_meeting'16:00
adrian_otto#topic Pre-Announcements16:00
adrian_otto1) Roll Call will not need your company affiliation in #openstack-meeting-alt as that is not customary here.16:00
adrian_ottoYou can simply respond with a hello of some sort. Responding at roll call is optional.16:00
*** openstack changes topic to "Pre-Announcements (Meeting topic: Solum Team Meeting)"16:00
adrian_otto#topic Roll Call16:00
*** openstack changes topic to "Roll Call (Meeting topic: Solum Team Meeting)"16:00
adrian_ottoGood morning!16:01
*** tomblank has joined #openstack-meeting-alt16:01
coolsvapHey, Swapnil Kulkarni(coolsvap) here16:01
gokrokve_Good morning! Georgy from Mirantis is here16:01
tomblankTom Blankenship, Rackspace16:01
*** paulczar has joined #openstack-meeting-alt16:01
uri1803Hi folks, Uri Cohen, GigaSpaces16:01
*** claytonc has joined #openstack-meeting-alt16:02
*** sarob has quit IRC16:02
*** solstice has joined #openstack-meeting-alt16:02
jwforreshi, Jessica Forrester16:02
*** muralia has joined #openstack-meeting-alt16:02
claytoncClayton Coleman16:02
*** solstice is now known as Guest5450316:02
*** briancline has quit IRC16:02
paulczarPaul Czarkowski, Rackspace16:02
muraliaMurali Allada, Rackspace16:02
*** alexheneveld has joined #openstack-meeting-alt16:03
alexheneveldalex heneveld, cloudsoft16:03
adrian_ottowould you all like to have an informal ODS retrospective during our open discussion today?16:04
*** sapuri has joined #openstack-meeting-alt16:04
claytonc}116:05
*** devkulkarni1 has joined #openstack-meeting-alt16:05
claytonc+116:05
muraliaYes.16:05
*** stanlagun has joined #openstack-meeting-alt16:05
*** danmcp_mtg has joined #openstack-meeting-alt16:05
uri1803+116:05
*** Subbu_ has joined #openstack-meeting-alt16:05
danmcp_mtgDan McPherson, Red Hat16:05
alexheneveld+116:05
sapuriSandeep Puri, Cisco16:05
gokrokve_+116:05
Subbu_Subbu Allamaraju, eBay16:05
adrian_ottookay, I will raise that for discussion right before open discussion16:05
devkulkarni1Devdatta Kulkarni, Rackspace16:05
*** rajdeep has joined #openstack-meeting-alt16:06
adrian_ottookay, let's proceed.16:06
adrian_ottoanyone else may chime in at any time.16:07
adrian_otto#topic Review action items from prior meeting16:07
adrian_ottoACTION: adrian_otto to create a breakout session index on the wiki (adrian_otto, 16:58:01)16:07
adrian_ottoStatus: completed: https://wiki.openstack.org/wiki/Solum/BreakoutMeetings16:07
*** openstack changes topic to "Review action items from prior meeting (Meeting topic: Solum Team Meeting)"16:07
*** funzo has joined #openstack-meeting-alt16:07
adrian_ottothat was the only action item16:07
adrian_otto#topic Announcements16:07
*** openstack changes topic to "Announcements (Meeting topic: Solum Team Meeting)"16:07
adrian_otto1) Mirantis is joining the Solum team. Please welcome them.16:07
funzowelcome!16:08
muraliaWelcome folks!16:08
adrian_ottowe have gokrokve_ here with us this morning16:08
rajdeepWelcome, even though i am also new!16:08
coolsvapHello!16:08
gokrokve_Thank you!16:08
adrian_ottorajdeep: welcome!16:08
gokrokve_We plan to have more folks from Mirantis here.16:08
*** kraman has joined #openstack-meeting-alt16:09
adrian_ottogreat!16:09
Subbu_adrian_otto: small typo on the wiki - it is referring to #solum channel16:09
Subbu_Was that intentional>16:10
Subbu_?16:10
adrian_ottooh, my16:10
adrian_ottowhich page is that appearing on?16:10
Subbu_https://wiki.openstack.org/wiki/Solum/BreakoutMeetings16:10
adrian_ottoactually, that's right, those will be in #solum16:10
*** tnurlygayanov has joined #openstack-meeting-alt16:10
noorulHello16:10
*** aratim has joined #openstack-meeting-alt16:10
tnurlygayanovHello )16:10
Subbu_k16:11
adrian_ottobecause the #openstack-meeting-alt channel is used for regularly scheduled meetings16:11
stanlagunhello :)16:11
adrian_ottoand I did not want to interfere with any others16:11
*** tanisdl has quit IRC16:11
adrian_ottoSubbu_: will taht be okay, do you think?16:11
*** tanisdl has joined #openstack-meeting-alt16:11
*** akuznetsova has joined #openstack-meeting-alt16:11
Subbu_makes sense. less conflicts16:11
adrian_ottookay, so here is our next announcement:16:12
adrian_otto2) Solum API Deep Dive schedules for this week:16:12
adrian_ottoPART I: Wednesday 2013-11-13 1:00 PM US/Pacific (2100 UTC)16:12
adrian_otto#link http://www.worldtimebuddy.com/?qm=1&lid=8,0,4726206&h=8&date=2013-11-13&sln=13-1416:12
adrian_ottoPART II: Friday 2013-11-15 1:00 PM US/Pacific (2100 UTC)16:12
adrian_otto#link http://www.worldtimebuddy.com/?qm=1&lid=8,0,4726206&h=8&date=2013-11-15&sln=13-1416:12
*** sergmelikyan has quit IRC16:12
rajdeeplooks very asia unfriendly time16:13
rajdeep:(16:13
adrian_ottoas discussed above, these will be in #solum and are intended for those who are interested in this topic to spend more focused time on it16:13
adrian_ottothe timeslot was selected from a croudsourced poll.16:13
funzoadrian_otto: is the plan for the deep dive to do part of it on IRC so folks can participate that aren't in the office?16:13
adrian_ottosorry for those of you on the other side of the globe.16:13
*** briancline has joined #openstack-meeting-alt16:13
rajdeepok np16:13
adrian_ottofungi: they are IRC meetings. What did you mean?16:14
funzoadrian_otto: didn't realize that16:14
stanlagunIt is midnight for most of Mirantis folks16:14
adrian_ottooh, yes, you can participate by IRC.16:14
adrian_ottostanlagun: sorry about that. We secured the timeslots before we knew you would be joining us.16:14
*** uri1803 has quit IRC16:15
adrian_ottowe used a tool called Doodle, which we will use again when we select future meeting times.16:15
adrian_ottoso if you see a link to Doodle anywhere in the ML, be sure to participate in that so we can accommodate your preferences.16:15
adrian_ottonext announcement...16:15
adrian_otto3) My deepest apologies for the confusion on the meeting time. My calendar emitted a rouge meeting invite.16:16
adrian_ottoPLEASE *delete* all appearances of "Solum Team Meeting" or "Solum Weekly Meeting" from you calendars. I will find a way to start fresh.16:16
*** akuznetsov has quit IRC16:16
adrian_ottothose of us in attendance already got the right time.16:16
adrian_ottoso my apologies to those of you reading this from transcripts.16:17
adrian_ottookay, next we will move into blueprints16:17
adrian_ottoI have a few that were carried over from a prior agenda:16:17
*** uri1803_ has joined #openstack-meeting-alt16:17
adrian_otto#link https://wiki.openstack.org/wiki/Meetings/Solum16:18
adrian_otto#topic Git Deploy Blueprint16:18
*** openstack changes topic to "Git Deploy Blueprint (Meeting topic: Solum Team Meeting)"16:18
adrian_otto#link https://blueprints.launchpad.net/solum/+spec/git-integration16:18
adrian_ottoPresent child blueprints and identify any ready for approval.16:18
adrian_otto(do we actually have anything new on this to discuss)16:18
adrian_otto?16:18
rajdeepone question : what if developer is not using git as a source control16:19
adrian_ottowe also have...16:19
adrian_ottorajdeep: good question16:19
adrian_ottothey will be able to bypass that16:19
adrian_ottothey will have a few options, including using the REST API directly16:19
adrian_ottousing a CLI tool16:19
adrian_ottousing an IDE plugin, or another UI16:20
nooruladrian_otto: Is this blueprint taken to mailing list?16:20
stanlagunhg? TFS?16:20
claytoncthere has also been discussion about pluggable source16:20
claytoncGit is the initial focus16:20
adrian_ottoyes, we can discuss this on ML.16:20
gokrokve_Will the git commit pass a gerrit review before?16:20
alexhenevelddid y'all get the chance to discuss this at all in HK?16:20
claytoncbut the desire would be to abstract that detail to a source provider16:20
adrian_ottogokrokve_: we have not discussed that yet, but we might use Gerrit in Solum16:21
gokrokve_Is it supposed that there will be some specific development process?16:21
adrian_ottoGerrit would host the git repo in that case16:21
funzoit would be a good idea to implement a gate, that could be jenkins or gerrit or whatever16:21
rajdeepi guess wrapper is a better approach and pluggin git, svn , TFS16:21
kramanalexheneveld not everyone was present in HK. A lot of the design discussion will also take place at F2F16:21
claytoncfunzo: that's a good point - there are probably two source flows: a) pushes to a repo, b) flows from a gate16:21
sapuriany review tool (like gerrit) probably should not have tight coupling - more likely an optional coupling16:21
alexheneveldk thx adrian_otto - as some of you know my 2p is that this will be easier if we split it into smaller parts16:22
funzoclaytonc: +116:22
claytoncsapuri: absolutely16:22
adrian_ottowe have not sorted out how best to support the gating use case16:22
alexheneveldcode repo and build on one side ... deploy and run on the other16:22
adrian_ottobut we will certainly allow a deployment artifact to bypass the build and go straight to deployment16:22
rajdeepsapuri +1, many enterprise developers find gerrit cumbersone16:22
adrian_ottoso if you want to run your own Jenkins, you can do that16:22
kramanif we keep the seperation clean and just have git invoke REST API when it is ready to push out code. might make it more flexible for other source controls as well16:23
adrian_ottowe have room for this on the Design Workshop agenda, so we can revisit it then too16:23
stanlagunWhat is gonna be in that git for short-term plans? Python projects? Or do you plan on building C++ apps etc?16:23
devkulkarni1kraman: +116:23
claytoncstanlagun: that is intended to be generic16:24
claytoncsee the language packs discussion in the wiki16:24
*** brents has joined #openstack-meeting-alt16:24
alexheneveldkraman: +116:24
sapurikraman: +116:24
coolsvapclaytonc: +116:24
*** akuznetsova has left #openstack-meeting-alt16:24
adrian_ottoI should have mentioned the Design Workshop in the announcements section, sorry. Here is the registration link if you plan to attend in person in San Francisco on Nov 19+20:16:25
adrian_otto#link https://www.eventbrite.com/event/913083156316:25
alexheneveldI will be with you all in spirit.16:26
adrian_ottowe will be in #solum too16:26
Subbu_thx for the link16:27
adrian_ottoand we are discussing how we might also use Google Hangout for some of it16:27
coolsvapadrian_otto : +1 :)16:27
adrian_ottomy understanding is that there are 3 meeting rooms so we can have concurrent meetings16:27
coolsvapfor #solum & hangout, I will be on lookout for its announcement16:27
alexheneveldgreat16:27
uri1803_+1 for hangout16:28
*** sarob has joined #openstack-meeting-alt16:28
stanlagun+1 for hangout too16:28
noorulI am trying to understand a use case for DU Count > 116:28
adrian_ottook, we have a few more blueprints to touch on16:28
claytoncnoorul: php and python parts of an app16:29
claytoncthat's one16:29
gokrokve_Regarding Jenkins, do you see it inside solum to make actual build or it should be outside?16:29
claytoncthere was a long ML discussion on that a while back16:29
adrian_otto#topic Shell Access Blueprint16:29
*** openstack changes topic to "Shell Access Blueprint (Meeting topic: Solum Team Meeting)"16:29
claytoncnoorul: about whether it was a good idea16:29
adrian_otto#link https://blueprints.launchpad.net/solum/+spec/shell-access-to-du16:29
claytoncso on ssh key distribution specifically, had a long discussion with adam young at design summit16:29
*** rudrajit has quit IRC16:30
claytoncone concrete point of statement from keystone was that they don't plan on being a key distribution / change management system (even though they might implement ceilometer notifications for credential added / removed)16:30
*** Subbu_ has quit IRC16:30
claytoncso an integrator wishing to implement ssh access and distribute keys would need to build something on top of keystone to do that16:30
adrian_ottoCloud Keep (barbican) may be a good fir for that16:30
*** Subbu_ has joined #openstack-meeting-alt16:30
coolsvapclaytonc : +116:30
adrian_ottos/fir/fit/16:30
*** RRaj has joined #openstack-meeting-alt16:31
claytoncadrian_otto: the one integration point that might complicate it is the many to many relationship of keys (user a has 10 keys, user b has 10 keys, they can overlap occassionally for machine system keys)16:31
claytoncwould be good to talk about barbican on ML or in a breakout related to this topic16:31
adrian_otto#link https://github.com/cloudkeep16:31
funzoadrian_otto: yeah, I heard folks talking about barbican being the key distribution of choice16:31
*** yamahata has quit IRC16:31
sapuriclaytonc: +1 - on many to many16:32
*** boris-42 has quit IRC16:32
adrian_ottoin a nutshell, it's a central place where you can store secrets16:32
stanlagunDo you plan to support Windows as well?16:32
*** Guest54503 has quit IRC16:32
kramanSame here. barbican was suggested as best way to distribute keys to applications as well. But that will depend on the container APIs to some extent16:32
funzostanlagun: as guests?16:32
stanlagunyep16:32
claytoncnoorul: maybe we should write up examples of multi DU on ML and try to counter example each one (about why it's a bad idea or not)16:33
alexheneveldssh seems like a special case of the need to expose a management interface for DU's in some cases16:33
funzostanlagun: in theory if using instances, that would be possible16:33
adrian_ottostanlagun: it's not explicitly mentioned as a goal, but language agnostic is. I see no reason why Windows could not be supported if there were a language pack for it.16:33
claytoncalexheneveld: good point - there are operations above and beyond ssh16:33
alexheneveld(and also for services) -- many will have a management dashboard for which barbican (or similar) would make sense for credential mgmt16:33
claytonchowever SSH typically has specific key authorization needs that you can avoid via other management points - i think the key aspect is what makes it special16:33
*** sarob has quit IRC16:34
Subbu_interesting discussion about windows - it further lowers the common denominator :)16:34
kramanalexheneveld: on openshift its used a lot during development and some during production to be able to log in and see what the processes are actually doing. cant run strace etc without shell access16:34
adrian_ottoso do we have a desire to break this BP up into more child BP's that we can assign as work items?16:34
stanlagunThis depends on overall architecture. Window might be very different. No SSH connectivity, np GNU toolstack etc16:34
*** sarob has joined #openstack-meeting-alt16:34
alexheneveld+1 claytonc - nice if user can supply a public key / credential where that is possible16:34
gokrokve_What about HTTPS\CLI option? It is mentioned in BP.16:34
funzostanlagun: definitely more complicated issues to think about re containers16:34
alexheneveldi'd like to make sure what we build doesn't rule windows out -- but do any of us want to endure that pain now :)16:35
* funzo slowly takes one baby step back.16:35
stanlagunWell you can never be sure until you try one16:36
adrian_ottomy guidance on this is to keep windows in mind, and focus initially on the language types that will run on *nix16:36
claytoncalexheneveld: stanlagun a good way to think about it is that we should allow the mechanism by which you deploy to be plugged enough so that you can pass the appropriate info to start a windows instance and configure it16:36
claytonc(via heat)16:36
claytoncwhat adrian said16:36
*** chipc has joined #openstack-meeting-alt16:36
funzo+116:37
*** jergerber has joined #openstack-meeting-alt16:37
stanlagunWindows is where all of your futures would be most interesting because there are not many solutions for that OS. If you can handle windows Linux wouldn't going to be a problem either16:37
adrian_ottoand we should consider windows compat as a key criteria when evaluating options for the design16:37
alexheneveldkraman: absolutely we must be able to set up ssh access for many DU's.  (though there could be some where it isn't ... e.g. if it's running in a multi-tenant JVM or OSGi framework...)16:37
*** sarob_ has joined #openstack-meeting-alt16:37
adrian_ottonot necessarily implementing both tracks.16:37
claytoncalexheneveld: kraman possibly DU's have a set of capabilities that are intrinsic to what they are (containers, multitenant jvm, windows)16:37
alexheneveldi'm just saying we want to be able to expose *other* types of management endpoints which will also require credential mgmt16:37
adrian_ottoalexheneveld: indeed16:38
*** sarob has quit IRC16:38
adrian_ottook, let's proceed to our next BP16:38
*** sarob_ has quit IRC16:38
adrian_otto#topic WSGI Framework Discussion16:38
adrian_ottoPecan+WSME vs. Falcon16:38
*** openstack changes topic to "WSGI Framework Discussion (Meeting topic: Solum Team Meeting)"16:38
tnurlygayanovhow user will connect to the different instances via ssh? only one session for one host?16:38
adrian_otto#link https://review.openstack.org/#q,topic:bp/rest-api-base,n,z16:38
*** ruhe has joined #openstack-meeting-alt16:38
kramanalexheneveld yes, ssh or just shell access seup should be optional and up to cloud provider16:38
*** sarob has joined #openstack-meeting-alt16:38
*** IlyaE has joined #openstack-meeting-alt16:39
kramantnurlygayanov: that needs to be worked out still16:39
alexheneveldyep - a bunch of different capabilities of various types of {DU's, lang packs, services, kumquats}16:39
*** sarob_ has joined #openstack-meeting-alt16:40
stanlagunthats why I mentioned Windows in the first place as there is no SSH there16:40
adrian_ottook, I offered this guidance last week: http://lists.openstack.org/pipermail/openstack-dev/2013-November/018430.html16:40
muraliaadrian_otto: Have we decided to go with Pecan+WSME? What were some of the discussions you had with others at the summit in this regard?16:40
rajdeepsupporting multiple OS will complicate things a lot16:41
adrian_ottoI am seeking input on Falcon, as I have suggested we proceed with Pecan+WSME16:41
*** markmcclain has quit IRC16:41
funzoadrian_otto: so are we just going with falcon if that's what's in the patch16:41
rajdeepnot sure how man paas can do that today16:41
funzoah16:41
adrian_ottolook at the review topic linked above16:41
adrian_ottowe have a patch for Falcon, and another for Pecan+WSME16:41
adrian_ottoat: https://review.openstack.org/#q,topic:bp/rest-api-base,n,z16:42
*** sarob_ has quit IRC16:42
funzoi see16:42
*** sarob_ has joined #openstack-meeting-alt16:42
*** sergmelikyan has joined #openstack-meeting-alt16:42
muraliaI'd like to hear more about the discussions that were had with the community around Falcon vs Pecan+wsme at the summit16:43
*** sarob has quit IRC16:43
sapuriadrian_otto: no opinion on either, i like your suggestion in the mailing list that, we should pick what other openstack projects are using, as a starting point16:43
kramanmuralia: most projects are switching or are planning to switch to Pecan+WSME16:44
adrian_ottoI discussed it at length with Kurt Griffiths,16:44
adrian_ottowho is a key contributor to Falcon16:44
claytoncthe documentation angle and the separation of API abstraction slightly from the underlying domain model abstraction were the factors that convinced me that pecan+wsme was the better choice for a general, control-plane API.16:45
*** sacharya has joined #openstack-meeting-alt16:45
adrian_ottoand a number of PTL's on OpenStack projects16:45
kramanclaytonc: +116:45
adrian_ottoJay Pipes has good criticisms of Webob and WSME16:45
stanlagunPecan (0.3.2)  7,111 req/sec Falcon (0.1.7) with Cython (0.19.1) - 52,858  req/sec according to off site16:46
adrian_ottoI also sourced input from Clayton, and others from RH16:46
adrian_ottostanlagun: I see that performance difference as acceptable, from the perspective of a large scale cloud operator.16:47
adrian_ottocontrol plane API's just don't see request rates that high16:47
alexheneveldeveryone seems in violent agreement, but for the order of magnitude difference wrt pecan16:47
*** sarob_ has quit IRC16:47
adrian_ottoand if they are, that means you have a service with a ton of usage, and can use horizontal scale out to address it16:47
claytoncas a practical example, in openshift we see control plane traffic that is roughly 1-2 req/sec per ten thousand active applications16:47
alexheneveldhowever +1 adrian_otto claytonc -- for the requests this will be handling raw throughput is less important than maintainability16:48
claytoncscale that up to ten million active active applications you're talking 1k req/s which is achievable using tens of python servers16:48
adrian_ottoclaytonc: we see similar use patterns in our existing systems that offer Web UI capability16:48
muraliaI personally find falcon to be easier to use and less bulky. But I do buy into the separation of domain and api models. Performance is not really the issue.16:48
alexheneveldthe higher throughput might be needed for the language pack, but falcon could still be used in language pack16:49
kramanadrian_otto: Webob used the be a problem but no longer an issue based on discussions during summit.16:49
*** rajdeep has quit IRC16:49
stanlagunagree. I also would like Pecan more. The only concern with performance here is it is good to have common approach for all projects and for some of them performance can be an issue16:50
adrian_ottoin the absence of any new key drawback, I wold like to mark a decision in the direction of Pecan+WSME, and revisit it as needed. If it turns out that we have a real performance concern at some point, we can evaluate a tear out of Pecan+WSME, or other optimization options.16:50
kramanalexheneveld: the language packs can use any api or language they wish. doesnt have to be the same as solum16:50
Subbu_As long as the control plane is stateless, and gets zero traffic from running hosts, we can handle. We had issues some OpenStack components like neutro which get traffic from data plane.16:50
alexheneveldkraman: +116:50
alexheneveldadrian_otto: +1 ... enough talk16:50
adrian_ottoany objections prior to advancing the topic?16:50
coolsvapadrian, kamran : +116:50
claytonc+116:51
tomblank+116:51
stanlagun+116:51
muralia+116:51
kraman+116:51
*** alazarev has quit IRC16:51
claytoncSubbu_: would recommend that data plane traffic into solum be a separate scalable component anyway16:51
RRaj+116:51
funzodoit16:51
adrian_otto#agreed we will use Pecan+WSME as the WSGI Framework for solum, to be revisited as-needed.16:51
claytoncthat's a good addendum to adrian's comment - pecan is for control plane traffic16:51
*** cbrawn has joined #openstack-meeting-alt16:51
adrian_ottoclaytonc: agreed 100%16:52
adrian_otto#topic ODS Retrospective16:52
*** openstack changes topic to "ODS Retrospective (Meeting topic: Solum Team Meeting)"16:52
adrian_ottoThe HKG summit was full of a lot of energy16:52
RRajMissed the summit - was there Solum discussion/session?16:53
adrian_ottoabout 99% of it toward Solum was positive. I expected more controversy. It seems that random bloggers have more criticisms than the core of the OpenStack community.16:53
*** ryanpetrello has joined #openstack-meeting-alt16:53
*** rajdeep has joined #openstack-meeting-alt16:53
adrian_ottooh, in summary of events:16:53
adrian_ottoI had a Lightning Talk on day 116:53
adrian_ottoUnconference sessions on Day 2 and 316:53
*** sacharya has quit IRC16:53
RRajNice16:54
adrian_ottoa Panel on Day 1 where Solum came up a bit16:54
*** sacharya has joined #openstack-meeting-alt16:54
adrian_ottoand an Panel on Day 416:54
claytoncthe best piece of criticism I heard was about whether Solum inside OpenStack drives people out of openstack or brings them in (relating this back to heat discussions that occurred previously).  My argument there was that we are growing the space of potential people who can be involved in openstack (language authors, development tool frameworks, CI/CD, containers) more than we are hurting16:54
kramanWe also had a design session on Container support on day 416:54
noorulhttp://www.forbes.com/sites/benkepes/2013/11/04/breaking-sorry-rackspace-et-al-ubuntu-to-offer-openstack-hosted-cloudfoundry-based-paas/16:54
adrian_ottoit was mentioned in the RedHat keynote16:54
noorulI saw that the other day16:54
adrian_ottoI see all the Cloud Foundry buzz as irrelevant16:55
alexheneveldi do not think the bloggers are "random" ... everyone has their agenda #ignore16:55
adrian_ottothe question really is about will Solum have the support it needs from community contributors to make it a valuable addition to the OpenStack ecosystem16:55
*** zane has joined #openstack-meeting-alt16:56
adrian_ottoand that's clearly a yes.16:56
adrian_ottothere was one question that Clint Byrum raised in the Friday panel16:56
Subbu_running code16:56
sapuriadrian_otto: +116:56
claytoncadrian_otto: that's what I was referring to above16:56
coolsvapadrian: I agree, have seen a lot of community interest in Solum in ODS16:56
adrian_ottoabout Heat being a disruptive force, and that Solum may also be disruptive16:56
rajdeepi had one question on messaging layer16:57
adrian_ottoupon reflection, I did think of a better response16:57
adrian_ottothat disruptive forces generally result in an overall improvement16:57
adrian_ottobut can cause short term setbacks16:57
adrian_ottothe long term gain is a certainty in my mind. Developers will become more productive using cloud technology when our vision is achieved.16:58
claytonci'd also make the point that up until now openstack has focused mostly on administration and resource allocation - but IT is larger than it.  I see openstack as helping IT organizations deliver value to their companies, and application lifecycle is a huge component of that16:58
adrian_ottoand that's a good thing.16:58
*** akuznetsov has joined #openstack-meeting-alt16:58
alexheneveldon that note adrian_otto open source is a huge disruptor ... typically decimates a market when there is an open source solution16:58
alexheneveldbut is ultimately a good thing (imho :) )16:58
adrian_ottoI need to hit on open discussion too16:58
adrian_ottoas we are running low on time16:58
adrian_otto#topic Open Discussion16:58
*** openstack changes topic to "Open Discussion (Meeting topic: Solum Team Meeting)"16:58
nooruladrian_otto: Is this still worked on http://lists.solum.io/pipermail/solum/2013-October/000130.html ?16:59
alexheneveldrajdeep: messaging?16:59
alexheneveld(or take to ML)16:59
rajdeepok i will ask there16:59
adrian_ottonoorul: I will need an update from Roshan on that one.16:59
adrian_ottoI think that task is still pending17:00
kramanIf anyone is interested in looking at what it will take to better integrate containers into Nova (or perhaps create a new service), please add your email to https://etherpad.openstack.org/p/docker-nova-hkg around line 7017:00
adrian_otto#endmeeting17:00
*** openstack changes topic to "Action items from the last meeting (Meeting topic: savanna)"17:00
openstackMeeting ended Tue Nov 12 17:00:17 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/solum_team_meeting/2013/solum_team_meeting.2013-11-12-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/solum_team_meeting/2013/solum_team_meeting.2013-11-12-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/solum_team_meeting/2013/solum_team_meeting.2013-11-12-16.00.log.html17:00
adrian_ottoplease continue in #solum17:00
*** uri1803_ has quit IRC17:00
*** Subbu_ has quit IRC17:00
*** jwforres has left #openstack-meeting-alt17:00
*** cbrawn has quit IRC17:01
*** rajdeep has quit IRC17:02
*** RoshanAgr has joined #openstack-meeting-alt17:02
*** claytonc_ has joined #openstack-meeting-alt17:02
*** sapuri has left #openstack-meeting-alt17:04
*** tnurlygayanov has quit IRC17:05
*** claytonc has quit IRC17:05
*** natishalom has joined #openstack-meeting-alt17:08
*** natishalom has quit IRC17:19
*** aratim has quit IRC17:21
*** RRaj has quit IRC17:22
*** radix has joined #openstack-meeting-alt17:23
*** derekh has quit IRC17:25
*** ruhe has quit IRC17:32
*** kevinconway has joined #openstack-meeting-alt17:32
*** aignatov has joined #openstack-meeting-alt17:34
*** aratim has joined #openstack-meeting-alt17:39
*** aratim has quit IRC17:41
*** alexheneveld has quit IRC17:43
*** muralia has left #openstack-meeting-alt17:51
*** betsy has quit IRC17:53
*** denis_makogon is now known as dmakogon17:55
*** adrian_otto has quit IRC18:01
*** alexheneveld has joined #openstack-meeting-alt18:02
*** noorul has left #openstack-meeting-alt18:04
*** aignatov has quit IRC18:04
*** markmcclain has joined #openstack-meeting-alt18:05
*** adrian_otto has joined #openstack-meeting-alt18:06
*** alexheneveld has quit IRC18:10
*** IlyaE has quit IRC18:10
*** aratim has joined #openstack-meeting-alt18:15
*** MarkAtwood has joined #openstack-meeting-alt18:17
*** RoshanAgr has quit IRC18:18
*** zane has quit IRC18:21
*** claytonc_ has quit IRC18:29
*** betsy has joined #openstack-meeting-alt18:36
*** jog0 has joined #openstack-meeting-alt18:36
*** sarob has joined #openstack-meeting-alt18:37
*** yogeshmehra has joined #openstack-meeting-alt18:37
*** yogeshmehra has quit IRC18:38
*** yogesh_ has joined #openstack-meeting-alt18:40
*** lsmola_ has joined #openstack-meeting-alt18:41
*** claytonc_ has joined #openstack-meeting-alt18:43
*** markmcclain has quit IRC18:44
*** markmcclain has joined #openstack-meeting-alt18:46
*** RoshanAgr has joined #openstack-meeting-alt18:46
*** rpodolyaka1 has joined #openstack-meeting-alt18:49
*** gokrokve_ has quit IRC18:52
*** gokrokve has joined #openstack-meeting-alt18:53
*** yogesh_ has quit IRC18:54
*** tomblank has quit IRC18:54
*** yogesh_ has joined #openstack-meeting-alt18:55
*** tzumainn has joined #openstack-meeting-alt18:55
*** markmcclain has quit IRC18:57
*** gokrokve has quit IRC18:57
*** marios has joined #openstack-meeting-alt18:58
*** yogesh_ has quit IRC18:59
*** zane has joined #openstack-meeting-alt18:59
lifeless#startmeeting tripleo19:00
openstackMeeting started Tue Nov 12 19:00:54 2013 UTC and is due to finish in 60 minutes.  The chair is lifeless. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: tripleo)"19:00
openstackThe meeting name has been set to 'tripleo'19:00
lifeless#topic agenda19:01
*** openstack changes topic to "agenda (Meeting topic: tripleo)"19:01
lifeless     bugs19:01
lifeless    reviews19:01
lifeless    Projects needing releases19:01
lifeless    CD Cloud status19:01
lifeless    CI virtualized testing progress19:01
lifeless    Insert one-off agenda items here19:01
lifeless    post HK wrapup19:01
lifeless    open discussion19:01
lifeless#topic bugs19:01
*** openstack changes topic to "bugs (Meeting topic: tripleo)"19:01
lifeless#link https://bugs.launchpad.net/tripleo/19:01
lifeless#link https://bugs.launchpad.net/diskimage-builder/19:01
lifeless#link https://bugs.launchpad.net/os-refresh-config19:01
lifeless#link https://bugs.launchpad.net/os-apply-config19:01
lifeless#link https://bugs.launchpad.net/os-collect-config19:01
lifeless#link https://bugs.launchpad.net/tuskar19:01
lifeless#link https://bugs.launchpad.net/tuskar-ui19:01
*** yogesh_ has joined #openstack-meeting-alt19:01
*** jprovazn has joined #openstack-meeting-alt19:01
lifeless#link https://bugs.launchpad.net/python-tuskarclient19:01
jprovaznhi19:01
lsmola_hello19:02
mariosevening all19:02
pleia2o/19:02
lifelessand -this is a first- we have no bugs that haven't been triaged; *and* we have no bugs that are critical open.19:02
lifelesscongrats everyone!19:02
*** RoshanAgr has quit IRC19:02
lsmola_yaay19:02
slaglenice19:02
lifeless#info -this is a first- we have no bugs that haven't been triaged; *and* we have no bugs that are critical open.19:03
lifelessAnyone have a pet bug they want to discuss ?19:03
*** RoshanAgr has joined #openstack-meeting-alt19:03
dprincewell, my dog has fleas19:04
lsmola_lol19:04
lifelessmoving right along :)19:04
lifeless#topic reviews19:04
*** openstack changes topic to "reviews (Meeting topic: tripleo)"19:04
lifelesshttp://russellbryant.net/openstack-stats/tripleo-openreviews.html19:04
lifeless#link http://russellbryant.net/openstack-stats/tripleo-openreviews.html19:04
lifeless3rd quartile wait time: 0 days, 6 hours, 35 minutes19:05
lifelessthats looking pretty hawt19:05
jog0wow19:05
lifelessespecially since we just had massive teamwide travel disruption etc19:05
lifeless#info reviews looking good - oldest review is < 7 hours19:06
lifelessAnyone have stuff around reviews they want to discuss?19:06
slagleyou proposed to add me to core. did i pass the vote? :)19:06
*** markwash has quit IRC19:07
*** claytonc_ is now known as claytonc19:07
SpamapSI think we had massive teamwide busy-not-submitting-patches too.. but it is good to see we didn't let either side disrupt the other ;)19:07
lifelessslagle: I don't know19:07
lifelessslagle: lets see19:07
lifelessslagle: noone disagreed, but we didn't get as many respondents as I would have liked.19:08
lifelessslagle: so will add you19:08
lifelessslagle: and urge folk to vote next month19:08
*** sarob has quit IRC19:08
lsmola_slagle, I have noticed only +119:08
*** sarob has joined #openstack-meeting-alt19:09
*** sarob has quit IRC19:09
*** tomblank has joined #openstack-meeting-alt19:09
lsmola_lifeless, I think I forgot to reply, so I give +1 to all :-)19:09
jomaraeasy, tiger19:09
lsmola_hehe19:10
lsmola_lifeless, seemed to me like there was 100% agreement anyway :-)19:10
lifelesslet me action that now19:11
lifeless#info slagle added to core19:12
*** coolsvap has quit IRC19:12
SpamapS\o/19:13
SpamapSmoar core19:13
lifeless#topic  Projects needing releases19:13
*** openstack changes topic to "Projects needing releases (Meeting topic: tripleo)"19:13
lifelessrpodolyaka1: around?19:13
rpodolyaka1lifeless: yep19:13
rpodolyaka1it seems that only tuskar and python-tuskarclient have bugs in 'Fix commited' state19:14
rpodolyaka1since the last release19:14
rpodolyaka1I could volunteer to make releases of those this week too :)19:14
lifelessrpodolyaka1: I think we should go off of git, not off the bug tracker.19:14
lifelessrpodolyaka1: as code can land without bugs existing19:14
rpodolyaka1make sense19:15
lifelessrpodolyaka1: and thanks!19:15
SpamapSI started working on a launchpad script to translate git -> LP bugs19:15
lifeless#info rpodolyaka1 to do another set of releases19:15
rpodolyaka1ack19:15
lifelessSpamapS: what does that mean?19:15
SpamapSbackburnered, but I can dig it out and get it up some where that everybody can use it.19:15
SpamapSlifeless: git knows whether or not a bug fix has landed in a release..19:16
lifelessI have a prototype thing to report which projects need releases and help determine what version they need19:16
rpodolyaka1btw, I made a wiki page to describe the release management process https://wiki.openstack.org/wiki/TripleO/ReleaseManagement19:16
lifelessrpodolyaka1: I saw - awesome19:16
lifeless#link https://wiki.openstack.org/wiki/TripleO/ReleaseManagement19:16
SpamapSlifeless: we can scan fix committed bugs, find the review that landed, and move them to fix released.19:16
lifelessSpamapS: won't that leave fix committed bugs w/o metadata open and stale?19:16
mariosrpodolyaka1: i can help too if you like - ah, was just about to say ï'll hassle you for info on how but you posted that wiki page19:17
SpamapSlifeless: yes.19:17
lifeless#topic  CD Cloud status19:18
*** openstack changes topic to "CD Cloud status (Meeting topic: tripleo)"19:18
lifelessIt's up. THen it's down. THen it's up.19:18
lifelessI think we need to forge ahead with state preservation, live upgrades and then circle back on reliablity19:18
lifelessbecause we'll end up blocking the CI effort otherwise.19:18
mariosrpodolyaka1: so anyway, let me know if you need help19:19
SpamapSagreed, also we can start ramping up instrumenting to help debug the reliability.19:19
rpodolyaka1marios: sure19:19
lifelessjog0: whats the status of the rebuild patches - they are now critical path in that we can't move ahead until they are done19:19
jog0lifeless: make sense, but what are the reprocussions on CI if we cannot deploy reliably19:19
* jog0 looks19:20
lifelessjog0: thats what the rolling deploy story is about, so we don't take down a live node etc19:20
lifelessjog0: CI won't start out gating, just silent queue, so we can iterate up19:20
jog0lifeless: oh right19:20
*** morazi has joined #openstack-meeting-alt19:20
jog0lifeless: patches are in review19:20
jog0both got comments today one -1 will look at that and work on the patch you handed me as well19:21
lifelessjog0: so - https://trello.com/b/0jIoMrdo/tripleo19:22
jog0https://review.openstack.org/#/c/51735/ https://review.openstack.org/#/c/52704/  https://review.openstack.org/#/c/54308/19:22
lifelessjog0: we need nova rebuild for baremetal, we need rebuild preserving ephemeral for baremetal and we need baremetal ephemeral support19:22
lifelessjog0: I believe only the latter one is in review19:22
lifelessjog0: this worries me as I think atm only you have picked up the cards for this set of work19:23
lifelessCan anyone else dive in and help with these changes?19:23
jog0ack, will get patches out this afternoon (after I file expense reports :/)19:23
lifelessyeah, tell me about that :)19:24
*** ryanpetrello has quit IRC19:24
* dprince filed his19:24
jog0dprince: did you just volunteer to help with the nova changes?19:25
dprincejog0: I can, certainly if we need it19:26
dprincejog0: but I was referring to filing my expense report :)19:26
dprincejog0: happy to help though w/ Nova too19:26
jog0dprince: being this is the MVP help is good19:27
lifelessSpamapS: can you ?19:27
rpodolyaka1I'm willing to help too :)19:27
lifelessrpodolyaka1: awesome19:28
lifelessok, so - the top two cards in the trello I linked, under 'current MVP' - they link to an etherpad with details19:29
SpamapSlifeless: yes I can, currently just playing with the other side (element changes to support /mnt/state)19:29
lifelessplease ask me/jog0 if you have any questions about whats needed in nova19:29
lifelessSpamapS: I suspect latency on the nova side is going to dominate19:29
rpodolyaka1lifeless: ack19:30
SpamapSlifeless: agreed19:30
*** dguitarbite has quit IRC19:30
jog0lifeless: yeah, although I can use up some of my karma on this once we have all the patches in place19:30
lifelessok19:30
lifeless#topic  CI virtualized testing progress19:31
*** openstack changes topic to "CI virtualized testing progress (Meeting topic: tripleo)"19:31
*** aratim has quit IRC19:31
lifelesspleia2: ^19:32
pleia2got to meet up with dprince and derekh at summit about this, so they're going to help out19:32
pleia2we all need to get on the same page with a lifeless chat though19:32
*** _ozstacker_ has joined #openstack-meeting-alt19:32
*** rossella_s has joined #openstack-meeting-alt19:33
*** rsblendido has joined #openstack-meeting-alt19:33
dprincepleia2: sure. The extra trello for tripleo-ci efforts is meant to help out here.19:33
*** ozstacker has quit IRC19:33
pleia2dprince: do you want to sync up with lifeless after meeting, or plan something when derekh can attend (maybe tomorrow?)19:35
dprincepleia2: lets sync up ASAP19:35
pleia2ok good19:35
lifelesspleia2: cool; is there anything we should touch on team wide about this?19:35
pleia2lifeless: I don't think so19:35
lifelessok19:35
lifeless#topic  post HK wrapup19:36
*** openstack changes topic to "post HK wrapup (Meeting topic: tripleo)"19:36
lifelessso I need to go through all the blueprints, set administrivia state etc19:36
lifelesscan everyone that submitted a session make sure you've captured action items in the etherpads: any pad with no action items I'm going to presume to be historical record and close the blueprint that pointed at it:)19:36
lifelessI'm not likely to get this done until next week or even the week after, so no need to panic - OTOH doing it while fresh helps prevent memory decay19:37
lifelessI thought our sessions were fairly effective, though one thing stood out to me19:38
slaglethere wasn't a bp open for the session i proposed. should i just open one in that case?19:38
lifelessWe're not communicating clearly that we embrace diversity - e.g. the ceph vs glusterfs discussion19:38
lifelessslagle: no, please don't :)19:38
slagleok19:38
lifelessIn my head we totally want both things to be installable.19:38
mordredlifeless: I'm only lurking here, butI'd agree with that19:39
lifelessAnd -if- there are sufficient resources we should gate on both setups working19:39
mordredI constantly have to communicate to people that tripleo is open19:39
lifelessIf there aren't sufficient resources, or if neither is working at all, then we have a triage problem vs an openness problem.19:39
lifelessSame for o*c/puppet/chef - we should totally support what users will want; we deliberately designed to be neutral on the enterprise-CM front by having a super light weight layer that noone can confuse for chef/puppet/salt/ansible etc etc etc19:41
lifelessmordred: thanks for the feedback19:41
lifelessDoes anyone disagree with what I'm saying? THis is an idea time to discuss...19:41
mordredone clarifying thing, just so that we don't get in a wad later19:42
mordredI agree with what you said19:42
mordredexcept19:42
mordredif you combine this sentence:19:42
mordredAnd -if- there are sufficient resources we should gate on both setups working19:42
mordredwith this one:19:43
mordredSame for o*c/puppet/chef - we should totally support what users will want19:43
mordredit might lead people to believe that if we had resources we might gate on puppet or chef19:43
mordredwhich is not the case19:43
lifelessisn't it?19:43
mordredno19:43
mordredcategorically not19:43
lifelesswhy not?19:43
mordredbcause those aren't about having enough resources19:43
mordredthey're about developer segmentation19:43
mordredwe want any openstack developer to have a reasonable expectation to be able to debug an issue that pops up in the gate19:44
lifelessSo thats not currently touched on in the stuff I wrote up for review in the infra docs19:44
mordredgating on chef or puppet or salt increases teh surface area to an unreasonable amount of material each developer would need to grok19:44
lifelessabout requirements to have things gated19:44
clarkblifeless: right thats the bits I was talking about needing more 'why'19:45
mordredI think it's a different thing19:45
lifelessI don't disagree with you, but thats a infra constraint, not a tripleo constraint19:45
mordredor a different aspect of the same19:45
mordredit's neither19:45
mordredit's a project constraint19:45
mordredwell, scuse me - said that wrong19:45
lifelesswe're about to rathole; but19:45
mordredit's not an infra constraint either- we can and do run puppet/chef19:45
mordredbut yes19:45
slaglewhat's the way forward on getting the work we did for the puppet based elements as "part of tripleo"?19:45
mordredjust wantedot clarify yourlanguage19:45
slagleshould we propose for stackforge or something?19:46
lifelessopenstack as a whole is very wide already - I doubt any single developer truely understands cinder + neutron + tempest + nova + all the clients + devstack + d-g + jenkins + nodepool sufficiently well to debug any arbitrary gate failure19:46
*** markwash has joined #openstack-meeting-alt19:46
ccrouchlifeless: +119:46
dprincelifeless: I do19:46
lifelessmordred: so what you're saying isn't actually making sense to me19:46
* dprince :)19:46
mordredd-g + jenkins + nodepool19:46
mordredare not required for the dev to understand19:46
mordredthey are not relevant19:46
mordredthey dev DOES need to understand and be able to reproduce devstack + clients + their code19:47
mordredadn they can do that right now19:47
lifelessmordred: d-g and jenkins are; nodepool you are right19:47
mordredno, they are not19:47
lifelessmordred: hang on, you just massively reduced the scope by saying 'their code', not 'all of openstack'19:47
mordredit is totally possible for a dev to reproduce a failure without jenkins19:47
mordredok19:47
mordredback to the beginning19:47
mordredbecause we're in the middle19:47
lifelessmordred: but you're assessing whether gating on e.g. chef would make sense for part of tripleo by 'any openstack developer', not by 'tripleo devs'19:47
lifelessthats inconsistent19:47
mordredok. we are talking about two different thigns19:48
mordredlet's finish talking about hte first one19:48
dprinceAs someone who has run quite a bit of puppet/chef upstream in the past I'm quite used to the idea of them being considered 3rd party.19:48
lifelessslagle: the puppet stuff needs to meet the technical aspects - decoupling the things it conflates - then its fine to come in19:48
dprinceHaving them upstream might be a good feedback loop however.19:48
mordredthe point of any of this is that a developer who uploads a change should have a reasonable expectation of being able to locally test the change as the gate tests it19:49
mordredso that if the gate fails their change19:49
lifelessSo it may be moot, as I'm confident we don't have test resources yet.19:49
mordredthey have a reasonable expectation that they can debug the problem19:49
mordredthat's a design tenant for the gate and always has been19:49
slaglelifeless: not sure i follow. you mean seperating the element that enables puppet support vs the ones that are puppet based?19:50
mordredlifeless: does that part make sense?19:50
lifelessslagle: supporting package based install vs supporting puppet for CM in the deployed image vs actual puppet details of CM19:50
lifelessmordred: sure19:51
slagleyea, ok, makes sense. i think we were going to try an split that stuff up19:51
mordredgreat. so that's the general integrated gate19:51
*** sarob has joined #openstack-meeting-alt19:51
mordrednow, as for having a tripleo specific gating test that gates on things all the way including running puppet in node ... honestly that's a new scenario that I don't think we've well defined yet19:52
mordredI would be opposed to gating nova on that19:52
mordredbut I think an argument could be made that a tripleo gate containing that could be in-game19:52
lifelessI think of the same way as things like postgresql - and yes I know we have headaches with that :)19:53
lifelesswhich is that where there is a pluggable layer with significant community interest, and we have resources [provided by said community], gating on it is beneficial to keeping it intact.19:53
dprincemordred: if we don't gate Nova on it too then it'll just end up broken, no?19:53
lifelessAnd it will have the same headaches if the level of interest is too low.19:53
mordreddprince: it's possible19:53
lifelessso I think we need to be very clear about the commitment needed to add extra backends to the gate19:54
mordreddprince: but I do not think that the puppet/chef rule changes just because we're doing tripleo and not devstack19:54
dprinceI see this whole space as 3rd party19:54
dprinceAnd very valuable all the same.19:54
lifelessok, I'm going to timebox this now19:54
mordredkk19:54
lifelesssince we have 6 minutes19:54
dprincePeople get all worked up about gates sometimes.19:54
mordredsorry for the diversion19:54
lifeless#topic open discussion19:54
*** openstack changes topic to "open discussion (Meeting topic: tripleo)"19:54
lifelessnow of course, if y'all want 6 minutes of gate discussion, go to town19:55
*** eankutse has quit IRC19:55
*** brents has quit IRC19:55
marioshas anyone given thought to the whole merge.py/tripleo-heat-templates long term?19:55
*** denis_makogon has joined #openstack-meeting-alt19:56
lifelessmarios: yes, that should be entirely HOT19:56
mariosi ask because we're trying to get tuskar using that (merge.py)19:56
*** markmcclain has joined #openstack-meeting-alt19:56
*** pblaho has joined #openstack-meeting-alt19:56
stevebakerthere needs to be some kind of client-side inclusion mechanism19:56
lifelessmarios: a small number of highly parameterisable templates, they should live in tripleo-heat-templates (as they should be directly usable) and tuskar shouldn't need to do any mangling of them at all.19:56
mariosso one thing... could we make merge.py have a'main' so i canimport and call, vs something fugly like subprocess19:56
*** jtomasek has joined #openstack-meeting-alt19:57
lifelessmarios: totally - just add it19:57
slaglethat came up in a design session.  the plan is to clearly identify why merge.py exists and how we use it, and submit as enhancements to Heat19:57
marioslifeless: ack, kinda working on that on my local branch but wanted to sanity check19:57
mariosthanks19:57
*** gokrokve has joined #openstack-meeting-alt19:58
mariosslagle: i'll ping you about that tomrorrow - would like to hear more19:58
lifelessin general, tuskar needs to lean /much/ more heavily on nova and neutron - we need to stop manually scheduling stuff and depend on nova/heat to get it right19:58
stevebakerIt might be that only individual resource properties need an inclusion mechanism19:58
*** zane has quit IRC19:58
lifelessI have on my todo to review where we are at and describe clearly whats in my head for getting long term reuse19:58
marioslifeless: yes... that whole business of the 'bash script in heat meatdata to create flavors' etc... (as one example) is one of the things we need to resolve this next sprint19:58
lifelessmarios: interestingly, I was chatting with mikal19:59
lifelessmarios: and he did not understand *at all* why flavor creation was at all interesting for tuskar.19:59
*** rudrarugge has joined #openstack-meeting-alt19:59
lifelessmarios: so - one thing I think we might want to do is validate that vs deployer needs.19:59
marioslifeless: yeah. i guess the hk demo wasn't demonstrating that since there was only one compute class created19:59
lifelessmarios: not even that20:00
lifelessmarios: I went through it with him on sunday20:00
lifelessmarios: and he just didn't get the value, even if you have multiple different hardware profiles like racksapce does.20:00
lifelessmarios: I am worried we're solving a problem that we only think deployers have.20:00
lifelessok, sorry to cut this short, but EOM.20:01
lifeless#endmeeting20:01
*** openstack changes topic to "Action items from the last meeting (Meeting topic: savanna)"20:01
openstackMeeting ended Tue Nov 12 20:01:03 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tripleo/2013/tripleo.2013-11-12-19.00.html20:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tripleo/2013/tripleo.2013-11-12-19.00.txt20:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tripleo/2013/tripleo.2013-11-12-19.00.log.html20:01
*** lpabon has joined #openstack-meeting-alt20:01
marioslifeless: ok, lets talk some more later/tomorrow20:01
lifelessmarios: ack20:01
*** pblaho has left #openstack-meeting-alt20:01
lsmola_thanks, bye20:02
*** alexheneveld has joined #openstack-meeting-alt20:02
*** yogesh_ has quit IRC20:03
*** wdennis has joined #openstack-meeting-alt20:03
*** tzumainn has left #openstack-meeting-alt20:03
*** julim has quit IRC20:03
*** yogesh_ has joined #openstack-meeting-alt20:03
*** sarob has quit IRC20:04
*** julim has joined #openstack-meeting-alt20:06
*** eankutse has joined #openstack-meeting-alt20:07
*** zane has joined #openstack-meeting-alt20:08
*** aratim has joined #openstack-meeting-alt20:08
*** yogesh_ has quit IRC20:08
*** relaxdiego has joined #openstack-meeting-alt20:17
*** paulczar has left #openstack-meeting-alt20:18
*** jprovazn has quit IRC20:19
*** wdennis has quit IRC20:19
*** ekarlso has quit IRC20:22
*** ekarlso has joined #openstack-meeting-alt20:22
*** brents has joined #openstack-meeting-alt20:23
*** rpodolyaka1 has quit IRC20:26
*** rsblendido has quit IRC20:31
*** rossella_s has quit IRC20:31
*** radix has left #openstack-meeting-alt20:37
*** radix has joined #openstack-meeting-alt20:37
*** wdennis has joined #openstack-meeting-alt20:40
*** eankutse has quit IRC20:42
*** eankutse has joined #openstack-meeting-alt20:42
*** derekh has joined #openstack-meeting-alt20:45
*** betsy has quit IRC20:46
*** sarob has joined #openstack-meeting-alt20:47
*** tdeckers has joined #openstack-meeting-alt20:47
*** yogesh_ has joined #openstack-meeting-alt20:51
*** tdeckers has quit IRC20:53
*** morazi has left #openstack-meeting-alt20:57
*** amytron has joined #openstack-meeting-alt21:00
*** yogesh_ has quit IRC21:04
*** yogesh_ has joined #openstack-meeting-alt21:04
*** relaxdiego has quit IRC21:07
*** RoshanAgr has quit IRC21:08
*** yogesh_ has quit IRC21:09
*** julim has quit IRC21:11
*** RoshanAgr has joined #openstack-meeting-alt21:14
*** Barker has quit IRC21:15
*** amytron has quit IRC21:16
*** amytron has joined #openstack-meeting-alt21:17
*** denis_makogon has quit IRC21:19
*** sarob has quit IRC21:19
*** sarob has joined #openstack-meeting-alt21:20
*** RoshanAgr has quit IRC21:20
*** dprince has quit IRC21:21
*** RoshanAgr has joined #openstack-meeting-alt21:21
*** vipul is now known as vipul-away21:24
*** sarob has quit IRC21:24
*** adrian_otto has quit IRC21:25
*** devlaps has joined #openstack-meeting-alt21:25
*** sarob has joined #openstack-meeting-alt21:26
*** kgriffs has joined #openstack-meeting-alt21:27
*** twoputt has joined #openstack-meeting-alt21:28
*** twoputt_ has joined #openstack-meeting-alt21:28
*** vipul-away is now known as vipul21:31
*** aratim1 has joined #openstack-meeting-alt21:32
*** yogesh_ has joined #openstack-meeting-alt21:33
*** aratim has quit IRC21:33
*** nati_ueno has joined #openstack-meeting-alt21:34
*** yogesh_ has quit IRC21:34
*** nikhil is now known as nikhil-bbiab21:35
*** yogesh_ has joined #openstack-meeting-alt21:37
*** IlyaE has joined #openstack-meeting-alt21:38
*** brents has quit IRC21:38
*** wdennis has quit IRC21:41
*** brents has joined #openstack-meeting-alt21:49
*** vipul is now known as vipul-away21:49
*** vipul-away is now known as vipul21:49
*** derekh has quit IRC21:51
*** pcm_ has quit IRC21:53
*** nikhil-bbiab is now known as nikhil21:54
*** nati_ueno has quit IRC21:55
*** nati_ueno has joined #openstack-meeting-alt21:55
*** noslzzp has joined #openstack-meeting-alt21:57
*** lpabon has quit IRC21:58
*** rudrarug_ has joined #openstack-meeting-alt21:59
*** rudrarugge has quit IRC22:00
*** nati_ueno has quit IRC22:00
*** rudrarug_ has quit IRC22:01
*** RoshanAgr has quit IRC22:02
*** twoputt_ has quit IRC22:04
*** twoputt has quit IRC22:04
*** IlyaE has quit IRC22:04
*** adrian_otto has joined #openstack-meeting-alt22:05
*** IlyaE has joined #openstack-meeting-alt22:07
*** lblanchard has quit IRC22:07
*** noslzzp has quit IRC22:10
*** pdmars has quit IRC22:10
*** jog0 has left #openstack-meeting-alt22:12
*** IlyaE has quit IRC22:13
*** nati_ueno has joined #openstack-meeting-alt22:13
*** wdennis has joined #openstack-meeting-alt22:15
*** 16WABHHRQ has joined #openstack-meeting-alt22:19
*** twoputt has joined #openstack-meeting-alt22:19
*** ErikB has joined #openstack-meeting-alt22:19
*** ErikB has left #openstack-meeting-alt22:20
*** zane has quit IRC22:20
*** nati_ueno has quit IRC22:24
*** nati_ueno has joined #openstack-meeting-alt22:24
*** danmcp_mtg is now known as danmcp22:25
*** tomblank has quit IRC22:29
*** tomblank has joined #openstack-meeting-alt22:29
*** nati_uen_ has joined #openstack-meeting-alt22:29
*** nati_ueno has quit IRC22:29
*** nati_uen_ has quit IRC22:33
*** nati_ueno has joined #openstack-meeting-alt22:34
*** julim has joined #openstack-meeting-alt22:36
*** zane has joined #openstack-meeting-alt22:37
*** nati_ueno has quit IRC22:38
*** eankutse has quit IRC22:40
*** wdennis has quit IRC22:45
*** lblanchard has joined #openstack-meeting-alt22:48
*** lsmola_ has quit IRC22:48
*** wdennis_ has joined #openstack-meeting-alt22:49
*** adrian_otto has left #openstack-meeting-alt22:51
*** tomblank has quit IRC22:52
*** danmcp has left #openstack-meeting-alt22:54
*** kgriffs is now known as kgriffs_afk22:55
*** sacharya has quit IRC22:57
*** yogesh_ has quit IRC22:58
*** kraman has quit IRC23:00
*** kraman has joined #openstack-meeting-alt23:00
*** rudrarugge has joined #openstack-meeting-alt23:03
*** kraman has quit IRC23:04
*** devlaps has quit IRC23:05
*** amytron has quit IRC23:06
*** aratim1 has quit IRC23:08
*** RoshanAgr has joined #openstack-meeting-alt23:08
*** jtomasek has quit IRC23:10
*** wdennis_ is now known as wdennis23:10
*** yogesh_ has joined #openstack-meeting-alt23:16
*** yogesh_ has quit IRC23:17
*** 16WABHHRQ has quit IRC23:21
*** twoputt has quit IRC23:21
*** twoputt has joined #openstack-meeting-alt23:22
*** twoputt_ has joined #openstack-meeting-alt23:22
*** betsy has joined #openstack-meeting-alt23:25
*** alexheneveld has quit IRC23:27
*** julim has quit IRC23:33
*** zane has quit IRC23:38
*** zane has joined #openstack-meeting-alt23:38
*** zane has quit IRC23:42
*** aratim has joined #openstack-meeting-alt23:45
*** wdennis has quit IRC23:47
*** tomblank has joined #openstack-meeting-alt23:52
*** ccrouch has quit IRC23:53
*** jergerber has quit IRC23:55

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