Tuesday, 2013-11-26

*** ashaikh has joined #openstack-meeting-alt00:00
*** julim has quit IRC00:04
*** MarkAtwood has quit IRC00:05
*** betsy has quit IRC00:14
*** nati_uen_ has joined #openstack-meeting-alt00:23
*** markwash has quit IRC00:25
*** nati_uen_ has quit IRC00:25
*** nati_uen_ has joined #openstack-meeting-alt00:26
*** nati_ueno has quit IRC00:27
*** vkmc has quit IRC00:28
*** devkulkarni has quit IRC00:37
*** yogesh has joined #openstack-meeting-alt00:44
*** flwang has joined #openstack-meeting-alt00:47
*** eankutse has joined #openstack-meeting-alt00:47
*** yamahata_ has joined #openstack-meeting-alt00:48
*** gokrokve has quit IRC00:51
*** tanisdl has quit IRC00:52
*** alazarev has quit IRC00:53
*** devkulkarni has joined #openstack-meeting-alt00:55
*** alazarev has joined #openstack-meeting-alt00:55
*** eankutse has quit IRC00:56
*** cathy_zhang has joined #openstack-meeting-alt00:56
*** cathy_zhang has quit IRC00:56
*** cathy_zhang has joined #openstack-meeting-alt00:57
*** cathy_zhang has quit IRC00:57
*** cathy_zhang has joined #openstack-meeting-alt00:58
*** cathy_zhang has quit IRC01:01
*** cathy_zhang has joined #openstack-meeting-alt01:03
*** cathy_zhang has quit IRC01:03
*** banix has joined #openstack-meeting-alt01:04
*** nosnos has joined #openstack-meeting-alt01:09
*** nati_ueno has joined #openstack-meeting-alt01:14
*** bcrochet has quit IRC01:15
*** ashaikh has quit IRC01:15
*** devkulkarni has quit IRC01:16
*** nati_uen_ has quit IRC01:17
*** jomara has quit IRC01:17
*** rongze has joined #openstack-meeting-alt01:21
*** bcrochet has joined #openstack-meeting-alt01:23
*** eankutse has joined #openstack-meeting-alt01:24
*** jomara has joined #openstack-meeting-alt01:25
*** rongze has quit IRC01:26
*** eankutse has quit IRC01:32
*** rongze has joined #openstack-meeting-alt01:39
*** eankutse has joined #openstack-meeting-alt01:39
*** colinmcnamara has quit IRC01:40
*** _ozstacker_ has joined #openstack-meeting-alt01:44
*** rongze has quit IRC01:46
*** yogesh has quit IRC01:47
*** ozstacker has quit IRC01:48
*** flwang has quit IRC01:48
*** amcrn has quit IRC01:52
*** rnirmal has quit IRC01:55
*** sarob has joined #openstack-meeting-alt01:56
*** rongze has joined #openstack-meeting-alt02:01
*** nosnos_ has joined #openstack-meeting-alt02:02
*** yamahata_ has quit IRC02:03
*** nati_uen_ has joined #openstack-meeting-alt02:03
*** yogesh has joined #openstack-meeting-alt02:04
*** eankutse has quit IRC02:04
*** nosnos has quit IRC02:05
*** nati_ueno has quit IRC02:06
*** coolsvap has quit IRC02:06
*** yogesh_ has joined #openstack-meeting-alt02:09
*** nati_uen_ has quit IRC02:09
*** nati_ueno has joined #openstack-meeting-alt02:10
*** yogesh has quit IRC02:11
*** eankutse has joined #openstack-meeting-alt02:12
*** yogesh_ has quit IRC02:16
*** yogesh has joined #openstack-meeting-alt02:16
*** gokrokve has joined #openstack-meeting-alt02:17
*** yogesh has quit IRC02:21
*** nati_ueno has quit IRC02:21
*** markwash has joined #openstack-meeting-alt02:32
*** amytron has quit IRC02:32
*** gokrokve has quit IRC02:37
*** gokrokve has joined #openstack-meeting-alt02:37
*** sarob has quit IRC02:40
*** sarob has joined #openstack-meeting-alt02:40
*** gokrokve has quit IRC02:42
*** alazarev has quit IRC02:42
*** sarob has quit IRC02:45
*** sarob has joined #openstack-meeting-alt02:45
*** flwang has joined #openstack-meeting-alt02:53
*** noslzzp has quit IRC03:00
*** sarob has quit IRC03:01
*** sarob has joined #openstack-meeting-alt03:02
*** noslzzp has joined #openstack-meeting-alt03:05
*** sarob has quit IRC03:07
*** colinmcnamara has joined #openstack-meeting-alt03:22
*** vkozhukalov has joined #openstack-meeting-alt03:26
*** nati_ueno has joined #openstack-meeting-alt03:28
*** eankutse has quit IRC03:29
*** nati_ueno has quit IRC03:35
*** nati_ueno has joined #openstack-meeting-alt03:35
*** sarob has joined #openstack-meeting-alt03:37
*** NikitaKonovalov has quit IRC03:41
*** banix has quit IRC03:41
*** twoputt_ has quit IRC03:46
*** twoputt has quit IRC03:46
*** coolsvap has joined #openstack-meeting-alt03:50
*** ashaikh has joined #openstack-meeting-alt04:12
*** yamahata_ has joined #openstack-meeting-alt04:14
*** vipul-away is now known as vipul04:29
*** nati_uen_ has joined #openstack-meeting-alt04:29
*** coolsvap has quit IRC04:31
*** nosnos_ has quit IRC04:32
*** nosnos has joined #openstack-meeting-alt04:32
*** nati_ueno has quit IRC04:33
*** aguzikova has joined #openstack-meeting-alt04:37
*** gokrokve has joined #openstack-meeting-alt04:46
*** yamahata_ has quit IRC04:47
*** rongze has quit IRC04:48
*** gokrokve has quit IRC04:50
*** banix has joined #openstack-meeting-alt04:55
*** yogesh has joined #openstack-meeting-alt04:59
*** sarob has quit IRC05:02
*** yogesh has quit IRC05:04
*** coolsvap_ has joined #openstack-meeting-alt05:05
*** rongze has joined #openstack-meeting-alt05:19
*** coolsvap_ has quit IRC05:24
*** rongze has quit IRC05:27
*** sarob has joined #openstack-meeting-alt05:28
*** coolsvap has joined #openstack-meeting-alt05:29
*** sarob has quit IRC05:39
*** nadya has joined #openstack-meeting-alt05:45
*** nadya is now known as Guest5510505:45
*** mozawa has joined #openstack-meeting-alt05:50
*** Guest55105 has quit IRC05:56
*** radix_ has joined #openstack-meeting-alt05:59
*** alazarev has joined #openstack-meeting-alt05:59
*** yogesh has joined #openstack-meeting-alt06:03
*** banix has quit IRC06:04
*** sarob has joined #openstack-meeting-alt06:07
*** yogesh_ has joined #openstack-meeting-alt06:08
*** yogesh has quit IRC06:10
*** vkozhukalov has quit IRC06:15
*** denis_makogon has joined #openstack-meeting-alt06:23
*** rongze has joined #openstack-meeting-alt06:24
*** yogesh_ has quit IRC06:25
*** yogesh has joined #openstack-meeting-alt06:26
*** coolsvap has quit IRC06:26
*** rongze has quit IRC06:28
*** noslzzp has quit IRC06:28
*** boris-42 has joined #openstack-meeting-alt06:29
*** yogesh has quit IRC06:31
*** coolsvap has joined #openstack-meeting-alt06:33
*** coolsvap has quit IRC06:36
*** rongze has joined #openstack-meeting-alt06:38
*** yogesh has joined #openstack-meeting-alt06:42
*** akuznetsov has quit IRC06:45
*** colinmcnamara has quit IRC06:49
*** ashaikh has quit IRC06:51
*** sergmelikyan has quit IRC06:52
*** sarob has quit IRC06:54
*** yogesh has quit IRC06:54
*** yogesh has joined #openstack-meeting-alt06:54
*** nati_uen_ has quit IRC06:56
*** yogesh has quit IRC06:59
*** yogesh has joined #openstack-meeting-alt07:07
*** alazarev has quit IRC07:08
*** NikitaKonovalov has joined #openstack-meeting-alt07:10
*** nati_ueno has joined #openstack-meeting-alt07:12
*** mozawa has quit IRC07:12
*** mozawa has joined #openstack-meeting-alt07:12
*** NikitaKonovalov_ has joined #openstack-meeting-alt07:14
*** NikitaKonovalov has quit IRC07:15
*** NikitaKonovalov_ is now known as NikitaKonovalov07:15
*** ikhudoshyn has joined #openstack-meeting-alt07:29
*** SergeyLukjanov has joined #openstack-meeting-alt07:38
*** jtomasek has quit IRC07:38
*** jtomasek has joined #openstack-meeting-alt07:38
*** boris-42 has quit IRC07:42
*** jtomasek has quit IRC07:45
*** boris-42 has joined #openstack-meeting-alt07:45
*** katyafervent has quit IRC07:46
*** tsufiev has quit IRC07:46
*** tsufiev has joined #openstack-meeting-alt07:46
*** katyafervent has joined #openstack-meeting-alt07:47
*** jtomasek has joined #openstack-meeting-alt07:49
*** yogesh has quit IRC07:58
*** yogesh has joined #openstack-meeting-alt07:59
*** akuznetsov has joined #openstack-meeting-alt08:04
*** SergeyLukjanov has quit IRC08:06
*** jcoufal has joined #openstack-meeting-alt08:07
*** flaper87|afk is now known as flaper8708:10
*** yogesh has quit IRC08:16
*** yogesh_ has joined #openstack-meeting-alt08:19
*** sarob has joined #openstack-meeting-alt08:20
*** yogesh has joined #openstack-meeting-alt08:22
*** vkozhukalov has joined #openstack-meeting-alt08:23
*** yogesh_ has quit IRC08:24
*** sarob has quit IRC08:24
*** yogesh_ has joined #openstack-meeting-alt08:26
*** yogesh has quit IRC08:29
*** nati_ueno has quit IRC08:29
*** vkozhukalov has quit IRC08:34
*** NikitaKonovalov has quit IRC08:39
*** denis_makogon has quit IRC08:39
*** vkozhukalov has joined #openstack-meeting-alt08:41
*** yogesh has joined #openstack-meeting-alt08:45
*** yogesh_ has quit IRC08:49
*** sarob has joined #openstack-meeting-alt08:50
*** sarob has quit IRC08:52
*** sarob has joined #openstack-meeting-alt08:52
*** derekh has joined #openstack-meeting-alt08:54
*** sarob has quit IRC08:57
*** _coolsvap_ has joined #openstack-meeting-alt09:06
*** yogesh has quit IRC09:09
*** nati_ueno has joined #openstack-meeting-alt09:09
*** mozawa has quit IRC09:12
*** flwang has quit IRC09:12
*** yogesh_ has joined #openstack-meeting-alt09:14
*** yogesh_ has quit IRC09:17
*** yogesh has joined #openstack-meeting-alt09:18
*** aguzikova_ has joined #openstack-meeting-alt09:20
*** yogesh_ has joined #openstack-meeting-alt09:22
*** aguzikova has quit IRC09:23
*** yogesh has quit IRC09:23
*** NikitaKonovalov has joined #openstack-meeting-alt09:24
*** ruhe has joined #openstack-meeting-alt09:25
*** yamahata_ has joined #openstack-meeting-alt09:30
*** _coolsvap_ has quit IRC09:37
*** coolsvap has joined #openstack-meeting-alt09:37
*** nati_ueno has quit IRC09:40
*** sarob has joined #openstack-meeting-alt09:50
*** coolsvap has quit IRC10:00
*** SergeyLukjanov has joined #openstack-meeting-alt10:02
*** coolsvap has joined #openstack-meeting-alt10:06
*** yogesh_ has quit IRC10:06
*** yogesh has joined #openstack-meeting-alt10:07
*** aguzikova_ has quit IRC10:08
*** yogesh has quit IRC10:11
*** jcoufal has quit IRC10:13
*** away-gone is now known as denis_makogon10:17
*** sarob has quit IRC10:22
*** rongze has quit IRC10:29
*** coolsvap has quit IRC10:32
*** yamahata_ has quit IRC10:36
*** coolsvap has joined #openstack-meeting-alt10:38
*** coolsvap has quit IRC10:44
*** colinmcnamara has joined #openstack-meeting-alt10:50
*** sarob has joined #openstack-meeting-alt10:50
*** ityaptin has quit IRC10:54
*** sarob has quit IRC10:54
*** colinmcnamara has quit IRC10:55
*** rossella_s has joined #openstack-meeting-alt11:03
*** rsblendido has joined #openstack-meeting-alt11:03
*** ruhe has quit IRC11:07
*** coolsvap has joined #openstack-meeting-alt11:35
*** pcm_ has joined #openstack-meeting-alt11:41
*** sarob has joined #openstack-meeting-alt11:50
*** jcoufal has joined #openstack-meeting-alt11:53
*** pcm_ has quit IRC11:55
*** pcm_ has joined #openstack-meeting-alt11:56
*** flaper87 is now known as flaper87|afk12:11
*** nosnos has quit IRC12:11
*** sarob has quit IRC12:12
*** rongze has joined #openstack-meeting-alt12:15
*** flaper87|afk is now known as flaper8712:16
*** mozawa has joined #openstack-meeting-alt12:25
*** mozawa_ has joined #openstack-meeting-alt12:28
*** mozawa has quit IRC12:30
*** mozawa_ is now known as mozawa12:30
*** sarob has joined #openstack-meeting-alt12:32
*** vkmc has joined #openstack-meeting-alt12:32
*** mozawa has quit IRC12:36
*** sarob has quit IRC12:37
*** mozawa has joined #openstack-meeting-alt12:39
*** boris-42 has quit IRC12:41
*** yamahata_ has joined #openstack-meeting-alt12:47
*** flwang has joined #openstack-meeting-alt12:49
*** sarob has joined #openstack-meeting-alt12:50
*** mozawa has quit IRC12:52
*** sarob has quit IRC12:54
*** markmcclain has joined #openstack-meeting-alt12:56
*** pdmars has joined #openstack-meeting-alt12:59
*** ityaptin has joined #openstack-meeting-alt13:06
*** coolsvap has left #openstack-meeting-alt13:15
*** dhellmann-afk is now known as dhellmann13:15
*** coolsvap has joined #openstack-meeting-alt13:17
*** coolsvap has left #openstack-meeting-alt13:17
*** rongze has quit IRC13:17
*** rongze has joined #openstack-meeting-alt13:29
*** dhellmann is now known as dhellmann-afk13:31
*** amotoki has joined #openstack-meeting-alt13:37
*** alagalah has joined #openstack-meeting-alt13:45
*** sarob has joined #openstack-meeting-alt13:50
*** markmcclain has quit IRC13:50
*** dprince has joined #openstack-meeting-alt13:51
*** dguitarbite has joined #openstack-meeting-alt13:52
*** sarob has quit IRC13:54
*** sarob has joined #openstack-meeting-alt13:56
*** ruhe has joined #openstack-meeting-alt13:58
*** colinmcnamara has joined #openstack-meeting-alt13:59
colinmcnamaraHello14:00
sarob#startmeeting training-manuals14:00
openstackMeeting started Tue Nov 26 14:00:35 2013 UTC and is due to finish in 60 minutes.  The chair is sarob. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: training-manuals)"14:00
openstackThe meeting name has been set to 'training_manuals'14:00
sarobMorning14:00
colinmcnamaraMorning14:00
colinmcnamaraWaaaaaaay early morning14:01
sarobWho else we got ?14:01
alagalahhi14:01
dguitarbitehello14:01
sarobSweet14:01
dguitarbiteMorning14:01
sarobMorning14:02
colinmcnamaraHi prahnav14:02
dguitarbiteHi colin sean14:02
sarobSoooo, topics?14:02
colinmcnamaraYeah14:02
colinmcnamaraCards /.tasks14:03
*** NikitaKonovalov has quit IRC14:03
sarobYup anyone else?14:03
colinmcnamaraSo I'm back in USA. Log on to burn some cards14:03
colinmcnamaraNot exactly sure what tasks are next14:03
alagalahWell I did say hi14:03
colinmcnamaraIn trello14:03
alagalah???14:03
colinmcnamaraMorning Keith14:04
*** tdeckers has joined #openstack-meeting-alt14:04
alagalahMorning14:04
sarobHmm uessss14:04
sarobHey there14:04
alagalahI only see one Doing card, is that right?14:05
sarobI've got conversion, restructure, assoc and oper rough draft dates14:05
dguitarbiteyes14:05
colinmcnamaraBut specific task14:06
colinmcnamaraEg redesign diagram card14:06
*** flwang has quit IRC14:06
colinmcnamaraSpecific card would be. Redesign diagra. 1.1 I gdraw14:06
colinmcnamaraEtc14:06
sarob#topic cards status14:07
*** openstack changes topic to "cards status (Meeting topic: training-manuals)"14:07
alagalahCard#145?14:07
colinmcnamaraSpecific, measurable. Actionable14:07
*** flwang has joined #openstack-meeting-alt14:07
colinmcnamaraAre the specific tasks still in the gdoc?14:08
dguitarbiteI think so14:08
dguitarbiteI dont see a specific card deck here14:08
colinmcnamaraK, so it sounds like an action item that is open after the restructure is to build the open tasks out of the gdoc into trello so we ca. Track14:09
colinmcnamaraSarob is that accurate?14:10
colinmcnamaraIf So I can sign up to do that14:10
sarobYeah, the gdraw was a good restart14:10
sarobBut we have moved way past it being useful14:10
colinmcnamaraIs the gdoc up to date?14:11
sarobThe diagram you speak of?14:11
alagalahDoes gdoc == gdraw ?14:11
colinmcnamaraI was just using that as an example14:11
dguitarbiteyes14:11
*** dhellmann-afk is now known as dhellmann14:11
dguitarbitegdoc == gdraw14:11
dguitarbitegot the link?14:12
alagalahack, sarob shared14:12
*** julim has joined #openstack-meeting-alt14:12
colinmcnamaraI logged on last night to burn some cards.  And could not identify easily specific taks14:12
sarobHold on14:12
*** eankutse has joined #openstack-meeting-alt14:12
*** ccrouch has left #openstack-meeting-alt14:13
colinmcnamara#action colinmcnamara to build trello tasks out of current gdoc14:13
colinmcnamaraDoh  meetbot command ?14:13
*** eankutse has quit IRC14:14
*** eankutse has joined #openstack-meeting-alt14:14
*** isviridov is now known as help14:15
*** help is now known as isviridov14:15
colinmcnamaraI just put that as a task into trello and assigned it to myself14:16
sarob#action colinmcnamara to build trello tasks out of current gdoc14:16
sarobYup14:16
colinmcnamaraIf someone can post the link in the meeting notes14:17
colinmcnamaraOr put it on a card in the trello board14:17
sarobBut member the diagram was a rough start14:17
sarobI'll post the link14:17
colinmcnamaraDiagram was just an example14:18
sarobRight the real detail steps need to be in trello14:18
colinmcnamaraYup.14:19
colinmcnamaraThat also allows us to measure / estimate progress14:19
sarobReady to move on?14:19
*** isviridov has left #openstack-meeting-alt14:19
sarob#topic rough draft due dates14:20
*** openstack changes topic to "rough draft due dates (Meeting topic: training-manuals)"14:20
colinmcnamaraYou14:20
colinmcnamaraYup14:20
sarobI'd like to publish the associate guide to Havana by Friday14:20
sarobWithout quizzes14:21
sarobHow do you guys feel about that?14:21
colinmcnamaraJust for a sanity check, since the is not visibility of remaining tasks in trello14:21
sarobEhh?14:22
colinmcnamaraHow much is outstanding right now? (Again, only 24 hours back in my office)14:22
sarobThe queens English if you please sir14:22
colinmcnamaraI can't comment on publishing by Friday without w work estimation14:22
*** coolsvap has joined #openstack-meeting-alt14:22
sarobCards?14:22
colinmcnamaraYeah how many hours of work left14:22
sarobAhh okay14:23
sarobWell I see about 8-9 cards referencing assoc guide14:23
colinmcnamaraIn the gdoc?14:23
alagalahWhere?14:24
sarobBut that's diff that ready enuf to publish to Havana14:24
sarobCards on trello14:24
alagalahsarob: 8-9 cards but across what states ?14:24
sarobIn the sprint backlog14:25
alagalahah14:25
colinmcnamaraOk, have we groomed that?14:25
colinmcnamaraEg virtual box for windows.14:25
colinmcnamaraIs that outstanding. Pushed. Done?14:25
alagalahI see 7 cards in the Sprint directly related to Quizzing... .so if you filter those out...14:26
colinmcnamaraI assume that there are more tasks in the gdoc14:26
dguitarbitevirtual box in windows is outstanding14:26
colinmcnamaraAnd we basically have one workday left this eek14:27
colinmcnamaraWeek14:27
colinmcnamaraWith the holidays14:27
colinmcnamaraIn. Short, I don't have enough info to say whether we can publish by Friday14:27
sarobStuff outstanding right but is enough done for the associate guide to be published14:27
colinmcnamaraK14:28
alagalahFirstly, is the gdraw definitive of the course structure?14:28
alagalahie is it finished?14:28
sarobI think so14:28
alagalahOk, comments:14:28
alagalahI see references to bk002-Chxxxx and I see references to cardyyy14:29
*** sarob_ has joined #openstack-meeting-alt14:29
alagalahMy assumption is then that anything cardyyy has not been contributed up to the project... is that fair? If so then the immediate task would be to convert cardxxx in gdraw to bkyy-chzzz and merge, right?14:29
alagalahThen publish ?14:29
*** noorul has joined #openstack-meeting-alt14:29
*** sarob__ has joined #openstack-meeting-alt14:30
sarob__#link https://docs.google.com/a/yahoo-inc.com/drawings/d/1ju78O-PjkZIeSbpGkUndIohQeQy06QXseRPbCy2F6F8/edit14:30
alagalahAck that is the link I am looking at, assume you are putting it in here for the log14:30
colinmcnamaraWeird. That just asked me for a yahoo corp login14:31
sarobYeah hold on14:31
sarobPranav, Colin, Peter, Keith all have access14:32
sarobRick too14:33
colinmcnamaraCool. I'm on my ipad on limechat. I'll log I14:33
*** sarob_ has quit IRC14:33
colinmcnamaraOn with Mac and check14:33
alagalahYes I didn't have an issue since the original share, still linked in my gdocs account14:33
colinmcnamaraIt's waaay early. In in bed for this meeting14:33
colinmcnamaraK14:33
sarobI added a bit to the diagram14:34
alagalahha, I got up early to help Florian but he has work work14:34
alagalahsarob: Since last I looked, thats an understatement14:34
alagalahsarob: So is my assumption correct, cardxxx on diagram needs content merged?14:34
sarobNot neccessarly14:35
alagalahRight14:35
alagalahCard039 as a prime example14:35
sarobDiagram is a mess of notes and ideas14:35
alagalahIT's awesome but....14:35
alagalahIf you want to use it as a quasi "What do we have todo" to make trello cards and punch out docs by Fri...14:36
alagalahI'm just finding a way of easily seeing what needs to be done14:36
colinmcnamara+114:36
sarobI think we need to start reading the guide to verify if it is readable14:37
colinmcnamaraBtw, I normally don14:37
colinmcnamaraDon't put deadlines right after holidays14:37
alagalahSo should an action be to mark the gdraw in some way, either by "card" in the title needing a card, and bkxx being done, and then burn down cards and punch out a doc for readability ?14:37
colinmcnamaraThey normally slip14:37
colinmcnamaraSounds fair14:38
sarobLet's take a step back for a sec14:38
sarobDoes everyone think the new structure is goodness?14:39
sarobAs on master right now14:39
colinmcnamaraBreaking the operational tasks out first?14:40
colinmcnamaraIs that what you are referencing?14:40
sarobThe structure I speak of14:40
sarobchapter to sections14:41
sarobAs published14:41
colinmcnamara?14:42
sarobFrom the diagram14:42
colinmcnamaraI need to head down stairs and hop on my laptop. I'm on my ipad in bed14:42
colinmcnamaraTo reference the diagram14:42
sarobI think everyone needs to take a quick look at the associate and operator guides online14:43
*** banix has joined #openstack-meeting-alt14:43
sarobI was busy this last few weeks14:43
sarobI created the chapter to section structure from the diagram14:44
alagalahSarob: see unicast window, issue building since I re-imaged machine14:44
sarobEhh?14:45
*** colinmcn_ has joined #openstack-meeting-alt14:46
colinmcn_logged on via laptop now14:46
sarobI'm going to need coffee you get all techy14:46
alagalahsarbo: nvm I'll work it out14:46
colinmcn_so, associate guide structure14:46
colinmcn_(sorry about the nic change, logged on via laptop)14:46
sarobRight14:46
colinmcn_so in short, associate and operator got split out14:47
colinmcn_associate interacts with openstack14:47
colinmcn_operator instlls / configures14:47
colinmcn_associate is focused on a suer consuming, with tasks and quizes that break down into each functional task14:47
sarobYup, assoc has admin task, operator has install14:47
colinmcn_yes, concept and structure are sound14:47
sarobPlan was to use scripted virtualbox for both books14:48
colinmcn_yup14:48
colinmcn_though, I think past structure, there are some ops items still in associate14:48
sarobOperator would do separate install tasks on diff VMs14:49
colinmcn_operator is installing openstack on "bare metal"14:49
colinmcn_associate is consuming openstack, launching instances, etc14:49
colinmcn_correct?14:49
sarobYup14:49
dguitarbiteOperator is installing OpnStack14:49
dguitarbitenot necessary to be bare metal14:49
*** gals has quit IRC14:49
sarobIronic is not clear to me to include either14:50
colinmcn_put quotes around it14:50
colinmcn_sorry14:50
colinmcn_virtual bare metal14:50
sarobOkay14:50
sarobAhh okay14:50
colinmcn_installing openstack on an operating system14:50
alagalahIs this still the right repo? (should there be a link on the wiki?) https://github.com/openstack/openstack-manuals.git14:50
colinmcn_vs instantiating instances, providing access, etc14:50
sarobAlagalah right repo14:51
colinmcn_yes, training-guide subdir14:51
alagalahty14:51
colinmcn_btw, can you repost the link to the gdoc .. I switched computers and want to make sure i'm on the latest14:52
alagalahhttps://docs.google.com/drawings/d/1ju78O-PjkZIeSbpGkUndIohQeQy06QXseRPbCy2F6F8/edit14:52
*** sarob__ is now known as sarob_14:53
alagalahgenerating-sources now from a clean clone, so I'd love to have a look at all you've restructured, sarob, as that was your original RFC right?14:53
alagalahsarob_14:54
sarob_which rfc?14:54
alagalahRequest For Comment14:54
alagalahYou requested we comment about your restructure, hence... I'm rebulding now14:54
colinmcn_thx14:54
sarob_i know what it means, but what rfc are you referring to?14:54
*** sarob has quit IRC14:54
sarob_ahh, right14:54
colinmcn_I do want to propose one topic before 714:54
colinmcn_btw14:54
colinmcn_moving this back to 7 am pacific. 6am doesn't leave any prep time b4 the meeting14:54
*** colinmcn_ has quit IRC14:55
sarob_well there is another meeting at 7:30am pst14:55
*** colinmcn_ has joined #openstack-meeting-alt14:55
colinmcnamaraCrap14:55
sarob_schedule is all filled up14:55
colinmcnamaraAlso. Good luck getting more contributors on14:55
colinmcnamara6 am meeting is a barrier14:55
*** r_m_r has joined #openstack-meeting-alt14:55
colinmcnamaraMy 2 cents14:56
sarob_9am pst monday is still open14:56
alagalahEast Coast :)14:56
sarob_and 7am pst friday14:56
colinmcnamara9am Monday is better than 6 am any day14:56
sarob_probably right14:56
sarob_dguitarbyte does 9am pst work for you?14:57
colinmcnamaraCould always just create openstack-meeting-alt-214:57
sarob_should be 10:30pm in mumbai14:57
dguitarbitek14:58
sarob_lets not be guilty of that sin14:58
dguitarbitethats a good time for me14:58
sarob_okay cool14:58
sarob_anyone else chime in on time?14:58
*** r_m_r has quit IRC14:59
*** bauzas has joined #openstack-meeting-alt15:00
sarob_#topic general free for all15:00
alagalahOk15:01
sarob_#action sarob to reset meeting time for monday 9am pst15:01
colinmcn_sweeet!15:01
alagalahSo I just finished the build, will have a quick look15:01
alagalahI'm sure its gorgeous15:01
alagalahWhat are we going to do about the gdraw?15:01
alagalahI'm still not clear about how we make a gdraw-> trello compiler?15:01
alagalahMeatscript seems simplest :)15:02
sarob_its a brainstorming tool15:02
alagalahI think its wonderful, it lays it out visually, which is perfect for me15:02
alagalahI just want to know what specific thing I can help with15:02
sarob_i went through the cloud admin and install guide15:02
colinmcn_meatscripts are the tool to use15:02
*** bauzas has left #openstack-meeting-alt15:02
sarob_dumped what could go where into the digram15:02
sarob_diagram15:02
colinmcn_its a good visualization15:03
sarob_then roughed out the structure15:03
sarob_started making stuff15:03
colinmcn_especially on my 27" monitors vs my 13" laptop15:03
colinmcn_;)15:03
sarob_so the associate guide15:03
sarob_it needs some clean up15:03
sarob_but i think it is mostly complete for a rough draft15:04
colinmcn_yeah, for rough draft15:04
colinmcn_if rough draft = rc115:04
sarob_sure15:04
colinmcn_I suggest, we do a rc1,2,3 structure15:04
dguitarbiteassociate is complete for rough draft, I need to put up the install section as per OVS fixes and stuff15:04
colinmcn_and gate bugs / features that way15:04
*** betsy has joined #openstack-meeting-alt15:04
colinmcn_so, rough draft = feature complete and squashing bugs15:04
sarob_so we need some cards on associate guide review for publish15:04
colinmcn_sounds like there are a couple features necessary15:05
sarob_and another for publish to havana action15:05
colinmcn_so, do we have concensus on mapping to RC1/2/315:05
colinmcn_and being strict about adding features vs squashing bugs?15:05
colinmcn_thats a pretty big one15:05
dguitarbiteYep, makes sense15:05
colinmcn_so if rough draft equals feature complete (maybe with errors)15:06
colinmcn_then we need to identify and prioritize any feature work15:06
colinmcn_before we make the call15:06
sarob_i am good with that15:06
dguitarbiteRC1/2/3 -- in sync with other projects as they are dependent on them15:06
sarob_righto15:06
colinmcn_normally the process15:06
alagalahdguitarbite: What OVS fixes need to be incorporated?15:06
colinmcn_h1/2/3, rc1/2/315:07
dguitarbiteOVS 1.4 ships with Ubuntu 12.04, OVS 1.9 is needed for getting Neutron working properly15:07
dguitarbitesome fixes on that15:07
alagalahAh15:08
sarob_The training-manuals team meets weekly on Monday at 1700 UTC on #openstack-meeting15:08
sarob_posted15:08
colinmcn_sweet15:08
colinmcn_awesome15:08
sarob_note not alt15:08
alagalahdguitarbite: Yes, been going thru that hell with OVS on DevStack on Fed1815:08
colinmcn_ahhhh15:08
colinmcn_thank you15:08
sarob_sanity check, we are going to lose the channel in 20 min15:09
*** vkozhukalov has quit IRC15:09
colinmcn_and I need to hop down to the dentist pretty soon15:09
alagalahSarob_ ...15:10
alagalahPretty15:10
sarob_#action colin will rough out release dates15:10
sarob_thx15:10
alagalahwelcome and well deserved... I love it in fact15:10
sarob_cool15:10
alagalahI will do a walk thru this weekend as if I'm an instructor, and no, I don't want that on the action items15:10
alagalahI will report back if I got it done, I have a code freeze I have to meet on another proj15:11
* sarob_ no action items whataaaaa15:11
sarob_sigh okay15:11
alagalahSorry mate15:11
colinmcn_sorry sarob, day jobs15:11
sarob_lets all read through what is published15:12
alagalahBut the intention is there, if I can go through this as if I am teaching someone.... then it's a win... that is my goal...15:12
*** colinmcnamara has quit IRC15:12
sarob_we need to get the associate and operator guide to a point that an instructor and a student can follow them15:12
colinmcn_yup15:12
colinmcn_and that really comes from a dry run15:12
colinmcn_with the students capturing bugs15:12
colinmcn_it's easy to get tunnel vision15:13
sarob_the cards should be mostly coming from that experience at this point15:13
colinmcn_cool15:13
sarob_lets cut this at that point15:13
sarob_any last words of wisdoms15:14
colinmcn_i'm good15:14
alagalahLaters15:14
sarob_colin needs his teeth drilled15:14
sarob_i need coffee15:14
colinmcn_:/15:14
colinmcn_yup15:14
colinmcn_sux15:14
sarob_ive got interviews15:15
colinmcn_time to adjurn15:15
sarob_cheers all15:15
colinmcn_endmeeting?15:15
sarob_#endmeeting15:15
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:15
openstackMeeting ended Tue Nov 26 15:15:19 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:15
openstackMinutes:        http://eavesdrop.openstack.org/meetings/training_manuals/2013/training_manuals.2013-11-26-14.00.html15:15
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/training_manuals/2013/training_manuals.2013-11-26-14.00.txt15:15
openstackLog:            http://eavesdrop.openstack.org/meetings/training_manuals/2013/training_manuals.2013-11-26-14.00.log.html15:15
*** gokrokve has joined #openstack-meeting-alt15:15
*** colinmcn_ has quit IRC15:16
*** Barker has joined #openstack-meeting-alt15:16
sarob_cheers mates15:18
*** sarob_ has quit IRC15:19
*** sarob has joined #openstack-meeting-alt15:20
*** sarob has quit IRC15:24
*** venkatesh has joined #openstack-meeting-alt15:27
*** alazarev has joined #openstack-meeting-alt15:27
*** rudrajit has joined #openstack-meeting-alt15:29
*** andrewmo has joined #openstack-meeting-alt15:31
*** sacharya has joined #openstack-meeting-alt15:31
*** DennyZhang has joined #openstack-meeting-alt15:32
*** DennyZhang has quit IRC15:34
*** DennyZhang has joined #openstack-meeting-alt15:36
*** samkottler has joined #openstack-meeting-alt15:36
*** eharney has joined #openstack-meeting-alt15:39
*** flwang has quit IRC15:39
*** flwang has joined #openstack-meeting-alt15:40
*** noslzzp has joined #openstack-meeting-alt15:41
*** dhellmann is now known as dhellmann-afk15:41
*** devkulkarni has joined #openstack-meeting-alt15:42
*** dguitarbite has quit IRC15:44
*** rnirmal has joined #openstack-meeting-alt15:45
*** sacharya has quit IRC15:46
*** akuznetsov has quit IRC15:46
*** andrewmo has quit IRC15:48
*** funzo has joined #openstack-meeting-alt15:49
*** briancline has joined #openstack-meeting-alt15:50
*** MarkAtwood has joined #openstack-meeting-alt15:51
*** jtomasek has quit IRC15:53
*** jmontemayor has joined #openstack-meeting-alt15:55
*** aguzikova has joined #openstack-meeting-alt15:56
*** adrian_otto has joined #openstack-meeting-alt15:56
*** jtomasek has joined #openstack-meeting-alt15:56
*** rudrajit has quit IRC15:57
*** dhellmann-afk is now known as dhellmann15:58
*** claytonc has joined #openstack-meeting-alt15:59
*** paulczar has joined #openstack-meeting-alt16:00
adrian_otto#startmeeting Solum Team Meeting16:01
openstackMeeting started Tue Nov 26 16:01:00 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:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: Solum Team Meeting)"16:01
openstackThe meeting name has been set to 'solum_team_meeting'16:01
*** muralia has joined #openstack-meeting-alt16:01
*** jwforres has joined #openstack-meeting-alt16:01
*** brents has joined #openstack-meeting-alt16:01
*** RoshanAgr has joined #openstack-meeting-alt16:02
* samkottler waves16:02
*** paulmo has joined #openstack-meeting-alt16:02
*** kraman2 has joined #openstack-meeting-alt16:02
*** amytron has joined #openstack-meeting-alt16:02
*** tomblank has joined #openstack-meeting-alt16:02
adrian_otto#topic Roll Call16:02
*** openstack changes topic to "Roll Call (Meeting topic: Solum Team Meeting)"16:02
russellbo/16:02
kraman2here16:02
brianclineo/16:02
tomblankTom Blankenship, Rackspace16:02
claytonco/16:02
adrian_ottohello everyone16:02
RoshanAgrRoshan Agrawal, Rackspace16:03
* samkottler is here16:03
* funzo is here16:03
tdeckersTom Deckers, Cisco... new guy16:03
coolsvapSwapnil Kulkarni16:03
muraliaMurali Allada, Rackspace16:03
funzohey tdeckers, welcome16:03
* russellb doesn't think corporate affiliations are important in this context, fwiw16:03
RoshanAgrwelcome Tom16:03
jwforresJessica here16:03
paulmoPaul Montgomery, Rackspace16:03
* briancline also a new guy, at least for this project16:03
brentsBrent Smithurst, ActiveState16:04
devkulkarniDevdatta Kulkarni, Rackspace16:04
*** rajdeep has joined #openstack-meeting-alt16:04
adrian_ottowelcome newcomers!16:04
*** aratim has joined #openstack-meeting-alt16:04
paulczarPaul Czarkowski, Rackspace16:04
rajdeephi16:04
aratimArati Mahimane, Rackspace16:05
russellbsigh16:05
rajdeepRajdeep Dua, VMware16:05
adrian_otto#link https://wiki.openstack.org/wiki/Meetings/Solum our agenda for today16:05
devkulkarniwhoa.. lots of items16:06
*** sallamaraju has joined #openstack-meeting-alt16:06
adrian_otto#Topic Announcements16:06
*** openstack changes topic to "Announcements (Meeting topic: Solum Team Meeting)"16:06
adrian_ottoneed to move quickly to get through this monster agenda16:06
adrian_otto1) Working Groups16:06
adrian_ottoWe have arranged two working groups:16:06
adrian_ottoA) Language Pack Working Group16:06
adrian_ottoSubscribe to https://blueprints.launchpad.net/solum/+spec/lang-pack to join it.16:06
adrian_otto(we can make a LP team for this as needed)16:06
adrian_ottoParticipate in the Doodle poll to schedule the meeting series: https://wiki.openstack.org/wiki/Solum/BreakoutMeetings#Language_Pack_Working_Group_Series16:07
russellbi'm a little concerned about the sizes of these groups and the impact it may make on getting something done ASAP16:07
russellbi'd almost rather just one person go off and make a strawman proposal16:07
russellband we beat it up on the mailing list16:07
adrian_ottorussellb: we should do that too16:07
russellbinstead of limiting progress to a meeting once a week16:07
kraman2russellb: +116:07
adrian_ottoI think it's importatnt to source input from the full group, but not all of us are expected to generate code16:08
adrian_ottoB) Git Integration Working Group16:08
adrian_ottoSubscribe to https://blueprints.launchpad.net/solum/+spec/git-integration to join it.16:08
russellbdesign by committee :)16:08
adrian_ottoParticipate in the Doodle poll to schedule the meeting series: https://wiki.openstack.org/wiki/Solum/BreakoutMeetings#Git_Integration_Working_Group_Series16:08
claytoncfor the language-pack working group i have not seen feedback via the ML, I would expect people who are interested to be responding already16:08
adrian_ottolet's try a few things and see what works best16:08
adrian_otto#topic Review action items from prior meeting16:08
*** openstack changes topic to "Review action items from prior meeting (Meeting topic: Solum Team Meeting)"16:08
*** SergeyLukjanov has quit IRC16:08
adrian_ottoaotto: Schedule breakout meetings for new working groups16:08
adrian_otto(in progress, Doodle polls mentioned above)16:08
adrian_otto#topic Review of Solum SFO Community Workshop16:09
*** openstack changes topic to "Review of Solum SFO Community Workshop (Meeting topic: Solum Team Meeting)"16:09
*** sergmelikyan has joined #openstack-meeting-alt16:09
adrian_ottohttps://etherpad.openstack.org/p/SolumSFOCommunityWorkshop16:09
adrian_ottoRoshan Agrawal: Report number of attendees, companies represented, format, lessons learned, and next steps.16:09
adrian_ottoFor remote participants: Are there improvements we could make for next time?16:09
adrian_ottolet's wait for Roshan first16:09
RoshanAgrWe had 35 attendees in person16:09
RoshanAgrand another 25 joined remotely16:09
*** flwang has quit IRC16:09
RoshanAgrAll in all, heavy participation16:09
russellbnow we need code from all these people :)16:10
*** yamahata_ has quit IRC16:10
*** ashaikh has joined #openstack-meeting-alt16:10
RoshanAgrrussellb: yes sure :-)16:10
*** hemanth has joined #openstack-meeting-alt16:10
adrian_ottofor those who have not been watching the Gerrit system, we have good velocity in terms of patches16:10
adrian_ottokeep up the great participation in terms of code reviews16:10
RoshanAgrAny feedback from participants on the structure of the workshop?16:10
RoshanAgrMy sense is that it went really well16:11
*** markwash has quit IRC16:11
coolsvapadrian_otto, RoshanAgr : The arrangement was very nice, hangout helped a lot to be involved, the timing could be a concern for some :) but i guess it can be followed for future workshops16:11
RoshanAgrWe worked thorugh several design topics16:11
adrian_ottowe got positive remarks from a bunch of you, but are really seeking ways to improve for next time, so if you have criticism, and don't want to voice it here, please catch me or Roshan on PM16:11
RoshanAgrWe have etherpad notes from the workshop - we should file them/reference them for further discussions on the topics discussed16:12
adrian_ottodid the Remote attendees all feel like they were able to follow?16:12
brianclineagreed on what coolsvap mentioned regarding timing16:12
russellbhangout worked well, i just had a lot of conflicts16:13
brianclineby any chance was it able to be recorded?16:13
russellbbriancline: probably a better use of time to just review the notes16:13
RoshanAgrWe have notes: https://etherpad.openstack.org/p/SolumWorkshopTrack1Notes16:13
adrian_ottobriancline: good suggestion, we will see about doing that next time16:13
russellband start ML threads on anything that needs more discussion16:14
claytoncIn terms of pure productive output it likely was extremely valuable for driving consensus on a few core topics16:14
adrian_ottorussellb: yes16:14
claytoncforcing people to yay/nay items16:14
brianclineRoshanAgr: thanks16:14
adrian_ottoHow frequently should we schedule these events? In-Person? Virtual?16:14
RoshanAgrbriancline: welcome16:14
funzovirtual is much easier on budgets16:14
claytoncno more than every 4 months16:14
adrian_ottomost of us are attending ODS on 6 month intervals16:14
claytoncpost ODS is potentially a good option16:15
RoshanAgrhow about every 3 months16:15
*** rajdeep has quit IRC16:15
RoshanAgrright in the middle of two ODS16:15
russellbevery 3 is pretty aggressive16:15
claytoncit lets us absorb other teams stuff and then bring it back to a targetted discussion16:15
brianclinewhat about a combination of both, except a traveling circus? for instance an Austin office for a subsequent venue16:15
claytonci believe other teams are suggesting that16:15
brianclinethat is, unless most participants are in the bay area16:15
RoshanAgrI am suggesting twice a year.16:15
russellbtwice/year like design summits makes sense16:16
RoshanAgrODS + workshop + ODS + workshop16:16
adrian_ottowe should do some homework to plot the location of participants. We do know we are pretty spread out, mostly from the US16:16
*** hemanth has quit IRC16:16
russellbbut should always treat the mailing list as the first class citizen, and where decisions should ultimately be made whenever possible :)16:16
adrian_ottook, so please think on this topic and we will follow up on ML16:16
*** brents_ has joined #openstack-meeting-alt16:16
adrian_ottorussellb: agreed16:17
adrian_otto#topic Discuss alignment with Icehouse Release Schedule16:17
*** openstack changes topic to "Discuss alignment with Icehouse Release Schedule (Meeting topic: Solum Team Meeting)"16:17
*** brents has quit IRC16:17
*** brents_ is now known as brents16:17
adrian_ottoDo we want to align with the icehouse milestone schedule: https://wiki.openstack.org/wiki/Icehouse_Release_Schedule16:17
*** dhellmann is now known as dhellmann-afk16:17
*** sacharya has joined #openstack-meeting-alt16:17
russellbadrian_otto: what does alignment mean16:17
adrian_ottowe have 4 milestones in LP, but I have not targeted them to dates16:17
adrian_ottoalignment would mean milestone 1 = i2, etc16:18
adrian_ottoso we would do a time based release schedule rather than feature based16:18
russellbin general, working along the openstack schedule makes sense, but i don't know if the existing milestones are scoped to match the schedule right now, are they?16:18
adrian_ottothis might not make sense until we have a base set of functionality first16:18
*** akuznetsov has joined #openstack-meeting-alt16:18
*** rajdeep has joined #openstack-meeting-alt16:18
kraman2adrian_otto: while starting this project might make more sense to do feature basd release for the first few releases16:18
adrian_ottomy opinion is that we should start alignment as soon as we have one working use case16:19
claytoncthe combination of those two statements makes sense to me16:19
brianclineI would think so, to avoid another swift-like situation (it may have served well in the past but for a new project it seems anomalous)16:19
tomblankadrian_otto: it may be too soon for us to go to date based schedule but as soon as we have base functionality i think that would be good.16:19
russellbas long as each iteration is aggressive, feature based seems OK for now16:19
adrian_ottook, anyone feel strongly that we should switch to dates before we have some basic features done?16:20
sallamarajuRoshanAgr was the use case described on white board with 7-8 steps captured some place?16:20
RoshanAgrit is on my phone, and Krisha also has it. I or Krisha will publish it16:20
brianclineI sort of do, though it seems a valid point that i1 is going to be a miss in that case16:20
russellbi dunno ... time based is tempting, makes life easier with it aligned with everything else16:20
russellbi1 does have some notable stuff16:20
claytoncsallamaraju: RoshanAgr i owe a todo from ML to add more scenarios like that as well16:20
kraman2RoshanAgr: I have the picture as well and can publish it16:21
russellbthere's an API binary, the service is integrated with devstack, some initial API implementation is there16:21
RoshanAgrclaytonc: perfect16:21
*** jtomasek has quit IRC16:21
* briancline intrigued16:21
brianclinedidn't realize it was that far along (mostly re: devstack)16:21
russellbthe more i think of it, the more i like just using the main openstack schedule16:21
russellbyeah we need more people writing/reading the code16:21
brianclinein that case, I actually feel more strongly now about icehouse alignment16:21
adrian_ottook, so I think I see consensus here that we should stay on the feature milestone system for now16:22
russellbdecent velocity, but not that many people compared to how many say they are interested in this project16:22
adrian_ottoand revisit alignment with the date based system16:22
russellbi'm actually arguing the opposite16:22
adrian_ottook16:22
russellbdon't have to do the feature freeze part16:22
russellbbut alignment is good16:23
brianclinewrt the aforementioned writing/reading code part, I'm glad to help, as the holidays are going to be slooowww for me this year, it seems16:23
russellband as each openstack milestone hits, a solum milestone update email can go out talking about project status and what we accomplished16:23
adrian_ottorussellb: I see the key reason that the number of developers submitting patches is small is because there are many developers who are getting used to the way this project works.16:23
* russellb nods16:23
adrian_ottowe have a lot of open design items16:23
*** venkatesh has quit IRC16:24
brianclineyes, that's the sole reason I haven't tangibly jumped in by now16:24
adrian_ottoand as we converge on some ideas, and devs get familiar with the way things work, whic will ramp up naturally16:24
russellbyep, need to burn through those, and hopefully identify the smallest reasonable iteration to start with16:24
rajdeep+1 on open design items16:24
adrian_ottoso, let's table this discussionfor now16:25
russellbok...16:25
adrian_ottoand let's revisit it on ML to make the consensus very clear16:25
*** alazarev has quit IRC16:25
adrian_ottoand let's look at some blueprints to help advance our design situation16:25
*** sarob has joined #openstack-meeting-alt16:25
adrian_otto#topic Review Blueprints16:25
*** openstack changes topic to "Review Blueprints (Meeting topic: Solum Team Meeting)"16:25
adrian_ottoFirst Milestone: https://launchpad.net/solum/+milestone/0.116:25
russellblink doesn't work16:26
adrian_ottothis is a view of all blueprints for the first milestone16:26
adrian_ottooh, no16:26
RoshanAgrhttps://launchpad.net/solum/+milestone/milestone-116:26
RoshanAgrThat is the right link16:26
rajdeeppermission error16:26
adrian_ottohttps://launchpad.net/solum16:26
adrian_ottolook at the section "Series and milestones"16:27
*** alazarev has joined #openstack-meeting-alt16:27
adrian_ottothen click on milestone-1 on that little line/dot chart16:27
adrian_ottothat should show you the blueprints in this milestone16:27
adrian_ottodoes that work?16:27
russellbthe link RoshanAgr posted works16:27
adrian_ottook, sorry for the mixup16:28
adrian_ottoSubscribe to each blueprint if you want email updates on them.16:28
adrian_ottoAsk for Assignee status if you can keep track of development on the feature and report on it weekly at our IRC meetings. You do not have to write the code yourself if you are the Assignee, only champion it.16:28
kraman2adrian_otto: the blueprint for git is not specifically the one for git pull workflow. is that intentional?16:28
RoshanAgrAbility to push code to the platform via Git: I would request Assignee status for that blueprint16:28
russellbfwiw, assignee in other projects == implementor16:28
adrian_ottokraman2: Roshan will address16:28
kraman2RoshanAgr: will ping you offline16:29
adrian_ottohold on before we jump in on those16:29
RoshanAgrkraman2: sure16:29
adrian_ottolet's start simple16:29
adrian_otto#link https://blueprints.launchpad.net/solum/+spec/definitions Definitions and terminology used in Project Solum16:29
adrian_otto Seek Definition Approval. Are we ready to proceed, or is more discussion needed?16:29
tdeckersjust catching up... Application seems ambiguous.  Has Application package been considered?16:30
adrian_ottotdeckers: we can revisit that one16:30
adrian_ottoI'll just take noted for subjects to discuss on this BP if we are not ready to approve it16:31
adrian_ottosince we have a long list to look at today16:31
*** venkatesh has joined #openstack-meeting-alt16:31
tdeckersnp16:31
claytonctdeckers: let's go to the ML on that one16:31
claytonchaven't had a good discussion16:31
adrian_ottook, will do, let's advance to the next if there are no further remarks16:31
*** Barker has quit IRC16:31
brianclineI would say strike "OS Container" and keep it generic as "Deployment Unit"16:31
RoshanAgrbriancline: +116:32
claytonc+116:32
tdeckers+116:32
coolsvap+116:32
gokrokve+116:32
tomblank+116:32
adrian_ottoOk, thanks. We will not seek approval, because we have more changes on this16:32
jwforresI would like to see some concept of 1-1 vs 1-many on the relationships in that diagram if possible16:32
adrian_ottowill revisit later.16:33
adrian_otto#link https://blueprints.launchpad.net/solum/+spec/app-deploy-manage (roshanagr) Solum-R1 Stories: Application Deployment/management16:33
adrian_ottoNote, this has several child blueprints, each will be individually discussed/approved.16:33
russellbR1 == milestone 1?  or?16:33
adrian_ottoyes R1=milestone116:33
adrian_ottoSeek Definition Approval. Are we ready to proceed, or is more discussion needed?16:33
RoshanAgrrussellb: R1 != milestone 116:33
russellbheh16:33
adrian_ottowhat?16:33
adrian_ottooh, because some were marked as out of scope?16:34
gokrokveR1 = requirement #116:34
RoshanAgryes16:34
*** Barker has joined #openstack-meeting-alt16:34
RoshanAgralso , what gokrokve said16:34
adrian_ottoaha, I see16:34
russellbi think it's useful to capture requirements around the milestone16:34
russellbso if some of this is in and some out, maybe it makes sense to clarify that somehow?16:35
adrian_ottoso do we need further iteration on this as proposed, or should we approve this, and focus on the child BP's next?16:35
RoshanAgrrussellb: yes agreed. We still need some requiment identifier16:35
*** s3wong has joined #openstack-meeting-alt16:35
russellbI think it should be updated to clearly identify what is in scope for the milestone16:35
RoshanAgrR1, R2 is an attempt, but I can see how that can be confusing16:35
russellband the rest pushed off to something else16:35
devkulkarnirussellb: +116:36
kraman2this is a high level blueprint which is broken down into smaller ones. perhaps we should keep only the implementation BPs as part of the milestone.16:36
russellbperhaps.16:36
*** alagalah has left #openstack-meeting-alt16:36
gokrokveYes. We had a list of requirements to be implemented in M1.16:36
russellbthe list of blueprints targeted at the milestone sort of define the milestone on their own16:36
gokrokveThis list was captured in etherpad.16:37
rajdeepone question on deployment16:37
adrian_ottokraman2: that's somethign I did discuss with Rohan, and I support that approach16:37
adrian_otto*Roshan16:37
RoshanAgrkraman2: agreed.16:37
russellbsome of this is user story stuff, and some of it identifies some design details (the CLI stuff)16:37
adrian_ottorajdeep: ?16:37
rajdeephow does the persistent store get rewired from local settings to remote setting16:37
rajdeepon deployment16:37
russellbthe story would be less detailed and just that ... I can create a thing via the CLI16:37
kraman2russellb: ys, but we can move that into the CLI BP itself16:37
russellbor see the deatils of the thing16:37
russellbsure16:37
*** betsy_ has joined #openstack-meeting-alt16:38
*** s3wong has quit IRC16:38
adrian_ottorajdeep: can you expand on that question with some additional detail about your concern?16:38
*** betsy has quit IRC16:38
*** betsy_ is now known as betsy16:38
rajdeepe.g jdbc url would change to the private ip of the container where service is running16:38
*** eankutse1 has joined #openstack-meeting-alt16:38
*** tnurlygayanov_ has joined #openstack-meeting-alt16:38
rajdeepdeveloper first builds the app locally16:39
rajdeepand then does deployment to solum16:39
rajdeepsolum should auto rewire to the remote persistent store16:39
*** eankutse has quit IRC16:40
adrian_ottoin that case you would need to make the configuration option flexible. One way to do that is to use a service registry. Another way might be to abstract data services behind Heat resources that are defined by Providers, and you look up the address of it at runtime.16:40
gokrokveSolum will support runtime variables and environment but it is up to developer to map these variables to some specific services' parameters.16:40
adrian_ottogokrokve: yes, and environment variables is another way to handle it, which is a bit less flexible, but a common technique16:41
rajdeepyes we should do both auto and manual rewiring16:41
rajdeepgiving option to the developer16:41
tdeckerspersistance service lookup seems the way to go.  Would be interesting to see how migrations of the persistence service itself would be handled though16:41
adrian_ottook, so not to get too far in the weeds on this right now16:42
tdeckerse.g. schema migrations is apps require it, etc..16:42
*** markwash has joined #openstack-meeting-alt16:42
rajdeepok16:42
gokrokveIt might be a requirement for "badger" or "language pack" to support auto rewiring for common services.16:42
adrian_ottowe have a few important blueprints that I'd like to get assigned today16:42
gokrokveI can take User authentication for incoming requests.16:42
russellbgokrokve: is that just using keystone auth token middleware?16:43
adrian_ottook, we will get there in a couple minutes gokrokve16:43
RoshanAgrI volunteer for: Ability to push code to the platform via Git16:43
russellbshould be pretty quick/easy :)16:43
adrian_ottoour next one is:16:43
adrian_otto#link https://blueprints.launchpad.net/solum/+spec/git-integration (assignee-needed) Ability to push code to the platform via Git16:43
adrian_ottoremember that being assigned means that you will be polled at these weekly meetings for status16:43
gokrokverussellb: Not really. It is an integration with keystone but we need to figure out an access model for solum resources.16:43
adrian_ottothat we expect you to keep informed about the status of allr elated dev work16:43
gokrokveYes. I will update you on the status for this BP each meeting.16:44
adrian_ottobut it does not meant that you will individually write all the code16:44
russellbdoes the blueprint capture the first iteration of git integration?16:44
* russellb thinks the primary author of the code should be the assignee :)16:44
kraman2russellb: there is a git-pull BP for that16:44
devkulkarnirussellb: BP has two parts16:44
kraman2i can take that one16:44
russellbkraman2: cool16:44
devkulkarnione is git-pull, another bp is git-push16:44
brianclineI'd like to jump on solum-git-pull as well16:44
*** MarkAtwood has quit IRC16:44
RoshanAgradrian_otto: is the expectation for an assignee writes some code16:45
russellbso this has both pull and push under it, both are part of first iteration?16:45
*** coolsvap_ has joined #openstack-meeting-alt16:45
adrian_ottoso if you want to work on one of these (contribute code/design) just subscribe to the BP16:45
russellbRoshanAgr: i hope so16:45
kraman2no, only pull is part of first itr16:45
*** coolsvap has quit IRC16:45
adrian_ottoand let one of you own it who is a subject matter expert16:45
russellbok, if just pull, looks like some dependency juggling needs to be done16:45
kraman2atleast thats what we discussed suring F2F16:45
russellbor just remove the push from the dep tree16:46
kraman2russellb: push is needed as well16:46
kraman2there pull and push are seperate16:46
russellbright, but the way the blueprints are set up right now, it's saying both are in the first milestone16:46
kraman2if we keep just pull BP on milestone 1, we should be fine16:46
russellbok, so then git-integration wouldn't be on milestone-116:46
kraman2adrian_otto: RoshanAgr: can we make that change?16:47
russellband just solum-git-pull16:47
devkulkarnirussellb: that is correct16:47
paulczarfor first itr could be as basic as a url to a tarball ( github generates these automagically )  â€¦ that would reduce the deps even further16:47
RoshanAgrrussellb: a subset of that will be (it still needs to broken into child blueprints16:47
*** SergeyLukjanov has joined #openstack-meeting-alt16:47
adrian_ottook, so do I have a volunteer to own the parent blueprint git-integration (Roshan, do you want it, or is there a better Stacker for that?)16:47
kraman2adrian_otto: I can own the git flow16:47
kraman2if RoshanAgr doesnt mind :)16:48
adrian_ottook, set yourself as assignee, or if it does not allow you I can do it for you16:48
russellbRoshanAgr asked about code expectation, i don't think that was answered16:48
RoshanAgrkraman2: I won't mind :-)16:48
russellb<RoshanAgr> adrian_otto: is the expectation for an assignee writes some code16:48
adrian_ottorussellb: I missed that sorry. What was the concern? Can we repeat it?16:48
adrian_ottoaha16:48
adrian_ottono, an assignee is not necessarily a code writer16:48
russellbwhy?16:48
adrian_ottobut you need to follow all the patches for that feature16:49
russellbwhy wouldn't you go to the person doing the work for an update?16:49
adrian_ottoso I prefer that it be owned by a developer16:49
adrian_ottoso they can review all the code that posts to that blueprint. It should at least be a reviewer.16:49
adrian_ottothis is a case where there will be more than one developer16:49
adrian_ottoif there is onyl one, this is simple, he/she owns it16:50
kraman2russellb: how are other projects (nova?) structured ?16:50
adrian_ottoif there is a group contributing, then you pick a captain, essentially16:50
russellband if there are multiple, one of the developers would own it?16:50
russellbright ... then the answer to the question is yes then right?16:50
adrian_ottorussellb: yes16:50
russellbthe expectation is generally that the assignee is helping write the code at least16:50
RoshanAgrIn the case of git blueprint, kraman2 has volunteered16:50
adrian_ottoyes, that makes sense for that one16:50
RoshanAgrI think he is the right owner of it since he will be closer to the code16:51
* briancline also volunteered for pull16:51
adrian_ottoany other participants will be subscribers16:51
adrian_ottoand I ask that if you write *any* code for that bp that you review all patches for it.16:51
kraman2+116:51
adrian_ottoso you don't end up with duplicative contributions, or in conflict16:51
adrian_ottofor those who are new to using Gerrit+Launchpad together, the system can automatically post links to the patches in the LP whiteboard for the blueprint16:52
adrian_ottowhen the Gerrit topic is listed in the whiteboard16:52
adrian_ottoso all you need to do is be a subscriber, and you will get an email every time someone posts a review against that blueprint16:53
adrian_ottomake sense?16:53
russellbyou can also get email notifications from gerrit16:53
russellbfor new changes, merged changes, or any updates to reviews16:53
adrian_ottorussellb: yes16:53
adrian_ottothat's more of a firehose16:53
russellbbut i would expect anyone working on this full time to keep up with that, IMO16:54
russellbshould always have an idea of what code is in flight16:54
adrian_ottook, so we had a packed agenda today, and I knew it would be hard to get through all of it, so I'll allow you to use the Agenda wiki page to know what needs to be assigned, and let's get those all assigned. See me if there are any questions, please.16:55
brianclineso as a closing point, the current assignees on these should be following everything related, possibly contributing code16:55
adrian_ottofor those topics that need discussion, let's fire up ML threads for each16:56
brianclineif i understood that correctly16:56
kraman2briancline: i think assignees will be contributing code16:56
russellbkraman2: +1 :)16:56
adrian_ottobriancline: yes, if you own it, there is an expectation that you are down in the details16:56
*** ativelkov has joined #openstack-meeting-alt16:56
adrian_ottoand that you are helping advance it16:56
brianclineok16:57
adrian_ottoand even if you are doing most of the code, and you don't want to be the owner, you will not be forced to.16:57
devkulkarnibriancline, kraman2: please feel free to add/modify to git-solum-pull bp. will be happy to discuss it afterwards16:57
adrian_ottobut one of your co-contributors will16:57
russellbi don't understand why the person doing most of the code would *not* be the owner16:57
russellbthey are the owner by definition, to me16:57
kraman2devkulkarni: will start a ML thread about it16:57
adrian_ottorussellb: I think that will happen naturally16:58
adrian_ottoand we can re-assign the owner when it makes sense16:58
russellbok.16:58
*** boris-42 has joined #openstack-meeting-alt16:58
adrian_ottobut I don't want contributors to get the sense that if they are not marked as the owner that they can't work on it16:58
coolsvap_I think instead of much debating about who should own it, be a subscriber and write code :)16:58
adrian_ottoso I want to be very explicit about that16:58
devkulkarnicoolsvap_: +2 :)16:59
*** flaper87 is now known as flaper87|afk16:59
adrian_ottoexactly16:59
adrian_ottoso16:59
adrian_otto#topic Open Discussion16:59
*** openstack changes topic to "Open Discussion (Meeting topic: Solum Team Meeting)"16:59
adrian_ottosorry I never have enough time for this part of the meeting16:59
adrian_ottoI will need to do a better job of keeping the Agenda shorter16:59
gokrokveIt will be hard for this stage of the project.17:00
russellbML threads should help17:00
adrian_ottoindeed17:00
RoshanAgrWe covered a lot. great meeting17:00
adrian_ottothanks everyone, I'm super pumped about where we are17:00
adrian_otto#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
brianclinecoolsvap_: right, just want to avoid duplication of efforts since folks tend to have different thresholds of when they should push up code for a review17:00
openstackMeeting ended Tue Nov 26 17:00:41 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-26-16.01.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/solum_team_meeting/2013/solum_team_meeting.2013-11-26-16.01.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/solum_team_meeting/2013/solum_team_meeting.2013-11-26-16.01.log.html17:00
*** sergmelikyan has quit IRC17:00
*** rajdeep has quit IRC17:01
adrian_ottofeel free to continue discussion in #solum17:01
*** IgorYozhikov has joined #openstack-meeting-alt17:01
*** paulmo has left #openstack-meeting-alt17:01
*** paulczar has left #openstack-meeting-alt17:01
*** jwforres has left #openstack-meeting-alt17:01
ativelkovAny Muranoers here? :)17:02
katyaferventHi!17:02
*** kraman2 has left #openstack-meeting-alt17:03
ogelbukho/17:03
IgorYozhikov+17:03
tnurlygayanov_yes)17:04
*** dteselkin has joined #openstack-meeting-alt17:04
ativelkovGood. Solum guys had a great conversation here, let's do our own meeting productive as well )17:04
*** coolsvap_ is now known as coolsvap_away17:04
ativelkov#startmeeting murano17:04
openstackMeeting started Tue Nov 26 17:04:36 2013 UTC and is due to finish in 60 minutes.  The chair is ativelkov. Information about MeetBot at http://wiki.debian.org/MeetBot.17:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:04
*** openstack changes topic to " (Meeting topic: murano)"17:04
openstackThe meeting name has been set to 'murano'17:04
gokrokveHi!17:04
*** igormarnat__ has joined #openstack-meeting-alt17:04
igormarnat__Howdy17:05
brianclineadrian_otto: no doubt, my headspace is still within the existing 21 BPs as there's good foundation there that needs to be brought to life17:05
brianclineoops17:05
*** sergmelikyan has joined #openstack-meeting-alt17:05
ativelkovIt turns out we do not have any explicit agenda for today (my fault indeed - was to busy to publish it in advance)17:06
ativelkovBut let's start with AI review, as usual17:06
katyaferventYes, what's first17:07
*** lsmola has quit IRC17:07
*** stanlagun_ has joined #openstack-meeting-alt17:07
ativelkovWe planned to forward the LoadBalancer email to Neutron and Fuel team,17:08
ativelkov    asking for feedback17:08
igormarnat__Yep. Serge was in charge of this. Serge?17:08
*** markmcclain has joined #openstack-meeting-alt17:09
*** aguzikova has quit IRC17:09
sergmelikyanNot done yet :(17:10
ativelkovAny estimates?17:11
sergmelikyanWe have collected feedback from community, but not yet from Fuel team.17:11
gokrokveThis is a right time to do as they are implementing autoscaling and lb right now.17:11
sergmelikyanIt going to be done by Thurday17:11
igormarnat__Not from Neutron team as well, I guess17:11
gokrokveThursday is a holiday17:12
gokrokveeven Friday probably will be non working day17:12
sergmelikyanI will write e-mail tomorrow, and I expect that we going to collect some feedback before holidays. We already settled with implementation, AFAIK?17:13
ativelkovWell, it is settled, but if we get any feedback it may be changed17:13
igormarnat__+117:13
sergmelikyanMay be then we need to postpone implementation?17:14
sergmelikyanI had plans to begin with implementation on this week.17:15
katyaferventLet's discuss estimation17:15
ativelkovWell, if you expect it to be done soon, let's postpone it then - it should not take long17:15
sergmelikyanETA - 5-7 days with testing and etc...17:15
*** alazarev has quit IRC17:15
*** muralia has left #openstack-meeting-alt17:15
sergmelikyan(1-2 days for actual implementation)17:15
ativelkov#agreed postpone autoscaling implementation until we get actual feedback from Neutron and Fuel teams17:16
gokrokveFuel -> Heat ?17:16
ativelkovNo, fuel17:16
ativelkovwe needed some feedback from their side17:16
funzojust a note, the Neutron guys are currently meeting in #openstack-meeting and discussion data collection via ceilometer17:17
funzoassumption is this is the precursor to being able to offer autoscaling17:17
*** rakhmerov has joined #openstack-meeting-alt17:17
ativelkovfunzo: thanks17:17
sergmelikyanDue to one of the implementation strategies based on Nuutron LBaaS for which Fuel has no support at all17:17
ativelkovProbably we'll need separate discussion with them.17:19
gokrokveOk. Sergey you can work with Eugene Nikanorov. He is a part of LBaaS team, so he can probably help.17:19
igormarnat__I think it'll require some time for folks to get acquainted with the context, so let's initiate this by email.17:19
gokrokveEugene is in Saratov.17:19
ativelkovOk, let's move on17:19
ativelkovnext AI: gokrokve to summarise the decisions of Solum design workshop for further discussion of integration paths17:20
*** tsufiev_ has joined #openstack-meeting-alt17:20
gokrokveHm. Right now it is too early.17:20
tsufiev_hi there )17:21
ativelkovhi Timur17:21
*** sarob has quit IRC17:21
ativelkovgokrokve nothing to integrate with yet? )17:21
tsufiev_have i missed something important?17:21
gokrokveI am participating in mostly all Solum meeting, but right now the main focus of Solum team is to create initial design.17:21
*** sarob has joined #openstack-meeting-alt17:21
gokrokveThere are some integration points related to Windows ecosystem.17:22
*** david-lyle is now known as david-lyle_afk17:22
gokrokveSolum will be agnostic to OS.17:22
*** SergeyLukjanov has quit IRC17:23
gokrokveAnd Solum will support both VM and Container as a deployment unit.17:23
ativelkovwell, building windows-based images is a complicated stuff indeed17:23
*** SergeyLukjanov has joined #openstack-meeting-alt17:23
*** sarob_ has joined #openstack-meeting-alt17:23
gokrokveYes. There was a discussion about that in openstack-dev.17:23
*** vkozhukalov has joined #openstack-meeting-alt17:23
gokrokve[openstack-dev] [Solum] Working group on language packs17:24
ativelkov#info potential integration points with Solum related to Windows ecosystem17:24
ativelkovYes, this looks interesting17:24
ativelkovOk, then let's continue watching Solum's discussions and email distributions. We don't want to miss anything important there17:25
gokrokveI am also trying to bring more use cases for Application Catalog. We have some customers who want it.17:26
*** sarob has quit IRC17:26
gokrokveI am working with them to collect all necessary requirements.17:26
gokrokveSure. Keep an eye on Solum. This is very interesting project.17:26
*** Barker has quit IRC17:27
ativelkovYeah. But we need to make sure that our set of use-cases is generic and useful for the whole comunity: customer-specific things should not complicated the overall vision17:27
*** jcoufal has quit IRC17:27
*** eankutse1 has quit IRC17:27
gokrokveI remember that Heat team asked us about specific requirements for HOS software orchestration.17:27
gokrokveDo we have some?17:27
*** eankutse has joined #openstack-meeting-alt17:27
gokrokveHOS->HOT17:27
ativelkovstanlagun has answered to that email17:28
*** sarob_ has quit IRC17:28
gokrokveYes. But after a week, do we have more details on that. On this phase of implementation we can actually ask for some specific features.17:28
ativelkovWe don't know anything specific yet17:29
ativelkovIt completely depends on our implementation of metadata and workflow dsl17:29
ativelkovThat's actually our last AI from the last meeting17:29
gokrokveThen check software components definitions. Thay have an idea of different deployers (chef, puppet).17:29
ativelkov"tivelkov stanlagun to formalise the new metadata ideas in the etherpad"17:29
*** Barker has joined #openstack-meeting-alt17:29
*** cpallares has joined #openstack-meeting-alt17:29
*** cpallares has left #openstack-meeting-alt17:30
gokrokveAt least we can use HOT to install our agent.17:30
ativelkovThis is useful - but we need to settle the higher level first17:30
gokrokvesure.17:30
*** nadya_ has joined #openstack-meeting-alt17:30
ativelkovSo, the ether pad is not ready yet17:30
ativelkovWe are trying to come with some design proposal that would be complete and feature rich17:31
ativelkovthen we will reduce it to a subset of something easier to implement17:31
ativelkovHovever, the process turned out to be trickier then we expected17:31
*** MarkAtwood has joined #openstack-meeting-alt17:32
ativelkovAnyway, we expect it to be finished this week, so we may share the vision to others and start implementing once we get some feedback17:32
*** venkatesh has quit IRC17:32
ativelkovSo, tha't all on action items17:34
ativelkovLet's cover our other news17:34
*** nadya_ has quit IRC17:34
ativelkovsergmelikyan: what's new on release 0.3?17:34
sergmelikyanWe successfully released Murano v0.3 :)17:35
sergmelikyanWe have plans to release screencast-review with new features released with v0.317:36
gokrokvePlease work with Nick Chase on that.17:38
gokrokveHe can help you to do this in a right way.17:38
*** coolsvap_away has quit IRC17:38
sergmelikyangokrokve, Ok, but he is on vacation now17:38
ativelkov#action sergmelikyan to elaborate with Nick Chase on 0.3 screencast17:39
*** markmcclain has quit IRC17:39
*** alazarev has joined #openstack-meeting-alt17:39
*** IlyaE has joined #openstack-meeting-alt17:39
ativelkovMore news17:39
ativelkovrelease 0.4  is in progress17:40
ativelkovadvancedNetwowrking has been merged into master17:40
ativelkovexcessive testing should begin soon17:40
tnurlygayanov_do we have WebUI options for this?17:40
tsufiev_ no, we don't17:41
tsufiev_it is postponed until 0.517:41
*** FallenPegasus has joined #openstack-meeting-alt17:41
tnurlygayanov_ok, we started to test it )17:41
ativelkovAlso, we've found that there is a problem with nova-network support (https://bugs.launchpad.net/murano/+bug/1255057)17:41
ativelkovThis has just been fixed17:41
tnurlygayanov_so, how we should configure OpenStack to try this feature? How it will work with Nova network?17:43
ativelkovThere will be a configuration parameter indicating default network topology17:44
*** RoshanAgr has quit IRC17:44
*** rongze has quit IRC17:44
*** RoshanAgr has joined #openstack-meeting-alt17:44
tnurlygayanov_ok, I will test it )17:45
*** betsy has quit IRC17:45
ativelkovping me if you need more details17:46
ativelkovI think that was all for the current status17:47
ativelkovDoes anybody have something else to discuss?17:47
tnurlygayanov_ok, thank you )17:47
tnurlygayanov_yes, need to fix roadmap on the murano wiki page, we plan release Murano 0.4 in december17:48
tnurlygayanov_ou, it is already writed on wiki, ok )17:49
ativelkovOk, good catch17:49
*** rossella_s has quit IRC17:49
*** rsblendido has quit IRC17:49
ativelkovother questions?17:50
*** IlyaE has quit IRC17:50
ativelkovSeems like we are done17:51
ativelkovlets end the meeting then17:51
ativelkov#endmeeting17:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:51
openstackMeeting ended Tue Nov 26 17:51:51 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/murano/2013/murano.2013-11-26-17.04.html17:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/murano/2013/murano.2013-11-26-17.04.txt17:51
openstackLog:            http://eavesdrop.openstack.org/meetings/murano/2013/murano.2013-11-26-17.04.log.html17:51
*** tsufiev_ has quit IRC17:52
*** sarob has joined #openstack-meeting-alt17:52
*** derekh has quit IRC17:54
*** tnurlygayanov_ has quit IRC17:54
*** vipul is now known as vipul-away17:54
*** FallenPegasus has quit IRC17:56
*** twoputt has joined #openstack-meeting-alt17:58
*** twoputt_ has joined #openstack-meeting-alt17:58
*** nati_ueno has joined #openstack-meeting-alt17:58
*** nati_ueno has quit IRC17:59
*** nati_ueno has joined #openstack-meeting-alt18:00
*** sarob has quit IRC18:00
*** igormarnat__ has quit IRC18:01
*** colinmcnamara has joined #openstack-meeting-alt18:04
*** Uri__ has joined #openstack-meeting-alt18:04
*** Uri__ has quit IRC18:05
*** aguzikova has joined #openstack-meeting-alt18:12
*** DennyZhang has quit IRC18:17
*** yogesh has joined #openstack-meeting-alt18:17
*** gokrokve has quit IRC18:18
*** nadya_ has joined #openstack-meeting-alt18:18
*** gokrokve has joined #openstack-meeting-alt18:18
*** eankutse1 has joined #openstack-meeting-alt18:22
*** eankutse1 has quit IRC18:22
*** gokrokve has quit IRC18:23
*** eankutse1 has joined #openstack-meeting-alt18:23
*** boris-42 has quit IRC18:23
*** eankutse has quit IRC18:25
*** nadya_ has quit IRC18:27
*** vipul-away is now known as vipul18:29
*** IlyaE has joined #openstack-meeting-alt18:29
*** ruhe has quit IRC18:32
*** RoshanAgr has quit IRC18:35
*** ruhe has joined #openstack-meeting-alt18:35
*** SergeyLukjanov_ has joined #openstack-meeting-alt18:37
*** SergeyLukjanov has quit IRC18:37
*** ativelkov has quit IRC18:37
*** jprovazn has joined #openstack-meeting-alt18:38
*** SergeyLukjanov has joined #openstack-meeting-alt18:41
*** david-lyle_afk is now known as david-lyle18:42
*** SergeyLukjanov_ has quit IRC18:42
*** lsmola has joined #openstack-meeting-alt18:43
*** rongze has joined #openstack-meeting-alt18:44
*** RoshanAgr has joined #openstack-meeting-alt18:45
*** ccrouch has joined #openstack-meeting-alt18:46
*** yogesh has quit IRC18:47
*** tzumainn has joined #openstack-meeting-alt18:47
*** gokrokve has joined #openstack-meeting-alt18:47
*** yogesh has joined #openstack-meeting-alt18:47
*** jcoufal has joined #openstack-meeting-alt18:51
*** yogesh has quit IRC18:52
*** aguzikova has quit IRC18:53
*** rongze has quit IRC18:53
*** sarob has joined #openstack-meeting-alt18:55
*** marios has joined #openstack-meeting-alt18:55
*** rpodolyaka1 has joined #openstack-meeting-alt18:55
*** jog0 has joined #openstack-meeting-alt18:55
*** nadya_ has joined #openstack-meeting-alt18:57
*** jistr has joined #openstack-meeting-alt18:57
*** matty_dubs has joined #openstack-meeting-alt19:00
lifelessmorning19:01
lsmolahello19:01
rpodolyaka1o/19:01
dprincehi19:01
tzumainnhiya19:01
jprovaznhi19:01
matty_dubsHowdy19:01
marios\o19:01
jistrhi19:01
jcoufalo/19:01
slaglehi19:01
dkehno/19:01
lifeless#startmeeting tripleo19:02
openstackMeeting started Tue Nov 26 19:02:04 2013 UTC and is due to finish in 60 minutes.  The chair is lifeless. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
lifeless#topic agenda19:02
*** openstack changes topic to " (Meeting topic: tripleo)"19:02
openstackThe meeting name has been set to 'tripleo'19:02
*** openstack changes topic to "agenda (Meeting topic: tripleo)"19:02
lifeless     bugs19:02
lifeless    reviews19:02
lifeless    Projects needing releases19:02
lifeless    CD Cloud status19:02
lifeless    CI virtualized testing progress19:02
*** jtomasek has joined #openstack-meeting-alt19:02
lifeless    Insert one-off agenda items here19:02
lifeless    Blueprints and design planning / summit wrap-up19:02
lifeless    open discussion19:02
lifeless#topic bugs19:02
*** openstack changes topic to "bugs (Meeting topic: tripleo)"19:02
jog0o/19:02
lifeless#link https://bugs.launchpad.net/tripleo/19:02
bnemeco/19:02
lifeless#link https://bugs.launchpad.net/diskimage-builder/19:02
*** jtomasek has quit IRC19:02
lifeless#link https://bugs.launchpad.net/os-refresh-config19:02
lifeless#link https://bugs.launchpad.net/os-apply-config19:02
lifeless#link https://bugs.launchpad.net/os-collect-config19:02
lifeless#link https://bugs.launchpad.net/tuskar19:02
lifeless#link https://bugs.launchpad.net/tuskar-ui19:02
lifeless#link https://bugs.launchpad.net/python-tuskarclient19:02
*** sarob has quit IRC19:02
lifelessbug 125513119:03
*** jtomasek has joined #openstack-meeting-alt19:03
lifelessbug 125455519:03
lifelessbug 125424619:03
*** sarob has joined #openstack-meeting-alt19:03
lifelesshmm, I'm seeing a distinct lack of bots19:03
jtomasekHi19:03
lifelesshttps://bugs.launchpad.net/tripleo/+bug/125424619:03
lifelesshttps://bugs.launchpad.net/tripleo/+bug/125455519:03
lifelesshttps://bugs.launchpad.net/tripleo/+bug/125513119:04
lifelesscriticals19:04
lifelessalso https://bugs.launchpad.net/diskimage-builder/+bug/1252975 - rhel failin19:04
lifelessg in dib19:04
slaglei can fix that19:04
lifelessso everything is triaged - yay - but we've got four big issues open and being worked19:04
slaglelooks easy enough19:04
lifelessslagle: awesome19:04
lifelessnova just approved the revert to fix https://bugs.launchpad.net/tripleo/+bug/125513119:05
lifelessso that should be through soon assuming the gate gods have been appeased recently19:05
jomaraaloha19:05
lifelesswe have a workaround for https://bugs.launchpad.net/tripleo/+bug/1254555 in place, so nothing to do there except help the neutron folk as needed19:06
jog0lifeless: gate delay is ~ 2 hours right now19:06
lifelessand https://bugs.launchpad.net/tripleo/+bug/1254246 is currently not really known19:06
*** colinmcnamara has quit IRC19:06
rpodolyaka1looks like a race in neutron-server19:07
lifelessrpodolyaka1: want to poke into it ?19:08
rpodolyaka1lifeless:  sure, will ping neutron folks in mirantis too19:08
lifelessrpodolyaka1: brilliant19:08
lifeless#topic reviews19:08
*** openstack changes topic to "reviews (Meeting topic: tripleo)"19:08
lifeless     http://russellbryant.net/openstack-stats/tripleo-openreviews.html19:08
dkehnof late these are db locks19:08
lifeless    http://russellbryant.net/openstack-stats/tripleo-reviewers-30.txt19:08
lifeless    http://russellbryant.net/openstack-stats/tripleo-reviewers-90.txt19:08
lifeless19:09
lifelessStats since the last revision without -1 or -2 :19:09
lifeless    Average wait time: 0 days, 2 hours, 0 minutes19:09
lifeless    1rd quartile wait time: 0 days, 0 hours, 14 minutes19:09
lifeless    Median wait time: 0 days, 2 hours, 2 minutes19:09
lifeless    3rd quartile wait time: 0 days, 3 hours, 45 minutes19:09
lifeless^ awwwesome19:09
lifelesseither that or we're not changing nearly enough :)19:09
*** colinmcnamara has joined #openstack-meeting-alt19:09
lifelessNew patch sets in the last 30 days: 389 (13.0/day)19:09
lifelessChanges involved in the last 30 days: 210 (7.0/day)19:09
lifeless  New changes in the last 30 days: 201 (6.7/day)19:09
lifelessso - not a lack of changes, we're just on top of it. Cool.19:10
lifelessany reviews business to raise?19:10
matty_dubsWe're so good at reviews that it's almost a problem -- I had a hard time finding anything to review the other day. ;)19:10
matty_dubsGood problem to have.19:10
lsmolahehe19:10
*** nadya_ has quit IRC19:10
lifelessok, cool19:11
lifeless#topic Projects needing releases19:11
*** openstack changes topic to "Projects needing releases (Meeting topic: tripleo)"19:11
lifelessthis seems to be working well; do we have a volunteer?19:12
*** yogesh has joined #openstack-meeting-alt19:12
rpodolyaka1I'm used to doing reviews now, so it doesn't take me much time. Ill take it :)19:12
rpodolyaka1*releases19:12
lifelessrpodolyaka1: \o/19:12
lifeless#action rpodolyaka1 to release the world19:12
* rpodolyaka1 should have some sleep19:12
lifeless#topic  CD Cloud status19:12
*** openstack changes topic to "CD Cloud status (Meeting topic: tripleo)"19:13
lifelessSpamapS has been poking at this this morning and asked me to proxy for him19:13
lifeless07:23 < SpamapS> lifeless: waitcondition on nova-compute did not fix things. derekh has found a commit to19:13
lifeless                 revert which _does_ seem to fix things..19:13
lifeless07:24 < SpamapS> lifeless: https://review.openstack.org/58577 revert patch19:13
lifeless07:24 < dprince> bad nova19:13
lifeless07:24 < SpamapS> do we have a simple way to cherry pick things in tripleo-cd ?19:13
lifeless07:25 < SpamapS> lifeless: anyway, that is where we are at.19:13
lifeless07:25 < dprince> SpamapS: we actually have a mechanism to handle patches in TOCI, but not cherry picks.19:13
lifeless07:25 < SpamapS> lifeless: also I'm working on NTP because trying to debug crap with skewed clocks _SUCKS_19:13
lifeless07:26 < SpamapS> in theory setting DIB_REPOLOCATION_nova and DIB_REPOREF_nova would work19:14
lifeless07:26 < SpamapS> but my experience with those has been that they unfortunately do not work.19:14
lifeless07:26 < SpamapS> perhaps because I don't understand refs19:14
lifeless07:27 < SpamapS> anyway, have to hit the road now19:14
lifeless07:27 < SpamapS> hopefully will be back19:14
lifelessnova have approved that commit19:14
lifelessso in theory the cloud is usable again in 3h19:14
lifelessanyone else have cd-cloud info to add?19:14
lifeless#topic  CI virtualized testing progress19:15
*** openstack changes topic to "CI virtualized testing progress (Meeting topic: tripleo)"19:15
lifelesspleia2: / dprince: ^ you've been active recently on this :)19:15
dprincesome progress this week: https://review.openstack.org/#/q/status:open+project:openstack-infra/tripleo-ci,n,z19:16
pleia2got a couple more patches in last week and am now sorting out our networking strategy19:16
pleia2only broke my bridge twice last night :)19:16
lifelesspleia2: that sounds worse than I hope it is ;)19:16
dprinceThe client and worker elements are in progress. I understand we are waiting on some infra comments there.19:16
pleia2need to get dprince in the loop about our networking strategy (meeting later)19:17
lifelessdprince: we got infra comments, and I've followed up with my understanding of the implications.19:17
dprinceI'm chipping away from the top down by adding a couple heat tempaltes19:17
pleia2lifeless: not so bad, had to connect a keyboard to it ;)19:17
dprincepleia2: sounds good.19:17
lifelessdprince: we'd like a second ack from infra (well more from gear afficionados) but I think it's clear19:17
lifelessdprince: essentially clients get told about server failures, so we just arrange for two clients and two servers to form a mutual lock19:18
dprincelifeless: sounds good.19:18
dprincelifeless: I had one question about how we will manage the actual slaves. Which is will *we* actually manage them? or will infra?19:19
lifelesstripleo-cd-admins will manage them19:19
dprincelifeless/pleia2: would also like to have a meeting right after this if possible too.19:19
lifelessinfra folk are welcome to join that team of course19:19
* dprince forgot to send out an invite this week though19:19
pleia2dprince: wfm19:20
lifelessdprince: this is my morning of pain meetings wise but we'll see what we can do19:20
dprincelifeless: so will the Jenkins slave need puppet creds to install all the normal infra stuff?19:20
lifelessthe jenkins slave is spawned by nodepool19:20
lifelessthis is already in place, just in the old grizzly cloud we have19:21
lifelessoh! when you asked about slaves19:21
lifelessI thought you mean the test environment machines19:21
lifelessso - there are three things in test19:21
pleia2maybe we need a glossary of terms19:21
lifelessjenkins 'tripleo-gate' slave - infra operated19:21
lifelessgear broker - infra operated19:22
lifelesstest environment on a test environment machine - tripleo-cd-admins operated (has baremetal access)19:22
lifelessOh, I forgot two cd cloud things19:22
dprincelifeless: Right. I was asking about the jenkins node above mostly.19:22
lifelessfirstly we have ipv6 in the HP region now.19:22
lifelessit's not all configured but connectivity is there so we can use that to connect to ipv6 only regions some vendors have talked about19:23
lifelesssecondly I was curious where the RH region was at - do we have admin creds ?19:23
lifelessdprince: ^ that ones for you :)19:24
dprincelifeless: sorry, too many meetings.19:25
lifelessdprince: I know the feeling - no worries! :)19:25
dprincelifeless: SO, derekh and I should get initial access (internal) this Friday19:25
lifelessok cool19:25
lifelesswill follow up next week - note that once a single machine is up and running I think all the tripleo-cd-admins would be delighted to help with the bringup19:26
*** nati_uen_ has joined #openstack-meeting-alt19:26
dprincelifeless: So at least we'll be able to take stock of things. A week or two after that I hope the security team can work through the final details and give all the CD admins access as well.19:26
lifelesskk19:26
dprincelifeless: we are super anxious to get in there though19:26
lifelessanything else on CI testing?19:26
pleia2also worthy of note, holiday this week in US, I'm out thurs + fri19:26
lifelessdprince: yeah - let me know if the security guys want anything from me (e.g. docs/procedures etc)19:26
lifelessbut it should already be documented.19:27
lifelessdprince: where is the region located?19:27
dprincePhoenix I think.19:27
lifelesscool19:27
* dprince likes his servers hot19:27
dprinceHOT even19:27
*** eankutse1 has quit IRC19:28
*** nati_ueno has quit IRC19:28
*** igormarnat__ has joined #openstack-meeting-alt19:29
lifelessokies19:29
lifeless#topic  Blueprints and design planning / summit wrap-up19:29
*** openstack changes topic to "Blueprints and design planning / summit wrap-up (Meeting topic: tripleo)"19:29
lifelessso, I've done the boring administrivia follow-through from the HK summit19:29
*** nati_uen_ has quit IRC19:30
lifelessI *think* anyone coming and looking at blueprints will now see an accurate summation of the jointly agreed things19:30
lifelessand stuff that needs more discussion is called out19:30
tzumainnlifeless, I know that jcoufal was working on wireframes for an installer, should that be part of the summation?19:30
*** nati_ueno has joined #openstack-meeting-alt19:30
jomarait should19:31
lifelessTuskar folk: I closed a bunch of blueprints that really didn't make sense as blueprints - most of them were descriptions of defects - e.g. bugs - rather than genuine major works that need coordination and approval19:31
jistrack19:31
lifelesstzumainn: blueprints are very good at capturing, they are not good at design or evolution of ideas.19:31
lifelesstzumainn: I think we should capture stuff as blueprints that is big enough we want formal approval on it; and we should do that once the thing has been broadly discussed - the blueprint is an output, not an input.19:32
tzumainnlifeless, sure, but should it be included as part of what was discussed at summit?  I noticed that you had a line item that linked to an etherpad instead of a blueprint19:32
lifelesstzumainn: ok so:19:33
*** igormarnat__ has quit IRC19:34
lifeless - the etherpad I linked to was really not a tripleo thing to decide on; it was in our timeslot because it's important to us but all the work for it will be Ironic, so the blueprint aspects should be in Ironic19:34
tzumainnlifeless, right, I understand that - I'm just wondering if the installer could have been called out, because it's something we're actively working on for icehouse19:35
lifeless - the slick deployment of clouds through the UI story is important, and I'm happy for there to be a broad blueprint about that - I'll reply to Jaromir's mail :)19:35
jcoufallifeless: Yeah, I think, tzumainn's point is, that we want to keep on mind that this is one of our deliverables for Icehouse. We can generate blueprints once we have more details19:35
lifelessjcoufal: so I'd say -a- blueprint :)19:35
lifelessand yes, having slick install is very important19:35
lifelessbugs are super granular; blueprints are not19:36
lifeless(building analogy - this nail is not hammered in correctly - bug; the building is the wrong shape - blueprint)19:36
jcoufalok, sounds good19:36
tzumainnlifeless, yeah, jcoufal expressed my point better than I did - I was just hoping that we could build awareness that we're working on this feature19:36
lifelesstzumainn: agreed19:37
tzumainnokay, thanks for answering my question!19:37
lifelessI've actually been talking the tuskar story to nvoa folk face to face fairly often19:37
lifelesssome of the things I've been concerned about from the get go get very strong pushback19:37
lifelesslike the manual scheduling19:37
lifelessother things I thought were cool they were just plain confused about - like creation of flavors19:38
lifelessso - why don't we switch to open discussion and spend a bit of time talking through this?19:38
jcoufalsure19:38
lifelessif there's no more stuff specifically about us having blueprints etc19:38
lifeless{waits for timeout}19:38
ccrouchhttps://blueprints.launchpad.net/openstack?searchtext=tripleo19:38
ccrouchthis is list right?19:38
ccrouchpresumably there are more than two targeted for icehouse?19:39
jomaraccrouch: i think they're mislabeled; some of them actually have iCEHOUSE in the name19:40
jomara(but dont have icehouse marked as series)19:40
lifelessoh, the series field I have been ignoring19:41
lifelessthe list itself is accurate19:41
ccrouchright, so more administrivia maybe required?19:41
ccrouchlifeless: so everything approved is targetted for icehouse?19:41
lifelessccrouch: that is in a tripleo project yes19:41
lifelessI can't comment on e.g. ceilometer stuff19:42
ccrouchyep, makes sense19:42
ccrouchthis is the link thats mentioned on  https://wiki.openstack.org/wiki/TripleO so I wanted to make sure we're advertising the right stuff19:43
lifelessyup19:44
lifelessyou are19:44
lifelessnote that the blueprints isn't the complete list of what TripleO is doing19:44
lsmolalifeless, hopefully, all ceilometer stuff we need should land in I19:44
lifelesswe have the basic theme of 'drive deployments by makign the TripleOCloud better and more awesome' which gives organic structure.19:44
lifeless(recorded in the trello experiment)19:45
lifelessand we have bugs which gives lots of identified bits of individual work19:45
lifelessok19:46
lifeless#topic open discussion19:46
*** openstack changes topic to "open discussion (Meeting topic: tripleo)"19:46
*** Ng has joined #openstack-meeting-alt19:46
lifelessso design stuff around tuskar19:46
jcoufalalright just small update from my side19:46
lifelessplease!19:46
*** sarob has quit IRC19:46
jcoufalI am close to send updated story of overcloud installer.19:47
jcoufal At the moment, we are focusing on really basic stuff - register nodes (manual + autodiscover) -> assign services -> deploy.19:47
*** sarob has joined #openstack-meeting-alt19:47
jcoufalThe whole flavor creation and advanced features are pushed back a bit, in sake of slick well working basic installer.19:47
lifelesscool19:48
shadowerplus given the confusion and pushback it's better to give them space for proper design and discussion19:48
jcoufal Once we have it, we can go further and work on adding more advanced features19:48
lifelesscan we skip assign services?19:48
lifelesslike - just let nova sort it out?19:48
jcoufalto let nova sort out which services are deployed where?19:48
lifelessyeah19:49
lifelessa big chunk of the complexity in tuskar that is contentious is the way it does it's own scheduling19:49
marioslifeless: i believe referring to e.g. neutron, swift etc19:49
slagledoes assigning services require that nova patch that has been in limbo a while?19:49
marioslifeless: not nova-* services19:49
*** rongze has joined #openstack-meeting-alt19:49
slaglethe one around returning the baremetal id's19:49
lifelessmarios: ack; that was my understanding19:49
mariosslagle: that was merged afaik19:49
slagleoh, cool19:49
shadowerslagle: well I think we should just move to ironic19:49
lifelessit might be v3 only19:50
shadowerwas it?19:50
shadowerah right19:50
lifelessanyhow - focus! :)19:50
*** tomblank has left #openstack-meeting-alt19:50
jcoufallifeless: well for user it might be confusing that he can't choose which nodes are compute / controller / object or block storage19:50
lifelesspoint is, today - as I understand it - we have tuskar doing scheduling, passing to heat, which passes to nova19:50
lifelessjcoufal: It's confusing to me that user would want to choose19:50
*** tzumainn_ has joined #openstack-meeting-alt19:50
lsmolalifeless, so how will nova sort it out?19:51
jistrlsmola: +119:51
*** tzumainn has quit IRC19:51
*** sarob_ has joined #openstack-meeting-alt19:51
*** sarob has quit IRC19:51
lsmolalifeless, like I have 10 baremetal nodes I reallz need just compute power19:51
*** tzumainn_ is now known as tzumainn19:52
lifelessIn the heat template19:52
mariosslagle: shadower: https://review.openstack.org/#/c/42047 fyi19:52
lsmolalifeless, how will nova know what I need?19:52
lifelesschoose based on flavor19:52
lifelessnot on node19:52
jcoufalflavor is representing node19:52
lifelessflavor represents a collection of nodes19:52
jistrjcoufal: well, a hardware type rather than node, right?19:53
lifelessthe current TripleOCloud, for instance, has two flavors.19:53
jcoufalright19:53
lifelessone 96GB/24Cores/2TB of disk19:53
*** adrian_otto has left #openstack-meeting-alt19:53
lifelessand one 64GB/8cores/2TB disk19:53
lifelessI'm saying that rather than poking under the hood at the list of nodes19:53
*** rongze has quit IRC19:54
jcoufalI still see odd why I cannot control where my stuff goes...19:54
shadowerlifeless: how do these work in the BM sense? Are they autodiscovered or do you assign a flavour to each node when you register it?19:54
lifelessjust say 'compute can run on flavors X,Y,Z' 'network on flavors X,Y' etc19:54
lsmolalifeless, hmm19:54
jcoufalwell yes, but this is advanced approach19:54
jcoufalwhy don't we start with basics?19:54
lifelessjcoufal: So this is the disconnect I think. If you have 7 machines you can pay attention to such detail. You cannot when you have 7000.19:55
jcoufallifeless: agree with you. But, we want to have basics done first19:55
lifelessshadower: baremetal flavor setup is something we could in principle automate. But it's undercloud config and the story being discussed is overcloud install :)19:55
lsmolalifeless, well true, we had resource clasess for that19:55
*** sarob_ has quit IRC19:55
lsmolalifeless, now I see that flavor is resource class19:56
lifelessjcoufal: ok, so my point is that you need to write /more/ code to do node level stuff19:56
lifelessjcoufal: because you have to write a topology generator.19:56
lifelessjcoufal: maybe if we step back to even more basic. And say V0: support just one baremetal flavor.19:56
*** aratim1 has joined #openstack-meeting-alt19:56
lifelessjcoufal: so the inputs to the UI become: you have N machines, we are doing to install a cloud for you. Click here to install.19:57
marioslifeless: so that assumes just one service type, compute (to start with)19:57
lifelessjcoufal: we can say if N==1 then its an all in one cloud. If N==2 it's control + hypervisor.19:57
lifelessmarios: no, not at all. ^19:58
*** aratim1 has quit IRC19:58
marioslifeless: i'm equating one baremetal flavor to one service19:58
lifelessmarios: nope.19:58
lifelessmarios: it just means there is one type of hardware.19:58
lifelessmarios: consider the test rack RH had at the summit (which was AWESOME)19:58
*** twoputt_ has quit IRC19:58
*** twoputt has quit IRC19:58
jcoufalwell, but user needs to define the flavors anyway, it's not that he comes to UI and says - install me anything19:58
lifelessmarios: it had - as far as I know - exactly one hardware config in the entire rack.19:58
lifelessjcoufal: thats true, but even so - if the rack is like the one at the summit, its one flavor.19:59
lifelesswouldn't truely basic be the ability to install into that rack ?19:59
*** aratim has quit IRC19:59
lifelessok, we're out of time here - but #tripleo is still open, and if it's not too late inyour evening I think this is a good conversation to keep rolling with.20:00
lifeless#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Nov 26 20:00:37 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tripleo/2013/tripleo.2013-11-26-19.02.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tripleo/2013/tripleo.2013-11-26-19.02.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tripleo/2013/tripleo.2013-11-26-19.02.log.html20:00
*** rpodolyaka1 has left #openstack-meeting-alt20:00
*** Ng has left #openstack-meeting-alt20:01
jcoufalo/20:01
jcoufalc'ya in #tripleo20:01
*** colinmcnamara has quit IRC20:01
*** matty_dubs has left #openstack-meeting-alt20:02
*** colinmcnamara has joined #openstack-meeting-alt20:03
*** tzumainn has left #openstack-meeting-alt20:05
*** derekh has joined #openstack-meeting-alt20:05
*** ccrouch has left #openstack-meeting-alt20:05
*** vipul is now known as vipul-away20:14
*** vipul-away is now known as vipul20:14
*** julim has quit IRC20:17
*** sarob has joined #openstack-meeting-alt20:18
*** tdeckers has left #openstack-meeting-alt20:18
*** nati_uen_ has joined #openstack-meeting-alt20:18
*** aratim has joined #openstack-meeting-alt20:20
*** nati_ueno has quit IRC20:21
*** hub_cap is now known as pub_tap20:25
*** denis_makogon_ has joined #openstack-meeting-alt20:34
*** denis_makogon has quit IRC20:41
*** denis_makogon_ is now known as denis_makogon20:41
*** vipul is now known as vipul-away20:41
*** dmakogon_ has joined #openstack-meeting-alt20:41
*** yogesh has quit IRC20:43
*** dprince has quit IRC20:43
*** yogesh has joined #openstack-meeting-alt20:43
*** dhellmann-afk is now known as dhellmann20:44
*** DennyZhang has joined #openstack-meeting-alt20:45
*** aratim has quit IRC20:47
*** yogesh has quit IRC20:48
*** jistr has quit IRC20:49
*** aratim has joined #openstack-meeting-alt20:49
*** rongze has joined #openstack-meeting-alt20:50
*** sarob has quit IRC20:50
*** rongze has quit IRC20:56
*** jcoufal has quit IRC20:57
*** betsy has joined #openstack-meeting-alt20:58
*** eankutse has joined #openstack-meeting-alt21:02
*** boris-42 has joined #openstack-meeting-alt21:03
*** RoshanAgr has quit IRC21:04
*** sarob has joined #openstack-meeting-alt21:05
*** vipul-away is now known as vipul21:05
*** yogesh has joined #openstack-meeting-alt21:06
*** rakhmerov has quit IRC21:07
*** banix has quit IRC21:09
*** jog0 has left #openstack-meeting-alt21:13
*** sarob has quit IRC21:22
*** sarob has joined #openstack-meeting-alt21:26
*** julim has joined #openstack-meeting-alt21:26
*** banix has joined #openstack-meeting-alt21:31
*** rnirmal has quit IRC21:31
*** devlaps has joined #openstack-meeting-alt21:35
*** yamahata_ has joined #openstack-meeting-alt21:36
*** banix has quit IRC21:37
*** rakhmerov has joined #openstack-meeting-alt21:38
*** SlickNik has left #openstack-meeting-alt21:39
*** aratim1 has joined #openstack-meeting-alt21:40
*** jprovazn has quit IRC21:42
*** aratim has quit IRC21:43
*** rakhmerov has quit IRC21:48
*** vkozhukalov has quit IRC21:52
*** rongze has joined #openstack-meeting-alt21:52
*** rongze has quit IRC21:59
*** DennyZhang has quit IRC22:00
*** yamahata_ has quit IRC22:00
*** pub_tap is now known as hub_cap22:01
*** twoputt has joined #openstack-meeting-alt22:02
*** twoputt_ has joined #openstack-meeting-alt22:02
*** derekh has quit IRC22:04
*** pdmars has quit IRC22:05
*** aratim1 has quit IRC22:07
*** IlyaE has quit IRC22:07
*** aratim has joined #openstack-meeting-alt22:08
*** ruhe has quit IRC22:08
*** IlyaE has joined #openstack-meeting-alt22:09
*** yamahata_ has joined #openstack-meeting-alt22:14
*** IlyaE has quit IRC22:16
*** banix has joined #openstack-meeting-alt22:20
*** eankutse has quit IRC22:21
*** vipul is now known as vipul-away22:22
*** vipul-away is now known as vipul22:22
*** SergeyLukjanov has quit IRC22:25
*** Barker has quit IRC22:26
*** amcrn has joined #openstack-meeting-alt22:32
*** yamahata_ has quit IRC22:38
*** aratim has quit IRC22:39
*** aratim has joined #openstack-meeting-alt22:42
*** rakhmerov has joined #openstack-meeting-alt22:43
*** kevinconway has quit IRC22:43
*** rongze has joined #openstack-meeting-alt22:55
*** ashaikh has quit IRC22:55
*** denis_makogon has quit IRC22:56
*** stanlagun_ has quit IRC22:56
*** yamahata_ has joined #openstack-meeting-alt22:57
*** jcooley_ has joined #openstack-meeting-alt22:58
*** jmontemayor has quit IRC22:59
*** rongze has quit IRC22:59
*** lsmola has quit IRC23:06
*** yogesh has quit IRC23:08
*** jtomasek has quit IRC23:08
*** yogesh has joined #openstack-meeting-alt23:08
*** amotoki has quit IRC23:09
*** pcm_ has quit IRC23:10
*** gokrokve has quit IRC23:12
*** gokrokve has joined #openstack-meeting-alt23:12
*** gokrokve has quit IRC23:12
*** yogesh has quit IRC23:13
*** julim has quit IRC23:16
*** amytron has quit IRC23:16
*** banix has quit IRC23:17
*** rakhmerov has quit IRC23:17
*** eharney has quit IRC23:18
*** aratim has quit IRC23:19
*** devkulkarni has quit IRC23:19
*** aratim has joined #openstack-meeting-alt23:19
*** yamahata_ has quit IRC23:20
*** claytonc has quit IRC23:24
*** aratim has quit IRC23:24
*** sacharya has quit IRC23:30
*** boris-42 has quit IRC23:32
*** vipul has quit IRC23:43
*** vipul has joined #openstack-meeting-alt23:44
*** vkmc has quit IRC23:45
*** eankutse has joined #openstack-meeting-alt23:47
*** MarkAtwood has quit IRC23:54
*** rongze has joined #openstack-meeting-alt23:56
*** jcooley_ has quit IRC23:56

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