Tuesday, 2014-03-25

*** colinmcnamara has quit IRC00:06
*** openstack has joined #openstack-meeting-alt00:19
*** ChanServ sets mode: +o openstack00:19
*** demorris has joined #openstack-meeting-alt00:19
*** IlyaE has joined #openstack-meeting-alt00:19
*** tedchang has quit IRC00:20
*** tedchang has joined #openstack-meeting-alt00:21
*** IlyaE has quit IRC00:26
*** michael-yu has quit IRC00:26
*** flaper87 is now known as flaper87|afk00:26
*** baoli has joined #openstack-meeting-alt00:27
*** baoli has quit IRC00:28
*** baoli has joined #openstack-meeting-alt00:28
*** colinmcnamara has joined #openstack-meeting-alt00:29
*** alazarev has quit IRC00:33
*** bdpayne has quit IRC00:36
*** salv-orlando has joined #openstack-meeting-alt00:37
*** demorris has quit IRC00:37
*** michael-yu has joined #openstack-meeting-alt00:39
*** jcooley has quit IRC00:45
*** samstav has quit IRC00:45
*** chadlung has quit IRC00:47
*** Barker has joined #openstack-meeting-alt00:49
*** yamahata has joined #openstack-meeting-alt00:55
*** yamahata_ has quit IRC00:56
*** colinmcnamara has quit IRC00:56
*** yamahata_ has joined #openstack-meeting-alt00:56
*** colinmcnamara has joined #openstack-meeting-alt01:04
*** michael-yu has quit IRC01:04
*** colinmcnamara has quit IRC01:05
*** jjmb has joined #openstack-meeting-alt01:05
*** krtaylor has quit IRC01:07
*** bill_az__ has quit IRC01:09
*** krtaylor has joined #openstack-meeting-alt01:11
*** krtaylor has quit IRC01:20
*** malini has quit IRC01:21
*** mwagner_lap has joined #openstack-meeting-alt01:23
*** krtaylor has joined #openstack-meeting-alt01:23
*** richm has quit IRC01:24
*** rwsu has quit IRC01:26
*** mattgriffin has joined #openstack-meeting-alt01:29
*** SumitNaiksatam has joined #openstack-meeting-alt01:29
*** nosnos has joined #openstack-meeting-alt01:29
*** zhiyan_ is now known as zhiyan01:32
*** jjmb1 has joined #openstack-meeting-alt01:40
*** jjmb has quit IRC01:41
*** rwsu has joined #openstack-meeting-alt01:42
*** SumitNaiksatam has quit IRC01:45
*** khyati has quit IRC01:47
*** yamahata_ has quit IRC01:48
*** lenrow has joined #openstack-meeting-alt01:49
*** lenrow has quit IRC01:50
*** yamahata_ has joined #openstack-meeting-alt01:50
*** lenrow has joined #openstack-meeting-alt01:51
*** SumitNaiksatam has joined #openstack-meeting-alt01:52
*** IYozhikov_away has quit IRC01:56
*** IgorYozhikov has joined #openstack-meeting-alt01:56
*** ogelbukh has quit IRC01:57
*** IgorYozhikov is now known as IYozhikov_away01:57
*** katyafervent has quit IRC01:57
*** katyafervent has joined #openstack-meeting-alt01:57
*** denis_makogon has quit IRC01:58
*** denis_makogon has joined #openstack-meeting-alt01:58
*** baoli has quit IRC02:00
*** ogelbukh has joined #openstack-meeting-alt02:00
*** doug_shelley66 has quit IRC02:01
*** xuhanp has joined #openstack-meeting-alt02:01
*** malini1 has joined #openstack-meeting-alt02:03
*** woodster1 has joined #openstack-meeting-alt02:11
*** caleb_ has joined #openstack-meeting-alt02:11
*** mattgriffin has quit IRC02:14
*** beagles has quit IRC02:16
*** malini1 has quit IRC02:18
*** amcrn has quit IRC02:26
*** amytron has joined #openstack-meeting-alt02:28
*** HenryG has joined #openstack-meeting-alt02:29
*** sbalukoff has quit IRC02:31
*** troytoman is now known as troytoman-away02:31
*** mestery has joined #openstack-meeting-alt02:34
*** hockeynut has quit IRC02:34
*** Sukhdev has joined #openstack-meeting-alt02:40
*** Barker has quit IRC02:45
*** mestery has quit IRC02:46
*** banix has joined #openstack-meeting-alt02:46
*** mestery has joined #openstack-meeting-alt02:46
*** Barker has joined #openstack-meeting-alt02:48
*** salv-orlando_ has joined #openstack-meeting-alt02:49
*** salv-orlando has quit IRC02:50
*** salv-orlando_ is now known as salv-orlando02:50
*** banix has quit IRC02:51
*** Barker has quit IRC02:56
*** arnaud__ has quit IRC02:57
*** banix has joined #openstack-meeting-alt03:01
*** zhiyan is now known as zhiyan_03:10
*** zhiyan_ is now known as zhiyan03:11
*** woodster1 has quit IRC03:11
*** david-lyle has joined #openstack-meeting-alt03:17
*** bdpayne has joined #openstack-meeting-alt03:20
*** gokrokve has joined #openstack-meeting-alt03:27
*** woodster1 has joined #openstack-meeting-alt03:28
*** nosnos has quit IRC03:29
*** chandankumar_ has joined #openstack-meeting-alt03:32
*** vkozhukalov has joined #openstack-meeting-alt03:35
*** michael-yu has joined #openstack-meeting-alt03:37
*** chandankumar_ has quit IRC03:40
*** michael-yu has quit IRC03:41
*** bdpayne has quit IRC03:43
*** Sukhdev has quit IRC03:43
*** harlowja_ is now known as harlowja_away03:49
*** gokrokve has quit IRC03:50
*** gokrokve has joined #openstack-meeting-alt03:52
*** banix has quit IRC03:54
*** chandankumar_ has joined #openstack-meeting-alt03:55
*** banix has joined #openstack-meeting-alt03:56
*** gokrokve has quit IRC03:57
*** alazarev has joined #openstack-meeting-alt04:01
*** bdpayne has joined #openstack-meeting-alt04:03
*** banix has quit IRC04:11
*** nati_ueno has quit IRC04:13
*** chandankumar_ has quit IRC04:23
*** michael-yu has joined #openstack-meeting-alt04:23
*** malini has joined #openstack-meeting-alt04:24
*** nosnos has joined #openstack-meeting-alt04:25
*** bdpayne has quit IRC04:26
*** jecarey has quit IRC04:30
*** Sukhdev has joined #openstack-meeting-alt04:32
*** caleb_ has quit IRC04:38
*** nati_ueno has joined #openstack-meeting-alt04:40
*** bdpayne has joined #openstack-meeting-alt04:41
*** malini has quit IRC04:43
*** malini has joined #openstack-meeting-alt04:45
*** alazarev has quit IRC04:48
*** khyati has joined #openstack-meeting-alt04:54
*** yamahata has quit IRC04:58
*** yamahata has joined #openstack-meeting-alt04:58
*** yamahata has quit IRC04:59
*** yamahata has joined #openstack-meeting-alt04:59
*** _nadya_ has joined #openstack-meeting-alt05:01
*** eghobo has joined #openstack-meeting-alt05:01
*** vkozhukalov has quit IRC05:05
*** vkozhukalov has joined #openstack-meeting-alt05:15
*** michael-yu has quit IRC05:19
*** gokrokve has joined #openstack-meeting-alt05:21
*** _nadya_ has quit IRC05:21
*** gokrokve has quit IRC05:25
*** woodster1 has quit IRC05:29
*** IlyaE has joined #openstack-meeting-alt05:31
*** bdpayne has quit IRC05:36
*** dguitarbite has quit IRC05:37
*** garyk has quit IRC05:38
*** vkozhukalov has quit IRC05:39
*** dguitarbite has joined #openstack-meeting-alt05:41
*** _nadya_ has joined #openstack-meeting-alt05:41
*** alazarev has joined #openstack-meeting-alt05:43
*** _nadya_ has quit IRC05:44
*** nati_ueno has quit IRC05:47
*** chandan_kumar has quit IRC05:48
*** nati_ueno has joined #openstack-meeting-alt05:51
*** woodster1 has joined #openstack-meeting-alt06:00
*** SushilKM has joined #openstack-meeting-alt06:02
*** Sukhdev has quit IRC06:04
*** woodster1 has quit IRC06:07
*** woodster1 has joined #openstack-meeting-alt06:10
*** tedchang has quit IRC06:11
*** doug_shelley66 has joined #openstack-meeting-alt06:12
*** woodster1 has quit IRC06:12
*** andreaf has joined #openstack-meeting-alt06:14
*** alazarev has quit IRC06:14
*** mestery has quit IRC06:18
*** michael-yu has joined #openstack-meeting-alt06:22
*** SushilKM has left #openstack-meeting-alt06:25
*** amytron has quit IRC06:28
*** tedchang has joined #openstack-meeting-alt06:45
*** chenchong has joined #openstack-meeting-alt06:45
*** eghobo has quit IRC06:46
*** lsmola_ has quit IRC07:02
*** lsmola_ has joined #openstack-meeting-alt07:02
*** vkozhukalov has joined #openstack-meeting-alt07:03
*** garyk has joined #openstack-meeting-alt07:05
*** eghobo has joined #openstack-meeting-alt07:05
*** andreaf has quit IRC07:08
*** malini has quit IRC07:13
*** IlyaE has quit IRC07:14
*** ityaptin has quit IRC07:16
*** jtomasek has joined #openstack-meeting-alt07:16
*** ttrumm has joined #openstack-meeting-alt07:20
*** gokrokve has joined #openstack-meeting-alt07:21
*** garyk has quit IRC07:25
*** gokrokve has quit IRC07:26
*** khyati has quit IRC07:27
*** lenrow has quit IRC07:27
*** saju_m has joined #openstack-meeting-alt07:30
*** nati_ueno has quit IRC07:37
*** luqas has joined #openstack-meeting-alt07:45
*** flaper87|afk is now known as flaper8707:51
*** michael-yu has quit IRC07:52
*** eghobo has quit IRC07:54
*** nwidell has joined #openstack-meeting-alt08:02
*** jprovazn has joined #openstack-meeting-alt08:10
*** woodster1 has joined #openstack-meeting-alt08:13
*** gusmaskowitz has joined #openstack-meeting-alt08:13
*** woodster1 has quit IRC08:17
*** nwidell has quit IRC08:32
*** d0ugal has joined #openstack-meeting-alt08:34
*** jgallard has joined #openstack-meeting-alt08:35
*** saju_m has quit IRC08:50
*** nwidell has joined #openstack-meeting-alt08:50
*** gusmaskowitz has quit IRC08:52
*** saju_m has joined #openstack-meeting-alt08:52
*** gusmaskowitz has joined #openstack-meeting-alt08:53
*** andreaf has joined #openstack-meeting-alt08:53
*** bogdando has joined #openstack-meeting-alt08:54
*** nacim has joined #openstack-meeting-alt08:55
*** jcoufal has joined #openstack-meeting-alt08:57
*** gokrokve has joined #openstack-meeting-alt09:05
*** gokrokve has quit IRC09:05
*** gokrokve has joined #openstack-meeting-alt09:05
*** sbalukoff has joined #openstack-meeting-alt09:12
*** chandan_kumar has joined #openstack-meeting-alt09:13
*** safchain has joined #openstack-meeting-alt09:15
*** derekh has joined #openstack-meeting-alt09:15
*** tedchang has quit IRC09:17
*** johnthetubaguy has joined #openstack-meeting-alt09:21
*** luqas has quit IRC09:25
*** luqas has joined #openstack-meeting-alt09:29
*** saju_m has quit IRC09:38
*** nosnos has quit IRC09:39
*** andreaf has quit IRC09:49
*** eankutse has joined #openstack-meeting-alt09:54
*** eankutse has quit IRC09:54
*** eankutse has joined #openstack-meeting-alt09:55
*** saju_m has joined #openstack-meeting-alt09:57
*** gusmaskowitz has quit IRC10:06
*** doug_shelley66 has quit IRC10:11
*** doug_shelley66 has joined #openstack-meeting-alt10:11
*** salv-orlando has quit IRC10:14
*** xuhanp has quit IRC10:23
*** eankutse1 has joined #openstack-meeting-alt10:30
*** eankutse has quit IRC10:33
*** markmcclain has joined #openstack-meeting-alt10:39
*** gusmaskowitz has joined #openstack-meeting-alt10:42
*** eanxgeek|log is now known as eanxgeek10:52
*** andreaf has joined #openstack-meeting-alt10:54
*** saju_m has quit IRC11:07
*** saju_m has joined #openstack-meeting-alt11:08
*** saju_m has quit IRC11:09
*** mwagner_lap has quit IRC11:12
*** ttrumm has quit IRC11:15
*** saju_m has joined #openstack-meeting-alt11:15
*** gokrokve has quit IRC11:23
*** jjmb1 has quit IRC11:24
*** gokrokve has joined #openstack-meeting-alt11:34
*** ttrumm has joined #openstack-meeting-alt11:37
*** gokrokve_ has joined #openstack-meeting-alt11:38
*** saju_m has quit IRC11:38
*** saju_m has joined #openstack-meeting-alt11:38
*** gokrokve has quit IRC11:39
*** gokrokve_ has quit IRC11:42
*** demorris has joined #openstack-meeting-alt11:44
*** nwidell has quit IRC11:50
*** jgallard has quit IRC11:51
*** nwidell has joined #openstack-meeting-alt11:54
*** bcrochet has quit IRC11:59
*** bcrochet has joined #openstack-meeting-alt12:01
*** baoli has joined #openstack-meeting-alt12:02
*** harlowja_away has quit IRC12:03
*** pdmars has joined #openstack-meeting-alt12:03
*** gokrokve has joined #openstack-meeting-alt12:10
*** julim has joined #openstack-meeting-alt12:13
*** gokrokve has quit IRC12:19
*** jgallard has joined #openstack-meeting-alt12:19
*** demorris has quit IRC12:20
*** gokrokve has joined #openstack-meeting-alt12:22
*** gusmaskowitz has quit IRC12:22
*** david-lyle has quit IRC12:23
*** markmcclain has quit IRC12:24
*** markmcclain has joined #openstack-meeting-alt12:24
*** markmcclain1 has joined #openstack-meeting-alt12:25
*** yamahata has quit IRC12:27
*** markmcclain2 has joined #openstack-meeting-alt12:27
*** markmcclain2 has quit IRC12:27
*** gokrokve has quit IRC12:28
*** markmcclain2 has joined #openstack-meeting-alt12:28
*** markmcclain has quit IRC12:29
*** markmcclain1 has quit IRC12:29
*** markmcclain2 has quit IRC12:30
*** markmcclain has joined #openstack-meeting-alt12:31
*** gokrokve has joined #openstack-meeting-alt12:32
*** irenab has joined #openstack-meeting-alt12:40
*** saju_m has quit IRC12:41
*** gokrokve has quit IRC12:43
*** gokrokve has joined #openstack-meeting-alt12:43
*** mwagner_lap has joined #openstack-meeting-alt12:46
*** lblanchard has joined #openstack-meeting-alt12:46
*** gokrokve has quit IRC12:47
*** doug_shelley66 has quit IRC12:48
*** irenab has quit IRC12:52
*** luqas has quit IRC12:52
*** rkukura has joined #openstack-meeting-alt12:52
*** gokrokve has joined #openstack-meeting-alt12:53
*** saju_m has joined #openstack-meeting-alt12:55
*** dguitarbite has quit IRC12:56
*** BrianB_ has joined #openstack-meeting-alt12:56
*** dguitarbite has joined #openstack-meeting-alt12:56
*** julienvey has joined #openstack-meeting-alt12:57
*** xuhanp has joined #openstack-meeting-alt12:58
*** julienvey has quit IRC12:58
*** julienvey has joined #openstack-meeting-alt12:58
*** saju_m has quit IRC12:59
*** beagles has joined #openstack-meeting-alt13:00
*** saju_m has joined #openstack-meeting-alt13:00
*** heyongli has joined #openstack-meeting-alt13:02
*** noslzzp has joined #openstack-meeting-alt13:02
*** dprince has joined #openstack-meeting-alt13:03
*** saju_m has quit IRC13:04
baoli#startmeeting PCI passthrough13:05
openstackMeeting started Tue Mar 25 13:05:06 2014 UTC and is due to finish in 60 minutes.  The chair is baoli. Information about MeetBot at http://wiki.debian.org/MeetBot.13:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:05
*** openstack changes topic to " (Meeting topic: PCI passthrough)"13:05
openstackThe meeting name has been set to 'pci_passthrough'13:05
*** saju_m has joined #openstack-meeting-alt13:05
baoliHi13:05
*** heyongli has quit IRC13:07
*** heyongli has joined #openstack-meeting-alt13:07
baoliHi heyongli13:08
*** itzikb has joined #openstack-meeting-alt13:08
heyonglihi13:08
*** irenab has joined #openstack-meeting-alt13:08
irenabhi13:08
baoliHi Irenab13:08
irenabsorry being late, didn't pay attention that was disconnected13:08
baoliWe can start with irenab's doc on use cases13:08
irenabsure13:09
baolihttps://docs.google.com/document/d/1zgMaXqrCnad01-jQH7Mkmf6amlghw9RMScGLBrKslmw/edit13:09
rkukurahi - I’m here, but not able to pay 100% attention13:09
*** saju_m has quit IRC13:09
baolirkukura, thanks for getting up early13:09
rkukurawoke up at 4:00 AM13:10
heyonglitoo early for you13:10
irenabrkukura: appretiate it13:10
*** saju_m has joined #openstack-meeting-alt13:10
*** sadasu has joined #openstack-meeting-alt13:11
*** woodster1 has joined #openstack-meeting-alt13:13
*** eankutse has joined #openstack-meeting-alt13:14
*** eankutse has quit IRC13:14
*** woodster1 has quit IRC13:15
*** eankutse has joined #openstack-meeting-alt13:15
sadasuI was about 9 mins late13:15
sadasunot sure what was discussed13:15
baolisadasu, https://docs.google.com/document/d/1zgMaXqrCnad01-jQH7Mkmf6amlghw9RMScGLBrKslmw/edit13:16
*** julienvey has quit IRC13:16
sadasuI can't gather context from the last 5 mins that I am logged in13:16
*** spzala has joined #openstack-meeting-alt13:16
baoliAny comments on the doc?13:16
irenabsadasu: discussion on use case doc13:17
sadasuI need we need to add information on why and how device selection happens13:18
sadasuI think that would be part of the use case13:18
heyonglifirst things, this is for sriov use case, i'm ok with sriov use case, and for support sriov, there need some other use case to be considerated, and i like to put them to nova side bp for common support13:18
*** ameade has joined #openstack-meeting-alt13:18
irenabsadsu: it is just initial doc to put the list of use cases, we can then enter into more details13:18
heyongliso nova side support be common , include the sriov use case13:18
sadasuireanb: agreed…just giving input on what can be added next13:19
sadasuheyongli: yes, we can add non-sriov use case too13:20
heyonglisadasu, i don't mean add them to this doc13:20
irenabheyongli: agree with you. I just feel that SR-IOV networking devices have quite special use cases13:20
sadasuheyongli: just re-read….lets not spread out info in diff places13:20
heyonglii like to keep the sriov case as sriov, just ensure common pci design can support this13:20
sadasuwe had originally discussed that we will capture all use cases in one place...13:21
*** ChanServ changes topic to "the gerrit event stream is currently hung, blocking all testing. troubleshooting is in progress (next update at 14:00 utc)"13:21
sadasuyou can dive into a lot of depth in a diff doc but lets at least capture all use cases in one place13:21
irenabsadasu: I thought we mean SR-IOV/networking use cases13:21
heyonglii just think,  sriov discuss get sriov use case clear,13:22
heyongliyeah, irenab, +113:22
heyonglipci changes should also keep common pci use case move forward, and i'm here hope to make the pci common part support SRIOV13:23
irenabafter going into details on updated nova bp, I think it has enough details both for generic and SR-IOV use cases13:23
sadasudon't you think at least the top level use cases should be in one place to give the impression we work together?13:23
irenabsadasu: I think Heyongli's bp includes SR-IOV cases from nova perspective13:24
sadasuok…I am lost here...13:24
irenabbut for example mettering use case is something special for networking and not related to nova at all13:24
sadasuI understand that this information exists in other places...13:24
heyonglisadasu, to prevent icehouse's endless discuss keep going, i very want the discussion and work can be parttion easily13:25
sadasuI thought we are coming up with a way to present during the summit...13:25
*** chenchong has left #openstack-meeting-alt13:25
irenabmaybe we need to return to the initial intention form setting new doc to capture SR-IOV use cases13:25
irenab^for13:25
sadasuI thought we are having a generic nova/neutron joint session where we discuss top level use cases, SR-IOV and non-SR-IOV13:26
sadasuput it in a format that would eventually end up in an etherpad13:26
sadasuthen we dive into a lot more detail for SR-IOV in a neutron session and non-se-iov case in nova session13:27
heyonglii doubt and worry a big design will block the process13:27
irenabDo you think non networking SR-IOV case needs discussion?13:27
sadasuexactly for that reason, please don't start with splitting because this big design will affect all use-cases13:27
*** mestery has joined #openstack-meeting-alt13:28
irenabseems the most challanges and requests for changes come from networking cases13:28
*** mestery has quit IRC13:28
irenabsadasu: please suggest how to proceed13:28
sadasuirenab: I am predicting we will have a big discussion about flavor, host aggregate13:29
heyonglisadasu, the design won't impact the use case, the use case impact the design might, so it might ok to keep them split and less couple13:29
*** mestery has joined #openstack-meeting-alt13:29
sadasulets get this taken care of first..that was the biggest blocker for Icehouse13:29
*** demorris has joined #openstack-meeting-alt13:29
*** ChanServ changes topic to "(Meeting topic: PCI passthrough)"13:30
sadasufor that discussion to happen, lets capture all use cases in one place at high level13:30
irenabI think I understand sadasu's concern. Need to take into account both non-networking and networking use cases to impact the overall approach13:30
heyongliagree, but do we already agree the flavor should be there? and for aggregate , it's might be the holder of flavor.13:30
*** doug_shelley66 has joined #openstack-meeting-alt13:30
sadasuafter that point, we can split it and get into more detail for sr-iov13:31
heyongliagree for the biggest blocker13:31
*** gusmaskowitz has joined #openstack-meeting-alt13:31
*** banix has joined #openstack-meeting-alt13:31
baolishould we focus on individual use cases, document them one at a time. and then we can decide to put them together or not.13:31
sadasuI am not picking an approach here…I think we should present them all13:31
irenabbaoli: +113:31
baoliirenab, in that regard, I felt that the doc should provide detailed use cases.13:32
irenabbaoli: agree, it was the initial version to put the list of use cases that should be covered.13:33
sadasuto prove that a particular solution that we are presenting is taking care of all use cases, we should put them all together and present together13:33
*** markmcclain has quit IRC13:34
baoliAlso, I don't think reference to flavor is appropriate because use cases are better not to be tailored to specific implementation at this point.13:34
sadasuby particular solution I am specifically talking about flavor and host aggregate debates again13:34
sadasubaoli: agreed..13:35
sadasuirenab: the doc is talking about flavor in the use cases when that is actually part of a proposed solution13:35
irenabI used term flavor for abstract definition for different categories of devices, just didn't find better name13:35
heyonglii more prefer revise current design, no revolution current design so i prefer a graduate way to achive that,if possible13:35
sadasuwe are actually just looking for a way for the admin to specify a group of devices that satisfy a specific criteria13:36
irenabguys, the doc is open for editing, so  all can add  more use cases or  modify13:36
baoliirenab, so start with a good format to present each use case and people can start adding.13:37
beaglesI admit to being a bit confused. Is there a particular issue with what sadasu is saying? Also is there a particular issue with using irenab's document as a starting point? I feel I am missing something13:38
irenabits possible to add gloassary for the doc and explain that flavor is  group of devices that satisfy a specific criteria . Would it do the job?13:38
*** yamahata has joined #openstack-meeting-alt13:38
sadasubeagles: no issue with irenab's doc13:38
*** hockeynut has joined #openstack-meeting-alt13:39
beaglesI would agree that it would be best if we were "armed" with ideas and information on how respond to hard questions about impacts and how it is all going to hang together13:39
sadasuon the other hand there is a proposal to split use cases into 2 separate docs13:39
sadasuso pushing to capture all of them in irenab's doc13:39
heyongliirenab, that's might just be current flavor? it can not avoid to say how to specify 'criteria' things13:39
baoliFor example, heyongli talks about a use case in one of his recent emails: an image only runs on a certain hardware from a particular vendor.13:40
sadasuheyongli: yes we can talk about flavor in the design section...13:40
beaglesoh.. ahh... mmmm why would we want to do that? We can certainly assemble them into something comprehensive... if they don't mesh, my "feeling" is that we would be missing something.13:40
heyonglisadasu, not just split to 2 docs, i kind of prefer non use case don't impact sriov, if possible, might small bp to achieve our goal.13:40
*** nati_ueno has joined #openstack-meeting-alt13:40
irenabheyongli: I think baoli want to keep the description without stating the approach13:40
beagleskind of a naive and vague point of view... I know :)13:40
sadasunot while specifying use cases…because potentially that problem can be solved in multiple ways, flavor being one of them13:41
sadasubeagles: agreed13:42
*** luqas has joined #openstack-meeting-alt13:42
baoliso the format can be: name, summary, detailed description, if necessary a diagram for illustration purpose.13:42
sadasubaoli: +113:42
irenabbaoli: I'll add the format according to the traditioanl UML use case template, we can drop what is not relevant. Will do it after the meeting13:43
baoliirenab,  that sounds great!13:43
sadasuheyongli: how the BP pans out is different from a consistent design, don't u think?13:44
baoliI hope that people can start adding/commenting to the doc.13:44
irenabDoes some one has more use cases to add or any suggestion on doc organization?13:44
sadasubeagles : +113:44
*** ttrumm has quit IRC13:44
*** ttrumm has joined #openstack-meeting-alt13:45
sadasuireanb: VM with high throughput, no live migration13:45
sadasuVM with medium throughput, with live migration13:45
beaglesirenab, I have some vague ideas on doc organization, but I'd like to ruminate a bit and maybe throw some ideas around instead of wasting meeting time13:45
sadasuVM with mixture of SR-IOV port +PCI passthrough storage device13:45
sadasuVM with one SR-IOV port with regular non-SR-IOV port13:46
beaglesI had a similar issue with the parity work.. a bunch of disjoint pieces spread all over and followed a bunch of ways. I could never find a way that I felt wasn't awkward as hell13:46
irenabbaeagles: would be great13:46
sadasu beagles: +113:47
sadasuireanb: until we figure out the final format, we can add the list of use cases in your doc13:48
*** walker_ has joined #openstack-meeting-alt13:48
baoliso recap: we'll finalize the doc organization, and then people add/comment use cases into the doc.13:49
beaglessadasu, yeah.. I think right now it would be good to keep things in one place and then break out and organize. It is easier than going the other way, where things might get missed13:49
irenabsadasu: great13:49
*** samstav has joined #openstack-meeting-alt13:50
irenabI think the non networking use cases can be in nova bp for now, at least till we figure out the details of networking SR-IOV related use case.13:50
irenabheyongli: what to you think?13:51
heyonglii just don't know if one big design will get core's attention13:52
*** michael-yu has joined #openstack-meeting-alt13:52
*** jecarey has joined #openstack-meeting-alt13:52
irenabmy feeling was that non networking PCI staff was already in and we want to add networking use cases support13:52
heyonglican't agree with you more irenab13:53
irenabbut it can be good to see all use cases defined anyway13:53
heyonglinon networking stuff also need improve, i just don't want it to be part of sriov, but i do like you can take that as a factor13:54
*** balajiiyer has joined #openstack-meeting-alt13:54
*** sadasu_ has joined #openstack-meeting-alt13:54
*** sadasu has quit IRC13:54
*** hockeynut has quit IRC13:54
*** dguitarbite has quit IRC13:54
*** balajiiyer has left #openstack-meeting-alt13:55
beaglesin this phase would it have to be more than a mention of how they don't interfere and are handled in a consistent fashion.. and maybe that it would be a valid test point?13:55
irenabso next step, I'll add template for use case description, anyone adds use cases that are relevant. Am I right?13:56
sadasu_yes13:56
beagless'cool with me13:56
baolicool13:56
heyonglialso fine to me13:56
irenabgreat13:56
*** zns has joined #openstack-meeting-alt13:57
irenabbaoli: wanted to check if you plan some further work on your nova patch till Juno summit13:57
*** colinmcnamara has joined #openstack-meeting-alt13:58
heyongliin case something changed in our discuss, any patch update seems ... i don't know that13:58
baoliirenab, I don't have a plan yet. It purpose is to facilitate integration with neutron13:58
baoliheyongli, please take a look at https://review.openstack.org/#/c/82206/ when you have a chance.13:59
irenabI think it can help to promote it to Juno, nova parts take a lot of time to get in13:59
*** nati_ueno has quit IRC13:59
heyonglibaoli, i look at it today but not feedback yet13:59
heyonglii will spend more time on it14:00
*** michael-yu has quit IRC14:00
sadasu_heyongli: what little BP were you talking about earlier?14:00
baoliheyongli, thanks. we need to come up with a resolution.14:00
heyonglisadasu_, i want to split big bp to small one, if possible14:00
heyongliin my plan14:00
*** caleb_ has joined #openstack-meeting-alt14:00
baolitime is up. I have to end this meeting now. Expecting to see the use case doc format so that we can start contributing.14:01
baoli#endmeeting14:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:01
openstackMeeting ended Tue Mar 25 14:01:38 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:01
beaglescheers14:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-03-25-13.05.html14:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-03-25-13.05.txt14:01
openstackLog:            http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-03-25-13.05.log.html14:01
baolithanks everyone14:01
*** yuyangbj has joined #openstack-meeting-alt14:01
heyonglibye14:01
*** nacim has quit IRC14:02
irenabbye14:02
*** heyongli has quit IRC14:02
sadasu_thanks everyone14:02
*** sadasu_ has quit IRC14:03
*** Barker has joined #openstack-meeting-alt14:04
*** jswarren has quit IRC14:08
*** woodster1 has joined #openstack-meeting-alt14:08
*** amytron has joined #openstack-meeting-alt14:15
*** rkukura has left #openstack-meeting-alt14:22
*** mestery has quit IRC14:24
*** kevinconway has joined #openstack-meeting-alt14:25
*** yuyangbj1 has joined #openstack-meeting-alt14:25
*** woodster1 has quit IRC14:26
*** yuyangbj has quit IRC14:26
*** colinmcnamara has quit IRC14:30
*** david-lyle has joined #openstack-meeting-alt14:31
*** alazarev has joined #openstack-meeting-alt14:32
*** markmcclain has joined #openstack-meeting-alt14:32
*** markmcclain has quit IRC14:32
*** mestery has joined #openstack-meeting-alt14:33
*** markmcclain has joined #openstack-meeting-alt14:33
*** hockeynut has joined #openstack-meeting-alt14:36
*** irenab has quit IRC14:38
*** jswarren has joined #openstack-meeting-alt14:39
*** dprince has quit IRC14:40
*** ttrumm has quit IRC14:40
*** woodster1 has joined #openstack-meeting-alt14:41
*** rramirez has joined #openstack-meeting-alt14:43
*** dprince has joined #openstack-meeting-alt14:53
*** woodster2 has joined #openstack-meeting-alt14:53
*** woodster1 has quit IRC14:53
*** sriram has joined #openstack-meeting-alt14:55
*** cjellick has quit IRC14:56
*** alcabrera has joined #openstack-meeting-alt14:58
*** malini has joined #openstack-meeting-alt14:59
*** kgriffs_afk is now known as kgriffs14:59
*** baoli has quit IRC14:59
*** IlyaE has joined #openstack-meeting-alt15:00
*** cpallares has joined #openstack-meeting-alt15:00
kgriffs#startmeeting marconi15:00
openstackMeeting started Tue Mar 25 15:00:14 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
*** balajiiyer has joined #openstack-meeting-alt15: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
kgriffs#topic roll call15:00
*** openstack changes topic to "roll call (Meeting topic: marconi)"15:00
kgriffso/15:00
balajiiyero/15:00
*** oz_akan_ has joined #openstack-meeting-alt15:00
*** amitgandhi has joined #openstack-meeting-alt15:00
flwang\o/15:00
cpallareso/15:00
alcabrera\\o//15:00
oz_akan_hey15:00
sriram\o o/15:00
malinio/15:00
* alcabrera notices all of Marconi's team members are named after ascii-waving figures15:01
megan_wo/15:02
alcabrera#link https://wiki.openstack.org/wiki/Meetings/Marconi#Agenda15:02
kgriffsthanks everyone for coming!15:02
kgriffs#topic graduation review15:02
*** openstack changes topic to "graduation review (Meeting topic: marconi)"15:02
kgriffsso, a few gaps I wanted to mention that weren't called out elsewhere15:03
*** luqas has quit IRC15:03
kgriffsfirst, everyone please sign up here: https://ask.openstack.org15:03
amitgandhio/15:03
kgriffsand watch the "marconi" tag. I think it will email you15:03
kgriffsparticipation there is a graduation requirement15:03
kgriffsany questions?15:04
alcabrera#action everyone sign up for ask.openstack.org15:04
* malini signed up now15:04
alcabrera#link https://ask.openstack.org15:04
* kgriffs gives malini +5 bonus points15:04
* sriram is signed up15:04
kgriffsrock on. Like I said, please help me watch for questions there.15:05
malinisriram gets +10 bonus points ;)15:05
kgriffspretty please with a cherry on top15:05
kgriffs:)15:05
balajiiyer*notices marconi is not in the tag cloud*15:05
* alcabrera joined15:05
* sriram woot15:05
balajiiyerneed more questions for marconi ;)15:05
malinibalajiiyer: I see marconi15:05
*** baoli has joined #openstack-meeting-alt15:05
kgriffsbalajiiyer: there are just 1-2 questions so far, but that should be changing over the next several months as we work to get higher visibility15:05
balajiiyermalini: I checked the tag cloud on the home page15:05
* amitgandhi is signed up15:06
kgriffswell, and heck, feel free to post your questions there and encourage friends and family too as well15:06
malinibalajiiyer: my home is probably different from yours ;)15:06
kgriffsif we answer common questions "in the open" we build up a nice FAQ15:06
sriram+115:06
amitgandhiour faq etherpad should move some of it to here15:07
kgriffsso, when people ask something in IRC or on the ML, maybe we should direct them to Ask for certain types of Q's15:07
kgriffsamitgandhi: good idea!15:07
kgriffsanything an end-user or an operator would want to know, I guess15:07
kgriffs#action everyone to cross-post FAQ for end users and operators on ask.openstack.org15:08
kgriffsok, next gap15:09
maliniare we allowed to do tht in ask? i.e Marconi team creating questions and answers vs questions coming from outside Marconi team?15:09
maliniQuestion for ask maybe15:09
*** nacim has joined #openstack-meeting-alt15:09
amitgandhimalini: if its valuable information i say yes15:10
amitgandhiif its a sales pitch then prob not15:10
*** spzala has quit IRC15:10
kgriffsright, no astroturfing or whatever the correct term is15:11
kgriffsbut if it is a good, honest question, no reason to just post there and a different team member can answer15:11
flwangkgriffs: yes, it's just a q&a system can be leveraged to track some useful info15:12
kgriffsIt's basically StackOverflow for marconi15:12
malinicool15:12
flwangkgriffs: +115:12
kgriffsanyway, only ask something there if you've heard the question come up a couple times in the wild and/or encourage the original questioner to post over there15:12
kgriffsok, next gap15:12
kgriffs"Project must provide a 2+ person team that will handle the project specific vulnerability process"15:12
kgriffsI need 2 volunteers for this one15:13
kgriffshttps://wiki.openstack.org/wiki/Vulnerability_Management15:13
*** saju_m has quit IRC15:13
maliniIs this security related?15:13
*** chenchong has joined #openstack-meeting-alt15:13
alcabrerawhat does this even mean?15:13
kgriffsmalini: yes15:13
alcabreraah15:13
alcabrerathanks for the link15:13
*** spzala has joined #openstack-meeting-alt15:13
alcabrera#link https://wiki.openstack.org/wiki/Vulnerability_Management15:13
kgriffsso, they need help with patches, threat modeling, whatever15:13
maliniI emailed sriram who works in OSSG y'day, if he is interested in helping us with Security.15:13
alcabreravery good page15:13
maliniHe is interested in joining us, & will join us in openstack-marconi later (meeting time doesnt work for him)15:14
kgriffsoic15:14
kgriffsso, I can help with this as well15:14
maliniHe might be a good person to help us with the open security bps as well15:14
kgriffsbut, my time is limited. too many fingers in too many pies. :p15:15
kgriffsso, I'd like to still get two other volunteers besides myself15:15
kgriffsok, well, think on it and we will crystalize that committee next week15:15
*** johnthetubaguy has quit IRC15:15
kgriffssound good?15:15
amitgandhimight be good to pull jdp into this too as he has interest (we can talk offline about it kgriffs)15:16
alcabrera+1 for time to think and crystallize15:16
kgriffsamitgandhi: kk15:16
kgriffsamitgandhi: ping me after15:16
alcabreraoh yes, jdp -- good suggestion, amitgandhi15:16
*** johnthetubaguy has joined #openstack-meeting-alt15:16
kgriffs#action crystalize security swat team for Marconi15:16
*** woodster2 has left #openstack-meeting-alt15:16
kgriffsone more gap15:16
kgriffs"Project should have engaged with marketing team to check suitable official name"15:17
kgriffsI asked around and the suggestion was to just show up at their next meeting and ask15:17
* amitgandhi hopes we dont have to change to macaroni15:17
kgriffstheir mailing list is closed to non-subscribers15:17
*** spzala has quit IRC15:17
kgriffsamitgandhi: stop it! You're making me hungry!15:17
alcabreramacaroni and openstack cheese15:18
kgriffsmmmm15:18
sriramhah15:18
flwangOpenStack Messaging Service (Marconi)15:18
*** alazarev has quit IRC15:18
kgriffsmegan_w: do you have time on thursday at 11 central to attend the next marketing team meeting?15:18
megan_wkgriffs: yes, i'll plan to attend15:19
kgriffsok, here is the info on the team and meeting time15:19
kgriffshttps://wiki.openstack.org/wiki/Governance/Foundation/Marketing15:19
kgriffs#link https://wiki.openstack.org/wiki/Governance/Foundation/Marketing15:19
kgriffs#action megan_w to attend marketing meeting15:19
megan_wthanks15:20
kgriffsmegan_w: they should have an open discussion time at the end and we can ask them about that graduation requirement15:20
kgriffsthanks for your help!15:20
*** jjmb has joined #openstack-meeting-alt15:20
megan_wsounds good15:20
megan_wnp15:20
kgriffsI'll try to be there too.15:20
kgriffs#action kgriffs to attend marketing meeting15:21
*** xuhanp has quit IRC15:21
kgriffsok, so those are the remaining gaps that I am aware of at this point.15:21
kgriffsI noticed some more patches to the governance requirements doc, but I think we are already doing those15:22
alcabrera#info gaps summary: ask participation, vulnerability handling team, marketing counsel <-> marconi name15:22
kgriffsotherwise, as everyone is aware, we have been working on an etherpad to collect everyones thoughts on "what's next"15:23
kgriffs#link https://etherpad.openstack.org/p/marconi-incubation-round-215:23
kgriffsplease continue editing and contributing there.15:23
*** noslzzp has quit IRC15:24
kgriffsWe will need to start crystalizing all this soon15:24
*** noslzzp has joined #openstack-meeting-alt15:24
*** mestery has quit IRC15:24
kgriffs#action everyone to provide feedback on the incubation pad and discuss questions/ideas/concerns15:24
kgriffsmake sense?15:24
alcabrerayup15:25
alcabreraI'll take a look some time today. :)15:25
flwangkgriffs: yes15:25
kgriffsthanks!15:25
kgriffs#topic ATL summit15:25
*** openstack changes topic to "ATL summit (Meeting topic: marconi)"15:25
kgriffsanyone have anything they want to mention on this topic?15:25
*** lenrow has joined #openstack-meeting-alt15:26
megan_wi'll be there if you guys need any business-y support15:26
kgriffssweet15:26
malinimegan_w: we need more money ;)15:26
megan_wi'm also working to get some use cases/testimonies together of people using marconi in productions15:26
alcabreralol, malini15:26
*** vkmc has joined #openstack-meeting-alt15:26
*** vkmc has joined #openstack-meeting-alt15:26
flwangmegan_w: is there any sessions about best practice of Marconi?15:27
megan_wflwang: not sure15:27
flwangdeployment, GUI support, operations, etc15:27
kgriffsflwang: you mean an OS talk or workshop?15:27
kgriffssorry15:27
flwangkgriffs: yep15:27
kgriffss/OS/summit15:27
amitgandhioz_akan_ is doing the ops/deployment stuff right?15:27
kgriffsso, I'm glad you brought that up. reminds me that I needed to tell everyone15:27
flwangkgriffs: I'm going to start some work about this, so just curious if there is a session I can get some useful info :D15:28
kgriffsfor whatever reason, not a single one of the proposed talks was accepted by the track chairs15:28
kgriffsand the workshop was accepted as an "alternate" in case a different workshop is cancelled15:28
alcabreraWe have "Hands On w/ Marconi" as an alternate15:28
flwangkgriffs: so? we only have design session slots?15:28
*** cjellick has joined #openstack-meeting-alt15:28
alcabrerayup15:28
amitgandhiflwang: GUI support is almost there - i think horizon work was mostly done, but ran into some keystone related issues...15:28
kgriffsso, we have the following venues15:28
*** jmontemayor has joined #openstack-meeting-alt15:29
kgriffs1. marconi design sessions15:29
kgriffs2. other projects design sessions (several projects are interested in integrating with marconi)15:29
flwangamitgandhi: cool, thanks for that info15:29
flwangamitgandhi: will it be completed in Icehouse?15:29
kgriffs3. there are some kind of 15 minutes talks going on - not sure if they are "summit" or some parallel conference that happens to be in the same location. :p15:30
kgriffsflaper87 is watching for more info about #315:30
amitgandhiflwang: prob not.  last i heard jay-atl was working with flavio on the way marconi - keystone integration was happening.  I think that work has stalled15:30
kgriffs4. Project "Pod". Each project gets a dedicated hang-out / mini unconference table15:30
flwangkgriffs: AFAIK, some companies are interested in porting Marconi in production env, so it would be super cool to have an operations session15:31
kgriffsflwang: oz_akan_ proposed a talk on that. Maybe we can trim it to 15 minutes15:31
kgriffs(to get it into venue #3)15:31
flaper87o/15:32
flwangkgriffs: it would be nice, thanks15:32
flaper87back15:32
kgriffsflwang: I think we should do a few screencasts and put them on the wiki too15:32
flwangkgriffs: good idea, I can work with oz_akan_ to make it happen15:32
kgriffsrock on15:32
kgriffsI added a note to the etherpad15:32
flwangkgriffs: because I'm trying to setup it :)15:32
kgriffsduring Juno I want to totally rock out on our docs15:33
flwangmore production deployment, more feedbacks, more stable15:33
kgriffsflwang: cool, let's get that recorded15:33
flwangkgriffs: love it15:33
*** Duane has joined #openstack-meeting-alt15:33
kgriffseven if it just used pop-up bubbles rather than voice over, that would be super awesome15:33
flaper87actually, lemme take that back. gtg again! (I started the FAQ here https://etherpad.openstack.org/p/draft-marconi-faq add comments )15:33
kgriffsflaper87: ttfn15:34
kgriffs#link https://etherpad.openstack.org/p/draft-marconi-faq15:34
kgriffsspeaking of docs, heh15:34
kgriffsalcabrera, megan_w, malini: can you help with the FAQ?15:34
alcabrerakgriffs: sure thing15:34
kgriffsflwang: you too15:35
malinikgriffs: of course15:35
megan_wsure15:35
kgriffs:D15:35
kgriffs#action core team to contribute to the FAQ15:35
sriram+1 for the FAQ, I'll help around where I can as well.15:35
*** itzikb has quit IRC15:35
malinisriram: wooot15:35
*** jjmb has quit IRC15:36
kgriffs#topic review updates to the API v1.1 spec15:36
*** openstack changes topic to "review updates to the API v1.1 spec (Meeting topic: marconi)"15:36
kgriffsdarn, flaper87 is MIA again.15:36
* kgriffs sad panda15:36
alcabrerawe'll never get to have nice things. :(15:37
kgriffslet's review pop semantics today15:37
alcabreraworks for me15:37
kgriffs"Added new "pop" semantics for claiming and deleting messages in a single request. Note that this should only be used when an application is OK with the risk of missing a message when a worker crashes."15:37
kgriffsso, a little background15:38
kgriffsthis idea arose independently from two sources15:38
*** colinmcnamara has joined #openstack-meeting-alt15:38
kgriffsfirst, was the request to add it because it would make it easier to map marconi semantics to AMQP15:38
*** feleouet has quit IRC15:38
*** Leonr has joined #openstack-meeting-alt15:38
kgriffssecond, I actually spoke with someone who is planning to use Marconi and they requested this feature for processing certain kinds of events, and they were willing to make the durability tradeoff15:39
kgriffsmy first stab at this was adding it to the DELETE messages operation:15:39
kgriffs#link https://wiki.openstack.org/wiki/Marconi/specs/api/v1.1#Delete_Multiple_Messages15:40
alcabrerawould that be a multi-pop, kgriffs?15:40
kgriffsI'd like to get everyones thoughts and suggestions15:40
kgriffsalcabrera: yes, you can set pop=N15:40
alcabreragotcha -- interesting15:40
kgriffsalcabrera: that was also requested by the user15:40
alcabreraso, my initial thoughts15:41
alcabreraare that this POP functionality is valuable15:41
alcabreraI've used a variant of it already15:41
alcabrerawhich a sort of claim and delete one at a atime15:41
flwangkgriffs: is it a new endpoint?15:41
alcabrera**which is a15:41
kgriffsflwang: no, it is adding additional semantics to the existing messages resource15:42
*** krtaylor has quit IRC15:42
flwangdelete-bulk?15:42
flwangor like pop-bulk?15:42
*** betsy has joined #openstack-meeting-alt15:42
kgriffsyeah. basically, you can delete all messages, a few by ID, or N. In the last case, the deleted messages are returned to you, and there is a guarantee that nobody else will delete those same messages.15:43
kgriffs"pop specifies a certain number of messages to pop off the queue, which is equivalent to claiming and deleting those messages atomically (therefore guaranteeing once-and-only-once delivery)"15:44
sriramI think pop makes it much easier to issue a request, rather than supply a large number of ids.15:44
megan_wsriram: agreed15:44
vkmco/ *catching up*15:44
kgriffsdepends on what you are trying to do15:44
alcabreravkmc: :)15:44
kgriffsvkmc: hi!15:45
malinikgriffs: pop will be done in a single call ?15:45
vkmcAdding a pop function certainly simplifies automation, I like that!15:45
alcabreraHTTP DELETE /queues/{q}/messages?ids=[1, 2, 3]&pop=3 -- what would this do?15:45
alcabreradoes 'pop' gather from the front of the queue?15:46
kgriffsmalini: yes, a single call. you trade off the safety of the two-phase claim+delete for improved performance/convenience15:46
flwangkgriffs: yep, what's the http url looks like?15:46
sriramalcabrera: +1 good question15:46
*** markwash has joined #openstack-meeting-alt15:46
vkmcYeah, it may be confusing to use pop with ids15:47
kgriffshttp DELETE marconi.example.org/queues/videos/messages?pop=1015:47
kgriffsif you specify both ids and pop, pop is ignored15:47
maliniBut DELETE currently just returns a 20415:47
kgriffsyou really are supposed to use one or the other15:47
*** SumitNaiksatam has quit IRC15:47
alcabrerahmmm15:47
alcabreratempts me in the direction of a new endpoint15:48
maliniwe probably want to return a message & delete it15:48
kgriffsI'm not super happy about having the exclusive-or semantic, but this was the best I thought of so far short of coming up with a new resource15:48
alcabreraHTTP POST /queues/videos/pop?n=1015:48
alcabreraor even15:48
maliniwhy not just claim?15:48
alcabreraHTTP POST /queues/videos/messages/pop?n=1015:48
maliniHTTP CLAIM /queues/videos/pop?n=1015:49
*** tanisdl has joined #openstack-meeting-alt15:49
alcabrerabecause CLAIM isn't an HTTP verb, malini. :(15:49
malinigrr.. :D15:49
alcabrerahehe15:49
sriramso does popping follow any order here?15:49
maliniI will drink more coffee before next meeting ;)15:49
kgriffsmalini: because the client doesn't want to make two requests, and also this semantic may make it easier to support broker-based backends, in which case I guess we would say for those backends the two-step claim isn't available?15:49
alcabreraI'd love to avoid overloading endpoints. Different functionality should have a different interface.15:50
*** krtaylor has joined #openstack-meeting-alt15:50
kgriffswell, technically, there isn't anything wrong with coming up with custom HTTP verbs, but I know people will say WAH?! if we do that. :p15:50
kgriffsalcabrera: mmm, noted. However, remember this isn't RPC over HTTP either. We have to work in terms of resources, and IDK that a "pop" resource makes any sense.15:51
alcabrerahmmm15:51
*** yuyangbj1 has left #openstack-meeting-alt15:51
*** luqas has joined #openstack-meeting-alt15:51
alcabrerafair enough15:51
kgriffsthere may be another way, don't get me wrong15:51
kgriffswe just need to work within the architectural style we've chosen15:51
amitgandhi+1 for not having a resource called pop15:52
*** eghobo has joined #openstack-meeting-alt15:52
kgriffs#info try to find a way to not have mutually exclusive query string params on a single resource15:52
alcabreraPopResource15:52
alcabreraheh15:52
*** eghobo has quit IRC15:52
kgriffslet me play with it and we can revisit next time15:53
*** eghobo has joined #openstack-meeting-alt15:53
alcabrera+115:53
*** gusmaskowitz has left #openstack-meeting-alt15:53
flwangpop most like an action, not a new resouse15:53
kgriffsyep15:54
flwangso i prefer to don't implement it with a new endpoint15:54
sriramyeah15:54
kgriffsok, last thing - we have a couple days before rc1 is cut.15:54
*** jergerber has joined #openstack-meeting-alt15:54
kgriffsLet's discuss the remaining bugs in #openstack-marconi15:54
kgriffs#topic open discussion15:54
*** openstack changes topic to "open discussion (Meeting topic: marconi)"15:54
malinican we start doing some retros in g+ ?15:55
maliniwhat we are doing well, where we can improve?15:55
maliniespecially focusing around graduation15:55
kgriffsmalini: how often would you propose?15:55
malinievery  3 weeks /month15:56
*** rramirez has quit IRC15:56
*** amotoki_ has joined #openstack-meeting-alt15:56
kgriffsmilestone releases are about every 4 i think15:56
kgriffsthat may be a natural time to do them, but may not be often enough15:56
alcabreraI'm partial to once a month15:57
flwangsounds like reflections :)15:57
alcabreraI really like the idea of a retro/reflections15:57
maliniflwang: yes :)15:57
alcabrerafor team-marconi15:57
*** nwidell has quit IRC15:57
kgriffsso, +1 for retrospectives15:57
flwang+115:57
kgriffswe would have two parts: (1) reflect on our development process and community15:57
kgriffs(2) up-periscope on graduation15:58
megan_w+115:58
malinikgriffs: +115:58
kgriffsmonthly sounds good15:58
alcabrera+115:58
alcabrerain some sense15:58
alcabreraflaper87 is having such a thing in two days15:58
alcabrerathe marconi g+ hangout15:59
maliniBut tht's more of an FAQ , rt?15:59
alcabrerait might be15:59
malinithis is for the team to reflect15:59
alcabreraI've lost track of the vision behind that particular hang out. >.>15:59
alcabreraThough, I like it. :)15:59
kgriffsok, g+ is useful until we get full. Also you trade having logs for higher-bandwidth communication.15:59
*** mestery has joined #openstack-meeting-alt15:59
maliniam ok with anything where we can talk, rather than type15:59
alcabreraand human-to-human voice15:59
kgriffsvisual?15:59
malinivisual wud be nice to have, not mandatory16:00
flwanggoogle hangouts16:00
kgriffs#action set up monthly v&v meetings16:00
alcabrera+116:00
megan_wFWIW, g+ doesn't work great past 8 people16:00
maliniflwang: has a 10 person limit16:00
kgriffs#action kgriffs to set up monthly v&v meetings16:00
kgriffsok, let's continue this chat over in #openstack-marconi16:01
amitgandhiwe'll all hangout by malini's machine16:01
amitgandhi;-)16:01
kgriffs#endmeeting16:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:01
openstackMeeting ended Tue Mar 25 16:01:27 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-03-25-15.00.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-03-25-15.00.txt16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-03-25-15.00.log.html16:01
*** amitgandhi has left #openstack-meeting-alt16:01
alcabreraI'll copy minutes over.16:02
*** Sukhdev has joined #openstack-meeting-alt16:02
kgriffsalcabrera: thanks!16:03
*** alcabrera has left #openstack-meeting-alt16:03
*** SumitNaiksatam has joined #openstack-meeting-alt16:04
*** Sukhdev has quit IRC16:06
*** baoli has quit IRC16:08
*** mestery has quit IRC16:09
*** SumitNaiksatam has quit IRC16:10
*** mestery has joined #openstack-meeting-alt16:10
*** SumitNaiksatam has joined #openstack-meeting-alt16:10
*** baoli has joined #openstack-meeting-alt16:10
*** khyati has joined #openstack-meeting-alt16:12
*** colinmcnamara has quit IRC16:13
*** troytoman-away is now known as troytoman16:15
*** nati_ueno has joined #openstack-meeting-alt16:17
*** troytoman is now known as troytoman-away16:17
*** cpallares has left #openstack-meeting-alt16:17
*** khyati has quit IRC16:18
*** troytoman-away is now known as troytoman16:19
*** khyati has joined #openstack-meeting-alt16:19
*** atiwari has joined #openstack-meeting-alt16:20
*** markwash has quit IRC16:20
*** alazarev has joined #openstack-meeting-alt16:21
*** tedchang has joined #openstack-meeting-alt16:22
*** vkozhukalov has quit IRC16:23
*** markwash has joined #openstack-meeting-alt16:23
*** amytron_ has joined #openstack-meeting-alt16:25
*** amytron has quit IRC16:26
*** amytron_ is now known as amytron16:26
*** Duane has quit IRC16:26
*** Duane has joined #openstack-meeting-alt16:27
*** andreaf has quit IRC16:27
*** tedchang has quit IRC16:28
*** n0ano has quit IRC16:29
*** nati_ueno has quit IRC16:30
*** Duane_ has joined #openstack-meeting-alt16:30
*** troytoman is now known as troytoman-away16:30
*** Duane has quit IRC16:31
*** n0ano has joined #openstack-meeting-alt16:32
*** chenchong has quit IRC16:33
*** chenchong has joined #openstack-meeting-alt16:34
*** rramirez has joined #openstack-meeting-alt16:35
*** alazarev has quit IRC16:35
*** SushilKM has joined #openstack-meeting-alt16:38
*** balajiiyer has quit IRC16:38
*** lenrow has quit IRC16:45
*** rajdeep has joined #openstack-meeting-alt16:46
*** rajdeep has quit IRC16:47
*** alazarev has joined #openstack-meeting-alt16:47
*** markwash_ has joined #openstack-meeting-alt16:48
*** markwash has quit IRC16:49
*** markwash_ is now known as markwash16:49
*** michael-yu has joined #openstack-meeting-alt16:49
*** pballand has joined #openstack-meeting-alt16:49
*** katyafervent2 has joined #openstack-meeting-alt16:53
*** tsufiev_ has joined #openstack-meeting-alt16:54
*** vkmc has quit IRC16:55
*** mattgriffin has joined #openstack-meeting-alt16:55
*** thinrichs has joined #openstack-meeting-alt16:57
*** thinrichs has quit IRC16:57
*** thinrichs has joined #openstack-meeting-alt16:57
*** ativelkov has joined #openstack-meeting-alt16:58
*** igormarnat_ has joined #openstack-meeting-alt16:58
*** IYozhikov_away is now known as IgorYozhikov16:59
ativelkov#startmeeting murano17:00
openstackMeeting started Tue Mar 25 17:00:10 2014 UTC and is due to finish in 60 minutes.  The chair is ativelkov. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: murano)"17:00
openstackThe meeting name has been set to 'murano'17:00
*** jcoufal has quit IRC17:00
tsufiev_hello17:00
ativelkovHi folks. Anybody here for Murano meeting?17:00
ativelkovIdentify yourself please17:00
katyafervent2Hi!17:00
tsufiev_not much...17:01
*** markmcclain1 has joined #openstack-meeting-alt17:01
*** markmcclain1 has quit IRC17:01
sergmelikyano/17:01
*** markmcclain1 has joined #openstack-meeting-alt17:02
*** markmcclain has quit IRC17:02
ativelkovLess people - faster meeting :)17:02
ativelkovWe have agenda here17:02
ativelkov#link https://wiki.openstack.org/wiki/Meetings/MuranoAgenda#Agenda17:02
*** nati_ueno has joined #openstack-meeting-alt17:02
ativelkovNot much agenda items as well, I believe17:02
dteselkinHi!17:02
tsufiev_api&formats versioning is missing :(17:03
*** sriram has left #openstack-meeting-alt17:03
tsufiev_sorry, it is in place17:03
*** harlowja has joined #openstack-meeting-alt17:03
*** eankutse has quit IRC17:03
*** chenchong has quit IRC17:03
ativelkovprobably it is becuase I update it not too long ago17:03
ativelkovSo, let's begin17:03
*** mspreitz has joined #openstack-meeting-alt17:04
ativelkov#topic AI review17:04
*** openstack changes topic to "AI review (Meeting topic: murano)"17:04
ativelkovWe didn't make any formal AIs last time17:04
*** stanlagun has joined #openstack-meeting-alt17:04
ativelkovhowever we made an important decision: we've decided to get rid of murano-comon repository17:05
ruhemurano-common is already merged in murano-api17:05
katyafervent2Cool! Thanks ruhe17:05
ruheand i'm working on merging it into murano-agent17:05
ativelkovCool!17:05
ativelkov#info murano-common is already merged in murano-api17:06
ruhewhere i've got stuck a little bit because i need to test that i didn't break anything :)17:06
ativelkov#info merging of murano-common into murano-agent is in progress17:06
*** colinmcnamara has joined #openstack-meeting-alt17:06
ruheand our CI is not yet ready to test changes in murano-agent17:06
ativelkovruhe: you mean linux-based one?17:07
ruheativelkov: yes17:07
ruhei hope we'll create jobs for murano-agent changes in our CI17:08
ruheright after the release17:08
*** drray833 has quit IRC17:08
*** balajiiyer has joined #openstack-meeting-alt17:09
ativelkovI would prefer first to have a cloud-init-deployable murano-agent instead of embedding it to image17:09
ativelkovThis will simplify the development of the agent17:09
ruheativelkov: agree. that should be the first priority17:10
sergmelikyan+117:10
ativelkovand will make sence in having CI on it. Otherwise there is no continuous development at the first place17:10
*** kgriffs is now known as kgriffs_afk17:10
ativelkovAre we agreed on that?17:10
dteselkin+117:11
*** safchain has quit IRC17:11
ruhe+117:11
tsufiev_+117:11
katyafervent2+117:11
stanlagun+117:11
ativelkov#agreed to make a priority to create a cloud-init deployable agent after 0.5 is released17:12
ativelkovDo we have a blueprint for this change?17:12
stanlagundo we know how to do it?17:12
ruhedoes this agreement include windows-based agent? :)17:12
*** saurabhs has joined #openstack-meeting-alt17:12
*** michael-yu has quit IRC17:12
*** beagles is now known as beagles_brb17:12
ruhestanlagun: we're engineers, we'll figure it out ;)17:13
ativelkovruhe: we plan to run python-agent on windows as well17:13
*** arnaud has joined #openstack-meeting-alt17:13
*** balajiiyer has quit IRC17:13
ruheativelkov: hooray! one agent to rule them all17:13
ativelkovIt will just need to learn how to execute powershell-based execution plans, afair17:13
dteselkinAs for windows-agent, testing it on VM will require a powerfull system :)17:13
stanlagunas soon as we teach pthon-agent to execute PowerShell17:14
*** betsy_ has joined #openstack-meeting-alt17:14
ruheactivestate python might have these capabilities17:14
*** arnaud has quit IRC17:14
*** tedchang has joined #openstack-meeting-alt17:15
ativelkovstanlagun: any estimates on how difficult it may be?17:15
*** nacim has quit IRC17:15
*** arnaud has joined #openstack-meeting-alt17:15
stanlagunany python have these capabilities. It is just not that trivial to implement17:15
*** betsy has quit IRC17:15
*** betsy_ is now known as betsy17:15
dteselkinWe could simply call external powershell.exe application.17:15
stanlagunnot that simple. My estimation is up to 3 days17:15
ruhestanlagun: 3 days compared to 6 month release cycle sound good to me17:16
ativelkovwell, "up to 3 days" is quite fine17:16
ativelkovit would be a problem it were months17:16
ativelkovdays is quite ok17:16
stanlagunAnd several days more to turn python-agent into Windows service17:17
dteselkinSo we should add a new dependecy into our image builder - python17:17
ativelkovBut I didn't get any answer about blueprint, so I assume there is no BP17:17
*** saurabhs1 has joined #openstack-meeting-alt17:17
ativelkovdteselkin: eventual goal of this activity is to avoid using image builder at all17:17
dteselkinHow will we build windows images then?17:17
stanlagunwhy do we need to build them?17:18
ativelkovwell, for windows the customers will have to embed cloud-base init into the images, that's true17:18
ativelkovbut this should be the only thing to embed17:18
dteselkin+python17:19
ativelkovpython should be installable in the same manner as everuthing else17:19
ativelkovwith cloud-base-init17:19
dteselkincloud-init embeds it's oun python17:19
dteselkin*own17:19
*** khyati has quit IRC17:19
*** balajiiyer has joined #openstack-meeting-alt17:19
dteselkinit doesn't install it system-wide17:19
*** saurabhs has quit IRC17:19
ruhewell, in some cases users might prefer to have images with everythin pre-installed. disk-image-builder will do the job for linux images17:19
stanlaguncan agent use it as well?17:19
dteselkinuse what ?17:20
stanlagunWe are not going to drop image builder. But the goal is that it would be optional17:20
ruhestanlagun: +117:20
dteselkinIt's ok I think17:20
*** zns has quit IRC17:21
ativelkovSo, do we have a volunteer to create a BP for cloud-init-deployable agent?17:21
ruheativelkov: o/17:21
*** michael-yu has joined #openstack-meeting-alt17:21
ativelkovthanks17:21
ativelkov#action ruhe to create a BP on cloud-init-deployable agent17:21
ativelkovdteselkin: if I understand stanlagun's question, he asks if the python which was installed by cloud-init may be made available to other services (i.e. to our agent)?17:22
ruhei'll create the BP, but we'll need to brain-storm possible implementations in a group17:22
*** mspreitz has quit IRC17:23
*** bdpayne has joined #openstack-meeting-alt17:23
ativelkovruhe: sure. The questions is harder then it seems, as the repository for installable artifacts should be available even if the internet connectivity is not present17:23
ruheativelkov: dteselkin: stanlagun: linux's cloud-init uses system python. actually all the major distros have python pre-installed17:23
dteselkinativelkov, it should be tested. In theory, it's possible, but doesn't look like a good idea17:24
dteselkinruhe, in linux - yes17:24
dteselkinBut windows doesn't have it preinstalled of course17:24
ativelkovruhe: this mostly concerns windows, as it does not have neither python nor a simple (apt-get like) way to deploy it17:24
dteselkinSo to have unified agent really unufied I think it's better to add system wide python to windows17:25
stanlagunativelkov: If we inject cloud-init into Windows image we can inject Python as well. Or use cloud-init's one. Lets do a little research on it17:25
*** andreaf has joined #openstack-meeting-alt17:25
*** khyati has joined #openstack-meeting-alt17:25
ruheeh, windows users are used to perform a lot of manual work. i think they wouldn't complain if they'll have to build images with murano agent by themselves17:25
ativelkovok17:25
ativelkovAnyway, we are now way too far in the future17:25
ativelkovwe still have 0.5 at hand17:25
ativelkovLet's proceed with the agenda17:26
ativelkov#topic API versioning17:26
*** openstack changes topic to "API versioning (Meeting topic: murano)"17:26
ativelkovtsufiev_: please lead this17:26
tsufiev_ok17:26
tsufiev_so, the first and most obvious question: to what extent should each new version of murano components support older formats and apis?17:27
tsufiev_or more narrow question: should murano 0.5 dynamic UI processor support v.1 dynamic UI definitions (pre 0.5)?17:28
stanlagunI stand for Murano consistency. Dashboard version X guarantee to work with API version X only17:28
*** balajiiyer has left #openstack-meeting-alt17:29
ruheat this point i'd prefer to support only one version - current version. across all the projects in the same release17:29
katyafervent2+1 to stanlagun17:29
sergmelikyanRuhe, stanlagun +117:29
*** balajiiyer has joined #openstack-meeting-alt17:29
stanlagunThere is no point in supporting old UI forms without supporting XML workflows and old APIs as well17:29
*** amotoki_ has quit IRC17:29
tsufiev_for now that seems ok for me, but it can change in future, when there will be much more Murano resources of a certain version17:29
stanlagunlets leave it till Murano 1.017:30
tsufiev_will it be ok for current murano customers?17:30
ruhewe could think about it from a different point of view - what should be the upgrade path for Murano users? but, indeed, that's a questions for future17:30
stanlagunwe are breaking backward compatibility anyway17:30
stanlagunand probably will do it again in 0.617:30
ativelkovWhat I suggest is to always have a format classifier in all files17:31
ativelkovDSL, UI definitions, object models, etc17:31
tsufiev_i agree, breaking dynamic UI format backward compatibility seems minor issue comparing with the dropping out of all workflows :)17:31
ativelkovjust to fix the format17:31
stanlagunYes. But maybe not Version17:31
tsufiev_stanlagun: why not?17:32
stanlagunor not just Version17:32
stanlagunMaybe MinimumMuranoVersion17:32
*** jprovazn has quit IRC17:32
*** SushilKM has quit IRC17:32
tsufiev_could you elaborate it a bit?17:32
*** gyee has joined #openstack-meeting-alt17:32
stanlagunSuppose that your form uses some YAQL function that was introduced in version x.y.z. But the format of the form hasn't changed17:33
ativelkovMinimumMuranoVersion and similar params should be part of Package metadata17:34
ativelkovnot for forms17:34
ativelkovThis is entirely different topic17:34
stanlagunEvery template should have minimum required Murano version that can handle it17:34
stanlagunforms also use YAQL functions17:34
ativelkovThere shluld also be a Minimum Openstack version )17:34
stanlagunMaybe that too for things that depend on OpenStack17:34
*** zns has joined #openstack-meeting-alt17:35
ativelkovstanlagun: I would suggest to have these constraint on a per-package basis17:35
tsufiev_ativelkov: agree, there will be a lot of dependencies )17:35
ruheother approach - document changes and give users clear upgrade path instructions17:35
*** Sukhdev has joined #openstack-meeting-alt17:35
stanlagunativelkov: agree17:35
tsufiev_ativelkov: +117:35
tsufiev_still each file should denote its format version17:36
*** troytoman-away is now known as troytoman17:36
ativelkovbut format is format, so there should be a clear format identifyer for each document17:36
ativelkovtsufiev_: +1 )17:36
*** gusmaskowitz has joined #openstack-meeting-alt17:36
*** markmcclain1 has quit IRC17:36
tsufiev_will simple numeric format like '1', '2' be enough for us?17:37
stanlagunokay until you don't have to support older versions till 1.017:37
ativelkovFor packages I've started from 1.017:37
stanlaguntsufiev_: does it really important?17:37
stanlagun1 = 1.0.17:37
*** khyati has quit IRC17:38
katyafervent2we can have 1 and 1.1 at the same time17:38
tsufiev_stanlagun: it is important, because once we agree on it, we won't change it17:38
stanlagunlets assume it is just a number17:38
tsufiev_i vote for the integers17:39
stanlagunas soon as we would need something ather than 1 we get back on this and discuss on 1.2 vs 2.017:39
tsufiev_keeps things simple17:39
*** gusmaskowitz has left #openstack-meeting-alt17:39
stanlagunthis is Python. You just non need to think about this17:39
tsufiev_stanlagun: but you're right, don't need to bother, cause YAML-parser does it for us17:40
*** balajiiyer has left #openstack-meeting-alt17:40
ruhei personally don't care until we really need versioning. we're in active development stage now, and will be for the next 6 months17:40
stanlagunyep. So this doesn't affect any code you may write to support it17:40
*** eankutse has joined #openstack-meeting-alt17:40
ativelkovSeems we are agreed here17:41
ativelkovmoving on?17:41
*** eankutse has quit IRC17:41
tsufiev_yes17:41
*** flaper87 is now known as flaper87|afk17:41
ativelkov#topic MuranoPL package name17:41
*** openstack changes topic to "MuranoPL package name (Meeting topic: murano)"17:41
ativelkovsergmelikyan: can you lead this?17:42
sergmelikyanativelkov, sure!17:42
stanlagunCan you explain the topic?17:42
sergmelikyanWe selecting name of the package were core of our Murano PL going to be placed.17:42
stanlagunHave we discussed MuranoPL namespaces?17:42
sergmelikyanstanlagun, not yet17:42
sergmelikyanpackage will have name like muranoapi.<name>17:43
stanlagunI thought you were talking about AppCatalog package (zip file)17:44
sergmelikyanI suggest name "engine", are there any other suggestions?17:44
sergmelikyanLets select most popular one17:44
ativelkovI like "dsl" and "pl"17:44
stanlagunengine is already used17:44
sergmelikyan*language17:44
sergmelikyansorry17:44
*** mspreitz has joined #openstack-meeting-alt17:44
tsufiev_+1 for pl17:44
ruheit's a turing-complete language. so... pl17:44
stanlagun+1 for dsl. pl is too confusing. Looks like Perl extension17:45
*** ramashri has joined #openstack-meeting-alt17:45
ativelkovpl/dsl - same as pl/sql :)17:45
tsufiev_stanlagun: lol, haven't thought about perl )17:45
*** ramashri has quit IRC17:45
ruheativelkov: we might get sued by you-know-who :)17:46
sergmelikyanbut pl in pl/sql is procedure language ;)17:46
stanlagunpl/sql without sql is nothing. We should not make an impression that MuranoPL is GP-language like Python17:46
*** markmcclain has joined #openstack-meeting-alt17:46
ativelkovI would prefer 3-characters naming17:46
sergmelikyanruhe, dsl does not mean not turing-complete language.17:47
ativelkovSo, we have options "language", "pl", "dsl" - right?17:47
*** SumitNaiksatam has quit IRC17:47
ativelkovany other options? I want to make a vote17:47
stanlagunmpl17:47
*** eankutse has joined #openstack-meeting-alt17:47
ruhedemocratic vote agian? :)17:47
tsufiev_mpl is nice too17:47
ativelkovYes, I nlike votings17:47
ativelkovthey are better then fightings )17:48
*** matty_dubs has joined #openstack-meeting-alt17:48
*** mestery_ has joined #openstack-meeting-alt17:48
*** mestery has quit IRC17:48
ativelkov#startvote Which name should we choose? pl, dsl, mpl, language17:48
openstackBegin voting on: Which name should we choose? Valid vote options are pl, dsl, mpl, language.17:48
openstackVote using '#vote OPTION'. Only your last vote counts.17:48
ativelkov#vote dsl17:48
*** mspreitz_ has joined #openstack-meeting-alt17:48
*** amcrn has joined #openstack-meeting-alt17:49
sergmelikyan#vote dsl17:49
katyafervent2#vote pl17:49
stanlagun#vote dsl17:49
ruhe#vote abstain17:49
openstackruhe: abstain is not a valid option. Valid options are pl, dsl, mpl, language.17:49
dteselkin#vote dsl17:49
tsufiev_#vote dsl17:49
*** eankutse has quit IRC17:49
*** mspreitz_ has left #openstack-meeting-alt17:49
*** SumitNaiksatam has joined #openstack-meeting-alt17:50
ativelkovAnybody else?17:50
*** mspreitz has left #openstack-meeting-alt17:50
*** mestery_ is now known as mestery17:50
ativelkov#endvote17:50
openstackVoted on "Which name should we choose?" Results are17:50
openstackdsl (5): tsufiev_, stanlagun, dteselkin, ativelkov, sergmelikyan17:50
openstackpl (1): katyafervent217:50
ativelkov#agreed so it is dsl17:50
stanlagunwe also need to choose murano.dsl vs murano.eninge.dsl17:51
ruhestanlagun: what option do you prefer?17:51
stanlagunmurano.dsl17:51
*** igormarnat_ has quit IRC17:51
ruhethen i vote murano.dsl :)17:51
ativelkovI like the first one. It is shorter (pep8 <80 hehe) and dsl has its value regardless of the engine which uses it17:52
ativelkovNo objections?17:52
*** eankutse has joined #openstack-meeting-alt17:52
*** eankutse has quit IRC17:52
ativelkov#agreed Put dsl package on the top level inside murano17:52
ativelkov#topic Open Discussion17:53
*** openstack changes topic to "Open Discussion (Meeting topic: murano)"17:53
ativelkovAny open issues or questions to discuss?17:53
sergmelikyanpackage namespaces?17:53
stanlagunI think it would be best to ask comunity in ML17:54
ativelkovsergmelikyan: please elaborate17:54
sergmelikyanAll classed declared in MuranoPL should be placed in some namespaces. For now it is org.openstack, e.g. org.openstack.Oject17:55
stanlagunorg.openstack.murano.Object vs com.mirantis.murano.Objects vs something else17:55
ativelkovah17:55
ativelkovI see17:55
*** derekh has quit IRC17:55
ativelkovI would prefer it to be org.openstack.murano, however there is a legal issue here17:55
stanlagunmaybe have just murano.XXX for system classes17:55
ativelkovor, there may be a legal issue17:55
stanlagunor system.XXX17:56
ativelkovI would have it uniform and bound to domains - just to discurouge others from doing something.else17:56
*** jgallard has quit IRC17:56
stanlagunmakes sence17:56
ativelkovbut the question "Are we allowed to use foundation-owned domain for this17:56
ativelkovbut the question "Are we allowed to use foundation-owned domain for this" remain open17:57
*** pballand has quit IRC17:57
stanlagunThe question is who can answer such question17:57
ativelkovFoundation17:57
*** thinrichs has quit IRC17:57
stanlagunDo you know to question Foundation?17:57
ruhei'd prefer to avoid OpenStack name in our project until Murano gets official status17:57
*** markmcclain has quit IRC17:58
stanlagunIt might be too late to change it then17:58
*** mspreitz has joined #openstack-meeting-alt17:58
ruhethat's one of the rights projects get when they get integrated status - they can officialy use OpenStack brand17:58
ruhethat's how i understand that17:59
stanlagunWe are going to do everything possible to keep backward compatibility starting from some version (say 1.0)17:59
ativelkovThat is not the brand usage17:59
ativelkovThat is just the identifier17:59
ativelkovAnyway, we can explain our concerns and as the mailing list for advice. Foundation members monitor it17:59
stanlagunMaybe register dedicated murano domain? org.murano-project.system.Object :)18:00
ativelkovThis is a nice option, btw18:00
*** yogesh_ has joined #openstack-meeting-alt18:00
ruhewho's going to own murano-project.org? Murano foundation? :)18:00
ativelkov)18:00
ruheoops, out of time18:00
ativelkovoops, yes.18:01
ativelkovOk, continue next time then18:01
ativelkov#endmeeting18:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:01
openstackMeeting ended Tue Mar 25 18:01:19 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:01
stanlagunThis would be Mirantis gift for Foundation in trade for integrated status18:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/murano/2014/murano.2014-03-25-17.00.html18:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/murano/2014/murano.2014-03-25-17.00.txt18:01
openstackLog:            http://eavesdrop.openstack.org/meetings/murano/2014/murano.2014-03-25-17.00.log.html18:01
*** colinmcnamara has quit IRC18:01
*** eguz has joined #openstack-meeting-alt18:02
*** kgriffs_afk is now known as kgriffs18:02
*** tsufiev_ has left #openstack-meeting-alt18:02
*** beagles_brb is now known as beagles18:03
*** igormarnat_ has joined #openstack-meeting-alt18:04
*** ativelkov is now known as ativelkov_away18:05
*** eghobo has quit IRC18:05
*** ativelkov_away is now known as ativelkov18:06
*** troytoman is now known as troytoman-away18:08
*** eankutse has joined #openstack-meeting-alt18:08
*** banix has quit IRC18:08
*** ativelkov is now known as ativelkov_away18:09
*** ativelkov_away is now known as ativelkov18:09
*** ativelkov is now known as ativelkov_away18:09
*** ativelkov_away is now known as ativelkov18:09
*** _nadya_ has joined #openstack-meeting-alt18:10
*** vkozhukalov has joined #openstack-meeting-alt18:10
*** khyati has joined #openstack-meeting-alt18:12
*** banix has joined #openstack-meeting-alt18:12
*** ativelkov is now known as ativelkov_away18:14
*** _nadya_ has quit IRC18:20
*** oz_akan_ has quit IRC18:21
*** rramirez has quit IRC18:23
*** michael-yu has quit IRC18:23
*** igormarnat_ has quit IRC18:24
*** michael-yu has joined #openstack-meeting-alt18:25
*** hockeynut has quit IRC18:29
*** eankutse has joined #openstack-meeting-alt18:29
*** eankutse has quit IRC18:30
*** alazarev has quit IRC18:35
*** johnthetubaguy has quit IRC18:36
*** alazarev has joined #openstack-meeting-alt18:37
*** venkatesh has joined #openstack-meeting-alt18:40
*** mspreitz has left #openstack-meeting-alt18:40
*** eankutse has joined #openstack-meeting-alt18:42
*** bdpayne has quit IRC18:42
*** alazarev has quit IRC18:45
*** mattgriffin has quit IRC18:45
*** katyafervent2 has quit IRC18:45
*** hockeynut has joined #openstack-meeting-alt18:46
*** kgriffs is now known as kgriffs_afk18:50
*** rpodolyaka1 has joined #openstack-meeting-alt18:50
*** _nadya_ has joined #openstack-meeting-alt18:50
*** shakayumi has joined #openstack-meeting-alt18:50
*** shakayumi has quit IRC18:50
*** shakayumi has joined #openstack-meeting-alt18:51
*** lsmola has joined #openstack-meeting-alt18:55
*** doug_shelley66 has quit IRC18:57
*** greghaynes has joined #openstack-meeting-alt18:58
*** doug_shelley66 has joined #openstack-meeting-alt18:58
*** zhiyan is now known as zhiyan_18:58
*** derekh has joined #openstack-meeting-alt18:59
*** _nadya_ has quit IRC18:59
*** jistr has joined #openstack-meeting-alt18:59
*** pbelanyi has joined #openstack-meeting-alt19:00
*** Duane_ has quit IRC19:00
*** walker_ has quit IRC19:00
*** Duane has joined #openstack-meeting-alt19:00
lifelessmorning19:01
bnemeco/19:01
jistrhi19:01
slaglehello19:02
rpodolyaka1o/19:02
*** morazi has joined #openstack-meeting-alt19:02
andreafo/19:02
lsmolahello19:02
lifeless#startmeeting tripleo19:02
openstackMeeting started Tue Mar 25 19:02:20 2014 UTC and is due to finish in 60 minutes.  The chair is lifeless. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
*** jprovazn has joined #openstack-meeting-alt19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
greghaynesO/19:02
*** openstack changes topic to " (Meeting topic: tripleo)"19:02
openstackThe meeting name has been set to 'tripleo'19:02
derekhhi19:02
*** jang1 has joined #openstack-meeting-alt19:02
GheRiveroo/19:03
*** julienvey has joined #openstack-meeting-alt19:03
*** zhiyan_ is now known as zhiyan19:03
jprovaznhi19:03
lifeless#topic agenda19:03
*** openstack changes topic to "agenda (Meeting topic: tripleo)"19:03
lifeless    bugs19:03
lifeless    reviews19:03
lifeless    Projects needing releases19:03
lifeless    CD Cloud status19:03
lifeless    CI19:03
lifeless    Insert one-off agenda items here19:03
lifeless    open discussion19:03
lifeless#topic bugs19:03
*** openstack changes topic to "bugs (Meeting topic: tripleo)"19:03
lifeless#link https://bugs.launchpad.net/tripleo/19:04
lifeless#link https://bugs.launchpad.net/diskimage-builder/19:04
lifeless#link https://bugs.launchpad.net/os-refresh-config19:04
lifeless#link https://bugs.launchpad.net/os-apply-config19:04
lifeless#link https://bugs.launchpad.net/os-collect-config19:04
lifeless#link https://bugs.launchpad.net/tuskar19:04
lifeless#link https://bugs.launchpad.net/python-tuskarclient19:04
*** _nadya_ has joined #openstack-meeting-alt19:05
*** shakayumi has quit IRC19:05
lifelessso first up, untriaged stuff...19:05
*** Duane has quit IRC19:05
lifelesshttps://bugs.launchpad.net/diskimage-builder/ has 4 untriaged bugs19:05
*** walker_ has joined #openstack-meeting-alt19:06
*** noslzzp has quit IRC19:06
lifelessand so does https://bugs.launchpad.net/tripleo19:06
derekhhttps://bugs.launchpad.net/diskimage-builder/+bug/1290541 is fix I believe19:06
lifelessany suggests for keeping on top of that other than saying 'we need to try harder' ?19:06
*** walker_ has quit IRC19:07
*** Duane has joined #openstack-meeting-alt19:07
*** walker_ has joined #openstack-meeting-alt19:07
*** markwash has quit IRC19:08
rpodolyaka1a script that will collect untriaged bugs and post a list of those to #tripleo periodically?19:08
lifelessrpodolyaka1: sounds cool. are you wolunteering ?19:08
rpodolyaka1lifeless: sure19:08
lifeless\o/19:08
lifeless#action rpodolyaka1 to make an untriaged nag bot19:08
*** zns has quit IRC19:09
lifelesscriticals...19:09
greghaynesThe dib bugs all have asignee's, just no importance :/19:09
lifelessgreghaynes: that typically means self filed-and-assigned, which is where folk need guidance19:10
*** bdpayne has joined #openstack-meeting-alt19:10
lifelessgreghaynes: e.g. its an antipattern all of its own19:10
matty_dubsSo, as someone not too actively working on TripleO, it occurs to me -- if a whole team of people is supposed to be doing triage, but no one is, that tells me that people really don't care about triage.19:10
matty_dubsOr the problem would be self-correcting.19:11
*** rpodolyaka1 has quit IRC19:11
lifelessmatty_dubs: or that triage is hard/annoying/painful - not doing doesn't imply not caring19:11
*** rpodolyaka1 has joined #openstack-meeting-alt19:11
lifelessmatty_dubs: (see 'Switch' for citations on that)19:11
matty_dubsYeah, true enough.19:11
*** SumitNaiksatam has quit IRC19:11
lifelesserm, I mean 'not doing doesn't *only* imply not caring'19:12
jistri think the bot rpodolyaka1 mentioned would help a good bit. For me the most annoying thing about triage is looking if there are any untriaged bugs.19:12
jistre.g. having to look per-project19:12
lifelesshttps://bugs.launchpad.net/tripleo/+bugs?search=Search&field.importance=Critical19:12
derekhaccording to logstash we havn't had any occurrences of https://bugs.launchpad.net/tripleo/+bug/1292141 in ci since upping the pip timeout, we should close it and reopen another for a local pip chache (no longer critical)19:12
lifelessjistr: yeah, its quite terrible19:12
*** SumitNaiksatam has joined #openstack-meeting-alt19:13
lifelessderekh: I saw a different error string, but still a pypi issue last night19:13
*** slagle_ has joined #openstack-meeting-alt19:13
derekhlifeless: any idea where? or what the error was?19:13
lifelessderekh: broke my dib less cp's patch (which was broken for other reasons, but spurious fail is still a problem)19:13
lifelessderekh: sec19:13
*** rbrady has joined #openstack-meeting-alt19:14
*** Ng has joined #openstack-meeting-alt19:14
lifelesshttps://review.openstack.org/#/c/82683/ http://logs.openstack.org/83/82683/1/check-tripleo/check-tripleo-seed-precise/1f5ff5b/console.html19:14
lifeless2014-03-25 01:25:40.327 |     data = self._sock.recv(left)19:14
lifeless2014-03-25 01:25:40.327 | error: [Errno 104] Connection reset by peer19:14
*** slagle has quit IRC19:15
*** noslzzp has joined #openstack-meeting-alt19:15
lifelessderekh: so, I think we need more error strings for network / pip fails, and the bug is still really important - but if the data doesn't support that, sure, lets downgrade.19:15
lifelessare 1293782 and 1295703 the same issue ?19:16
*** alazarev has joined #openstack-meeting-alt19:16
*** malini is now known as malini_afk19:16
lifelessah the flow one is fixed19:17
derekhlifeless: ok, will downgrade, the error quoted in the bug seems to be gone, or close and open a new one?19:17
slagle_i submitted a couple reviews this morning for https://bugs.launchpad.net/tripleo/+bug/127064619:17
lifelessderekh: IMO given two bugs with the same cause and different symptoms we should dupe them :)19:18
derekhlifeless: k19:18
lifelessderekh: so I'm not sure there is any benefit shuffling the metadata around - we depend on a network resource that isn't reliable - thats the bug19:18
slagle_i think we should really consider just making the default mtu be 1400 in the dnsmasq options for neutron-dhcp-agent19:18
slagle_on the overcloud19:18
slagle_it fixes the issue for me19:18
*** slagle_ is now known as slagle19:18
*** balajiiyer has joined #openstack-meeting-alt19:19
*** balajiiyer has quit IRC19:19
*** balajiiyer has joined #openstack-meeting-alt19:19
derekhlifeless: yes but this particular problem wasn't specific to our netwrok (or at least may not be), I put a similar fix into devstack and it seems to have gotten rid of the bug there also, anyways getting sidetracked19:19
*** hockeynut has quit IRC19:20
*** rlandy has joined #openstack-meeting-alt19:20
lifelessslagle: I'm torn. Its clearly not a deployment caused bug. So yes, doing the workaround is appropriate.19:20
*** kgriffs_afk is now known as kgriffs19:21
lifelessslagle: OTOH OMG WTF ARE THEY THINKING, DONT MESS WITH THE END TO END SIGNALLING MECHANISMS!19:21
slaglei don't feel like i have enough networking expertise to say that using 1400 is "right" thing19:21
*** denis_makogon_ has joined #openstack-meeting-alt19:21
slaglebut...all the solutions i can find online just say to use it and be done with it19:21
lifelesslets talk after the meeting briefly19:21
slaglecould just be collective ignorance :)19:22
lifelesswhat about 1290490 ?19:22
lifelessand 1292141 ?19:22
lifelessah 141 is what derekh mentioned19:22
*** denis_makogon has quit IRC19:22
*** denis_makogon_ is now known as denis_makogon19:22
GheRiverodowngrading the MTU is a must as it's now19:22
*** dmakogon_ has joined #openstack-meeting-alt19:23
*** BrianB_ has quit IRC19:23
lifelessI've retitled 14119:24
*** bdpayne_ has joined #openstack-meeting-alt19:25
*** balajiiyer has left #openstack-meeting-alt19:25
lifelessderekh: ^19:25
derekhlifeless: cool, ok to downgrad to hig? since its not as common as it was ?19:26
derekh*high19:26
lifelessderekh: sure19:26
lifelessI'd like to downgrade https://bugs.launchpad.net/tripleo/+bug/1290490 too19:26
lifelessany objetions ?19:26
*** bdpayne has quit IRC19:27
derekhlifeless: looks like it happens about 3 times a day, interestingly in the last week mostly happened on the 21st19:28
lifeless1290490 ?19:29
derekhlifeless: yup19:29
*** venkatesh has quit IRC19:29
derekhlifeless: anyways no objection from me, just info19:30
lifelesshuh, I didn't realise 1290490 was hitting CI19:30
lifelessif it is, I think it is still very important19:31
lifelessderekh: got pointers?19:31
lifelessok what about https://bugs.launchpad.net/tripleo/+bug/1271344 ?19:31
derekhlifeless: I'll refine my search later to ensure I'm seraching on the correct thing19:31
lifelessI think we can downgrade https://bugs.launchpad.net/tripleo/+bug/1271344 - its very important but not breaking CI at the moment, right ?19:32
*** Duane has quit IRC19:32
*** luqas has quit IRC19:32
*** Duane has joined #openstack-meeting-alt19:33
derekhlifeless: correct, at least I haven't seen it19:34
lifelessok19:34
*** baoli has quit IRC19:35
*** Sukhdev has quit IRC19:35
*** zhiyan is now known as zhiyan_19:36
lifelessok, time to move on19:37
lifelesswe've touched on all the criticals for which people are here, I believe.19:37
lifeless#topic reviews19:37
*** openstack changes topic to "reviews (Meeting topic: tripleo)"19:37
lifelesshttp://russellbryant.net/openstack-stats/tripleo-openreviews.html19:37
*** jecarey has quit IRC19:37
lifeless19:37
lifelessStats since the last revision without -1 or -2 :19:37
lifeless    Average wait time: 5 days, 6 hours, 2 minutes19:37
lifeless    1rd quartile wait time: 0 days, 21 hours, 34 minutes19:37
lifeless    Median wait time: 3 days, 23 hours, 44 minutes19:37
lifeless    3rd quartile wait time: 5 days, 23 hours, 7 minutes19:37
*** stanlagun has left #openstack-meeting-alt19:37
*** Duane has quit IRC19:37
lifelesswe're in trouble :(19:37
lifelessany thoughts on why?19:38
derekhlifeless: lots more people on the team and no more cores19:38
*** baoli has joined #openstack-meeting-alt19:38
slagle+119:38
derekhlifeless: oh and I could do better too19:38
lifelesshttp://russellbryant.net/openstack-stats/tripleo-reviewers-30.txt if we want to look at reviewer activity19:39
lifelessonly 6 people doing more than 3 reviews a day on average19:39
NgI've fallen way behind where I was :/19:39
lifelessderekh: # of cores doesn't affect the stats above19:39
slaglemaybe we should have a review day or afternoon19:40
* slagle steals idea from ironic19:40
lifelessderekh: because - if the patch is ready, cores can rubber stamp and go very fast19:40
lifelessslagle: maybe!. I'd be quite keen on that if it looked like we're overloaded, but what the stats above say to me is that we've collectively stopped pushing as a community19:41
lifelessalso19:41
lifelessa lot of the new contributors are not yet reviewing consistently19:41
lifelesslike 1 review or so, and (from what I've seen) primarily on patches they need (e.g. from colleagues fixing something affecting them)19:42
devanandaslagle: that we have review days is a symptom of cores not reviewing steadily IMHO19:42
lifelesswhich isn't a bad thing19:42
andreaflifeless: e.g. I started contributing and I hope to be reviewing soon, but it takes a bit of time to get up to speed19:42
lifelessbut its not the thing we need19:42
lifelessandreaf: hey - cool!19:42
devanandaslagle: and so when we have external deadlines, it takes a concerted effort to push through the backlog, which is not ideal19:42
lifelessandreaf: please do. Note that the fastest way to get feedback on your reviews is to start commenting, right or wrong.19:42
slagleok, fair enough19:43
derekhlifeless: I dissagree people have to spend time on a review to know its ready... anyways we also have a backlog from when ci was busted which never got cleared19:43
lifelessderekh: point taken, and I'll send that mail asap :)19:44
lifelessonce I sort more beaureaucrap @ work19:44
bnemecIt's a tricky project to review properly.  Lots of interdependencies between git repos, lots of new (to me) components, and no unit tests so you have to verify logic in addition to everything else.19:44
*** _nadya_ has quit IRC19:44
greghaynesstackalytics graph for review rate seems pretty steady lately19:45
lifelessbnemec: thats interesting! perhaps we need a guide explaining things a bit more? To me, its easy to review because we know 'if you change a public API, you'll break something'19:45
*** shakayumi has joined #openstack-meeting-alt19:45
*** shakayumi has quit IRC19:45
bnemeclifeless: Right, but entire elements in dib and t-i-e are completely untested in the gate.19:45
bnemecWe're working on Fedora, but even with that we won't be hitting everything.19:45
lifelessbnemec: yes, I know - long way to go19:46
*** mattgriffin has joined #openstack-meeting-alt19:46
lifelessmore stats19:46
*** jecarey has joined #openstack-meeting-alt19:46
lifelessTotal reviews: 2176 (72.5/day)19:46
lifelessTotal reviewers: 82 (avg 0.9 reviews/day)19:46
lifelessTotal reviews by core team: 1174 (39.1/day)19:46
lifelessCore team size: 20 (avg 2.0 reviews/day)19:46
lifelessNew patch sets in the last 30 days: 1343 (44.8/day)19:46
lifelesscores are doing 40 reviews/day and 44 patch sets are being pushed a day19:47
lifelessbut19:47
lifeless  Queue growth in the last 30 days: 64 (2.1/day)19:47
lifelessso we're falling behind19:47
lifelesswhat if we ask all cores to do *one more review a day*19:47
lifelessthats 16 more reviews a day19:48
lifelesswhich could in principle land 8 changesets a day19:48
lifelessand tip things back in the right direction - can everyone here commit to 1 more review a day ?19:48
* derekh doesn't count them but will try19:48
slagleso what is that? let's be explicit19:48
slagle2 reviews a day?19:48
* jistr will try19:48
bnemecThere's some pretty low-hanging fruit out there too.  For example: https://review.openstack.org/#/c/80337/19:49
lsmolalifeleless, I will try19:49
*** IlyaE has quit IRC19:49
lifelessslagle: sure, lets say that.19:49
lifelesslsmola: thanks19:50
lifeless#action lifeless to propose minimum of 2 reviews/day commitment from core reviewers in tripleo19:50
andreafbnemec: more low hanging fruit: https://review.openstack.org/#/c/81813/ and https://review.openstack.org/#/c/82035/19:50
NgI will do19:50
*** jmontemayor has quit IRC19:50
jprovaznack19:50
lifelesswe need to roll19:51
lifeless#topic19:51
lifelessProjects needing releases19:51
*** openstack changes topic to " (Meeting topic: tripleo)"19:51
lifeless#topic Projects needing releases19:52
*** openstack changes topic to "Projects needing releases (Meeting topic: tripleo)"19:52
lifelessrpodolyaka1: you up for this?19:52
rpodolyaka1lifeless: yep!19:52
lifeless\o/19:52
lifeless#topic CI cloud status19:52
*** openstack changes topic to "CI cloud status (Meeting topic: tripleo)"19:52
lifelessHP region is ok, tripleo-cd still paused, but SpamapS thinks we can unpause soon with the new heat shiny19:53
lifelessRedhat region I believe is ready to add to the CI system \o/19:53
lifelessanyone have more to add ?19:53
Ng\o/19:53
derekhlifeless: patch is ready, I've been holding off on getting the nodepool vm's back to 8G19:53
lifeless#topic CI19:53
*** openstack changes topic to "CI (Meeting topic: tripleo)"19:53
lifelessderekh: ack, because of machine size in that region ?19:54
lifelessderekh: andreaf: tempest - I think tempest should just run from the slave like it does for devstack19:54
derekhlifeless: well because of the number of them 64G x 3 in overcloud19:54
dprincelifeless: machine size and number of machines19:54
lifelessdprince: ack19:54
devanandalifeless: hi! on CI, I'd like to bring up a question19:54
lifelessdevananda: shoot!19:54
devanandalifeless: specifically, how soon can Ironic start relying on tripleo-ci19:55
lifelessderekh: andreaf: I mailed the -dev list about tempest.19:55
andreaflifeless: so we can't use an element to configure tempest then?19:55
devanandaya'll are already posting -nv checks on our patch sets, which is great19:55
*** khyati has quit IRC19:55
lifelessandreaf: I think you'll get worse results19:55
devanandaalso, as a non-integrated project, afaik, it's OK for tripleo to vote on ironic... and I think I trust you guys ;)19:56
dprincederekh: we'll get more machines in the future so lets go for it now (regardless of size)19:56
lifelessandreaf: you can and may want to do for prod deploys, but CI is resource limited, we need to be juidicious where we run stuff19:56
derekhlifeless: yup, saw it, either is good with me, just thougt it would be good to reuse what we have  from seed but whatever19:56
lifelessderekh: andreaf: you guys should do whatever works best, was really just getting my thoughts out there where you can see them :)19:56
andreaflifeless: ok so we need some alternate lib/tempest to set-up tempest for tripleo kind of environment - or some more ifs in the existing one19:57
lifelessdevananda: CI for ironic with tripleo: https://bugs.launchpad.net/ironic/+bug/1297063 this bug19:57
lifelessdevananda: lists *all* the outstanding patchsets need to be running Ironic properly in check19:57
derekhdprince: ok, will push it up later19:57
lifelessdevananda: one each in Ironic, tripleo-incubator, image-elements, heat-templates19:57
lifelessdevananda: we get those four landed, and you should see failures such as the one reported in that bug19:58
lifelessdevananda: w.r.t. voting - once we're multi region we'll start turning the voting bit on.19:58
lifelesswith infra's cooperation19:58
lifelessandreaf: really be guided by derekh here19:58
dprincelifeless: once we are multi-region and stable19:58
lifelessandreaf: he's spent way more time on it than I19:58
devanandalifeless: voting globally vs. voting on ironic are different topics19:59
derekhon fedora ci runs we need https://review.openstack.org/#/c/82562/ and https://review.openstack.org/#/q/status:open+branch:master+topic:add-f20-jobs,n,z19:59
lifelessdevananda: lets follow that up when its actually something we can do19:59
devanandalifeless: ack19:59
andreaflifeless: ok that's fine at least I've got a clear direction on where to focus on now, thanks19:59
*** _nadya_ has joined #openstack-meeting-alt19:59
lifeless#topic open discussion20:00
*** openstack changes topic to "open discussion (Meeting topic: tripleo)"20:00
lifeless30 seconds20:00
*** Barker has quit IRC20:00
devanandalifeless: do you need anything from ironic folks for the tie/tht/t-i bugs?20:00
lifelessdevananda: reviews :)20:00
devanandaack20:00
*** caleb_ has quit IRC20:00
derekhcrap, time flies on these meetings20:01
*** caleb_ has joined #openstack-meeting-alt20:01
lsmolathanks guys, have a great week20:03
jistrthanks, see ya20:03
*** Ng has left #openstack-meeting-alt20:03
*** pbelanyi has quit IRC20:04
*** Barker has joined #openstack-meeting-alt20:04
*** baoli has quit IRC20:04
*** rlandy has left #openstack-meeting-alt20:04
lifeless#endmeeting20:05
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:05
openstackMeeting ended Tue Mar 25 20:05:08 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:05
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tripleo/2014/tripleo.2014-03-25-19.02.html20:05
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tripleo/2014/tripleo.2014-03-25-19.02.txt20:05
openstackLog:            http://eavesdrop.openstack.org/meetings/tripleo/2014/tripleo.2014-03-25-19.02.log.html20:05
*** derekh has quit IRC20:05
*** lblanchard has quit IRC20:05
*** matty_dubs has left #openstack-meeting-alt20:05
*** greghaynes has left #openstack-meeting-alt20:06
*** jistr has quit IRC20:06
*** lblanchard has joined #openstack-meeting-alt20:06
*** IlyaE has joined #openstack-meeting-alt20:07
*** rpodolyaka1 has quit IRC20:07
*** michael-yu has quit IRC20:08
*** demorris has quit IRC20:11
*** rpodolyaka1 has joined #openstack-meeting-alt20:11
*** rpodolyaka1 has quit IRC20:15
*** jprovazn has quit IRC20:15
*** michael-yu has joined #openstack-meeting-alt20:17
*** khyati has joined #openstack-meeting-alt20:17
*** mattgriffin has quit IRC20:18
*** alazarev has quit IRC20:20
*** _nadya_ has quit IRC20:20
*** eanxgeek is now known as eanxgeek|log20:23
*** colinmcnamara has joined #openstack-meeting-alt20:23
*** vkmc has joined #openstack-meeting-alt20:24
*** vkmc has joined #openstack-meeting-alt20:24
*** banix has quit IRC20:26
*** vkozhukalov has quit IRC20:28
*** rockyg has joined #openstack-meeting-alt20:28
*** Barker has quit IRC20:32
*** Leonr has quit IRC20:32
*** dprince has quit IRC20:33
*** demorris has joined #openstack-meeting-alt20:33
*** alazarev has joined #openstack-meeting-alt20:37
*** rpodolyaka1 has joined #openstack-meeting-alt20:38
*** lsmola has quit IRC20:39
*** rpodolyaka1 has quit IRC20:42
*** bdpayne_ has quit IRC20:48
*** markwash has joined #openstack-meeting-alt20:49
*** colinmcnamara has quit IRC20:51
*** colinmcnamara has joined #openstack-meeting-alt20:57
*** Duane has joined #openstack-meeting-alt20:58
*** IlyaE has quit IRC21:01
*** jang1 has quit IRC21:01
*** banix has joined #openstack-meeting-alt21:04
*** bdpayne has joined #openstack-meeting-alt21:06
*** pdmars has quit IRC21:07
*** Leonr has joined #openstack-meeting-alt21:09
*** khyati has quit IRC21:16
*** noslzzp has quit IRC21:17
*** Duane has quit IRC21:17
*** doug_shelley66 has quit IRC21:18
*** Barker has joined #openstack-meeting-alt21:18
*** jmontemayor has joined #openstack-meeting-alt21:21
*** lblanchard has quit IRC21:21
*** ameade has quit IRC21:28
*** mattgriffin has joined #openstack-meeting-alt21:29
*** julienvey has quit IRC21:30
*** gokrokve has quit IRC21:32
*** colinmcnamara has quit IRC21:32
*** banix has quit IRC21:35
*** khyati has joined #openstack-meeting-alt21:37
*** codekobe has quit IRC21:40
*** jeblair_ has joined #openstack-meeting-alt21:42
*** jeblair_ is now known as corvus21:43
*** eankutse has quit IRC21:43
*** IlyaE has joined #openstack-meeting-alt21:43
*** codekobe has joined #openstack-meeting-alt21:45
*** jeblair has quit IRC21:45
*** corvus is now known as jeblair21:45
*** eankutse has joined #openstack-meeting-alt21:46
*** russellb has quit IRC21:47
*** doug_shelley66 has joined #openstack-meeting-alt21:47
*** wendar has quit IRC21:47
*** russellb has joined #openstack-meeting-alt21:48
*** mwagner_lap has quit IRC21:49
*** wendar has joined #openstack-meeting-alt21:49
*** michael-yu has quit IRC21:50
*** malini_afk is now known as malini21:52
*** michael-yu has joined #openstack-meeting-alt21:57
*** caleb_ has quit IRC21:57
*** caleb_ has joined #openstack-meeting-alt22:00
*** eankutse has quit IRC22:03
*** kevinconway has quit IRC22:11
*** markwash_ has joined #openstack-meeting-alt22:12
*** markwash has quit IRC22:14
*** markwash_ is now known as markwash22:14
*** mattgriffin has quit IRC22:14
*** alazarev has quit IRC22:16
*** caleb_ has quit IRC22:17
*** alazarev has joined #openstack-meeting-alt22:18
*** yogesh_ has quit IRC22:18
*** alazarev has quit IRC22:18
*** zns has joined #openstack-meeting-alt22:19
*** mattgriffin has joined #openstack-meeting-alt22:20
*** alazarev has joined #openstack-meeting-alt22:20
*** alazarev has quit IRC22:22
*** Leonr has quit IRC22:23
*** balajiiyer has joined #openstack-meeting-alt22:24
*** IlyaE has quit IRC22:24
*** zns has quit IRC22:25
*** zns has joined #openstack-meeting-alt22:25
*** Leonr has joined #openstack-meeting-alt22:27
*** balajiiyer has quit IRC22:28
*** tanisdl has quit IRC22:34
*** walker_ has quit IRC22:41
*** Leonr has quit IRC22:43
*** jergerber has quit IRC22:44
*** denis_makogon has quit IRC22:46
*** betsy has quit IRC22:46
*** colinmcnamara has joined #openstack-meeting-alt22:48
*** colinmcnamara has quit IRC22:48
*** michael-yu has quit IRC22:50
*** mattgriffin has quit IRC22:51
*** michael-yu has joined #openstack-meeting-alt22:52
*** banix has joined #openstack-meeting-alt22:54
*** mwagner_lap has joined #openstack-meeting-alt23:02
*** malini has left #openstack-meeting-alt23:04
*** david-lyle has quit IRC23:08
*** markmcclain has joined #openstack-meeting-alt23:10
*** markmcclain1 has joined #openstack-meeting-alt23:11
*** markmcclain has quit IRC23:15
*** rockyg has quit IRC23:16
*** amytron has quit IRC23:22
*** andreaf has quit IRC23:22
*** demorris has quit IRC23:23
*** krtaylor has quit IRC23:23
*** julim has quit IRC23:30
*** markmcclain1 has quit IRC23:30
*** banix has quit IRC23:33
*** bdpayne_ has joined #openstack-meeting-alt23:33
*** caleb_ has joined #openstack-meeting-alt23:33
*** bdpayne has quit IRC23:34
*** jmontemayor has quit IRC23:35
*** baoli has joined #openstack-meeting-alt23:46
*** noslzzp has joined #openstack-meeting-alt23:51
*** mwagner_ has joined #openstack-meeting-alt23:54
*** colinmcnamara has joined #openstack-meeting-alt23:56

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