Tuesday, 2014-06-03

*** jayaram has joined #openstack-meeting-alt00:00
*** pballand has joined #openstack-meeting-alt00:01
*** marcoemorais has joined #openstack-meeting-alt00:10
*** ranjitha has quit IRC00:11
*** jayaram has quit IRC00:12
*** rmoe has quit IRC00:15
*** nati_uen_ has quit IRC00:16
*** zhiyan_ is now known as zhiyan00:16
*** nati_ueno has joined #openstack-meeting-alt00:17
*** TravT has quit IRC00:18
*** SumitNaiksatam has quit IRC00:18
*** marcoemorais has quit IRC00:21
*** nati_ueno has quit IRC00:21
*** IlyaE has joined #openstack-meeting-alt00:21
*** safchain_ has quit IRC00:22
*** pballand has quit IRC00:24
*** _nadya_ has quit IRC00:25
*** arnaud has joined #openstack-meeting-alt00:29
*** jjmb has quit IRC00:30
*** gokrokve has quit IRC00:30
*** rmoe has joined #openstack-meeting-alt00:30
*** nati_ueno has joined #openstack-meeting-alt00:32
*** cjellick has quit IRC00:33
*** cjellick has joined #openstack-meeting-alt00:34
*** chuckC has quit IRC00:34
*** Yogi11 has quit IRC00:37
*** cjellick has quit IRC00:38
*** otherwiseguy has quit IRC00:45
*** nati_ueno has quit IRC00:46
*** nati_ueno has joined #openstack-meeting-alt00:47
*** chuckC has joined #openstack-meeting-alt00:50
*** nati_ueno has quit IRC00:51
*** _nadya_ has joined #openstack-meeting-alt00:52
*** SumitNaiksatam has joined #openstack-meeting-alt00:54
*** bdpayne has quit IRC00:54
*** banix has joined #openstack-meeting-alt00:55
*** Barker has joined #openstack-meeting-alt00:57
*** NehaV has quit IRC00:57
*** alazarev has quit IRC00:58
*** jaypipes has joined #openstack-meeting-alt01:01
*** caleb_ has joined #openstack-meeting-alt01:01
*** oomichi has quit IRC01:04
*** gokrokve has joined #openstack-meeting-alt01:04
*** nati_ueno has joined #openstack-meeting-alt01:07
*** caleb_ has quit IRC01:08
*** jaypipes has quit IRC01:09
*** nosnos has joined #openstack-meeting-alt01:09
*** Barker has quit IRC01:10
*** Barker has joined #openstack-meeting-alt01:12
*** alazarev has joined #openstack-meeting-alt01:16
*** otherwiseguy has joined #openstack-meeting-alt01:18
*** nati_ueno has quit IRC01:23
*** nati_ueno has joined #openstack-meeting-alt01:24
*** nati_ueno has quit IRC01:24
*** Yogi1 has joined #openstack-meeting-alt01:25
*** nati_ueno has joined #openstack-meeting-alt01:25
*** Yogi11 has joined #openstack-meeting-alt01:25
*** nati_uen_ has joined #openstack-meeting-alt01:26
*** nati_uen_ has quit IRC01:26
*** nati_uen_ has joined #openstack-meeting-alt01:26
*** satish has joined #openstack-meeting-alt01:26
*** nati_uen_ has quit IRC01:26
*** IlyaE has quit IRC01:28
*** Yogi1 has quit IRC01:29
*** nati_ueno has quit IRC01:29
*** IlyaE has joined #openstack-meeting-alt01:30
*** rueben has joined #openstack-meeting-alt01:39
*** nelsnels_ has joined #openstack-meeting-alt01:39
*** ranjitha has joined #openstack-meeting-alt01:40
*** morganfainberg is now known as morganfainberg_Z01:41
*** rueben has quit IRC01:42
*** nelsnelson has quit IRC01:42
*** rueben has joined #openstack-meeting-alt01:42
*** rueben has quit IRC01:42
*** jayaram has joined #openstack-meeting-alt01:44
*** ranjitha has quit IRC01:46
*** amytron has joined #openstack-meeting-alt01:48
*** _nadya_ has quit IRC01:51
*** Sukhdev has joined #openstack-meeting-alt01:51
*** dims has quit IRC01:59
*** alazarev has quit IRC02:00
*** yamahata has joined #openstack-meeting-alt02:02
*** Slower has quit IRC02:09
*** samstav has quit IRC02:09
*** gokrokve has quit IRC02:11
*** baoli has quit IRC02:11
*** oomichi has joined #openstack-meeting-alt02:11
*** ramishra has joined #openstack-meeting-alt02:17
*** _nadya_ has joined #openstack-meeting-alt02:17
*** Sukhdev has quit IRC02:17
*** dprince has quit IRC02:19
*** richm has quit IRC02:25
*** xianghui has joined #openstack-meeting-alt02:26
*** Barker has quit IRC02:27
*** caleb_ has joined #openstack-meeting-alt02:29
*** IlyaE has quit IRC02:30
*** baoli has joined #openstack-meeting-alt02:30
*** NehaV has joined #openstack-meeting-alt02:30
*** shakamunyi has quit IRC02:31
*** annashe__ has quit IRC02:32
*** sbalukoff has quit IRC02:32
*** tdruiva has joined #openstack-meeting-alt02:44
*** jjmb has joined #openstack-meeting-alt02:45
*** baoli has quit IRC02:46
*** arnaud has quit IRC02:47
*** zhiyan is now known as zhiyan_02:50
*** mberlin has joined #openstack-meeting-alt02:53
*** mberlin1 has quit IRC02:56
*** mattoliverau has quit IRC02:56
*** mattoliverau has joined #openstack-meeting-alt02:56
*** dtx00ff has joined #openstack-meeting-alt03:01
*** zhiyan_ is now known as zhiyan03:03
*** Yogi11 has quit IRC03:09
*** zz_gondoi is now known as gondoi03:12
*** dtx00ff has quit IRC03:13
*** coolsvap|afk is now known as coolsvap03:13
*** dtx00ff has joined #openstack-meeting-alt03:15
*** jjmb has quit IRC03:19
*** nosnos has quit IRC03:20
*** gondoi is now known as zz_gondoi03:21
*** xianghui has quit IRC03:25
*** satish has quit IRC03:25
*** jayaram has quit IRC03:26
*** xianghui has joined #openstack-meeting-alt03:28
*** flwang has joined #openstack-meeting-alt03:28
*** dtx00ff has quit IRC03:28
*** dtx00ff has joined #openstack-meeting-alt03:29
*** alazarev has joined #openstack-meeting-alt03:29
*** balajiiyer has joined #openstack-meeting-alt03:30
*** balajiiyer has quit IRC03:31
*** sbalukoff has joined #openstack-meeting-alt03:31
*** zz_gondoi is now known as gondoi03:33
*** jayaram has joined #openstack-meeting-alt03:33
*** dtx00ff_ has joined #openstack-meeting-alt03:40
*** dtx00ff has quit IRC03:43
*** gondoi is now known as zz_gondoi03:44
*** eghobo has quit IRC03:47
*** alazarev has quit IRC03:48
*** banix has quit IRC03:50
*** baoli has joined #openstack-meeting-alt03:51
*** emagana has joined #openstack-meeting-alt03:51
*** baoli has quit IRC03:57
*** alazarev has joined #openstack-meeting-alt03:59
*** zz_gondoi is now known as gondoi03:59
*** nosnos has joined #openstack-meeting-alt04:00
*** amcrn has quit IRC04:01
*** annashe__ has joined #openstack-meeting-alt04:01
*** gondoi is now known as zz_gondoi04:03
*** rmoe has quit IRC04:08
*** otherwiseguy has quit IRC04:08
*** rmoe has joined #openstack-meeting-alt04:10
*** NehaV has quit IRC04:14
*** emagana has quit IRC04:15
*** emaganap has joined #openstack-meeting-alt04:19
*** kenhui has joined #openstack-meeting-alt04:20
*** caleb_ has quit IRC04:24
*** baoli has joined #openstack-meeting-alt04:27
*** emaganap has quit IRC04:30
*** emagana has joined #openstack-meeting-alt04:30
*** baoli has quit IRC04:31
*** flwang has quit IRC04:32
*** emagana has quit IRC04:35
*** jayaram has quit IRC04:35
*** yogeshmehra has joined #openstack-meeting-alt04:42
*** eghobo has joined #openstack-meeting-alt04:42
*** NehaV has joined #openstack-meeting-alt04:45
*** alazarev has quit IRC04:48
*** harlowja is now known as harlowja_away04:48
*** SumitNaiksatam has left #openstack-meeting-alt04:51
*** mattgriffin has quit IRC04:51
*** NehaV has quit IRC04:54
*** zhiyan is now known as zhiyan_05:01
*** _nadya_ has quit IRC05:04
*** _nadya_ has joined #openstack-meeting-alt05:04
*** marcoemorais has joined #openstack-meeting-alt05:04
*** vkmc has quit IRC05:05
*** bmelande has joined #openstack-meeting-alt05:05
*** marcoemorais1 has joined #openstack-meeting-alt05:06
*** marcoemorais has quit IRC05:08
*** alazarev has joined #openstack-meeting-alt05:17
*** _nadya_ has quit IRC05:19
*** emagana has joined #openstack-meeting-alt05:20
*** emagana has quit IRC05:23
*** amcrn has joined #openstack-meeting-alt05:26
*** baoli has joined #openstack-meeting-alt05:28
*** yogeshmehra has quit IRC05:28
*** yogeshmehra has joined #openstack-meeting-alt05:29
*** IlyaE has joined #openstack-meeting-alt05:32
*** baoli has quit IRC05:33
*** yogeshmehra has quit IRC05:33
*** Youcef has joined #openstack-meeting-alt05:34
*** jcoufal has joined #openstack-meeting-alt05:41
*** yamamoto_ has joined #openstack-meeting-alt05:41
*** yogeshmehra has joined #openstack-meeting-alt05:43
*** coolsvap is now known as coolsvap|afk05:56
*** coolsvap|afk is now known as coolsvap06:01
*** bmelande has quit IRC06:05
*** kenhui has quit IRC06:17
*** xianghui has quit IRC06:18
*** kevinbenton has quit IRC06:19
*** _nadya_ has joined #openstack-meeting-alt06:25
*** baoli has joined #openstack-meeting-alt06:29
*** baoli_ has joined #openstack-meeting-alt06:30
*** baoli has quit IRC06:33
*** baoli_ has quit IRC06:35
*** IlyaE has quit IRC06:36
*** IlyaE has joined #openstack-meeting-alt06:36
*** nati_ueno has joined #openstack-meeting-alt06:38
*** _nadya_ has quit IRC06:39
*** IlyaE has quit IRC06:40
*** xianghui has joined #openstack-meeting-alt06:44
*** SushillKM has joined #openstack-meeting-alt06:46
*** SushillKM has left #openstack-meeting-alt06:46
*** alazarev has quit IRC06:48
*** NehaV has joined #openstack-meeting-alt06:50
*** xianghui has quit IRC06:51
*** ramishra has quit IRC06:51
*** coolsvap is now known as coolsvap|afk06:57
*** NehaV has quit IRC06:58
*** dtx00ff has joined #openstack-meeting-alt06:58
*** ramishra has joined #openstack-meeting-alt06:59
*** IlyaE has joined #openstack-meeting-alt07:00
*** dtx00ff_ has quit IRC07:01
*** coolsvap|afk is now known as coolsvap07:02
*** artem_panchenko1 has joined #openstack-meeting-alt07:04
*** artem_panchenko1 has left #openstack-meeting-alt07:04
*** xianghui has joined #openstack-meeting-alt07:08
*** gyee has quit IRC07:10
*** eghobo has quit IRC07:18
*** andreaf has joined #openstack-meeting-alt07:22
*** jtomasek has joined #openstack-meeting-alt07:23
*** dtx00ff_ has joined #openstack-meeting-alt07:24
*** andreaf has quit IRC07:26
*** dtx00ff has quit IRC07:28
*** IlyaE has quit IRC07:31
*** annashe__ has quit IRC07:37
*** annashe__ has joined #openstack-meeting-alt07:38
*** annashe__ has quit IRC07:42
*** ramishra has quit IRC07:42
*** nacim has quit IRC07:43
*** nacim has joined #openstack-meeting-alt07:43
*** jgallard has joined #openstack-meeting-alt07:49
*** stannie has joined #openstack-meeting-alt07:56
*** _nadya_ has joined #openstack-meeting-alt07:56
*** yamamoto_ has quit IRC08:00
*** ramishra has joined #openstack-meeting-alt08:01
*** safchain has joined #openstack-meeting-alt08:05
*** xianghui has quit IRC08:05
*** derekh_ has joined #openstack-meeting-alt08:20
*** nati_ueno has quit IRC08:21
*** xianghui has joined #openstack-meeting-alt08:22
*** coolsvap is now known as coolsvap|afk08:24
*** andreaf has joined #openstack-meeting-alt08:28
*** oomichi has quit IRC08:29
*** dtx00ff has joined #openstack-meeting-alt08:30
*** baoli has joined #openstack-meeting-alt08:31
*** tchaypo has joined #openstack-meeting-alt08:31
*** dtx00ff_ has quit IRC08:32
*** julienvey has joined #openstack-meeting-alt08:33
*** baoli has quit IRC08:35
*** oomichi has joined #openstack-meeting-alt08:35
*** flaper87|afk is now known as flaper8708:41
*** xianghui has quit IRC08:45
*** coolsvap|afk is now known as coolsvap08:46
*** dtx00ff has quit IRC08:46
*** ramishra has quit IRC08:47
*** amcrn has quit IRC08:49
*** yogeshmehra has quit IRC08:51
*** yogeshmehra has joined #openstack-meeting-alt08:52
*** yogeshmehra has quit IRC08:57
*** xianghui has joined #openstack-meeting-alt08:58
*** igordcard has joined #openstack-meeting-alt09:09
*** _nadya_ has quit IRC09:10
*** _nadya_ has joined #openstack-meeting-alt09:15
*** marcoemorais1 has quit IRC09:22
*** ramishra has joined #openstack-meeting-alt09:25
*** bogdando has joined #openstack-meeting-alt09:26
*** armax has joined #openstack-meeting-alt09:30
*** baoli has joined #openstack-meeting-alt09:32
*** baoli has quit IRC09:37
*** ranjitha has joined #openstack-meeting-alt09:43
*** flaper87 is now known as flaper87|afk09:50
*** armax has quit IRC09:52
*** amotoki has joined #openstack-meeting-alt09:57
*** ramishra has quit IRC10:01
*** jjmb has joined #openstack-meeting-alt10:01
*** tdruiva has quit IRC10:02
*** sbalukoff has quit IRC10:07
*** jgallard has quit IRC10:12
*** dtx00ff has joined #openstack-meeting-alt10:19
*** julienvey has quit IRC10:22
*** dkehn_ has joined #openstack-meeting-alt10:23
*** coolsvap is now known as coolsvap|afk10:24
*** xianghui has quit IRC10:26
*** dkehnx has quit IRC10:26
*** ramishra has joined #openstack-meeting-alt10:27
*** baoli has joined #openstack-meeting-alt10:32
*** tdruiva has joined #openstack-meeting-alt10:33
*** dtx00ff has quit IRC10:34
*** baoli has quit IRC10:37
*** _nadya_ has quit IRC10:38
*** _nadya_ has joined #openstack-meeting-alt10:40
*** tdruiva has quit IRC10:42
*** xianghui has joined #openstack-meeting-alt10:44
*** banix has joined #openstack-meeting-alt10:45
*** xianghui has quit IRC10:50
*** demorris has joined #openstack-meeting-alt10:51
*** yamahata has quit IRC10:52
*** zz_gondoi is now known as gondoi10:57
*** gondoi is now known as zz_gondoi10:58
*** flaper87|afk is now known as flaper8711:04
*** dims_ has joined #openstack-meeting-alt11:14
*** ranjitha has quit IRC11:19
*** demorris has quit IRC11:19
*** aostapenko has joined #openstack-meeting-alt11:20
*** banix has quit IRC11:22
*** julienvey has joined #openstack-meeting-alt11:29
*** Yogi1 has joined #openstack-meeting-alt11:34
*** nacim has quit IRC11:36
*** safchain has quit IRC11:37
*** yamahata has joined #openstack-meeting-alt11:39
*** dmakogon_ is now known as denis_makogon11:41
*** artem_panchenko has joined #openstack-meeting-alt11:44
*** artem_panchenko has left #openstack-meeting-alt11:44
*** flaper87 is now known as flaper87|afk11:46
*** nacim has joined #openstack-meeting-alt11:46
*** vkmc has joined #openstack-meeting-alt11:48
*** vkmc has joined #openstack-meeting-alt11:48
*** amytron has quit IRC11:48
*** ramishra has quit IRC11:50
*** ramishra has joined #openstack-meeting-alt11:50
*** ramishra has quit IRC11:50
*** ramishra has joined #openstack-meeting-alt11:51
*** mwagner_lap has quit IRC11:53
*** sankarshan has joined #openstack-meeting-alt11:54
*** safchain has joined #openstack-meeting-alt11:54
*** satish has joined #openstack-meeting-alt11:55
*** baoli has joined #openstack-meeting-alt12:00
*** sankarshan is now known as sankarshan_away12:01
*** jamie_h has joined #openstack-meeting-alt12:04
*** amotoki has quit IRC12:05
*** sbalukoff has joined #openstack-meeting-alt12:13
*** pdmars has joined #openstack-meeting-alt12:13
*** tdruiva has joined #openstack-meeting-alt12:15
*** pdmars has quit IRC12:16
*** pdmars has joined #openstack-meeting-alt12:16
*** jdob has joined #openstack-meeting-alt12:20
*** zhiyan_ is now known as zhiyan12:21
*** ramishra has quit IRC12:26
*** ramishra has joined #openstack-meeting-alt12:26
*** jgallard has joined #openstack-meeting-alt12:27
*** zhiyan is now known as zhiyan_12:31
*** dims_ has quit IRC12:31
*** dims_ has joined #openstack-meeting-alt12:32
*** oomichi has quit IRC12:32
*** xianghui has joined #openstack-meeting-alt12:33
*** ramishra has quit IRC12:36
*** tdruiva has quit IRC12:36
*** Yogi1 has quit IRC12:41
*** julim has joined #openstack-meeting-alt12:46
*** zhangleiqiang has joined #openstack-meeting-alt12:48
*** jcoufal has quit IRC12:52
*** jcoufal has joined #openstack-meeting-alt12:53
*** ramishra has joined #openstack-meeting-alt12:54
*** dprince has joined #openstack-meeting-alt12:56
*** rpodolyaka has joined #openstack-meeting-alt12:58
*** sadasu has joined #openstack-meeting-alt12:59
baoli#startmeeting PCI passthrough13:00
openstackMeeting started Tue Jun  3 13:00:13 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
baoliHi13:00
*** rpothier has joined #openstack-meeting-alt13:00
sadasuHello13:00
rpothierHi13:00
*** rpodolyaka has left #openstack-meeting-alt13:00
sadasubaoli: How is your spec review going?13:01
baolihttps://review.openstack.org/#/c/86606/19/specs/juno/pci-passthrough-sriov.rst13:01
baolithat's the latest version13:01
*** heyongli has joined #openstack-meeting-alt13:02
*** nacim has quit IRC13:02
baoliheyongli, Hi13:03
heyonglihi13:03
*** jaypipes has joined #openstack-meeting-alt13:04
baolilatest spec: https://review.openstack.org/#/c/86606/19/specs/juno/pci-passthrough-sriov.rst13:04
*** BrianB__ has joined #openstack-meeting-alt13:04
heyonglinotice John remove -2,  happy13:04
baoliJohn had some comments. The latest spec tried to address most of his concerns13:05
heyongliYunhong help to address the db init problem13:05
heyonglitrying change to node name, i think13:05
baoliheyongli, did he open a bug for that?13:06
heyongliyou open one, do not sync up for bug, i don't know yet13:06
baoliheyongli: are you talking about this one? https://review.openstack.org/#/c/82206/13:07
heyonglishould be this one, but i don't know the detail plan of yunhong13:07
baoliOk, I'll sync up with him.13:08
baoliRegarding the spec, please provide your comments if any. Hopefully, John and other cores will look at the latest version soon13:09
heyonglisure13:09
*** armax has joined #openstack-meeting-alt13:09
baolirpothier and I are working on the patches.13:10
heyongliwhich pach set? sriov?13:11
*** jecarey has quit IRC13:11
baoliwe'll be submitting patches for review soon.13:11
beaglescool!13:11
*** amytron has joined #openstack-meeting-alt13:11
baoliheyongli, the original poc will be broken up into several patches to facilitate reviews13:11
heyonglithat's very coll13:11
*** _nadya_ has quit IRC13:12
baoliI appreciate everyone's effort to move this forward!13:12
*** nosnos has quit IRC13:12
*** banix has joined #openstack-meeting-alt13:12
heyongliwe all hope sriov became reality,13:13
baoliheyongli, can you also review https://review.openstack.org/#/c/81954/13:13
baoliMaybe another +1 will prompt the cores for actions.13:13
heyonglii post +1, i will check it again tomorrow13:13
*** Yogi1 has joined #openstack-meeting-alt13:14
baolioh, got it. Thanks a lot!13:14
*** Yogi11 has joined #openstack-meeting-alt13:15
heyongliyourself could post +1, -:)13:15
heyongliany specific topic today?13:15
baolifeel free to bring up any topic. Otherwise, we can also discuss the other works/features listed on the meeting wiki13:17
*** Yogi1 has quit IRC13:18
*** Barker has joined #openstack-meeting-alt13:19
heyonglipossibly changing the names of existing vnic-types13:21
heyongliassociate a default vnic-type with a neutron network13:21
heyonglithese 2 seems pure neutron work13:22
baoliheyongli, that's true.13:22
heyongliwhat's admin controlled knobs13:22
*** mattgriffin has joined #openstack-meeting-alt13:22
baoliheyongli, in the original version of the spec, we had that discussion13:22
heyongliAPI related?13:23
heyongligot13:23
sadasuit appears we don't have any Nova related action items13:25
sadasufor Neutron, I don't think Irena is in the IRC13:26
heyongliseem not,13:26
sadasuI had a couple of questions on her spec13:26
baolisadasu: irena is on vacation this week. I forgot to mention that in the beginning of the meeting13:26
sadasuyes, I remember her mentioning that during the summit13:26
sadasubaoli: so is the meeting done?13:27
heyongliso short meeting?13:27
baolisadasu, what do you mean for nova-related action items?13:27
*** nacim has joined #openstack-meeting-alt13:27
baoliif you guys don't have anything else to talk about, we can call it a day.13:27
*** mfer has joined #openstack-meeting-alt13:28
sadasunothing from me13:28
heyongliyeah, nothing for today,13:28
heyongliso, bye13:28
sadasuthanks13:28
baolicool. We'll try to make some progress before next meeting.13:28
heyongliprobably +213:28
baoliheyongli, that would be great!13:29
*** nati_ueno has joined #openstack-meeting-alt13:29
baoliThanks everyone,and see you next week13:29
heyonglisee you13:29
baoli#endmeeting13:29
*** openstack changes topic to "Zuul is offline due to an operational issue; ETA 2200 UTC."13:29
openstackMeeting ended Tue Jun  3 13:29:28 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-06-03-13.00.html13:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-06-03-13.00.txt13:29
openstackLog:            http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-06-03-13.00.log.html13:29
*** heyongli has quit IRC13:29
*** rpothier has left #openstack-meeting-alt13:29
*** sadasu has quit IRC13:29
*** zz_gondoi is now known as gondoi13:30
*** ramishra has quit IRC13:31
*** dkehn_ is now known as dkehnx13:32
*** Obulpathi has joined #openstack-meeting-alt13:32
*** Obulpathi has quit IRC13:32
*** Obulpathi has joined #openstack-meeting-alt13:32
*** jgrimm has joined #openstack-meeting-alt13:33
*** aglarendil has joined #openstack-meeting-alt13:34
*** jecarey has joined #openstack-meeting-alt13:35
*** ramishra has joined #openstack-meeting-alt13:36
*** amytron has quit IRC13:37
*** nelsnels_ has quit IRC13:39
*** nelsnelson has joined #openstack-meeting-alt13:39
*** dkehn_ has joined #openstack-meeting-alt13:42
*** demorris has joined #openstack-meeting-alt13:43
*** otherwiseguy has joined #openstack-meeting-alt13:43
*** oomichi has joined #openstack-meeting-alt13:44
*** Yogi11 has quit IRC13:44
*** dkehnx has quit IRC13:45
*** dkehn_ is now known as dkehnx13:46
*** oomichi has quit IRC13:47
*** armax has quit IRC13:48
*** james_li has joined #openstack-meeting-alt13:51
*** kevinconway has joined #openstack-meeting-alt13:51
*** shakamunyi has joined #openstack-meeting-alt13:51
*** xianghui has quit IRC13:52
*** samstav has joined #openstack-meeting-alt13:52
*** satish has quit IRC13:53
*** james_li has quit IRC13:57
*** esker has joined #openstack-meeting-alt13:57
*** satish has joined #openstack-meeting-alt13:57
*** xuhanp has joined #openstack-meeting-alt13:59
*** jdob_ has joined #openstack-meeting-alt14:00
*** armax has joined #openstack-meeting-alt14:01
*** dane_leblanc has joined #openstack-meeting-alt14:01
*** thangp has joined #openstack-meeting-alt14:01
*** tdruiva has joined #openstack-meeting-alt14:02
*** jcoufal has quit IRC14:03
*** tdruiva has quit IRC14:03
*** tdruiva has joined #openstack-meeting-alt14:04
*** eankutse has joined #openstack-meeting-alt14:05
*** tdruiva has quit IRC14:08
*** _nadya_ has joined #openstack-meeting-alt14:08
*** tdruiva has joined #openstack-meeting-alt14:09
*** NehaV has joined #openstack-meeting-alt14:10
*** balajiiyer has joined #openstack-meeting-alt14:10
*** kgriffs|afk is now known as kgriffs14:11
*** jdob_ has quit IRC14:11
*** gondoi is now known as zz_gondoi14:11
*** tdruiva has quit IRC14:13
*** zz_gondoi is now known as gondoi14:13
*** ramishra has quit IRC14:14
*** amytron has joined #openstack-meeting-alt14:15
*** demorris has quit IRC14:17
*** flaper87|afk is now known as flaper8714:17
*** sreshetnyak has joined #openstack-meeting-alt14:18
*** Yogi1 has joined #openstack-meeting-alt14:20
*** demorris has joined #openstack-meeting-alt14:20
*** paul_glass has joined #openstack-meeting-alt14:21
*** mwagner_lap has joined #openstack-meeting-alt14:21
*** Yogi1 has left #openstack-meeting-alt14:23
*** alazarev has joined #openstack-meeting-alt14:28
*** andreaf has quit IRC14:29
*** nati_ueno has quit IRC14:29
*** tdruiva has joined #openstack-meeting-alt14:31
*** pballand has joined #openstack-meeting-alt14:32
*** eankutse has quit IRC14:33
*** eankutse has joined #openstack-meeting-alt14:34
*** eankutse has quit IRC14:34
*** eankutse has joined #openstack-meeting-alt14:34
*** gokrokve has joined #openstack-meeting-alt14:36
*** TravT has joined #openstack-meeting-alt14:39
*** spzala has joined #openstack-meeting-alt14:43
*** caleb_ has joined #openstack-meeting-alt14:49
*** dims_ has quit IRC14:49
*** paul_glass has quit IRC14:51
*** emagana has joined #openstack-meeting-alt14:51
*** rueben has joined #openstack-meeting-alt14:52
*** sriram has joined #openstack-meeting-alt14:54
*** jmontemayor has joined #openstack-meeting-alt14:54
*** jmontemayor has quit IRC14:54
*** jmontemayor has joined #openstack-meeting-alt14:54
*** ramashri has joined #openstack-meeting-alt14:55
*** emagana has quit IRC14:56
*** igordcard has quit IRC14:56
*** emagana has joined #openstack-meeting-alt14:56
*** paul_glass has joined #openstack-meeting-alt14:57
*** mspreitz has joined #openstack-meeting-alt14:58
*** balajiiyer has quit IRC14:58
*** melodous has joined #openstack-meeting-alt14:59
*** IlyaE has joined #openstack-meeting-alt14:59
*** alcabrera has joined #openstack-meeting-alt14:59
*** paul_glass1 has joined #openstack-meeting-alt14:59
*** tjanczuk has joined #openstack-meeting-alt15:00
*** paul_glass1 has quit IRC15:00
*** dane_leblanc has quit IRC15:01
*** paul_glass1 has joined #openstack-meeting-alt15:01
*** paul_glass1 has left #openstack-meeting-alt15:01
*** rueben has quit IRC15:01
*** luizfar has joined #openstack-meeting-alt15:01
*** cpallares has joined #openstack-meeting-alt15:01
cpallareso/15:02
*** prashanthr_ has joined #openstack-meeting-alt15:02
cpallares\o15:02
alcabrera(o)15:02
cpallares\0/15:02
*** samstav_ has joined #openstack-meeting-alt15:02
alcabrerahaha15:02
tjanczuk\015:02
*** paul_glass has quit IRC15:02
kgriffs#startmeeting marconi15:02
openstackMeeting started Tue Jun  3 15:02:42 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:02
*** openstack changes topic to " (Meeting topic: marconi)"15:02
openstackThe meeting name has been set to 'marconi'15:02
*** jcoufal has joined #openstack-meeting-alt15:02
*** caleb_ has quit IRC15:03
*** jcoufal has quit IRC15:03
vkmco/15:03
*** samstav_ has quit IRC15:03
kgriffso/15:03
*** jcoufal has joined #openstack-meeting-alt15:03
*** paul_glass has joined #openstack-meeting-alt15:03
*** paul_glass has left #openstack-meeting-alt15:03
*** safchain has quit IRC15:03
alcabrera~o~15:03
*** carl_baldwin has joined #openstack-meeting-alt15:03
cpallares\o_O/15:04
vkmc*\o/*15:04
kgriffs#topic Using the mailing list to offload meeting time15:04
*** openstack changes topic to "Using the mailing list to offload meeting time (Meeting topic: marconi)"15:04
prashanthr_lots of 'o' art in progress 0-015:04
kgriffsso, as you may have noticed, a few of us have being trying to use the mailing list more15:04
sriramo/15:04
*** safchain has joined #openstack-meeting-alt15:04
kgriffsI think it is a good way to have "the meeting before the meeting" which will make our agenda items go much quicker15:05
Obulpathio/15:05
*** xuhanp has quit IRC15:05
tjanczukI think ML works better than IRC for longer discussions that require more context.15:05
*** samstav has quit IRC15:05
kgriffs+115:05
tjanczukThe price is it takes longer to discuss.15:06
kgriffsalso, it allows more people in the community to join in the conversations, or at least follow along15:06
*** rueben has joined #openstack-meeting-alt15:06
kgriffstjanczuk: yep. I think we can find a balance between IRC, ML, and mtgs.15:06
*** emagana has quit IRC15:07
kgriffsWe should really discuss each topic in all three places, but strive to capture important notes/decisions in the ML if they come up elsewhere15:07
*** _nadya_ has quit IRC15:07
kgriffsjust my $0.0215:07
*** AAzza has joined #openstack-meeting-alt15:07
*** mpanetta has joined #openstack-meeting-alt15:08
kgriffsyou can also use the ML to vet and idea, and then we can finalize it in our meetings, which are also logged/recorded15:08
*** alazarev has quit IRC15:08
*** abettadapur has joined #openstack-meeting-alt15:08
*** malini has joined #openstack-meeting-alt15:09
alcabreraFrom a communications POV, it makes sense to engage the ML for questions of direction15:09
alcabreraare we building the thing that people want to use?15:09
kgriffsanyway, I'd like everyone to try to follow subjects starting with [marconi] on the mailing list, and participate in those threads15:09
tjanczukIt would be good if the responsiveness to ML topics was similar to IRC ones.15:10
kgriffsalcabrera: that's a good point. On that question, we may want to also use the user list (openstack@) to engage folks on usability and operations15:11
kgriffstjanczuk: +115:11
alcabreragood thought, kgriffs15:11
*** demorris has quit IRC15:11
kgriffsok, so let's everyone be more active on the mailing lists. Also, I'd like to see more activity on the Ask site from folks outside the core reviewers team. Just sayin'. :)15:12
kgriffsmoving on...15:12
*** caleb_ has joined #openstack-meeting-alt15:12
kgriffs#topic specs process15:13
*** openstack changes topic to "specs process (Meeting topic: marconi)"15:13
kgriffsmalini: can you summarize the discussion so far?15:13
malinisure15:13
maliniHope everybody had a chance to review the thread in ML15:13
alcabreraa bit15:13
maliniWe have most of OS moving the Specs route & I just wanted to pick everybody's brains if Marconi should too15:14
alcabrera#link http://lists.openstack.org/pipermail/openstack-dev/2014-June/036509.html15:14
*** zhangleiqiang has quit IRC15:14
maliniSpecs is good, because it bring a certain formal process in the design phase15:14
*** demorris has joined #openstack-meeting-alt15:14
maliniBut I think us being a small team, we dont need it yet15:14
maliniSince we do a lot of design discussions in IRC/ML/meetings15:15
*** ramishra has joined #openstack-meeting-alt15:15
*** samstav has joined #openstack-meeting-alt15:15
alcabreraI have a few thoughts on this15:15
malinialcabrera: sure15:15
*** emagana has joined #openstack-meeting-alt15:15
alcabreraI'm not sure how specs are being used across OS15:16
alcabrerabut15:16
*** tonytan4ever has joined #openstack-meeting-alt15:16
alcabrerawhere specs are most valuable, are not in reference to particular BPs, but rather15:16
alcabrerainto protcols15:16
alcabrerawire or whatnot15:16
alcabreragrammars15:16
alcabrerafor DSLs etc15:16
alcabreraand15:16
alcabrerafor HTTP expected behaviors15:16
alcabreraand APIs15:16
tjanczukI think having a spec up front is useful for controversial issues that need discussion. For all other issues it could be done post-mortem as documentation.15:16
malinifor clarity specs == design docs, in what I have seen for other OS projects15:16
malinitjanczuk: +115:16
kgriffsbasically, it is a formalization of the blueprinting process15:17
malini& tht too , we shud not require it for every bp15:17
kgriffsso, instead of editing a wiki page and linking that to a bp, you actually write up specs in text files and they go through the gerrit review process15:17
kgriffsiirc15:17
alcabreraqueue flavors would one area that would warrant a design spec, imo15:17
alcabrera**would be one15:17
kgriffstjanczuk: that makes sense15:17
sriramalcabrera: +115:17
kgriffsI think there are a few dimensions to this discussion15:18
kgriffsfirst, is which types of work items benefit from formal specs15:18
kgriffssecond, when you go to write that spec, what level of detail should go into it?15:19
*** ramishra has quit IRC15:19
malinikgriffs: can we just leave it to the implementor to decide when to write a spec & what shud go in it?15:20
malini the person who does the implementation cud write a spec to solicit feedback15:20
malinior document why something was done in a specific way15:20
kgriffsmalini: i think we could give them a lot of flexibility, but I would like to have a page on our wiki (contributor's guide) with some basic guidelines15:20
*** caleb_ has quit IRC15:21
kgriffsanyone can write a wiki page today and link to a bp. the difference with this new process is it goes through formal review15:21
maliniwe will also need some basic stuff done to enable using specs15:21
vkmcif we don't provide some basic guidelines we will end up reviewing the way specs has been written instead of focusing on the spec15:21
maliniadd a new github repo etc15:21
*** caleb_ has joined #openstack-meeting-alt15:21
alcabreraI like the idea of providing guidelines15:21
Obulpathi+1 for guidelines15:22
maliniAs a −1 for how to write guidelines, we will end up mandating stuff which wont make sense in each situation15:22
maliniMy idea behind spec is solicit feedback early on, when you are not sure how to implement15:22
kgriffsok, maybe before we forget about it, can someone create a placeholder page on the wiki under "contributor guide"? #link https://wiki.openstack.org/wiki/Marconi15:22
tjanczukGenerally speaking I'd rather be reviewing code than specs. For most changes whatever English one puts in the code submission is adequate as a spec.15:23
vkmchm.. thats true15:23
malinithe whole spec thing sounds uncomfortably similar to detailed design docs15:23
maliniI wud rather us not have DD for every case15:23
tjanczukDeath by waterfall15:23
kgriffsyeah...15:23
kgriffshmmm.15:24
alcabreraI agree with malini -- if we do anything spec-like, we must tread with caution15:24
alcabreraif we need design discussions, the place to do that is a combination of the ML, IRC, and meetings15:24
Obulpathiit does sound like design doc to me15:24
alcabreraa spec goes stale quickly for new ideas, so is only of value for things that have solidified15:25
alcabreraor have some promise of staying stable15:25
alcabreraalong the lines of semantic versioning15:25
kgriffsthe goal i think is to have a page to summarize those discussions to act as memory pegs and call out stuff that needs to be followed up on (TBD items)15:25
malinikgriffs: +115:26
alcabrerakgriffs: do you think we could achieve such a thing with wikis?15:26
kgriffsif we can find a way to do that more consistently with our bp's, i don't think we need the specs process at the moment, at least15:26
alcabrerakgriffs: +115:26
*** cjellick has joined #openstack-meeting-alt15:26
maliniLets just revisit using specs  @ K or a future release15:26
*** samstav has quit IRC15:26
alcabreramalini: agreed15:26
kgriffsI mean, we already do a fair job of it between wiki (marconi/specs/my-bp-name-here) and etherpad15:26
alcabrerakgriffs: oh yeah, etherpad too!15:26
maliniI think it makes sense for other teams working in diff TZ15:27
kgriffsmaybe we can think about shoring that up since it already seems to work pretty well, and revisit specs another time15:27
*** samstav has joined #openstack-meeting-alt15:27
*** emagana has quit IRC15:27
*** _nadya_ has joined #openstack-meeting-alt15:27
tjanczukfolks, I need to run in a few minutes, could we just summarize quickly the AMQP status next?15:27
malinisince flaper87 conveniently works in all TZ, we are covered for now ;)15:27
alcabrerahaha15:27
kgriffsheh15:27
Obulpathilol15:27
*** emagana has joined #openstack-meeting-alt15:28
*** _nadya_ has quit IRC15:28
alcabreratjanczuk: sounds like a good idea15:28
kgriffsok, so let's do a vote next meeting about specs, and think about ways to be a little more consistent about using wiki specs15:28
alcabreraamqp next?15:28
kgriffs#action kgriffs to hold vote on specs next meeting15:28
kgriffs#topic AMQP driver15:28
*** openstack changes topic to "AMQP driver (Meeting topic: marconi)"15:28
tjanczukI've been out for the last week+, I wonder if any progress code or decision-wise has been made on AMQP?15:29
kgriffsalcabrera, vkmc?15:29
kgriffsflaper87?15:29
vkmctjanczuk, I'm working on adding the support for AMQP15:29
vkmcso... we are going for AMQP 1.015:29
malinigtg now15:29
vkmcat least, as a first step into it15:29
kgriffsmalini: thanks! o/15:29
alcabreramalini: take care!15:30
vkmcmaybe we could add support for other AMQP versions in the future15:30
vkmcmalini, ttyl! :) o/15:30
*** balajiiyer has joined #openstack-meeting-alt15:30
*** esker has quit IRC15:30
*** malini is now known as malini_afk15:30
vkmcthe main blocker with the implementation of this driver is that the python library for qpid-proton is not available yet15:31
tjanczukWe had some discussions about this last time I was here. The gist is I am happy to write Rabbit support (AMQP 0.9). In fact I am doing it this week. The question is, can this be taken into Marconi when all is done?15:31
*** esker has joined #openstack-meeting-alt15:31
tjanczukRabbit has excellent Python library that is ready to go today.15:31
vkmcok, but that is a driver for Rabbit15:32
vkmcnot for AMQP15:32
*** gondoi is now known as zz_gondoi15:32
tjanczukYes, this is the driver for Rabbit (the most popular AMQP implementation out there)15:32
*** emagana has quit IRC15:32
tjanczukBesides, AMQP is a red herring here. I care about Rabbit not AMQP. I could as well use MQTT to talk to Rabbit if we choose so.15:33
alcabreraso, I feel like this is a question of legacy, and also about what we are willing to fit in the marconi repository15:33
vkmcof course, but right now we are focusing on flexibility15:33
vkmcadding a driver for AMQP allows us to be broker independent15:33
alcabreraon the side of legacy, it is my understanding that 0.9.1 is important to a lot of people, even though 1.0 is the target for newer implementattions15:33
*** gyee has joined #openstack-meeting-alt15:34
alcabreraI say this as an AMQP outsider, so my view might be skewed -- the ML can confirm this better than I15:34
kgriffsI think we may just need to bite the bullet and do two drivers, one for each15:34
vkmcthat would be the first step... later on, we could discuss adding a Rabbit driver to cover AMPQ < 1.015:34
*** demorris has quit IRC15:34
alcabreraI'm happy with the idea of going double-driver in-tree15:34
alcabreragiven that we have two eager volunteers: vkmc and tjanczuk15:35
kgriffsFrom what I understand, the Rabbit folks would be happy to prioritize their 1.0 support if they see enough demand for it, but I suspect it will be 1-2 years for that to happen15:35
alcabrerahow do you all feel about this?15:35
tjanczukRabbit and 1.0 is pipe dream IMO.15:35
kgriffsi'd basically call it "RabbitMQ driver" and "AMQP 1.0" driver.15:35
kgriffsI'd be fine with having both in-tree15:36
tjanczukkgriffs: +115:36
vkmcalcabrera, +115:36
Obulpathi+115:36
tjanczukSo, if I write a Rabbit driver, can we take it in?15:36
alcabrerayes15:36
kgriffstjanczuk: yes, there is the risk that Rabbit will never to 1.0, but if they do we can deprecate the 0.9 driver at that point.15:36
*** ramishra has joined #openstack-meeting-alt15:36
tjanczukExcellent, sounds like we are on the same page. Now I need to drive my kids to school ;)15:37
tjanczukI will be back on openstack-marconi later in the day.15:37
*** gokrokve has quit IRC15:37
alcabreratjanczuk: take care, and thanks for joining in15:37
vkmcsounds good since AMQP < 1.0 and AMQP 1.0 are two different protocols15:37
vkmctjanczuk, o/ ttyl!15:37
kgriffstjanczuk, vkmc: keep the team updated on what parts of the API can be supported, and which cannot.15:37
*** rueben has quit IRC15:37
kgriffswe have a little freedom with 1.1, and lots of freedom in 2.0 to make changes if needed15:38
Obulpathitjanczuk: take care!15:38
vkmckgriffs, will do, in fact I have some ideas to discuss after the meeting15:38
kgriffskk15:38
alcabreracool15:38
alcabreraany other thoughts on the amqp thread?15:39
kgriffs#topic Healthier Community: Let's Adopt a Code of Conduct15:40
*** openstack changes topic to "Healthier Community: Let's Adopt a Code of Conduct (Meeting topic: marconi)"15:40
kgriffsalcabrera?15:40
alcabrerayup!15:40
alcabreraso here's the situation15:40
alcabreraand it ranges outside of marconi, though I wanted to start the discussion here15:40
alcabreraopenstack's code of conduct is lacking in several ways15:41
*** dkehnx has quit IRC15:41
alcabrerait addresses many of the work related issues15:41
alcabrerabut does not cover a lot of the social interactions that happen15:41
alcabreralemme grab that link15:41
*** demorris has joined #openstack-meeting-alt15:41
*** dkehnx has joined #openstack-meeting-alt15:41
alcabrera#link http://www.openstack.org/legal/community-code-of-conduct/15:41
*** tjanczuk has quit IRC15:41
alcabrerathe only items that discuss interactions between people, are 2) and 4)15:42
alcabrera"Be respectful", and "If we disagree, consult others"15:42
alcabreraneither detail what is and isn't acceptable behavior15:42
alcabreraand leave it to general interpretation15:42
*** zz_gondoi is now known as gondoi15:42
alcabreraa solid code of conduct needs 4 things, as per15:42
alcabrera#link http://www.ashedryden.com/blog/codes-of-conduct-101-faq15:42
*** rueben has joined #openstack-meeting-alt15:43
alcabrerathe very first section in that link summarizes those requirements15:43
alcabreraand one more problem, aside from that15:43
*** morganfainberg_Z is now known as morganfainberg15:43
alcabrerais that the openstack CoC does not make it clear who to contact if something does come up15:43
*** eghobo has joined #openstack-meeting-alt15:44
alcabrerait makes mention of the TC and UC, but I contend that this is not enough15:44
kgriffsthat's a big one15:44
kgriffsaccountability is vital15:44
alcabrerayes!15:44
alcabreracodes of conduct are crucial for growing a healthty community15:45
alcabreraand I'd like to see openstack do better in this regard15:45
*** aratim has joined #openstack-meeting-alt15:45
cpallaresYep, especially one growing and changing.15:45
alcabrerawhat do you all think? :)15:45
*** gondoi is now known as zz_gondoi15:45
kgriffsI think the current code of conduct is too often ignored.15:45
Obulpathiwe should submit a feedback ...15:46
*** tomblank has joined #openstack-meeting-alt15:46
vkmcyou are right that there are vital parts missing on the current code15:46
vkmcand yeah... agree with kgriffs15:46
*** andreaf has joined #openstack-meeting-alt15:46
kgriffshowever15:46
Obulpathiasking them to update on the issues .. especially whom to contact when something is wrong15:46
vkmc+1 Obulpathi15:46
kgriffsi did see some positive signs at the conference that people are becoming more cognizant of this topic15:46
*** rmoe has quit IRC15:46
kgriffs...and supportive of making it better15:47
alcabreragood to hear15:47
*** nati_ueno has joined #openstack-meeting-alt15:47
alcabreraI like Obulpathi's suggestions - we need action15:47
kgriffshowever, the movement will need some care and feeding for it to bear fruit15:47
alcabreraagreed, kgriffs.15:47
alcabrerait is no simple matter, because we need a whole lot of (4) from ashedryden's faq15:48
alcabreraTraining and reference materials from those that would moderate the community15:48
vkmcwe also add in the code that people should not have a defensive15:48
Obulpathiwe also go through CoC for Deabian, Linux, Python and see how they are dealing with these issues15:48
cpallaresObulpathi: +1 :)15:48
*** zz_gondoi is now known as gondoi15:48
*** ramishra has quit IRC15:49
cpallaresI think alcabrera had some good suggestions, like the CoC from the Rust community.15:49
alcabrera#link http://www.ashedryden.com/blog/codes-of-conduct-101-faq#coc101examples15:49
alcabreragood examples ^^15:49
* Obulpathi looking into it15:49
alcabreracpallares: and yeah, the Rust one is great, too!15:50
kgriffsalcabrera: Jesse Noller and Alex Gaynor may be good allies here. I think OpenStack can learn from the broader Python community.15:50
alcabrerakgriffs: agreed15:50
kgriffsI was super impressed by the esprit de corps at PyCon Montreal, for example15:50
*** thurloat has left #openstack-meeting-alt15:50
alcabrera#link http://jessenoller.com/blog/2012/12/7/the-code-of-conduct15:50
vkmcs/we also add in the code that people should not have a defensive/we could also add in the code that people shouldn't have a defensive behaviour... having good faith is important too15:50
alcabreravkmc: good point. these conversations can make people uncomfortable. it takes a bit to navigate this space15:51
alcabreraso kgriffs made a great point earlier, that even our current CoC is ignored15:52
*** nati_uen_ has joined #openstack-meeting-alt15:52
alcabrerawe need to understand the need for moderators, and in the interim, I think team-core members should serve as those that would moderate discussions15:52
kgriffssaw this engraved on a wall in Atlanta: We rise in glory as we sink in pride." (Andrew Young).15:53
*** nati_ue__ has joined #openstack-meeting-alt15:53
*** muralia has joined #openstack-meeting-alt15:53
kgriffs</random>15:53
*** alazarev has joined #openstack-meeting-alt15:53
*** adrian_otto has joined #openstack-meeting-alt15:53
*** nati_ue__ has quit IRC15:53
alcabrerawhat do you all think of having core serve as moderators for now?15:54
alcabrera**serving15:54
*** esker has quit IRC15:54
*** datsun180b has joined #openstack-meeting-alt15:54
*** nati_ue__ has joined #openstack-meeting-alt15:54
kgriffsmakes a lot of sense for core reviewers to lead by example, as well as be moderators15:54
*** esker has joined #openstack-meeting-alt15:54
vkmc+1 alcabrera15:55
alcabreracool15:55
*** balajiiyer has quit IRC15:55
vkmccore devs not only know about the code, but they also know the community :)15:55
*** nati_ueno has quit IRC15:55
*** balajiiyer has joined #openstack-meeting-alt15:55
prashanthr_vkmc : ha ha nice point :)15:55
kgriffsmoderators should keep in mind that often people don't realize that the way they are coming across is not constructive. i suppose even the very act of moderating will need to follow the CoC. :D15:56
alcabrerakgriffs: definitely! it's not easy! :)15:56
alcabreraI speak with experience moderating an IRC community on that point15:56
*** nati_uen_ has quit IRC15:57
alcabreraI'll take some next actions on this15:57
cpallaresPerhaps, we should also add review/suggestions etiquette to the CoC, such as if your comment is not constructive or adding to the argument...15:57
alcabreracpallares: good thought!15:58
*** paulmo has joined #openstack-meeting-alt15:58
alcabreraI think there might something like that I once saw in the OS wiki15:58
alcabrerabut yeah15:58
alcabrerathat needs to be closer to the CoC, or at least linked15:58
cpallaresThat would be nice for the mailing list too.15:58
*** devkulkarni has joined #openstack-meeting-alt15:59
alcabreraI'll figure out who handles CoC things for next week15:59
kgriffsok folks, we are short on time15:59
alcabreraand submit feedback15:59
kgriffs#topic open discussion15:59
*** openstack changes topic to "open discussion (Meeting topic: marconi)"15:59
alcabrerathanks all for listening and sharing feedback!15:59
kgriffs#action megan_w to check trademarks for our shortlist of names15:59
*** derekh_ has quit IRC16:00
kgriffs#endmeeting16:00
*** openstack changes topic to "Zuul is offline due to an operational issue; ETA 2200 UTC."16:00
openstackMeeting ended Tue Jun  3 16:00:16 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-06-03-15.02.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-06-03-15.02.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-06-03-15.02.log.html16:00
adrian_otto#startmeeting Solum Team Meeting16:00
openstackMeeting started Tue Jun  3 16:00:27 2014 UTC and is due to finish in 60 minutes.  The chair is adrian_otto. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
*** alcabrera has left #openstack-meeting-alt16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** mpanetta has left #openstack-meeting-alt16:00
*** amotoki has joined #openstack-meeting-alt16:00
*** openstack changes topic to " (Meeting topic: Solum Team Meeting)"16:00
openstackThe meeting name has been set to 'solum_team_meeting'16:00
adrian_ottohttps://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2014-06-03_1600_UTC Our Agenta16:00
*** prashanthr_ has left #openstack-meeting-alt16:00
adrian_otto#topic Roll Call16:00
*** openstack changes topic to "Roll Call (Meeting topic: Solum Team Meeting)"16:00
adrian_ottoAdrian Otto16:00
*** AAzza has left #openstack-meeting-alt16:00
paulmoPaul Montgomery16:00
funzoChris Alfonso16:00
julienveyJulien Vey16:00
tomblanktom blankenship16:00
devkulkarniDevdatta Kulkarni16:01
*** ravips has joined #openstack-meeting-alt16:01
stanniePierre Padrixe16:01
*** mspreitz has left #openstack-meeting-alt16:01
ravipsRavi Sankar16:01
*** cpallares has left #openstack-meeting-alt16:01
muraliamurali allada16:01
datsun180bEd Cranford16:01
*** esker has quit IRC16:02
*** abettadapur has left #openstack-meeting-alt16:02
*** esker has joined #openstack-meeting-alt16:02
datsun180bcz was double-booked and won't make this meeting today16:02
*** julim has quit IRC16:02
adrian_ottowelcome everyone16:02
*** iqbalmohomed has joined #openstack-meeting-alt16:02
adrian_ottothanks datsun180b16:02
iqbalmohomedHello all16:02
adrian_ottoI am happy to have your original nick back!16:03
*** flaper87 is now known as flaper87|afk16:03
adrian_ottohello iqbalmohomed16:03
*** esker has quit IRC16:04
adrian_ottook, let's begin with announcements. Anyone else who has not chimed in may feel free to chat us at any time to be recorded in attendance.16:04
*** jrist-afk is now known as jrist16:04
adrian_otto#topic Announcements16:04
*** openstack changes topic to "Announcements (Meeting topic: Solum Team Meeting)"16:04
adrian_ottook, first of all, we extend our gratitude to Anita Kuno who agreed to serve as our election official16:04
*** rueben has quit IRC16:05
*** thangp has quit IRC16:05
adrian_ottoyou may be pleased that in accordance with our ratified election rules, no further action is required for an election this cycle, as no new candidates for the PTL position were declared.16:05
adrian_ottoI will serve as your PTL for this cycle.16:05
*** rmoe has joined #openstack-meeting-alt16:05
julienveycongrats adrian_otto16:06
adrian_ottoI will re-open candidacy when the Juno cycle comes to a close.16:06
tomblankadrian_otto: congrats and thanks for performing this role for the project!16:06
*** caleb_` has joined #openstack-meeting-alt16:07
adrian_ottothanks everyone for your support. I am very proud of the work we do here, and am humbled to be a part of it.16:07
*** richm has joined #openstack-meeting-alt16:07
adrian_ottonext up, action items.16:07
adrian_otto#topic Review Action Items16:07
*** openstack changes topic to "Review Action Items (Meeting topic: Solum Team Meeting)"16:07
adrian_ottoasalkeld 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.16:07
adrian_ottoI did see an email thread about this.16:07
julienveyyes, http://lists.openstack.org/pipermail/openstack-dev/2014-June/036490.html16:07
julienveyit seems we will have to go with chained trusts in keystone16:08
julienveybut it is not implemented yet16:08
adrian_otto#link http://lists.openstack.org/pipermail/openstack-dev/2014-June/036490.html ML Discussion about Trust Tokens16:08
adrian_ottothanks julienvey for the link16:08
*** caleb_ has quit IRC16:08
adrian_ottook, I think I saw a review in the queue for something about OAuth16:08
julienveyyes, I abandonned that16:08
adrian_ottoI'm pretty sure I down-voted that awaiting an outcome from this discussion.16:09
adrian_ottook, thanks julienvey16:09
julienveyI think steve from the heat is working with the keystone guys to have chained trusts between services16:09
adrian_ottodo we have an expected timeframe for chained trusts? Are we able to contribute that, or is it happening regardless?16:09
julienveyI will ask angus or steve if there is a blueprint or a bug open about that16:10
adrian_ottook, julienvey are you willing to reach out to him a few times this week to see if there is anything we can do to help?16:10
julienveyand if someone is working on that16:10
julienveyadrian_otto: sure16:10
*** bdpayne has joined #openstack-meeting-alt16:10
paulmoI'm pretty interested in these discussions as well.16:10
adrian_ottowould you accept that as an action item? I see this as a high priority matter for us.16:10
julienveyyes16:10
adrian_otto#action julienvey to follow up with Heat contributors about Keystone chained trusted tokens, to offer our support. Include Solum Stackers in discussions.16:11
adrian_ottook, awesome, thanks for that.16:11
adrian_ottonext we have a bunch of topics relating to our top areas of development focus16:12
*** Stanzi has joined #openstack-meeting-alt16:12
*** rbenali has joined #openstack-meeting-alt16:12
adrian_ottoI'd like us to timebox each of these so we have time to at least touch on each.16:12
adrian_ottowe do not need implementation plan perfection today, but at the very least subgroups of us who are interested, or who we know we can include to drive forward progress on each.16:13
adrian_ottohere we go...16:13
adrian_otto#topic Mistral Integration Discussion (target 10 min discussion)16:13
*** openstack changes topic to "Mistral Integration Discussion (target 10 min discussion) (Meeting topic: Solum Team Meeting)"16:13
adrian_ottodevkulkarni: this was from you16:13
adrian_ottowe have three links to share:16:13
devkulkarnithis is progressing along. datsun180b and asalkeld made headways into this16:13
adrian_ottoactually two16:14
adrian_otto#link https://blueprints.launchpad.net/solum/+spec/pipeline Pipeline Blueprint16:14
adrian_otto#link https://bugs.launchpad.net/solum/+bug/1322748 Initial Mistral Feature Task16:14
adrian_ottofeel free to add other references16:14
*** rajdeep has joined #openstack-meeting-alt16:14
devkulkarniasalkeld has series of patches integrating mistral and pipeline resources16:14
devkulkarnidatsun180b will be able to provide more updates16:14
adrian_ottook, what key issues are open that we can offer guidance about?16:14
devkulkarniso one key issue is whether to expose the mistral dsl to app developers16:15
adrian_ottodatsun180b: anything potentially controversial?16:15
datsun180boh the majority of what i accomplished is just getting mistral into our vagrant env16:15
devkulkarnimy impression is mistral dsl is still too level and we should not expose that to the app developers16:15
adrian_ottodevkulkarni: yes, the dsl is a good one to cover.16:15
devkulkarnithoughts?16:15
adrian_ottoif I may summarize that one for the others here today16:16
devkulkarniplease do adrian_otto. that will be helpful16:16
aratim+1 devkulkarni we need a simpler DSL to be exposed to the end user16:16
julienveydevkulkarni: you think solum should act as a dsl on top of mistral's dsl ?16:16
muraliaI think we should not expose the mistral dsl to end users.16:16
paulmoDon't expose Mistral DSL to users directly.  It would make switching out workflows really difficult later unless we accept Mistral DSL as the language for Solum workflow forever.16:16
adrian_ottowe intend to use Mistral as the backend our first implementation of Pipelines16:16
*** dims_ has joined #openstack-meeting-alt16:16
adrian_ottoit has a DSL, but we think it might be best not to expose that directly, in the interest of keeping the user experience very simple16:16
*** yamahata has quit IRC16:16
iqbalmohomedNot exposing the DSL also lets people use a different workflow engine16:17
adrian_ottowe will link through to the mistral resources, so if someone is so inclined as to interact with the mistral service, they can customize those workflows there.16:17
paulmo+1 iqbalmohomed16:17
adrian_ottoiqbalmohomed: exactly.16:17
ravips+1 iqbalmohomed16:17
devkulkarnijulienvey: thoughts?16:17
adrian_ottobut the overall intent here is to make something useful for the general case without complicating the UX16:17
julienveyhaving a dsl over the mistral dsl would require a lot more work on our side16:18
julienveyin the long term, it's good16:18
julienveybut we could start with angus' way of dealing with it16:18
julienveyhaving a workbook url in the pipeline16:18
devkulkarniso I am thinking that the dsl that we come up with is more about describing the pipeline16:19
paulmohttp://workflowpatterns.com/evaluations/standard/index.php might be useful if we want to partially adopt a standard.16:19
devkulkarniit can refer to existing workbooks16:19
devkulkarnithat is huge listing paulmo.16:20
julienveydevkulkarni: good idea16:20
devkulkarnigut reaction is NO :)16:20
julienveysuch as heat templates can reference another heat template16:20
devkulkarniyep16:20
stannieyep I also like it16:20
*** dims_ has quit IRC16:21
devkulkarnido we want to get an agreed on this or think it over a bit and revisit next time again?16:21
adrian_ottoI think there is a way for us to allow for workflows to be tweaked without making a comprehensive DSL16:21
adrian_ottoso to the extent that is practical, I suggest that as our direction, and we can continue to revisit this as we learn more.16:22
adrian_ottosound fair?16:22
muralia+116:22
adrian_ottoand there would be no need to adopt the Mistral DSL until we had such a discussion16:22
devkulkarniagree16:22
adrian_ottook, any more thoughts on this before we advance to the next tpic?16:23
adrian_ottonext...16:23
adrian_otto#topic Custom Language Pack Discussion16:23
*** openstack changes topic to "Custom Language Pack Discussion (Meeting topic: Solum Team Meeting)"16:23
adrian_otto#link https://blueprints.launchpad.net/solum/+spec/auto-select-lang-pack16:23
adrian_otto•#link https://blueprints.launchpad.net/solum/+spec/custom-language-packs Custom Language Pack Blueprint16:23
devkulkarniSo noorul, adrian_otto have been brainstorming about what do we mean by custom lang packs16:23
*** markmcclain has joined #openstack-meeting-alt16:24
devkulkarniin my mind there are three kinds of lang packs — 1) provided by operator 2) lang packs/build packs belonging to other PaaS systems that we can support in Solum 3) lang packs that an app developer wants to create with custom libraries (e.g. chef testing tools)16:24
*** jgallard has quit IRC16:24
julienveydevkulkarni: what's the difference between 1 and 2 ?16:25
devkulkarniI want to hear what you all think about this topic?16:25
adrian_ottoWe have at least two options for how we define the LP itself. 1) The LP is just an image in glance, done. 2) The LP may leverage an existing image, but add a git-repo to use as an external build-pack (approach consistent with Heroku and Cloud Foundry)16:25
julienveywould cedarish fit into 1 or 2 ?16:25
adrian_ottothe two are not mutually exclusive16:25
*** annashe__ has joined #openstack-meeting-alt16:25
devkulkarnioperator may provide some base lang packs which may or may not be compatible with other systems16:25
adrian_ottocedarish would be #2 in my list16:25
paulmoIt seems 2 would go into bucket 1 or 3?16:25
devkulkarniI think cedarish is 216:25
julienveyI think 2 can fit into 116:26
adrian_ottoyes16:26
julienveycedarish is a "multi-language" LP16:26
*** xwizard has joined #openstack-meeting-alt16:27
devkulkarnisure16:27
adrian_ottoso perhaps we start out with the #1 definition type, and then plan to expand that to add git-repo plugin capability to allow Solum users to extend it.16:27
adrian_ottoand operators can decide whether to include the images that contain the hooks for that extensibility16:27
julienveyhooks are a good idea16:27
devkulkarniadrian_otto: your definition of LP is not complete in the sense that #1 will be required no matter what16:27
adrian_ottook, any alternate points of view to consider here?16:27
devkulkarni#1 is what we actually have to do for any LP to be supported via Solum16:28
devkulkarniso that is not really a defining characteristic of a LP imo16:28
*** Stanzi has quit IRC16:28
adrian_ottodevkulkarni: #1 is required. The question is whether to have #2 as well.16:28
*** Stanzi has joined #openstack-meeting-alt16:28
devkulkarniexactly16:28
adrian_ottowe agree 100%.16:28
devkulkarniand the discussion at least to me is what are conceptually options available for #216:29
adrian_ottoso I suppose I cold ahve framed the options as (1), or (1+2)16:29
*** IlyaE has quit IRC16:29
devkulkarnithe proposed git repo hook approach — that would cover app developers specifying their required libs etc.16:29
iqbalmohomedwould that be similar to heroku's buildpacks?16:30
devkulkarniwould that also cover mechanisms in solum to support LPs/build packs from other PaaSes16:30
adrian_ottothe remote repo does a bit more as well, allowing the actual build execution logic to be adjusted.16:30
devkulkarnior that could be a separate discussion16:30
adrian_ottobecause alternate scripts could be provided.16:30
iqbalmohomedthis is via git execution hooks?16:30
*** IlyaE has joined #openstack-meeting-alt16:30
julienveyi think the example for (2) is adding the .net capability to cedarish. Am I right ?16:30
adrian_ottoso I don't hear any argument against using both approaches16:30
adrian_ottojulienvey: yes, that's a perfect example16:31
*** tsufiev has joined #openstack-meeting-alt16:31
adrian_ottoI'd like to be able to allow a user to add that without a code patch to solum :-)16:31
tomblankadrian_otto: +1 on using both approaches16:31
julienveyyes, and hooks (in solum) to add capabalities would be an elegant way of dealing with it, imo16:32
devkulkarniok, hold on, lets reiterate what the two approaches are.16:32
devkulkarniI see only only approach — git hooks16:32
devkulkarniwhat is the other approach?16:32
*** sreshetnyak has quit IRC16:33
iqbalmohomedimages in glance?16:33
devkulkarnisaving LP in glance is not an approach16:33
*** sreshetnyak has joined #openstack-meeting-alt16:33
devkulkarnithat is required no matter what16:33
julienveydevkulkarni: I don't understand what you mean by git hooks16:33
devkulkarniwe are talking about customizing language packs16:33
devkulkarniwe need approaches to do that .. the end result will go in glance no matter what16:33
julienveysure16:34
adrian_ottothe extensibility point will be a way to indicate that a build should consult the content in an external git repo that contains a build pack (compatible with Heroku and CF)16:34
devkulkarnione approach that is coming up, as suggested by adrian_otto, is to use custom repo with git hooks (paraphrasing — could be wrong)16:34
adrian_ottothat could be a parameter, or metadata, etc.16:34
adrian_ottoit's not exactly a hook16:34
devkulkarnithanks for clarification adrian_otto16:35
adrian_ottojust an external reference of where to get plugin code to adapt the build processing16:35
adrian_ottook, I think that was the confusion point16:35
rajdeepi was thinking since CF and Heroku build packs are already there with an ecosystem16:35
rajdeepwouldn't it make sense to base our definition on those16:35
*** tonytan4ever has quit IRC16:35
rajdeeprather than trying to build a new one16:35
devkulkarnirajdeep: but they are not same, or are they?16:36
adrian_ottoI think it's time to record this in a task ticket, possibly linked to a wiki that can exhibit a simple block diagram to express the concept.16:36
rajdeepthey are mostly16:36
rajdeepCf is based on heroku build packs16:36
devkulkarniwhat about OpenShift cartridges?16:36
adrian_ottowe also have a task that would allow compatibility with Openshift Catridges too16:36
adrian_ottothat's already on the wishlist16:37
rajdeepinfact CF team introduced them later as it was the best way to introduce a new platform16:37
adrian_ottobut let's walk before we run.16:37
aratimhow will this approach help the user to create his own language pack?16:37
devkulkarniso that is other other category (#3) that I had in mind16:38
adrian_ottoaratim: as an end user I can post my custom build scripts in a git repo, and pick an LP entry that uses an image that will take my repo as a parameter/metadata and download it (as needed) and use it to run the build16:38
devkulkarniwhich I think will be addressed by the custom repo approach16:38
devkulkarnisuggested by adrian_otto16:38
devkulkarniyeah, that should work16:39
adrian_ottook, let's wrap up on this one and move to the next16:39
aratimadrian_otto: yeah makes sense16:39
adrian_ottodevkulkarni: are you willing to take an action item to work with me on this to clearly document the approach and how it addresses each use case?16:39
devkulkarnisure adrian_otto16:39
devkulkarnilets do it16:39
*** bdpayne has quit IRC16:39
adrian_otto#action devkulkarni to work with adrian_otto to document the LP devleopment approach in BP+task+wiki to clearly outline our approach, and how it solves each use case.16:40
adrian_ottoand we will take input from anyone who is willing to review this, and add remarks16:40
adrian_ottonext, we have...16:40
adrian_otto#topic Source to Image Pipeline Discussion16:40
*** openstack changes topic to "Source to Image Pipeline Discussion (Meeting topic: Solum Team Meeting)"16:40
devkulkarnimuralia has the latest on the pipeline -> plan discussion16:41
adrian_ottoWe touched on this last week, but did not have time to explore nova-docker enhancements16:41
muraliathere is a google doc with some approaches. I'm going ot move these comments to the blueprint.16:41
*** Slower has joined #openstack-meeting-alt16:41
muraliahttps://docs.google.com/document/d/1a0yjxKWbwnY7g9NZtYALEZdm1g8Uf4fixDZLAgRBZCU/edit?pli=1#16:41
adrian_ottomuralia: I have the Solum Spec repo further down in the agenda16:42
muraliaok.16:42
*** annashe__ has quit IRC16:42
devkulkarniokay, so about nova docker improvements..16:42
adrian_ottoonce we open that, let's put the GoogleDoc content into RST and post it there for review.16:42
devkulkarniwe touched upon it last time.16:42
*** annashe__ has joined #openstack-meeting-alt16:43
devkulkarnithe questions that I had (which we touched upon last time), was what are the exact things needed from us for that16:43
adrian_ottothat=nova-docker?16:44
devkulkarniyes16:44
adrian_ottoglance integration16:44
devkulkarninova docker driver improvements16:44
adrian_ottoneeds a multi-tenant solution16:44
*** rueben has joined #openstack-meeting-alt16:45
adrian_ottoso rather than interfacing through docker to docker-registry to glance, we can just integrate directly with glance16:45
*** julim has joined #openstack-meeting-alt16:45
*** harlowja_away is now known as harlowja16:45
adrian_ottoand that approach works as a first iteration workaround16:45
*** yogeshmehra has joined #openstack-meeting-alt16:45
devkulkarniyeah, that should be helpful16:45
adrian_ottothen we can explore the future of docker-registry with the #nova-docker team16:45
*** ramishra has joined #openstack-meeting-alt16:46
*** nati_ue__ has quit IRC16:46
adrian_ottowe did discuss that subject in Atlanta, and it appears to have non-technical aspects to motivating the stakeholders16:46
adrian_ottothis is something that the #openstack-containers team can deal with.16:46
devkulkarnicool.. I guess my questions were more from the Juno-1 feature list (this is listed in Juno-1)16:47
*** annashe__ has quit IRC16:47
devkulkarnido you think nova docker driver improvements should be in Juno-1 or could they be moved out?16:47
adrian_ottoyes, bypassing nova-docker's use of docker-registry will suit our near term needs16:47
adrian_ottoand fixing docker-registry can be deferred as needed.16:48
adrian_ottoAnyone disagree?16:48
tomblankshould we collect our requirements in a single place/document, prioritze them, identify any must have features for Solum juno release, etc?16:48
devkulkarniI guess we need time to think :)16:48
adrian_ottook, let's advance to our last couple of topics. These should be short.16:48
adrian_otto#topic Review Tasks16:49
*** openstack changes topic to "Review Tasks (Meeting topic: Solum Team Meeting)"16:49
julienveyI don't see why this is in our roadmap, it's a dependency we have on nov-docker, like we have on heat or mistral16:49
adrian_ottoI am doing some housekeeping on this:16:49
adrian_otto#link https://launchpad.net/solum/+milestone/2014.1.216:49
adrian_ottoI plan to tag this release today or tomorrow16:49
*** redrobot has left #openstack-meeting-alt16:49
devkulkarnijulienvey: same thoughts here16:49
adrian_ottoI am moving everything that's not fix released to juno16:49
*** stan_lagun has joined #openstack-meeting-alt16:50
adrian_ottoand pulling everything in juno that is fix-released into 2014.1.216:50
*** gokrokve has joined #openstack-meeting-alt16:50
adrian_ottoso expect to see that shuffling in our tasks and BPs16:50
adrian_ottoany concerns with this?16:50
adrian_ottoI'd like to also lock down our demo to using the tagged release16:51
adrian_ottoso it's not a moving target16:51
devkulkarni+1 to locking down demo to a tagged release16:51
paulmoYeah, +1 to that as well16:51
adrian_ottoI can tag releases as often as we need to in order to make changes to the demo setup16:51
adrian_otto#agreed we will adjust our demo environment to use the upcoming 2014.1.2 release, and update to newer releases as needed.16:52
adrian_ottook, last agenda item16:52
adrian_otto(next to last)16:52
adrian_otto#topic Solum Spec Repo16:52
*** openstack changes topic to "Solum Spec Repo (Meeting topic: Solum Team Meeting)"16:52
*** demorris has quit IRC16:52
adrian_ottoI am planning to start a new code repository that will hold RST files of our specifications. The porpose of this is to allow for review of our design plans in the same way we do code reviews16:53
adrian_ottothe same reviewers will be attached to this repo16:53
devkulkarniI think this will be helpful.. at least instead of googledocs16:53
adrian_ottomuralia will place our design work there, and we can more easily source input and have debate on items where we disagree16:53
ravipsthat will be very useful16:53
*** sriram has left #openstack-meeting-alt16:54
muralia+116:54
adrian_ottook, so I will give you a heads up on the ML once that merges16:54
paulmo+1 to this idea; btw, http://rst.ninjs.org/ might be useful for editors and such16:54
tomblankis there a way to timebox the review period?16:54
adrian_ottowe can try that out, and switch to something else later if we don't find it useful16:54
devkulkarniis there a need to timebox review period?16:54
adrian_ottothe Keystone team has used this approach successfully16:54
adrian_ottodevkulkarni: we can do that as needed16:55
adrian_ottothat's something we can certainly negotiate on an ML thread per design16:55
tomblankdevkulkarni: sometimes, I think it would be useful.16:55
tomblankadrian_otto:  +116:55
adrian_ottoI agree that having a deadline on something can help us focus on key issues16:55
julienveywill we have to post all our design there or only high-level features ?16:55
adrian_ottonot every design needs a deadline16:55
adrian_ottobut ones that are critical to our Juno milestones should16:55
*** s3wong has joined #openstack-meeting-alt16:56
adrian_ottojulienvey: we can use our discretion16:56
tomblankadrian_otto:  again, agree...16:56
adrian_ottolet's use it to see if it helps16:56
paulmoI also like the timebox idea in that we can define a minimum review time to give folks in various time zones a fair chance.  2 days minimum I would think.16:56
tomblankand we can adjust as needed..16:56
devkulkarnibtw, kgriffs warned about the design process getting heavy handed .. take a look at this email on marconi16:56
devkulkarni*his16:57
adrian_ottothanks devkulkarni. We can take that as an opportunity to learn from our peers.16:57
julienveydevkulkarni: do you have a link ?16:57
tomblankpaulmo: +116:58
adrian_ottoI will also offer myself as a release valve if any of our contributors are not comfortable with any design proceedings, please see me about it so I can work to address those concerns for you.16:58
devkulkarniwill send it to you julienvey (don't have it handy)16:58
devkulkarniit was sent couple of days back16:58
adrian_otto#topic Open Discussion16:58
*** openstack changes topic to "Open Discussion (Meeting topic: Solum Team Meeting)"16:58
adrian_otto2 mins remaining.16:58
*** rbenali has quit IRC16:58
*** bdpayne has joined #openstack-meeting-alt16:59
*** satish has quit IRC16:59
*** NehaV has quit IRC16:59
rajdeephave we done customer validation of features being built for solum16:59
*** arnaud has joined #openstack-meeting-alt16:59
adrian_ottothanks everyone for attending today. Next week we should have a shorter agenda, so not quite as rushed.16:59
*** markwash has joined #openstack-meeting-alt16:59
*** amcrn has joined #openstack-meeting-alt17:00
adrian_ottorajdeep: we would love more!17:00
adrian_otto#endmeeting17:00
*** openstack changes topic to "Zuul is offline due to an operational issue; ETA 2200 UTC."17:00
openstackMeeting ended Tue Jun  3 17:00:13 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/solum_team_meeting/2014/solum_team_meeting.2014-06-03-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/solum_team_meeting/2014/solum_team_meeting.2014-06-03-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/solum_team_meeting/2014/solum_team_meeting.2014-06-03-16.00.log.html17:00
*** devkulkarni has left #openstack-meeting-alt17:00
*** tomblank has left #openstack-meeting-alt17:00
*** thinrichs has joined #openstack-meeting-alt17:00
*** ankurrr has joined #openstack-meeting-alt17:00
*** paulmo has left #openstack-meeting-alt17:00
rajdeepit might be useful ..17:00
*** rajdeep has quit IRC17:00
adrian_ottowe can continue in #solum on that topic17:00
*** esker has joined #openstack-meeting-alt17:00
*** datsun180b has left #openstack-meeting-alt17:00
*** julienvey has quit IRC17:01
*** ativelkov has joined #openstack-meeting-alt17:01
xwizardhi there!17:02
*** iqbalmohomed has quit IRC17:02
katyaferventHi17:02
ativelkovhi17:02
tsufievo|17:02
ativelkovMurano time?17:02
stan_laguno/17:02
xwizardso, should we start a neeting?17:02
*** akuznetsova_ has joined #openstack-meeting-alt17:02
xwizardyes17:02
ativelkovyup17:02
*** sarob has joined #openstack-meeting-alt17:02
xwizardok17:02
ruheoo17:03
ruhe#startmeeting murano17:03
openstackMeeting started Tue Jun  3 17:03:02 2014 UTC and is due to finish in 60 minutes.  The chair is ruhe. Information about MeetBot at http://wiki.debian.org/MeetBot.17:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:03
*** openstack changes topic to " (Meeting topic: murano)"17:03
openstackThe meeting name has been set to 'murano'17:03
ruhe#link https://wiki.openstack.org/wiki/Meetings/MuranoAgenda#Agenda17:03
ruheroll call: done :)17:03
*** xwizard is now known as tnurlygayanov__17:03
*** thangp has joined #openstack-meeting-alt17:03
ruheone moment, need to invite more peopel17:04
*** sjmc7 has joined #openstack-meeting-alt17:04
ruhe#topic action items review17:04
*** openstack changes topic to "action items review (Meeting topic: murano)"17:04
ruhe1. btully to create blueprints extracted from generic17:04
*** btully has joined #openstack-meeting-alt17:05
dteselkinHi17:05
ruhe#info btully created blueprints extracted from generic https://blueprints.launchpad.net/murano/+spec/murano-ui-horizon-patterns17:05
ruhethose BPs are scheduled for juno-117:05
ruhe2. ruhe create blueprint for external repositories17:05
ruhe#info ruhe created BP for online repo: https://blueprints.launchpad.net/murano/+spec/online-app-repository design is still drafting17:06
*** tonytan4ever has joined #openstack-meeting-alt17:06
ruhealso, there was an AI on me - mark murano-dsvm job as voting17:06
ruhehere is a patch to infra https://review.openstack.org/#/c/97462/17:06
ruheonce it is merged we will not be able to merge changes in Murano which breake murano-dsvm job in Jenkins. which is good17:06
ruhei don't see any other action items from previous meetings17:07
ruhe#topic juno-1 status review17:08
*** openstack changes topic to "juno-1 status review (Meeting topic: murano)"17:08
ruhe#link https://launchpad.net/murano/+milestone/juno-117:08
ruheoverall we're doing good17:08
*** baoli has quit IRC17:08
ruhei'm a bit concerned about a bunch of UI blueprints in "Unknown" state. btully: do you have any update on those?17:08
btullywhich ones? i'm not clear on "state" is that something that gets set on the blueprint?17:10
tsufievbtully, he means 'Delivery' status17:10
ruhebtully: ah. i should've tell you about that :)17:10
*** tonytan4ever has quit IRC17:11
ruhebtully: when you look at the list of blueprints at https://launchpad.net/murano/+milestone/juno-1 there is "Delivery" column17:11
*** baoli has joined #openstack-meeting-alt17:11
ruhebtully: common practice is to set the "delivery" field in "Started" once you started working on a blueprint17:11
ruheeven if there are no patches on review17:11
btullyok, how do i do that?17:11
btullyi don't see a "delivery" field17:12
ruhebtully: just open the blueprint and update field "Implementation" to "Started"17:12
btullyahh ok17:12
ruhethat's launchpad, it's messy :)17:12
btullythanks17:12
ruheanything else to discuss on the current topic?17:13
*** satish has joined #openstack-meeting-alt17:13
tsufievbtully, also gerrit updates status automatically, if you write the appropriate line in commit message and send it to review17:13
tsufievline is 'Implements: blueprint name-of-blueprint'17:13
ativelkov"Targets blueprint: name-of-blueprint" is better17:14
*** kgriffs is now known as kgriffs|afk17:15
ativelkovIf the checking does not address the BP completely17:15
*** adrian_otto has left #openstack-meeting-alt17:15
ativelkovcheck-in*17:15
btullythanks, good to know17:15
*** ramishra has quit IRC17:15
*** Obulpathi has quit IRC17:15
tsufievanyways, you can read those tips at https://wiki.openstack.org/wiki/Gerrit_Workflow17:15
*** arnaud has quit IRC17:15
ruhe#topic ID and GUID usage discussion17:16
*** openstack changes topic to "ID and GUID usage discussion (Meeting topic: murano)"17:16
ruhekatyafervent: that's your topic. please go ahead17:16
btullyso for those items I haven't looked at yet, do i leave them as Unknown or do i need to change them to "Not Started"17:16
katyaferventhere is the etherpad https://etherpad.openstack.org/p/murano-quid-discussion17:16
*** Slower has quit IRC17:16
ruhebtully: either is ok. i'd suggest "Not Started"17:16
*** Slower has joined #openstack-meeting-alt17:17
*** Obulpathi has joined #openstack-meeting-alt17:17
*** dims_ has joined #openstack-meeting-alt17:17
btullyk17:17
katyaferventthis topic brought from bug scrub and here is a bug https://bugs.launchpad.net/murano/+bug/131967717:17
sjmc7i don't think database performance is much of a consideration with UUIDs - being similar to other openstack services has some advantages though17:17
*** markwash has quit IRC17:17
katyaferventwhat do you think, should we make our ids in guid format?17:18
tsufievsjmc7, there was one issue related directly to uuid length - so that question arised17:18
sjmc7i think if we're going to use uuids, we should format them as guids17:18
ativelkovwhat was the reason behind our own id generator?17:18
ativelkovstan_lagun: sergmelikyan: do you rmemeber?17:18
sjmc7there are openstack utility functions for handling them (heat tests if a stack id is a guid or a stack name, for instance)17:19
stan_lagunwhy should we care? IDs are not GUIDs. They are just unique strings. Therir format should not be constraint in any way17:19
*** markwash has joined #openstack-meeting-alt17:19
sjmc7they'rein URLs17:19
sjmc7they must be constrained in some ways17:19
katyaferventsorry this is a valid link https://bugs.launchpad.net/murano/+bug/129200917:19
gokrokveThere was a discussion in Solum and TripleO about using UUIDs as a primary key17:20
*** emagana has joined #openstack-meeting-alt17:20
gokrokvete reason to use int ID was the performance17:20
*** Obulpathi has quit IRC17:20
ruhestan_lagun: imho consistency across openstack projects is a constraint. thus i'd prefer to go with UUID, unless there is a strong argument not to use them17:20
sjmc7did anyone measure the performance impact? i would wager than UUID lookups are not the bottleneck for most services17:21
*** Obulpathi has joined #openstack-meeting-alt17:21
*** markmcclain has quit IRC17:21
tnurlygayanov__sjmc7, for uids?17:21
gokrokveClint from TripleO had some reasons to propose integer IDs.17:21
stan_lagunI don't suggest not to use UUIDs. I'm just saying that exact format (with or without dashes) is not important. Another implementation can generate random string or sequence numbers converted to string and that should be fine17:21
gokrokveIndexing performance was among these reasons17:22
sergmelikyanI think what to use as pkey  in the database - is does not matter. But ID for entities should not be bound to UUID17:22
stan_lagunWe should not REQUIRE dashes or any particular ID format17:22
tnurlygayanov__I think the uids will not affect perofrmance itself17:22
sjmc7are names unique?17:22
stan_lagunwhat names?17:22
sjmc7do all entities have unique names?17:23
stan_lagunno17:23
stan_lagunjust unique ID17:23
sergmelikyanI am against using UUID as ID for Object Model entities17:23
tsufievsergmelikyan, why?17:23
ruhesergmelikyan: stan_lagun: what are the arguments not to use UUID?17:23
*** tonytan4ever has joined #openstack-meeting-alt17:24
stan_lagunID can be any string if that string is relatively short and unique within that object model17:24
*** dprince has quit IRC17:24
*** shakamunyi has quit IRC17:24
sergmelikyantsufiev, because object model may be written manually? Because shorten IDs may be much easily consumed in demos?17:24
stan_lagunruhe, again, I'm not saying not to use UUID. You can use anything that is unique including UUID. We shouldn't care17:24
ativelkovFor readability we can define some human-readable IDs17:25
*** arnaud has joined #openstack-meeting-alt17:25
tsufievsergmelikyan, nobody forces us to use genuine UUIDs in demos :)17:25
ativelkovit's up to the API users to generate them17:25
stan_lagunfor example for tests it is better to use ids like 'postgreSql1' instead of GUID17:25
sergmelikyanyep, so why constrain them with UUID?17:25
tsufievsimple IDs are fine as long as you can guarantee that they are limited to the scope of one Application17:26
sjmc7the API is generating IDs, right?17:26
sjmc7not users17:26
stan_lagunwe do use UUIDs. But there is no need to enforce it or require some particular formatting17:27
sergmelikyansjmc7, no, IDs are generated by users17:27
stan_lagunIDs are generated by dashboard :)17:27
stan_lagunnot by end user17:27
tsufievstan_lagun, and it uses dashless UUIDs17:27
stan_lagunmaybe someday API will generate them17:27
*** baoli has quit IRC17:27
*** tdruiva has quit IRC17:28
*** tdruiva has joined #openstack-meeting-alt17:28
*** aratim has quit IRC17:28
stan_laguntsufiev And if you make it just random string everything will still work17:29
sjmc7the reasons i see for using GUIDs is that it's easy to identify them in logs, URLs etc. other than that, i don't really care, but i think that since they're going to be generated by the dashboard or muranoclient they will have some predfined format17:29
ruhei haven't seen any argument not to use UUID as id in Murano. i suggest we proceed and let katyafervent to do what she planned to do17:29
tsufievsjmc7, yes, kind of a convention17:29
*** baoli has joined #openstack-meeting-alt17:30
ruhelet's move on. this discussion doesn't move to something constructive17:31
sergmelikyanruhe +117:31
ruheeveryone please state your thoughts in that document https://etherpad.openstack.org/p/murano-quid-discussion17:31
ruhe#topic Open Discussion17:32
*** openstack changes topic to "Open Discussion (Meeting topic: murano)"17:32
*** muralia has quit IRC17:32
ruhei can give an update on alembic migrations. patch is finished basically, but for some reason it works everywhere except the gate17:33
ruheso, i'm blocked on https://review.openstack.org/#/c/97251/ which would let me to debug the problem17:33
ruhei'll continue with setting up unit-testing infrastructure for DB layer17:34
tsufievruhe, it seems it's not the only problem with the gate (at least today) :)17:34
ruhetsufiev: yeah. another important topic for us is the state of murano-ci17:34
ruhetnurlygayanov__: can you give an update on murano-ci?17:35
*** NehaV has joined #openstack-meeting-alt17:35
tnurlygayanov__yes17:35
tsufievruhe, actually i meant Jenkins zuul, but you're also right :)17:35
tnurlygayanov__so, right now we have some problems and we work on it17:35
ruhetnurlygayanov__: any estimates? when will it become stable?17:36
*** annashe__ has joined #openstack-meeting-alt17:36
tnurlygayanov__I see now some new commits for dashboard tests with fixes17:36
*** nati_ueno has joined #openstack-meeting-alt17:36
tnurlygayanov__yes, 1-2 days and murano-ci will works for all commits17:37
ruhetnurlygayanov__: so, the idea is - we ask developers to update selenium tests whenever their patch breaks the tests?17:37
tnurlygayanov__today we fix big problem with RabbitMQ connectivity and started to create CI job for tests with deployment in new CI17:37
*** jeckersb is now known as jeckersb_gone17:37
*** jeckersb_gone is now known as jeckersb17:38
tnurlygayanov__ruhe, yes, and QA team will help to update tests17:38
tnurlygayanov__in the same patch set17:38
ruhetnurlygayanov__: ok. thank you17:38
*** sarob has quit IRC17:38
tnurlygayanov__because it is only one way to save our CI tests green17:38
*** ravips has left #openstack-meeting-alt17:39
*** eghobo has quit IRC17:39
*** SumitNaiksatam has joined #openstack-meeting-alt17:40
sjmc7i have something for open discussion if we're done with CI17:40
ruhesjmc7: yes, please go ahead17:40
sjmc7regarding testing also - i'd like some base classes to make it easier to run unit tests on the API17:41
sjmc7i can do them unless someone else is desperate to17:41
sjmc7currently we don't really have any test functions for the API other than the integration tests17:41
sjmc7just stuff like faking context, setting up an inmemory database17:42
sjmc7if anyone has thoughts or input i'll maybe create a blueprint or etherpad or something17:43
sjmc7i can tell by the stunned silence everyone is very keen17:43
*** markwash_ has joined #openstack-meeting-alt17:44
ruhesjmc7: i support this idea. the only thing i'd like to discuss is DB mocking vs using in-memory sqlite for API tests17:44
tsufievsjmc7, we're not yet recovered from uuid vs. guid quarrel :)17:44
sjmc7yeah - i'm not sure about that either. ha, tsufiev :)17:44
sjmc7i sort of prefer an in-memory because it means it's testing it more like it will actually be run; otherwise changes to the DB often do not get mirrored in mocks17:45
*** kgriffs|afk is now known as kgriffs17:45
tsufievsjmc7, unit tests for api are good, though i don't know how long current api will remain the same17:45
sjmc7but i'm ok with either way17:45
sjmc7ah :)17:45
ruhesjmc7: my experience from other projects shows that mocking DB usually ends up with tests which tests mocks. i'd like to hear what other folks think about that17:45
*** demorris has joined #openstack-meeting-alt17:45
*** safchain has quit IRC17:46
sjmc7yeah, that's my experience, ruhe - which is why i think i prefer using an in-memory sqllite db with migrations applied17:46
tsufievafaik, sergmelikyan is currently investigating the possibilities of rewriting api17:46
sjmc7ah. to what end?17:46
sergmelikyansjmc7, +1 for in-memory database17:46
sjmc7i think that's even more reason to be able to write good unit tests17:46
sergmelikyantsufiev, it is not quite right statement :)17:46
sjmc7if the API is changing sgnificantly17:46
ruhetsufiev: rewriting API is not just something you can do in a month or two. it'll take a lot of time17:46
*** markwash has quit IRC17:46
*** markwash_ is now known as markwash17:46
sergmelikyansjmc7, definitely17:47
ruheso, unit-tests are needed very much (this sounds like ruglish)17:47
sjmc7:D17:47
sjmc7your ruglish is way better than my engsian17:47
ruhe:)17:48
sjmc7ok. i'll take a look at what other projects have done. i think glance and heat both use an in-memory DB and create fake contexts17:48
ruhesjmc7: thank you for starting this17:48
sjmc7thank me when i've actually started it :)17:48
tsufievsjmc7,  btw, api is not the only component that cries for unit tests17:49
*** tjanczuk has joined #openstack-meeting-alt17:49
*** otherwiseguy has quit IRC17:49
tsufievdashboard does it even more17:49
ruheyes, i think we need to get back to muranopl tests17:50
ruhetsufiev: is dashboard code unit-test-coverable?17:50
*** kevinbenton_ has joined #openstack-meeting-alt17:50
sjmc7django has a test framework17:51
*** emaganap has joined #openstack-meeting-alt17:51
tsufievruhe, to some extent. that's s complicated question - not only server part needs to be tested, but also client code17:51
sjmc7but since horizon mostly makes calls to outside services i'm not sure how much there is to test17:51
ruhemaybe selenium tests would be enough?17:52
ruhe* existing selenium tests17:52
tsufievruhe, maybe, once they start working :)17:52
tsufievthe problem with selenium tests is that can't keep the pace with changes in code17:53
*** rueben has quit IRC17:53
tsufievideally, one person should write the code and tests for it - which is not true for selenium tests in murano17:53
*** emagana has quit IRC17:53
ruhetsufiev: would you personally be willing to write/update selenium tests whenever you change dashboard code?17:54
sjmc7:)17:54
*** balajiiyer has quit IRC17:54
tsufievruhe, first I will need at least 2 weeks to dig into this and study all the existing good practices17:54
*** kgriffs is now known as kgriffs|afk17:55
tsufievok, maybe a bit less...17:55
ruhethat's my concern with these tests. we only have two options - 1. enforce developers to maintain these tests in their patches to dashboard 2. turn off these tests on commits and run them on a regular (nightly?) basis17:56
sjmc7how does horizon do it?17:56
tsufievruhe, i mean, at this moment i don't know enough about them and cannot give a conscious answer :)17:56
tsufievsjmc7, horizon consists of 2 parts - horizon and openstack_dashboard17:57
ruhesjmc7: horizon has a very-very basic tests. afaik they only test that login panel is available17:57
tsufievafaik, there unit tests for horizon17:57
sjmc7but they do it with the django test framework?17:57
*** jprovazn has joined #openstack-meeting-alt17:58
tsufievhttps://github.com/openstack/horizon/tree/master/horizon/test/tests17:58
tsufievi wouldn't say there is only one test, but still not many17:59
*** aveiga has joined #openstack-meeting-alt17:59
tsufievso, muranodashboard can follow this way - unittest library part, use webtest for dashboard business logic17:59
ruhewe're running out of the time. tsufiev: it would be great if you and tnurlygayanov__ research existing approaches with dashboard testing and conduct some kind of a report and possible solutions/directions for us17:59
*** balajiiyer has joined #openstack-meeting-alt18:00
tsufievruhe, ok18:00
ruhethanks everyone18:00
sjmc7thanks ruhe18:00
tsufievthank you18:00
*** sjmc7 has left #openstack-meeting-alt18:00
ruhe#endmeeting18:00
*** openstack changes topic to "Zuul is offline due to an operational issue; ETA 2200 UTC."18:00
openstackMeeting ended Tue Jun  3 18:00:37 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/murano/2014/murano.2014-06-03-17.03.html18:00
*** ankurrr has left #openstack-meeting-alt18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/murano/2014/murano.2014-06-03-17.03.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/murano/2014/murano.2014-06-03-17.03.log.html18:00
s3wonginteresting channel topic...18:01
*** emaganap has quit IRC18:01
sc68calwho's here for the Neutron QoS API subteam?18:01
nati_uenohi!18:01
s3wongsc68cal: here18:01
aveigao/18:01
*** stan_lagun has left #openstack-meeting-alt18:01
*** tsufiev has left #openstack-meeting-alt18:02
sc68cal#startmeeting neutron_qos18:02
openstackMeeting started Tue Jun  3 18:02:15 2014 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
*** openstack changes topic to " (Meeting topic: neutron_qos)"18:02
openstackThe meeting name has been set to 'neutron_qos'18:02
*** aratim has joined #openstack-meeting-alt18:02
*** nati_ueno has quit IRC18:02
sc68calI haven't started building agendas for the meeting just yet, I also need to make a wiki page for us18:02
*** nati_uen_ has joined #openstack-meeting-alt18:02
sc68calso for now we'll keep it pretty free form until we settle into a rhythm18:03
*** emagana has joined #openstack-meeting-alt18:03
sc68calI know nati_uen_ has some stuff to share18:03
nati_uen_yes18:03
nati_uen_Can I share it now?18:03
nati_uen_or do you guys have another topics?18:03
*** caleb_` has quit IRC18:04
*** thinrichs has quit IRC18:04
sc68calanyone have any other topics they want to share?18:04
*** rueben has joined #openstack-meeting-alt18:05
*** julim has quit IRC18:05
nati_uen_ok, so let me share mine18:05
nati_uen_I'm working on Action support for security group18:05
nati_uen_BP --> https://review.openstack.org/#/c/93112/18:05
nati_uen_My idea is specify qos apply rule in security group as an action18:05
nati_uen_so In current QoS BP, we can apply qos resource for port and network18:06
nati_uen_In addition to this, I would like to apply qos for security groups18:06
*** dtx00ff has joined #openstack-meeting-alt18:06
*** flaper87|afk is now known as flaper8718:06
nati_uen_because it is same in most of application deployment18:06
nati_uen_For example, web3tier app18:06
*** btully has left #openstack-meeting-alt18:07
nati_uen_We will have, web security group, app security group and db security group18:07
nati_uen_They will have different security filtering policy.18:07
*** julim has joined #openstack-meeting-alt18:07
nati_uen_I believe QoS configuration overwraps this grouping18:07
aveiganati_uen_: are you proposing a method to add QoS to Egress rules? For instance, being able to do EF and AF to RTP and SIP, respectively?18:07
*** SushillKM has joined #openstack-meeting-alt18:07
nati_uen_aveiga: yes. we can specify it engress or igress18:08
aveiga:)18:08
nati_uen_i'm not sure all driver may support it..18:08
sc68calSo - we could use the existing match criteria the sec group exposes (like port ranges)18:08
sc68calthen just use the QoS api to store the mark that it would apply?18:09
nati_uen_yes18:09
sc68calcool - less work for me :)18:09
nati_uen_What I'm thinking is to use qos resources18:09
sc68calinstead of making drivers that do port ranges18:09
nati_uen_ya hopefully :)18:09
nati_uen_We can also reuse existing security group rpc internally18:09
nati_uen_https://github.com/openstack/neutron/blob/master/neutron/db/securitygroups_rpc_base.py#L35318:10
sc68calyeah, cut down on some of the RPC methods the qos api extension required18:10
nati_uen_We can mix def from QoS policy in the code here18:10
*** luizfar has quit IRC18:10
nati_uen_yes18:10
kevinbenton_so a security group rule would just reference a policy as an action, right?18:11
nati_uen_yes18:11
*** luizfar has joined #openstack-meeting-alt18:11
nati_uen_L214 https://review.openstack.org/#/c/93112/14/specs/juno/security_group_action.rst <--18:11
sc68calso another thing I wanted to make sure was still ok, was doing QoS policies per port and network, since that affects other implementations, like kevinbenton_18:12
*** SushillKM has left #openstack-meeting-alt18:12
nati_uen_yes. IMO, we may have two way18:12
sc68calperfect. :)18:12
kevinbenton_sounds good18:12
nati_uen_OK Thanks. Let's collaborate on this18:12
kevinbenton_so actually if the reference is from the security group side, what do you need on the qos db side?18:13
sc68calI think the security group action would reference the qos_id18:13
nati_uen_if you like spec, let me do some poc work18:13
nati_uen_I don't think it will impact qos design18:13
nati_uen_on API18:14
nati_uen_rcp part may be simplifed18:14
nati_uen_I tried to make it working till this meeting, but it looks like need some more time18:14
*** muralia has joined #openstack-meeting-alt18:14
sc68calno worries18:14
nati_uen_hopefully, I could share the poc in next meeting18:15
sc68calcool18:16
nati_uen_ok that is all from me18:16
*** alazarev has quit IRC18:16
sc68calI have some work to do on the DB side for the qos API, so I'll be updating my review in time for next meeting too18:16
nati_uen_OK18:16
kevinbenton_nati_uen_ that sounds good18:16
nati_uen_kevinbenton_: Thanks18:16
nati_uen_it is great if we could remove WIP in qos bp18:17
sc68calmost likely it'll still be WIP, but I'll try and address some reviewer comments and other things18:17
s3wongsc68cal: would you mind posting a link to your review (so far)?18:17
sc68cals3wong: https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/ml2-qos,n,z18:17
nati_uen_https://review.openstack.org/#/c/88599/18:17
s3wongsc68cal: thanks18:17
sc68calboy are gerrit reviews ugly.18:17
sc68calI'll also update the spec from the comments people posted. Which by the way, thanks!!18:18
*** muralia has left #openstack-meeting-alt18:18
kevinbenton_trailing whitespaces!18:18
sc68caland /qoses.json :)18:18
nati_uen_he he18:19
*** denis_makogon_ has joined #openstack-meeting-alt18:19
sc68calI am really convinced that the neutron-spec is a Good Thing18:19
nati_uen_ya18:19
sc68calbecause the QOS api extension stuff was just all. over. the. place.18:19
*** Stanzi has quit IRC18:19
sc68calmailing list, launchpad, commit messages.....18:19
*** Stanzi has joined #openstack-meeting-alt18:19
kevinbenton_®18:19
* nati_uen_ wondering how kevin input the magic word18:20
kevinbenton_had to google it, that’s why i was too slow to get it right after Good Thing®18:20
nati_uen_"Good Thing®" ha ha ha18:20
sc68calGood Thing™18:20
nati_uen_18:20
*** zzelle_ has joined #openstack-meeting-alt18:21
nati_uen_so all topic is covered?18:21
sc68calI think so - I'll just switch to open discussion since I don't have a real agenda yet :)18:21
sc68cal#topic open discussion18:21
*** openstack changes topic to "open discussion (Meeting topic: neutron_qos)"18:21
*** Sukhdev has joined #openstack-meeting-alt18:22
nati_uen_so ref impl is ovs based, right?18:22
sc68calcorrect18:22
nati_uen_ok18:22
nati_uen_so ml2 + ovs mech driver18:22
nati_uen_support it18:22
nati_uen_how we specify directions?18:22
sc68calyes - and there is a ml2 + lb mech impl for ratelimit18:22
nati_uen_ok18:22
*** Barker has quit IRC18:22
nati_uen_ingress only?18:23
kevinbenton_the reference won’t be able to rate limit, just tag, right?18:23
*** aratim has left #openstack-meeting-alt18:23
sc68calI think egress18:23
nati_uen_ok18:23
nati_uen_Can we use it in virtual router?18:23
sc68calhttps://review.openstack.org/9633118:23
nati_uen_ok Thanks18:23
sc68calI would imagine so, tag the virtual router's port with a rate-limit policy18:23
nati_uen_so someone will apply rate limit by tag?18:24
sc68calunsure18:24
sc68caldo you mean by .1q tag?18:24
*** Barker has joined #openstack-meeting-alt18:25
*** Leonr has joined #openstack-meeting-alt18:25
*** denis_makogon has quit IRC18:25
nati_uen_ah may be I don't understand the meaning of "just tag"18:25
*** denis_makogon_ is now known as denis_makogon18:25
sc68calAhhhh18:25
sc68calok I mean like18:25
s3wongsc68cal: .1p is priority tagging, if I remember correctly?18:25
*** dmakogon_ has joined #openstack-meeting-alt18:25
*** shakayumi has joined #openstack-meeting-alt18:26
sc68calneutron port-update <router port ID> --qos <ratelimit policy ID>18:26
sc68calsorry for the confusion18:26
*** shakayumi has quit IRC18:26
s3wongsc68cal: what is the definition of ratelimit policy?18:26
*** jmontemayor has quit IRC18:26
s3wong(sorry, too lazy to look up now...)18:27
sc68calfairly basic18:27
sc68calhttps://review.openstack.org/#/c/88599/3/specs/juno/qos-api-extension.rst18:27
sc68calline.... 8018:27
sc68calbut I think I need to coordinate with the Linuxbridge ratelimit spec author to verify18:27
s3wongOK. kbps18:27
*** emagana has quit IRC18:28
sc68calhttps://review.openstack.org/#/c/96331/4/specs/juno/ml2-qos-linuxbridge.rst18:28
*** _nadya_ has joined #openstack-meeting-alt18:28
*** emagana has joined #openstack-meeting-alt18:28
*** alazarev has joined #openstack-meeting-alt18:31
nati_uen_ok so any other topics?18:31
*** SumitNaiksatam has quit IRC18:31
kevinbenton_nothing from me18:31
nati_uen_me too18:31
s3wongI am interested in QoS due to group-policy policy-rule action18:31
*** netapp has quit IRC18:32
s3wongbut will have to look at the current proposal to better understood how we can utilize this18:32
sc68calCurrently, I think GP is going to consume the qos API18:32
*** _nadya_ has quit IRC18:32
sc68calor at least the hope is to minimize duplication by having the GP drive the qos API18:32
*** balajiiyer has quit IRC18:32
s3wongsc68cal: sounds good - quite honestly we don't yet have any definition on how to set QoS as action18:33
*** jmontemayor has joined #openstack-meeting-alt18:33
s3wongbut utilizing the qos API directly is a good plan18:33
*** jmontemayor has quit IRC18:34
*** balajiiyer has joined #openstack-meeting-alt18:34
*** kgriffs|afk is now known as kgriffs18:34
*** jmontemayor has joined #openstack-meeting-alt18:34
sc68calAnything else? I can give everyone back half an our18:35
sc68cal*hour18:35
s3wongall good18:35
sc68calI'll make a subteam wiki page so we can start building agendas for things people want to talk about :)18:35
sc68cal#action sc68cal make a subteam wiki page18:35
s3wongsounds great18:36
sc68calOK then everyone, thanks for joining, see everyone next week!18:36
sc68cal#endmeeting18:36
s3wongbye18:36
*** openstack changes topic to "Zuul is offline due to an operational issue; ETA 2200 UTC."18:36
openstackMeeting ended Tue Jun  3 18:36:26 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:36
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2014/neutron_qos.2014-06-03-18.02.html18:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2014/neutron_qos.2014-06-03-18.02.txt18:36
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2014/neutron_qos.2014-06-03-18.02.log.html18:36
*** aveiga has quit IRC18:36
*** netapp has joined #openstack-meeting-alt18:36
*** samstav has quit IRC18:37
nati_uen_bye!18:37
*** nati_uen_ has quit IRC18:39
*** nati_ueno has joined #openstack-meeting-alt18:39
*** samstav has joined #openstack-meeting-alt18:39
*** samstav_ has joined #openstack-meeting-alt18:40
*** samstav has quit IRC18:40
*** Youcef has quit IRC18:41
*** ajo|mac has joined #openstack-meeting-alt18:42
*** kgriffs is now known as kgriffs|afk18:44
*** IlyaE has quit IRC18:44
*** yogeshmehra has quit IRC18:46
*** morazi has joined #openstack-meeting-alt18:46
*** yogeshmehra has joined #openstack-meeting-alt18:46
*** pballand has quit IRC18:48
*** yogeshme_ has joined #openstack-meeting-alt18:49
*** yogeshmehra has quit IRC18:51
*** nati_ueno has quit IRC18:53
*** luizfar_ has joined #openstack-meeting-alt18:54
*** luizfar has quit IRC18:54
*** kgriffs|afk is now known as kgriffs18:54
*** luizfar_ is now known as luizfar18:54
*** otherwiseguy has joined #openstack-meeting-alt18:54
*** nati_uen_ has joined #openstack-meeting-alt18:55
*** rpodolyaka1 has joined #openstack-meeting-alt18:55
tchaypooh good, I'm already here18:57
*** matty_dubs has joined #openstack-meeting-alt18:58
*** ccrouch has joined #openstack-meeting-alt18:59
*** TheJulia has joined #openstack-meeting-alt18:59
*** otherwiseguy has quit IRC18:59
*** dprince has joined #openstack-meeting-alt19:00
*** pcrews has joined #openstack-meeting-alt19:00
jdobo/19:00
rpodolyaka1o/19:00
*** dtx00ff has quit IRC19:00
lifelesso/19:00
jprovaznhi19:00
GheRiveroo/19:00
*** pballand has joined #openstack-meeting-alt19:00
bnemec\o19:00
*** dtx00ff has joined #openstack-meeting-alt19:01
lifeless#startmeeting tripleo19:01
openstackMeeting started Tue Jun  3 19:01:14 2014 UTC and is due to finish in 60 minutes.  The chair is lifeless. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: tripleo)"19:01
openstackThe meeting name has been set to 'tripleo'19:01
Ng.o/19:01
*** greghaynes has joined #openstack-meeting-alt19:01
greghaynesO/19:01
lifeless#topic agenda19:01
*** openstack changes topic to "agenda (Meeting topic: tripleo)"19:01
jcoufalo/19:01
lifeless    bugs19:01
lifeless    reviews19:01
lifeless    Projects needing releases19:01
lifeless    CD Cloud status19:01
lifeless    CI19:01
lifeless    Tuskar19:01
lifeless    Insert one-off agenda items here19:01
lifeless    open discussion19:01
lifeless#topic bugs19:01
*** openstack changes topic to "bugs (Meeting topic: tripleo)"19:01
*** otherwiseguy has joined #openstack-meeting-alt19:01
*** jmontemayor has quit IRC19:01
lifeless#link https://bugs.launchpad.net/tripleo/19:01
lifeless#link https://bugs.launchpad.net/diskimage-builder/19:01
lifeless#link https://bugs.launchpad.net/os-refresh-config19:01
lifeless#link https://bugs.launchpad.net/os-apply-config19:01
lifeless#link https://bugs.launchpad.net/os-collect-config19:02
lifeless#link https://bugs.launchpad.net/os-cloud-config19:02
lifeless#link https://bugs.launchpad.net/tuskar19:02
lifeless#link https://bugs.launchpad.net/python-tuskarclient19:02
*** emagana has quit IRC19:02
*** derekh_ has joined #openstack-meeting-alt19:02
rwsuhi19:02
derekh_hi19:02
*** jistr has joined #openstack-meeting-alt19:02
matty_dubso/19:02
slaglehello19:03
jistro/19:03
dprincehello TripleO19:03
shadowerhey19:03
SpamapSo/19:03
*** betsy has joined #openstack-meeting-alt19:03
*** samstav_ has quit IRC19:03
*** tjanczuk has quit IRC19:03
jristo/19:03
*** samstav has joined #openstack-meeting-alt19:04
tchaypoapplmorgens19:04
*** Obulpathi has quit IRC19:04
lifelesstriage is looking a lot better. thank you to the folk that got on top of it!19:04
*** samstav has quit IRC19:04
tchaypostevek and i got through a bunch in an office together last friday19:04
lifelesslooks like a bunch of the criticals will be fixed by the next release19:05
lifelessbut their bug state isn't quite right19:05
*** Obulpathi has joined #openstack-meeting-alt19:05
*** otherwiseguy has quit IRC19:05
lifelesse.g. why is https://bugs.launchpad.net/tripleo/+bug/1318039 a partial fix?19:06
lifelessdprince: ^19:06
*** jmontemayor has joined #openstack-meeting-alt19:06
dprincelifeless: it should be fully fixed by my patch I think19:07
lifelessok, will tweak to fix committed19:07
dprincelifeless: Initially I thought we might do both...19:07
lifelesscould folk take just a minute and review the criticals list particularly in the tripleo bug container19:08
lifelessand if anything there is incorrect or stale fix it?19:08
*** samstav has joined #openstack-meeting-alt19:08
* dprince marks 1318039 as fix committed19:08
*** tzumainn has joined #openstack-meeting-alt19:08
*** satish has quit IRC19:09
*** IlyaE has joined #openstack-meeting-alt19:10
*** emagana has joined #openstack-meeting-alt19:10
tchaypoas far as I can tell mestery's fix for https://bugs.launchpad.net/tripleo/+bug/1290486 is working well, we've had a few other people comment to say that it's fixed for them.19:10
mesterytchaypo: Yay!19:10
lifelesscool, was that in Neutron? can we close our end of it ?19:11
*** markwash_ has joined #openstack-meeting-alt19:12
SpamapShttps://bugs.launchpad.net/tripleo/+bug/1317056 needs a volunteer19:12
tchaypoour end is marked "fix commited" which i think is right19:12
rpodolyaka1SpamapS:  just assigned it to myself :)19:12
lifelesstchaypo: ah no19:13
SpamapSrpodolyaka1: \o/19:13
lifelesstchaypo: fix committed means 'the next release of that project will fix the issue'19:13
lifelesstchaypo: AIUI the change is not in a tripleo codebase19:13
*** NehaV1 has joined #openstack-meeting-alt19:14
*** NehaV has quit IRC19:14
*** Obulpathi has quit IRC19:14
tchaypolifeless: ah, good point. in progress then?19:14
*** markwash has quit IRC19:14
*** emagana has quit IRC19:14
lifelesstchaypo: so theres some idiomatic use of the tracker here; if the bug shows up in tripleo we have a task for it; once fixed and we don't need to see it anymore, then we typically close it19:14
*** Obulpathi has joined #openstack-meeting-alt19:15
lifelessI'd close fix released (as good as anything really)19:15
lifelessrpodolyaka1: \o/19:15
lifelessok, any more bug discussion ?19:15
*** kevinbenton_ has quit IRC19:16
lifeless#topic reviews19:16
*** openstack changes topic to "reviews (Meeting topic: tripleo)"19:16
lifelesshttp://www.nemebean.com/reviewstats/tripleo-open.html19:17
lifelessulp19:17
lifelessno worse19:17
lifelessbut also no better19:17
lifeless19:17
lifelessStats since the last revision without -1 or -2 :19:17
lifeless    Average wait time: 9 days, 17 hours, 20 minutes19:17
lifeless    1rd quartile wait time: 3 days, 7 hours, 25 minutes19:17
lifeless    Median wait time: 5 days, 19 hours, 43 minutes19:17
lifeless    3rd quartile wait time: 12 days, 7 hours, 32 minutes19:17
*** emagana has joined #openstack-meeting-alt19:18
*** markwash_ has quit IRC19:18
lifelessstats are a few days old but close enough I think19:18
lifelesslets try for 11 next week? I"ll be doing a reviewer roundup this week, since its the first of the month19:18
bnemecOh, sorry.  Updated my web server and I may have broken the file transfer...19:19
shadowermy reviews dropped in the last few weeks because reasons, will start doing them again properly now19:19
*** NehaV1 has quit IRC19:19
lifelessok, cool19:20
lifelessdesign reviews19:20
jdobi've been too heads down on specs too, I need to resurface and look at normal reviews19:20
lifelessI'm not seeing enough folk comment on the specs19:20
*** netapp has quit IRC19:20
jdobis there a full policy on when a spec will be accepted? (or want me to hold that until open discussion?)19:20
jdobi know we're leaving the +A for lifeless but not sure when he pulls that trigger19:21
tchaypoI commented on a few but I haven't followed up. Will try to do that today. I have seen a few items that should be specs but haven't written any of them up19:21
lifelessjdob: so at the moment I am feeling my way19:21
*** tjanczuk has joined #openstack-meeting-alt19:21
lifelesshow long to wait for ops input19:21
lifelesshow much consensus amongst the review community is needed19:21
lifelessI don't have an algorithm yet19:21
jdobword, that totally makes sense since it's a new process19:22
lifelessits a very good question19:22
*** netapp has joined #openstack-meeting-alt19:22
lifelessand one of the ways we can learn is us as a group saying 'hey, that needed to bake longer', and 'oi, get that one off the stove'19:22
lifelessI thinkk the general process though is draft-> core reviews until broadlyhappy, ops and user reviews, final polish, +A19:23
jdoband related to specs, can we get someone to write up specs/blueprints for the tht changes? ive seen it referenced in 3 reviews now without a link to it19:23
jdobpersonally, I could really use a summary of what the changes will look like19:23
jdoboutside of the email outlining the high level steps19:24
lifelessthe tht changes ?19:24
shadowerjdob: you mean stuff like the HOT conversion, reducing merge.py impact etc?19:24
jdobconversion to HOT templates, pulling out provider resources, etc19:24
jdob(got lazy in my typing, sorry)19:24
jdobshadower: ya, that's it19:24
lifeless+1, love to see some prose around that19:25
shadowerwe've kind of hashed that out on the mailing list, I could specify19:25
shadowerspec'ify19:25
jdobit's important for Tuskar and i'd like to have something to point the people who pay me at to say "This is a dependency"19:25
shadowerk, will do19:25
jdobhopefully it'll be easy then if its just converting the email into spec19:25
jdobthanks shadower  :D19:25
jdoblast comment on this topic, I really dig this spec process19:25
shadower+119:25
*** zzelle_ has left #openstack-meeting-alt19:25
*** shakayumi has joined #openstack-meeting-alt19:26
*** shakayumi has quit IRC19:26
shadowerI'm not a fan of gerrit's UI but it sure beats launchpad blueprints for discussions19:26
*** otherwiseguy has joined #openstack-meeting-alt19:26
jdobsame on both accounts19:26
jdobboth counts?19:26
jdobnot actually sure what the real phrase is19:26
*** tnurlygayanov__ has quit IRC19:26
lifelesscounts19:26
slagleneed gerrit to actually render the rst19:27
*** dane_leblanc has joined #openstack-meeting-alt19:27
jdobgood to know :)19:27
jdobdude, yes19:27
*** s3wong_ has joined #openstack-meeting-alt19:27
lifelessI belive its a reference to double-counting systems like votes19:27
* SpamapS doesn't understand why people hate on Gerrit.. but w'ever. :)19:27
jristearly and often?19:27
jdobi've been checking them out because it's way easier to generate and read them19:27
lifelesswhere two groups that don't trust each other cross-check :)19:27
shadowerSpamapS: not hate, but it's got its warts19:27
*** s3wong_ has quit IRC19:27
jdobappropriate phrase to use around here then :)19:27
derekh_the gate-tripleo-specs-docs generates the docs doesn't it19:28
jdober, meaning to read them that way19:28
*** dane_leblanc has quit IRC19:28
derekh_but it would be noce to comment agains a rendered rst... ponys19:28
jdobas compared to straight rst19:28
jdobwhich, despite their claims of being WYSIWYG, is exactly not that (but I digress)19:28
*** dane_leblanc has joined #openstack-meeting-alt19:28
*** resker has joined #openstack-meeting-alt19:29
*** s3wong has quit IRC19:29
slaglederekh_: oh does it?19:29
derekh_slagle: http://docs-draft.openstack.org/26/95026/2/check/gate-tripleo-specs-docs/ad3398a/doc/build/html/specs/juno/tripleo-juno-ci-improvements.html19:29
lifelessok19:30
jdoboh crap, that's handy19:30
lifelessmoving on19:30
*** Obulpathi has quit IRC19:30
lifeless#topic projects needing releases19:30
*** openstack changes topic to "projects needing releases (Meeting topic: tripleo)"19:30
rpodolyaka1you can count on me19:30
*** esker has quit IRC19:30
tchaypoyou can find the generated RST from the "gate-tripleo-specs-docs" link in the jenkins comment19:30
lifeless\o/19:30
lifeless#action rpodolyaka1 to save the universe^W^W^Wrelease the world19:30
*** otherwiseguy has quit IRC19:30
lifeless#topic CD Cloud Status19:31
*** openstack changes topic to "CD Cloud Status (Meeting topic: tripleo)"19:31
lifelessHP region one is mid rebuild19:31
*** Obulpathi has joined #openstack-meeting-alt19:31
lifelessAFAIK the RH region one is fine19:31
derekh_lifeless: yup, R2 seems to be tocking along ok19:31
*** otherwiseguy has joined #openstack-meeting-alt19:32
lifeless#topic CI19:32
*** openstack changes topic to "CI (Meeting topic: tripleo)"19:32
*** esker has joined #openstack-meeting-alt19:32
lifelessjoe gordon is gluing our logs into elastic-recheck at the moment19:32
derekh_new version of CI spec is out there,19:32
lifelessthis should help us get more figures on specific failures19:32
lifelessderekh_: cool!19:32
*** rueben has quit IRC19:33
lifelessI'd also like to say word up to pcrews who has joined TripleO within HP19:33
SpamapSwe did have one weird thing where swift/glance broke nodepool btw19:33
derekh_lifeless: it wont include the fedora logs, I looked into that today and can add systemd support on top of it when he has it finished19:33
*** Obulpathi has quit IRC19:33
lifelessand is apparently very interested in CI things :)19:33
SpamapSbut I believe infra is working on a fix and it was a temporary problem19:33
* pcrews waves and is happy to join the party :)19:33
pcrewsand also does love CI tinkering in general19:33
lifelessalso tchaypo has applied to be a tripleo-cd-admin19:33
*** resker has quit IRC19:33
*** Obulpathi has joined #openstack-meeting-alt19:33
SpamapSderekh_: we could just turn off binary journalling and use those crazy text based logs. ;)19:34
* tchaypo is a sucker19:34
dprinceSpamapS: yeah, last we talked that was a temporary image upload fluke right?19:34
lifelessso let me remind all the tripleo-cd-admins we look for much more than 2x+2 - please indicate your support on his self-adding-proposal19:34
derekh_SpamapS: k, didn't know that was possible19:34
derekh_SpamapS: I was just gonns write the logs out to unit specific files at the end of the ci run19:34
lifeless(or your lack of support if appropriate :))19:35
*** rueben has joined #openstack-meeting-alt19:35
lifelesstchaypo: whats the url ?19:35
lifelessderekh_: whatever works19:35
derekh_lifeless: tchaypo https://review.openstack.org/#/c/95614/19:36
*** otherwiseguy has quit IRC19:36
lifelesspcrews: so derekh_ is a great person with fairly large tz overlap with you to find CI things to poke at19:36
SpamapSderekh_: I believe you can teach rsyslogd to read from the systemd journal19:37
lifelesspcrews: once you've got some experience with the particulars you might also consider being an admin19:37
pcrewscool and ++.19:37
derekh_pcrews: lifeless I'm also currently writing some docs on how CI is put together so should have something for you to read up on soon19:37
*** dane_leblanc has quit IRC19:38
lifelesspcrews: taking his 'fix CI' spec from the tripleo-specs review queue and a) thoughtfully reviewing and b) starting to action stuff in parallel would be great19:38
derekh_pcrews: but feel free to poke me with questions19:38
lifelessok, moving on ?19:38
*** Barker has quit IRC19:38
lifeless#topic Tuskar19:38
*** openstack changes topic to "Tuskar (Meeting topic: tripleo)"19:38
derekh_SpamapS: ok cool, will see if it makes more sense19:38
jdobhttps://review.openstack.org/#/c/9472019:38
jdobi'd very much appreciate eyes on that, it's the Tuskar REST API spec19:39
jdobthat's kinda gonna drive everything for Juno19:39
lifelessjcoufal requested this section. jcoufal - please let us know what you want touched on, if there is anything specific19:39
jdobalso recently submitted is https://review.openstack.org/#/c/97553/, which is the new storage backend for Tuskar19:39
jdobthose are the big two Tuskar could use eyes on, and like I already requested, some notes on the template conversion (which was resolved earlier in the meeting)19:39
jcoufallifeless: I wanted to have this topic regularly, not just today with some specifics. In general I would like us to discuss progress, news and what needs attention in Tuskar (e.g. reviews, blockers, etc)19:40
lifelessjcoufal: thats fine - I realised you wanted a regular section19:41
tchaypoSo what's news in Tuskar-land?19:42
lifelessthat said, reviews and bugs should happen in the reviews and bugs sections IMO19:42
lifelessjcoufal: anyhow,  you have the stage :)19:42
tchaypono pressure ;)19:42
*** mkoderer has quit IRC19:42
jdoblifeless: sorry, I wasnt sure where to drop that request for eyes, here or the reviews section19:42
jcoufalyeah, I think majority is covered in jdob specs19:43
jcoufaljdob: would you mind to cover the progress there in few words?19:43
*** NehaV has joined #openstack-meeting-alt19:43
jdobok, quick summary:19:43
jdobthe REST API spec changes the model of Tuskar talking to Heat to making Tuskar more of a planning service19:43
jdobfor saving, configuring, organizing, etc the heat templates19:44
jdobthats in https://review.openstack.org/#/c/9472019:44
*** otherwiseguy has joined #openstack-meeting-alt19:44
jdobto anyone who has looked, it's changed quite a bit last friday, so worth another look19:44
jdobthe second major change is instead of having a database backend and a special domain model, it's going to be much closer tied to HOT19:44
jdobthat's in https://review.openstack.org/#/c/97553/ which was just posted this morning19:44
jdobi haven't read it yet, but my understanding is that it talks about using other OpenStack options for storing the heat templates and environment files19:45
jdobthose two things are the major driving changes in Juno19:45
* tchaypo stars reviews for review post-caffeine19:45
jdobthe third piece, the one that assembles the Heat templates inside of the Tuskar service, is a WIP19:45
jdobthat i'm currently working on19:45
jdobwhen not banging my head against a keyboard19:46
jcoufalthanks jdob for the summary19:46
tchaypoBoth of the first two reviews you linked also seem to be workflow -119:46
jdoboh crud, I need to remove the -1 from the REST API19:46
tchaypowhich my understanding is equivalent to "WIP" or "not yet ready for review"19:46
jdobnot sure about the latter, I'll take that up with dmakogon_19:46
tchaypoat least, i think that's what the red X in the workflow column means19:46
jdober, dougal19:46
jdobi can see why you'd think that. i've still reviewed those for specs19:47
jdobfiguring people are claiming they have stuff that warrants eyes but isn't intended to be merged yet19:47
*** demorris has quit IRC19:47
jdobthough that might just be me interpretting things differently in the spec repo19:48
*** caleb_ has joined #openstack-meeting-alt19:48
lifeless-1 workflow == WIP == draft == cannot merge => lower review priority19:48
*** caleb_ has quit IRC19:48
*** otherwiseguy has quit IRC19:48
*** emaganap has joined #openstack-meeting-alt19:48
*** jecarey has quit IRC19:48
jdobregardless, in this case, I'm requesting eyes on both and I'll get the -1 workflow sorted out19:48
lifelesskk19:48
*** IlyaE has quit IRC19:48
jdobthanks :D19:48
*** jecarey has joined #openstack-meeting-alt19:48
lifelessanything more tuskar specific?19:48
*** caleb_ has joined #openstack-meeting-alt19:49
jdobnot from my end, everything I've been doing is in spec-form19:49
jcoufalregarding tripleo/tuskar-ui, I am not going to talk a lot about it since it falls under Horizon now, but it is topic relevant. Anyway, no updates here :)19:49
d0ugaljdob, tchaypo - the second is ready for review - I just need to do a few minor tweaks. Mostly to do with wording etc.19:49
*** NehaV has quit IRC19:49
*** NehaV has joined #openstack-meeting-alt19:50
*** emagana has quit IRC19:50
lifelessok19:51
lifeless#tpoic open discussion19:51
lifeless#topic open discussion19:51
*** openstack changes topic to "open discussion (Meeting topic: tripleo)"19:51
tchaypomid-cycle meetup dates19:51
*** caleb_ has quit IRC19:51
jcoufalhere we go :)19:51
lifelessso yeah19:51
lifelessI've chatted with devananda and mikal19:51
lifelesswe don't want TripleO to overlap with Nova19:51
lifelesstoo many folk need to be at both19:52
*** caleb_ has joined #openstack-meeting-alt19:52
lifelessand we don't want to colocate - Nova has a very full schedule already and its quite a different sort of meetup19:52
jcoufallifeless: when do they plan to have it?19:52
lifelessless do-y more design-y-only19:52
*** sballe has joined #openstack-meeting-alt19:53
tchaypoSo that rules out the mid-July date?19:53
jcoufalbased on devananda's comment it looks that all three dates overlap19:54
jcoufalAnd thinking about August, it is very close to the end of the cycle19:54
tchaypothey all seem to overlp with something, except for the mid-august date, and that's very late in the cycle.19:54
jcoufaltchaypo: exactly19:54
jcoufalany suggestions?19:54
lifelesshttps://etherpad.openstack.org/p/juno-nova-midcycle-options19:55
lifelessI'd rather be near the end of the cycle than not at all19:55
tchaypoIf we could bring back concorde so that people could get between raleigh and pycon-au easier...19:55
lifelessso I'd like to suggest that the 11th august makes the most sense to me19:56
* greghaynes adds bring back concorde to trello19:56
jdobI can do august 1119:56
jcoufalso we are thinking Aug11?19:57
greghaynesAdd that date to the etherpad?19:57
jcoufalI will19:57
*** otherwiseguy has joined #openstack-meeting-alt19:58
jdobwant to put a deadline on voting so we can settle on something?19:58
derekh_Can we have a cut off for new days being added to the etherpad19:58
*** BrianB__ has quit IRC19:58
jcoufaldone19:58
greghaynesyesplz19:58
bnemechttps://etherpad.openstack.org/p/juno-midcycle-meetup19:58
derekh_jdob: +119:59
jcoufaljdob: I will leave a bit more time there and we will see how it goes19:59
jdobsure, but set an end19:59
jcoufalafter we might put a deadline19:59
jdobthursday?19:59
jdobend of week?19:59
jcoufaljdob: too early19:59
jdobkk19:59
*** julienvey has joined #openstack-meeting-alt19:59
*** flaper87 is now known as flaper87|afk20:00
jcoufallet's wait until next weeks meeting20:00
*** eankutse has quit IRC20:00
jcoufaland we can set a deadline there20:00
*** eankutse has joined #openstack-meeting-alt20:00
jcoufalI will write the update to the mailing list20:00
*** amytron has quit IRC20:00
lifelessok, we're out of time. Thanks for playing, have a good day / night/whatever :))20:00
lifelessjcoufal: thanks!20:00
lifeless#endmeeting20:00
*** openstack changes topic to "Zuul is offline due to an operational issue; ETA 2200 UTC."20:00
openstackMeeting ended Tue Jun  3 20:00:56 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tripleo/2014/tripleo.2014-06-03-19.01.html20:01
jdobo/20:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tripleo/2014/tripleo.2014-06-03-19.01.txt20:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tripleo/2014/tripleo.2014-06-03-19.01.log.html20:01
jcoufalthank you guys, have a great day/night/whatever20:01
matty_dubsSee ya, jcoufal!20:01
*** matty_dubs has left #openstack-meeting-alt20:01
*** greghaynes has left #openstack-meeting-alt20:01
*** pcrews has left #openstack-meeting-alt20:01
rpodolyaka1thanks all! good night!20:01
*** jmcbride has joined #openstack-meeting-alt20:01
*** rpodolyaka1 has left #openstack-meeting-alt20:01
*** tzumainn has left #openstack-meeting-alt20:02
*** markwash has joined #openstack-meeting-alt20:02
*** markwash has quit IRC20:02
*** otherwiseguy has quit IRC20:02
*** Ng has left #openstack-meeting-alt20:03
*** markwash has joined #openstack-meeting-alt20:03
*** jtomasek has quit IRC20:03
*** TheJulia has left #openstack-meeting-alt20:03
*** tonytan4ever has quit IRC20:03
*** otherwiseguy has joined #openstack-meeting-alt20:06
*** sarob has joined #openstack-meeting-alt20:07
*** amytron has joined #openstack-meeting-alt20:08
*** derekh_ has quit IRC20:08
*** ccrouch has left #openstack-meeting-alt20:08
*** amytron has quit IRC20:08
*** esker has quit IRC20:09
*** esker has joined #openstack-meeting-alt20:10
*** kevinbenton_ has joined #openstack-meeting-alt20:11
*** _nadya_ has joined #openstack-meeting-alt20:11
*** otherwiseguy has quit IRC20:11
*** meghal1 has joined #openstack-meeting-alt20:12
*** amytron has joined #openstack-meeting-alt20:13
*** pballand has quit IRC20:14
*** esker has quit IRC20:14
*** jcoufal has quit IRC20:15
*** jaycaz1 has joined #openstack-meeting-alt20:18
*** jistr has quit IRC20:20
*** amytron has quit IRC20:20
*** Sukhdev has quit IRC20:22
*** meghal1 has quit IRC20:24
*** NehaV has quit IRC20:25
*** _nadya_ has quit IRC20:27
*** _nadya_ has joined #openstack-meeting-alt20:27
*** nati_uen_ has quit IRC20:28
*** jecarey has quit IRC20:28
*** demorris has joined #openstack-meeting-alt20:28
*** amytron has joined #openstack-meeting-alt20:30
*** otherwiseguy has joined #openstack-meeting-alt20:32
*** Barker has joined #openstack-meeting-alt20:32
*** meghal has joined #openstack-meeting-alt20:33
*** dguryanov has joined #openstack-meeting-alt20:33
*** demorris has quit IRC20:34
*** _nadya_ has quit IRC20:35
*** NehaV has joined #openstack-meeting-alt20:35
*** sballe has quit IRC20:35
*** arnaud has quit IRC20:35
*** caleb_ has quit IRC20:36
*** otherwiseguy has quit IRC20:36
*** julim has quit IRC20:37
*** jecarey has joined #openstack-meeting-alt20:40
*** jmcbride has quit IRC20:41
*** arnaud has joined #openstack-meeting-alt20:41
*** caleb_ has joined #openstack-meeting-alt20:41
*** jmcbride has joined #openstack-meeting-alt20:43
*** ramashri has quit IRC20:44
*** ramashri has joined #openstack-meeting-alt20:46
*** nati_ueno has joined #openstack-meeting-alt20:47
*** jmcbride has quit IRC20:48
*** otherwiseguy has joined #openstack-meeting-alt20:49
*** IlyaE has joined #openstack-meeting-alt20:52
*** otherwiseguy has quit IRC20:53
*** mattgriffin has quit IRC20:56
*** jmcbride has joined #openstack-meeting-alt20:56
*** rueben has quit IRC20:59
*** jmcbride has quit IRC20:59
*** nati_uen_ has joined #openstack-meeting-alt21:00
*** nati_ueno has quit IRC21:00
*** kgriffs is now known as kgriffs|afk21:00
*** jdob has quit IRC21:00
*** dhellman_ has joined #openstack-meeting-alt21:01
*** jprovazn has quit IRC21:02
*** rueben has joined #openstack-meeting-alt21:03
*** meghal has quit IRC21:03
*** meghal1 has joined #openstack-meeting-alt21:03
*** igordcard has joined #openstack-meeting-alt21:03
*** amytron has quit IRC21:04
*** thangp has quit IRC21:04
*** pdmars has quit IRC21:05
*** _nadya_ has joined #openstack-meeting-alt21:05
*** kgriffs|afk is now known as kgriffs21:05
*** baoli has quit IRC21:07
*** jecarey has quit IRC21:08
*** jecarey has joined #openstack-meeting-alt21:08
*** luizfar has quit IRC21:10
*** dhellmann has quit IRC21:11
*** otherwiseguy has joined #openstack-meeting-alt21:12
*** dims__ has joined #openstack-meeting-alt21:13
*** jaycaz1 has quit IRC21:13
*** dhellmann has joined #openstack-meeting-alt21:13
*** armax_ has joined #openstack-meeting-alt21:15
*** jaycaz has joined #openstack-meeting-alt21:15
*** jaycaz has quit IRC21:15
*** armax has quit IRC21:15
*** armax_ is now known as armax21:15
*** jaycaz has joined #openstack-meeting-alt21:15
*** dims_ has quit IRC21:15
*** otherwiseguy has quit IRC21:16
*** otherwiseguy has joined #openstack-meeting-alt21:19
*** tdruiva has quit IRC21:21
*** yogeshme_ has quit IRC21:21
*** jaycaz has quit IRC21:21
*** tdruiva has joined #openstack-meeting-alt21:21
*** yogeshmehra has joined #openstack-meeting-alt21:22
*** demorris has joined #openstack-meeting-alt21:22
*** luizfar has joined #openstack-meeting-alt21:22
*** balajiiyer has quit IRC21:23
*** otherwiseguy has quit IRC21:23
*** jamie_h has quit IRC21:25
*** safchain has joined #openstack-meeting-alt21:25
*** dhellman_ has quit IRC21:26
*** Obulpathi has quit IRC21:30
*** IlyaE has quit IRC21:30
*** Leonr has quit IRC21:33
*** meghal1 has quit IRC21:34
*** mfer has quit IRC21:35
*** demorris has quit IRC21:36
*** morazi has quit IRC21:37
*** emaganap has quit IRC21:39
*** NehaV has quit IRC21:39
*** Leonr has joined #openstack-meeting-alt21:40
*** tjanczuk has quit IRC21:40
*** marun is now known as marun_afk21:40
*** Haiying has joined #openstack-meeting-alt21:41
*** emagana has joined #openstack-meeting-alt21:42
*** dims__ has quit IRC21:42
*** arnaud has quit IRC21:42
*** yogeshmehra has quit IRC21:43
*** yogeshmehra has joined #openstack-meeting-alt21:43
*** yogeshmehra has quit IRC21:48
*** kevinbenton_ has quit IRC21:48
*** caleb_ has quit IRC21:48
*** otherwiseguy has joined #openstack-meeting-alt21:49
*** samstav has quit IRC21:50
*** NehaV has joined #openstack-meeting-alt21:50
*** kgriffs is now known as kgriffs|afk21:51
*** _nadya_ has quit IRC21:51
*** markwash has quit IRC21:54
*** nati_uen_ has quit IRC21:54
*** luizfar has quit IRC21:56
*** samstav has joined #openstack-meeting-alt21:56
*** armax has left #openstack-meeting-alt21:57
*** adrian_otto has joined #openstack-meeting-alt21:57
*** samstav has quit IRC21:57
*** samstav has joined #openstack-meeting-alt21:57
*** stannie has quit IRC21:59
*** asalkeld has joined #openstack-meeting-alt21:59
adrian_otto#startmeeting containers22:00
openstackMeeting started Tue Jun  3 22:00:24 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: containers)"22:00
openstackThe meeting name has been set to 'containers'22:00
adrian_otto#link https://wiki.openstack.org/wiki/Meetings/Containers#Agenda_for_2014-06-03_2200_UTC Our Agenda22:00
adrian_otto#topic Roll Call22:00
*** openstack changes topic to "Roll Call (Meeting topic: containers)"22:00
ewindischo/22:00
funzoChris Alfonso22:00
adrian_ottoAdrian Otto22:00
julienveyJulien Vey22:00
Slowero/  Ian Main22:00
asalkeldo/22:01
dguryanovDmitry Guryanov22:01
*** mwagner_lap has quit IRC22:02
*** kevinbenton_ has joined #openstack-meeting-alt22:02
*** nati_ueno has joined #openstack-meeting-alt22:02
adrian_ottoWelcome everyone.22:02
adrian_otto#topic Announcements22:02
*** openstack changes topic to "Announcements (Meeting topic: containers)"22:02
*** thomasem has joined #openstack-meeting-alt22:02
thomasemo/22:03
adrian_ottoany announcements from team members?22:03
*** meghal has joined #openstack-meeting-alt22:03
adrian_otto#topic Review Action Items22:03
adrian_ottoadrian_otto to begin an ML thread for input on our Top Themes, and formation of a Wiki page to clearly document them for future reference22:03
*** openstack changes topic to "Review Action Items (Meeting topic: containers)"22:03
*** ctracey has joined #openstack-meeting-alt22:03
ewindischwe formed a nova-docker subteam22:03
ctraceyhola22:04
adrian_ottoaah, back to Announcements ;-)22:04
*** sarob has quit IRC22:04
ewindischuh, that was it? ;-)22:04
adrian_ottoewindisch: you are welcome to link that here if you wish22:04
adrian_ottook22:04
*** eankutse has quit IRC22:04
adrian_ottoadrian_otto to begin an ML thread for input on our Top Themes, and formation of a Wiki page to clearly document them for future reference22:04
adrian_ottoStatus complete22:04
*** rueben has quit IRC22:05
adrian_otto#link http://lists.openstack.org/pipermail/openstack-dev/2014-May/035977.html ML Thread for Top Themes22:05
adrian_ottoadrian_otto to attend upcoming Nova meeting, and report Containers Team position on cinder support for containers in Nova22:05
*** jmcbride has joined #openstack-meeting-alt22:05
adrian_ottoStatus complete22:05
adrian_otto#topic Questions about Containers+Cinder22:05
*** openstack changes topic to "Questions about Containers+Cinder (Meeting topic: containers)"22:05
adrian_otto(PhilD) Does not supporting cinder mean that a system using containers won't pass the DevRef standard ?22:06
SlowerWe were just looking into that22:06
*** sarob has joined #openstack-meeting-alt22:06
funzowhat Slower said22:06
*** emagana has quit IRC22:06
*** emagana has joined #openstack-meeting-alt22:06
SlowerI have no answers though heh22:06
*** denis_makogon has quit IRC22:06
ewindischadrian_otto: that’s been a big concern of mine - and there is no real solid answer22:06
*** rl has quit IRC22:06
*** NehaV has quit IRC22:07
*** IlyaE has joined #openstack-meeting-alt22:07
*** emaganap has joined #openstack-meeting-alt22:07
ewindischexcept that I spoke to Josh McKenty and Rob Hirschfield, and they both stated that they’d - ideally - like to make it such that Docker can pass DefCore standards22:07
ewindisch(and containers)22:07
ewindischthat if there is an issue, it may lie in problems in the DefCore definitions, rather than an innate inability of containers to comply...22:08
Slowerwhat would be involved to get eg docker to support cinder?22:08
ctraceyThere are a lot of "hypervisor" agnostic OpenStack use cases that have no need for Cinder22:09
Sloweror is that just a no go?  someone want to give a little background?22:09
ewindischbut yes, as-of-right-now, lack of Cinder support would fail a RefStack and thus DefCore check22:09
ewindischSlower: I’ve done the analysis. Implementing it would be no more difficult than the pause/unpause work22:09
Slowerto me that sounds reasonable then..22:10
*** sarob has quit IRC22:10
adrian_ottoso is it appropriate to relax the requirement, or is there a way to technically meet the requirement, even if that approach is theoretical?22:10
SlowerI'd be willing to take that on22:10
funzoewindisch: Slower sounds like a good thing to do this week.22:10
funzoSlower: you mean we. WE, man22:10
Slowerwith the amazing funzo's help22:10
*** emagana has quit IRC22:10
ctraceyI think the requirement needs to be relaxed even if it gets implemented22:10
Slowerfunzo: but of course :)22:11
adrian_ottook, is there a concrete reference to the Defcore requirement we are concerned about?22:11
adrian_ottoI'd like to record it with a #link if possible22:11
ewindischI’m good until Thursday, but then I go to SF for Dockercon and will be out-of-pocket until Wedsday or Thursday22:11
*** JHop has joined #openstack-meeting-alt22:11
Slowerewindisch: ok we'll hit you up for info tomorrow22:11
*** dims has joined #openstack-meeting-alt22:12
ewindischhttps://wiki.openstack.org/wiki/RefStack/DefCore_Requirements22:12
adrian_ottoSlower: are you willing to take an action item to identify technical options for better meeting the cinder integration expectations?22:12
*** Barker has quit IRC22:12
*** rueben has joined #openstack-meeting-alt22:12
ewindischstrictly speaking, that forwards you to the implementation of refstack which lists this: https://github.com/stackforge/refstack/blob/master/defcore/havana/coretests.json22:12
adrian_ottothanks ewindisch22:12
adrian_otto#link https://wiki.openstack.org/wiki/RefStack/DefCore_Requirements22:12
adrian_otto#link https://github.com/stackforge/refstack/blob/master/defcore/havana/coretests.json22:13
ewindischSlower: sounds good. I even have a patch started on the nova-docker side22:13
Sloweradrian_otto: sure22:13
adrian_ottowhat I'd be looking for is preposals for what more sensible requirements might be, and what options exist for implementation that close the gap toward that22:13
ewindischthe big gap in defcore compatibility isn’t in supporting Cinder22:14
adrian_otto#action Slower to identify implementation options for adding cinder support to nova-docker to more closely meet expectations for DefCore criteria22:14
ewindischbut the inability of containers to actually mount filesystems22:14
Sloweradrian_otto: well basically Im going to try to implement it for nova docker22:14
Sloweryeah22:14
adrian_ottoa pull request is fine ;-)22:14
Slowergood then :)22:14
ewindischthat is, we can support cinder from the docker driver, but we can’t pass refstack tests as they exist today without mounting filesystems22:15
adrian_ottook, so ctracey does this address your concern?22:15
ewindischand it’s up for debate as to if that should be a defcore requirement22:15
ctraceyYes. Though I think this is bigger than docker integration itself.22:15
adrian_ottook, so one option to deal with that would be to meet with the Coredef committee, right?22:16
*** emaganap has quit IRC22:16
adrian_ottoand raise this subject for discussion there22:16
ctraceyYep22:16
adrian_ottodoes anyone know when they meet, or could peek at the list of meeting schedules to find out?22:17
ewindischadrian_otto: yes. I would preface that with actually getting cinder support in nova-docker and seeing to having a basic ‘just dd to the disk’ test in Tempest22:17
*** _nadya_ has joined #openstack-meeting-alt22:17
adrian_ottoewindisch: that's fair22:17
adrian_ottowe don't have to activate on this immediately, but I'd like to work this from both ends if we don't need the cinder requirements to be as strict22:18
ewindischadrian_otto: Thursday is the refstack/defcore meeting… I’ve been making sure to attend since the sumit22:18
adrian_ottoewindisch: ok, thanks22:18
*** gondoi is now known as zz_gondoi22:18
ewindisch*summit22:18
*** rl has joined #openstack-meeting-alt22:19
adrian_ottoso should we wait a week or two, and then add this subject to the agenda for that meeting once we have naieve support for cinder in nova-docker?22:19
adrian_ottowe will have this same concern for other virt drivers as well22:19
adrian_ottoor other downstream technology that we might access through libvirt, etc.22:19
*** SumitNaiksatam has joined #openstack-meeting-alt22:20
adrian_otto#action adrian_otto to follow up with Slower and ewindisch to determine when we should address cinder requirements with refstack team22:20
adrian_ottoany other thoughts on this question?22:20
dguryanovWhat about mounts from host? Isn't it simpler to add another API call to nova ?22:20
*** tjanczuk has joined #openstack-meeting-alt22:21
ewindischdguryanov: there are security concerns with that22:21
ewindischfilesystem mounting can easily compromise the host22:21
adrian_ottoit could be offered as a use-at-your-own-risk feature, right?22:22
*** yogeshmehra has joined #openstack-meeting-alt22:22
adrian_ottothere are some environments where that might be acceptable22:22
ewindischbut yes, there are workarounds. You could launch a qemu instance, mount the filesystem, then use NFS (or something) to serve back to the container.22:23
Slowerthat requires knowlegeable users though22:23
*** jmontemayor has quit IRC22:23
*** IlyaE has quit IRC22:23
adrian_ottook, let's wrap on this one for this week22:23
*** IlyaE has joined #openstack-meeting-alt22:24
adrian_ottowe will revisit this in the action items review at our next week meeting.22:24
*** nati_ueno has quit IRC22:24
adrian_ottowith any luck we might have reviews to reference22:24
*** asalkeld has left #openstack-meeting-alt22:24
adrian_ottoand we can also revisit this in our Open Discussion22:24
adrian_otto#topic Containers in OpenStack -- Review Top Themes22:25
*** openstack changes topic to "Containers in OpenStack -- Review Top Themes (Meeting topic: containers)"22:25
adrian_otto#link https://wiki.openstack.org/wiki/Teams/Containers#Top_Themes Top Themes from Stakeholders22:25
adrian_ottodo you all think we are focusing in the right areas? barking up the wrong tree?22:25
*** Haiying has quit IRC22:25
adrian_ottothat wiki is a derivative of:22:25
adrian_otto#link https://etherpad.openstack.org/p/containers Containers Etherpad22:25
ewindischI’m happy with it. Do you want to call a vote?22:26
adrian_ottoonly if we feel we need one22:26
adrian_ottoI'm open to hearing any suggestions to tweak it, and just use this as a tool for guiding our focus22:27
adrian_ottoif not, I'll advance to a more interesting topic22:27
adrian_otto#topic Identify Preferred Implementation Approaches22:27
*** openstack changes topic to "Identify Preferred Implementation Approaches (Meeting topic: containers)"22:27
*** luizfar has joined #openstack-meeting-alt22:27
adrian_ottoIdentify Implementation options identified in https://etherpad.openstack.org/p/containers and determine if there is consensus for a primary approach.22:27
adrian_ottoso over the last couple of weeks we explored some pro/con arguments for each of the implementation options. This consensus will answer the question: "Where do containers fit in OpenStack?"22:28
*** sarob has joined #openstack-meeting-alt22:29
adrian_ottoso before we debate the merits of each, I'd like to ask if there are other options that should be on that list?22:29
*** thomasem has quit IRC22:30
ewindischI’m still not sure how #3 differs from #1… they both read as, “add extensions to Nova”, how those extensions look is TBD22:30
adrian_ottonote that option 3 could be implemented using a host agent or a guest agent, or both22:30
adrian_ottoewindisch: ^22:31
adrian_ottowhereas, #1 probably ony addresses the functionality set that VMs and containers have in common22:31
ewindischadrian_otto: #1 lists, “- implement containers extensions to sit on top / extend Nova “22:31
*** nati_ueno has joined #openstack-meeting-alt22:32
ewindischmaybe scratch that line from #1 and move it to #3 for clarity?22:32
adrian_ottook22:32
adrian_ottothanks for moving that22:33
adrian_ottook, are there more options?22:33
*** Leonr has quit IRC22:33
*** luizfar has quit IRC22:34
adrian_ottook, so let's take a quick poll to see where we are starting22:34
ewindisch#afterstack22:34
ewindisch;-)22:34
adrian_ottowhat's the heading number of the option you currently prefer?22:35
adrian_otto322:35
ewindischin this case, my guiding principle has been to do #3 with an open door to #5, as I don’t think we can make a solid determination on that without a better plan for what those containers extensions will look like for Nova.22:35
adrian_ottoyes, 3 does not preclude 5.22:35
adrian_ottoso I suppose we might narrow the options to what to do first22:36
adrian_ottoand then expand on taht with some future vision for where to head next22:36
adrian_ottoso we have two indications of #3, do I hear others?22:36
SlowerI think #3 is the best balance and most attainable22:37
ewindischI should clarify I’m suggesting we do planning for #3, then decide if we should continue with #3, switch to #2, or switch to #5.22:37
dguryanov3. as virt driver + extend nova, if I anderstood correctly22:37
Slowerand we can basically start with #1 and add #3 features22:37
*** amytron has joined #openstack-meeting-alt22:37
adrian_ottoSlower: yes.22:38
adrian_ottook, any more thoughts?22:38
Slowerit seems like #1 has pretty good political backing22:38
ewindischSlower: agreed, but #3 is an extension of #1, more than a divergent option22:39
adrian_ottoI have not found any stackers who think that Containers should not fit anywhere22:39
ewindisch“do everything we can to the Nova API then do the rest in extensions"22:39
ewindischadrian_otto: you haven’t spoken to Joe Gordon, then ;-)22:39
adrian_ottobut we have not yet reached consensus about where they belong short, medium, and long term22:39
adrian_ottoewindisch: is it possible for us to express his point of view in a fair way, so we can understand it?22:40
meghalso in #3 by host-agent does it refer to something like a docker daemon running on compute hosts ? and nova-api interacting with that agent ?22:40
adrian_ottomeghal: Yes, thats one way to deal with it. We could have a nova extension that talks to a combination of host and/or guest agents to deal with the "inside the os" functionality22:41
adrian_ottoanother option is to have a separate API endpoint for that, and only use nova for the "outside the os" functionality set22:42
ewindischadrian_otto: sorry, I was kidding - I believe his expression was more of, “containers shouldn’t be everywhere” - rather than, “anywhere”.22:42
dguryanovWhat about application containers? 3. is suitable only for lightweight-VM-containers22:42
adrian_ottodguryanov: agreed, an app container (such as a JVM, if I understand you) would be better managed by an approach like #2.22:43
meghaladrian_otto:  thanks, so by guest-agents we are also looking into possibility of inside vm OS scenarios…so coming into picture after vm instances are already booted22:43
*** kevinbenton_ has quit IRC22:43
*** rueben has quit IRC22:44
adrian_ottomeghal: yes. For example, if we want to support the running of a process within the container for example, with a particular shell environment set at boot time.22:44
ewindischadrian_otto: I understood his question more directed at docker-style microservices versus lxc/openvz “full OS” containers22:44
*** jgrimm has quit IRC22:44
ctraceyisnt that already doable in nova-docker today?22:45
adrian_ottoctracey: yes.22:45
ewindischactually #3 does raise some interesting points if we look at implementing these features for V22:45
ewindischVMs22:46
ewindischright now, we can specify the command-line for Docker containers, but that is seen as mapped to the kernel command-line22:46
*** jmcbride has quit IRC22:46
meghaladrian_otto: got it…thanks…yes, ewindisch I actually confused #3 with vms and thought about interacting with qemu guest agent inside the vms22:46
meghalqemu guest agent for example22:47
ewindischif we wanted to extend the nova api to run a command “inside the OS”, then the mapping between kernel and OS is mismatched22:47
adrian_otto+122:47
*** nati_uen_ has joined #openstack-meeting-alt22:47
adrian_ottook, I had Host Agent Discussion on the agenda, knowing that we would use more time on the previous discussion22:48
adrian_ottoI'm planning to keep that there for next week, and have you all think about this, and watch for ML discussion on the topic22:48
*** tjanczuk has quit IRC22:49
adrian_ottoso I will open us up for Open Discussion now22:49
adrian_otto#topic Open Discussion22:49
*** openstack changes topic to "Open Discussion (Meeting topic: containers)"22:49
ewindischfirst - back to Cinder...22:49
ewindischone big stopper is that attaching block devices to the host is responsiblity of the virt driver22:49
ewindischthat is, connecting iscsi, fiber-channel, coraid, etc… is all virt-driver specific22:50
dguryanovI think we could move code from libvirt's driver to some common lib22:50
ewindischyes, we can, and I’ve spoken to mikal about it.22:50
*** nati_ueno has quit IRC22:50
ewindischhe is okay with us doing that, even with the containers code outside the tree, but we need to do the blueprint22:50
ewindischI promised it, but haven’t delivered on it yet. :)22:51
ewindischI was planning to have that ready for this week’s Nova meeting, though22:52
dguryanovSo who will actually fix the code?22:53
adrian_ottoSlower?22:54
Slowerhehe22:54
ewindischdguryanov: I’m willing/able to do work on it, but I’d appreciate help from anyone willing (Slower?)22:54
Sloweryeah I can help22:54
Slowerfunzo will too I bet :)22:54
SlowerI guess just calling to libvirt won't work?22:55
Slowerseems like splitting it out is not the best idea?22:55
ewindischSlower: it doesn’t belong in virt/libvirt, it can be easily moved out22:55
ewindischI counted maybe 3-4 lines that seemed to really depend on libvirt, but it’s possible I’ve misguaged the effort22:55
Sloweroh this is just the nova libvirt driver, not libvirt itself?22:55
*** jmcbride has joined #openstack-meeting-alt22:56
Slowergotcha22:56
Slowerok22:56
dguryanovCIFS support should be implemented separately, because qemu accesses it without block device on host.22:56
Slowerewindisch: ya I can help with that22:56
ewindischSlower: thanks22:56
*** Stanzi has quit IRC22:56
* Slower is slow sometimes22:57
ewindischdguryanov: interesting.22:57
*** Stanzi has joined #openstack-meeting-alt22:57
ewindischdguryanov: that’s something that is an acceptable caveat, though, “Cinder support - doesn’t support CIFS” - etc22:57
ewindischI suspect vmware, xen don’t support all of the cinder backends22:58
dguryanovYes, as I remember they support ISCSI and possibly NFS22:58
ewindischnext topic - cloud-init?22:58
*** kevinconway has quit IRC22:58
ewindischthat might be outside the scope for this team? I suppose it’s a per-image issue.22:59
*** yogeshmehra has quit IRC22:59
ewindischit might be a matter of creating a document saying how to use it with containers — or not22:59
*** julienvey has quit IRC22:59
*** carl_baldwin has quit IRC22:59
harlowjahmmm, cloud-init22:59
harlowjadid i hear cloud-init22:59
ewindischsince it isn’t something I think we can address in the drivers themselves22:59
*** yogeshmehra has joined #openstack-meeting-alt22:59
*** TravT has quit IRC22:59
Slowerso the issue is it's only in some containers?22:59
adrian_ottotime to wrap23:00
adrian_ottothanks everyone. I liked getting more technical this week, we will keep this up.23:00
Slowercool thx guys23:00
ewindischthanks adrian_otto.23:00
ctraceythanks all23:00
adrian_ottonext meeting is Tue 6/10 at 1600 UTC23:00
ewindisch*and everyone else23:00
adrian_otto#endmeeting23:00
*** openstack changes topic to "Zuul is offline due to an operational issue; ETA 2200 UTC."23:00
openstackMeeting ended Tue Jun  3 23:00:50 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/containers/2014/containers.2014-06-03-22.00.html23:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/containers/2014/containers.2014-06-03-22.00.txt23:00
openstackLog:            http://eavesdrop.openstack.org/meetings/containers/2014/containers.2014-06-03-22.00.log.html23:00
*** Stanzi has quit IRC23:01
*** esker has joined #openstack-meeting-alt23:02
*** ykotko has quit IRC23:03
*** aostapenko has quit IRC23:03
*** ykotko has joined #openstack-meeting-alt23:03
*** dguryanov has quit IRC23:03
*** aostapenko has joined #openstack-meeting-alt23:04
*** yogeshmehra has quit IRC23:04
*** kevinbenton_ has joined #openstack-meeting-alt23:06
*** esker has quit IRC23:10
*** igordcard has quit IRC23:11
*** a_teem_ has joined #openstack-meeting-alt23:14
*** zhiyan_ is now known as zhiyan23:17
*** zhiyan is now known as zhiyan_23:18
*** banix has quit IRC23:18
*** safchain has quit IRC23:19
*** EmilienM_ has joined #openstack-meeting-alt23:20
*** DinaBelova2 has joined #openstack-meeting-alt23:20
*** alaski_ has joined #openstack-meeting-alt23:20
*** a_teem has quit IRC23:20
*** alaski has quit IRC23:20
*** peoplemerge has quit IRC23:20
*** andreaf has quit IRC23:20
*** dmakogon_ has quit IRC23:20
*** ruhe has quit IRC23:20
*** DinaBelova has quit IRC23:20
*** EmilienM has quit IRC23:20
*** DinaBelova2 is now known as DinaBelova23:20
*** EmilienM_ is now known as EmilienM23:20
*** rossella_s has quit IRC23:20
*** ruhe2 has joined #openstack-meeting-alt23:20
*** dmakogon_ has joined #openstack-meeting-alt23:20
*** rossella has joined #openstack-meeting-alt23:20
*** andreaf has joined #openstack-meeting-alt23:20
*** rossella is now known as rossella_s23:20
*** ruhe2 is now known as ruhe23:20
*** samstav has quit IRC23:22
*** peoplemerge has joined #openstack-meeting-alt23:23
*** IlyaE has quit IRC23:34
*** tdruiva has quit IRC23:37
*** annashe__ has quit IRC23:38
*** IlyaE has joined #openstack-meeting-alt23:38
*** IlyaE has quit IRC23:41
*** IlyaE has joined #openstack-meeting-alt23:41
*** IlyaE has quit IRC23:41
*** andreaf has quit IRC23:42
*** oomichi has joined #openstack-meeting-alt23:48
*** otherwiseguy has quit IRC23:51
*** dprince has quit IRC23:53
*** mattgriffin has joined #openstack-meeting-alt23:54
*** baoli has joined #openstack-meeting-alt23:55
*** gokrokve has quit IRC23:58

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