Tuesday, 2014-03-04

*** zns has quit IRC00:04
*** jmontemayor has quit IRC00:04
*** jcooley_ has quit IRC00:04
*** jcooley_ has joined #openstack-meeting-alt00:05
*** SheenaG_ has joined #openstack-meeting-alt00:06
*** samstav has quit IRC00:12
*** doug_shelley66 has quit IRC00:13
*** samstav has joined #openstack-meeting-alt00:14
*** colinmcnamara has joined #openstack-meeting-alt00:14
*** julim has quit IRC00:14
*** sc68cal has quit IRC00:15
*** malini has joined #openstack-meeting-alt00:15
*** chadlung has quit IRC00:17
*** sc68cal has joined #openstack-meeting-alt00:18
*** caleb_ has quit IRC00:21
*** hockeynut has quit IRC00:25
*** rwsu has quit IRC00:27
*** woodster1 has quit IRC00:28
*** xuhanp has joined #openstack-meeting-alt00:28
*** jcoufal has quit IRC00:29
*** rwsu has joined #openstack-meeting-alt00:30
*** amotoki has quit IRC00:30
*** cjellick has quit IRC00:32
*** jdob has quit IRC00:34
*** jdob has joined #openstack-meeting-alt00:35
*** jdob has quit IRC00:40
*** troytoman is now known as troytoman-away00:41
*** dhellmann is now known as dhellmann_00:43
*** lisaclark1 has joined #openstack-meeting-alt00:45
*** ramashri has joined #openstack-meeting-alt00:46
*** atiwari has quit IRC00:46
*** nati_ueno has joined #openstack-meeting-alt00:46
*** mattgriffin has joined #openstack-meeting-alt00:47
*** eankutse1 has joined #openstack-meeting-alt00:49
*** nati_uen_ has quit IRC00:49
*** troytoman-away is now known as troytoman00:50
*** nati_ueno has quit IRC00:51
*** richm has quit IRC00:52
*** eankutse has quit IRC00:52
*** eankutse1 has quit IRC00:53
*** troytoman is now known as troytoman-away00:55
*** flwang has quit IRC00:56
*** nati_ueno has joined #openstack-meeting-alt00:57
*** michael-yu has quit IRC00:58
*** xuhanp has quit IRC01:00
*** matjazp has joined #openstack-meeting-alt01:00
*** cody-somerville has quit IRC01:02
*** cjellick has joined #openstack-meeting-alt01:02
*** matjazp has quit IRC01:04
*** malini has quit IRC01:06
*** nati_ueno has quit IRC01:09
*** nati_ueno has joined #openstack-meeting-alt01:10
*** nati_ueno has quit IRC01:10
*** nati_ueno has joined #openstack-meeting-alt01:11
*** nati_ueno has quit IRC01:12
*** nati_ueno has joined #openstack-meeting-alt01:12
*** dane_leblanc has quit IRC01:13
*** jcoufal has joined #openstack-meeting-alt01:14
*** nati_ueno has quit IRC01:14
*** nati_ueno has joined #openstack-meeting-alt01:15
*** cjellick has quit IRC01:15
*** jcoufal has quit IRC01:15
*** nati_ueno has quit IRC01:16
*** nati_ueno has joined #openstack-meeting-alt01:16
*** mattgriffin has quit IRC01:17
*** ramashri has quit IRC01:17
*** nati_ueno has quit IRC01:17
*** bill_az has quit IRC01:17
*** rwsu has quit IRC01:17
*** nati_ueno has joined #openstack-meeting-alt01:17
*** nati_ueno has quit IRC01:18
*** nati_ueno has joined #openstack-meeting-alt01:19
*** slagle has quit IRC01:20
*** nati_ueno has quit IRC01:22
*** nati_ueno has joined #openstack-meeting-alt01:22
*** nati_ueno has quit IRC01:23
*** nati_ueno has joined #openstack-meeting-alt01:23
*** michael-yu has joined #openstack-meeting-alt01:24
*** nati_ueno has quit IRC01:24
*** nati_ueno has joined #openstack-meeting-alt01:25
*** dprince has quit IRC01:25
*** nati_ueno has quit IRC01:26
*** nati_ueno has joined #openstack-meeting-alt01:26
*** nati_uen_ has joined #openstack-meeting-alt01:27
*** nati_ueno has quit IRC01:27
*** alazarev has quit IRC01:28
*** nati_uen_ has quit IRC01:28
*** michael-yu has quit IRC01:28
*** nosnos has joined #openstack-meeting-alt01:29
*** nati_ueno has joined #openstack-meeting-alt01:29
*** alazarev has joined #openstack-meeting-alt01:30
*** nati_ueno has quit IRC01:30
*** derekh has quit IRC01:30
*** alazarev has quit IRC01:30
*** nati_ueno has joined #openstack-meeting-alt01:30
*** michael-yu has joined #openstack-meeting-alt01:30
*** nati_ueno has quit IRC01:31
*** nati_ueno has joined #openstack-meeting-alt01:31
*** nati_ueno has quit IRC01:32
*** michael-yu has quit IRC01:36
*** SheenaG_ has left #openstack-meeting-alt01:37
*** colinmcnamara has quit IRC01:37
*** garyduan has joined #openstack-meeting-alt01:39
*** xuhanp has joined #openstack-meeting-alt01:39
*** dane_leblanc has joined #openstack-meeting-alt01:44
*** lisaclark1 has quit IRC01:45
*** alazarev has joined #openstack-meeting-alt01:47
*** jcooley_ has quit IRC01:49
*** noslzzp has joined #openstack-meeting-alt01:49
*** jcooley_ has joined #openstack-meeting-alt01:49
*** lisaclark1 has joined #openstack-meeting-alt01:52
*** colinmcnamara has joined #openstack-meeting-alt01:53
*** jcooley_ has quit IRC01:53
*** amcrn has quit IRC01:55
*** bdpayne has quit IRC01:55
*** jcooley_ has joined #openstack-meeting-alt01:56
*** michael-yu has joined #openstack-meeting-alt01:58
*** michael-yu has quit IRC02:00
*** matjazp has joined #openstack-meeting-alt02:01
*** jcooley_ has quit IRC02:02
*** dane_leblanc has quit IRC02:02
*** matjazp has quit IRC02:05
*** jcooley_ has joined #openstack-meeting-alt02:07
*** jcooley_ has quit IRC02:08
*** doug_shelley66 has joined #openstack-meeting-alt02:12
*** jcooley_ has joined #openstack-meeting-alt02:13
*** jcooley_ has quit IRC02:13
*** slagle has joined #openstack-meeting-alt02:14
*** Leonr has joined #openstack-meeting-alt02:14
*** banix has joined #openstack-meeting-alt02:14
*** colinmcnamara has quit IRC02:24
*** jcooley_ has joined #openstack-meeting-alt02:26
*** jcooley_ has quit IRC02:26
*** mandeep has joined #openstack-meeting-alt02:28
*** mandeep has left #openstack-meeting-alt02:29
*** gokrokve has quit IRC02:30
*** khyati has quit IRC02:31
*** samstav has quit IRC02:32
*** lisaclark1 has quit IRC02:32
*** yamahata has quit IRC02:36
*** mattgriffin has joined #openstack-meeting-alt02:37
*** sparkycollier has joined #openstack-meeting-alt02:42
*** flwang has joined #openstack-meeting-alt02:47
*** mandeep has joined #openstack-meeting-alt02:48
*** mandeep has quit IRC02:56
*** amotoki has joined #openstack-meeting-alt02:58
*** nati_ueno has joined #openstack-meeting-alt02:59
*** nati_ueno has quit IRC02:59
*** matjazp has joined #openstack-meeting-alt03:02
*** sparkycollier has quit IRC03:03
*** sparkycollier has joined #openstack-meeting-alt03:04
*** doug_shelley66 has quit IRC03:05
*** jecarey has joined #openstack-meeting-alt03:06
*** matjazp has quit IRC03:06
*** amcrn has joined #openstack-meeting-alt03:08
*** Haiying has joined #openstack-meeting-alt03:08
*** sparkycollier has quit IRC03:10
*** sparkycollier has joined #openstack-meeting-alt03:12
*** yamahata has joined #openstack-meeting-alt03:22
*** gokrokve has joined #openstack-meeting-alt03:27
*** khyati has joined #openstack-meeting-alt03:29
*** sparkycollier has quit IRC03:31
*** khyati has quit IRC03:32
*** SumitNaiksatam has joined #openstack-meeting-alt03:32
*** woodster1 has joined #openstack-meeting-alt03:35
*** akuznetsov has quit IRC03:36
*** chandan_kumar has joined #openstack-meeting-alt03:37
*** annegentle has quit IRC03:42
*** michael-yu has joined #openstack-meeting-alt03:44
*** michael-yu has quit IRC03:47
*** Leonr has quit IRC03:52
*** malini has joined #openstack-meeting-alt03:56
*** arnaud has quit IRC04:01
*** khyati has joined #openstack-meeting-alt04:02
*** matjazp has joined #openstack-meeting-alt04:02
*** alazarev has quit IRC04:06
*** matjazp has quit IRC04:07
*** sc68cal has quit IRC04:17
*** Haiying has quit IRC04:20
*** Haiying has joined #openstack-meeting-alt04:20
*** sc68cal has joined #openstack-meeting-alt04:20
*** akuznetsov has joined #openstack-meeting-alt04:26
*** harlowja is now known as harlowja_away04:30
*** harlowja_away is now known as harlowja04:35
*** jcooley_ has joined #openstack-meeting-alt04:37
*** slagle has quit IRC04:38
*** malini has quit IRC04:41
*** Haiying has quit IRC04:43
*** akuznetsov has quit IRC04:45
*** nati_ueno has joined #openstack-meeting-alt04:45
*** _nadya_ has joined #openstack-meeting-alt04:46
*** slagle has joined #openstack-meeting-alt04:49
*** akuznetsov has joined #openstack-meeting-alt04:51
*** banix has quit IRC04:52
*** jecarey has quit IRC04:52
*** chandan_kumar has quit IRC04:53
*** jjmb1 has joined #openstack-meeting-alt04:54
*** jjmb has quit IRC04:54
*** michael-yu has joined #openstack-meeting-alt04:56
*** slagle has quit IRC04:57
*** akuznetsov has quit IRC05:01
*** jcooley_ has quit IRC05:02
*** slagle has joined #openstack-meeting-alt05:03
*** matjazp has joined #openstack-meeting-alt05:03
*** matjazp_ has joined #openstack-meeting-alt05:05
*** matjazp has quit IRC05:07
*** alazarev has joined #openstack-meeting-alt05:09
*** matjazp_ has quit IRC05:09
*** michael-yu has quit IRC05:12
*** jecarey has joined #openstack-meeting-alt05:14
*** akuznetsov has joined #openstack-meeting-alt05:15
*** _nadya_ has quit IRC05:21
*** akuznetsov has quit IRC05:29
*** banix has joined #openstack-meeting-alt05:29
*** shakayumi has joined #openstack-meeting-alt05:30
*** jcooley_ has joined #openstack-meeting-alt05:36
*** gokrokve has quit IRC05:38
*** gokrokve has joined #openstack-meeting-alt05:39
*** banix has quit IRC05:41
*** noslzzp has quit IRC05:43
*** gokrokve has quit IRC05:43
*** noslzzp has joined #openstack-meeting-alt05:43
*** zhiyan_ is now known as zhiyan05:44
*** noslzzp has quit IRC05:49
*** jecarey has quit IRC05:52
*** alazarev has quit IRC05:52
*** banix has joined #openstack-meeting-alt06:06
*** matjazp has joined #openstack-meeting-alt06:06
*** matjazp has quit IRC06:10
*** amcrn has quit IRC06:13
*** matjazp has joined #openstack-meeting-alt06:14
*** harlowja is now known as harlowja_away06:16
*** _nadya_ has joined #openstack-meeting-alt06:16
*** doug_shelley66 has joined #openstack-meeting-alt06:21
*** _nadya_ has quit IRC06:23
*** gokrokve has joined #openstack-meeting-alt06:27
*** gokrokve_ has joined #openstack-meeting-alt06:29
*** bdpayne has joined #openstack-meeting-alt06:30
*** gokrokve has quit IRC06:31
*** mandeep has joined #openstack-meeting-alt06:33
*** mandeep has quit IRC06:34
*** gyee has quit IRC06:34
*** matjazp has quit IRC06:35
*** alazarev has joined #openstack-meeting-alt06:37
*** mattgriffin has quit IRC06:38
*** denis_makogon has joined #openstack-meeting-alt06:46
*** yogesh has joined #openstack-meeting-alt06:47
*** khyati has quit IRC06:48
*** bdpayne has quit IRC06:50
*** yogesh has quit IRC06:55
*** flwang has quit IRC06:58
*** alazarev has quit IRC07:04
*** saju_m has joined #openstack-meeting-alt07:12
*** flwang has joined #openstack-meeting-alt07:17
*** woodster1 has quit IRC07:17
*** lsmola has joined #openstack-meeting-alt07:23
*** nosnos has quit IRC07:31
*** nosnos_ has joined #openstack-meeting-alt07:31
*** slagle has quit IRC07:31
*** banix has quit IRC07:35
*** matjazp has joined #openstack-meeting-alt07:39
*** mozawa has joined #openstack-meeting-alt07:41
*** amotoki has quit IRC07:47
*** yogesh has joined #openstack-meeting-alt07:52
*** flaper87|afk is now known as flaper8707:58
*** luqas has joined #openstack-meeting-alt08:03
*** nosnos_ has quit IRC08:04
*** nosnos has joined #openstack-meeting-alt08:04
*** safchain has joined #openstack-meeting-alt08:09
*** matjazp has quit IRC08:15
*** matjazp has joined #openstack-meeting-alt08:24
*** saju_m has quit IRC08:26
*** julienvey_ has joined #openstack-meeting-alt08:28
*** yogesh_ has joined #openstack-meeting-alt08:30
*** yogesh has quit IRC08:32
*** flaper87|afk has joined #openstack-meeting-alt08:35
*** jgallard has joined #openstack-meeting-alt08:41
*** denis_makogon has quit IRC08:47
*** flaper87|afk has quit IRC08:50
*** flwang has quit IRC08:54
*** flwang has joined #openstack-meeting-alt09:00
*** jjmb1 has quit IRC09:02
*** arborism has joined #openstack-meeting-alt09:04
*** arborism is now known as amcrn09:07
*** sballe has quit IRC09:08
*** sballe has joined #openstack-meeting-alt09:08
*** yogesh_ has quit IRC09:08
*** jjmb has joined #openstack-meeting-alt09:10
*** matjazp has quit IRC09:14
*** sballe has quit IRC09:17
*** matjazp has joined #openstack-meeting-alt09:23
*** flwang has quit IRC09:24
*** _nadya_ has joined #openstack-meeting-alt09:24
*** johnthetubaguy has joined #openstack-meeting-alt09:26
*** johnthetubaguy1 has joined #openstack-meeting-alt09:28
*** johnthetubaguy has quit IRC09:28
*** nacim has joined #openstack-meeting-alt09:28
*** _nadya_ has quit IRC09:30
*** akuznetsov has joined #openstack-meeting-alt09:33
*** matjazp has quit IRC09:35
*** mozawa has quit IRC09:38
*** xuhanp has quit IRC09:39
*** matjazp has joined #openstack-meeting-alt09:39
*** luqas has quit IRC09:40
*** dmakogon_ is now known as denis_makogon09:40
*** saju_m has joined #openstack-meeting-alt09:42
*** krtaylor has quit IRC09:44
*** luqas has joined #openstack-meeting-alt09:44
*** luqas has quit IRC09:58
*** shakayumi has quit IRC10:07
*** aedocw has quit IRC10:09
*** nati_ueno has quit IRC10:12
*** yamahata has quit IRC10:18
*** matjazp has quit IRC10:28
*** luqas has joined #openstack-meeting-alt10:45
*** flwang has joined #openstack-meeting-alt10:47
*** ramashri has joined #openstack-meeting-alt10:54
*** amcrn has quit IRC11:04
*** jgallard has quit IRC11:05
*** _nadya_ has joined #openstack-meeting-alt11:09
*** Ranjitha has joined #openstack-meeting-alt11:12
*** yamahata has joined #openstack-meeting-alt11:12
*** ramashri has quit IRC11:13
*** amcrn has joined #openstack-meeting-alt11:13
*** Ranjitha has quit IRC11:16
*** Ranjitha_ has joined #openstack-meeting-alt11:16
*** yamahata has quit IRC11:16
*** jjmb has quit IRC11:20
*** hgedikli_ has joined #openstack-meeting-alt11:31
*** johnthetubaguy1 has quit IRC11:32
*** hgedikli has quit IRC11:35
*** julienvey_ has quit IRC11:41
*** _nadya_ has quit IRC11:50
*** yamahata has joined #openstack-meeting-alt11:50
*** balajiiyer has joined #openstack-meeting-alt11:50
*** hgedikli has joined #openstack-meeting-alt11:52
*** VINOD has joined #openstack-meeting-alt11:55
*** heyongli has joined #openstack-meeting-alt11:59
*** _nadya_ has joined #openstack-meeting-alt11:59
*** _nadya_ has quit IRC12:04
*** ekarlso has quit IRC12:09
*** aedocw has joined #openstack-meeting-alt12:09
*** yamahata has quit IRC12:10
*** vkmc has joined #openstack-meeting-alt12:18
*** vkmc has joined #openstack-meeting-alt12:18
*** balajiiyer has quit IRC12:21
*** slagle has joined #openstack-meeting-alt12:23
*** _nadya_ has joined #openstack-meeting-alt12:25
*** luqas has quit IRC12:26
*** _nadya_ has quit IRC12:31
*** julienvey_ has joined #openstack-meeting-alt12:35
*** david-lyle has quit IRC12:39
*** saju_m has quit IRC12:40
*** mwagner_lap has quit IRC12:40
*** zhiyan has left #openstack-meeting-alt12:43
*** irenab has joined #openstack-meeting-alt12:43
*** zhiyan has joined #openstack-meeting-alt12:43
*** _nadya_ has joined #openstack-meeting-alt12:50
*** saju_m has joined #openstack-meeting-alt12:52
*** pdmars has joined #openstack-meeting-alt13:01
*** pdmars has quit IRC13:01
*** sadasu has joined #openstack-meeting-alt13:01
sadasuhi13:01
heyonglihello13:01
irenabhi13:02
*** pdmars has joined #openstack-meeting-alt13:02
*** _nadya_ has quit IRC13:02
*** markmcclain has joined #openstack-meeting-alt13:03
sadasuHi Irena13:03
irenabHi, soory I didn'y have much progress with generic PCI MD, had crazy week with other tasks13:04
irenabI hpe to be back on this starting tomorrow13:04
sadasuI am finally at the point where I can start working on the SriovMechanismDriverBase/Mixin class13:04
*** baoli has joined #openstack-meeting-alt13:04
*** xuhanp has joined #openstack-meeting-alt13:04
*** saju_m has quit IRC13:04
baoli#startmeeting PCI Passthrough13:04
openstackMeeting started Tue Mar  4 13:04:46 2014 UTC and is due to finish in 60 minutes.  The chair is baoli. Information about MeetBot at http://wiki.debian.org/MeetBot.13:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:04
*** openstack changes topic to " (Meeting topic: PCI Passthrough)"13:04
openstackThe meeting name has been set to 'pci_passthrough'13:04
baoliHi13:04
sadasuwhat generic pci md?13:05
irenabhi13:05
baolisorry for being late. My neighbor happens to be at my doorstep13:05
irenabsadasu: the one you call SriovMechanismDriverBase13:05
sadasuok :-)13:05
sadasusame here...but I have time now, and I was going to volunteer13:05
irenabbaoli: thank you for putting info on wiki13:05
baoliirenab, np13:06
sadasudo u already have BP for that...if so sorry I missed it13:06
*** _nadya_ has joined #openstack-meeting-alt13:06
baoliAre you guys talking about the MD Base for SRIOV?13:06
sadasubaoli: yes13:06
irenabI have this one ml2-sriov-nic-switch13:06
irenaband thought to do it as part of it13:06
sadasuok..13:07
irenabwe have bp opened by baoli, it can land there if need some neutral pace :-)13:07
sadasuis ml2-sriov-nic-switch originally intended for your mech driver?13:08
irenabhttps://blueprints.launchpad.net/neutron/+spec/pci-passthrough-sriov13:08
baoliirenab, I think that it deserves a separate BP. Yours and Sandy's are focusing on the vendor MD.13:08
*** _nadya_ has quit IRC13:08
irenabbaoli: agree, it can be implemented on the one I posted before13:08
baoliirenab, that's great.13:09
irenabsadasu: yes, it is intended for next gen of our solution. The original Mlnx_MD hopefully will be merged in comming days13:09
sadasuirenab, ok got it13:09
sadasubaoli's existing BP seems to be a better place13:10
irenabsadasu: I think I have in mind what is needed, we can chat if you like13:10
irenabso agreed, doing it on baoli's bp13:10
sadasuyes, I had sent email to list after last meeting, do we continue there or another IRC?13:11
*** dhellmann_ is now known as dhellmann13:11
irenabsadasu: seems that we are the only one who answer there, so we can chat on neutron channel incase there will be more interest and maybe send update on the list13:11
sadasuirenab, sounds good13:12
heyonglihi baoli,  how about yours nova side work?13:12
baoliheyongli, Hi13:12
baoliYongli, Did you see my response to your comments?13:13
heyongliyeah13:13
heyonglii hope you try another patch set as base, that's work,  maybe the interface to sriov part is little diffrent13:14
*** BrianB_ has joined #openstack-meeting-alt13:15
baoliDo you mean your patch?13:15
heyonglior, you can just drop my last patch and use you interface implement13:15
irenabbaoli, heyongli: I wanted to ask general question13:16
heyongliplease13:16
baoliirenab, go ahead13:16
*** luqas has joined #openstack-meeting-alt13:17
irenabbaoli, seems you are pushing all in one commit changes and heyongly pushes many small commits13:17
*** flaper87 has quit IRC13:17
*** flaper87 has joined #openstack-meeting-alt13:17
irenabwhat is the best handled by nova cores?13:17
*** sadasu has quit IRC13:18
*** sadasu has joined #openstack-meeting-alt13:18
*** baoli has quit IRC13:18
*** baoli has joined #openstack-meeting-alt13:18
*** BrianB_ has quit IRC13:18
*** BrianB_ has joined #openstack-meeting-alt13:18
*** jecarey has joined #openstack-meeting-alt13:18
irenabany reviews done?13:18
heyonglismall is good, for easy review13:18
heyongliwhat do you mean/13:18
irenabcurrently we need this code to be accepted, wa tis the best way to push it13:19
heyonglismaller patch make it easy for review to catch up our idea i think13:19
irenabalos need to be sure work is done, not duplicated and no conflicts13:19
heyongliyeah, i also worry this13:20
baoliIrenab, please see the response I put in the bug review: https://review.openstack.org/#/c/67500/13:20
heyonglinow baoli given all in one solution had some duplicated function13:20
heyonglihttps://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/pci-extra-info,n,z13:21
heyongliyunhong and my patch set is here13:21
irenabOk. maybe just need to update on wiki what patches are required13:22
heyonglibaoli, i think  you can depnd on our patch except the "pci request mark interface", your patch is work , that's cool13:22
baoliyongli, I'll take a look at your patch again once I have a chance. The duplication is minimal. And as I have indicated in my response, the two routines are used in different places13:23
*** lsmola has quit IRC13:23
*** markmcclain has quit IRC13:23
irenabI should get equipment in comming days and want to try all the patches together, just want to be sure what to apply13:23
*** ekarlso has joined #openstack-meeting-alt13:23
heyonglii know , if you want merge to nova ,then the match spec is dup13:23
sadasuyou mean https://review.openstack.org/#/c/57859/?13:24
sadasudup of what?13:24
irenabbaoli: is there anything that prevent further work on your patch?13:25
heyonglinot 5785913:25
baoliYongli, I gave comments to  your patch a while back and didn't see response.13:26
heyonglii mean baoli's  nova side patch set for basic sriov suport, https://review.openstack.org/#/c/67500/13:26
heyonglibaoli, i'm sorry, i check it but which patch?13:27
baoliirenab, can you clarify your question?13:27
baoliyongli, the same patch13:27
baoliLet me repeat what I did in my patch:13:28
heyonglito my patch set?13:28
baoliheyongli, yes13:28
baoliSo give me one minute13:28
irenabbaoli: wanted to ask if there is some disagreements of nova guys on your patch, I see it in your response comment13:28
irenab"But it also depends on the community consensus on how it should be implemented eventually"13:29
baoliIrenab, as you know, we didn't actually reach agreement.13:29
heyongli13:29
heyongliBaodong (Robert) LiFeb 713:29
heyongliPlease specify how this is done. In this wiki:https://wiki.openstack.org/wiki/PCI_passthrough_SRIOV_support_Icehouse, it indicates that the existing PCI alias will be extended. For neutron SRIOV, we need to tag networking sriov ports with the attribute "net-group" (or whatever name we can agree on), and stats report for these ports is based on that.13:29
heyongliThis patch doesn't seem to reflect the wiki and support the neutron sriov requirement.13:29
irenabbaoli: so the question is, how to proceed here13:30
heyongliyour concern of this  is solved by https://review.openstack.org/#/c/74633/13:30
baoliSo this patch is based on the wiki https://wiki.openstack.org/wiki/Nova-neutron-sriov that we have discussed and agreed, and a few things that I have asked to Yongli and Yunhong, plus some fixes to the existing code13:31
heyongliyunhong write this, i foget to reply you done13:31
baoliAnd I think that you and sadasu would need something soon. That's why I put all them together13:32
irenabbaoli: agree and appreciate, but this is to POC13:33
irenabwhat about production version and plan for Juno13:33
irenab?13:33
*** sballe has joined #openstack-meeting-alt13:33
baoliIrenab, as you have seen from the meeting wiki, I put the recap of discussion over there13:34
baoliSo what's for juno is something for discussion13:34
baoliAs you know, the nova side of things are not approved for Icehouse13:34
irenabbaoli: It is very helpfull. What wil be the next step once we review and add/comment?13:35
irenabI think we need to make it some sort of proposal with options, share with community. What do you think?13:35
baoliIrenab, I'd recommend that you use the patch for testing because it works13:36
*** dhellmann is now known as dhellmann_13:36
*** lsmola has joined #openstack-meeting-alt13:36
baoliAs for the next step, we said that we are going to plan for a session in the summit13:36
irenabbaoli: thanks, will  do so13:36
irenabI just thought we already doing it :-)13:37
baoliIrenab, any comments about the Recap I put in the wiki?13:38
irenabneed to read it more carefully, will send comments later13:38
baoliIrenab, thanks13:39
irenabI saw some mails on neutron flavors for services13:39
irenabI think we probably need to initiate something similar for tenant/admin API for NIC related options13:39
baoliIrenab, what's the subject of the email?13:40
irenabbaoli: Flavor Framework13:40
irenabit sis related to neutron services, but just see it as example of something that starts the discussion on ML in advance13:41
baolicool, I'll take a close look at it today.13:41
irenabI think we need to reach some model we agree and propose it13:42
heyonglibaoli , i just read your recap, i might wrong, but PCI Group is just a extra info tag as we discussed.13:42
irenabbaoli: by the way, need to update meeting time to  Tue13:43
*** nacim_ has joined #openstack-meeting-alt13:43
*** nacim has quit IRC13:44
heyongliand i don't remember a pci stats group concept,  do i missing something?13:44
baoliYongli, I think that the difference is not just one against many13:44
irenabbaoli: any updates from beagles on documentation?13:44
*** krtaylor has joined #openstack-meeting-alt13:44
baoliyongli, pci stats group is there, right? how do you come up with an stats entry?13:45
heyongliare you mean the pool?13:45
baoliirenab, I didn't see anything from beagle, I thought he'd show up today13:45
heyonglidefine by the pci_flavor_attr13:45
baoliyongli, yes.13:46
irenabseems people continue to come and go...13:46
heyonglido you mind i update the nova side description a litte bit?,13:47
heyonglior i can put to dev mail first13:47
heyonglii try to get a slide to show design choice and why13:47
irenabhayongli: It can be great13:47
baoliYongli, you can come up with a paragraph and put a link in to the wiki13:48
heyonglimaybe usefull to get some core sponsor.13:48
heyonglibaoli: if i do that , we had 2 desciption about same thing13:48
*** markmcclain has joined #openstack-meeting-alt13:48
baoliyongli, if it's the same, then no need. But it could be useful to see what' exactly in your mind13:49
heyonglibaoli, i think it should be same as we discussed so long time13:49
irenabguys, we need one place to put all info and communicate to ML. I guess on Summit we need to present and get core's sponsorship13:49
heyonglii try to put it to mail first13:49
baoliyongli, cool.13:50
baoliIrenab, agreed13:50
heyonglijust put it to the recap?13:51
baoliYongli, I didnt' do full recap on the PCI Flavor since the wiki has more detailed info. So you may update that section to give a summarized good description on the key things in PCI flavor13:51
*** doug_shelley66 has quit IRC13:52
irenabDo we want to propose some action items for next week?13:52
heyonglii worry what should be put to the recap section, let's just do it. and every one can review it and we can agree to a identical description.13:53
irenabplease send email once wiki updated13:53
baoliYongli, I had a link in the PCI flavor section to Ian's wiki13:53
heyonglii will just send mail at fist13:53
baoliyongli, ok, let's start with that13:54
irenabI think we need cover Top Down picture from user(tenant/admin) perspective before drill down to technical side13:54
baoliirenab, sure. I also think that we should collect the use cases13:55
irenabbaoli: agree13:55
irenabShall we make it agenda for next meeting? After we sync on ongoing patches13:56
heyongliin my bp there had some, but i wonder is that we want?13:56
*** nosnos has quit IRC13:56
baoliirenab, sure.13:56
*** eankutse has joined #openstack-meeting-alt13:57
*** VINOD has quit IRC13:58
baoliI can start a agenda section in the wiki, and you guys can put whatever you want to talk about in that section before next meeting. How does that sound?13:58
heyonglicool13:58
irenabgreat13:58
*** jecarey has quit IRC13:59
baoliDo you know what's the deadline for proposing summit session?13:59
baoliI'll check it out13:59
irenabnot sure, but I think ~week before14:00
heyonglino idea, i try to setup one, but not find where to do that, seems no invite code sent out14:00
irenabI think its not opne yet for design summit14:00
baoliThank you guys. time is up for this meeting14:00
irenabthanks14:00
heyonglibye14:00
baoli#endmeeting14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
openstackMeeting ended Tue Mar  4 14:00:42 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-03-04-13.04.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-03-04-13.04.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-03-04-13.04.log.html14:00
irenabbaoli: will ping if have issues with bringing the patch up14:00
sadasuthanks all14:01
*** NehaV has joined #openstack-meeting-alt14:01
*** heyongli has quit IRC14:01
*** sadasu has quit IRC14:01
*** balajiiyer has joined #openstack-meeting-alt14:02
*** beagles has joined #openstack-meeting-alt14:03
*** annegentle has joined #openstack-meeting-alt14:09
*** dguitarbite has joined #openstack-meeting-alt14:17
*** cgoncalves has quit IRC14:17
*** julim has joined #openstack-meeting-alt14:17
*** balajiiyer has left #openstack-meeting-alt14:18
*** lsmola has quit IRC14:24
*** woodster1 has joined #openstack-meeting-alt14:24
*** cgoncalves has joined #openstack-meeting-alt14:27
*** cgoncalves has quit IRC14:27
*** cgoncalves has joined #openstack-meeting-alt14:27
*** ameade has joined #openstack-meeting-alt14:27
*** cgoncalves has quit IRC14:27
*** jgallard has joined #openstack-meeting-alt14:28
*** cgoncalves has joined #openstack-meeting-alt14:28
*** cgoncalves has quit IRC14:28
*** cgoncalves has joined #openstack-meeting-alt14:28
*** banix has joined #openstack-meeting-alt14:30
*** doug_shelley66 has joined #openstack-meeting-alt14:30
*** lblanchard has joined #openstack-meeting-alt14:30
*** lisaclark1 has joined #openstack-meeting-alt14:32
*** richm has joined #openstack-meeting-alt14:32
*** jjmb has joined #openstack-meeting-alt14:32
*** lsmola has joined #openstack-meeting-alt14:33
*** lsmola has quit IRC14:33
*** Ranjitha_ has quit IRC14:33
*** lsmola has joined #openstack-meeting-alt14:34
*** luqas has quit IRC14:34
*** ametts has joined #openstack-meeting-alt14:37
*** luqas has joined #openstack-meeting-alt14:37
*** jjmb has quit IRC14:39
*** bill_az has joined #openstack-meeting-alt14:39
*** samstav has joined #openstack-meeting-alt14:44
*** jjmb has joined #openstack-meeting-alt14:45
*** jjmb has quit IRC14:46
*** jjmb has joined #openstack-meeting-alt14:46
*** dguitarbite has quit IRC14:49
*** lsmola has quit IRC14:50
*** lisaclark1 has quit IRC14:50
*** jecarey has joined #openstack-meeting-alt14:52
*** kevinconway has joined #openstack-meeting-alt14:54
*** banix has quit IRC14:55
*** lisaclark1 has joined #openstack-meeting-alt14:57
*** alcabrera has joined #openstack-meeting-alt14:58
*** saikrishna_ has joined #openstack-meeting-alt14:59
*** kgriffs_afk is now known as kgriffs14:59
*** zns has joined #openstack-meeting-alt14:59
*** malini has joined #openstack-meeting-alt15:00
*** samstav has quit IRC15:00
kgriffs#startmeeting marconi15:00
openstackMeeting started Tue Mar  4 15:00:32 2014 UTC and is due to finish in 60 minutes.  The chair is kgriffs. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: marconi)"15:00
openstackThe meeting name has been set to 'marconi'15:00
*** samstav has joined #openstack-meeting-alt15:00
flaper87'SUP PEOPLEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE?????????????????15:00
kgriffsroll call15:00
kgriffso/15:00
malini\o/15:00
*** irenab has quit IRC15:01
*** balajiiyer has joined #openstack-meeting-alt15:01
flaper87o/15:01
alcabrerahey all!15:01
balajiiyero/15:01
saikrishna_hi all!15:01
flwango/15:01
*** gokrokve_ has quit IRC15:01
flaper87wow, so many folks15:01
*** gokrokve has joined #openstack-meeting-alt15:01
alcabrerawe grow every few weeks. :)15:01
flaper87It brings tears to my eyes15:01
* alcabrera hands out the poptarts15:01
malinialcabrera: the dentist would love tht15:02
alcabreralol15:02
alcabreraoh yes15:02
alcabrera[$]15:02
kgriffs#topic actions from last time15:02
*** openstack changes topic to "actions from last time (Meeting topic: marconi)"15:02
*** xuhanp has quit IRC15:02
alcabrera#link http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-02-18-15.04.html15:02
kgriffsjust one was noted15:02
kgriffsbalajiiyer to follow up with Megan and get us a case study for the summit talk15:02
* flaper87 remembers last time actions once in a week15:02
alcabreranot much action last time - how unusual!15:03
flaper87guess what, it always happens on Tuesdays at 15:00 UTC15:03
*** cpallares has joined #openstack-meeting-alt15:03
balajiiyerkgriffs: can we carry forward it to this week?15:03
kgriffsheh15:03
kgriffs#action balajiiyer to follow up with Megan and get us a case study for the summit talk15:03
kgriffs#topic i-315:03
*** openstack changes topic to "i-3 (Meeting topic: marconi)"15:03
alcabreraOh yeah - i3 is close15:03
alcabreravery close15:03
flaper87like hours close15:03
maliniit is here!15:03
kgriffsflaper87: last time they cut it the following morning. Will they cut during the TC meeting this time do you think?15:04
kgriffssorry, not TC meeting15:04
kgriffsrelease meeting15:04
kgriffsI know last time was a special case because of zuul15:04
flaper87kgriffs: no, it usually closes at some late time in the west coast15:04
flaper87so the cut will happen in the morning15:04
kgriffsoh good!15:05
flaper87but we should block patches today15:05
*** xuhanp has joined #openstack-meeting-alt15:05
flaper87those that are not worth shipping with i-315:05
kgriffsok15:05
kgriffsI am going to blitz v1.1 over the next few hours. If I can't get all the patches in by the next 3 hours, let's say v1.1 is going to be an experimental feature15:06
kgriffspeople will have to go get HEAD to play with it at the summit15:06
flaper87sure thing15:06
kgriffsok. sorry, I'm an eternal optimist. :p15:06
kgriffsother patches?15:06
kgriffs#link https://launchpad.net/marconi/+milestone/icehouse-315:07
flwangkgriffs: /health ?15:07
flaper87flwang: I think we should hold it until after i-315:07
flaper87and I'm not sure whether it makes sense to let it land after the FF15:08
flwangflaper87: do that mean Juno ?15:08
flaper87what do you think?15:08
kgriffshmm15:08
*** caleb_ has joined #openstack-meeting-alt15:08
flwangflaper87: if you guys believe its overall shape is ok, how about lets try to land it before 6 Mar15:08
alcabrerahave we solidified the health/ping semantics?15:08
*** walker_ has joined #openstack-meeting-alt15:08
flwangi-3 but after FF15:09
alcabreraif we have, then I'm favorable towards letting it land soon15:09
alcabreraand making small fixes to it as needed15:09
flwangand yes, it depends on the overall v1.1 status15:09
kgriffsare we "allowed" to land features after i-3 but still for icehouse?15:09
flaper87ok, lets work on that15:09
flaper87kgriffs: you mean after FF15:09
kgriffsflaper87: that's what I mean15:09
kgriffsFF for i-315:09
flaper87kgriffs: yest but only if a Feature Freeze Exception is granted15:09
flwang4 Mar is FF, 6 Mar is i-315:09
kgriffsok15:10
kgriffshmmm15:10
flwanghttps://wiki.openstack.org/wiki/Icehouse_Release_Schedule15:10
alcabreraI gotta run guys. I think I'll be back in time for the last 10 minutes of this meeting!15:10
flaper87flwang: lets work on getting it ready and then ask a Feature Freeze if necessary15:10
alcabreramy basic thoughts: api v1.1 and tempest need help15:10
flaper87alcabrera: kk, ttyl15:10
alcabrerao/15:10
*** eankutse has quit IRC15:10
flwangflaper87: ok15:10
kgriffsflaper87: yep, I was just under the impression that FF for the last milestone was also FF for the icehouse release, which seems to be correct15:10
*** mpanetta has joined #openstack-meeting-alt15:10
*** eankutse has joined #openstack-meeting-alt15:10
*** alcabrera has quit IRC15:10
maliniwe also need somebody to start working on sqlalchemy tests15:10
*** eankutse has quit IRC15:11
flaper87kgriffs: yep15:11
flaper87malini: mmh, what tests?15:11
flaper87there are tests for sqlalchemy already15:11
malinithe gate jobs against diff backends15:11
flwangflaper87: +115:11
maliniflaper87: we have only unit tests, rt?15:11
flaper87malini: oh ok, yeah, I'll help you creating some gates for that15:12
flwangmalini: you mean functional test?15:12
flaper87malini: nope, functional too15:12
maliniwe need the functional tests running against diff backends15:12
*** hockeynut has joined #openstack-meeting-alt15:12
maliniflaper87: tht is cool..I didnt know tht !!15:12
flaper87malini: I'll help you getting the sqlalchemy gate setup15:12
flwangkgriffs: seems we're still missing the func test against v1.115:12
maliniI'll chk it out15:12
flaper87malini: I replaced all the sqlite tests with sqlalchemy15:12
flaper87:)15:12
*** jergerber has joined #openstack-meeting-alt15:12
kgriffsflwang: yes we are15:12
flwangflaper87: malini: cound me15:12
flwangkgriffs: do you think it's a blocker for landing the v1.1?15:13
maliniI was planning to start working on fun tests for 1.1, if somebody can tackle the gate part..I have a good idea of what/how to do tht15:13
flwangkgriffs: if so, seems we can't make it15:13
flwangmalini: count me, after I complete the /health15:14
maliniflwang: awesome! thabks!15:14
kgriffsflwang: well, our only possible solution would be to add functional tests to the mainline and if we find any bugs, we would need to backport those to the icehouse RC15:14
malinithanks! *15:14
flwangkgriffs: make sense for me, thanks for the clarification15:15
kgriffsok, so I would like to propose a 2-hour super hero sprint15:15
kgriffslots of code, lots or reviewing15:15
flaper87kgriffs: sounds good15:15
kgriffsthen we meet back in #openstack-marconi and decide what our final bp15:16
flwangkgriffs: +115:16
kgriffsset of bp's will be15:16
flaper87kgriffs: we could probably make today's meeting shorter and use that time for coding too15:16
kgriffsok15:16
kgriffslet's speed this along then15:16
* kgriffs seconds flaper87's motion15:16
kgriffs#topic tempest15:16
*** openstack changes topic to "tempest (Meeting topic: marconi)"15:16
flwangflaper87: competing with time?15:16
kgriffsmalini: status?15:16
maliniI have a patch outstanding to address the devstack issue15:17
flaper87flwang: I'm always competing with time :P15:17
kgriffsmalini: have you confirmed it will work?15:17
malinihttps://review.openstack.org/7783215:17
flaper87malini: mind giving a summary of the latest findings15:17
flaper87?15:17
malinikgriffs: it does work on a brand new devstack install when I tried..so hope it'll work15:17
flaper87malini: cool15:18
*** amytron has joined #openstack-meeting-alt15:18
maliniI pinged a few core reviewers..but havent heard back yet15:18
maliniflaper87: Its basically a workaround till we figure the stdout issue15:18
flaper87looks like a fix to me15:18
flaper87:P15:18
kgriffsflaper87: the gist is that something still requires stdout but we can't figure out what15:18
maliniflaper87: hmm…I would like to know why ..but can live with this for now15:19
kgriffswe tried monkey-patching sys.stdout and nobody called write on it15:19
*** xuhanp has quit IRC15:19
flaper87mmhh, that's interesting15:19
flaper87what's even more interesting is that all projects are using the same logging module15:19
flaper87so, I can't think OTOH what's wrong with marconi15:19
kgriffsso, we got logging to stop using stdout15:19
maliniflaper87, flwang: if you are buddies with any devstack core reviewers, try bribing them to look at the patch ;)15:19
kgriffsso I don't think it's logging any more15:19
kgriffssomething else15:19
*** lisaclark1 has left #openstack-meeting-alt15:20
*** mattgriffin has joined #openstack-meeting-alt15:20
maliniflaper87: I think there is something different15:20
malinionly ceilometer & us specify the log dir in devstack scripts15:20
kgriffsanyway, if we can get this to land and revisit for Juno, that would be WUNDERBAR15:20
flaper87malini: mmhh15:20
flaper87ok15:20
flaper87malini: and now you know what project I copied our devstack code fromn15:21
flaper87:D15:21
malini:D15:21
kgriffsdevstack does crazy stuff with FD redirects15:21
flaper87from*15:21
flwangmalini: may i know the patch link? I will see what I can do15:21
flaper87ok, moving forward15:21
kgriffsyep15:21
maliniflwang: https://review.openstack.org/#/c/7783215:21
flwangmalini: thanks15:21
maliniflwang: thank You!!15:21
kgriffskk15:21
kgriffslet's git-r-done15:22
kgriffs#topic documentation15:22
*** openstack changes topic to "documentation (Meeting topic: marconi)"15:22
kgriffsbalajiiyer: ^^^15:22
balajiiyerkgriffs: Latest patch set 20 needs some review15:22
flaper87balajiiyer: gtk15:22
malinibalajiiyer: can you post the review link plz?15:22
balajiiyerhttps://review.openstack.org/#/c/72001/15:23
balajiiyerThere was a trademark issue on 19, that was fixed.15:23
flaper87#link https://review.openstack.org/#/c/72001/15:23
balajiiyerWe also have operations doc now15:23
kgriffsbalajiiyer: is that part of the same patch?15:24
balajiiyerOz will be submitting a patch today15:24
kgriffsoic15:24
* flaper87 wants an operation gummy bears15:24
kgriffsok, let's get these merged today15:24
cpallareslol15:24
kgriffsif needed, please file bugs for minor nits and we will follow up15:24
*** chandan_kumar has joined #openstack-meeting-alt15:24
kgriffslet's make sure the major stuff is OK15:24
flwangkgriffs: +115:25
balajiiyerkgriffs: ok15:25
kgriffs#topic sqlalchemy15:25
*** openstack changes topic to "sqlalchemy (Meeting topic: marconi)"15:25
flaper87IT'S DONEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE15:25
kgriffsw00t15:25
flwanghaha15:25
kgriffsthis one should be done right? https://blueprints.launchpad.net/marconi/+spec/sql-sharding-controllers15:25
balajiiyerflaper87: awesome15:25
flaper87kgriffs: yeah, alej completed the sharding part15:25
kgriffsETOO_MANY_EES15:26
flaper87we need to test it carefully with other backends now15:26
kgriffsk, I will update that bp15:26
flaper87kgriffs: you mean, EEEEEEEEEEEEEEEEEEETOMANYEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE15:26
kgriffsheh15:26
flwangkgriffs: I would suggest to make sqlalchemy as the default backend to be more friendly for the new comer15:26
flwangkgriffs: flaper87: make sense?15:26
flaper87so, I'll help amlini with getting the gate done for that15:26
flaper87flwang: it is the default backend15:26
*** yamahata has joined #openstack-meeting-alt15:26
flwangflaper87: now?15:27
flaper87yes15:27
flwangflaper87: coooooooooooool15:27
flaper87haha15:27
*** alcabrera has joined #openstack-meeting-alt15:27
kgriffscan I mark as implemented the SQL Storage Driver?15:27
flaper87it's funny how I swapped it and people still thinks they're using sqlite15:27
kgriffsI assume so...15:27
flaper87muahahahah muahahha muahahaha15:27
flaper87:D15:27
flwangflaper87: I'm always using mongodb, so i'm not aware of that15:27
flaper87well, they're using sqlite but through sqla15:27
alcabreralol15:27
* alcabrera returns sooner than expected15:27
flaper87kgriffs: yeah, mark it as done15:27
flaper87alcabrera: coool, wb15:28
alcabrerakgriffs: +1 for sql marked as done15:28
*** david-lyle has joined #openstack-meeting-alt15:28
flwangalcabrera: $$$$$$15:28
* ametts is going to try it with Microsoft Access15:28
alcabreraat this point, it's just bug fixes, since it's functionally feature complete15:28
*** NehaV has quit IRC15:28
flaper87alcabrera: hahahahahahahaha15:28
flaper87hahaha15:28
kgriffsametts: that's crazy talk!15:28
flaper87ametts: ^15:28
*** NehaV has joined #openstack-meeting-alt15:28
alcabreraametts: try out the experimental Microsoft Excel backend. :P15:28
kgriffs#topic pecan15:28
*** openstack changes topic to "pecan (Meeting topic: marconi)"15:28
balajiiyerkgriffs: working on perf benchmarks15:29
balajiiyerI have numbers with tsung, wrking with ab now15:29
kgriffsThis can land after the FF, but I want to make sure we are on track to deliver a good, objective report15:29
balajiiyerkgriffs: yeah, have to do some due diligence before I can publish numbers, will have it by end of this week15:30
kgriffsbalajiiyer: rock on15:30
alcabreracool15:30
alcabrera#note balajiiyer making good progress on evaluating pecan15:30
*** alazarev has joined #openstack-meeting-alt15:31
alcabreraany other thoughts on this topic?15:31
kgriffsThe more things we can quantify, the better15:31
balajiiyerIm using mongodb as the storage driver, and possibly look at in-memory storage drivers15:31
balajiiyerany other ideas what else I can do?15:31
*** lsmola has joined #openstack-meeting-alt15:32
flaper87balajiiyer: sqlalchemy + mysql15:32
alcabreraflaper87: +115:32
alcabreraso, another thought came to mind15:32
balajiiyerIm treating this as 'Marconi in Pecan', vs 'Marconi in Falcon', so Im swapping out transport drivers, keeping everything else a constant.15:32
balajiiyerflaper87: ok15:33
alcabreraThere's a lot of talk of performance, and I understand that's a point of interest. It's one of the easier things to measure objectively.15:33
alcabreraI'm very interested in the subjective side of the equation, too15:33
alcabrerahow easy is it to extend marconi using one vs. the other?15:34
alcabreraThings of that nature.15:34
flaper87balajiiyer: also, lets make sure we come up with some ideas as to how both pecan and falcon can be improved15:34
alcabreraI understand that's hard to be objective about, though. :/15:34
flaper87the whole point is not just to find out which is faster, easier etc but to come up with an idea of how we can contribute back to both communities regardless of our final choice15:34
alcabreragood words, flaper8715:34
balajiiyeralcabrera: yeah, I have a set of evaluation criteria, that is one of those.15:34
flwangflaper87: +115:35
alcabrerapeople will continue to use pecan and falcon for their own projects. Let's try to make both more awesome15:35
kgriffsgood thoughts15:35
* flaper87 for president15:35
alcabrera#note pecan+falcon: how can we make both better? Share feedback with community15:36
* alcabrera votes flaper87 - every time15:36
balajiiyer*takes notes*15:36
flaper87ok, open discussion and then code ?15:37
alcabreraapi v1.1 discussion is next, I believe15:37
flaper87yeah, we were thinking to make the meeting shorter this week and do a full code immersion15:37
alcabreraah15:37
alcabreraokay15:37
alcabrerasounds good to me15:37
kgriffs#note Goals for Pecan evaluation include: identify areas of improvement for both frameworks where we can contribute, provide guidance on when to use each framework, deliver metrics, and provide well-thought-out arguments for subjective metrics15:38
flaper87not sure what kgriffs thoughts are about moving the v1.1 discussion to the enxt meeting15:38
kgriffsoh, I'm pretty much ignoring today's agenda. :p15:38
flaper87LOL15:38
kgriffscrunch time15:38
flaper87hahaha15:38
*** coolsvap has joined #openstack-meeting-alt15:38
flaper87ROFL15:38
kgriffsok, let me just emphasize this point and then let's get to work15:39
kgriffsImagine if we could rewind 18 months or so15:39
kgriffsand our team were the ones floating the idea of Pecan15:39
kgriffsnow, what kind of a report would we create and circulate to other OS teams?15:40
kgriffsmaybe that isn't quite the right thought experiment, but you get the idea15:40
kgriffsactually15:41
alcabrerakind of fuzzy15:41
kgriffslet's adjust this15:41
kgriffsso, here is how I would personally go about introducing pecan15:41
kgriffsfirst, I would find a different project and ask them to basically do what we are doing15:42
kgriffsI would want an "outside" opinion15:42
kgriffsand I would consider carefully a set of criteria15:42
*** samstav has quit IRC15:42
kgriffsthen I would take the results to the community and see if I could get another project to give Pecan a try15:43
*** samstav has joined #openstack-meeting-alt15:43
kgriffspreferably a core (AKA "kernel") project: network, storage, compute15:43
*** mattgriffin has quit IRC15:44
alcabrerawhat that tells me, is that this is only the beginning of the evaluation question15:44
*** adrian_otto has joined #openstack-meeting-alt15:44
alcabrerawhat would API v3 in Nova look like with Falcon is the first thing that comes to mind15:44
alcabrerathings of that nature15:44
*** hockeynut has quit IRC15:44
alcabreraI'm favorable towards an ongoing experiment15:45
alcabreratool diversity is a powerful thing15:45
alcabrerathat's it from me15:45
*** datsun180b has joined #openstack-meeting-alt15:45
flaper87sounds good to me too15:46
*** mattgriffin has joined #openstack-meeting-alt15:46
kgriffsI tried to argue last year for a broader evaluation period on the ML. Not that I think Falcon is inherently "better" but that this is how you create standards in a community; you do it organically and with evaluations, gathering the data over time and working towards a rough consensus.15:46
kgriffsBut, I was shouted down15:46
alcabrera:(15:46
kgriffsin any case, I am trying to keep our evaluation as objective and serious as possible15:46
balajiiyer*hopes to deliver*15:47
kgriffsthat is why I explicitly wanted balajiiyer to lead that effort.15:47
*** paulmo_ has joined #openstack-meeting-alt15:47
*** markmcclain has quit IRC15:47
kgriffshe is brand new to openstack, and started with little to no experience in either framework15:48
kgriffsand I have been telling everyone every chance I get to quantify things, be open-minded, and let's do this the right way15:48
*** devkulkarni has joined #openstack-meeting-alt15:48
kgriffsIdeally, we would take our findings to the community and see if we can get another project to do the same excercise15:49
kgriffsCould everyone come back and say Falcon totally sucks and nobody wants to use it?15:50
kgriffssure.15:50
kgriffsbut I suspect the answer is going to be more gray than that and we will find that arguing over which is better: forks or knives15:51
kgriffs...is just silly and a huge waste of time15:51
kgriffswhenever someone asks me what framework they should use for their new project, I say: try both and decide which one works best for you, your team, and your project15:52
alcabrera+115:52
kgriffsI honestly do15:52
kgriffsAll I am asking is for promoters of other frameworks to do the same15:52
kgriffsthis is how you build a community15:52
flwangkgriffs: +115:52
kgriffsand yes, I am well aware this is all going on the record.15:52
kgriffssomeone needed to recognize the elephant in the room15:53
* alcabrera cheers15:53
alcabrera#note kgriffs advocates for open-minded evaluation of tools and technologies15:53
*** johnthetubaguy has joined #openstack-meeting-alt15:54
kgriffsok, sorry, this ended up taking the full hour after all.15:54
kgriffs#topic open discussion15:54
*** openstack changes topic to "open discussion (Meeting topic: marconi)"15:54
*** sparkycollier has joined #openstack-meeting-alt15:54
*** noslzzp has joined #openstack-meeting-alt15:54
flaper87#link https://plus.google.com/events/ckjhm8rggnqvrnspftna845kubk15:55
alcabreraoh yeah15:55
flaper87Marconi hangout15:55
alcabreraMarch 2715:55
flwangflaper87: I will watch it15:55
alcabrera#note Marconi G+/Hangout happening March 2715:55
maliniwhat is tht for?15:56
flwanggeneral or any best practice15:56
kgriffsok, so everyone have a good idea of what they will focus on the next 2 hours15:56
*** nati_ueno has joined #openstack-meeting-alt15:57
flwangI have watched all the Marconi I can get from youtube, including kgriffs', flaper87 and alcabrera's, haha15:57
*** johnthetubaguy1 has joined #openstack-meeting-alt15:57
kgriffsoh oh. :)15:57
kgriffs#endmeeting15:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:57
openstackMeeting ended Tue Mar  4 15:57:39 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-03-04-15.00.html15:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-03-04-15.00.txt15:57
openstackLog:            http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-03-04-15.00.log.html15:57
alcabreraI'll gather the minutes15:57
kgriffssee you all on the other side!15:57
kgriffsalcabrera: thanks!15:57
*** aratim has joined #openstack-meeting-alt15:58
*** noorul has joined #openstack-meeting-alt15:58
*** coolsvap1 has joined #openstack-meeting-alt15:58
*** johnthetubaguy has quit IRC15:58
*** mpanetta has left #openstack-meeting-alt15:58
*** muralia has joined #openstack-meeting-alt15:58
*** hockeynut has joined #openstack-meeting-alt15:59
*** ycombina_ has joined #openstack-meeting-alt15:59
adrian_otto#startmeeting Solum Team Meeting16:00
openstackMeeting started Tue Mar  4 16:00:14 2014 UTC and is due to finish in 60 minutes.  The chair is adrian_otto. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: Solum Team Meeting)"16:00
openstackThe meeting name has been set to 'solum_team_meeting'16:00
adrian_ottohttps://wiki.openstack.org/wiki/Meetings/Solum Our Agenda for today16:00
adrian_otto#topic Roll Call16:00
*** openstack changes topic to "Roll Call (Meeting topic: Solum Team Meeting)"16:00
*** alcabrera has left #openstack-meeting-alt16:00
*** paulczar has joined #openstack-meeting-alt16:00
devkulkarniDevdatta Kulkarni16:00
adrian_ottohello everyone!16:00
muraliamurali16:00
paulmo_Paul Montgomery16:00
*** coolsvap has quit IRC16:00
adrian_ottoAdrian Otto16:00
noorulNoorul Islam K M16:00
paulczarPaul Czarkowski16:01
ycombina_Shaunak Kashyap16:01
aratimArati Mahimane16:01
*** hockeynut has quit IRC16:01
*** alexheneveld has joined #openstack-meeting-alt16:01
alexheneveldhello16:01
julienvey_Julien Vey16:01
*** jjmb has quit IRC16:01
adrian_ottoAlex, welcome!16:01
*** tomblank has joined #openstack-meeting-alt16:01
julienvey_won't be able to stay long16:01
stanniePierre Padrixe16:02
tomblanktom blankenship16:02
coolsvap1Swapnil16:02
funzoChris Alfonso16:02
*** cpallares has left #openstack-meeting-alt16:02
adrian_ottojulienvey_: thanks for the heads up. How long will you be with us today?16:02
alexheneveldgood to be back - and great to be seeing so much activity16:02
julienvey_adrian_otto half an hour16:03
adrian_ottook, in that case, I am planning to shuffle the agenda so you can provide input on the Incubation Discussion16:03
adrian_ottoanyone feel strongly to the contrary?16:03
*** atiwari has joined #openstack-meeting-alt16:04
datsun180bargh, missed my cue16:04
gokrokveHi16:04
datsun180bEd Cranford16:04
adrian_ottowe are still in Roll call, datsun180b16:04
*** malini has left #openstack-meeting-alt16:04
gokrokveGeorgy Okrokvertskhov16:04
adrian_ottook, so we will do Incubation discussion just before Review Action Items.16:04
adrian_ottothanks everyone for attending. Let's proceed to announcements. Feel free to chime in at any time to record your attendance if you have not already.16:05
adrian_otto#topic Announcements16:05
*** openstack changes topic to "Announcements (Meeting topic: Solum Team Meeting)"16:05
adrian_ottoSolum Summit Registration - Make your travel arrangements16:05
*** saikrishna_ has quit IRC16:05
adrian_ottoTuesday, March 25, 2014 - Wednesday, March 26, 201416:06
adrian_otto#link https://wiki.openstack.org/wiki/Solum/Summit Find Link to registration here16:06
adrian_ottothis is a very important event for us. I might argue it's the most important Summit for this project period.16:06
adrian_ottoso if you are on the fence for whether to attend in person, please attend.16:06
adrian_ottonext announcement: Solum Demo Session at Atlanta ODS Event16:07
adrian_ottoplease take a moment to vote for our demo session: Vote at: https://www.openstack.org/vote-atlanta/Presentation/introducing-solum16:07
adrian_ottoinstead of submitting a whole mess of sessions, we just want everyone to focus on this, and make it awesome16:07
adrian_ottoall your votes will make a huge difference16:08
muraliaVoting was closed on March 3rd. Thats what the website says.16:08
adrian_ottooh, well.16:08
*** luqas has quit IRC16:08
adrian_ottoif you happen to know a member of the committee who reviews these, possibly a mention is justified.16:08
*** rajdeep has joined #openstack-meeting-alt16:08
adrian_ottoas voting is only part of the criteria for selection16:09
adrian_ottonext announcement:16:09
adrian_ottoCAMP 15 day Public Review is open. Ends 2014-03-17. Please make comments based on what we have learned in Solum.16:09
adrian_otto#link https://www.oasis-open.org/news/announcements/15-day-public-review-for-cloud-application-management-for-platforms-camp-v1-1-end16:09
adrian_ottothis is a PaaS standard that may still be shaped by what we do in this project.16:09
adrian_ottoif you care about what lands in the standard, please review and comment16:10
rajdeepare we trying to get paas vendors to get involved in the standard?16:10
adrian_ottorajdeep: I think all of us should take an interest, and know what's proposed16:10
adrian_ottothe more consensus reached early, the better it will be16:11
rajdeepok standard will become successful if established players adopt it16:11
adrian_ottoits' worth an hour or two to look and jot down remarks16:11
alexheneveldre CAMP asalkeld (for whom I guess this time slot is not very friendly!) and I had a chat16:11
alexheneveldone spot of confusion was whether it should be used for the pipeline (build triggers etc) ... i tend to think *not*16:12
muralia+116:12
alexheneveldit is designed to describe and manage application deployments (assemblies)16:12
adrian_ottoalex, yes. I think we should touch on that again during open discussion today16:12
alexheneveldhowever it could be interesting to give an abstracted api on top of things like build services16:12
*** eankutse has joined #openstack-meeting-alt16:12
*** dhellmann_ is now known as dhellmann16:12
*** eankutse has quit IRC16:12
*** eanxgeek|log is now known as eanxgeek16:12
alexheneveldadrian_otto: cool16:13
*** eankutse has joined #openstack-meeting-alt16:13
adrian_ottook, next topic16:13
adrian_otto#topic Incubation Discussion16:13
*** openstack changes topic to "Incubation Discussion (Meeting topic: Solum Team Meeting)"16:13
adrian_ottoAre we interested in changing our wiki content to adjust language referring to us as "OpenStack Related" to state an intent to file for OpenStack incubation upon achievement of milestones agreed to by the team members?16:13
*** jmontemayor has joined #openstack-meeting-alt16:13
adrian_ottoI'm seeking a perspective from as many of you as possible on this question16:13
funzoI'm not sure of what the cons are from doing this16:14
julienvey_I agreed with that statement, but do we discuss the milestone today ?16:14
julienvey_s/agreed/agree16:14
noorulWe need clarity on m116:14
adrian_ottowe can discuss the milestone whenever it makes sense16:14
*** saikrishna_ has joined #openstack-meeting-alt16:14
*** markmcclain has joined #openstack-meeting-alt16:15
adrian_ottoperhaps it's m1, or maybe something different. The question really hinges on whether we want to state an intent to pursue an incubation period in our future.16:15
adrian_ottoand if that's desired by our contributors, then we should be clear about that intent16:15
*** woodster1 has left #openstack-meeting-alt16:15
noorulI think it was our intent from the beginning to apply for incubation16:16
devkulkarnithe only con I see is, once an intent is stated and if for some reason that does not get followed through, what does that mean?16:16
julienvey_it's desired for me :)16:16
stannie+1 noorul16:16
adrian_ottodevkulkarni: if we change our minds, that's fine.16:16
datsun180bi don't think there's anything wrong with stating intent and reevaluating later if needs or circumstances change16:16
adrian_ottobut based on the input I have so far, I think we do have that intent16:16
datsun180bthat's what intent is16:16
gokrokve+116:17
devkulkarniin that case, there is no con as such imo.16:17
alexheneveld+116:17
gokrokveThe main part will be a clear mission statement to make a proper posiotioning in the community16:17
tomblank+116:17
devkulkarni+1 to changing the wiki16:17
muralia+116:17
stannie+116:17
*** luqas has joined #openstack-meeting-alt16:17
adrian_ottogokrokve: exactly, I will begin to offer some draft statements for us to discuss.16:17
tomblankgokrokve: yes, i think that is important16:17
adrian_ottothat's a prerequisite for application16:18
adrian_ottook, this appears to be unanimous. Are there any alternative viewpoints to consider?16:18
*** rajdeep_ has joined #openstack-meeting-alt16:18
*** rajdeep has quit IRC16:19
adrian_ottowelcome back rajdeep_16:19
paulczar+116:19
rajdeep_Currently are we in the pre incubation phase?16:19
aratim+116:19
adrian_ottook, hearing no objections to the suggestion, I will move to a #agreed on this point,adn we can take this a step further16:19
adrian_otto#agreed Solum will adjust it's public facing documentation to state a clear intent to pursue an incubation period for the project.16:20
*** alazarev has quit IRC16:20
adrian_otto#action adrian_otto to adjust the wiki to show intent for incubation16:20
adrian_ottorajdeep_: yes, we are in pre-incubation16:20
rajdeep_ah ok16:21
adrian_ottoso the next logical question is when would be the best time to process an application for incubation?16:21
adrian_ottobased on the prevailing criteria, once we have a mission statement, we qualify.16:21
julienvey_yes16:22
adrian_ottoone possibility is to pursue this on an immediate basis16:22
datsun180bi don't know if there's such thing as too early in this case16:22
*** _nadya_ has joined #openstack-meeting-alt16:22
adrian_ottoso that Juno would potentially be our first full cycle in inbubation16:22
adrian_ottodatsun180b: exactly. That's what incubation is intended for.16:23
muraliaYes, we should do it right away. We'll probably attract more contributors that way.16:23
adrian_ottoafter a full cycle in incubation, and doing train based release milestones, we may be at a point suitable for integrated status.16:23
julienvey_is there a deadline for incubated projects to get integrated ?16:24
adrian_ottojulienvey_: good question. You can ally any time.16:24
*** cjellick has joined #openstack-meeting-alt16:24
adrian_ottobut you must go through a full cycle before you can graduate out of incubated into integrated status16:25
devkulkarniI would like to hear gokrokve's views on how distracting it is for the team while the discussion is happening about incubation? what are your experiences with murano?16:25
gokrokvedevkulkarni: In our case it was pretty clam. There are some discussions with another incubation request for Climate project.16:26
*** alazarev has joined #openstack-meeting-alt16:26
gokrokveThe main concerns were mission statement and needs of such program\functionality16:26
gokrokveThe team should be prepared to answer that.16:26
*** tnurlygayanov has joined #openstack-meeting-alt16:26
gokrokveThere are not much technical questions.16:26
devkulkarnigokrokve: I see.16:27
*** johnthetubaguy1 is now known as johnthetubaguy16:27
adrian_ottoI expect the technical criteria is more about exiting incubation rather than entering.16:27
adrian_ottoand we have followed all the guidelines that are normally requested.16:27
*** vkmc has quit IRC16:27
adrian_ottoso I don't expect major rework16:27
gokrokveadrian_otto: Sure. There are some requirements for incubation, but as I see they already satisfied in Solum (devstack-gate, requirements check)16:28
adrian_ottoas our first core croup were almost all in the OpenStack Technical Committee16:28
adrian_ottook, so I am happy to take an action item to offer a mission statement16:28
rajdeep_ /NICK rajdeep16:28
gokrokveYes. We need to explain why this project should be a part of OpenStack.16:28
adrian_ottothat we can etherpad on to refine16:29
adrian_ottoso let16:29
gokrokveIt will be hard as there are many PaaS solutions which work with OpenStack.16:29
adrian_ottous assume for sake of discussion that we are at the point of having a mission we all believe in, and all the rationale needed for an applicaiton16:29
stanniewe will have to explain how Solum works differently16:29
adrian_ottowould anyone object to filing right away?16:30
gokrokveWith the recent CloudFoundry movement to open-source community it will be even harder.16:30
*** saikrishna_ has quit IRC16:30
devkulkarnigokrokve: Yes. I guess in a way this approach will make us crystallize our thinking around the differences and needs very clearly.16:30
adrian_ottogokrokve: I am confident this project is different enough that we can make it clear why these are in fact apples and oranges16:30
*** slagle has quit IRC16:31
julienvey_adrian_otto: +116:31
noorulIsn't important, which milestone will bring that difference?16:31
gokrokveSure. We need to prepare couple stron use cases which show where Solum adds value.16:31
nooruls/Isn't/Isn't that16:32
*** shakayumi has joined #openstack-meeting-alt16:32
adrian_ottonoorul: that's a good question. Because we are taking an iterative approach, some of the differences will be less obvious in the beginning, but the key differences are in the orientation with the IaaS of OpenStack16:32
gokrokvenoorul: I think this is important. We need to show that there are benefits right now.16:33
noorulThat is what I also felt but I think m1 has deviation from earlier plan.16:33
gokrokvenoorul: I think nobodt will listen stories about benefits in 5 year horizon.16:33
adrian_ottowe know from our discussions with potential end users, that there are a wide variety of needs and use cases. Solum appeals to some of those, and other existing systems appeal to others.16:34
adrian_ottopractically all cars have four wheels. Some are SUV's and others are two door coupes. Why do we need both types? Because the consumers have differing interests.16:35
paulczaradrian_otto: I agree you should draft up a mission statement as you have a good clear vision about what solum is and why it's important to openstack and different to <insert other thing here>16:35
adrian_ottook, I willt ake that as an action16:35
adrian_otto#action adrian_otto to draft mission statement and solicit input form interested contributors16:35
adrian_ottoif you would like to help, just let me know and I will be certain to include you (even if you are reading this as a transcript)16:36
julienvey_I have to go, thanks adrian_otto for bringing this up early, interesting discussion16:36
adrian_ottojulienvey_: thanks! See you next time!16:37
alexheneveldbeing integrated with heat and openstack is a big differentiator16:37
*** muralia has quit IRC16:37
adrian_ottook, any more thoughts to consider on the incubation subject?16:37
alexheneveldcf has a nice approach based on bosh creating "stem cell nodes" but the "build on stem cells" approach won't fit everything.  having standards of heat and openstack underneath allows nice alternatives.16:37
*** julienvey_ has quit IRC16:38
*** muralia has joined #openstack-meeting-alt16:38
adrian_ottoalexheneveld: +116:38
adrian_ottook, let's proceed to action items16:38
adrian_otto#topic Review Action Items16:38
*** openstack changes topic to "Review Action Items (Meeting topic: Solum Team Meeting)"16:38
adrian_ottoadrian_otto to support muralia for review of https://etherpad.openstack.org/p/MinimalCLI (for tasks specific to blueprints)16:39
adrian_ottomuralia: Should we carry this forward, or are we happy with this now?16:39
muraliaI've looked through the etherpad. https://etherpad.openstack.org/p/MinimalCLI16:39
muraliait's good for now16:39
noorulI have questions16:39
muraliai had to make a few changes to the app create command16:39
muraliasure16:39
adrian_ottonoorul: please proceed16:40
noorul1. Are we considering plan file for m1?16:40
*** harlowja_away is now known as harlowja16:40
devkulkarninoorul: I can answer that16:40
muraliaI'm workign with Angus to decide this. most probably not, or atleast, just a basic one with just a repo url16:40
devkulkarniasalkeld took first stab at implementing it. he found some issues which I think he is working out with alex.16:41
*** harlowja has quit IRC16:41
adrian_ottonoorul: Once concern we are working on is how best to express the difference between an application configuration, the related workflow(s), and the deployment architecture.16:41
devkulkarniIn the mean time I think asalkeld is proceeding with a very simple plan file (which just contains git repo url), or an option of no plan file.16:41
*** alazarev has quit IRC16:41
adrian_ottopiling that all into one file made sense conceptually, but in practice turned out to be a bit messy16:41
alexheneveld+ the project config file and the application deployment plan should be separate16:42
alexheneveld+1 ^^^16:42
*** ramashri has joined #openstack-meeting-alt16:42
adrian_ottoso we are interested in ideas for how to address this16:42
*** saikrishna_ has joined #openstack-meeting-alt16:42
alexheneveldin particular you may have multiple deployment plans, for different environments etc16:42
adrian_ottoone possibility is what alexheneveld is suggesting which is to use separate files for the config and deployment16:42
*** eankutse has quit IRC16:43
adrian_ottowe could still have a single plan file that makes references to other files as needed16:43
*** eankutse has joined #openstack-meeting-alt16:43
alexheneveldand project config (is there a better name for this?) focuses on per-project stuff, like how to build it, test it, what to promote when where etc16:43
paulczarwith m1 functionality being very limited,  do we really need a plan file ?   or I guess more,  can we just have a default plan file and have the CLI/API auto select it ?16:44
alexheneveld+1 adrian_otto project config would refer to individual deployment plans16:44
devkulkarnialexheneveld: is there a etherpad that you and asalkeld are discussing this in?16:44
adrian_ottonoorul: the short answer to your question is yes, there will be a plan file. The uncertainty at this point is exactly what belongs in there, and what should be broken out into supporting files16:44
noorulIs this decision factored in this etherpad ?16:44
noorulI think we should focus on m116:44
alexhenevelddevkulkarni: so far i don't think so ... i caught asalkeld quite late his time and it was a quick chat but i expect he will write it up16:44
noorulFor m1 do we need plan file?16:45
muraliaFor M1, we might just want to keep it simple. one option is to just have one build/deployment workflow in solum for M1 and just pass in a plan file with a git repo url in it. or even ignore the plan file and just pass in the git repo url to the assembly create CLI call.16:45
adrian_ottoso one way to continue making forward progress on the m1 target is to defer some of the design effort, and focus on the simple case first.16:45
muraliaI think the best would be to not use a plan file and keep it simple.16:45
noorulWhen I spoke to Angus y'day, I requested him to send an email to ML with planless idea16:45
alexheneveld+1 quite possibly we don't need deployment plan file for m1, there is a default way an app always gets deployed16:45
noorulI think he will be doing it may be by tomorrow16:46
adrian_ottothat would essentially amount to setting the repo URL as an environment variable, or an argument to the CLI16:46
adrian_ottoas that's the minimum piece if information needed for the simple workflow16:46
adrian_ottos/if/of/16:46
muraliaadrian_otto: it could be sent in as an argument to the 'assembly create' command16:47
devkulkarni+1 to argument to CLI16:47
adrian_ottook, we are getting a bit crunched on time for today16:47
alexheneveld(the plan file would really be for setting different deployment configurations, as i see it)16:47
*** safchain has quit IRC16:47
adrian_ottoI do see this decision as very important16:47
adrian_ottowould we like to continue now, or revisit this?16:47
muraliawe could continue discussion on this etherpad. https://etherpad.openstack.org/p/MinimalCLI16:47
adrian_ottomuralia: okay, thanks. We can also schedule a breakout meeting for this if there is sufficient interest16:48
devkulkarniI would not like to clutter the cli etherpad with discussion about plan16:48
muraliasure16:48
adrian_ottothen link to another etherpad in that one16:48
*** gyee has joined #openstack-meeting-alt16:48
nooruldevkulkarni: I think this is very important16:48
nooruldevkulkarni: We need to narrow down the scope for m1.16:48
devkulkarninoorul: yes, I am not disagreeing. there was another etherpad (something called solum-demystified)16:49
muraliahttps://etherpad.openstack.org/p/solum-demystified16:49
devkulkarniI think plan was being discussed there. so just suggesting that we do plan brainstorming there. but no hard preference. anything that works16:49
adrian_ottoso let's ask it… who feels strongly that we should have a comprehensive plan file as part of m1, versus a streamlined workflow for the general case, and a simplified approach to accompany it?16:49
adrian_ottoI am partial to the simple approach, which will allow us freedom to iterate on it16:50
muralia+1 for simple approach16:50
devkulkarni+1 to streamlined workflow for general case16:50
stanniesimple and then iterate16:50
stannie+116:50
tomblank+1 simple approach and then iterate on it16:50
datsun180b+1 for simple16:50
rajdeep_i think we should focus on getting app deployed without too many complications16:50
adrian_ottook, good16:51
alexheneveld+116:51
adrian_ottoalternate viewpoints to consider?16:51
adrian_ottook , I will move to a #agreed16:51
adrian_otto#agreed to use a simplified plan file approach for m1, so that it is suitable for a general use case, and allows additional features to be added in subsequent iterations.16:52
adrian_ottodoes that sound about right?16:52
*** SumitNaiksatam has quit IRC16:53
devkulkarniso we are still saying we will have a plan file — just making sure..16:53
devkulkarnibut a simplified one16:53
adrian_ottodevkulkarni: it may be implicit16:53
adrian_ottothere will be a plan resource regardless16:53
muraliano, we shouldnt. I'm guess that will be hashed out in the email that angus will send out soon16:53
adrian_ottobut we might actually bypass the file itself by using the CLI16:53
devkulkarnisure, okay.16:54
adrian_ottook, since we have limited time remaining, I'd like owners of blueprints to place any updates in the whiteboards on those respective BP's.16:54
*** balajiiyer has left #openstack-meeting-alt16:54
adrian_ottoif you would like us all to hear your update, you are welcome to make it now.16:54
devkulkarniadrian_otto: okay, will do.16:54
devkulkarniupdates on specify-lang-pack. aratim's work got merged!!16:55
adrian_ottowhoot16:55
* paulmo_ cheers Arati16:55
adrian_otto#topic Open Discussion16:55
*** openstack changes topic to "Open Discussion (Meeting topic: Solum Team Meeting)"16:55
devkulkarnistannie is planning to work on the rest of the actions (PUT/POST, etc.) from that BP16:55
adrian_ottoexcellent16:56
*** harlowja has joined #openstack-meeting-alt16:56
devkulkarniadrian_otto: gokrovke, asalkeld, and I were chatting about similarities and differences between murano.16:57
adrian_ottoI will be proposing additional core reviewer candidate(s) over the next week16:57
adrian_ottoif you have input, I'm open to hearing from you16:57
devkulkarnihave you had a chance to sync up with gokrovke about this?16:57
adrian_ottodevkulkarni: I had a chat with gokrokve, yes.16:57
stanniedevkulkarni: I am currently working on functional tests for components so Julien Vey started working on PUT/POST for LP16:57
devkulkarnihow does murano's workflow DSL line up with what we want to express?16:57
devkulkarnistannie: sounds good!! you guys rock :)16:58
stanniesince he needs PUT/POST etc for LP in the functionnal test he started on LP :)16:58
noorulYes!16:58
adrian_ottodevkulkarni: they are in the same ballbpark. I think there is a good opportunity for us to work together16:58
*** tsufiev has joined #openstack-meeting-alt16:58
*** _nadya_ has quit IRC16:58
adrian_ottoI'm convinced that neither project wants unnecessary overlap, so it makes sense to coordinate efforts to the extent convenient16:59
noorulwe were discussing thins the othe rday16:59
gokrokveadrian_otto: Agree. There is a lot of synergy between the projects.16:59
*** ativelkov has joined #openstack-meeting-alt16:59
devkulkarnigokrove, adrian_otto: sounds good17:00
adrian_ottogokrokve: yes. It might be wise for us to co-author a Wiki page that discusses the similarities17:00
adrian_ottothanks everyone17:00
gokrokveadrian_otto: Sure.17:00
adrian_otto#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Tue Mar  4 17:00:25 2014 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/2014/solum_team_meeting.2014-03-04-16.00.html17:00
*** tomblank has left #openstack-meeting-alt17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/solum_team_meeting/2014/solum_team_meeting.2014-03-04-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/solum_team_meeting/2014/solum_team_meeting.2014-03-04-16.00.log.html17:00
*** noorul has left #openstack-meeting-alt17:00
sergmelikyano/17:00
*** paulmo_ has left #openstack-meeting-alt17:00
*** rajdeep_ has quit IRC17:00
*** samstav_ has joined #openstack-meeting-alt17:01
ativelkov#startmeeting murano17:01
openstackMeeting started Tue Mar  4 17:01:14 2014 UTC and is due to finish in 60 minutes.  The chair is ativelkov. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: murano)"17:01
openstackThe meeting name has been set to 'murano'17:01
ativelkovHi folks17:01
ruheHi!17:01
ativelkovA quick check who is present, please?17:01
tsufievhello!17:01
*** ycombina_ has left #openstack-meeting-alt17:01
*** aratim has left #openstack-meeting-alt17:01
*** datsun180b has left #openstack-meeting-alt17:02
sergmelikyano/17:02
*** devkulkarni has left #openstack-meeting-alt17:02
*** sparkycollier has quit IRC17:02
ativelkovOk, let's begin17:03
IgorYozhikovHi17:03
ativelkov#link https://wiki.openstack.org/wiki/Meetings/MuranoAgenda#Agenda17:03
ativelkov#topic AI review17:03
*** openstack changes topic to "AI review (Meeting topic: murano)"17:03
ativelkovWe have just a few of AIs for today17:03
ativelkovativelkov to create the remaining blueprints targeting 0.517:03
ativelkovThe bluepwints and roadmap were created17:03
ativelkovthanks to sergmelikyan for assistance with this17:04
*** bdpayne has joined #openstack-meeting-alt17:04
*** samstav has quit IRC17:04
ativelkov#link http://wiki.openstack.org/wiki/Murano/Roadmap#Version_0.5_.28end_of_March.2C_2014.29 - this is the updated roadmap17:04
ativelkovIt turns our we are going to have the biggest release ever17:04
*** alexheneveld has quit IRC17:04
ativelkovThe next ai was low priority: tsufiev to look at Marconi (low priority task)17:05
*** slagle has joined #openstack-meeting-alt17:05
tsufievhaven't started yet17:05
ativelkovI see17:05
gokrokveHi17:05
ativelkovcould you please create a BP for this?17:05
katyaferventHi guys17:05
ativelkovhi17:05
ruheativelkov: do you mind if i link my bp repository-reorganization on this wiki page?17:05
tsufievativelkov: yes, will do17:05
*** jdob has joined #openstack-meeting-alt17:06
ativelkovruke - sure, please do17:06
ativelkov#action ruhe to add repository-reorganization BP to roadmap17:06
*** alexheneveld has joined #openstack-meeting-alt17:06
ativelkov#action tsufiev to create a BP on Marconi usage17:06
*** alazarev has joined #openstack-meeting-alt17:06
*** sparkycollier has joined #openstack-meeting-alt17:07
ativelkovnext ai17:07
ativelkovativelkov to update the incubation statuspad17:07
ativelkovIt is updated17:07
ativelkov#link http://etherpad.openstack.org/p/murano-incubation-status17:07
*** doug_shelley66 has quit IRC17:07
ativelkovThe etherpad link is added to our Incubation page on wiki17:08
ativelkov#link http://wiki.openstack.org/wiki/Murano/Incubation17:08
ativelkovWe are done with AIs, I guess17:08
ativelkovNext topic :)17:09
ativelkov#topic Roadmap review for Murano 0.517:09
*** openstack changes topic to "Roadmap review for Murano 0.5 (Meeting topic: murano)"17:09
ativelkovSo, the roadmap is updated17:09
*** doug_shelley66 has joined #openstack-meeting-alt17:09
ativelkovI've structured it in several dimensions17:09
katyaferventNow it's more clear)17:09
*** markwash has joined #openstack-meeting-alt17:10
ativelkovFirst part is feature-based, second is split by modules, third one is infrustructure-related.17:10
ativelkovThe latter is mostly needed to simplify our incubation17:10
ativelkovIt's quite long, so I don't want to repeat it here: I'd rather answer the questions if somebody have them17:11
ruheativelkov: should we create BPs for the last 3 infra items? maybe they exist already?17:11
ativelkovruhe: yes, I am sure we need them17:12
*** khyati has joined #openstack-meeting-alt17:12
*** khyati has quit IRC17:12
ruheativelkov: then you can add one more AI for me :)17:12
*** Leonr has joined #openstack-meeting-alt17:13
ativelkovdoes anybody know if launchpad allows to differentiate "tasks", "use-cases" and "feature improvements"?17:13
*** nati_ueno has quit IRC17:13
*** ozstacker has joined #openstack-meeting-alt17:13
ativelkov#action ruhe to create BPs for infrustructure-related items in roadmap17:13
*** rwsu has joined #openstack-meeting-alt17:14
*** dprince has joined #openstack-meeting-alt17:14
ativelkovAny other questions on the roadmap?17:14
ativelkovOk, then let's proceed17:14
ativelkov#topic MuranoRepository v2 API17:15
*** openstack changes topic to "MuranoRepository v2 API (Meeting topic: murano)"17:15
ativelkovI'd pass the word to katyafervent who designed this API17:15
ativelkovkatyafervent, could you give an update?17:16
*** noslzzp has quit IRC17:16
katyaferventWell, we have designed it collaboratively I just documented it17:16
*** paulczar has left #openstack-meeting-alt17:16
*** jcoufal has joined #openstack-meeting-alt17:16
*** adrian_otto has left #openstack-meeting-alt17:17
katyaferventHere http://docs.muranorepositoryapi.apiary.io/ it could be found17:17
katyaferventso we need to approve it together with the community and it will be ready for an implementation17:17
ativelkov#link http://docs.muranorepositoryapi.apiary.io/ - docs for the muranorepository17:18
ruhekatyafervent: where should i post my comments - mailing list?17:18
katyaferventAlso we decided do not to switch for Pecan for now17:18
tsufievkatyafervent: is it possible to use apiary for discussion?17:18
*** samstav_ has quit IRC17:18
ativelkovkatyafervent: which engine should we use?17:18
katyaferventruhe, you can post comment directly on that page, etherpad or mailing list17:18
*** samstav has joined #openstack-meeting-alt17:19
katyaferventhttps://etherpad.openstack.org/p/muranorepository-api17:19
katyaferventhere is the etherpad for a discussion17:19
ativelkovI would prefer to use community-approved ways of discussing17:19
ativelkovso, etherpad should be fine17:19
katyaferventthat is etherpad, right?17:19
*** baoli has quit IRC17:19
katyaferventOk)17:19
ativelkovYes17:19
katyaferventWe will stay with Flask17:20
katyaferventRight?17:20
ativelkovI've already added some notes to the etherpad17:20
tsufievativelkov: ok, just curious )17:20
*** _nadya_ has joined #openstack-meeting-alt17:20
ativelkov#info Flask to be used to implement v2 api of murano metadata repository17:20
katyaferventThat's it for v2 API17:21
* ozstacker is away: I'm out smoking crack with triplecheesesina. how we roll.17:21
katyaferventleave your comments on the etherpad page17:21
* ozstacker is back (gone 00:00:07)17:21
*** muralia has left #openstack-meeting-alt17:21
ativelkovAny questions on the current api draft?17:21
*** akuznetsova_ has joined #openstack-meeting-alt17:22
ativelkovSo, then I'd suggest to postpone this discussion to the next meeting - I hope more people will read the drafts and have more questions17:22
katyaferventativelkov, good idea17:23
*** derekh has joined #openstack-meeting-alt17:23
*** derekh has quit IRC17:23
*** sarob_ has joined #openstack-meeting-alt17:23
ativelkovnext topic17:23
ativelkov#topic Commands/Events discussion17:23
*** openstack changes topic to "Commands/Events discussion (Meeting topic: murano)"17:23
ativelkovgokrokve: please, drive this17:24
gokrokveSure.17:24
*** alexheneveld has quit IRC17:24
*** Haiying has joined #openstack-meeting-alt17:24
*** luqas has quit IRC17:24
gokrokveMurano needs to provide a way for extarnal tools to call specific action of the application.17:24
*** _nadya_ has quit IRC17:25
gokrokveThe simplest example is backup action.17:25
gokrokveCalled by Mistral service, for example.17:25
gokrokveThere is a BP to add an ability to register event hooks capability in Murano DSL for application definitions.17:26
ativelkovWhy do we need some additional hooks?17:26
gokrokveEach application\class can register a set of actions which will be available to call from the outside17:26
ativelkovFrom the DSLs point of view any public method of the application can be called from outside. Why do you need to "register" something?17:27
gokrokveI am not saying that they are additional. A callable hook is a term to describe something which is exposed to outside17:27
gokrokveBecause you need to support this on API level17:27
sergmelikyanbut support on API level also does not need any registration17:28
ativelkovfor now we have an API endpoint like /v1/environments/%env_id%/deploy17:28
gokrokvefor users the term event hook is understandable. The term public action is not self obvious for user and can be a source of wrong exposing by application developer who considers public method from OOP world17:28
ativelkovthis eventually calls a "deploy" action for the given env17:29
sergmelikyanWe can call this actions/commands/events by uri like ativelkov shown above17:29
ativelkovThere is one point here though17:29
*** caleb_ has quit IRC17:29
ativelkovThese APIs - as external connection points - are actually part of CLOUD interface17:30
ativelkovnot the application's17:30
*** sc68cal has quit IRC17:30
gokrokveHow user will get a list of actions available. How cloud admin ot user can prevent call to this action17:30
ativelkovSo, I would say that the cloud administrator should be responsible for allowing or forbidding to call these APIs17:30
*** sc68cal has joined #openstack-meeting-alt17:31
ativelkovI think about the following two use-cases17:31
ativelkov1) Admin's case17:31
gokrokveSure. That is why I suppose to add a well defined entity with controllable access.17:31
ativelkovFor a given application-package administrato may inspect the list of public actions17:31
ativelkovfor each of these actions administrator may enable or disable external communication17:32
ativelkovand even probably specify the URL17:32
ativelkovor define a notification topic if we use notification-based APIs instead of REST17:32
*** derekh has joined #openstack-meeting-alt17:32
ativelkovThen, a second case17:32
ativelkov2) user's17:32
sergmelikyangokrokve, i think first level of control should be available to application publisher. I am not sure that there is a reason for cloud administrator to interfere here17:33
ativelkovUser deploya an application from this package17:33
gokrokveWhat about user? Ex an example, I deployed an application which has public method backup. I don't want this method to be called as I did not prepare backup env. How I can disable it?17:33
*** cody-somerville has joined #openstack-meeting-alt17:33
*** markwash has quit IRC17:33
sergmelikyanSince all action are are done on behalf of the user, using his\ resources.17:34
ativelkovFor a deployed application user may see a list of endpoints (call them "hooks" if you wish) which we configured by admin17:34
ativelkovand then use them as he wishes17:34
ativelkovsergmelikyan: application publisher may not be aware about the cloud environment and its capabilities17:34
sergmelikyangokrokve, there could not be actions outside of the application/environment17:34
gokrokveativelkov: This will require admin to read the application DSL and in advance figure out all use cases for users.17:35
gokrokveI don't think that this will work.17:35
sergmelikyanativelkov, sure but cloud administrator is not aware about which action what capabilities require17:35
ativelkovThat's a good point, I agree17:35
*** hockeynut has joined #openstack-meeting-alt17:35
ativelkovBut I don't think that app publisher can define this alone as well17:35
sergmelikyangokrokve, but I don't see how registering action in API gives any benefits17:36
*** sc68cal has quit IRC17:36
ativelkovsergmelikyan: +117:36
*** stanlagun has joined #openstack-meeting-alt17:36
ativelkovactually, "registered event" will be just additional keyword to the method declaration17:36
gokrokveSo. application developer will expose as much as possible to the outside to have a flexibility. User will do a fine tune of what he wants to use and what should be prohibited in his environment.17:36
*** sc68cal has joined #openstack-meeting-alt17:36
sergmelikyangokrokve, who is "user" that you are mentioning?17:37
gokrokvesergmelikyan: tha actual implementation can be different. This BP just shows the requirement of:17:37
gokrokve1) ability to list hook available for application17:37
gokrokve2) enable\disable there hook in his particular deployment17:37
gokrokveUser is a person who deployms an app in his environment17:38
ativelkovI've got your point17:38
gokrokveAs I said, app developer will tend to expose as much as possible17:39
sergmelikyanDo you mean that action are available to someone that does not have any access to actual deployed environment?17:39
gokrokveUser will tend to restrict as much as possible allowing anly hooks which he actually uses17:39
ativelkovI just don't like the term "hook"17:39
sergmelikyangokrokve, what reasons to restrict?17:40
gokrokveYou can do this by exposing actions directly. But there should be API call to list them and enable them17:40
ativelkovAs these are just a publicly available actions17:40
sergmelikyanpublicly?!17:40
gokrokvesergmelikyan: because you can break something17:40
ativelkovwell, I mean, from outside of the environment17:40
sergmelikyanWhat reason may be to have them publicly available?17:40
sergmelikyanIf resources to which this actions/commands apply available only to the user?17:41
ativelkovsergmelikyan: I mean there are 3 types of accessability for class actions17:41
gokrokvesergmelikyan: these actions are exposed to outside. someone sends a request to this hook and Murano will perform action which may be undesired from user perspective17:41
ativelkov1) private - i.e. the actions which are called only by other actions of this class17:41
ativelkov2) old-sense public (you may call them "internal" , which is similar to C#) - actions which may be called by other classes of this environment17:42
gokrokvesergmelikyan: because 3rd party systems not necesserely integrated with keystone17:42
ativelkov3) gokrokve-sense public (or "hooks") - to allow calling them via murano-api or notifications17:43
* ozstacker is away: off to smoke some crack with triplecheesesina17:43
* ozstacker is back (gone 00:00:01)17:43
ativelkovLike, ceilometer will call "scaleUp" action17:43
ativelkovso, scaleUp action is publicly available via some API17:44
sergmelikyanbut ceilometer could not call this action without user authentication - resources are money17:44
*** troytoman-away is now known as troytoman17:44
ativelkovNice point17:44
ativelkovThis means that the user - when generating a URL for this action - may specify some secret key there17:44
*** jaypipes has quit IRC17:45
*** jraim_ has joined #openstack-meeting-alt17:45
ativelkovSo, the actual method will be called by calling muranohost/api/v2/enviroments/%env_id%/%app_id%/event_name/?token=...17:46
ativelkovwhere the token is generated by user's request17:46
ativelkovWe may think about using barbican to share this secret17:46
ativelkovBut this is a long-term goal17:46
ativelkovWe need a simple concept to begin with17:47
*** Haiying has quit IRC17:47
ativelkovI would still think about admin's ability to restrict the usage of the public actions for the whole package17:48
ativelkovBut this is also just a desired option17:48
ativelkovIn general I like gokrokve's proposal17:48
*** mwagner_lap has joined #openstack-meeting-alt17:49
ativelkovAny other concerns about this topic?17:49
gokrokvelet's move on.17:49
ativelkovSo, have we agreed that this feature is needed?17:49
gokrokveWhat is about devstack gate?17:50
gokrokveFeature itself is needed. I have customer's demand for it.17:50
ativelkov#agreed to have a public action discovery and enablence17:50
ativelkov#topic Open discussion17:50
*** openstack changes topic to "Open discussion (Meeting topic: murano)"17:50
sergmelikyanI think in case of direct control over which method may be called by what service we need some way to register specific action under specific (i think random) URI with specific access token that can be shared with one or more applications. Simularly how it is done in many existing authentication systems.17:51
ativelkovsergmelikyan: yes, exactly17:51
sergmelikyanAnd this is should be done on methods marked somehow as 'public/external'17:51
*** vish1 has joined #openstack-meeting-alt17:52
*** doug_shelley66 has quit IRC17:52
ativelkovyup17:52
ativelkovSo, the devstack gate. That's mostly a question to tnurlygayanov17:52
*** doug_shelley66 has joined #openstack-meeting-alt17:52
ativelkovafaik, there are two patchsets waiting: one in infra, another one in our repo17:52
*** chandan_kumar has quit IRC17:53
*** zns has quit IRC17:53
ativelkovThe links can be found in incubation-status etherpad17:53
*** jraim has quit IRC17:53
*** vishy has quit IRC17:53
*** vish1 is now known as vishy17:53
*** jraim_ is now known as jraim17:53
ativelkovprobably tnurlygayanov can give more update on this. Timur?17:53
tnurlygayanovhm )17:53
tnurlygayanovhi there )17:53
tnurlygayanovyes, we have devstack scripts and functional tests for devstack gates17:54
tnurlygayanovand we just wainting for aprove17:54
tnurlygayanovHere the link https://review.openstack.org/#/c/75078/17:55
*** Ranjitha has joined #openstack-meeting-alt17:55
ruhetnurlygayanov: there are some unresolved comments in your patch https://review.openstack.org/#/c/74998/17:55
tnurlygayanovand also this https://review.openstack.org/#/c/74998/17:55
tnurlygayanovyes, I will fix it17:55
*** _nadya_ has joined #openstack-meeting-alt17:55
*** gokrokve has quit IRC17:55
tnurlygayanovDmitry Teselkin will help me with it17:55
*** sarob_ has quit IRC17:55
tnurlygayanovI hope )17:55
*** gokrokve has joined #openstack-meeting-alt17:56
*** sarob_ has joined #openstack-meeting-alt17:56
*** arnaud has joined #openstack-meeting-alt17:56
ativelkovGood, sounds nice17:56
ativelkovAny other questions?17:57
*** hockeynut has quit IRC17:57
stanlagunSorry for being late, but can we schedule hangout to discuss event handling? This seems to be much wider topic17:57
ativelkovstanlagun: we may do it in IRC, so others may join17:58
stanlagunAnd life-cycle management in general17:58
*** noslzzp has joined #openstack-meeting-alt17:58
ativelkovwe can make it tomorrow in murano channel17:58
*** alexheneveld has joined #openstack-meeting-alt17:58
stanlagunothers can join hangout too17:58
ativelkovWe'll IRC is a common way17:59
ativelkovWe may start in IRC and will move to hangout if everybody are ok with that17:59
ativelkovI'll schedule a meeting and send an invite17:59
ativelkovWe are running out of time17:59
* ozstacker is away: 17:59
ativelkovSo, just a reminder: TC will be reviwing our incubation request today18:00
ativelkovat 20:00 UTC18:00
ativelkovAll who are interested may join #openstack-dev18:00
ativelkovThanks for joining, bye )18:00
katyaferventOk)18:00
*** ozstacker has quit IRC18:00
ativelkov#endmeeting18:00
katyaferventbb18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Tue Mar  4 18:00:41 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/murano/2014/murano.2014-03-04-17.01.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/murano/2014/murano.2014-03-04-17.01.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/murano/2014/murano.2014-03-04-17.01.log.html18:00
*** gokrokve has quit IRC18:00
*** ozstacker has joined #openstack-meeting-alt18:01
*** caleb_ has joined #openstack-meeting-alt18:01
*** akuznetsova_ has quit IRC18:01
*** gokrokve has joined #openstack-meeting-alt18:01
*** jcoufal_ has joined #openstack-meeting-alt18:02
*** ozstacker has quit IRC18:02
*** balajiiyer has joined #openstack-meeting-alt18:03
*** tsufiev has quit IRC18:03
*** _nadya_ has quit IRC18:03
*** jcoufal has quit IRC18:05
*** Haiying has joined #openstack-meeting-alt18:06
*** samstav has quit IRC18:07
*** jgallard has quit IRC18:08
*** samstav has joined #openstack-meeting-alt18:08
*** colinmcnamara has joined #openstack-meeting-alt18:09
*** yamahata__ has joined #openstack-meeting-alt18:10
*** yamahata has quit IRC18:14
*** _nadya_ has joined #openstack-meeting-alt18:14
*** noslzzp has quit IRC18:16
*** yogesh has joined #openstack-meeting-alt18:18
*** hockeynut has joined #openstack-meeting-alt18:19
*** eankutse has quit IRC18:21
*** nati_ueno has joined #openstack-meeting-alt18:22
*** nati_ueno has quit IRC18:22
*** eankutse has joined #openstack-meeting-alt18:23
*** nati_ueno has joined #openstack-meeting-alt18:23
*** gokrokve has quit IRC18:25
*** gokrokve has joined #openstack-meeting-alt18:25
*** gokrokve has quit IRC18:29
*** sparkycollier has quit IRC18:29
*** jaypipes has joined #openstack-meeting-alt18:30
*** Ranjitha has quit IRC18:30
*** michael-yu has joined #openstack-meeting-alt18:30
*** balajiiyer has quit IRC18:33
*** markwash has joined #openstack-meeting-alt18:35
*** jaypipes has quit IRC18:36
*** baoli has joined #openstack-meeting-alt18:37
*** baoli has quit IRC18:37
*** baoli has joined #openstack-meeting-alt18:38
*** nacim_ has quit IRC18:40
*** ramashri has quit IRC18:42
*** khyati has joined #openstack-meeting-alt18:43
*** ycombina_ has joined #openstack-meeting-alt18:44
*** tchaypo has joined #openstack-meeting-alt18:46
*** gokrokve has joined #openstack-meeting-alt18:50
*** michael-yu has quit IRC18:51
*** johnthetubaguy has quit IRC18:51
*** balajiiyer has joined #openstack-meeting-alt18:53
*** jaypipes has joined #openstack-meeting-alt18:53
*** balajiiyer1 has joined #openstack-meeting-alt18:55
*** jistr has joined #openstack-meeting-alt18:57
*** akrivoka has joined #openstack-meeting-alt18:57
*** balajiiyer has quit IRC18:58
*** pbelanyi has joined #openstack-meeting-alt18:59
*** sgrasley has joined #openstack-meeting-alt18:59
*** morazi has joined #openstack-meeting-alt18:59
*** rlandy has joined #openstack-meeting-alt18:59
*** Haiying has quit IRC18:59
*** bknudson has joined #openstack-meeting-alt19:00
*** ccrouch has joined #openstack-meeting-alt19:02
*** bknudson has left #openstack-meeting-alt19:02
jistro/19:03
*** jogo has joined #openstack-meeting-alt19:03
marios\o19:04
*** stanlagun has left #openstack-meeting-alt19:04
jristo/19:04
*** alexheneveld has quit IRC19:05
*** michael-yu has joined #openstack-meeting-alt19:05
*** zns has joined #openstack-meeting-alt19:06
jristhmm19:06
jristI wonder if it is off due to the mid march meetup19:06
tchaypolifeless is currently talking at a whiteboard19:06
*** noslzzp has joined #openstack-meeting-alt19:06
jristlol19:07
tchaypospamaps is fixing ci last i heard19:07
tchaypoyep, still going at it19:07
*** sballe has quit IRC19:07
*** ycombina_ has quit IRC19:07
jistrlifeless: will there be a meeting?19:07
*** Ranjitha has joined #openstack-meeting-alt19:09
*** pblaho has joined #openstack-meeting-alt19:10
jistrtchaypo: if you have lifeless there, could you please pass my question ^19:10
pblaho\o19:10
jistro/19:10
mariosjistr: matty dubs said he didn't think so mate (from what it looks like there)19:12
jistrmarios: ok thanks19:12
mariosnight guys ;)19:12
jistrgood night19:12
pblahodo we have meeting now?19:13
jistrpblaho: most probably there won't be a meeting today19:14
pblahojistr: ah.. ok... will see19:14
*** balajiiyer1 has left #openstack-meeting-alt19:15
*** _nadya_ has quit IRC19:15
lsmolahello19:16
*** gokrokve_ has joined #openstack-meeting-alt19:17
*** gokrokve has quit IRC19:21
*** SumitNaiksatam has joined #openstack-meeting-alt19:23
*** bdpayne_ has joined #openstack-meeting-alt19:24
*** amcrn has quit IRC19:24
*** bdpayne has quit IRC19:24
*** _nadya_ has joined #openstack-meeting-alt19:27
*** ycombina_ has joined #openstack-meeting-alt19:29
*** lsmola has quit IRC19:35
*** pbelanyi has quit IRC19:36
*** _nadya_ has quit IRC19:36
*** jcoufal_ has quit IRC19:37
* pblaho leaving...19:38
pblahoo/19:38
*** pblaho has quit IRC19:38
*** baoli has quit IRC19:38
*** rlandy has left #openstack-meeting-alt19:40
*** baoli has joined #openstack-meeting-alt19:41
*** baoli has quit IRC19:41
*** baoli has joined #openstack-meeting-alt19:41
*** ramashri has joined #openstack-meeting-alt19:46
*** arborism has joined #openstack-meeting-alt19:47
*** arborism is now known as amcrn19:47
*** kebray has joined #openstack-meeting-alt19:55
*** banix has joined #openstack-meeting-alt19:59
*** _dim has joined #openstack-meeting-alt19:59
*** catohornet has joined #openstack-meeting-alt20:00
*** Sukhdev has joined #openstack-meeting-alt20:00
*** denis_makogon_ has joined #openstack-meeting-alt20:01
*** IlyaE has joined #openstack-meeting-alt20:02
*** ycombina_ has quit IRC20:02
*** kebray_ has joined #openstack-meeting-alt20:02
*** gyee has quit IRC20:03
*** kebray_ has quit IRC20:04
*** chadlung has joined #openstack-meeting-alt20:04
*** kebray has quit IRC20:05
*** kebray has joined #openstack-meeting-alt20:05
*** esker has joined #openstack-meeting-alt20:07
*** denis_makogon has quit IRC20:09
*** denis_makogon_ is now known as denis_makogon20:09
*** dmakogon_ has joined #openstack-meeting-alt20:09
*** rbrady has joined #openstack-meeting-alt20:13
*** jcoufal has joined #openstack-meeting-alt20:14
*** shakayumi has quit IRC20:17
*** shakayumi has joined #openstack-meeting-alt20:19
*** jistr has quit IRC20:20
*** colinmcnamara has quit IRC20:25
*** Ranjitha has quit IRC20:25
*** kebray_ has joined #openstack-meeting-alt20:30
*** markwash has quit IRC20:32
*** kebray has quit IRC20:33
*** roeyc has joined #openstack-meeting-alt20:36
*** ramashri has quit IRC20:37
*** alazarev has quit IRC20:37
*** noslzzp has quit IRC20:38
*** _dim has quit IRC20:39
*** michael-yu has quit IRC20:40
*** saikrishna_ has quit IRC20:40
*** roeyc has quit IRC20:41
*** sparkycollier has joined #openstack-meeting-alt20:42
*** jcooley_ has quit IRC20:43
*** jaypipes has quit IRC20:44
*** markwash has joined #openstack-meeting-alt20:45
*** caleb_ has quit IRC20:45
*** esker has quit IRC20:48
*** roeyc has joined #openstack-meeting-alt20:48
*** mattgriffin has quit IRC20:49
*** caleb_ has joined #openstack-meeting-alt20:50
*** cody-somerville has quit IRC20:50
*** bcrochet has quit IRC20:51
*** chadlung has quit IRC20:51
*** bcrochet has joined #openstack-meeting-alt20:52
*** chadlung has joined #openstack-meeting-alt20:52
*** hockeynut has quit IRC20:55
*** akrivoka has quit IRC20:55
*** mattgriffin has joined #openstack-meeting-alt20:55
*** jcoufal has quit IRC20:58
*** sparkycollier has quit IRC20:58
*** tchaypo has left #openstack-meeting-alt21:00
*** bcrochet has quit IRC21:01
*** Ranjitha has joined #openstack-meeting-alt21:02
*** michael-yu has joined #openstack-meeting-alt21:03
*** bcrochet has joined #openstack-meeting-alt21:03
*** jcoufal has joined #openstack-meeting-alt21:03
*** eanxgeek is now known as eanxgeek|log21:05
*** kebray_ has quit IRC21:08
*** colinmcnamara has joined #openstack-meeting-alt21:09
*** sparkycollier has joined #openstack-meeting-alt21:09
*** bcrochet has quit IRC21:13
*** bcrochet has joined #openstack-meeting-alt21:15
*** flaper87 is now known as flaper87|afk21:20
*** IlyaE has quit IRC21:21
*** esker has joined #openstack-meeting-alt21:22
*** esker has quit IRC21:22
*** esker has joined #openstack-meeting-alt21:23
*** alazarev has joined #openstack-meeting-alt21:23
*** jcooley_ has joined #openstack-meeting-alt21:23
*** larsks has quit IRC21:23
*** sarob__ has joined #openstack-meeting-alt21:26
*** sarob__ has quit IRC21:26
*** chadlung has quit IRC21:26
*** esker has quit IRC21:27
*** julim has quit IRC21:31
*** alazarev has quit IRC21:37
*** alazarev has joined #openstack-meeting-alt21:39
*** arunkant has quit IRC21:43
*** alazarev has quit IRC21:44
*** jcoufal has quit IRC21:50
*** alazarev has joined #openstack-meeting-alt21:51
*** jcoufal has joined #openstack-meeting-alt21:52
*** zns has quit IRC21:52
*** hockeynut has joined #openstack-meeting-alt21:53
*** chadlung has joined #openstack-meeting-alt21:55
*** troytoman is now known as troytoman-away21:55
*** jcooley_ has quit IRC21:57
*** gyee has joined #openstack-meeting-alt21:58
*** lblanchard has quit IRC21:58
*** Sukhdev has quit IRC22:00
*** zns has joined #openstack-meeting-alt22:04
*** troytoman-away is now known as troytoman22:06
*** IlyaE has joined #openstack-meeting-alt22:14
*** BrianB_ has quit IRC22:16
*** eankutse has quit IRC22:17
*** eankutse has joined #openstack-meeting-alt22:17
*** dhellmann is now known as dhellmann_22:18
*** arnaud__ has joined #openstack-meeting-alt22:21
*** ameade has quit IRC22:25
*** colinmcnamara has quit IRC22:25
*** doug_shelley66 has quit IRC22:25
*** arnaud__ has quit IRC22:28
*** larsks has joined #openstack-meeting-alt22:33
*** _nadya_ has joined #openstack-meeting-alt22:37
*** jecarey has quit IRC22:37
*** colinmcnamara has joined #openstack-meeting-alt22:39
*** Ranjitha has quit IRC22:40
*** _nadya_ has quit IRC22:41
*** samstav has quit IRC22:41
*** samstav has joined #openstack-meeting-alt22:42
*** jcooley_ has joined #openstack-meeting-alt22:44
*** chadlung has quit IRC22:46
*** pdmars has quit IRC22:46
*** jecarey has joined #openstack-meeting-alt22:49
*** denis_makogon has quit IRC22:51
*** nati_ueno has quit IRC22:54
*** Ranjitha has joined #openstack-meeting-alt22:54
*** nati_ueno has joined #openstack-meeting-alt22:56
*** banix has quit IRC22:56
*** doug_shelley66 has joined #openstack-meeting-alt22:57
*** amytron_ has joined #openstack-meeting-alt22:58
*** hockeynut has quit IRC22:58
*** amytron has quit IRC22:58
*** amytron_ is now known as amytron22:58
*** yogesh has quit IRC23:00
*** jaypipes has joined #openstack-meeting-alt23:00
*** kgriffs is now known as kgriffs_afk23:00
*** caleb_ has quit IRC23:02
*** roeyc has quit IRC23:03
*** arborism has joined #openstack-meeting-alt23:05
*** amcrn has quit IRC23:06
*** jcoufal has quit IRC23:06
*** shakayumi has quit IRC23:14
*** rbrady is now known as rbrady-afk23:15
*** zns has quit IRC23:19
*** dprince has quit IRC23:19
*** sparkycollier has quit IRC23:20
*** hockeynut has joined #openstack-meeting-alt23:21
*** roeyc has joined #openstack-meeting-alt23:23
*** doug_shelley66 has quit IRC23:23
*** mattgriffin has quit IRC23:23
*** doug_shelley66 has joined #openstack-meeting-alt23:24
*** jergerber has quit IRC23:25
*** doug_shelley66 has quit IRC23:28
*** eankutse1 has joined #openstack-meeting-alt23:28
*** eankutse1 has quit IRC23:28
*** doug_shelley66 has joined #openstack-meeting-alt23:29
*** jcoufal has joined #openstack-meeting-alt23:30
*** samstav has quit IRC23:31
*** walker_ has quit IRC23:31
*** samstav has joined #openstack-meeting-alt23:31
*** eankutse has quit IRC23:32
*** kevinconway has quit IRC23:33
*** david-lyle has quit IRC23:34
*** roeyc has quit IRC23:35
*** Leonr has quit IRC23:39
*** jcoufal has quit IRC23:39
*** dprince has joined #openstack-meeting-alt23:40
*** alazarev has quit IRC23:41
*** jcoufal has joined #openstack-meeting-alt23:41
*** samstav has quit IRC23:41
*** colinmcnamara has quit IRC23:43
*** mwagner_lap has quit IRC23:44
*** markwash has quit IRC23:45
*** kebray has joined #openstack-meeting-alt23:45
*** sarob_ has quit IRC23:46
*** sarob_ has joined #openstack-meeting-alt23:46
*** zns has joined #openstack-meeting-alt23:47
*** xuhanp has joined #openstack-meeting-alt23:53
*** cjellick has quit IRC23:56
*** kebray has quit IRC23:57
*** IlyaE has quit IRC23:58

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