Tuesday, 2014-05-27

*** luizfar has quit IRC00:04
*** xuhanp has joined #openstack-meeting-alt00:05
*** eankutse has joined #openstack-meeting-alt00:06
*** HenryG has quit IRC00:11
*** eankutse has quit IRC00:11
*** nati_ueno has joined #openstack-meeting-alt00:12
*** xuhanp has quit IRC00:16
*** kenhui has joined #openstack-meeting-alt00:16
*** nati_ueno has quit IRC00:17
*** jasonb365 has joined #openstack-meeting-alt00:19
*** nati_uen_ has joined #openstack-meeting-alt00:22
*** nati_ue__ has joined #openstack-meeting-alt00:27
*** banix has quit IRC00:29
*** nati_uen_ has quit IRC00:30
*** jasonb365 has quit IRC00:31
*** nati_ue__ has quit IRC00:32
*** nati_uen_ has joined #openstack-meeting-alt00:35
*** xuhanp has joined #openstack-meeting-alt00:36
*** caleb_ has joined #openstack-meeting-alt00:36
*** banix has joined #openstack-meeting-alt00:37
*** tdruiva has joined #openstack-meeting-alt00:37
*** zhiyan_ is now known as zhiyan00:38
*** nati_uen_ has quit IRC00:39
*** xuhanp has quit IRC00:49
*** gokrokve_ has quit IRC00:51
*** gokrokve has joined #openstack-meeting-alt00:52
*** igor_ has joined #openstack-meeting-alt00:52
*** nati_uen_ has joined #openstack-meeting-alt00:52
*** nati_ue__ has joined #openstack-meeting-alt00:54
*** demorris has joined #openstack-meeting-alt00:55
*** gokrokve has quit IRC00:56
*** igor_ has quit IRC00:57
*** nati_uen_ has quit IRC00:57
*** nati_ueno has joined #openstack-meeting-alt00:57
*** nati_ue__ has quit IRC00:59
*** nati_ueno has quit IRC00:59
*** Haiying has quit IRC01:00
*** nati_ueno has joined #openstack-meeting-alt01:00
*** tdruiva has quit IRC01:03
*** carl_baldwin_m has quit IRC01:03
*** carl_baldwin_m has joined #openstack-meeting-alt01:03
*** nati_ueno has quit IRC01:04
*** carl_baldwin_m has quit IRC01:07
*** nati_ueno has joined #openstack-meeting-alt01:09
*** Haiying has joined #openstack-meeting-alt01:16
*** demorris has quit IRC01:25
*** demorris has joined #openstack-meeting-alt01:25
*** david-lyle has quit IRC01:30
*** kenhui has quit IRC01:31
*** demorris has quit IRC01:33
*** nati_ueno has quit IRC01:33
*** yamahata has joined #openstack-meeting-alt01:37
*** oomichi has joined #openstack-meeting-alt01:40
*** gokrokve has joined #openstack-meeting-alt01:44
*** nosnos has joined #openstack-meeting-alt01:44
*** michael-yu has joined #openstack-meeting-alt01:48
*** gokrokve has quit IRC01:48
*** michael-yu has quit IRC01:48
*** igor_ has joined #openstack-meeting-alt01:53
*** igor_ has quit IRC01:57
*** nati_ueno has joined #openstack-meeting-alt02:00
*** jjmb has joined #openstack-meeting-alt02:01
*** persia has quit IRC02:01
*** persia_ has joined #openstack-meeting-alt02:03
*** persia_ is now known as Guest7785002:04
*** persia has joined #openstack-meeting-alt02:04
*** persia is now known as Guest997502:04
*** Guest9975 has joined #openstack-meeting-alt02:04
*** Guest9975 is now known as persia02:04
*** Haiying has quit IRC02:06
*** michael-yu has joined #openstack-meeting-alt02:08
*** Haiying has joined #openstack-meeting-alt02:10
*** nati_ueno has quit IRC02:10
*** IlyaE has quit IRC02:10
*** michael-yu has quit IRC02:13
*** NehaV has joined #openstack-meeting-alt02:18
*** nati_ueno has joined #openstack-meeting-alt02:19
*** michael-yu has joined #openstack-meeting-alt02:19
*** demorris has joined #openstack-meeting-alt02:21
*** michael-yu has quit IRC02:23
*** nati_ueno has quit IRC02:25
*** NehaV has quit IRC02:26
*** vkmc has quit IRC02:29
*** zhiyan is now known as zhiyan_02:29
*** david-lyle has joined #openstack-meeting-alt02:31
*** nati_ueno has joined #openstack-meeting-alt02:33
*** david-lyle has quit IRC02:35
*** mberlin has joined #openstack-meeting-alt02:36
*** mberlin1 has quit IRC02:37
*** HenryG has joined #openstack-meeting-alt02:37
*** jasonb365 has joined #openstack-meeting-alt02:38
*** gokrokve has joined #openstack-meeting-alt02:41
*** hdd_ has joined #openstack-meeting-alt02:42
*** demorris has quit IRC02:42
*** gokrokve has quit IRC02:46
*** zhiyan_ is now known as zhiyan02:46
*** jjmb has quit IRC02:46
*** zhiyan is now known as zhiyan_02:52
*** zhiyan_ is now known as zhiyan02:52
*** igor_ has joined #openstack-meeting-alt02:54
*** igor_ has quit IRC02:58
*** kenhui has joined #openstack-meeting-alt02:59
*** NehaV has joined #openstack-meeting-alt03:03
*** NehaV has quit IRC03:04
*** coolsvap|afk is now known as coolsvap03:06
*** kenhui has quit IRC03:08
*** kenhui has joined #openstack-meeting-alt03:09
*** dims has quit IRC03:16
*** kenhui has quit IRC03:23
*** nosnos has quit IRC03:25
*** yamamoto_ has joined #openstack-meeting-alt03:27
*** eghobo has joined #openstack-meeting-alt03:30
*** david-lyle has joined #openstack-meeting-alt03:32
*** david-lyle has quit IRC03:36
*** david-lyle has joined #openstack-meeting-alt03:38
*** gokrokve has joined #openstack-meeting-alt03:42
*** david-lyle has quit IRC03:43
*** gokrokve has quit IRC03:46
*** akuznetsov has joined #openstack-meeting-alt03:48
*** igor_ has joined #openstack-meeting-alt03:55
*** jasonb365 has quit IRC03:59
*** igor_ has quit IRC03:59
*** tdruiva has joined #openstack-meeting-alt04:02
*** Haiying has quit IRC04:13
*** zhiyan is now known as zhiyan_04:14
*** akuznetsov has quit IRC04:16
*** akuznetsov has joined #openstack-meeting-alt04:18
*** banix has quit IRC04:18
*** zhiyan_ is now known as zhiyan04:21
*** david-lyle has joined #openstack-meeting-alt04:24
*** IlyaE has joined #openstack-meeting-alt04:28
*** nati_ueno has quit IRC04:31
*** nati_ueno has joined #openstack-meeting-alt04:32
*** TravT has joined #openstack-meeting-alt04:33
*** gokrokve has joined #openstack-meeting-alt04:43
*** nosnos has joined #openstack-meeting-alt04:46
*** gokrokve has quit IRC04:48
*** gokrokve has joined #openstack-meeting-alt04:48
*** IlyaE has quit IRC04:51
*** coolsvap is now known as coolsvap|afk04:54
*** igor_ has joined #openstack-meeting-alt04:55
*** igor_ has quit IRC05:00
*** hdd_ has quit IRC05:08
*** gokrokve has quit IRC05:17
*** IlyaE has joined #openstack-meeting-alt05:17
*** gokrokve has joined #openstack-meeting-alt05:18
*** gokrokve has quit IRC05:22
*** IlyaE has quit IRC05:31
*** TravT has quit IRC05:33
*** zhiyan is now known as zhiyan_05:40
*** zhiyan_ is now known as zhiyan05:41
*** eghobo has quit IRC05:44
*** _nadya_ has joined #openstack-meeting-alt05:46
*** gokrokve has joined #openstack-meeting-alt05:48
*** coolsvap|afk is now known as coolsvap05:50
*** gokrokve has quit IRC05:54
*** igor_ has joined #openstack-meeting-alt05:56
*** yogesh has joined #openstack-meeting-alt05:58
*** caleb_ has quit IRC05:59
*** igor_ has quit IRC06:00
*** IlyaE has joined #openstack-meeting-alt06:04
*** xuhanp has joined #openstack-meeting-alt06:05
*** yogesh has quit IRC06:08
*** _nadya_ has quit IRC06:08
*** _nadya_ has joined #openstack-meeting-alt06:11
*** SushilKM has joined #openstack-meeting-alt06:22
*** SushilKM has left #openstack-meeting-alt06:22
*** yogesh has joined #openstack-meeting-alt06:36
*** gokrokve has joined #openstack-meeting-alt06:49
*** jtomasek has joined #openstack-meeting-alt06:52
*** artem_panchenko has joined #openstack-meeting-alt06:53
*** artem_panchenko has left #openstack-meeting-alt06:53
*** gokrokve has quit IRC06:54
*** david-lyle has quit IRC06:54
*** yogesh has quit IRC06:55
*** igor_ has joined #openstack-meeting-alt06:57
*** igor_ has quit IRC07:01
*** boris-42 has quit IRC07:03
*** yogeshmehra has joined #openstack-meeting-alt07:10
*** boris-42 has joined #openstack-meeting-alt07:10
*** annashen_ has quit IRC07:11
*** jtomasek has quit IRC07:15
*** jtomasek has joined #openstack-meeting-alt07:15
*** annashen_ has joined #openstack-meeting-alt07:15
*** jcoufal has joined #openstack-meeting-alt07:17
*** nati_ueno has quit IRC07:18
*** nati_ueno has joined #openstack-meeting-alt07:19
*** markmcclain has joined #openstack-meeting-alt07:23
*** nati_ueno has quit IRC07:23
*** yamamoto_ has quit IRC07:24
*** d0ugal_ has quit IRC07:25
*** flaper87|afk is now known as flaper8707:26
*** IlyaE has quit IRC07:28
*** jtomasek has quit IRC07:29
*** markmcclain has quit IRC07:35
*** IlyaE has joined #openstack-meeting-alt07:35
*** annashen_ has quit IRC07:42
*** matrohon has joined #openstack-meeting-alt07:43
*** akuznetsov has quit IRC07:43
*** amotoki has joined #openstack-meeting-alt07:49
*** gokrokve has joined #openstack-meeting-alt07:49
*** nati_ueno has joined #openstack-meeting-alt07:50
*** gokrokve has quit IRC07:54
*** nati_ueno has quit IRC07:54
*** safchain has joined #openstack-meeting-alt07:54
*** nacim has joined #openstack-meeting-alt08:02
*** jgallard has joined #openstack-meeting-alt08:04
*** akuznetsov has joined #openstack-meeting-alt08:09
*** derekh_ has joined #openstack-meeting-alt08:17
*** IlyaE has quit IRC08:17
*** Ng has left #openstack-meeting-alt08:19
*** stannie has quit IRC08:21
*** tdruiva has quit IRC08:26
*** coolsvap is now known as coolsvap|afk08:34
*** igor_ has joined #openstack-meeting-alt08:41
*** coolsvap|afk is now known as coolsvap08:45
*** nosnos has quit IRC08:48
*** nosnos has joined #openstack-meeting-alt08:48
*** mberlin1 has joined #openstack-meeting-alt08:49
*** gokrokve has joined #openstack-meeting-alt08:49
*** nati_ueno has joined #openstack-meeting-alt08:50
*** mberlin has quit IRC08:51
*** nosnos has quit IRC08:53
*** gokrokve has quit IRC08:53
*** nati_ueno has quit IRC08:55
*** tdruiva has joined #openstack-meeting-alt08:56
*** andreaf has joined #openstack-meeting-alt08:59
*** tdruiva has quit IRC09:05
*** nelsnelson has joined #openstack-meeting-alt09:07
*** igordcard has joined #openstack-meeting-alt09:10
*** jtomasek has joined #openstack-meeting-alt09:14
*** xuhanp has quit IRC09:19
*** amotoki has quit IRC09:22
*** xuhanp has joined #openstack-meeting-alt09:31
*** yogeshmehra has quit IRC09:31
*** nosnos has joined #openstack-meeting-alt09:35
*** zhiyan is now known as zhiyan_09:39
*** nacim has quit IRC09:47
*** gokrokve has joined #openstack-meeting-alt09:49
*** gokrokve_ has joined #openstack-meeting-alt09:51
*** dmakogon has joined #openstack-meeting-alt09:51
*** nati_ueno has joined #openstack-meeting-alt09:51
*** gokrokve has quit IRC09:53
*** nati_ueno has quit IRC09:55
*** gokrokve_ has quit IRC09:55
*** coolsvap is now known as coolsvap|afk10:00
*** nacim has joined #openstack-meeting-alt10:01
*** nacim has quit IRC10:03
*** nacim has joined #openstack-meeting-alt10:04
*** nosnos has quit IRC10:07
*** jgallard has quit IRC10:08
*** jgallard has joined #openstack-meeting-alt10:08
*** jgallard has quit IRC10:13
*** xuhanp has quit IRC10:14
*** hdd_ has joined #openstack-meeting-alt10:23
*** nacim_ has joined #openstack-meeting-alt10:31
*** dmakogon has quit IRC10:32
*** nacim has quit IRC10:33
*** _nadya_ has quit IRC10:44
*** demorris has joined #openstack-meeting-alt10:44
*** gokrokve has joined #openstack-meeting-alt10:49
*** nati_ueno has joined #openstack-meeting-alt10:52
*** gokrokve has quit IRC10:53
*** nati_ueno has quit IRC10:56
*** igordcard has quit IRC11:02
*** demorris has quit IRC11:10
*** Yogi1 has joined #openstack-meeting-alt11:13
*** zhiyan_ is now known as zhiyan11:17
*** jjmb has joined #openstack-meeting-alt11:25
*** dims has joined #openstack-meeting-alt11:28
*** 20WAAGQA1 is now known as shadower11:28
*** safchain has quit IRC11:31
*** safchain has joined #openstack-meeting-alt11:36
*** yamahata has quit IRC11:36
*** eankutse has joined #openstack-meeting-alt11:39
*** hdd_ has quit IRC11:42
*** gokrokve has joined #openstack-meeting-alt11:49
*** vkmc has joined #openstack-meeting-alt11:51
*** vkmc has joined #openstack-meeting-alt11:51
*** gokrokve has quit IRC11:53
*** jgallard has joined #openstack-meeting-alt11:54
*** nati_uen_ has joined #openstack-meeting-alt11:55
*** _nadya_ has joined #openstack-meeting-alt11:55
*** satish has joined #openstack-meeting-alt11:58
*** nati_uen_ has quit IRC11:59
*** _nadya__ has joined #openstack-meeting-alt12:00
*** _nadya_ has quit IRC12:00
*** mwagner_lap has quit IRC12:08
*** flaper87 is now known as flaper87|afk12:11
*** markvoelker has quit IRC12:12
*** markvoelker has joined #openstack-meeting-alt12:14
*** jjmb has quit IRC12:15
*** dprince has joined #openstack-meeting-alt12:18
*** dims has quit IRC12:20
*** dprince has quit IRC12:25
*** dprince has joined #openstack-meeting-alt12:26
*** jjmb has joined #openstack-meeting-alt12:29
*** jjmb has quit IRC12:30
*** jdob has joined #openstack-meeting-alt12:33
*** irenab has joined #openstack-meeting-alt12:41
*** yamahata has joined #openstack-meeting-alt12:42
*** dims has joined #openstack-meeting-alt12:45
*** yamahata has quit IRC12:45
*** yamahata has joined #openstack-meeting-alt12:46
*** rmoe has joined #openstack-meeting-alt12:48
*** gokrokve has joined #openstack-meeting-alt12:49
*** Yogi1 has quit IRC12:52
*** jamie_h has joined #openstack-meeting-alt12:53
*** gokrokve has quit IRC12:54
*** _crobertsrh is now known as crobertsrh12:55
*** nati_ueno has joined #openstack-meeting-alt12:55
*** rbrady has joined #openstack-meeting-alt12:56
*** heyongli has joined #openstack-meeting-alt12:57
*** rpodolyaka has joined #openstack-meeting-alt12:57
*** noslzzp has joined #openstack-meeting-alt12:58
*** nati_ueno has quit IRC13:00
*** baoli has joined #openstack-meeting-alt13:00
baoli#startmeeting PCI Passthrough13:00
openstackMeeting started Tue May 27 13:00:30 2014 UTC and is due to finish in 60 minutes.  The chair is baoli. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: PCI Passthrough)"13:00
openstackThe meeting name has been set to 'pci_passthrough'13:00
*** yjiang5 has joined #openstack-meeting-alt13:00
baoliHi13:00
heyonglihi, all13:00
yjiang5hi13:00
heyonglihow many alarm you set13:01
yjiang5heyongli:  2 this time :)13:01
irenabhi13:01
baoliyjiang5, thanks a lot for joining13:01
*** rpodolyaka has left #openstack-meeting-alt13:01
yjiang5baoli: :)13:02
irenabbaoli: great work on the spec!13:02
baoliI put together a little agenda for today: https://wiki.openstack.org/wiki/Meetings/Passthrough#Agenda_on_May_26th.2C_201413:02
baoliirenab, heyongli: thanks for reviewing13:02
*** carl_baldwin_m has joined #openstack-meeting-alt13:03
irenabgreat, lets start according to agenda13:03
heyonglido we join NFV instead of pci sriov alone?13:03
*** sadasu has joined #openstack-meeting-alt13:04
irenabI am not sure we can keep focus there, but must follow what happens in NFV13:04
baoliagreed13:04
beaglesI also concur13:05
*** julim has joined #openstack-meeting-alt13:05
baoliI asked Jointhetubaguy to review the spec. Hoepfully he will remove the -2 soon.13:05
*** lenrow has joined #openstack-meeting-alt13:05
*** eankutse has quit IRC13:06
*** eankutse has joined #openstack-meeting-alt13:06
irenabbaoli: good, I think -2 may cause other cores to skip review13:06
beaglesirenab, that is probably correct13:06
* beagles apologizes for being a couple of minutes late and also offers baoli praise on his spec work!13:07
*** jcoufal has quit IRC13:07
*** jcoufal_ has joined #openstack-meeting-alt13:07
*** carl_baldwin_m has quit IRC13:07
*** carl_baldwin_m has joined #openstack-meeting-alt13:07
baoliThanks beagles13:08
baolianything else about the spec?13:08
irenabI passed any concern on review13:09
baoliIf you think it's in good shape, please give +1.13:09
heyonglisure,13:09
irenabAlready done. I just was suprised you do not need any help :-)13:09
*** BrianB_ has joined #openstack-meeting-alt13:09
baoliirenab, I appreciated your offering of help.13:10
irenabbaoli: I am just concerned to have it as soon as possible under review13:10
baoliirenab, we also have a team here to help.13:11
*** tdruiva has joined #openstack-meeting-alt13:11
irenabas beagles mentioned there is a lot of changes in the neutronV2 area13:11
irenabbaoli: great!13:11
irenabshall we skip to next topic on agenda?13:12
*** mberlin1 has quit IRC13:12
*** rpothier has joined #openstack-meeting-alt13:12
baoliirenab, do you expect any significant change and difference from the POC, in the neutronv2 area?13:12
baoliirenab, I'd like to hear from you on that.13:12
irenabbaoli: Not for our needs, but other mainly refactoring tasks may be pushed by others13:13
*** xuhanp has joined #openstack-meeting-alt13:13
*** eankutse has quit IRC13:13
baoliirenab, in that case, I'd like to see them addressed separately.13:13
*** banix has joined #openstack-meeting-alt13:14
*** oomichi has quit IRC13:14
irenabbaoli: the point I wanted to raise is that you may find youself rebasing the patch, but its part of the process, so will be OK.13:14
*** eankutse has joined #openstack-meeting-alt13:14
baoliI appreciated everyone's help. So let's get the spec approved, and started reviewing the official patch soon.13:15
irenab+113:15
*** Yogi1 has joined #openstack-meeting-alt13:17
irenabtempest tests ?13:17
baoli#topic tempest tests13:17
*** openstack changes topic to "tempest tests (Meeting topic: PCI Passthrough)"13:17
beaglesbefore discussing tempest tests are we talking about a single patch or multiple patches?13:17
beagles(too slow)13:17
baolibeagles, we'll submit multiple patches to facilitate the review process. But there might be dependencies between the patches13:18
beaglesbaoli: cool... the dependency thing is cool as well. been-there-done-that with several reviews lately.13:19
baoliirenab, mlnx has CI tests. Does it support sr-iov networkign already?13:20
heyonglidependencies is ok if every one is keep every thing not broken13:20
irenabbaoli: yes13:20
baoliirenab, does it need to be enhanced/modified with the new nova code?13:20
irenabbaoli: it covers mellanox sr-iov mech driver, which does not use13:21
*** _nadya__ has quit IRC13:21
irenabdoes not use the POC, it has some external package to do resource allocation of VFs13:21
*** betsy has joined #openstack-meeting-alt13:22
irenabgoing forward with HW_VEB mech. driver it will use your code in nova13:22
*** carl_baldwin_m has quit IRC13:22
*** carl_baldwin_m has joined #openstack-meeting-alt13:22
*** jaypipes has joined #openstack-meeting-alt13:22
*** carl_baldwin_m has quit IRC13:23
baoliirenab, do you expect any change of code for mlnx tempest tests?13:23
irenabfor now we run mostly api tests13:23
baoliirenab, so no real hardware based tests?13:23
irenabbali: need to start end 2 end tests with real networking13:23
yjiang5 irenab baoli: IIRC, we have CI test also for PCI, but not cover SR-IOV yet, only generic PCI passthrough integration test. I think possibly we need discuss the NFV testing as a general topic in NFV meeting, which requires gate on hardware?13:24
irenabbaoli: yues with real hardware, but not with full end 2 end tests13:24
*** mberlin has joined #openstack-meeting-alt13:24
*** jecarey has quit IRC13:25
yjiang5irenab: baoli: how is neutron handle the hardware specific integration testing?13:25
baoliSadasu is not here. But with cisco MD, I believe we'll have tests on real hw as well.13:25
irenabyjiang5: it expects the 3rd party testing system to verify13:25
sadasubaoli: I am right here13:25
baolisadasu, sorry didn't notice13:26
sadasucomment regarding cisco tempest tests is correct13:26
irenabdo you think we need special tests to be added to tempest?13:26
*** kenhui has joined #openstack-meeting-alt13:27
sadasuirenab: yes...we have to13:28
yjiang5irenab: sadasu: I think we need special tests in tempest, but will be skipped in gate.13:28
sadasuyes, these tests would have ti be specific to verndor specific CI tests13:28
*** tdruiva has quit IRC13:28
sadasuI am not sure if this would be a dependency for baoli's nova commit13:29
irenabsadasu: I am not sure why tests should be specific. I think that setup is vendor specific but tests should be common13:29
yjiang5sadasu: Do we need vendor specific CI? I thought it will be generic one, but be executed in 3rd party hardware. Nova has no hardware specific driver, .13:29
yjiang5irenab: +113:29
sadasuvendor specific hw setup, but common CI tests...thanks for correcting irenab13:30
irenabso I guess we need tests to cover nova boot for -- nic port_id case with SR-IOV port request, right?13:31
baolione question through, vendor MD requires specific config, right?13:31
baoliirenab, that's right13:31
sadasuirenab: correct13:31
sadasubut that should still be part of tests for the mech drivers13:31
*** _nadya_ has joined #openstack-meeting-alt13:32
sadasuhow is this usually done in Nova?13:32
baolisadasu, so tests are specific to MD drivers.13:32
yjiang5irenab: one thing come to mind is, the provider_physical_network will be test environment specific ?13:32
irenabyjiang5: correct13:32
*** luizfar has joined #openstack-meeting-alt13:34
baoliyjiang5: unless we'd like to develop common tests, from which vendor tests are based on, which will setup vendor specific config, etc.13:34
sadasuI think the tests that check the nova boot with --nic port_id would be common13:34
sadasualso the neutron port create tests would be common13:34
irenabsadasu: agree13:34
sadasu I am only not sure if each vendor's CI tests would want to add additional tests that are specific to their use case13:35
sadasuin this particular aspect the tests might differ13:35
sadasubut that completely depends on each vendor13:35
*** Ng has joined #openstack-meeting-alt13:35
irenabI do not have much knowledge on tempest tests, need some time to look and see what is there and which tests are missing for SR-IOV case13:35
irenabI think at least basic connectivity cases should be covered by common tests13:36
sadasuthere are no tests that are specific to the SR-IOV case at this point13:36
*** _nadya_ has quit IRC13:37
*** sballe_ has joined #openstack-meeting-alt13:37
beaglesirenab: true, but the usage pattern (create port, pass to nova) may not be exercised. mlavalle or marun may be able to give you some quick feedback on that13:37
irenabfor my understanding, except for using pre created neutron port with vnic_type=direct, there should be common cases that are applicable for SR-IOV based solution13:37
yjiang5sadasu: in neutron, will vendor-specific test case be added to tempest?13:37
sadasuI don't think we would have to come up with completely new tests, modifying existing tests (pre create sr-iov port) to suit the SR-IOV case would take care of most of the testing13:38
sadasuyjiang5: not to generic tempest tests13:38
yjiang5sadasu: thanks.13:39
irenabbeagles: I'll take a look and check with marun or mlavalle13:39
baoliirenab, sadasu, would you like to take a look at tempest tests for sr-iov networking?13:39
beaglessadasu, some of these tests are based on "works with nova-network, works with neutron"-parity kind of thing so it is quite possible that new tests will be needed -13:39
beagles... so that's an action item :)13:39
*** sballe has quit IRC13:39
beaglesooo13:39
beaglesalso.. btw there is  WIP of porting neutron to use oslo.rpc. it should not affect tempest tests (directly anyways) but...13:40
yjiang5beagles: I think it should be ok, right?13:40
irenabbeagles: sounds like you want to take a look on tempest :-)13:40
beaglesit may benefit from coordination with the people working on it for creating any additional unit tests etc13:40
beaglesirenab, please no :)13:41
yjiang5irenab: I will have a look on tempest13:41
beaglesI will definitely help though.. just that the third party CI stuff is completely foreign to me...13:41
baoliwe need to finalize the tempest tests soon.13:41
sadasubaoli: I am already looking into the tempest tests for the cisco CI case for my ML2 driver13:41
irenabyjiang5: thanks!13:41
baolisadasu, great and thanks!13:41
*** sballe_ has quit IRC13:42
baoliyjiang5, thanks.13:42
irenabsadasu: anythink you would like to share for next meeting, to consider to put it upstream?13:42
baoliSo next meeting, we may have a concrete plan for tempest tests?13:42
sadasuInternally, I am doing a lot of end-to-end testing with baoli's patched13:42
beaglesin all seriousness.. I will help with tempest, but I don't know if I am the best one to drive it. Quick review and independent testing of patches, etc.13:43
sadasubut I doubt I wil have all that translated into tempest tests in juno-1 or even juno-213:43
sadasucurrently,the priority it for me to get my ml2 driver into Juno13:43
heyonglisadasu, the test case you mentioned for sriov will be upstream?13:44
*** flaper87|afk is now known as flaper8713:44
yjiang5beagles: I think we should first define policy for haredware basesed testing, and then defint the list of integration testing should be added.13:44
irenabsadsu: I guess it worth to discuss in the team here to see if can push together, seems that it may be valuable for all13:44
beaglesyjiang5, that makes sense13:44
sadasutempest tests with more sophisticated testing will be added incrementally, given adding these tests also has its own review process13:44
yjiang5sadasu: agree, once we have the list/scenerio should be covered, then we can implement step by step.13:44
baoliif it's not a prerequisite to have tempest tests ready in order to commit the code, we can strive to make them for juno-3 or later13:44
yjiang5baoli: +113:45
sadasubaoli: +1 that is what I am shooting for13:45
baolicool.13:45
beaglesbaoli, +1 agreed... important to have, but landing a little later is cool13:45
irenabbaoli: makes sence, just need to make sure that nova side does not require any tempest by itself13:45
sadasuI don't want to add more hurdles to any of these commit...we have enough already13:46
beaglesirenab, yeah we should unit test that to death...13:46
baoliI think that we just need to keep that in mind, and keep looking at it.13:46
irenabbaoli: agree13:46
sadasuyes, we have the unit tests and I have end-to end integration tests13:46
*** Obulpathi has joined #openstack-meeting-alt13:46
sadasuits just not part of upstream tempest13:46
*** Obulpathi has quit IRC13:46
baoliShall we continue to the next topic?13:47
beagleswe should also do a quick check of the existing tempest tests to see if there are any deficiencies in coverage that might be quickly mitigated to catch any regressions we might inadvertantly add13:47
*** Obulpathi has joined #openstack-meeting-alt13:47
beaglestranslation: try and avoid breaking stuff :)13:47
baolibeagles, sure13:47
irenabbaoli: yes, please13:47
sadasuyes, again that can be done in our own testbeds...not pushed upstream right away13:47
baoli#topic bugs13:48
*** openstack changes topic to "bugs (Meeting topic: PCI Passthrough)"13:48
baoliyjiang5 and heyongli, can you guys take a look at https://review.openstack.org/#/c/82206/Init13:48
heyonglifirst bug link if broken , i add myself to second one and review soon13:48
baoliSorry, I will fix that13:48
*** gokrokve has joined #openstack-meeting-alt13:49
*** jcoufal has joined #openstack-meeting-alt13:49
heyonglithis one Abandoned13:50
heyongliplease recover13:50
baolihttps://review.openstack.org/#/c/82206/13:50
baoliPlease take a look at the comments regarding the node id13:50
heyonglisure13:50
baoliPlease let me know what you guys think about the node_id versus host name in the PCI device table.13:51
*** jjmb has joined #openstack-meeting-alt13:51
baoliIf needed, we need to open a new bug, or address that in 8220613:52
irenabwe  have less than 10 mins left, I am afraid we wont cover next topics today13:52
heyonglisure, baoli13:52
baoliok, to be quick, I will update the next bug soon.13:52
*** jcoufal_ has quit IRC13:52
irenabI am not sure we should right now enter into new advantures, lest try to land someting first13:53
*** balajiiyer has joined #openstack-meeting-alt13:53
*** rueben has joined #openstack-meeting-alt13:53
*** gokrokve has quit IRC13:53
irenabthere are few issues that may be worth to resolve as soos as possible, like vnic_type renaming if really needed13:54
*** jjmb1 has joined #openstack-meeting-alt13:54
baoliirenab, we should have them started so that they have a chance to get in in the next release. There are a lot of works13:54
*** sballe has joined #openstack-meeting-alt13:54
*** igor_ has quit IRC13:54
baoligiven the experience with the current work13:54
irenablet's give a priority to issues that may have an impact on current phase13:55
*** IlyaE has joined #openstack-meeting-alt13:56
*** jjmb2 has joined #openstack-meeting-alt13:56
*** jjmb has quit IRC13:56
baoliirenab, agree. The vnic-type renaming should have high priority, I think.13:56
*** nati_ueno has joined #openstack-meeting-alt13:56
*** jjmb has joined #openstack-meeting-alt13:56
*** caleb_ has joined #openstack-meeting-alt13:57
baoliFor others, depending on when users would need them13:57
irenabbaoli: do we have to change names? or once we get into nova api changes13:57
*** zhiyan is now known as zhiyan_13:57
*** jjmb has quit IRC13:57
*** jjmb has joined #openstack-meeting-alt13:58
yjiang5what's vnit-type renaming?13:58
irenabcurrently vnic_types are normal, direct and macvtap13:58
irenabmaybe worth to change macvtap to indirect13:58
*** jjmb1 has quit IRC13:58
irenabI am not sure its a must, at least networking  guys were OK with naming13:59
*** sballe has quit IRC13:59
baoliirenab, yea. So I don't think it has to. We can wait until somebody really cries for the change.13:59
yjiang5irenab: thanks for clarification14:00
baoliok, times is up. Let's meet next week.14:00
baoliThanks everyone14:00
beaglesyjiang5, vnit-type renaming - chuckle - an unintentional pun? because this is a "nit" about naming :)14:00
irenabUpdating, I will skip next week meeting14:00
beaglescheers!14:00
*** jjmb2 has quit IRC14:00
heyonglibye!14:00
irenabthanks guys14:00
*** nati_ueno has quit IRC14:00
beaglesirenab, on holiday? have a good trip!14:00
baoliirenab, have a good trip to Paris!14:00
baoli#endmeeting14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
*** satish_ has joined #openstack-meeting-alt14:00
openstackMeeting ended Tue May 27 14:00:53 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-05-27-13.00.html14:00
irenabthanks! Will do:-)14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-05-27-13.00.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-05-27-13.00.log.html14:00
*** beekneemech is now known as bnemec14:01
*** dane_leblanc has joined #openstack-meeting-alt14:01
*** satish has quit IRC14:01
*** rpothier has left #openstack-meeting-alt14:02
*** sadasu has quit IRC14:03
*** thangp has joined #openstack-meeting-alt14:05
*** gokrokve has joined #openstack-meeting-alt14:07
*** heyongli has quit IRC14:07
*** gokrokve_ has joined #openstack-meeting-alt14:08
*** jjmb has quit IRC14:10
*** eddie_ has joined #openstack-meeting-alt14:11
*** gokrokve has quit IRC14:11
*** flaper87 is now known as flaper87|afk14:12
*** demorris has joined #openstack-meeting-alt14:12
*** tdruiva has joined #openstack-meeting-alt14:12
*** amytron has joined #openstack-meeting-alt14:13
*** Barker has joined #openstack-meeting-alt14:14
*** irenab has quit IRC14:15
*** yjiang5 has left #openstack-meeting-alt14:15
*** jasonb365 has joined #openstack-meeting-alt14:16
*** corvus is now known as jeblair14:16
*** tvoran has joined #openstack-meeting-alt14:20
*** jmontemayor has joined #openstack-meeting-alt14:21
*** dlenrow has joined #openstack-meeting-alt14:22
*** lenrow has quit IRC14:25
*** james_li has joined #openstack-meeting-alt14:26
*** jecarey has joined #openstack-meeting-alt14:28
*** sileht has quit IRC14:28
*** sileht has joined #openstack-meeting-alt14:30
*** david-lyle has joined #openstack-meeting-alt14:30
*** sballe_ has joined #openstack-meeting-alt14:31
*** gokrokve has joined #openstack-meeting-alt14:33
*** atiwari has joined #openstack-meeting-alt14:35
*** gokrokve_ has quit IRC14:36
*** otherwiseguy has joined #openstack-meeting-alt14:36
*** alazarev has joined #openstack-meeting-alt14:36
*** sileht has quit IRC14:37
*** TravT has joined #openstack-meeting-alt14:39
*** sileht has joined #openstack-meeting-alt14:40
*** rueben has quit IRC14:44
*** sballe_ has quit IRC14:45
*** rueben has joined #openstack-meeting-alt14:47
*** venkatesh has joined #openstack-meeting-alt14:47
*** gcb has joined #openstack-meeting-alt14:49
*** sileht has quit IRC14:49
*** prashanthr_ has joined #openstack-meeting-alt14:50
*** sileht has joined #openstack-meeting-alt14:51
*** caleb_ has quit IRC14:57
*** nati_ueno has joined #openstack-meeting-alt14:57
*** n0ano has joined #openstack-meeting-alt14:57
*** otherwiseguy has quit IRC14:57
*** otherwiseguy has joined #openstack-meeting-alt14:58
*** gcb has quit IRC14:58
*** mspreitz has joined #openstack-meeting-alt14:58
*** jasonb365 has quit IRC14:59
*** Barker has quit IRC15:00
*** jmontemayor has quit IRC15:00
*** satish_ has quit IRC15:00
*** lascii is now known as alaski15:01
*** nati_ueno has quit IRC15:01
*** jmontemayor has joined #openstack-meeting-alt15:01
*** sriram has joined #openstack-meeting-alt15:01
*** rkukura has joined #openstack-meeting-alt15:02
*** mpanetta has joined #openstack-meeting-alt15:02
kgriffso/15:02
Obulpathio/15:02
vkmco/15:02
kgriffs#startmeeting marconi15:02
openstackMeeting started Tue May 27 15:02:59 2014 UTC and is due to finish in 60 minutes.  The chair is kgriffs. Information about MeetBot at http://wiki.debian.org/MeetBot.15:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:03
*** openstack changes topic to " (Meeting topic: marconi)"15:03
sriram\o o/15:03
openstackThe meeting name has been set to 'marconi'15:03
kgriffs#topic roll call15:03
*** openstack changes topic to "roll call (Meeting topic: marconi)"15:03
kgriffso/15:03
sriramo/15:03
mpanettao/15:03
Obulpathio/15:03
*** malini_afk has joined #openstack-meeting-alt15:03
*** malini_afk is now known as malini15:03
*** sriram_p has joined #openstack-meeting-alt15:03
*** jmontemayor has quit IRC15:04
kgriffsIt seems we are missing Mr. Percoco15:04
*** AAzza has joined #openstack-meeting-alt15:04
malinio/15:04
maliniMr. Percoco said he cant make it today15:04
maliniHe has a python meetup to go to15:04
*** morganfainberg_Z is now known as morganfainberg15:04
*** amytron has quit IRC15:05
kgriffsoic15:05
*** shivamshukla_ has joined #openstack-meeting-alt15:05
*** zhiyan_ is now known as zhiyan15:05
*** cpallares has joined #openstack-meeting-alt15:05
kgriffs#topic review actions from last time15:05
*** openstack changes topic to "review actions from last time (Meeting topic: marconi)"15:05
kgriffs#link http://eavesdrop.openstack.org/meetings/marconi_team_meeting/2014/marconi_team_meeting.2014-05-20-15.01.html15:05
kgriffs1. kgriffs to address over vs. under cloud in FAQ, mention on home page15:06
kgriffsI added a section to the FAQ about this - feel free to improve upon my first attempt at addressing the question15:06
kgriffs#link https://wiki.openstack.org/wiki/Frequently_Asked_Questions_(Marconi)15:07
kgriffsI still need to add a note about it to the home page15:07
kgriffsI'll do that right after this meeting15:07
kgriffs2. kgriffs to document roadmap and send to ML for feedback15:07
*** satish has joined #openstack-meeting-alt15:08
kgriffsdone15:08
kgriffs#link https://wiki.openstack.org/wiki/Roadmap_(Marconi)15:08
kgriffswe obviously have tons to do, but we also have lots of contributors now, so I am optimistic. :D15:08
kgriffsany questions/comments/concerns/rude remarks about the roadmpa?15:09
maliniI am good15:09
maliniI am positive abt  completing the Tempest tests, but not so much abt getting reviews for it15:10
*** dane_leblanc has quit IRC15:10
*** amytron has joined #openstack-meeting-alt15:10
*** terryw has joined #openstack-meeting-alt15:10
kgriffssounds like they need more core reviewers?15:11
*** abettadapur has joined #openstack-meeting-alt15:11
kgriffsor more reviewers that are active?15:11
*** otherwiseguy has quit IRC15:11
*** caleb_ has joined #openstack-meeting-alt15:11
malinithey have  ton of patches coming in everday :(15:11
*** jasonb365 has joined #openstack-meeting-alt15:12
*** carl_baldwin_ has joined #openstack-meeting-alt15:12
kgriffsi bet... hmmm. Well, maybe one of us on the team can work towards becoming a core reviewer to help lighten their load so other reviewers have more time for incubated projects. :)15:13
kgriffsmalini: maybe we can bring this up with devenanda and jarrett15:14
malinisure - tht'll be great!15:14
kgriffssee if between the three projects we can come up with 1-2 folks15:14
*** zhiyan is now known as zhiyan_15:14
kgriffsI'll send an email to the ML15:14
kgriffs#action kgriffs to reach out to ironic, barbican wrt tempest patch backlog15:15
kgriffs3. megan_w to check trademarks for our shortlist of names15:16
*** alazarev has quit IRC15:16
kgriffsmegan_w|afk: ^^^15:17
kgriffslots of people missing today. :(15:17
kgriffs#action megan_w to check trademarks for our shortlist of names15:17
Obulpathiyes :(15:17
kgriffs#action flaper87 to summarize 0.9 vs. 1.0 discussion in the context of openstack, add to AMQP driver bp, send to ML15:18
sriram_pls15:18
*** rkukura has left #openstack-meeting-alt15:18
*** amytron has quit IRC15:18
kgriffs#action kgriffs, megan_w to get some feedback on AMQP 1.0 from Rackspace ops15:18
kgriffs#topic Remove "Get a Specific Message" in v1.1?15:19
*** openstack changes topic to "Remove "Get a Specific Message" in v1.1? (Meeting topic: marconi)"15:19
*** demorris has quit IRC15:19
kgriffsSo, this keeps coming up as a point of confusion15:19
*** ametts has joined #openstack-meeting-alt15:20
kgriffsit adds to the "this API is strange for a message bus" factor15:20
*** akuznetsov has quit IRC15:20
kgriffsalso, it is perceived as a blocker for implementing certain kinds of backends15:20
kgriffsfinally, IMO it doesn't add any value to the API; I haven't been able to think of a reason anyone would need to get a message by ID, but I could be totally wrong - please tell me if you have a use case in mind15:21
malinikgriffs: +115:21
maliniif somebody needs to get a specific message by id, they could do it waith the multiple messages API call too15:22
kgriffsObulpathi: what do you think?15:22
*** alazarev has joined #openstack-meeting-alt15:22
*** tvoran has quit IRC15:22
Obulpathikgriffs: I don't see a use case for get the message by id15:22
sriramyes, in the case of distributive task queues and such it shouldnt matter.15:22
*** gyee has joined #openstack-meeting-alt15:23
kgriffsmalini: good point. should we get rid of this one as well? https://wiki.openstack.org/wiki/Marconi/specs/api/v1.1#Get_a_Set_of_Messages_by_ID15:23
Obulpathi+115:23
sriramdoes SQS have support for it by any chance?15:23
* sriram digs into it15:23
kgriffssriram: I don't believe so, but please double-check15:24
sriramon it15:24
prashanthr_then will the delete single message by id also be deprecated ?15:24
Obulpathino ..15:24
kgriffsprashanthr_: yes15:24
kgriffsoops15:24
kgriffsno15:24
kgriffssorry, misread15:24
kgriffsdeletes remain15:24
prashanthr_okay.15:25
Obulpathiclient shuld be able to delete the message once it works on it .. so we need that15:25
maliniif we dont support get by message id, what is the point of ever returning content-location/ message ids?15:25
*** akuznetsov has joined #openstack-meeting-alt15:25
kgriffsbut... hmmm, that gets me to thinking about something, but I guess that would be a 2.0 type change15:25
*** demorris has joined #openstack-meeting-alt15:25
kgriffsmalini: for the deletes?15:25
vkmcI don't see the need of getting a message by ID either... iirc consumers want first n messages in the queue and that's all15:25
*** venkatesh has quit IRC15:26
kgriffsfor 2.0 we could do something a little more drastic15:26
Obulpathi+115:26
*** rueben has quit IRC15:26
kgriffslike, we assign a "delete" id when you claim messages, and you use that to delete things. then delete only makes sense within the context of claiming messages15:26
kgriffsiirc, that's basically how SQS works15:27
sriramyes15:27
malinikgriffs: I like tht15:27
kgriffsalthough, if you take away the feed endpoints, that is basically what we have today in any case15:27
kgriffsI'll make a note of this idea in the 2.0 notes so we can discuss later15:27
*** rueben has joined #openstack-meeting-alt15:28
Obulpathican we delete the message using the claim id itself?15:28
kgriffsanyway, sounds like we are in agreement that we should remove getting one or more messages by id in v1.115:28
kgriffsObulpathi: you mean, delete the claim deletes all the associated messages?15:28
sriramI cant find evidence of SQS supporting getting a message by id either.15:28
sriramkgriffs: +1, we can remove it.15:29
Obulpathikgriffs: yes15:29
*** tonytan4ever has joined #openstack-meeting-alt15:29
maliniObulpathi: as is, claimed messages are deleted with message id + claim id15:29
Obulpathiok :)15:29
Obulpathimalini: :)15:29
kgriffsObulpathi: possibly, but we will need to decide if we want to encourage deleting multiple messages at a time, or if that is an anti-pattern; food for thought15:29
kgriffsI'll note that idea on the 2.0 spec as well15:30
*** emagana has joined #openstack-meeting-alt15:30
Obulpathioh got it .. we can claim multiple message in a single clain ..15:30
Obulpathi*claim15:30
Obulpathiso we need ability to delete messages individually15:30
kgriffs#agreed remove support for GET single, multiple messages by ID in API v1.115:30
*** lenrow has joined #openstack-meeting-alt15:30
sriramyes multiple messages can have the same claim id.15:31
kgriffsObulpathi: yes, probably, but let's keep thinking about it15:31
Obulpathiok15:31
sriram+115:31
kgriffsmoving on...15:31
*** Yogi1 has quit IRC15:31
kgriffs#action kgriffs to create the bp and update the v1.1 spec for removing support of GET by ID15:31
*** eankutse has quit IRC15:32
*** Yogi1 has joined #openstack-meeting-alt15:32
*** eankutse has joined #openstack-meeting-alt15:32
kgriffsI'm going to skip some of these agenda items until next time, since I really need flaper87|afk to be here15:32
maliniok..15:32
kgriffsthat brings us to...15:32
kgriffs#action Adding a base test class for v1.115:32
kgriffssriram: ^^^15:32
sriramyes15:33
kgriffs#link https://blueprints.launchpad.net/marconi/+spec/decoupling-unit-tests15:33
sriramwe need this to be done ASAP.15:33
*** dlenrow has quit IRC15:33
maliniabettadapur: does your v1.1 functional tests patch add a new base class for 1.1 ?15:33
kgriffsok. I think some of the decoupling has already happened, or maybe I am thinking of some work i did in an abandoned patch. :p15:34
*** tvoran has joined #openstack-meeting-alt15:34
abettadapurit does not15:34
*** kenhui has quit IRC15:34
sriramthe tests are for both v1 and v1.1 right now, we dont want to be doing ifs to check for api version.15:34
abettadapur(though it shouldn't need to, because functional uses an existing server no?)15:34
*** thomasem has joined #openstack-meeting-alt15:35
kgriffsI'm OK with this work, but I would like to find a way to share tests for functionality that is identical between 1.0 and 1.115:35
maliniI think other projects do this by adding new base classes15:35
sriramespecially for changes that are breaking v1, we need to have the unit tests in there for new features, to get a jenkins +1 :P15:35
kgriffsI suppose we could have a "v1.x" base class with shared tests15:35
*** tvoran has quit IRC15:35
*** jmontemayor has joined #openstack-meeting-alt15:36
kgriffsthen "v1.0" and "v1.1" inherit from that?15:36
*** jmontemayor has quit IRC15:36
*** amytron has joined #openstack-meeting-alt15:36
*** tvoran has joined #openstack-meeting-alt15:36
sriramhmm, so the v1.x will have the superset of all features?15:36
*** pdmars has joined #openstack-meeting-alt15:36
*** rueben has quit IRC15:36
Obulpathior .. is there a way we can read the return code fmo a config file?15:36
*** jmontemayor has joined #openstack-meeting-alt15:36
*** rmoe has quit IRC15:37
Obulpathi*form a config file .. depending on the version15:37
kgriffsObulpathi: the pattern we have been using for minor differences is to inherit from a base class with the test, then set a class variable for the return code or something15:37
Obulpathiok ... cool15:37
kgriffsalternatively, the base class can have a "protected" helper15:37
kgriffslike def _do_this_test15:38
maliniObulpathi: it wont be just the return codes tht differ..we will have deprecated/new APIs etc.15:38
srirammalini: +115:38
kgriffsand then you have in the child, do_this_test that calls _do_this_Test, passing in the expected return code15:38
Obulpathimalini: ok15:38
maliniWe need to do some research into how other projects did this15:38
maliniThis is not a new problem :)15:38
Obulpathi+115:38
*** rueben has joined #openstack-meeting-alt15:38
kgriffssure. Flavio will have some ideas based on his work on other projects15:38
sriramyes, we need to get this figured out soon. for other patches to land.15:38
kgriffsfwiw, the class variable pattern was originally his idea, so may have come from another proj15:39
kgriffsok15:39
*** alazarev has quit IRC15:39
kgriffsmalini: I made you "approver" for the design on the bp15:39
malinicool!15:39
*** zhiyan_ is now known as zhiyan15:39
kgriffswho would like to do the implementation?15:40
*** Barker has joined #openstack-meeting-alt15:40
sriramI can do it, once I'm done with marconi-bench15:40
*** annashen_ has joined #openstack-meeting-alt15:40
maliniwe need this by J-1 , rt?15:40
kgriffsmalini: just set definition to "approved" when we figure out a direction15:40
kgriffsmalini: yes15:40
srirammalini: yes15:40
kgriffsok, I'll assign to you sriram15:40
kgriffsand target for j-115:40
sriramcool, lots of work to do :D15:41
*** demorris has quit IRC15:41
*** adrian_otto has joined #openstack-meeting-alt15:41
kgriffs#topic Updates on blueprints15:42
*** openstack changes topic to "Updates on blueprints (Meeting topic: marconi)"15:42
kgriffs#link https://launchpad.net/marconi/+milestone/juno-115:42
kgriffsMalini: API V1.1 - Pop operation15:42
malinikgriffs: I got some comments from flaper87|afk - working on tht now15:43
maliniwill have this by J-115:43
*** eghobo has joined #openstack-meeting-alt15:43
kgriffssriram: API v1.1 - Lazily Create Queues15:44
sriramkgriffs: got some comments from flaper87|afk as well.15:44
sriramwill address them, and should be by j-115:44
sriramwill also need the unit tests here after we have a separate base class there.15:45
Obulpathianyone assigned to work on health endpoint?15:45
sriramthat might be a blocker for now, or do we want to do something else there.15:45
kgriffsObulpathi: flwang was working on that, but I haven't heard from him for a couple weeks...15:45
*** zul has joined #openstack-meeting-alt15:46
*** Barker has quit IRC15:46
Obulpathikgriffs: cool15:46
malinihe might be in the middle of his move15:46
Obulpathiany open issues I can take on?15:46
*** paulmo has joined #openstack-meeting-alt15:46
*** demorris has joined #openstack-meeting-alt15:46
kgriffsis anyone working on "API v1.1 header changes."15:47
*** Barker has joined #openstack-meeting-alt15:47
maliniI think I saw abettadapur assigned to it somewhere?15:47
Obulpathiyes, I think he is working on that15:48
kgriffsah, ok. I need to assign the bp to him then15:48
kgriffsObulpathi: how about this one?15:48
kgriffshttps://blueprints.launchpad.net/marconi/+spec/api-version-discovery15:48
*** markwash has joined #openstack-meeting-alt15:49
Obulpathisure15:49
*** xuhanp has quit IRC15:49
kgriffswe would want to check around with some other projects to see if there is a de-facto standard way to do this.15:49
*** muralia has joined #openstack-meeting-alt15:49
kgriffsObulpathi: assigned you15:50
abettadapuri have the header changes completed15:50
abettadapuri just need the unit tests to be compliant15:50
Obulpathikgriffs: :)15:50
kgriffsabettadapur: rock on15:50
abettadapuri can help sriram if he would like15:50
kgriffsObulpathi: I think you can also take "API v1.1 Request Document Changes"15:50
kgriffsand maybe also "API v1.1 Response Document Changes"15:50
sriramawesome, we can talk about that.15:50
kgriffsbut we should check with Fei to see if he has started those or not15:51
Obulpathiok ...15:51
*** zhiyan is now known as zhiyan_15:51
Obulpathiabettadapur: Good work :)15:51
kgriffsObulpathi: watch for flwang in IRC and catch him if you can. :)15:51
*** balajiiyer has quit IRC15:51
Obulpathikgriffs: ok15:51
kgriffsabettadapur: is there a patch submitted already?15:51
kgriffs#link https://blueprints.launchpad.net/marconi/+spec/api-v1.1-header-changes15:52
abettadapurno there isn't15:52
abettadapurit would be rejected by jenkins, so i havent done that15:52
kgriffsok, I was just making sure since I didn't see a reference on the whiteboard15:52
*** stannie has joined #openstack-meeting-alt15:52
kgriffsabettadapur: remind me what your launchpad ID is?15:52
abettadapurabettadapur i think15:53
abettadapurno15:53
abettadapuralexbettadapur15:53
kgriffsabettadapur: ok, you are now assigned to the bp15:53
abettadapurok15:53
kgriffsit's all official now15:53
kgriffs:)15:53
Obulpathi:)15:53
kgriffsvkmc: are you going to be working on this? https://blueprints.launchpad.net/marconi/+spec/storage-amqp15:54
vkmckgriffs, I'm yeah15:54
*** luizfar has quit IRC15:54
vkmckgriffs, I wanted to hear your opinion about what AMQP version to support15:55
*** luizfar has joined #openstack-meeting-alt15:55
vkmcyours and everyone else in Marconi of course15:55
*** shakamunyi has joined #openstack-meeting-alt15:56
kgriffsvkmc: btw, I assigned the bp to you, and also set you as "drafter". That means it's up to you to come up with a design and get flaper87's blessing. :)15:56
kgriffsvkmc: who is your mentor?15:56
vkmckgriffs, thanks for that15:56
vkmckgriffs, alcabrera and flaper87 :)15:56
kgriffsok15:56
*** fmaldonado_ has joined #openstack-meeting-alt15:57
*** xuhanp has joined #openstack-meeting-alt15:57
*** rmoe has joined #openstack-meeting-alt15:57
kgriffsre 0.9 vs. 1.015:57
kgriffsFlavio is discussing the state of 1.0 in RabbitMQ15:57
*** s1rp has joined #openstack-meeting-alt15:58
vkmcI see, great15:58
kgriffsI think if we can get the rabbit team to commit to doing a little more work on their 1.0 plugin, 1.0 is the way to go15:58
*** apmelton has joined #openstack-meeting-alt15:58
kgriffsvkmc: so, I'd sync up with flaper87|afk on that15:59
*** mspreitz has left #openstack-meeting-alt15:59
*** zz_gondoi is now known as gondoi15:59
vkmccool!15:59
vkmcjust one thing I'm doubtful about...15:59
*** danpb has joined #openstack-meeting-alt16:00
vkmcI saw that oslo.messaging is adding support for AMQP 1.0 https://blueprints.launchpad.net/oslo.messaging/+spec/amqp10-driver-implementation too16:00
*** tomblank1 has joined #openstack-meeting-alt16:00
vkmcisn't Oslo a common lib which we might use?16:00
dimsvkmc, it's not ready yet16:01
adrian_ottokgriffs: all done?16:01
*** hallyn has joined #openstack-meeting-alt16:01
kgriffsvkmc: we won't use it as a backend per se, but we might use it to RPC to other services16:01
*** xuhanp has quit IRC16:01
kgriffsadrian_otto: yep16:01
adrian_ottotx16:01
thomasemo/16:01
kgriffsok folks, let's wrap this up16:01
kgriffsthanks everyone!16:01
kgriffs#endmeeting16:01
vkmcthanks! :)16:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:01
Obulpathithank you :)16:01
openstackMeeting ended Tue May 27 16:01:51 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-05-27-15.02.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-05-27-15.02.txt16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-05-27-15.02.log.html16:01
adrian_otto#startmeeting containers16:02
*** AAzza has left #openstack-meeting-alt16:02
*** sriram is now known as sriram_afk16:02
openstackMeeting started Tue May 27 16:02:06 2014 UTC and is due to finish in 60 minutes.  The chair is adrian_otto. Information about MeetBot at http://wiki.debian.org/MeetBot.16:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:02
*** openstack changes topic to " (Meeting topic: containers)"16:02
adrian_otto#link https://wiki.openstack.org/wiki/Meetings/Containers#Agenda_for_2014-05-27_1600_UTC Our Agenda16:02
openstackThe meeting name has been set to 'containers'16:02
zulhi16:02
*** paulczar has joined #openstack-meeting-alt16:02
thomasemo/ hey hey16:02
zulsorry i missed the last meting16:02
apmeltono/16:02
adrian_otto#topic Roll Call16:02
*** cpallares has left #openstack-meeting-alt16:02
*** openstack changes topic to "Roll Call (Meeting topic: containers)"16:02
*** prashanthr_ has left #openstack-meeting-alt16:02
paulczarhere!16:02
adrian_ottoAdrian Otto16:02
*** abettadapur has left #openstack-meeting-alt16:02
julienveyJulien Vey16:02
muraliamurali allada16:02
zulChuckShort16:02
tomblank1tom blankenship16:02
paulmoPaul Montgomery16:02
thomasemThomas Maddox16:02
*** mpanetta has left #openstack-meeting-alt16:02
s1rpRick Harris16:02
stanniePierre Padrixe16:02
*** tonytan4ever has quit IRC16:02
*** sriram_afk has left #openstack-meeting-alt16:02
*** tonytan4ever has joined #openstack-meeting-alt16:03
*** serue has joined #openstack-meeting-alt16:03
sriram_pSriram Padmanabhan16:03
apmeltonAndrew Melton16:03
*** hallyn has left #openstack-meeting-alt16:03
adrian_ottohello everyone16:03
danpbDaniel Berrange16:04
serueSerge Hallyn16:04
*** gondoi has quit IRC16:04
*** balajiiyer has joined #openstack-meeting-alt16:04
*** sriram_p has quit IRC16:04
adrian_ottoI will pause for just one more moment for additional attendees. You are all welcome to chime in at any time to be recorded in the roll if we missed you in this section16:04
adrian_otto#topic Announcements16:05
*** openstack changes topic to "Announcements (Meeting topic: containers)"16:05
adrian_ottowelcome everyone to our second meeting. We anticipate different participants each week, as we have an alternating meeting schedule16:05
adrian_ottofor future reference the upcoming meeting schedule is published here: https://wiki.openstack.org/wiki/Meetings/Containers16:05
adrian_ottofor those of you who did not attend the first meeting:16:06
adrian_otto#link http://eavesdrop.openstack.org/meetings/containers/2014/containers.2014-05-20-22.00.html Minutes/Log from first meeting16:06
adrian_otto#topic Review Action Items16:06
*** openstack changes topic to "Review Action Items (Meeting topic: containers)"16:06
adrian_ottoWe did not have any action items last week, so skipping this16:06
adrian_otto#topic Introductions (For attendees not present on 2014-05-20)16:06
*** openstack changes topic to "Introductions (For attendees not present on 2014-05-20) (Meeting topic: containers)"16:06
adrian_ottoThis is for voluntary introduction from new attendees. Welcome! Describe your interest in containers, and this team. What is your role in hone OpenStack community, and what should we remember about you?16:06
*** tonytan4ever has left #openstack-meeting-alt16:07
adrian_ottoif you prefer, you are welcome to record your interests in the etherpad:16:07
adrian_otto#Link https://etherpad.openstack.org/p/containers Containers Etherpad16:07
adrian_otto#link https://etherpad.openstack.org/p/containers Containers Etherpad16:07
adrian_ottook16:07
adrian_ottoanyone feel like an introduction?16:07
thomasemSure16:07
thomasemThomas Maddox, working at Rackspace. My interest at the moment is in improving container support for LibvirtLXC in Nova, but also container support overall.16:08
zulChuck SHort, working at Canonical, My interest is making containers a first class hypervisor in openstack, wrote the initial libvirt-lxc, and working on a out of tree native lxc driver16:09
*** dguryanov|2 has joined #openstack-meeting-alt16:09
julienveyI'm Julien Vey, working at Numergy on Solum. Interested to have containers support in OpenStack first for Solum use-cases and after to manage applications with needs of fast spawn and bare-metal performance (no hypervisor overhead),  Isolation for micro-services without the cost of having to run a vm16:10
*** jamie_h has quit IRC16:10
danpbDaniel Berrange, Red Hat. libvirt upstream tech lead / architect. My interested in ensuring that Nova is able to provide 1st class support for both container & VM based virt, and to ensure Libvirt LXC is making the most of this16:11
*** jejb has joined #openstack-meeting-alt16:11
paulmoPaul Montgomery, Rackspace, also working on project Solum.  Along with Nova/container drivers, I'm particularly interested in securing containers (preventing backouts and such).16:11
paulmobreakouts16:11
adrian_ottoWelcome Thomas, Chuck, Daniel, Julien, and Paul. I'm Adrian Otto, serving as your chair/coordinator/moderator. I am a Principal Architect at Rackspace, and PTL for Solum. I want container functionality, like what we get form nova-docker today, plus more to support CI/CD use cases for openstack end users16:12
adrian_ottodoes anyone else wish to make an introduction?16:12
dguryanov|2Dmitry Guryanov, Parallels, work on Parallels Cloud Server, OpenVZ16:12
jejbJames Bottomley, Parallels; interested mostly in Containers API unification and Kernel issues16:13
stanniePierre Padrixe, Numergy, also from Solum team. Interested mostly in Docker Container in Openstack16:13
adrian_ottoWelcome Pierre, James and Dmitry!16:13
adrian_ottoanyone else is welcome to chime in as we proceed.16:14
*** nati_ueno has joined #openstack-meeting-alt16:14
adrian_ottoso it seems that we all have a lot of shared interests. We began last week with identifying those interests, and did a thought exercise to tease some of the ideas out.16:14
adrian_otto#topic Containers in OpenStack -- Stakeholder Interests16:15
*** openstack changes topic to "Containers in OpenStack -- Stakeholder Interests (Meeting topic: containers)"16:15
adrian_ottoso for those of you who are attending for the first time this week, please record your input here:16:15
adrian_otto#link https://etherpad.openstack.org/p/containers Containers Etherpad16:15
adrian_ottowe will take a moment to review that now, as there is new content to consider16:15
*** zz_gondoi has joined #openstack-meeting-alt16:15
adrian_ottoand discuss16:15
*** balajiiyer has left #openstack-meeting-alt16:15
*** zz_gondoi is now known as gondoi16:16
adrian_ottonow, there are a lot of topics in there16:16
adrian_ottomy goal is not to debate each one today, but instead to give us all a high level idea of where we are all coming from, and focus us i the areas where we have the strongest sense of shared insterest16:16
*** amotoki has joined #openstack-meeting-alt16:17
adrian_ottodanpb: you may want to skim to the bottom to give the proposed use cases some consideration for our next agenda item16:17
danpbadrian_otto: yes, i saw those, its a nice list16:18
adrian_ottook, great, feel free to hack that up or build on it16:18
thomasemI'll continue to flesh out my section in the stakeholder section as I organize my thoughts better. :)16:19
adrian_ottothomasem: good. There's no rush.16:19
thomasemcool16:20
dguryanov|2We're interested in containers, which are suitable for hosters, i.e. environment inside container is hostile. It's not possible on vanilla kernels, only on OpenVZ ones.16:20
*** rueben has quit IRC16:22
adrian_ottodguryanov|2: It would be great for you to reach out to paulmo, as you both have an interest in making container environments very secure. We all want that, I expect, but I'd like to have those who take a special interest in the security aspects to become better acquainted.16:22
* paulmo nods. Containers + a Mandatory Access Control mechanism such as SELinux may hold some possibilities16:22
*** alazarev has joined #openstack-meeting-alt16:23
adrian_ottoOnce you all have had a chance to read through the etherpad, and would like to begin group discussion on next steps, please chime in here16:23
zulso i was wondering if there is an appetite for a containers framework ala ironic, there was some discussion about this at ODS16:23
*** Yogi1 has quit IRC16:23
jejbsecurity contexts really don't help with hostile root.  The eventual solution will be USER_NS16:24
thomasemWe're also pretty interested in that as well. Already have some basic SELinux stuff up around containers. We have a few folks that aren't here today focused on container security on our team. I'll communicate to them that there is a good opportunity to collaboration here.16:24
*** malini has left #openstack-meeting-alt16:24
thomasems/to/for/16:24
*** Slower has joined #openstack-meeting-alt16:24
*** tvoran has quit IRC16:24
paulmojejb: There are many layers to this security onion for sure. :)  thomasem: Great!16:24
danpbyeah, different people have different standards for what they'd consider "Secure" to  mean16:25
thomasemdefinitely16:25
danpbsome people think that upstream kernels with userns are "secure" containers16:25
paulczarhas anyone looked at and have comments to make on the selinux support added to docker 0.11 ?16:25
jejbdanpb, pretty much, they are ... we think user_ns is more secure than the original OpenVZ root capability16:26
*** jgallard has quit IRC16:26
*** annashen_ has quit IRC16:26
*** derekh_ has quit IRC16:26
*** tvoran has joined #openstack-meeting-alt16:26
adrian_ottoI added a Top Theems section to the etherpad at the top16:26
adrian_ottoif I am missing any of the ones where we have strong shared interest, please feel free to add to that list16:27
danpbthe flip-side is that other people will say that allowing the host kernel to mount any untrusted filesystems is insecure no matter what you might do (given that we've seen CVEs in filesystem drivers like ext3/ext4 before)16:27
seruevery mudh so yes  (atm)16:27
serueand, currently, not allowed :)16:27
jejbThe solution to mount is being discussed on the lxc mailing list, but I agree it's a problem16:27
serueit seems clear to me that a fusefs with process running as container's root uid on the host is the answer16:28
jejbThis is one of the "best practise" areas where all containers do different things16:28
danpbyep, and it's probably not for OpenStack to care about the particular underlying impl / security architecture16:29
jejbsorry, have to run to next next meeting16:29
adrian_ottojejb: thanks for attending16:29
danpbbut rather to just follow whatever security best practices the specific container technology recommends16:29
adrian_ottodanpb: +116:30
adrian_ottook, would anyone like more time for reviewing the Etherpad?16:30
danpbadrian_otto: i think you should continue, given we're already 1/2 way through our time16:30
adrian_ottoI'd like to suggest some action items around the Top Themes16:30
adrian_ottomy thought there is to make those into a section on the Team Wiki16:31
adrian_ottoand plan our next agenda(s) based on those16:31
zulthats fine with me16:31
julienveylooks good16:32
adrian_ottoI'm happy to start an ML thread as well tagged with [Containers][Nova] that solicits input too16:32
zuli think we should start the discussion :)16:32
*** jcoufal has quit IRC16:32
zuladrian_otto:  please16:32
adrian_otto#action adrain_otto to begin an ML thread for input on our Top Themes, and formation of a Wiki page to clearly document them for future reference16:32
*** tdruiva has quit IRC16:32
funzohi, sorry I'm late o/16:32
adrian_ottotypo on my name16:32
adrian_ottoirc://irc.freenode.net:6667/#action adrian_otto to begin an ML thread for input on our Top Themes, and formation of a Wiki page to clearly document them for future reference16:33
danpbnot entirely sure that theme #4 is really an item on its own is it ?16:33
*** tdruiva has joined #openstack-meeting-alt16:33
adrian_ottook, close enough16:33
*** lsmola2 has joined #openstack-meeting-alt16:33
danpbi mean "can use a variety of container technology" is really just inherent in anything openstack does16:33
*** jejb has quit IRC16:33
adrian_ottodanpb: good point, it's realyl a sub point on the #1 theme16:33
danpbeverything is always pluggable with different impls in openstack world16:34
adrian_ottodanpb: +116:34
julienveyit should drive our decisions, but is not a theme on its own16:34
*** gokrokve has quit IRC16:34
adrian_ottook, I axed that one16:35
*** gokrokve has joined #openstack-meeting-alt16:35
adrian_ottolet's advance to our next topic16:35
adrian_otto#topic Containers Use Cases16:35
*** openstack changes topic to "Containers Use Cases (Meeting topic: containers)"16:35
*** mwagner_lap has joined #openstack-meeting-alt16:35
adrian_ottoExamine/enumerate use cases / scenarios for containers which do not require cinder storage, to demonstrate that cinder should be considered optional for Nova driver inclusion (Daniel Berrange / danpb)16:35
danpbso i think the examples people have listed there are a pretty decent representative set16:36
adrian_ottoI copied the drafts of the use cases to discuss into the bottom of the same etherpad: https://etherpad.openstack.org/p/containers16:36
danpbits pretty clear from them that containers are plenty useful without cinder16:36
*** terryw is now known as otherwiseguy16:36
adrian_ottook, thanks danpb. Are there any alternate points of view to consider on this subject?16:37
julienveythe end goal is to have some sort of persistent storage, and if we don't use cinder, we should be sure to have a way to do this16:37
*** rueben has joined #openstack-meeting-alt16:37
danpbultimately what we're showing here is that there's any number of ways to get persistent storage via the network, instead of direct attached storage16:37
adrian_ottojulienvey: Eric Windisich suggested a service like Manila may be the long term answer to that concern.16:37
julienveyyes, Manila could be a good option16:38
adrian_ottoTrove is another16:38
dguryanov|2Excuse me, I've missed previous meeting, what is the problem with attaching cinder volumes to containers?16:38
*** Barker has quit IRC16:39
danpbdguryanov|2: there's no real fundamental problem IMHO16:39
adrian_ottodguryanov|2: good question, the practice can require an insecure instance of a container where the mount functions are available, and allow a breakout.16:39
*** kenhui has joined #openstack-meeting-alt16:39
*** hazmat has joined #openstack-meeting-alt16:39
adrian_ottoat least that was Eric's concern about Docker containers16:39
danpbdguryanov|2: it was really just that  Docker doesn't support exposing block devs to its containers16:39
*** gokrokve has quit IRC16:39
*** jtomasek has quit IRC16:39
julienveyyes, mostly a Docker problem16:39
*** lsmola3 has joined #openstack-meeting-alt16:40
adrian_ottoapparently there is at least oen way to mitigate that that the nova-docker team has been working on16:40
danpband some  Nova  cores suggested that should be a blocker that prevents acceptance of docker16:40
*** jmontemayor has quit IRC16:40
danpbso this was just an attempt to demonstrate that lack of  cinder support should not be a blocker for docker acceptance16:40
adrian_ottook, so nobody chimed in with an alternating point of view, so can I conclude we have unanimous consent on this topic?16:40
danpbfor libvirt LXC at least, we *can* expose arbitrary host block devs to containers, and i guess openvz probably can too16:41
dguryanov|2You can't allow both direct access to a block device and mount. But either mount or read/write has no big security problems.16:42
*** lsmola2 has quit IRC16:42
*** nacim_ has quit IRC16:42
adrian_ottodanpb: yes, my understanding is it can be done, as long as it's done at container creation time. I am uncertain if it can be done at an arbitrary future point in time without a clever approach.16:42
thomasemYeah, you can mount from the host16:42
*** zhiyan_ is now known as zhiyan16:42
adrian_ottolike using a bind mount, and placing device files on that as needed16:42
thomasemThat's what we already do with the container image anyway16:42
*** safchain has quit IRC16:42
thomasemyeah16:42
*** crobertsrh has left #openstack-meeting-alt16:42
dguryanov|2Bind mounts is another question, I was talking about providing access rights to a real block device.16:43
dguryanov|2I think nova API should be extended for bindmounts :)16:43
*** eankutse has quit IRC16:43
dguryanov|2And instead of providing block device name, you should provide mount point.16:43
adrian_ottook, I am going to open us up for Open Discussion16:44
danpbdguryanov|2: yep, its quite possible we should do that16:44
adrian_otto#topic Open Discussion16:44
*** openstack changes topic to "Open Discussion (Meeting topic: containers)"16:44
danpbdguryanov|2: that could be useful with full machine virt too16:44
danpbdguryanov|2: because in combination with a guest agent, it'd let you expose the block dev & mount it in the guest in one go16:44
dguryanov|2Yes, agree16:45
*** lsmola3 has quit IRC16:45
*** lsmola2 has joined #openstack-meeting-alt16:45
*** jasonb365 has quit IRC16:45
*** Barker has joined #openstack-meeting-alt16:46
* danpb has to leave now unfortunately16:46
thomasemcatch ya later16:46
adrian_ottodanpb: thanks very much for attending. Catch you next time.16:46
*** danpb has quit IRC16:46
*** beyounn_1 has joined #openstack-meeting-alt16:46
*** pdmars has quit IRC16:47
*** amytron has quit IRC16:47
*** tvoran has quit IRC16:47
adrian_ottodoes anyone have suggestions for our top topics for next week?16:47
*** demorris has quit IRC16:47
*** Barker has quit IRC16:47
thomasemIt'd be good to catch up and the perception of our discussion around cinder, it sounds like.16:48
thomasems/and/on16:48
julienveywe could start discussing Theme 2 "Drive agreement on where containers belong"16:48
adrian_ottothomasem: I can attend the next Nova team meeting and report our consensus on that topic, and invite anyone with opposing viewpoints to join us for a discussion on that topic.16:49
thomasemadrian_otto: sounds good to me!16:49
adrian_ottowe have been asked to act as a Nova sub-team concurrently16:49
thomasemAh, I see16:49
adrian_otto#action adrian_otto to attend upcoming Nova meeting, and report Containers Team position on cinder support for containers in Nova16:49
dguryanov|2I think we should discuss implementation details, it seems we all want to add our technology to openstack, but nova guys will never accept 4 different drivers.16:50
adrian_ottolast week ewindisch attended and checked in for us16:50
adrian_ottodguryanov|2: good idea. Were you thinking of this in the context of the suggestion above from julienvey, or as a separate topic?16:51
hazmatwrt to docker .. there's another category of issues, runtime attachment of resources and the application container.. isn't really supported. ie. attach neutron port16:51
thomasemYeah, that's one I haven't tested with libvirt-lxc too16:51
*** zhiyan is now known as zhiyan_16:51
adrian_ottohazmat: indeed. The idea of a host agent was raised as an option to address that16:51
*** david-lyle has quit IRC16:51
adrian_ottowe should debate the merits of that option16:52
*** david-lyle has joined #openstack-meeting-alt16:52
*** david-lyle has quit IRC16:52
*** rueben has quit IRC16:52
thomasemThat'd be a good discussion. Hopefully by then I will have had time to see whether that is or isn't possible with existing libvirt-lxc, and perhaps ponder some solutions.16:52
*** IgorYozhikov is now known as iyozhikov16:52
thomasemWe shall see :)16:52
*** dteselkin_ has joined #openstack-meeting-alt16:52
*** serue has quit IRC16:53
paulczarthe method preferred by the docker community to update mounts etc in realtime is to destroy/recreate the container16:53
*** nati_ueno has quit IRC16:53
dguryanov|2adrian_otto: after we reach an agreement on that topic16:54
paulczarI think it would be worth looking at addressing it like that … rather than trying to force it into acting like a regular openstack vm16:54
*** kgriffs is now known as kgriffs|afk16:54
*** lsmola2 has quit IRC16:54
*** SumitNaiksatam has quit IRC16:54
adrian_ottodguryanov|2: ok, tx16:54
*** harlowja_away is now known as harlowja_16:55
thomasemI'd be especially interested in the limitations there. That strikes me more as a workaround, then again, the containerized way of thinking is that we have the flexibility to do things like that.16:55
*** stan_lagun has joined #openstack-meeting-alt16:55
*** yamahata has quit IRC16:55
thomasemI've got to drop off. I'll catch y'all next time!16:56
adrian_ottoOk, I have added two discussion topics for next week here: https://wiki.openstack.org/wiki/Meetings/Containers#Agenda_for_2014-06-03_2200_UTC16:56
*** tsufiev has joined #openstack-meeting-alt16:56
thomasemsounds good!16:56
adrian_ottofeel free to add to that16:56
adrian_ottothomasem: see you next time16:56
*** nati_ueno has joined #openstack-meeting-alt16:56
*** thomasem has left #openstack-meeting-alt16:57
adrian_ottook, any final thoughts before moving to adjournment today?16:57
*** ewindisch has joined #openstack-meeting-alt16:57
adrian_ottooh, ewindisch has appeared!16:58
*** muralia has left #openstack-meeting-alt16:58
ewindischhi16:58
*** Leonr has joined #openstack-meeting-alt16:58
ewindischoh, off by hour error?16:58
ewindisch:(16:58
adrian_ottoThanks everyone for your time and attention today. I look forward to seeing you again  on 2014-06-03 at 2200 UTC16:59
adrian_otto#endmeeting16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:59
openstackMeeting ended Tue May 27 16:59:04 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/containers/2014/containers.2014-05-27-16.02.html16:59
apmeltono/16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/containers/2014/containers.2014-05-27-16.02.txt16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/containers/2014/containers.2014-05-27-16.02.log.html16:59
*** paulmo has left #openstack-meeting-alt16:59
*** thinrichs has joined #openstack-meeting-alt16:59
*** apmelton has left #openstack-meeting-alt16:59
*** Yogi1 has joined #openstack-meeting-alt16:59
*** _nadya_ has joined #openstack-meeting-alt17:00
*** Yogi11 has joined #openstack-meeting-alt17:00
*** pballand has joined #openstack-meeting-alt17:02
ruhe#startmeeting murano17:02
*** caleb_ has quit IRC17:02
openstackMeeting started Tue May 27 17:02:55 2014 UTC and is due to finish in 60 minutes.  The chair is ruhe. Information about MeetBot at http://wiki.debian.org/MeetBot.17:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:02
*** openstack changes topic to " (Meeting topic: murano)"17:02
openstackThe meeting name has been set to 'murano'17:02
*** mspreitz has joined #openstack-meeting-alt17:03
ruhe#topic roll call17:03
*** openstack changes topic to "roll call (Meeting topic: murano)"17:03
*** kgriffs|afk is now known as kgriffs17:03
tsufievTimur Sufiev17:03
ruhewho's here for the meeting today?17:03
*** tonytan4ever has joined #openstack-meeting-alt17:03
dteselkin_Dmitry Teselkin17:03
*** Yogi1 has quit IRC17:04
katyaferventEkaterina Fedorova17:04
*** xwizard has joined #openstack-meeting-alt17:04
*** adrian_otto has left #openstack-meeting-alt17:04
stan_lagunStan Lagun17:04
ruhewoohoo. we have a quorum17:05
ruhe#topic Action Items Review17:05
*** openstack changes topic to "Action Items Review (Meeting topic: murano)"17:05
ruhei wasn't present on the last meeting. i don't see any action items in the logs17:05
ruheis that correct?17:05
ruhe#topic Review roadmap for j-117:06
*** openstack changes topic to "Review roadmap for j-1 (Meeting topic: murano)"17:06
katyaferventYes, it's17:06
ruhe#link https://launchpad.net/murano/+milestone/juno-117:07
ruhethat's what we have planned for j-1 for now ^^17:07
*** xwizard is now known as tnurlygayanov_17:07
*** igormarnat has joined #openstack-meeting-alt17:07
ruhethere are a couple of features we'd like to land in j-117:07
*** tonytan4ever has quit IRC17:08
*** michael-yu has joined #openstack-meeting-alt17:08
ruheon of them is to allow users to use external Murano app repositories...17:08
katyaferventIt's just 10 blueprints17:08
*** dims has quit IRC17:08
tnurlygayanov_yes17:08
*** smonov has joined #openstack-meeting-alt17:08
tnurlygayanov_external repositories it is interesting17:08
tsufievruhe, interesting that normalize-dashboard-pagination is in list, while its dependency app-catalog-pagination doesn't17:08
ruhe#link https://wiki.openstack.org/wiki/Juno_Release_Schedule17:09
*** sarob has joined #openstack-meeting-alt17:09
ruhetsufiev: can you give me a link?17:09
tsufievruhe, oh, sorry it does17:09
ruhek17:09
*** _nadya_ has quit IRC17:09
*** isviridov is now known as isviridov|away17:09
tnurlygayanov_10 bp for 2 weeks?17:09
*** _nadya_ has joined #openstack-meeting-alt17:09
*** sarob_ has joined #openstack-meeting-alt17:10
*** btully has joined #openstack-meeting-alt17:10
*** smonov has left #openstack-meeting-alt17:10
ruhefor people present here i believe that would be enough. I guess Steve and his team will add somthing to this list17:10
tnurlygayanov_we have 3 bp's assignet to one man: Timur Sufiev17:11
tsufievbtully, just in time :). we're currently discussing murano blueprints for J117:11
tnurlygayanov_is it ok?17:11
btullysorry day back from a holiday weekend and i think our schedule's are confused17:11
*** ranjitha has joined #openstack-meeting-alt17:11
tsufievtnurlygayanov_ yes, 2 of them are already implemented and on review now17:11
tnurlygayanov_ou, ok17:11
btullysounds good tsufiev17:12
*** igordcard has joined #openstack-meeting-alt17:12
ruheso, i'm going to add one more blueprint for external repositories. that'll allow users to use our app incubator any time anywhere17:12
*** esker has joined #openstack-meeting-alt17:12
ruhe#action ruhe create blueprint for external repositories17:12
tnurlygayanov_also I suggest to update status for blueprints with status'Unknown'17:13
tsufievbtully, what do you think about https://blueprints.launchpad.net/murano/+spec/murano-ui-horizon-patterns ?17:13
*** dims has joined #openstack-meeting-alt17:13
*** sarob has quit IRC17:13
btullyI added some work items to it on Friday. Did you see those?17:13
*** annashen_ has joined #openstack-meeting-alt17:13
tsufievbtully, yes. i mean, in terms of planning and J1 priorities17:14
*** zzelle has joined #openstack-meeting-alt17:14
*** zzelle has left #openstack-meeting-alt17:14
btullyI'd be happy to start working on those work items with a TODO status, assuming george doesn't mind17:15
tnurlygayanov_ruhe, let's update status of https://blueprints.launchpad.net/murano/+spec/alembic-migrations17:15
ruhetnurlygayanov_: there are only two BPs in unknown state. mine is really in unknown state, i plan to start working on it later this week. katyafervent: what about your BP https://blueprints.launchpad.net/murano/+spec/add-article-about-heat-templates-as-app-def17:16
*** gokrokve has joined #openstack-meeting-alt17:16
tsufievto me, 'TODO' things in that blueprint can be easily done in J1... ruhe, does that mean we should split Brian's blueprint into several, one of which will be scheduled for J1?17:16
tnurlygayanov_ok. we can set 'Not Started'.17:16
ruhetsufiev: you can split that blueprint into separate ones or just track every TODO items as a blueprint work item17:17
katyaferventwell, I'm writing demo about deploying from heat templates17:17
ruhetsufiev: btully: that's up to you how to track it. choose what you feel is more appropriate17:18
katyaferventsince it would be ready I'll have the material and update documentation17:18
*** Akuznetsova_ has joined #openstack-meeting-alt17:18
btullyThis is all new to me, so I guess whatever is easiest?17:18
ruhefor me it is easier to track things in separate blueprints17:19
*** esker has quit IRC17:19
*** gokrokve_ has joined #openstack-meeting-alt17:19
tsufiev+1 for separate blueprints17:19
ruhebtully: will you please create blueprints for items you would like to implement in J1?17:20
*** andreaf has quit IRC17:20
btullyso you mean, the blueprint i already created, seperate the TODO items into new blueprints, even though they are all dependencies?17:21
*** tchaypo has joined #openstack-meeting-alt17:21
*** gokrokve has quit IRC17:21
tsufievbtully, i'd suggest to split the part you're going to do in J1 and add it as dependency to the original one17:21
*** dteselkin__ has joined #openstack-meeting-alt17:22
ruhe+1 to what tsufiev said17:22
btullyok. and just to be clear, when is J1 (or where can I find out when J1 is on Launchpad)?17:22
*** _nadya_ has quit IRC17:22
tsufievbtully, https://wiki.openstack.org/wiki/Juno_Release_Schedule17:22
ruhebtully: here is release schedule for OpenStack (which we're following) https://wiki.openstack.org/wiki/Juno_Release_Schedule17:22
btullyok, thanks17:23
*** amotoki has quit IRC17:23
ruhebtully: j1 is a shortcut for juno-1 https://launchpad.net/murano/+milestone/juno-1 . you'll need to update "Milestone target" in your blueprints17:24
btullyok17:24
ruheanything else on the topic "Review roadmap for j-1"?17:24
tsufievruhe, frankly speaking i have some doubts about https://blueprints.launchpad.net/murano/+spec/dynamic-fields-on-service-details at J117:25
*** mspreitz has quit IRC17:25
ruhe#action btully to create blueprints extracted from generic https://blueprints.launchpad.net/murano/+spec/murano-ui-horizon-patterns17:25
tsufievit requires changes in dynamic UI specification, and probably will break backwards compatibility17:25
*** dteselkin__ has quit IRC17:26
*** dteselkin_ has quit IRC17:26
*** dguryanov|2 has left #openstack-meeting-alt17:26
ruhetsufiev: select from two options :) 1. postpone it right now 2. keep scheduled for j1 and postpone later, in case if it really couldn't be done in j1 timeframe17:27
*** paulczar is now known as zz_paulczar17:27
tsufievok, i select the (2)17:27
*** emagana has quit IRC17:27
ruheany objections?17:28
tsufievit is enough time to implement it alone, just wanted to design new spec _right_ (and not in a hurry)17:28
ruhe#agreed postpone https://blueprints.launchpad.net/murano/+spec/dynamic-fields-on-service-details17:28
ruhetsufiev: please remove milestone target from this BP17:28
tsufievruhe, done17:29
ruheok. we need to move to the next topic17:29
ruhe#info agreed on the plan for j1. but we still expect more items from sjmc717:29
ruhe#topic Review blueprints for MuranoPL changes17:30
*** openstack changes topic to "Review blueprints for MuranoPL changes (Meeting topic: murano)"17:30
ruhestan_lagun: your turn17:30
*** ranjitha has quit IRC17:30
*** emagana has joined #openstack-meeting-alt17:30
btullyunder "Propose for sprint" do I leave it as "nothing selected"?17:30
ruhebtully: yes. this field is not used by OpenStack projects17:31
stan_lagunI've submitted quite a big number of blueprints today17:31
btullythanks17:31
stan_lagunAbout fixing various issues in MuranoPL17:31
*** nati_ueno has quit IRC17:31
gokrokve_Is there a BP for exception/error handling?17:31
stan_lagunso i guess we need to decide which of them are going to be scheduled for J117:32
stan_lagungokrokve_ yes17:32
gokrokve_This is what we had in previous version but not in the current.17:32
stan_lagunlet me find17:32
stan_lagunhttps://blueprints.launchpad.net/murano/+spec/muranopl-exception-handling17:32
gokrokve_I think this is very important for now as without exception handling deployment will hang forever in some cases.17:32
gokrokve_What is your ETA for this BP?17:33
stan_lagunI think it is possible implement this BP and other debugging-related things in J1 time-frame if we concentrate on this17:34
ruhebtully: one more request for you. please add me (ruhe) as an approver for your blueprints. (it's just a workaround for launchpad's inability to send notifications on new blieprints)17:34
btullyok thanks17:34
stan_lagunI mean 2 weeks of work for 1 dev should be enough17:34
btullyis your name "ruhe" in launchpad?17:35
btullyi see you (Ruslan) :)17:35
ruhebtully: it's my id in launchpad. it should work. otherwise you can use a slightly longer version "Ruslan Kamaldinov" :)17:35
gokrokve_stan_lagun: Cool. I vote to implement them at first.17:36
gokrokve_Then deployment process will be controllable.17:36
*** tdruiva has quit IRC17:36
ruhei support implementing error handling in j117:37
stan_lagunhttps://blueprints.launchpad.net/murano/+spec/muranopl-stack-traces17:37
stan_lagunthis is also part of debuggability17:37
*** tdruiva has joined #openstack-meeting-alt17:37
ruhestan_lagun: you already have https://blueprints.launchpad.net/murano/+spec/hot-packages17:37
*** jprovazn has joined #openstack-meeting-alt17:37
stan_lagunThis BP duplicates https://blueprints.launchpad.net/murano/+spec/muranopl-stacktrace :(17:37
ruhestan_lagun: will you be able to handle https://blueprints.launchpad.net/murano/+spec/muranopl-exception-handling in the same time?17:38
stan_lagunHOT packages is nearly finished. One bug need to be addressed17:38
ruhestan_lagun: good17:38
*** tonytan4ever has joined #openstack-meeting-alt17:39
ruhestan_lagun: can you please mark one of these "stacktrace" blueprints as a duplicate?17:39
stan_lagunI also would like to improve debugability of contracts. I've written to ML on this17:39
stan_lagunok17:39
ruhestan_lagun: you'll need to change definition to "Superseded"17:39
ruhestan_lagun: you want to improve debugability of contracts also in J1?17:40
stan_lagunyes17:41
*** eghobo has quit IRC17:41
stan_lagunactually I already have prototype implementation that I'm going to commit as soon as we discuss all the details in ML17:41
gokrokve_What else do we have in BPs?17:42
*** eghobo has joined #openstack-meeting-alt17:42
ruhestan_lagun: and you already filed a bug for that. i'd suggest to track this as a blueprint17:42
*** nati_ueno has joined #openstack-meeting-alt17:42
stan_lagunruhe, that bug is only part of the work17:42
*** zhiyan_ is now known as zhiyan17:43
ruhegokrokve_: it's seems like we have enough work items for J1. would you like to add more?17:43
stan_lagunIf you talking about https://bugs.launchpad.net/murano/+bug/131369417:43
gokrokve_No. That is fine to have couple important BPs for J1.17:43
gokrokve_Smaller scope is better.17:44
ruheto summarize:17:44
stan_lagunI'd like to add one more17:44
stan_lagunhttps://blueprints.launchpad.net/murano/+spec/rename-workflow-to-methods17:44
gokrokve_There will be a space to add other BPs as soon as Steve is back.17:44
*** caleb_ has joined #openstack-meeting-alt17:44
ruhe#info agreed to target https://blueprints.launchpad.net/murano/+spec/muranopl-exception-handling to J117:44
stan_lagun30 minutes of work but very breaking change :)17:44
gokrokve_stan_lagun: +1. It should be trivial change.17:44
stan_lagunyes. But breaks 100% of existing apps17:45
ruhe#info agreed to target https://blueprints.launchpad.net/murano/+spec/muranopl-stack-traces (or the other one with similar description) to J117:45
gokrokve_Can we do support both?17:45
stan_lagunYes, we can (and drop support for Workflow in K release, for example)17:45
gokrokve_And then deprecate Workflows gradually providing autoconversion?17:46
gokrokve_Ok.17:46
stan_lagunBut anyway I think we need to discuss how we handle breaking changes17:46
ruhegokrokve_: stan_lagun: i think we need a wider audience to discuss such changes. would it make sense to bring this topic to ML?17:46
gokrokve_Sure. And we need to change version of th format to reflect the change.17:46
*** Akuznetsova_ has quit IRC17:46
gokrokve_Lets explore what we can do and then show options to community in ML.17:47
*** michael-yu has quit IRC17:47
ruheok17:47
stan_lagunVersioning is another big future that is missing17:47
ruhewe definitely need versioning in Juno17:47
stan_lagunyep. But not in J117:48
*** tonytan4ever has quit IRC17:48
ruhestan_lagun: agree17:48
ruheany other items to discuss in this topic?17:48
stan_lagun1 topic from my side17:49
ruhestan_lagun: sure17:49
stan_lagunContract improvements that I've written in ML17:49
*** pcarver has joined #openstack-meeting-alt17:49
*** tonytan4ever has joined #openstack-meeting-alt17:49
stan_lagunThey also introduce breaking change. Although it is very unlikely to break anything17:50
gokrokve_I think we are not in danger here as our curent contracts are very simple.17:50
stan_lagungokrokve_ I suggest to simplify contracts17:51
stan_lagunBut maybe we need to agree on breaking changes before making such commits17:51
gokrokve_That is fine. Again, can we support both old and new versions of syntax?17:52
*** caleb_ has quit IRC17:52
stan_lagunno17:52
stan_lagunsyntax is the same17:52
*** zhiyan is now known as zhiyan_17:52
stan_lagunsemantic differences17:52
*** caleb_ has joined #openstack-meeting-alt17:52
stan_lagunbut the difference is only noticeable for corner cases17:53
*** rueben has joined #openstack-meeting-alt17:53
*** balajiiyer has joined #openstack-meeting-alt17:53
gokrokve_So both variants will be supported? Where is a breaking change?17:54
stan_lagunno, only one variant17:54
ruhestan_lagun: to make these changes transparent i suggest to prepare a patch to app incubator which updates all app definitiions before you send a patch that changes MuranoPL17:54
tsufievgokrokve_, the same contract will mean different things after these changes17:54
stan_lagunno incubator app will break17:55
*** smonov has joined #openstack-meeting-alt17:55
stan_lagunfor example currently $.int() means int or null. With my changes it would mean just int and null will be converted to 017:56
gokrokve_stan_lagun: Then it is ok to introduce this change.17:56
ruhe4 minutes left. we have one more topic to discuss17:56
gokrokve_Just do this ASAP as 0.5 just released and it will take month or two when it will be actually used.17:56
tsufievgokrokve_, you mean backporting changes from J1 to 0.5?17:57
*** rueben has quit IRC17:57
ruhe#info agreed to introduce changes in contracts (contract improvements)17:57
*** SushilKM has joined #openstack-meeting-alt17:57
ruhe#topic Make gate tests voting17:58
*** openstack changes topic to "Make gate tests voting (Meeting topic: murano)"17:58
*** michael-yu has joined #openstack-meeting-alt17:58
ruheso, we recently renamed stackforge/murano-api to stackforge/murano and renamed package muranoapi to murano17:58
*** pballand has quit IRC17:59
ruhe#link https://blueprints.launchpad.net/murano/+spec/rename-murano-api-to-murano17:59
ruheno, our dsvm job is green again17:59
*** caleb_ has quit IRC17:59
ruhei'd like to give it one more week to prove it's stable and make it voting17:59
tsufievno objections from my side17:59
ruheit means that patches will not be able to be merged if this job fails17:59
katyafervent+118:00
ruhe#info agreed to mark murano-dsvm job as voting one week later18:00
sc68calruhe: heads up, have a meeting slated for 180018:00
ruhethat's all for today. thanks everyone18:01
ruhe#endmeeting18:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:01
openstackMeeting ended Tue May 27 18:01:04 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/murano/2014/murano.2014-05-27-17.02.html18:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/murano/2014/murano.2014-05-27-17.02.txt18:01
openstackLog:            http://eavesdrop.openstack.org/meetings/murano/2014/murano.2014-05-27-17.02.log.html18:01
ruhesc68cal: thanks :)18:01
sc68cal:)18:01
*** balajiiyer has left #openstack-meeting-alt18:01
sc68calWho's attending the Neutron QoS subteam?18:01
*** tomblank1 has left #openstack-meeting-alt18:01
sc68cal#startmeeting neutron_qos18:01
openstackMeeting started Tue May 27 18:01:39 2014 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
*** tsufiev has left #openstack-meeting-alt18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: neutron_qos)"18:01
openstackThe meeting name has been set to 'neutron_qos'18:01
*** Kanzhe has joined #openstack-meeting-alt18:01
sc68cal#link https://wiki.openstack.org/wiki/Meetings#Neutron_Quality_of_Service_API_Sub_Team_Meeting18:01
*** emaganap has joined #openstack-meeting-alt18:02
Kanzhehi Sean18:02
sc68calhey how's it going?18:02
*** SushilKM has left #openstack-meeting-alt18:02
*** esker has joined #openstack-meeting-alt18:03
*** zz_paulczar is now known as paulczar18:03
*** caleb_ has joined #openstack-meeting-alt18:03
sc68calgoing to wait to 5 after to see who else joins for the meeting18:03
*** esker has quit IRC18:03
kevinbentonhi18:03
sc68calkevinbenton: hey!18:03
*** emagana has quit IRC18:03
smonovHello18:03
*** esker has joined #openstack-meeting-alt18:03
*** thinrichs has quit IRC18:04
sc68calsmonov: hello18:04
*** james_li has quit IRC18:04
*** eankutse has joined #openstack-meeting-alt18:05
*** david-lyle has joined #openstack-meeting-alt18:05
kevinbentoni’m on free airport wifi so my connenction might be unstable18:05
*** eankutse has quit IRC18:05
sc68calkevinbenton: ok - no worries :)18:05
*** eankutse has joined #openstack-meeting-alt18:05
sc68calSo it's 5 after, let's go ahead and start introductions - I'm Sean Collins and I work at Comcast18:05
sc68cal#topic introductions18:05
*** openstack changes topic to "introductions (Meeting topic: neutron_qos)"18:05
smonovHi guys. I'm Simeon Monov and work at IBM.18:06
kevinbentonI’m Kevin Benton and I work at Big Switch Networks18:07
*** sarob_ has quit IRC18:07
*** paulczar has left #openstack-meeting-alt18:08
*** btully has left #openstack-meeting-alt18:08
*** yogeshmehra has joined #openstack-meeting-alt18:08
KanzheKanzhe at Big Switch Network18:08
pcarverPaul Carver @ AT&T18:08
*** _nadya_ has joined #openstack-meeting-alt18:09
*** Yogi11 has quit IRC18:09
sc68calanyone else?18:09
sc68calOK - I'll just lay out what I've got so far for an agenda18:10
sc68cal#topic agenda18:10
*** openstack changes topic to "agenda (Meeting topic: neutron_qos)"18:10
sc68calReally the two things to talk about so far are a recap of the meeting we had in the neutron pod at the summit, and discussion of the current spec for the API in neutron-specs18:11
sc68calThen turn it over to open discussion, to give people time to digest the spec18:11
*** pballand has joined #openstack-meeting-alt18:11
sc68calany questions?18:12
kevinbentonsc68cal: do you have a link handy for the spec?18:12
*** Yogi1 has joined #openstack-meeting-alt18:12
sc68calkevinbenton: yup - https://review.openstack.org/#/c/88599/18:12
sc68cal#topic ATL summit recap18:12
*** openstack changes topic to "ATL summit recap (Meeting topic: neutron_qos)"18:12
*** Yogi11 has joined #openstack-meeting-alt18:12
sc68calSo for those that didn't attend, we had a well attended meeting at the networking pod at the ATL summit18:12
sc68calLots of really good discussions about where the API is, and what people are doing around QoS currently, and how we can bind everything together with a vendor neutral API18:13
*** nati_ueno has quit IRC18:13
*** nati_ueno has joined #openstack-meeting-alt18:14
*** Youcef has joined #openstack-meeting-alt18:14
sc68calSo currently I am working on improving the spec that was submitted to Neutron-specs, since the QoS extension API was mostly designed in Launchpad, so I am working to pull things into a single document18:15
sc68cal#topic spec18:15
*** openstack changes topic to "spec (Meeting topic: neutron_qos)"18:15
sc68cal#link https://review.openstack.org/#/c/88599/18:15
sc68cal#undo18:15
openstackRemoving item from minutes: <ircmeeting.items.Link object at 0x235d5d0>18:15
sc68cal#link https://review.openstack.org/#/c/88599/ QoS API extension specification18:15
kevinbentonsc68cal: so after a quick look at it. where is the association of a policy to a port/network going to be stored?18:16
sc68calkevinbenton: the API extension adds a new attribute to Ports and Networks18:16
sc68calqos_id18:16
sc68calto link back to a QoS object18:16
*** Yogi1 has quit IRC18:17
sc68calThe REST API impact section shows the code, but it probably needs to be made more explicit18:17
pcarverThe biggest issue in relation to the prototype we've been working on is that we're trying to make bandwidth guarantees between pairs of points. That doesn't fit exactly onto having the QoS be tied to a single port or network.18:17
sc68calit's a bit too low-level, tied directly to the WSGI interface of Neutron18:18
sc68cal(the EXTENDED_ATTRIBUTES_2_0 piece)18:18
sc68calpcarver: Are the pairs of ports on the same neutron net18:18
sc68calor between different networks in Neutron18:19
pcarverTypically I think they will be, although that includes traffic out to WAN via Q-router18:19
pcarverBut it wouldn't be 100% of traffic on that neutron network18:19
kevinbentonsc68cal: i see. so it will just be QOS: UUID in a network object18:20
sc68calkevinbenton: correct18:20
kevinbentonsc68cal: can we have a notion of a default QOS policy applied to networks and ports without one explicitly set?18:20
kevinbentonsc68cal: i’m thinking of a completely admin-driven workflow in this case where tenants aren’t allowed to set their own QoS policies18:21
Kanzhesc68cal: Would it make sense to have a separate mapping table, where QOS can be mapped to port, network, or other objects if other use case pops out?18:21
sc68calpcarver: I see - the difficulty with that is how do you define a QoS where the destination is on the WAN18:22
sc68caland out of the purview of Neutron18:22
*** krtaylor has quit IRC18:22
sc68calYou'd either create a network that goes out to the WAN, and associate a QoS with that entire network18:22
sc68calor go per-port18:22
pcarversc68cal: yes, the WAN is outside Neutron. We're assuming a DSCP honoring WAN that the OpenStack environmnet can hand off to18:23
sc68calyou'd just have to make a net that only egress traffic goes on, so you don't have the qos apply to traffic that is not egressing18:23
sc68calkevinbenton: Kanzhe: will get to your questions :)18:23
sc68calpcarver: excellent - that is very close to our usecase as well18:23
sc68calkevinbenton: we have a similar thought18:24
sc68calWe create networks that are owned by the admin tenant, and shared = true18:24
pcarverwe're focussing on guaranteeing bandwidth across the datacenter/LAN and getting the marked traffic out to the WAN18:24
sc68calthen we set a QoS policy on that, and tenants attach to it18:24
*** tonytan4ever has left #openstack-meeting-alt18:24
Kanzhepcarver: sc68cal , If the QOS mapping is in a separate table. One can construct a port-pair, then map qos to the port-pair.18:24
sc68calpcarver: OK - so looks like we're good at least on that if you do a network dedicated to just getting out to the WAN18:25
sc68calpcarver: we just need to figure out how we want to mark + ratelimit18:25
pcarveranother part of what we're doing is making sure that they underlying physical network has sufficient bandwidth on th erequired paths across physical links18:26
sc68calKanzhe: Correct, you could create a QOS policy and just apply the two ports18:26
sc68calinstead of the network18:26
*** jasonb365 has joined #openstack-meeting-alt18:26
sc68calbut it would apply to all traffic leaving those ports, unless your driver supports doing by destination address18:26
pcarverWe're interested in figuring out more about the discussion that has been going on the mailing list about physical topology18:26
sc68calpcarver: There was also a post that someone from the climate team posted18:27
sc68calsince climate is supposed to handle capacity and resource allocation - the context was for reserving IP addresses18:27
pcarverjust marking traffic isn't sufficient if the underlying physical network doesn't have sufficient bandwidth to meet the guaranteeds18:27
sc68calbut it might also apply to bandwidth capacity18:27
pcarverthat's why we've viewed it as an "admission conrol" problem18:27
pcarvera key capability is to be able to deny reservations if they would exceed the physical capacity18:28
sc68calpcarver: To me, that sounds like right up the alley of Climate18:28
*** jmontemayor has joined #openstack-meeting-alt18:29
pcarverbecause if you can't deny reservations then eventually you'll reach a point where all the traffic is highly marked and still gets poor throughput18:29
sc68calwe may need to get Neutron to expose bandwidth capacity so that Climate can make those decisions18:29
*** rueben has joined #openstack-meeting-alt18:29
*** demorris has joined #openstack-meeting-alt18:29
*** jmontemayor has quit IRC18:29
pcarverClimate is yet another project that I haven't had enough time to do all the reading on. Definitely on the "to read" list18:29
sc68calStill spitballing, but also Ceilometer18:30
sc68calthat would provide the real time counters as to utilization18:30
*** jmontemayor has joined #openstack-meeting-alt18:30
sc68calProbably does packet/byte counters already, or should18:30
*** slogan has joined #openstack-meeting-alt18:30
sc68calso between neutron climate and cielometer you could get a good idea of how much BW is in use, vs. how much total18:30
*** pballand has quit IRC18:31
DinaBelovapcarver - not Climate, Blazar is the new name)18:31
*** rueben has quit IRC18:31
sc68calAnyway, that's pretty deep in the weeds :)18:31
pcarversc68cal: I think you're talking about after the fact.18:31
pcarversc68cal: That's not a bad idea but doesn't make guarantees.18:31
*** rueben has joined #openstack-meeting-alt18:31
*** shivamshukla_ has quit IRC18:32
pcarverWe're thinking of VoIP use cases18:32
sc68calComcast has similar needs ;)18:32
pcarverThough video is certainly an area where you'd also want guarantees18:32
sc68calhonestly guarantees of BW is a huge space - it probably warrants *at least* its own spec18:33
sc68calbut before we get too carried away, any other q's about the qos api ext as it exists currently?18:33
pcarverDoes the QoS subteam need a sub-subteam?18:33
*** alazarev has quit IRC18:33
*** Barker has joined #openstack-meeting-alt18:34
pcarver:-)18:34
sc68cal:-)18:34
sc68calif someone puts a spec together, let's see where it goes18:34
kevinbentonfor bandwidth guaruntees?18:35
sc68calyeah18:35
sc68caland capacity18:35
sc68caloff the top of my head, it also probably has some overlap with group based policies18:35
*** slogan_ has joined #openstack-meeting-alt18:35
kevinbentonyeah, i agree that this patch gives us a good starting point and at least a high-level object to start expressing these needs in18:35
sc68calmaybe if we get some good pieces into this API, we could piggy back on GBPO to make those guarantees18:36
*** amytron has joined #openstack-meeting-alt18:36
sc68calwhere you say - guarantee X bandwith via GBPO and GBPO drives that via the qos api18:36
sc68calplus all the other pieces I mentiond ;)18:36
*** emaganap has quit IRC18:36
sc68caloh, the review finally rendered18:37
sc68cal#link http://docs-draft.openstack.org/99/88599/3/check/gate-neutron-specs-docs/f246385/doc/build/html/specs/juno/qos-api-extension.html QoS API extension (rendered)18:37
*** chuckC has quit IRC18:38
*** slogan has quit IRC18:38
*** ranjitha has joined #openstack-meeting-alt18:38
kevinbentoni have to leave early, plane is boarding now. sc68cal: thanks for putting this on18:39
sc68calkevinbenton: have a safe flight - thanks for joining!18:39
Kanzhekevinbenton: See u later. :-)18:40
sc68calIf there isn't any other questions - I'll give everyone back 15 minutes to let people digest the spec, review + add comments, and such18:41
*** IlyaE has quit IRC18:41
pcarversc68cal: I'm all in favor of moving forward. I'll continue to work with my peers to formulate more input but not to slow anything down.18:42
pcarverOur view of QoS may be in addition to or complementary to the current spec.18:42
*** stan_lagun has left #openstack-meeting-alt18:42
Kanzhesc68cal: This is a good starting point for QOS.18:43
sc68calpcarver: perfect - please do continue to discuss use cases18:43
sc68calKanzhe: thank you :)18:43
*** emagana has joined #openstack-meeting-alt18:43
*** emagana has quit IRC18:44
*** zhiyan_ is now known as zhiyan18:44
sc68calOK - until next week, thank you everyone for attending!18:44
KanzheThanks, bye.18:44
*** markwash has quit IRC18:44
*** Kanzhe has quit IRC18:44
smonovthanks18:44
sc68calI am also on #openstack-neutron during USA EST18:44
sc68calas well as the ML18:45
sc68caltake care everyone!18:45
sc68cal#endmeeting18:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:45
openstackMeeting ended Tue May 27 18:45:14 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2014/neutron_qos.2014-05-27-18.01.html18:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2014/neutron_qos.2014-05-27-18.01.txt18:45
*** emaganap has joined #openstack-meeting-alt18:45
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2014/neutron_qos.2014-05-27-18.01.log.html18:45
*** jmontemayor has quit IRC18:45
*** smonov has left #openstack-meeting-alt18:45
*** rpodolyaka1 has joined #openstack-meeting-alt18:45
*** rueben has quit IRC18:46
*** chuckC has joined #openstack-meeting-alt18:46
*** Barker has quit IRC18:46
*** yogeshmehra has quit IRC18:46
*** akuznetsov has quit IRC18:46
*** beagles has left #openstack-meeting-alt18:47
*** jmontemayor has joined #openstack-meeting-alt18:49
*** IlyaE has joined #openstack-meeting-alt18:49
*** markvoelker has quit IRC18:50
*** jmontemayor has quit IRC18:50
*** alazarev has joined #openstack-meeting-alt18:50
*** IlyaE has quit IRC18:51
*** rueben has joined #openstack-meeting-alt18:52
*** zhiyan is now known as zhiyan_18:55
*** lsmola2 has joined #openstack-meeting-alt18:56
*** markvoelker has joined #openstack-meeting-alt18:58
*** nati_ueno has quit IRC18:58
*** nati_ueno has joined #openstack-meeting-alt18:59
*** arnaud__ has joined #openstack-meeting-alt18:59
*** arnaud__ has quit IRC18:59
*** caleb_ has quit IRC19:00
*** amytron has quit IRC19:00
*** derekh_ has joined #openstack-meeting-alt19:02
jristo/19:03
*** jasonb365 has quit IRC19:04
*** morazi has joined #openstack-meeting-alt19:05
*** jasonb365 has joined #openstack-meeting-alt19:05
*** baoli has quit IRC19:05
*** Barker has joined #openstack-meeting-alt19:05
*** baoli has joined #openstack-meeting-alt19:06
*** amytron has joined #openstack-meeting-alt19:06
*** pdmars has joined #openstack-meeting-alt19:06
*** tvoran has joined #openstack-meeting-alt19:07
*** jmontemayor has joined #openstack-meeting-alt19:07
*** rockyg has joined #openstack-meeting-alt19:07
*** IlyaE has joined #openstack-meeting-alt19:08
*** james_li has joined #openstack-meeting-alt19:12
*** rpodolyaka1 has quit IRC19:12
lsmola2is there a meeting today?19:13
*** rueben has quit IRC19:13
* lsmola2 waves at jrist19:14
jristlsmola: nope19:14
jristlsmola2: apparently just the one tomorrow at 1am MT19:14
lsmola2jrist, yeah I am just checking the ical19:15
*** vkmc has quit IRC19:15
*** dlenrow has joined #openstack-meeting-alt19:19
jristlsmola: I guess you can go to sleep19:20
jrist;)19:20
*** lenrow has quit IRC19:22
*** morazi has left #openstack-meeting-alt19:22
*** kenhui has quit IRC19:24
*** _nadya_ has quit IRC19:31
*** nati_ueno has quit IRC19:33
*** caleb_ has joined #openstack-meeting-alt19:35
*** dlenrow has quit IRC19:36
*** ametts has left #openstack-meeting-alt19:36
*** lsmola2 has quit IRC19:40
*** tonytan4ever has joined #openstack-meeting-alt19:43
*** SumitNaiksatam has joined #openstack-meeting-alt19:44
*** nelsnelson has quit IRC19:44
*** alazarev has quit IRC19:45
*** nelsnelson has joined #openstack-meeting-alt19:45
*** dprince has quit IRC19:45
*** andreaf has joined #openstack-meeting-alt19:46
*** zhiyan_ is now known as zhiyan19:46
*** rueben has joined #openstack-meeting-alt19:48
*** rueben_ has joined #openstack-meeting-alt19:49
*** nati_ueno has joined #openstack-meeting-alt19:50
*** james_li has quit IRC19:51
*** ranjitha has quit IRC19:52
*** rueben_ has quit IRC19:52
*** rueben has quit IRC19:53
*** dims has quit IRC19:54
*** rueben has joined #openstack-meeting-alt19:54
*** rueben has quit IRC19:54
*** james_li has joined #openstack-meeting-alt19:55
*** zhiyan is now known as zhiyan_19:55
*** michael-yu has quit IRC19:56
*** gyee has quit IRC19:57
*** caleb_ has quit IRC20:00
*** nati_ueno has quit IRC20:00
*** markmcclain has joined #openstack-meeting-alt20:00
*** manishg has joined #openstack-meeting-alt20:00
*** satish has quit IRC20:00
*** manishg has left #openstack-meeting-alt20:00
*** satish has joined #openstack-meeting-alt20:01
*** caleb_ has joined #openstack-meeting-alt20:01
*** caleb_ has quit IRC20:01
*** rueben has joined #openstack-meeting-alt20:01
*** caleb_ has joined #openstack-meeting-alt20:02
*** michael-yu has joined #openstack-meeting-alt20:03
*** michael-yu has quit IRC20:07
*** michael-yu has joined #openstack-meeting-alt20:10
*** baoli has quit IRC20:12
*** nati_ueno has joined #openstack-meeting-alt20:12
*** chuckC has quit IRC20:13
*** demorris has quit IRC20:15
*** dhellman_ has joined #openstack-meeting-alt20:15
*** baoli has joined #openstack-meeting-alt20:16
*** dmakogon has joined #openstack-meeting-alt20:16
*** denis_makogon has quit IRC20:17
*** dmakogon is now known as denis_makogon20:17
*** dmakogon_ has joined #openstack-meeting-alt20:17
*** Slower has quit IRC20:17
*** Slower has joined #openstack-meeting-alt20:18
*** otherwiseguy has quit IRC20:19
*** boris-42 has quit IRC20:21
*** boris-42 has joined #openstack-meeting-alt20:21
*** rbenali has joined #openstack-meeting-alt20:23
*** demorris has joined #openstack-meeting-alt20:25
*** rueben has quit IRC20:26
*** dims has joined #openstack-meeting-alt20:26
*** jmontemayor has quit IRC20:27
*** Slower has quit IRC20:28
*** satish has quit IRC20:29
*** satish has joined #openstack-meeting-alt20:29
*** pdmars has quit IRC20:29
*** tvoran has quit IRC20:31
*** jmontemayor has joined #openstack-meeting-alt20:33
*** amytron has quit IRC20:33
*** IlyaE has quit IRC20:34
*** IlyaE has joined #openstack-meeting-alt20:34
*** Slower has joined #openstack-meeting-alt20:34
*** alazarev has joined #openstack-meeting-alt20:37
*** Barker has quit IRC20:37
*** tonytan4ever has quit IRC20:37
*** vkmc has joined #openstack-meeting-alt20:37
*** vkmc has joined #openstack-meeting-alt20:37
*** tonytan4ever has joined #openstack-meeting-alt20:38
*** Slower has quit IRC20:39
*** demorris has quit IRC20:39
*** Slower has joined #openstack-meeting-alt20:39
*** otherwiseguy has joined #openstack-meeting-alt20:41
*** Barker has joined #openstack-meeting-alt20:41
*** jtomasek has joined #openstack-meeting-alt20:41
*** jprovazn has quit IRC20:44
*** rueben has joined #openstack-meeting-alt20:44
*** rueben has joined #openstack-meeting-alt20:45
*** ranjitha has joined #openstack-meeting-alt20:46
*** zhiyan_ is now known as zhiyan20:47
*** jecarey has quit IRC20:48
*** gduan has quit IRC20:49
*** garyduan has joined #openstack-meeting-alt20:49
*** jdob has quit IRC20:50
*** gokrokve_ has quit IRC20:52
*** gduan has joined #openstack-meeting-alt20:52
*** garyduan has quit IRC20:54
*** zhiyan is now known as zhiyan_20:56
*** alazarev has quit IRC20:56
*** caleb_ has quit IRC20:57
*** markwash has joined #openstack-meeting-alt20:58
*** julim has quit IRC21:01
*** gyee has joined #openstack-meeting-alt21:02
*** jecarey has joined #openstack-meeting-alt21:02
*** Leon has joined #openstack-meeting-alt21:03
*** Leon is now known as Guest9660021:03
*** fmaldonado_ has quit IRC21:03
*** rueben has quit IRC21:05
*** Barker has quit IRC21:06
*** Leonr has quit IRC21:06
*** chuckC has joined #openstack-meeting-alt21:07
*** Guest96600 has quit IRC21:07
*** gyee has quit IRC21:07
*** nati_ueno has quit IRC21:08
*** Barker has joined #openstack-meeting-alt21:09
*** nati_ueno has joined #openstack-meeting-alt21:11
*** michael-yu has quit IRC21:12
*** jtomasek has quit IRC21:12
*** dims has quit IRC21:13
*** michael-yu has joined #openstack-meeting-alt21:15
*** tnurlygayanov_ has quit IRC21:15
*** rockyg has quit IRC21:15
*** markwash_ has joined #openstack-meeting-alt21:16
*** alazarev has joined #openstack-meeting-alt21:16
*** markwash has quit IRC21:17
*** gyee has joined #openstack-meeting-alt21:18
*** rueben has joined #openstack-meeting-alt21:19
*** dhellman_ has quit IRC21:19
*** michael-yu has quit IRC21:20
*** markwash_ has quit IRC21:21
*** markmcclain has quit IRC21:21
*** markwash has joined #openstack-meeting-alt21:21
*** markwash has quit IRC21:23
*** jasonb365 has quit IRC21:23
*** rueben has quit IRC21:23
*** BrianB_ has quit IRC21:24
*** tonytan4ever has quit IRC21:25
*** rueben has joined #openstack-meeting-alt21:26
*** Obulpathi has quit IRC21:26
*** jasonb365 has joined #openstack-meeting-alt21:27
*** Obulpathi has joined #openstack-meeting-alt21:27
*** Obulpathi has quit IRC21:32
-openstackstatus- NOTICE: Zuul is offline due to an operational issue; ETA 2200 UTC.21:33
*** ChanServ changes topic to "Zuul is offline due to an operational issue; ETA 2200 UTC."21:33
*** michael-yu has joined #openstack-meeting-alt21:33
*** Leonr has joined #openstack-meeting-alt21:33
*** Leonr has quit IRC21:34
*** Leonr has joined #openstack-meeting-alt21:35
*** nati_ueno has quit IRC21:37
*** thangp has quit IRC21:37
*** caleb_ has joined #openstack-meeting-alt21:38
*** jasonb365 has quit IRC21:38
*** Yogi11 has quit IRC21:39
*** davidlenwell_ has joined #openstack-meeting-alt21:40
*** Barker has quit IRC21:41
*** noslzzp has quit IRC21:41
*** caleb_ has quit IRC21:42
*** IlyaE has quit IRC21:43
*** nati_ueno has joined #openstack-meeting-alt21:43
*** SumitNaiksatam has quit IRC21:43
*** stannie has quit IRC21:43
*** davidlenwell_ has quit IRC21:44
*** Yogi1 has joined #openstack-meeting-alt21:44
*** caleb_ has joined #openstack-meeting-alt21:44
*** baoli has quit IRC21:44
*** luizfar has quit IRC21:44
*** Yogi1 has quit IRC21:44
*** luizfar has joined #openstack-meeting-alt21:45
*** SumitNaiksatam has joined #openstack-meeting-alt21:45
*** davidlenwell has quit IRC21:45
*** dims has joined #openstack-meeting-alt21:45
*** Yogi1 has joined #openstack-meeting-alt21:46
*** davidlenwell has joined #openstack-meeting-alt21:47
*** Yogi1 has quit IRC21:48
*** zhiyan_ is now known as zhiyan21:48
*** mwagner_lap has quit IRC21:52
*** tomblank1 has joined #openstack-meeting-alt21:52
*** asalkeld has joined #openstack-meeting-alt21:53
*** emaganap has quit IRC21:54
*** emagana has joined #openstack-meeting-alt21:55
*** harlowja_ is now known as harlowja_away21:57
*** zhiyan is now known as zhiyan_21:57
*** harlowja_away is now known as harlowja_21:57
*** paulmo has joined #openstack-meeting-alt21:59
*** adrian_otto has joined #openstack-meeting-alt21:59
adrian_otto#startmeeting Solum Team Meeting22:00
openstackMeeting started Tue May 27 22:00:02 2014 UTC and is due to finish in 60 minutes.  The chair is adrian_otto. Information about MeetBot at http://wiki.debian.org/MeetBot.22:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:00
*** openstack changes topic to " (Meeting topic: Solum Team Meeting)"22:00
openstackThe meeting name has been set to 'solum_team_meeting'22:00
adrian_otto#link https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2014-05-27_2200_UTC Our Agenda22:00
adrian_otto#topic Roll Call22:00
*** openstack changes topic to "Roll Call (Meeting topic: Solum Team Meeting)"22:00
paulmoPaul Montgomery22:00
adrian_ottoAdrian Otto22:00
*** devkulkarni has joined #openstack-meeting-alt22:00
*** ravips has joined #openstack-meeting-alt22:00
asalkeldo/22:00
tomblank1tom blankenship22:00
james_liJames Li22:01
*** muralia has joined #openstack-meeting-alt22:01
ravipsRavi22:01
muraliamurali22:01
julienveyJulien Vey22:01
devkulkarniDevdatta22:01
*** caleb_ has quit IRC22:02
adrian_ottofor those of us in the USA, I hope you had a meaningful Memorial Day holiday yesterday.22:02
adrian_ottowelcome everyone22:02
*** caleb_ has joined #openstack-meeting-alt22:03
adrian_ottoif you have not recorded your attendance yet, feel free to chime in at any time.22:03
adrian_otto#topic Announcements22:03
*** openstack changes topic to "Announcements (Meeting topic: Solum Team Meeting)"22:03
*** shakamunyi has quit IRC22:03
adrian_ottoI do not have any announcements prepared. Do any team members have any announcements they would like to make?22:03
asalkeldno, not really22:04
paulmoJust a request to help keep this up to date: https://wiki.openstack.org/wiki/Solum/ExternalDependencies22:04
adrian_ottopaulmo: thanks!22:04
devkulkarnino22:04
adrian_ottook, next agenda item22:04
adrian_otto#topic Ratify Election Rules22:04
*** openstack changes topic to "Ratify Election Rules (Meeting topic: Solum Team Meeting)"22:04
adrian_otto#link https://wiki.openstack.org/wiki/Solum/Elections Proposed Election Rules22:04
*** datsun180b has joined #openstack-meeting-alt22:04
adrian_ottoPlease take a moment to review this, which was based on your feedback from last week's meeting22:05
*** nati_ueno has quit IRC22:05
devkulkarniWhat is fullform of ATC?22:05
paulmo+1 dev, was about to ask22:05
adrian_ottoI will be seeking any feedback you may have to amend it prior to moving for a #agreed by unanimous consent.22:05
adrian_ottoATC = Active Technical Contributor22:05
asalkeldyou have code in tree?22:06
*** otherwiseguy has quit IRC22:06
adrian_ottomeans that you contributed code in the prior release, or the one before that, yes22:06
*** denis_makogon has quit IRC22:06
*** yamahata has joined #openstack-meeting-alt22:07
devkulkarnielection result date is missing (I think we had talked about it as well)22:07
asalkeldseems like the normal procedure22:07
devkulkarnithanks adrian_otto for the clarification22:07
adrian_ottook, I added a new #1 and pushed the rest down22:07
adrian_ottoso reload to see taht22:07
*** paulczar has joined #openstack-meeting-alt22:08
adrian_ottoI should clarify the 6-month release cycles22:08
paulmo"previous two release cycles" = 1 year?  That seems to not jive with #222:08
devkulkarnijust a minor tweak .. "who has made a contribution to Solum in one of the two previous release cycles" ?22:08
adrian_ottoreload again22:08
adrian_ottoand just updated #2 accordingly22:09
paulmo1's timeframe doesn't match with 2 and 3 if I read it correctly22:09
devkulkarniokay, that clarifies that the contribution could be in any one of the previous two release cycles22:09
asalkeldisn't there a generic openstack one we can link to?22:10
adrian_ottopaulmo: ok thx. #3 corrected.22:10
-openstackstatus- NOTICE: Zuul is started and processing changes that were in the queue when it was stopped. Changes uploaded or approved since then will need to be re-approved or rechecked.22:10
paulmoIs anyone qualified?  There haven't been 2 full cycles right?22:10
adrian_ottoasalkeld: no, because they use a more sophisticated process22:10
*** shakamunyi has joined #openstack-meeting-alt22:10
asalkeldI see22:10
adrian_ottopaulmo, yes, you just need one contribution.22:10
adrian_ottoso all current contributors qualify by these rules22:10
adrian_ottook, any other feedback on the rules?22:11
asalkeldlooks ok to me22:11
paulmoAh, ok,… perhaps 1 should be clarified with "who has made a contribution _at any time_ in the previous..."22:11
devkulkarnilgtm22:11
tomblank1paulmo: yes, i think that would clarify what you were asking about..22:12
tomblank1otherwise, looks good and we should go with it...22:12
adrian_ottopaulmo: how about: An ATC is an Active Technical Contributor, defined as any individual who has made a contribution to Solum within the previous two 6-month release cycles.22:12
paulmoYes, sounds good to me.22:12
adrian_ottook, tx22:12
tomblank1adrian_otto: +122:13
adrian_ottook, updated.22:13
adrian_ottoReview just to be sure.22:13
*** gondoi is now known as zz_gondoi22:13
adrian_ottoany objections to adopting these rules by unanimous consent?22:13
devkulkarnino22:13
paulmono objection22:13
ravipsno22:13
tomblank1no objection22:13
asalkeldno22:13
paulczardo it!22:13
muralianope22:13
adrian_ottook, hearing no objections:22:13
peoplemergeI'm here, trying to triage multiple meetings22:14
datsun180bno objections22:14
adrian_otto#agreed We have approved the following election rules: https://wiki.openstack.org/wiki/Solum/Elections22:14
adrian_ottothanks everyone22:14
adrian_ottonow, if at any time anyoen feels there is a problem with the rules, I ask that you bring those concerns here before editing the page.22:14
adrian_ottoso that we can address them as a team.22:14
adrian_ottook, let's advance to our next order of business22:15
adrian_otto#topic Review Action Items22:15
*** openstack changes topic to "Review Action Items (Meeting topic: Solum Team Meeting)"22:15
adrian_ottodrian_otto to file/update blueprints for Pipeline and Environments22:15
adrian_otto+a22:15
adrian_ottoStatus: COMPLETE.22:15
adrian_otto#link https://blueprints.launchpad.net/solum/+spec/pipeline Pipeline Blueprint22:15
adrian_ottoSee also: Linked bug/task tickets (there are a few already, we may add more as needed)22:16
adrian_ottolink https://blueprints.launchpad.net/solum/+spec/environments Environments Blueprint22:16
adrian_ottoit also has linked task tickets22:16
adrian_ottoany remarks on these?22:16
asalkeldas long as it is consistent with our gdoc I guess22:17
devkulkarniAbout Environments..22:17
asalkeldwere we not going to call them "targets"22:17
adrian_ottowe can link the Gdoc to it too22:17
asalkeldto avoid confusion22:17
devkulkarniI know we have clearer understanding of pipelines, but I am not sure if we have similar about environments22:17
devkulkarniyes, lets put the link of the gdoc in both the blueprints22:18
asalkelddevkulkarni, well - we all know what's in them22:18
adrian_ottoanyone have that handy?22:18
*** baoli has joined #openstack-meeting-alt22:18
asalkeldhttps://docs.google.com/a/salkeld.id.au/document/d/1a0yjxKWbwnY7g9NZtYALEZdm1g8Uf4fixDZLAgRBZCU/edit#22:18
adrian_ottoasalkeld: tx!22:18
*** aratim has joined #openstack-meeting-alt22:19
devkulkarniasalkeld:22:19
asalkeldyip22:19
devkulkarnione of things that we were discussing at Atlanta was whether pipelines are same as environments22:19
adrian_ottoit is already linked22:19
*** SumitNaiksatam has quit IRC22:19
devkulkarnithis was during our Thursday's discussion22:19
adrian_ottoto Pileplines22:19
adrian_ottomy understanding is that we maintained that a Pipeline is not an Environment22:20
devkulkarniso thats what I meant when I said that there needs to be some more clarity22:20
asalkelddevkulkarni, that is more credentials related22:20
devkulkarnioh okay22:20
adrian_ottoA Pipeline is an imperative process through with Solum is expected to progress22:20
devkulkarniwe did agree to that I think22:20
asalkeldso you *could* use a different pipeline instead of making different targets22:21
asalkeld(as a different user)22:21
asalkeld(if that made sense)22:21
adrian_ottowhereas an Environment is a place where we relate one or more assemblies in a shared context that may contain additional constraints or attributes.22:21
*** rueben has quit IRC22:21
*** jmontemayor has quit IRC22:22
devkulkarniokay.. does gdoc has discussion about environments as well?22:22
devkulkarni(will read it) we can proceed..22:22
adrian_ottoasalkeld: yes, I recall that as an option.22:22
asalkelddevkulkarni, not so much22:22
asalkeldI struggle to see the real use cases (it's quite advanced functionality)22:22
devkulkarniyeah.. pipelines are very clear..22:23
adrian_ottook, we can revisit Pipelines and Environments in our Open Discussion as needed22:23
devkulkarni+122:23
adrian_ottoif we end up not needing one of those blueprints, we can deal with that22:23
*** SumitNaiksatam has joined #openstack-meeting-alt22:23
adrian_ottonext on our agenda is...22:23
adrian_otto#topic Mistral Integration Discussion22:23
*** openstack changes topic to "Mistral Integration Discussion (Meeting topic: Solum Team Meeting)"22:23
adrian_ottodevkulkarni: all yours22:23
adrian_otto#link https://blueprints.launchpad.net/solum/+spec/solum-mistral Superseded Blueprint22:24
devkulkarniso lots of WIPs and blueprints have been created regarding this..22:24
adrian_ottothat was the BP you filed22:24
adrian_otto#link https://blueprints.launchpad.net/solum/+spec/pipeline Pipeline Blueprint22:24
adrian_ottothat is the new one22:24
adrian_otto#link https://bugs.launchpad.net/solum/+bug/1322748 Initial Mistral Feature Task22:24
adrian_ottoand that is the individual work item assigned to you22:24
devkulkarniI think asalkeld and datsun would have most to discuss about Mistral22:24
devkulkarniI did an initial WIP of the workbook22:24
devkulkarnijust to kickstart discussions..22:24
asalkeldwell I am working to get plugins into mistral22:25
asalkeldand julienvey is working on oauth22:25
asalkeldwe also need oauth in mistral22:25
adrian_ottoasalkeld: can you take a moment to share with us why Keystone is not the answer?22:25
devkulkarniHow are folks finding using mistral for Solum overall?22:25
asalkeldand I have been fixing bugs/raising bugs22:25
*** noslzzp has joined #openstack-meeting-alt22:25
asalkeldadrian_otto, it is keystone22:26
asalkeld(keystone now does oauth1)22:26
paulmoA clarification of the authorization features needed and what is missing would really help me.22:26
adrian_ottoare we referring to "oauth" and "v3 Keystone trusts" as synonyms?22:26
asalkeldand the tokens don't suffer from chained trust issue22:26
asalkeldso we logically need "trusts"22:27
paulmoKeystone server has trusts and OAuth1a already if I understand the pull requests correctly.22:27
asalkeldbut oauth tokens can be passed from service to service22:27
* morganfainberg felt a disturbance in the force...^wirc network22:27
adrian_ottohi morganfainberg22:27
asalkeldtrusts really don't like getting rescoped22:27
morganfainbergadrian_otto, hi there.22:28
asalkeldso won't work from solum -> mistral -> heat22:28
asalkeldanyways there are bp's out for all 3 projects22:28
asalkeldand people signed up for the work22:28
devkulkarnimy main concern here is, are we sure that Solum's fine-grained auth needs are completely satisfied by OAuth1.022:29
devkulkarnior would Keystone's Trusts would be the answer for us22:29
morganfainbergasalkeld, so is there something we (as keystone) can do to help make keystone ... better and/or suit your needs if Trusts etc aren't sufficient?22:29
devkulkarninotwithstanding that Keystone does not yet have chained trusts22:29
asalkeldmorganfainberg, we would need chained-trusts22:30
*** emagana has quit IRC22:30
paulmoKeystone has OAuth1a: https://review.openstack.org/#/c/29130/22:30
morganfainbergasalkeld, a chained trust is a rescopable trust?22:30
asalkeldbut from speaking to heat team, they believe that oauth is the answer22:30
asalkeldmorganfainberg, I believe so22:30
devkulkarnimorganfainberg: are you asking, or are you saying they are one and the same?22:30
* morganfainberg isn't clear on specifics of what a chained-trust would encompass22:30
asalkeldmorganfainberg, you would be able to create a trust token from a trust token22:31
morganfainbergasalkeld, a different trust?22:31
asalkeldyes22:31
adrian_ottoone of a lesser scope, right?22:32
morganfainbergadrian_otto, i would hope so22:32
asalkeldeach service needs a trust_id22:32
*** nati_ueno has joined #openstack-meeting-alt22:32
asalkeld(yes)22:32
asalkeldsolum is totally broken without this22:32
asalkeldmy suggestion is to just use keystone oauth22:32
morganfainbergso you'd scope to X, which would have permission to scope to Y,Z,and Q22:32
morganfainbergvia trusts.22:33
asalkeldmorganfainberg, yip22:33
morganfainbergasalkeld, if keystone oauth would be sufficient i think it would be better than trying to secure chained trusts like that.  i see so many security issues and edge cases with that kind of trust scoping22:33
asalkeldagree22:33
asalkeldtho' I am not an auth guru22:34
*** caleb_ has quit IRC22:34
morganfainbergasalkeld, it might... might be a security concern since oauth i don't think limits roles provided22:34
morganfainbergin it's current implementation22:34
asalkeldmorganfainberg, I'll ask about it22:35
asalkeldnot sure what the heat team plan to do about that)22:35
morganfainbergasalkeld, yeah please come over to -keystone channel after your meeting (or a little later this week) and we can hammer out the usecase clearly22:35
asalkeldok22:35
morganfainbergasalkeld we might even be able to drag some heat folks in.22:35
morganfainbergif they're around22:35
devkulkarniasalkeld: please mention when you plan to meet with keystone folks22:35
*** kgriffs is now known as kgriffs|afk22:35
asalkeldmaybe a ml discussion22:35
adrian_ottoasalkeld: would you feel comfortable taking an action item to follow up with the keystone team?22:36
devkulkarni+1 to ml discussion as well22:36
morganfainbergML would be good too (better) to seed the convo at least22:36
asalkeldadrian_otto, for sure22:36
* morganfainberg goes back to lurking.22:37
devkulkarnithanks morganfainberg22:37
adrian_otto#action asalkeld follow up with keystone team by ML, and IRC (as needed) to explore options for multi-service trust tokens, OAuth, or chaining, and finding the right fit for Solum.22:37
paulmoGood trusts and OAuth article: http://adam.younglogic.com/2013/03/trusts-and-oauth/22:37
morganfainbergdevkulkarni, of course!22:37
morganfainbergwe have some ideas on some composite token magic we want to implement but i'll look for the ML topic, the composite token might suit your needs as well.22:37
adrian_ottook, so our current topic is Mistral Inegration22:37
adrian_ottoIntegration22:38
morganfainberganyway.. cheers and catch you all later22:38
adrian_ottotx again morganfainberg22:38
tomblank1thx morganfainberg:22:38
asalkeldso re: mistral integration22:38
*** Sukhdev has joined #openstack-meeting-alt22:38
asalkeldI think (besides auth) it will be in good shape soon22:38
asalkeldthere are some needed patches inflight22:39
devkulkarniin mistral?22:39
adrian_ottook, does anyone have further concerns or remarks regarding Mistral Integration?22:39
asalkeldyip22:39
devkulkarnido we need any action from us?22:39
asalkeldi think we should be involved in mistral22:39
adrian_ottoasalkeld: +122:40
asalkeldbut we can start using it really soon22:40
asalkeld(auth will stop us doing useful stuff tho')22:40
adrian_ottoso let's become a Mistral user as discussed in Atlanta, and see where that takes us22:40
devkulkarni+122:41
asalkeldthat is the most important issue right now22:41
adrian_ottoworst case we can persist account credentails in barbican, and individually auth to separate services as needed22:41
adrian_ottoand we can shed that for a more elegant solution once we find the right approach22:41
adrian_ottomy understanding is that Heat made the same first step, right?22:41
*** nati_uen_ has joined #openstack-meeting-alt22:42
adrian_ottobut even worse, because it stored the account username and password in its own db22:42
asalkeldyeah, but it's nasty22:42
devkulkarnithere was no barbican then :P22:42
adrian_ottoright22:42
*** nati_ueno has quit IRC22:42
adrian_ottobut sometimes progress requires a little nasty22:42
adrian_ottoso let's see if there is something we can do in limited scope with the auth facilities we already have22:42
paulczarjust use the admin user/tenant until oath is ready ?22:42
adrian_ottopaulczar: seems to me that would work for now22:43
julienveypaulczar: simple but works fine for now, +122:43
devkulkarninot a bad option (although we have to deal with namespaces for stacks and such)22:43
asalkeldpaulczar, it's what to do when mistral is doing something on our part22:43
adrian_ottoexcept you would not want to allow end users to modify workflows22:43
adrian_ottounless they treat Solum as a single tenant system22:43
asalkeldso we would have to imbed user/pass into mistral tasks22:43
devkulkarniwe have discussed admin user/tenant option on and off..22:43
asalkeld(maybe the target/environment can help)22:44
asalkeldbut when we get a git hook, we need to get a token - it would need to be based on user/password22:45
asalkeldmmm - ok : I'll look at a plan "b"22:46
adrian_ottouser/password = barbican secret token22:46
adrian_ottolet's only go that route if it's clearly less work than adding missing capability to keystone22:46
julienveywe should be able to come with oauth pretty soon, keystone doc about that is quite good22:47
asalkeldmaybe our target/env can have a barbican reference22:47
adrian_ottoor the new stuff for keystone is controversial to the extent it can't land soon22:47
devkulkarnijulienvey: do you have a link?22:47
julienveyyes, 1s22:47
julienveyhttps://github.com/openstack/keystone/blob/bab63bff9dc4fb94912f1e9b8a7bba8445f34fd5/doc/source/extensions/oauth1.rst22:47
asalkeldadrian_otto, for oauth we don't need changes to keystone22:47
julienveyhttps://review.openstack.org/#/c/80193/15/examples/scripts/exercise_v3_oauth.py22:47
* paulmo is still not sure what is missing in KeyStone. It has trusts, it has OAuth1a...22:47
julienveyhttps://github.com/openstack/identity-api/blob/master/v3/src/markdown/identity-api-v3-os-oauth1-ext.md#create-request-token-post-os-oauth1request_token22:48
devkulkarnipaulmo: we need chained trusts. ks is missing that right now.22:48
devkulkarnijulienvey: thanks!22:48
adrian_ottoasalkeld: yes, we could have an "unauthenticated" Environment per tenant where there is a trust token scoped to a mistral workflow, right?22:48
asalkeldI need to go take my boy to school...22:48
adrian_ottotanks asalkeld22:48
*** zhiyan_ is now known as zhiyan22:48
adrian_ottodevkulkarni: we have a whole pile of discussion topics for today22:48
asalkeldadrian_otto, trust tokens in their current form won't work22:48
devkulkarniadrian_otto: we can take some of them and continue for others next week?22:49
adrian_ottoLanguage Packs, STI, Task Review22:49
devkulkarnibtw, the chained trust discussion is done22:49
adrian_ottowhich are time sensitive, and which should we push?22:49
devkulkarnitime sensitive is custom lang pack22:49
adrian_ottook22:49
adrian_otto#topic Custom Language Pack Discussion22:50
*** openstack changes topic to "Custom Language Pack Discussion (Meeting topic: Solum Team Meeting)"22:50
adrian_ottogo22:50
devkulkarniI wanted to brain storm what is a custom lang pack and how would we go about implementing it..22:50
devkulkarninoorul and I discussed some of it which is captured in an etherpad22:50
adrian_ottoI have a concept of this22:50
devkulkarnihttps://etherpad.openstack.org/p/custom-language-packs22:50
adrian_ottoyou register an app "type" by creating a language pack resource22:50
adrian_ottoand that type has a Git Repo associated with it22:51
*** derekh_ has quit IRC22:51
julienveya LP is basically is a glance image22:51
adrian_ottoSolum will git clone that repo, and execute a well known script within it22:51
devkulkarniyes, and a custom one is an image which has custom tools/libraries installed22:51
julienveyso we miss only the builder to build the app with this LP ?22:52
adrian_ottothat should run in the context of the related glance image22:52
paulczaris there a difference between an LP and a custom LP apart from who created and uploaded it ?22:52
adrian_ottothat way a service provider can externally maintain a custom LP22:52
adrian_ottopaulczar: I hope not.22:52
devkulkarnipaulczar: I don't think so..22:52
paulczargood :)22:52
adrian_ottodevkulkarni: we might need to revisit this next week22:53
devkulkarniokay.. I think this is a good discussion.. this is what I had in mind.. for want to time I suggest we continue next week22:53
adrian_ottoor plan to follow up between now and then22:53
devkulkarniyep22:53
adrian_ottowhat are you blocked on?22:53
devkulkarninothing specifically.22:54
paulczarwe should require two entrypoints in the image a ‘build’ and a ‘run’ …    probably need some way to specify if the build is ‘slug’ style or ‘whole image’ style22:54
adrian_ottook22:54
devkulkarnijust wanted to discuss what folks had in mind22:54
adrian_otto#topic Open Discussion22:54
*** openstack changes topic to "Open Discussion (Meeting topic: Solum Team Meeting)"22:54
adrian_ottoI will move remaining topics to next week's agenda for us22:54
tomblank1devkulkarni: we can always start up a ML discussion as well if needed before next week22:54
*** atiwari has quit IRC22:54
devkulkarnisounds good adrian_otto22:55
devkulkarniIn 5 minutes, what do we need for this "Nova docker driver improvements" :)22:55
adrian_ottoso an LP could either be an image that has a well known script inside of it that the instance executes22:55
devkulkarniIts here: https://wiki.openstack.org/wiki/Solum/HighLevelRoadmap22:55
datsun180bdevkulkarni: improve it22:55
* datsun180b dusts off hands22:55
devkulkarniha ha22:55
adrian_ottoor an external repo with a well known script in it22:55
adrian_ottonova-docker has weak Glance integration which must be addressed22:57
paulczardevkulkarni: support for environment variables, a default set with the image +  a lightweight version of cloud-init that turns user-data into env variable to override22:57
adrian_ottoit needs a sensible multi-tenancy setup.22:57
adrian_ottoone way is to bypass the glance-registry and access glance directly22:57
adrian_ottos/glance-registry/docker-registry service/22:57
*** zhiyan is now known as zhiyan_22:58
paulczardevkulkarni: ability to specify custom docker registry endpoint per image/user/tenant/whatever22:58
devkulkarniis this all being done by the openstack-containers team? why is it on solum's roadmap as a list of deliverables?22:58
devkulkarnithanks adrian_otto and paulczar for details22:59
adrian_ottoit can move from our roadmap when other teams commit to them as deliverables.22:59
adrian_ottobut until them, we see them as our concerns22:59
*** andreaf has quit IRC22:59
paulczardevkulkarni: ability to register an empty image in glance which has enough details for nova-docker to go and fetch the image from provided registry22:59
devkulkarniokay. makes sense.22:59
adrian_ottook, time has elapsed for our meeting22:59
adrian_ottothanks everyone for attending22:59
tomblank1and we (Solum team) may have to actually develop that code22:59
*** james_li has left #openstack-meeting-alt22:59
adrian_ottotomblank1: yes22:59
adrian_otto#endmeeting22:59
*** openstack changes topic to "Zuul is offline due to an operational issue; ETA 2200 UTC."22:59
openstackMeeting ended Tue May 27 22:59:56 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/solum_team_meeting/2014/solum_team_meeting.2014-05-27-22.00.html22:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/solum_team_meeting/2014/solum_team_meeting.2014-05-27-22.00.txt23:00
openstackLog:            http://eavesdrop.openstack.org/meetings/solum_team_meeting/2014/solum_team_meeting.2014-05-27-22.00.log.html23:00
*** paulczar has left #openstack-meeting-alt23:00
*** paulmo has left #openstack-meeting-alt23:00
*** tomblank1 has left #openstack-meeting-alt23:00
*** michael-yu has quit IRC23:00
*** michael-yu has joined #openstack-meeting-alt23:01
*** datsun180b has quit IRC23:02
*** muralia has quit IRC23:03
*** baoli has quit IRC23:06
*** beyounn_1 has quit IRC23:06
*** mwagner_lap has joined #openstack-meeting-alt23:08
*** beyounn_1 has joined #openstack-meeting-alt23:08
*** satish has quit IRC23:10
*** aratim has quit IRC23:12
*** jjmb has joined #openstack-meeting-alt23:14
*** rueben has joined #openstack-meeting-alt23:15
*** yamahata has quit IRC23:16
*** jjmb1 has joined #openstack-meeting-alt23:16
*** jjmb has quit IRC23:19
*** devkulkarni has quit IRC23:20
*** SumitNaiksatam has quit IRC23:23
*** otherwiseguy has joined #openstack-meeting-alt23:23
*** luizfar has quit IRC23:24
*** SumitNaiksatam has joined #openstack-meeting-alt23:24
*** rueben has quit IRC23:25
*** david-lyle has quit IRC23:25
*** jjmb1 has quit IRC23:26
*** ravips has quit IRC23:28
*** noslzzp has quit IRC23:29
*** igordcard has quit IRC23:29
*** jjmb has joined #openstack-meeting-alt23:34
*** TravT has quit IRC23:35
*** baoli has joined #openstack-meeting-alt23:39
*** aratim has joined #openstack-meeting-alt23:41
*** gokrokve has joined #openstack-meeting-alt23:41
*** jjmb has quit IRC23:42
*** ranjitha has quit IRC23:42
*** tdruiva has quit IRC23:44
*** tdruiva has joined #openstack-meeting-alt23:47
*** michael-yu has quit IRC23:50
*** eguz has joined #openstack-meeting-alt23:51
*** carl_baldwin_ has quit IRC23:52
*** eghobo has quit IRC23:55
*** luizfar has joined #openstack-meeting-alt23:55
*** baoli has quit IRC23:56

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