Tuesday, 2014-03-25

*** saschpe has quit IRC00:00
*** egallen has joined #openstack-meeting00:00
*** egallen has quit IRC00:02
*** saschpe has joined #openstack-meeting00:05
*** colinmcnamara has quit IRC00:06
*** whenry has joined #openstack-meeting00:07
*** brucer has joined #openstack-meeting00:09
*** epim has quit IRC00:10
*** stevemar has quit IRC00:11
*** radez is now known as radez_g0n300:13
*** s3wong has joined #openstack-meeting00:15
*** fawadkhaliq has quit IRC00:18
*** openstack has joined #openstack-meeting00:19
*** ChanServ sets mode: +o openstack00:19
*** IlyaE has joined #openstack-meeting00:19
*** RobinJ has quit IRC00:23
*** RobinJoe has quit IRC00:23
*** IlyaE has quit IRC00:26
*** matsuhashi has joined #openstack-meeting00:26
*** Tross has joined #openstack-meeting00:26
*** flaper87 is now known as flaper87|afk00:26
*** baoli has joined #openstack-meeting00:27
*** baoli has quit IRC00:28
*** phil_h has quit IRC00:28
*** baoli has joined #openstack-meeting00:28
*** colinmcnamara has joined #openstack-meeting00:29
*** tsekiyam_ has joined #openstack-meeting00:30
*** manishg has quit IRC00:30
*** tsekiyam_ has quit IRC00:31
*** bknudson has joined #openstack-meeting00:31
*** tsekiyama has quit IRC00:33
*** alazarev has quit IRC00:33
*** RobinJ has joined #openstack-meeting00:35
*** RobinJoe has joined #openstack-meeting00:36
*** bdpayne has quit IRC00:36
*** whenry has quit IRC00:37
*** salv-orlando has joined #openstack-meeting00:37
*** marcoemorais has quit IRC00:40
*** phil_h has joined #openstack-meeting00:40
*** EntropyWorks has quit IRC00:45
*** jcooley has quit IRC00:45
*** dcramer_ has joined #openstack-meeting00:46
*** zhikunliu has joined #openstack-meeting00:46
*** adalbas has quit IRC00:47
*** s3wong has quit IRC00:51
*** tkay has quit IRC00:52
*** yuanz has joined #openstack-meeting00:54
*** yamahata has joined #openstack-meeting00:55
*** llu_linux has joined #openstack-meeting00:55
*** lintan_ has joined #openstack-meeting00:55
*** cvbock1 has joined #openstack-meeting00:55
*** yamahata_ has quit IRC00:56
*** tianst20 has quit IRC00:56
*** colinmcnamara has quit IRC00:56
*** cvbock has quit IRC00:56
*** llu has quit IRC00:56
*** yamahata_ has joined #openstack-meeting00:56
*** lintan__ has quit IRC00:56
*** yuan has quit IRC00:57
*** tomoe_ has quit IRC00:58
*** weshay has quit IRC00:59
*** nermina has quit IRC01:03
*** colinmcnamara has joined #openstack-meeting01:04
*** colinmcnamara has quit IRC01:05
*** jjmb has joined #openstack-meeting01:05
*** krtaylor has quit IRC01:07
*** stevemar has joined #openstack-meeting01:09
*** bill_az__ has quit IRC01:09
*** thuc has quit IRC01:10
*** fawadkhaliq has joined #openstack-meeting01:10
*** thuc has joined #openstack-meeting01:10
*** RobinJoe has quit IRC01:11
*** RobinJ has quit IRC01:11
*** krtaylor has joined #openstack-meeting01:11
*** thuc has quit IRC01:15
*** mlavalle has quit IRC01:18
*** krtaylor has quit IRC01:20
*** mwagner_lap has joined #openstack-meeting01:23
*** krtaylor has joined #openstack-meeting01:23
*** rwsu has quit IRC01:26
*** natarajk has quit IRC01:26
*** Daisy_ has joined #openstack-meeting01:27
*** novas0x2a|laptop has quit IRC01:28
*** mattgriffin has joined #openstack-meeting01:29
*** SumitNaiksatam has joined #openstack-meeting01:29
*** nosnos has joined #openstack-meeting01:29
*** matsuhashi has quit IRC01:30
*** matsuhashi has joined #openstack-meeting01:30
*** zhiyan_ is now known as zhiyan01:32
*** carl_baldwin has joined #openstack-meeting01:35
*** Jianyong has joined #openstack-meeting01:36
*** Daisy_ has quit IRC01:38
*** Mandell has quit IRC01:40
*** jjmb1 has joined #openstack-meeting01:40
*** emagana has quit IRC01:41
*** neelashah has joined #openstack-meeting01:41
*** jjmb has quit IRC01:41
*** jasondotstar has joined #openstack-meeting01:41
*** rwsu has joined #openstack-meeting01:42
*** SumitNaiksatam has quit IRC01:45
*** sandywalsh has joined #openstack-meeting01:46
*** cvbock has joined #openstack-meeting01:47
*** yamahata_ has quit IRC01:48
*** cvbock1 has quit IRC01:48
*** tomoe_ has joined #openstack-meeting01:50
*** yamahata_ has joined #openstack-meeting01:50
*** ArxCruz_ has quit IRC01:51
*** SumitNaiksatam has joined #openstack-meeting01:52
*** mtanino has quit IRC01:54
*** Daisy_ has joined #openstack-meeting01:54
*** Gordonz has joined #openstack-meeting01:55
*** Gordonz has quit IRC01:56
*** yuan has joined #openstack-meeting01:56
gmurphyclear01:56
*** IYozhikov_away has quit IRC01:56
*** IgorYozhikov has joined #openstack-meeting01:56
*** Gordonz has joined #openstack-meeting01:56
*** enykeev has quit IRC01:57
*** ogelbukh has quit IRC01:57
*** IgorYozhikov is now known as IYozhikov_away01:57
*** carl_baldwin has quit IRC01:58
*** yuanz has quit IRC01:58
*** jamespage has quit IRC01:59
*** enykeev has joined #openstack-meeting01:59
*** jamespage has joined #openstack-meeting02:00
*** jamespage has quit IRC02:00
*** jamespage has joined #openstack-meeting02:00
*** baoli has quit IRC02:00
*** ogelbukh has joined #openstack-meeting02:00
*** fifieldt_ has joined #openstack-meeting02:00
*** doug_shelley66 has quit IRC02:01
*** xuhanp has joined #openstack-meeting02:01
*** Daisy_ has quit IRC02:06
*** gongysh has joined #openstack-meeting02:11
*** caleb_ has joined #openstack-meeting02:11
*** xianghui has joined #openstack-meeting02:12
*** carl_baldwin has joined #openstack-meeting02:14
*** mattgriffin has quit IRC02:14
*** carl_baldwin has quit IRC02:15
*** bknudson has quit IRC02:16
*** beagles has quit IRC02:16
*** carl_baldwin has joined #openstack-meeting02:19
*** dcramer_ has quit IRC02:19
*** thuc has joined #openstack-meeting02:21
*** xianghui has quit IRC02:22
*** carl_baldwin has quit IRC02:23
*** epico has joined #openstack-meeting02:23
*** xianghui has joined #openstack-meeting02:25
*** saschpe has quit IRC02:26
*** thuc has quit IRC02:26
*** amcrn has quit IRC02:26
*** carl_baldwin has joined #openstack-meeting02:27
*** saschpe has joined #openstack-meeting02:28
*** HenryG has joined #openstack-meeting02:29
*** jasondotstar has quit IRC02:30
*** haomaiwang has joined #openstack-meeting02:31
*** sbalukoff has quit IRC02:31
*** carl_baldwin has quit IRC02:31
*** troytoman is now known as troytoman-away02:31
*** tomoe_ has quit IRC02:33
*** rossk has quit IRC02:33
*** mestery has joined #openstack-meeting02:34
*** fawadkhaliq has quit IRC02:36
*** tomoe_ has joined #openstack-meeting02:36
*** Sukhdev has joined #openstack-meeting02:40
*** epico has quit IRC02:40
*** rfolco has quit IRC02:41
*** Daisy_ has joined #openstack-meeting02:42
*** tkay has joined #openstack-meeting02:43
*** rkukura has joined #openstack-meeting02:43
*** mestery has quit IRC02:46
*** thuc has joined #openstack-meeting02:46
*** banix has joined #openstack-meeting02:46
*** mestery has joined #openstack-meeting02:46
*** BrianB_ has quit IRC02:48
*** imsurit has joined #openstack-meeting02:48
*** salv-orlando_ has joined #openstack-meeting02:49
*** salv-orlando has quit IRC02:50
*** salv-orlando_ is now known as salv-orlando02:50
*** banix has quit IRC02:51
*** thuc_ has joined #openstack-meeting02:51
*** RobinJoe has joined #openstack-meeting02:53
*** RobinJ has joined #openstack-meeting02:53
*** thuc has quit IRC02:54
*** Tross has left #openstack-meeting02:57
*** arnaud__ has quit IRC02:57
*** Daisy_ has quit IRC02:58
*** tomoe_ has quit IRC02:58
*** banix has joined #openstack-meeting03:01
*** tkay has quit IRC03:06
*** zhiyan is now known as zhiyan_03:10
*** zhiyan_ is now known as zhiyan03:11
*** matsuhashi has quit IRC03:12
*** david-lyle has joined #openstack-meeting03:17
*** devlaps has quit IRC03:19
*** bdpayne has joined #openstack-meeting03:20
*** sweston has joined #openstack-meeting03:21
*** phil_h has quit IRC03:25
*** paragan has joined #openstack-meeting03:27
*** epico has joined #openstack-meeting03:27
*** epico has quit IRC03:27
*** gokrokve has joined #openstack-meeting03:27
*** haomaiw__ has joined #openstack-meeting03:28
*** fawadkhaliq has joined #openstack-meeting03:28
*** nosnos has quit IRC03:29
*** epico has joined #openstack-meeting03:30
*** matsuhashi has joined #openstack-meeting03:30
*** thuc has joined #openstack-meeting03:31
*** haomaiwang has quit IRC03:32
*** chandankumar_ has joined #openstack-meeting03:32
*** thuc_ has quit IRC03:34
*** vkozhukalov has joined #openstack-meeting03:35
*** thuc has quit IRC03:35
*** matsuhashi has quit IRC03:36
*** chandankumar_ has quit IRC03:40
*** erlon has quit IRC03:42
*** bdpayne has quit IRC03:43
*** Sukhdev has quit IRC03:43
*** ddutta has quit IRC03:44
*** sridhar has joined #openstack-meeting03:45
*** comay has quit IRC03:47
*** harlowja_ is now known as harlowja_away03:49
*** gokrokve has quit IRC03:50
*** amandeep has joined #openstack-meeting03:52
*** amandeep is now known as Guest1868703:52
*** gokrokve has joined #openstack-meeting03:52
*** pablosan_ has joined #openstack-meeting03:53
*** ddutta has joined #openstack-meeting03:54
*** alex-gone is now known as alex-sick03:54
*** banix has quit IRC03:54
*** pablosan has quit IRC03:54
*** Guest18687 is now known as jimidar03:54
*** chandankumar_ has joined #openstack-meeting03:55
*** banix has joined #openstack-meeting03:56
*** nelsnelson has quit IRC03:56
*** gokrokve has quit IRC03:57
*** tomoe_ has joined #openstack-meeting04:00
*** alazarev has joined #openstack-meeting04:01
*** bdpayne has joined #openstack-meeting04:03
*** jimidar has quit IRC04:04
*** Amandeeps has joined #openstack-meeting04:05
*** Amandeeps is now known as jimidar04:05
*** Longgeek has joined #openstack-meeting04:10
*** Mandell has joined #openstack-meeting04:10
*** banix has quit IRC04:11
*** nati_ueno has quit IRC04:13
*** tomoe_ has quit IRC04:13
*** tomoe_ has joined #openstack-meeting04:14
*** rkukura has left #openstack-meeting04:14
*** ddutta has quit IRC04:15
*** Linz has quit IRC04:16
*** Linz has joined #openstack-meeting04:16
*** thuc has joined #openstack-meeting04:18
*** tomoe_ has quit IRC04:18
*** thuc_ has joined #openstack-meeting04:18
*** devlaps has joined #openstack-meeting04:21
*** thuc has quit IRC04:22
*** matsuhashi has joined #openstack-meeting04:23
*** chandankumar_ has quit IRC04:23
*** nosnos has joined #openstack-meeting04:25
*** bdpayne has quit IRC04:26
*** fifieldt_ has quit IRC04:28
*** tomoe_ has joined #openstack-meeting04:29
*** tkay has joined #openstack-meeting04:29
*** jecarey has quit IRC04:30
*** Sukhdev has joined #openstack-meeting04:32
*** caleb_ has quit IRC04:38
*** thuc_ has quit IRC04:40
*** nati_ueno has joined #openstack-meeting04:40
*** thuc has joined #openstack-meeting04:41
*** bdpayne has joined #openstack-meeting04:41
*** thuc_ has joined #openstack-meeting04:45
*** thuc has quit IRC04:45
*** Linz has quit IRC04:46
*** Tross has joined #openstack-meeting04:47
*** alazarev has quit IRC04:48
*** fawadkhaliq has quit IRC04:54
*** tomoe_ has quit IRC04:54
*** tomoe_ has joined #openstack-meeting04:54
*** yamahata has quit IRC04:58
*** yamahata has joined #openstack-meeting04:58
*** tomoe_ has quit IRC04:59
*** yamahata has quit IRC04:59
*** yamahata has joined #openstack-meeting04:59
*** jimidar has quit IRC05:00
*** s3wong has joined #openstack-meeting05:00
*** ymht has joined #openstack-meeting05:00
yamahatahi05:01
*** _nadya_ has joined #openstack-meeting05:01
*** eghobo has joined #openstack-meeting05:01
yamahata#startmeeting neutron/servicevm05:02
openstackMeeting started Tue Mar 25 05:02:37 2014 UTC and is due to finish in 60 minutes.  The chair is yamahata. Information about MeetBot at http://wiki.debian.org/MeetBot.05:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:02
*** openstack changes topic to " (Meeting topic: neutron/servicevm)"05:02
openstackThe meeting name has been set to 'neutron_servicevm'05:02
yamahatahello. Does the new time slot work for you?05:03
*** thuc has joined #openstack-meeting05:03
s3wongI believe people from US East Coast made a comment on the ML05:03
yamahatavery sorry for those.05:04
*** masayukig has joined #openstack-meeting05:04
*** vkozhukalov has quit IRC05:05
yamahata#topic current-status05:05
*** openstack changes topic to "current-status (Meeting topic: neutron/servicevm)"05:05
*** stevemar has quit IRC05:05
yamahataI summarized blueprints, patches at the page05:06
yamahata#link https://wiki.openstack.org/wiki/Meetings/ServiceVM05:06
*** thuc_ has quit IRC05:06
yamahataNo patch was updated since the last week.05:06
s3wongyamahata: yes, I am still in the middle of reviewing the APIs; sorry for the delay05:07
*** tomoe_ has joined #openstack-meeting05:07
yamahatas3wong: no problem.05:07
yamahataany questions on design/patches?05:07
yamahataI'm going to update the patches this week or the next week.05:08
*** thuc has quit IRC05:08
yamahataIt will include drivers/guest agent for lbaas05:08
*** mdomsch has quit IRC05:09
s3wongyamahata: good - it is good to see a sample service using this framework05:09
yamahatas3wong: it just run haproxy in guest vm instead of namespace in network-node.05:10
yamahataopenstack RPC needs to be proxyied into tenant network from openstack management network05:10
*** dburmistrov has joined #openstack-meeting05:10
s3wongyamahata: is there going to be a pre-package image?05:11
yamahatas3wong: hopefully. I'm working on it right now.05:11
yamahataimage + devstack patch05:12
s3wongyamahata: interesting. LBaaS haproxy installation process was simply apt-get install haproxy on host OS05:12
s3wongso now for service VM, we need to specify the image location?05:13
yamahatas3wong: yes. At first we need register images as usual. And then register those ids for image to neutron.05:13
yamahataThe framework uses nova-client to boot VM with a given image05:14
*** matsuhashi has quit IRC05:14
*** vkozhukalov has joined #openstack-meeting05:15
s3wongyamahata: is the image id registeration to Neutron automatically or manual (by tenants?)?05:15
yamahataIn theory, same work flow can be applied for other service like router, firewall05:15
yamahatas3wong: It's manual at the moment.05:15
s3wongyamahata: OK05:16
yamahatas3wong: automation is desirable. But not sure it should be in this framework or by other external tool.05:17
*** tkay has quit IRC05:17
*** fifieldt_ has joined #openstack-meeting05:18
s3wongyamahata: sure, I am fine with it for initial implementation05:18
*** matsuhashi has joined #openstack-meeting05:18
yamahataany other questions?05:19
*** imsurit has quit IRC05:19
s3wongyamahata: will look into the code further05:19
yamahataI see.05:19
*** skraynev_afk is now known as skraynev05:19
yamahata#open discussion05:20
yamahataother subteam are concerned about servicevm. advanced-service-requirement and group-policy05:20
yamahataIt's important to cooperate with them05:21
*** gokrokve has joined #openstack-meeting05:21
s3wongyamahata: I am in both advanced-service and group-policy team - what is the primary concern you hear about?05:21
yamahatas3wong: nothing special at the moment.05:21
*** _nadya_ has quit IRC05:21
s3wongin group-policy we haven't really gotten into service yet05:21
yamahataUnfortunately I can't attend their IRC meeting due to its time slots.05:21
s3wongand in advanced service we had been discussing flavor and service context05:22
yamahataI'm following their discussion via logs.05:22
s3wongyamahata: I was going to say - even for a West coast person like me, it is now 10:22pm05:22
s3wongyamahata: so you may find it difficult for others in US to join this meeting actively05:22
yamahatas3wong: Right. such thing is inevitable.05:23
yamahataSo when there is a topic that is important for servicevm, please let me know. then I'll try to attend.05:24
s3wongyamahata: sure05:24
yamahataanother concern is router vm patch05:25
s3wongyamahata: please also let me know if there is anything you need from either group-policy side or advanced service side (which I would imagine you need things from advanced service side like service insertion via service context)05:25
yamahata#link https://blueprints.launchpad.net/neutron/+spec/cisco-config-agent05:25
yamahatas3wong: thanks, will do.05:25
*** gokrokve has quit IRC05:25
yamahata#link https://blueprints.launchpad.net/neutron/+spec/cisco-routing-service-vm05:26
yamahataTheir patches essentially do similar thing. So the patches(theirs and mine) should converge somehow05:26
yamahataat some point05:27
s3wongyamahata: do you plan to bundle L3 agent into a service VM too?05:27
yamahatas3wong: That's the plan05:27
*** emagana has joined #openstack-meeting05:27
yamahatas3wong: no, I mean lbaas-agent to bundle.05:27
*** tomoe_ has quit IRC05:28
yamahatas3wong: for l3-agent, it's another story.05:28
s3wongyamahata: yeah, who wants l3-agent :-)05:28
*** mihgen has joined #openstack-meeting05:29
yamahatas3wong: the planned image would include lbaas-agent with haproxy05:29
s3wongyamahata: makes sense05:29
yamahatahopefully some startup scripts.05:30
s3wongyamahata: yeah, if it is meant for haproxy only image, some components should be spawned either in inittab or one of the Sxx scripts05:31
*** IlyaE has joined #openstack-meeting05:31
yamahataokay. any topic to discuss?05:33
s3wongyamahata: I am good05:34
yamahatathanks. Since I plan to post new patches, let's have the meeting the next week.05:35
yamahata#endmeeting05:35
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"05:35
openstackMeeting ended Tue Mar 25 05:35:35 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:35
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_servicevm/2014/neutron_servicevm.2014-03-25-05.02.html05:35
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_servicevm/2014/neutron_servicevm.2014-03-25-05.02.txt05:35
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_servicevm/2014/neutron_servicevm.2014-03-25-05.02.log.html05:35
s3wongyamahata: thanks!05:36
*** Daisy_ has joined #openstack-meeting05:36
*** bdpayne has quit IRC05:36
*** dguitarbite has quit IRC05:37
*** Daisy_ has quit IRC05:37
*** fifieldt_ has quit IRC05:39
*** vkozhukalov has quit IRC05:39
*** dguitarbite has joined #openstack-meeting05:41
*** _nadya_ has joined #openstack-meeting05:41
*** alazarev has joined #openstack-meeting05:43
*** _nadya_ has quit IRC05:44
*** s3wong has quit IRC05:45
*** RobinJoe has quit IRC05:46
*** RobinJ has quit IRC05:46
*** RobinJoe has joined #openstack-meeting05:46
*** RobinJ has joined #openstack-meeting05:46
*** nati_ueno has quit IRC05:47
*** chandan_kumar has quit IRC05:48
*** epico_ has joined #openstack-meeting05:51
*** nati_ueno has joined #openstack-meeting05:51
*** sushils has joined #openstack-meeting05:53
*** fawadkhaliq has joined #openstack-meeting05:54
*** tomoe_ has joined #openstack-meeting05:55
*** nshaikh has joined #openstack-meeting05:58
*** otherwiseguy has quit IRC05:59
*** pradipta_away is now known as pradipta06:00
*** Sukhdev has quit IRC06:04
*** RobinJoe has quit IRC06:05
*** RobinJ has quit IRC06:05
*** tkay has joined #openstack-meeting06:08
*** mrda is now known as mrda_away06:08
*** sridhar has quit IRC06:11
*** doug_shelley66 has joined #openstack-meeting06:12
*** thuc has joined #openstack-meeting06:14
*** neelashah has quit IRC06:14
*** andreaf has joined #openstack-meeting06:14
*** alazarev has quit IRC06:14
*** ildikov_ has quit IRC06:15
*** mestery has quit IRC06:18
*** thuc has quit IRC06:19
*** nelsnelson has joined #openstack-meeting06:19
*** fawadkhaliq has quit IRC06:24
*** lukego has joined #openstack-meeting06:25
*** Mandell_ has joined #openstack-meeting06:28
*** Mandell has quit IRC06:28
*** ymht has quit IRC06:34
*** djoreilly has joined #openstack-meeting06:41
*** tkay has quit IRC06:44
*** eghobo has quit IRC06:46
*** Macaveli has joined #openstack-meeting06:48
*** Longgeek has quit IRC06:49
*** egallen has joined #openstack-meeting06:49
*** egallen has quit IRC06:51
*** Longgeek has joined #openstack-meeting06:55
*** sridhar has joined #openstack-meeting06:58
*** ildikov_ has joined #openstack-meeting06:59
*** ttrifonov_zZzz is now known as ttrifonov07:00
*** fifieldt_ has joined #openstack-meeting07:00
*** lsmola_ has quit IRC07:02
*** lsmola_ has joined #openstack-meeting07:02
*** vkozhukalov has joined #openstack-meeting07:03
*** eghobo has joined #openstack-meeting07:05
*** bogdando has quit IRC07:05
*** jlibosva has joined #openstack-meeting07:06
*** comay has joined #openstack-meeting07:07
*** andreaf has quit IRC07:08
*** Fdot has joined #openstack-meeting07:09
*** dburmistrov has quit IRC07:13
*** IlyaE has quit IRC07:14
*** sandywalsh has quit IRC07:16
*** epico_ has quit IRC07:16
*** ityaptin has quit IRC07:16
*** jtomasek has joined #openstack-meeting07:16
*** devlaps has quit IRC07:17
*** brucer has quit IRC07:21
*** gokrokve has joined #openstack-meeting07:21
*** Longgeek has quit IRC07:22
*** fifieldt_ has quit IRC07:24
*** gokrokve has quit IRC07:26
*** MaxV has joined #openstack-meeting07:28
*** belmoreira has joined #openstack-meeting07:29
*** saju_m has joined #openstack-meeting07:30
*** Longgeek has joined #openstack-meeting07:31
*** RobinJoe has joined #openstack-meeting07:32
*** RobinJ has joined #openstack-meeting07:32
*** epico_ has joined #openstack-meeting07:32
*** gibi has quit IRC07:33
*** RobinJ is now known as RobinJoe-away07:34
*** nati_ueno has quit IRC07:37
*** epico_ has quit IRC07:37
*** max_lobur has joined #openstack-meeting07:42
*** MaxV has quit IRC07:45
*** luqas has joined #openstack-meeting07:45
*** garyk has joined #openstack-meeting07:47
*** sushils has quit IRC07:48
*** ifarkas has joined #openstack-meeting07:48
*** amandeep has joined #openstack-meeting07:50
*** ttrifonov is now known as ttrifonov_zZzz07:50
*** amandeep is now known as Guest3220507:51
*** flaper87|afk is now known as flaper8707:51
*** Guest32205 is now known as jimidar07:53
*** ifarkas has left #openstack-meeting07:54
*** eghobo has quit IRC07:54
*** egallen has joined #openstack-meeting07:57
*** nwidell has joined #openstack-meeting08:02
*** bogdando has joined #openstack-meeting08:03
*** MaxV has joined #openstack-meeting08:03
*** che-arne has quit IRC08:04
*** MaxV has quit IRC08:07
*** jprovazn has joined #openstack-meeting08:10
*** ArthurBerezin has quit IRC08:15
*** egallen has quit IRC08:17
*** mihgen has quit IRC08:19
*** egallen has joined #openstack-meeting08:19
*** RobinJoe-away is now known as RobinJ08:21
*** RobinJoe has quit IRC08:22
*** RobinJ has quit IRC08:22
*** RobinJoe has joined #openstack-meeting08:22
*** RobinJ has joined #openstack-meeting08:22
*** jimidar has quit IRC08:23
*** jasondotstar has joined #openstack-meeting08:27
*** nwidell has quit IRC08:32
*** mrunge has joined #openstack-meeting08:32
*** d0ugal has joined #openstack-meeting08:34
*** jgallard has joined #openstack-meeting08:35
*** djoreilly has left #openstack-meeting08:35
*** RobinJ has quit IRC08:36
*** RobinJoe has quit IRC08:36
*** ttrifonov_zZzz is now known as ttrifonov08:37
*** ArthurBerezin has joined #openstack-meeting08:38
*** MaxV has joined #openstack-meeting08:42
*** matsuhashi has quit IRC08:49
*** saju_m has quit IRC08:50
*** nwidell has joined #openstack-meeting08:50
*** yassine has joined #openstack-meeting08:52
*** saju_m has joined #openstack-meeting08:52
*** andreaf has joined #openstack-meeting08:53
*** ArthurBerezin has left #openstack-meeting08:53
*** ygbo has joined #openstack-meeting08:55
*** nacim has joined #openstack-meeting08:55
*** phil__ has joined #openstack-meeting08:55
*** matsuhashi has joined #openstack-meeting08:56
*** jcoufal has joined #openstack-meeting08:57
*** afazekas has joined #openstack-meeting09:04
*** gokrokve has joined #openstack-meeting09:05
*** gokrokve has quit IRC09:05
*** gokrokve has joined #openstack-meeting09:05
*** sushils has joined #openstack-meeting09:08
*** rkukura has joined #openstack-meeting09:08
*** sbalukoff has joined #openstack-meeting09:12
*** chandan_kumar has joined #openstack-meeting09:13
*** matsuhashi has quit IRC09:14
*** safchain has joined #openstack-meeting09:15
*** derekh has joined #openstack-meeting09:15
*** matsuhashi has joined #openstack-meeting09:18
*** mkoderer has joined #openstack-meeting09:21
*** johnthetubaguy has joined #openstack-meeting09:21
*** pradipta is now known as pradipta_away09:24
*** tomoe_ has quit IRC09:24
*** pradipta_away is now known as pradipta09:24
*** luqas has quit IRC09:25
*** luqas has joined #openstack-meeting09:29
*** Longgeek has quit IRC09:29
*** ominakov has joined #openstack-meeting09:30
*** saju_m has quit IRC09:38
*** nosnos has quit IRC09:39
*** che-arne has joined #openstack-meeting09:41
*** rkukura has quit IRC09:41
*** Longgeek has joined #openstack-meeting09:43
*** henrynash has joined #openstack-meeting09:47
*** andreaf has quit IRC09:49
*** mrunge has quit IRC09:50
*** gongysh has quit IRC09:55
*** saju_m has joined #openstack-meeting09:57
*** max_lobur has quit IRC10:00
*** mrunge has joined #openstack-meeting10:04
*** mrunge has quit IRC10:04
*** mrunge has joined #openstack-meeting10:04
*** morganfainberg is now known as morganfainberg_Z10:05
*** zhikunliu has quit IRC10:05
*** matsuhashi has quit IRC10:08
*** dburmistrov_ has joined #openstack-meeting10:08
*** matsuhashi has joined #openstack-meeting10:10
*** doug_shelley66 has quit IRC10:11
*** doug_shelley66 has joined #openstack-meeting10:11
*** emagana has quit IRC10:13
*** salv-orlando has quit IRC10:14
*** overlayer has joined #openstack-meeting10:21
*** xuhanp has quit IRC10:23
*** overlayer has quit IRC10:26
*** overlayer has joined #openstack-meeting10:28
*** masayukig has quit IRC10:28
*** overlayer has quit IRC10:31
*** pradipta is now known as pradipta_away10:32
*** overlayer has joined #openstack-meeting10:32
*** brucer has joined #openstack-meeting10:34
*** markmcclain has joined #openstack-meeting10:39
*** emagana has joined #openstack-meeting10:44
*** weshay has joined #openstack-meeting10:47
*** jasondotstar has quit IRC10:47
*** andreaf has joined #openstack-meeting10:47
*** Jianyong has quit IRC10:49
*** Longgeek has quit IRC10:49
*** emagana has quit IRC10:52
*** max_lobur has joined #openstack-meeting10:52
*** epico has quit IRC10:52
*** max_lobur1 has joined #openstack-meeting10:53
*** doron_afk has joined #openstack-meeting10:54
*** max_lobur has quit IRC10:57
*** belmoreira has quit IRC11:00
*** mihgen has joined #openstack-meeting11:01
*** egallen has quit IRC11:05
*** saju_m has quit IRC11:07
*** saju_m has joined #openstack-meeting11:08
*** brucer has quit IRC11:08
*** saju_m has quit IRC11:09
*** Longgeek has joined #openstack-meeting11:12
*** mwagner_lap has quit IRC11:12
*** saju_m has joined #openstack-meeting11:15
*** xianghui has quit IRC11:20
*** rkukura has joined #openstack-meeting11:21
*** gokrokve has quit IRC11:23
*** jjmb1 has quit IRC11:24
*** miqui has joined #openstack-meeting11:26
*** tianst20 has joined #openstack-meeting11:31
*** doron_afk is now known as doron11:32
*** gokrokve has joined #openstack-meeting11:34
*** gokrokve_ has joined #openstack-meeting11:38
*** saju_m has quit IRC11:38
*** saju_m has joined #openstack-meeting11:38
*** Macaveli has quit IRC11:38
*** gokrokve has quit IRC11:39
*** MaxV has quit IRC11:41
*** gokrokve_ has quit IRC11:42
*** ArxCruz has joined #openstack-meeting11:48
*** nwidell has quit IRC11:50
*** belmoreira has joined #openstack-meeting11:51
*** jgallard has quit IRC11:51
*** MaxV has joined #openstack-meeting11:52
*** nwidell has joined #openstack-meeting11:54
*** dburmistrov_ has quit IRC11:55
*** belmoreira has quit IRC11:55
*** Macaveli has joined #openstack-meeting11:56
*** sandywalsh has joined #openstack-meeting11:57
*** eharney has quit IRC11:57
*** skraynev is now known as skraynev_afk12:01
*** sandywalsh has quit IRC12:01
*** baoli has joined #openstack-meeting12:02
*** ArthurBerezin1 has joined #openstack-meeting12:02
*** harlowja_away has quit IRC12:03
*** pdmars has joined #openstack-meeting12:03
*** ivasev has joined #openstack-meeting12:05
*** paragan has quit IRC12:05
*** jmh_ has joined #openstack-meeting12:07
*** ArthurBerezin1 has quit IRC12:07
*** ArthurBerezin has joined #openstack-meeting12:08
*** ArthurBerezin has quit IRC12:08
*** ArthurBerezin has joined #openstack-meeting12:08
*** gokrokve has joined #openstack-meeting12:10
*** dburmistrov_ has joined #openstack-meeting12:13
*** julim has joined #openstack-meeting12:13
*** ArthurBerezin has left #openstack-meeting12:16
*** matsuhashi has quit IRC12:16
*** dkranz has joined #openstack-meeting12:17
*** egallen has joined #openstack-meeting12:18
*** gokrokve has quit IRC12:19
*** jgallard has joined #openstack-meeting12:19
*** dburmistrov_ has quit IRC12:21
*** gokrokve has joined #openstack-meeting12:22
*** belmoreira has joined #openstack-meeting12:22
*** matsuhashi has joined #openstack-meeting12:23
*** david-lyle has quit IRC12:23
*** ashepelev has joined #openstack-meeting12:23
*** markmcclain has quit IRC12:24
*** markmcclain has joined #openstack-meeting12:24
*** markmcclain1 has joined #openstack-meeting12:25
*** imsurit has joined #openstack-meeting12:25
*** tomoe_ has joined #openstack-meeting12:26
*** yamahata has quit IRC12:27
*** markmcclain2 has joined #openstack-meeting12:27
*** markmcclain2 has quit IRC12:27
*** gokrokve has quit IRC12:28
*** dkranz has quit IRC12:28
*** markmcclain2 has joined #openstack-meeting12:28
*** dkranz has joined #openstack-meeting12:29
*** markmcclain has quit IRC12:29
*** markmcclain1 has quit IRC12:29
*** markmcclain2 has quit IRC12:30
*** aysyd has joined #openstack-meeting12:31
*** markmcclain has joined #openstack-meeting12:31
*** beagles has joined #openstack-meeting12:31
*** gokrokve has joined #openstack-meeting12:32
*** neelashah has joined #openstack-meeting12:32
*** nermina has joined #openstack-meeting12:33
*** rfolco has joined #openstack-meeting12:34
*** bgorski has joined #openstack-meeting12:34
*** zul has quit IRC12:38
*** ivasev has quit IRC12:39
*** zul has joined #openstack-meeting12:41
*** saju_m has quit IRC12:41
*** gokrokve has quit IRC12:43
*** gokrokve has joined #openstack-meeting12:43
*** mwagner_lap has joined #openstack-meeting12:46
*** lblanchard has joined #openstack-meeting12:46
*** gokrokve has quit IRC12:47
*** doug_shelley66 has quit IRC12:48
*** adalbas has joined #openstack-meeting12:48
*** marekd|away is now known as marekd12:52
*** mrodden has quit IRC12:52
*** mrodden has joined #openstack-meeting12:52
*** dims_ has quit IRC12:52
*** luqas has quit IRC12:52
*** jasondotstar has joined #openstack-meeting12:53
*** gokrokve has joined #openstack-meeting12:53
*** tomoe_ has quit IRC12:55
*** saju_m has joined #openstack-meeting12:55
*** tomoe_ has joined #openstack-meeting12:56
*** dguitarbite has quit IRC12:56
*** dguitarbite has joined #openstack-meeting12:56
*** thuc has joined #openstack-meeting12:57
*** julienvey has joined #openstack-meeting12:57
*** xuhanp has joined #openstack-meeting12:58
*** julienvey has quit IRC12:58
*** julienvey has joined #openstack-meeting12:58
*** thuc_ has joined #openstack-meeting12:58
*** saju_m has quit IRC12:59
*** dkranz has quit IRC12:59
*** pcm__ has joined #openstack-meeting13:00
*** saju_m has joined #openstack-meeting13:00
*** thuc has quit IRC13:01
*** rissmann1 has joined #openstack-meeting13:01
*** noslzzp has joined #openstack-meeting13:02
*** dims_ has joined #openstack-meeting13:02
*** dcramer_ has joined #openstack-meeting13:02
*** rissmann has quit IRC13:02
*** bashok has joined #openstack-meeting13:02
*** pcm__ has left #openstack-meeting13:02
*** jhenner1 has joined #openstack-meeting13:03
*** matsuhashi has quit IRC13:03
*** dprince has joined #openstack-meeting13:03
*** doron is now known as doron_afk13:04
*** jhenner has quit IRC13:04
*** rbowen has joined #openstack-meeting13:04
*** saju_m has quit IRC13:04
*** saju_m has joined #openstack-meeting13:05
*** ildikov_ has quit IRC13:06
*** erlon has joined #openstack-meeting13:06
*** bgorski has quit IRC13:07
*** thang_ has joined #openstack-meeting13:08
*** bknudson has joined #openstack-meeting13:09
*** saju_m has quit IRC13:09
*** DuncanT- has joined #openstack-meeting13:10
*** saju_m has joined #openstack-meeting13:11
*** doron_afk is now known as doron13:11
*** ildikov_ has joined #openstack-meeting13:13
*** julienvey has quit IRC13:16
*** spzala has joined #openstack-meeting13:16
*** ameade has joined #openstack-meeting13:18
*** nermina has quit IRC13:18
*** bgorski has joined #openstack-meeting13:19
*** pablosan_ is now known as pablosan13:20
openstackstatusNOTICE: the gerrit event stream is currently hung, blocking all testing. troubleshooting is in progress (next update at 14:00 utc)13:21
*** ChanServ changes topic to "the gerrit event stream is currently hung, blocking all testing. troubleshooting is in progress (next update at 14:00 utc)"13:21
*** dkranz has joined #openstack-meeting13:21
*** changbl has quit IRC13:22
*** eharney has joined #openstack-meeting13:23
*** mestery has joined #openstack-meeting13:28
*** mestery has quit IRC13:28
*** mestery has joined #openstack-meeting13:29
*** ChanServ changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:29
*** doug_shelley66 has joined #openstack-meeting13:30
*** banix has joined #openstack-meeting13:31
*** paragan has joined #openstack-meeting13:32
*** markmcclain has quit IRC13:34
*** doron is now known as doron_afk13:36
*** yamahata has joined #openstack-meeting13:38
*** nati_ueno has joined #openstack-meeting13:40
*** thuc_ has quit IRC13:41
*** luqas has joined #openstack-meeting13:42
*** thuc has joined #openstack-meeting13:42
*** ddutta has joined #openstack-meeting13:42
*** rakhmerov has joined #openstack-meeting13:46
*** thuc has quit IRC13:47
*** rissmann1 has quit IRC13:48
*** rissmann has joined #openstack-meeting13:50
*** shwetaap has joined #openstack-meeting13:50
*** radez_g0n3 is now known as radez13:51
*** jecarey has joined #openstack-meeting13:52
*** dcramer_ has quit IRC13:53
*** balajiiyer has joined #openstack-meeting13:54
*** dguitarbite has quit IRC13:54
*** ivasev has joined #openstack-meeting13:55
*** balajiiyer has left #openstack-meeting13:55
*** zns has joined #openstack-meeting13:57
*** colinmcnamara has joined #openstack-meeting13:58
*** nati_ueno has quit IRC13:59
*** tomoe_ has quit IRC14:00
*** aveiga has joined #openstack-meeting14:00
*** pcm__ has joined #openstack-meeting14:00
*** tomoe_ has joined #openstack-meeting14:00
*** caleb_ has joined #openstack-meeting14:00
sc68cal#startmeeting #neutron_ipv614:01
openstackMeeting started Tue Mar 25 14:01:21 2014 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: #neutron_ipv6)"14:01
openstackThe meeting name has been set to '_neutron_ipv6'14:01
sc68cal#endmeeting14:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:01
openstackMeeting ended Tue Mar 25 14:01:47 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/_neutron_ipv6/2014/_neutron_ipv6.2014-03-25-14.01.html14:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/_neutron_ipv6/2014/_neutron_ipv6.2014-03-25-14.01.txt14:01
openstackLog:            http://eavesdrop.openstack.org/meetings/_neutron_ipv6/2014/_neutron_ipv6.2014-03-25-14.01.log.html14:01
sc68calsorry, typo14:01
sc68cal#startmeeting neutron_ipv614:02
openstackMeeting started Tue Mar 25 14:02:03 2014 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.14:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
*** openstack changes topic to " (Meeting topic: neutron_ipv6)"14:02
openstackThe meeting name has been set to 'neutron_ipv6'14:02
*** nacim has quit IRC14:02
xuhanphello, sc68cal14:02
sc68calHello everyone14:02
aveigahello14:02
baoliHi14:02
*** yuyangbj has joined #openstack-meeting14:02
sc68calSo - we are currently nearing RC114:03
sc68calso current14:03
sc68calso currently most of the things getting merged are for existing bugs14:04
*** BrianB__ has joined #openstack-meeting14:04
xuhanpsc68cal, I think we need some core member's attention on those bugs :-)14:05
*** tomoe_ has quit IRC14:05
*** prad has joined #openstack-meeting14:05
*** MaxV has quit IRC14:05
sc68calxuhanp: agreed - I was hoping we could get your patch merged14:05
*** pfallenop has quit IRC14:05
sc68cal#link https://review.openstack.org/#/c/72252/2 Permit RAs from known routers14:06
*** MaxV has joined #openstack-meeting14:06
xuhanpsc68cal, I kind of worried comments will come late and then we won't have time to address them all.14:06
*** stevemar has joined #openstack-meeting14:06
xuhanpso should we send a email to ML to get them reviewed or just ping some core members on IRC?14:07
*** pfallenop has joined #openstack-meeting14:07
*** jhenner1 has quit IRC14:08
sc68calprobably ping on IRC14:08
*** jswarren has quit IRC14:08
xuhanpsc68cal, Ok. sound good14:08
sc68calI didn't get a chance to talk IPv6 at yesterday's main meeting, to bring it up14:08
*** vijendar has joined #openstack-meeting14:09
sc68calIn the meantime, if everyone could take a look at the review, that would be helpful14:10
sc68calxuhanp: I saw you got bit by a gate bug, we should probably do a recheck14:10
xuhanpsc68cal, yep. I am not sure why comment can try a new Jenkins job.14:11
xuhanps/try/trigger14:11
sc68calxuhanp: the Elastic Recheck comment has the format for triggering14:11
sc68cal"recheck bug 1288918"14:12
uvirtbotLaunchpad bug 1288918 in tempest "tempest.api.object_storage.test_account_quotas_negative.AccountQuotasNegativeTest:test_upload_large_object" [Low,Confirmed] https://launchpad.net/bugs/128891814:12
xuhanpyep. but there is no recheck between the two Jenkins especially when previous one was successful14:12
xuhanpanyway, I rechecked that bug again after the failure.14:13
*** prad has quit IRC14:14
sc68calok - just post a comment in your review to have it re-run jenkins14:14
sc68calthat -1 due to a gate bug is probably what is keeping core reviewers from looking at the patch14:14
xuhanpsc68cal, thanks14:14
sc68calDo we have any other reviews that are going to try and make RC1?14:15
*** prad has joined #openstack-meeting14:16
xuhanpsc68cal, I hope the fix which trigger provider rule when router update can be reviewed as well.14:16
xuhanp#link https://review.openstack.org/#/c/80932/14:16
*** whenry has joined #openstack-meeting14:18
sc68calperfect, I've added myself to that review14:18
*** rakhmerov has quit IRC14:20
sc68calxuhanp: for that review, a couple of the unit tests, for the plugins appear to have a lot in common14:20
sc68calcould they be folded into test_sg.SecurityGroupDBTestCase ?14:20
*** rakhmerov has joined #openstack-meeting14:20
sc68calor do they all have subtle differences?14:21
*** jasondotstar has quit IRC14:21
*** jhenner has joined #openstack-meeting14:21
xuhanpthe changed code is trigger from the different plugin14:21
*** rkukura has left #openstack-meeting14:22
xuhanptrying to open the link14:22
sc68calok - we can take it off line, I'll poke at it a bit14:23
xuhanpsc68cal, sure14:23
*** markvan has joined #openstack-meeting14:23
sc68calDo we have any new bugs or blueprints to discuss?14:24
*** mestery has quit IRC14:24
*** kevinconway has joined #openstack-meeting14:25
*** yuyangbj1 has joined #openstack-meeting14:25
sc68calok - i'll turn it over to open discussion if there are none14:25
sc68cal#topic open discussion14:26
*** openstack changes topic to "open discussion (Meeting topic: neutron_ipv6)"14:26
xuhanpI have a question about Shi Xiong's code change14:26
*** yuyangbj has quit IRC14:26
xuhanpactually two questions.14:26
xuhanp1. is dnsmasq for each subnet needed?14:27
xuhanpipv6 uses dnsmasq for each network I think14:27
*** bauzas has joined #openstack-meeting14:27
sc68calI think I saw a reviewer comment bringing up that point recently14:28
*** alexpilotti has quit IRC14:28
sc68calit doesn't look like shshang is here today14:29
xuhanpyep. we can discuss offline too.14:29
*** tomoe_ has joined #openstack-meeting14:29
sc68calIt may be worth discussing if it is able to be split into pieces14:30
*** colinmcnamara has quit IRC14:30
sc68cal40 reviwer comments on the most recent patch, in just one file. A bit overwhelming14:30
*** david-lyle has joined #openstack-meeting14:31
xuhanpsc68cal, yep. we may need to reply the comments before submit a new patch. otherwise people will feel like their comments are not addressed14:31
baolixuhanp, I did a little research on that. A broadcast to one qr-xxx port will be heard by all the VMs that are on different subnets from the same network, with the ovs plugin.14:31
*** alazarev has joined #openstack-meeting14:32
xuhanpbaoli, will that be a problem for current dhcp port?14:32
*** zoresvit has joined #openstack-meeting14:32
*** markmcclain has joined #openstack-meeting14:32
baoliso this relates to your question about one dnsmasq per qr-xxx port (or per subnet)14:33
*** mestery has joined #openstack-meeting14:33
*** markmcclain has joined #openstack-meeting14:33
xuhanpbaoli, yep. Got you about that. what about current IPv4 case?14:33
sc68calWe may need to determine if it is possible to have multiple subnets on the same network14:34
baoliThis also raises a question about multiple ipv6 subnets per network, what are the relationships between the subnets14:34
aveigatechnically, it should be possible to have multiple v6 subnets14:34
baoliwith ipv4, dnsmasq is running in the dhcp namespace, and no slaac!14:34
aveigayou should be able to receive multiple RAs and assign an addr per advertised scope14:35
xuhanpaveiga, you mean multiple addr on one interface, right?14:36
*** lukego has quit IRC14:36
aveigayes14:36
aveigathe problem would be showing neutron that you have multiple14:37
aveigacan the port show the extras?14:37
*** otherwiseguy has joined #openstack-meeting14:37
sc68calaveiga: yes14:37
aveigathen you should be fine14:37
sc68calIt already does for v4 + single v6 address14:37
aveigaright14:37
aveigasounds like it's just a matter of testing..14:37
sc68calbut we may need to tweak a bit for slaac calculations14:37
sc68calmake sue it calculates a EUI per subnet14:38
sc68cal*sure14:38
aveigayup14:38
xuhanpalso I guess we need to change the current logic when VM is assigned with subnet's IP.14:38
xuhanpI think neutron select one subnet as VM's IP14:39
xuhanpdifferent from nova-network14:39
xuhanpwhen --nic net-id= is not specified14:39
xuhanpto nova boot14:39
*** jswarren has joined #openstack-meeting14:39
xuhanpagain, this need testing14:40
*** dprince has quit IRC14:40
sc68calHenryG put together some tests in tempest for testing IPv6 subnets14:40
sc68calso - we may be able to put some tests into tempest for two v6 subnets on the same network14:40
sc68calsee what the current behavior is - and then push code to fix if needed14:41
xuhanpsc68cal, sounds great14:41
baolia VM receives one ip from each address family14:42
*** MaxV has quit IRC14:42
*** MaxV has joined #openstack-meeting14:42
*** rramirez has joined #openstack-meeting14:43
*** MaxV has quit IRC14:44
*** MaxV has joined #openstack-meeting14:44
*** jasondotstar has joined #openstack-meeting14:46
sc68calOk - if we don't have anything else to discuss - I can give everyone back 15 minutes14:47
*** armax has joined #openstack-meeting14:49
sc68calalright everyone - see you next week. I'm always on #openstack-neutron during US EST14:49
*** vhoward has joined #openstack-meeting14:49
*** mtanino has joined #openstack-meeting14:49
sc68cal#endmeeting14:49
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:49
openstackMeeting ended Tue Mar 25 14:49:52 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:49
baolisee you14:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-03-25-14.02.html14:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-03-25-14.02.txt14:49
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-03-25-14.02.log.html14:49
*** MaxV has quit IRC14:50
*** reed has joined #openstack-meeting14:51
*** MaxV has joined #openstack-meeting14:51
*** wwallnrr__ has joined #openstack-meeting14:52
*** dprince has joined #openstack-meeting14:53
*** terriyu has joined #openstack-meeting14:53
*** dcramer_ has joined #openstack-meeting14:54
*** thedodd has joined #openstack-meeting14:54
*** cjellick has quit IRC14:56
*** thuc_ has joined #openstack-meeting14:57
*** yuyangbj1 has left #openstack-meeting14:58
*** malini has joined #openstack-meeting14:58
*** malini has left #openstack-meeting14:58
*** bgorski has quit IRC14:59
n0ano#startmeeting gantt14:59
openstackMeeting started Tue Mar 25 14:59:19 2014 UTC and is due to finish in 60 minutes.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.14:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:59
*** openstack changes topic to " (Meeting topic: gantt)"14:59
openstackThe meeting name has been set to 'gantt'14:59
*** bgorski has joined #openstack-meeting14:59
*** sn0wb1rd has quit IRC14:59
n0anoanyone here to talk about the scheduler?14:59
*** kgriffs_afk is now known as kgriffs14:59
*** baoli has quit IRC14:59
*** IlyaE has joined #openstack-meeting15:00
*** matiu has quit IRC15:00
*** cath6184 has joined #openstack-meeting15:00
*** sn0wb1rd has joined #openstack-meeting15:00
bauzaso/15:01
*** max_lobur1 has left #openstack-meeting15:01
*** MaxV has quit IRC15:01
*** MaxV has joined #openstack-meeting15:01
bauzasnot a lot of people around :)15:02
*** toan_tran has joined #openstack-meeting15:02
n0anobauzas, might be just you & me, looks like you wore them out last week :-)15:02
bauzas:-)15:02
*** carl_baldwin has joined #openstack-meeting15:02
bauzasn0ano: have you read the minutes ?15:03
*** zoresvit has quit IRC15:03
*** luqas has quit IRC15:03
*** toan_tran has quit IRC15:03
*** aveiga has left #openstack-meeting15:03
*** aveiga has quit IRC15:03
bauzasI promise I haven't scared them :D15:03
n0anoyeah, last week, I've forgotten (incipient Alzheimer's) were there any open questions?15:03
*** primeministerp has joined #openstack-meeting15:04
n0anoone question I had, looks like you abandoned the client patch just to restart it again, any particular reason for not just updating the original patch?15:04
*** devlaps has joined #openstack-meeting15:04
bauzasno no no15:04
bauzasI'm still continuing to work on the client15:05
bauzasbut after discussing with -infra guys, seems like drafts don't like rebases15:05
*** baoli has joined #openstack-meeting15:05
bauzashence I created another patch15:05
bauzasWIP this time15:05
*** eharney has quit IRC15:05
*** ygbo has quit IRC15:06
n0anowell, if that's just a process thing that's fine15:06
bauzasbecause I was unable to amend the existing one (gerrit was refusing to update master)15:06
bauzasthe bp whiteboard is modified accordingly15:06
bauzasI removed all mentions of the previous patch15:06
*** digambar has joined #openstack-meeting15:07
n0anoAah, gerrit, it's caused me pain in the past, I understand completely (I had a linked set of patches and gerrit lost the links, I was not happy :-(15:07
bauzasyey15:07
bauzaswas pretty weird15:07
bauzaswell, to be honest, anteaya told me to stop submitting drafts15:07
*** toan_tran has joined #openstack-meeting15:07
bauzasthat works, but that doesn't like rebases15:08
bauzasanyway15:08
*** adalbas has quit IRC15:08
bauzasmaybe we can officially start ? :)15:08
bauzasand discuss about the topics ?15:08
n0anothe other thing you can do is create private update and send links out to interested parties, that would avoid some of those issues15:08
n0anofor sure but with just the two of us it's pretty easy...15:08
anteayan0ano: outside the meeting if you continue to have difficulty with gerrit, talk to me in -infra15:09
bauzasjust a matter of reading minutes without looking at the detailed logs :)15:09
anteayagerrit should be losing links15:09
anteayashouldn't15:09
n0anoanteaya, tnx, I'll remember that in future, I worked around the problem and hope not to run into it again15:09
*** nacim has joined #openstack-meeting15:09
anteayan0ano: it might be a workflow issue15:10
n0anoanteaya, I always suspect cockpit error, I have a slightly strange setup so I blame me on first look15:10
digambarHey guys, one question, if need to sask omething on the node so which node we follow for daily issues ??15:10
*** spzala has quit IRC15:10
bauzasdigambar: I don't understand the question :)15:11
n0anobauzas, +115:11
*** ygbo has joined #openstack-meeting15:11
digambarif need to ask osmething on the node so which node we follow for daily issues ??15:11
bauzasn0ano: so, about scheduler forklift15:11
digambarsomething**15:11
bauzasdigambar: still unclear to me, the question is :)15:11
n0anodigambar, what do you mean by node and what do you mean by daily issues?15:12
bauzasdigambar: what do you mean about node ?15:12
anteayan0ano: this is our recommended workflow: https://wiki.openstack.org/wiki/Gerrit_Workflow15:12
bauzas^^15:12
bauzashttps://review.openstack.org/#/c/82778/15:12
n0anoanteaya, I tried to follow that but I'm guessing I messed up (I had a linked set of patches so that's a little odd)15:12
bauzasscheduler client patch15:12
bauzasstill chasing some bugs15:13
*** saju_m has quit IRC15:13
*** spzala has joined #openstack-meeting15:13
anteayan0ano: find me in -infra later and we can walk through it together15:13
digambarIf I want to ask to something about the patches & bugs, so where I can connect you guys15:13
bauzasdigambar: you can reach us in #openstack-nova just by prefixing your question with our IRC nicknames :)15:14
n0anodigambar, I think you mean `contact you guys' and the first option is the dev mailing list, that should be your first choice15:14
digambaryes15:14
bauzasdigambar: I don't promise to be 24x7 up there thou15:14
digambarYeah, I understand15:14
n0anoI'm always on #openstack-dev but I'll add #openstack-nova also15:14
bauzasI also proposed a bp in nova-specs :15:15
digambarcool, Thank you :)15:15
n0anothe not there 24x7 is why I always suggest the mailing list first15:15
bauzashttps://review.openstack.org/#/c/82133/15:15
n0anoanyway15:15
n0ano#topic code forklist15:15
*** openstack changes topic to "code forklist (Meeting topic: gantt)"15:15
bauzasyey  !15:15
bauzasso, I was saying15:15
bauzasgood progress on it, still chasing bugs15:15
*** johnthetubaguy has quit IRC15:15
*** johnthetubaguy has joined #openstack-meeting15:16
n0anoI was going to ask, do you want a review or do you want to wait until after the bug hunt?15:16
bauzasn0ano: I think it's worth waiting for the new patchset15:16
bauzasn0ano: not that hard to fix15:16
n0anoNP, procrastination is my middle name15:16
bauzas:-)15:17
*** ddutta has quit IRC15:17
n0anogiven this is still a WIP I assume that, even after the bug hunt, this won't be ready to merge in yet, right?15:17
bauzasso, again, please note that https://review.openstack.org/#/c/82778/ is the new review for the sched client15:17
bauzasn0ano: we can't15:17
*** spzala has quit IRC15:17
bauzasuntil Juno15:17
*** pcm__ has quit IRC15:18
bauzaswe're currently in FF15:18
bauzasthe idea is to quickly raise the bar on the client for discussing it at the summit15:18
n0anothat's a given but after FF will this be ready, you still need some unit tests right?15:18
*** alazarev has quit IRC15:18
bauzasn0ano: yup15:18
*** luis_fdez has joined #openstack-meeting15:19
bauzaswe also need to have the bp validated15:19
bauzashttps://review.openstack.org/#/c/8213315:19
bauzasyou can review that one now15:19
n0anosure, I'll add that to my todo right now15:19
bauzasit's flagged as WIP too because of the the current nova-specs template under change15:20
*** whenry has quit IRC15:20
*** tianst has joined #openstack-meeting15:20
*** jjmb has joined #openstack-meeting15:20
bauzasI have to check status of it, and either promote it or produce a new patchset15:20
*** garyk has quit IRC15:20
*** changbl has joined #openstack-meeting15:20
*** xuhanp has quit IRC15:21
*** eharney has joined #openstack-meeting15:21
bauzasbtw, I spoke last week about http://summit.openstack.org/cfp/details/8015:21
toan_tranbauzas: just one quick question15:21
bauzasthis is the placeholder for discussing the BP15:21
bauzastoan_tran: sure15:21
digambarHey bauzas15:22
toan_tranwhat relation does this sch python lib have  with nova?15:22
digambarfor the scheduler lib, can help you on that ?15:22
bauzastoan_tran: that's the necessary step before forking code to gantt15:22
bauzasdigambar: I need some reviews on it yes15:23
digambaryes15:23
bauzasdigambar: but I don't think it requires another contributor15:23
digambarok15:23
n0anobauzas, we should probably propose a session to talk about gantt APIs also, I think that's another area people need to address15:23
bauzasthat's quite straightforward15:23
digambarany other work for gantt,  I can look at ?15:23
digambar1. I'll review it15:24
*** noslzzp has quit IRC15:24
digambar2. I am looking for ??15:24
*** noslzzp has joined #openstack-meeting15:24
bauzasn0ano: which APIs are you talking about ?15:24
*** mestery has quit IRC15:24
bauzasREST or RPC ?15:24
toan_trandigambar: try https://etherpad.openstack.org/p/icehouse-external-scheduler15:24
digambarok15:24
toan_trandigambar: a little messy, but look at the end15:25
bauzasbut indeed, we need to speak about step #315:25
digambarokay15:25
n0anobauzas, both, the RPC should just be a continuation of the current Nova ones but, for generalizing to support cinder & neutron & ... we should see if we need something more15:25
bauzasn0ano: that's something we need to tackle at the summit yes15:25
bauzasn0ano: I can propose a session15:26
n0anobauzas, if you want, go ahead15:26
bauzasok will do15:26
bauzasthat's because we need to make sure what will be the interfaces in the next future15:26
n0anoI don't think we need a session on forklift per se, it's pretty obvious what needs to be done there, it's more mechanical15:26
*** vkmc has joined #openstack-meeting15:26
*** vkmc has quit IRC15:26
*** vkmc has joined #openstack-meeting15:26
toan_trann0ano: can we organise some section with cinder & neutron folks?15:27
bauzasn0ano: well, the client lib is quite straightforward, I agree15:27
bauzastoan_tran: I don't think that's mature for Juno15:27
bauzasbut we can get feedback15:27
toan_tranbauzas: well, it's better if we have some initial though on that15:27
n0anotoan_tran, I would hope that some of the the cinder & neutron people would come to the gantt session15:28
bauzastoan_tran: I still persist that's a bit early :)15:28
*** Macaveli has quit IRC15:28
toan_tranI don't want we follow it to the end and others'd say that it's too complicated for them15:28
bauzasJuno will be focused on having the scheduler isolated from Nova15:28
*** cjellick has joined #openstack-meeting15:28
bauzasthat's K where we should focus on integrating other projects15:28
n0anobauzas, a bit but getting other ideas early would be good, especially when talking about APIs15:28
*** neelashah1 has joined #openstack-meeting15:29
toan_tranbauzas: of'course but to tackle RPC15:29
*** jmontemayor has joined #openstack-meeting15:29
toan_tranI'm afraid that we focus too much into nova15:29
bauzasso that means the discussion is about the interfaces15:29
toan_tranat some point we forget the generalization of gantt15:29
*** neelashah has quit IRC15:29
bauzashence what we discussed previously :)15:29
bauzasI will propose a session wide enough to get cinder and neutron folks joining in15:30
toan_tranbauzas: +115:30
n0anobauzas, +115:30
bauzasok15:30
n0anowe seem to be in violent agreement :-)15:30
bauzasabout the forklift by itself, there are some concerns about the service table and other pure technical aspects15:30
bauzasthat's only related to nova15:31
n0anoI think those will resolve themselves, once we get the interfaces clean enough that we can split out the current code15:31
bauzasthat's why I think the forklift is not that trivial to miss a summit session15:31
*** otherwiseguy has quit IRC15:32
n0anonot sure what concensus we need on it though, it's more a `just do it' problem.15:32
bauzasn0ano: we need to decouple DB tables that are not related to scheduler15:33
n0anobut why argue over this, let's just propose a forklist session and see if it's accepted and who comes15:33
bauzasn0ano: +1 :)15:33
bauzasok, I'm done with that topic15:33
n0anosince you've signed up for 2 sessions, I'll propose a forklift one15:33
*** Duane has joined #openstack-meeting15:33
*** dcramer_ has quit IRC15:34
bauzasthere is already one ;)15:34
bauzashttp://summit.openstack.org/cfp/details/8015:34
n0anoI'm constantly out of the loop (Alzheimers again), that's fine15:34
bauzasthe one missing is the one about future Gantt interfaces15:34
n0anobauzas, BTW the Juno summit is in Atlanta, will you be able to come?15:35
bauzasn0ano: yup15:35
n0anoexcellent15:35
bauzasn0ano: I'm moving from one company to another15:35
bauzasn0ano: and the move will be done at summit time15:36
*** jjmb has quit IRC15:36
bauzasanyway15:36
n0anoanyway15:36
bauzas:-)15:36
n0anoI think we've beaten this particular dead horse15:36
n0ano#opens15:36
bauzasnah15:36
bauzasnah15:36
bauzasno-db :)15:36
bauzasI have something to say :D15:37
n0ano#topic no-db15:37
*** openstack changes topic to "no-db (Meeting topic: gantt)"15:37
n0anobauzas, go for it15:37
*** ayoung has quit IRC15:37
bauzasso, about no-db, I spoke with boris-4215:37
bauzasthis morning15:37
bauzas(well, this EU TZ morning :-) )15:37
bauzasso, he will propose a session on no-db scheduler15:38
*** colinmcnamara has joined #openstack-meeting15:38
bauzaswe discussed on that thread last week15:38
*** emagana has joined #openstack-meeting15:38
bauzasabout the interest of having memcached or tooz15:38
*** feleouet has quit IRC15:38
*** Leonr has joined #openstack-meeting15:38
bauzasso, there will be opportunity for discussing about the implementation15:39
n0anonever heard of tooz, I would have thought we just do memcached to start and then think about alternatives if needed15:39
toan_trann0ano: +115:39
*** nshaikh has quit IRC15:40
bauzasat the moment, there is no progress on the BP, as the resource was defocused from that BP15:40
bauzasn0ano: that's what we agreed last week :-)15:40
n0anoI just wanted to see progress, with patches up for review I hate to see them just get ignored15:41
bauzasbut that's worth discussing with tooz contributors15:41
n0anoso, bottom line, don't expect any progress on no-db until after the summit15:42
bauzasn0ano: I don't think there will be progress until Juno15:42
bauzas+115:42
*** krtaylor has quit IRC15:42
toan_tranbauzas: last time I heard15:42
toan_tranthere was a prob with no-db implementation15:42
toan_trandid he said what it was?15:43
bauzastoan_tran: the only problem I heard of from boris-42 is resource :)15:43
toan_tranit's the design problem or just implementation's technical detail ?15:43
n0anotoan_tran, scalability issue, they were working on debugging it, looks like they don't have to resources to fix it right nwo15:43
bauzastoan_tran: there is no people working on atm15:43
bauzasn0ano: +115:43
toan_tranok15:44
bauzashence the discussion is about the memcached use15:44
bauzaswe should have a flexible backend15:44
*** rossella_ has quit IRC15:44
*** alexpilotti has joined #openstack-meeting15:44
bauzaswith use of stevedore's plugins for implementation15:44
bauzasso that we could either use a memcached driver or any other15:45
bauzashence the discussion around tooz15:45
*** rossella_ has joined #openstack-meeting15:45
n0anobauzas, no argument, which is why I'd implement memcached first and then look into other backends15:45
bauzashttps://github.com/stackforge/tooz15:45
bauzasn0ano: that would be worth having a stevedore namespace for this15:45
bauzaswith proper interfaces15:45
*** bashok has quit IRC15:45
bauzasthe few I saw from the bp was ok with that15:46
bauzasbut we just need to make sure it will still be the case in the next implementations15:46
n0anowell, there'll be a session at Juno, should be a lively one15:46
*** alexpilotti has quit IRC15:46
*** markwash has joined #openstack-meeting15:46
bauzas:D15:47
n0anoanything else on no-db15:47
bauzasnope15:47
n0anoOK, once more15:47
n0ano#topic opens15:47
*** openstack changes topic to "opens (Meeting topic: gantt)"15:47
bauzas:-)15:47
toan_tranI have some question :)15:47
*** SumitNaiksatam has quit IRC15:47
n0anoanything new?15:47
n0anotoan_tran, go for it15:47
toan_tranhas anyone ever measured the scheduling performance?15:47
bauzasyeah, I have a remark about the current gantt repo15:47
bauzastoan_tran: ask boris-4215:48
bauzastoan_tran: they made some benchs using Rally15:48
*** ayoung has joined #openstack-meeting15:48
toan_tranwell, they promised to have data published  :)15:48
toan_tranbut I haven't seen one :)15:48
bauzasopen a thread in -dev ML then :)15:49
*** tanisdl has joined #openstack-meeting15:49
toan_tranbauzas: +115:49
n0anotoan_tran, check out https://docs.google.com/document/d/1_DRv7it_mwalEZzLy5WO92TJcummpmWL4NWsWf0UWiQ/edit?pli=1#heading=h.6ixj0ctv4rwu15:49
*** krtaylor has joined #openstack-meeting15:50
toan_tranit does not have data15:50
bauzasn0ano: great document, missed it, thanks15:50
n0anotoan_tran, what about fig. 1?15:50
toan_trann0ano: only on compute_get_all()15:51
*** thuc_ has quit IRC15:51
bauzascould we tackle that on -dev ?15:51
*** luqas has joined #openstack-meeting15:51
toan_tranbauzas: OK15:51
bauzasI have something to discuss about gantt repo15:51
n0anothen, as bauzas said, raise it on -dev (be sure to CC boris)15:51
n0anobauzas, go for it15:51
*** thuc has joined #openstack-meeting15:51
bauzasok, at the moment, the gantt repo is a bit confusing people15:52
bauzasas it was generated a while ago15:52
*** eghobo has joined #openstack-meeting15:52
bauzasand as the efforts are now going to nova first15:52
*** eghobo has quit IRC15:52
bauzasI'm just saying that I think we should update the README file in gantt stating that this is currently not an official repo, much likely related to a sandbox15:53
*** eghobo has joined #openstack-meeting15:53
bauzasI can propose a patch on it15:53
bauzasand we also need to review the reviewers :D15:53
*** vhoward has left #openstack-meeting15:53
n0anobauzas, sure, that's a good idea15:53
*** ttrifonov is now known as ttrifonov_zZzz15:53
bauzasrussellb raised that concern earlier in the day15:53
n0anocurrent reviewers are the nova core team, it's easy enough to create our own team, we should probably discuss that at Juno15:54
*** jergerber has joined #openstack-meeting15:54
bauzas(11:06:52) russellb: i'm not sure if it can actually be removed, but at a minimum, we can push a commit that removes all code and leaves a README15:54
russellbo/15:54
bauzasrussellb: o/15:55
russellbbasically just wondering what you guys want to do with the repo15:55
n0anoI'm not sure we want to go that far, just changing the README would be my suggestiuon15:55
bauzasrussellb: we're quickly discussing on the gantt repo state15:55
russellbis there active work on the code?15:55
*** ominakov has quit IRC15:55
n0anoI'm still working on it15:55
*** ominakov has joined #openstack-meeting15:55
bauzasbtw, should we move it to stackforge ?15:55
*** ashepelev has quit IRC15:55
*** thuc has quit IRC15:56
russellbi asked about the stackforge move, -infra folks generally against it if there's any chance we'll move it back later15:56
*** rramirez has quit IRC15:56
bauzasrussellb: ok thanks for the heads-up15:56
russellbi don't think nova-core is looking at it15:56
*** amotoki_ has joined #openstack-meeting15:56
n0anowe'd definitely move it back so I'm good with leaving it15:56
*** Linz has joined #openstack-meeting15:57
bauzasn0ano: russellb: so I will propose a patch for updating README and stating this is not active code15:57
*** Linz has quit IRC15:57
russellbso if it stays we should just change the review team15:57
bauzasrussellb: +115:57
russellbotherwise nothing will ever get approved15:57
russellbheh15:57
*** nwidell has quit IRC15:57
*** Linz has joined #openstack-meeting15:57
*** elo1 has joined #openstack-meeting15:57
n0anothen we should change the review team `before` we change the README15:57
bauzasn0ano: agreed15:57
russellbnot sure the order matters15:58
russellbbut sure15:58
bauzaswe're running out of time15:58
n0anoWe need to identify the review team, I'll start a ML thread15:58
n0anofor today, yes, we'll have to continue on the ML15:58
bauzasok15:58
n0anotnx everyone15:58
n0ano#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
openstackMeeting ended Tue Mar 25 15:59:01 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-03-25-14.59.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-03-25-14.59.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-03-25-14.59.log.html15:59
bauzasthanks :)15:59
*** lcheng_ has joined #openstack-meeting15:59
*** mestery has joined #openstack-meeting15:59
*** Sukhdev has joined #openstack-meeting16:02
*** dcramer_ has joined #openstack-meeting16:02
*** SumitNaiksatam has joined #openstack-meeting16:04
*** Sukhdev has quit IRC16:06
*** baoli has quit IRC16:08
*** mestery has quit IRC16:09
*** marcoemorais has joined #openstack-meeting16:09
*** SumitNaiksatam has quit IRC16:10
*** mestery has joined #openstack-meeting16:10
*** hemna_ has joined #openstack-meeting16:10
*** SumitNaiksatam has joined #openstack-meeting16:10
*** baoli has joined #openstack-meeting16:10
*** ArthurBerezin has joined #openstack-meeting16:12
*** colinmcnamara has quit IRC16:13
*** skraynev_afk is now known as skraynev16:14
*** troytoman-away is now known as troytoman16:15
*** tianst has quit IRC16:15
*** nati_ueno has joined #openstack-meeting16:17
*** troytoman is now known as troytoman-away16:17
*** troytoman-away is now known as troytoman16:19
*** atiwari has joined #openstack-meeting16:20
*** markwash has quit IRC16:20
*** mihgen has quit IRC16:21
*** alazarev has joined #openstack-meeting16:21
*** ArthurBerezin has left #openstack-meeting16:21
*** dkranz has quit IRC16:22
*** vkozhukalov has quit IRC16:23
*** markwash has joined #openstack-meeting16:23
*** zoresvit has joined #openstack-meeting16:24
*** doron_afk is now known as doron16:25
*** belmoreira has quit IRC16:25
*** thuc has joined #openstack-meeting16:25
*** thuc has quit IRC16:26
*** doron is now known as doron_afk16:26
*** Duane has quit IRC16:26
*** thuc has joined #openstack-meeting16:26
*** Duane has joined #openstack-meeting16:27
*** andreaf has quit IRC16:27
*** dburmistrov has joined #openstack-meeting16:28
*** n0ano has quit IRC16:29
*** nati_ueno has quit IRC16:30
*** Duane_ has joined #openstack-meeting16:30
*** troytoman is now known as troytoman-away16:30
*** Duane has quit IRC16:31
*** n0ano has joined #openstack-meeting16:32
*** zoresvit has quit IRC16:34
*** dkranz has joined #openstack-meeting16:35
*** Longgeek has quit IRC16:35
*** rramirez has joined #openstack-meeting16:35
*** alazarev has quit IRC16:35
*** Longgeek has joined #openstack-meeting16:35
*** tomoe_ has quit IRC16:38
*** adalbas has joined #openstack-meeting16:38
*** bauzas has quit IRC16:40
*** Longgeek has quit IRC16:42
*** Shaan7 has quit IRC16:44
*** Shaan7 has joined #openstack-meeting16:44
*** alazarev has joined #openstack-meeting16:48
*** msdubov has joined #openstack-meeting16:48
*** markwash_ has joined #openstack-meeting16:48
*** markwash has quit IRC16:49
*** markwash_ is now known as markwash16:49
*** ivar-lazzaro has quit IRC16:50
*** jpeeler has joined #openstack-meeting16:52
*** jpeeler has quit IRC16:52
*** jpeeler has joined #openstack-meeting16:52
*** rmoe has joined #openstack-meeting16:53
*** vkmc has quit IRC16:55
*** rossella_s has joined #openstack-meeting16:55
*** mattgriffin has joined #openstack-meeting16:55
*** topol has joined #openstack-meeting16:57
*** garyk has joined #openstack-meeting16:58
*** toan_tran has quit IRC16:59
*** IYozhikov_away is now known as IgorYozhikov16:59
*** jcoufal has quit IRC17:00
*** olkonami has joined #openstack-meeting17:00
*** s3wong has joined #openstack-meeting17:00
*** paragan has quit IRC17:00
*** markmcclain1 has joined #openstack-meeting17:01
*** lukego has joined #openstack-meeting17:01
*** tomoe_ has joined #openstack-meeting17:01
*** markmcclain1 has joined #openstack-meeting17:02
*** markmcclain has quit IRC17:02
*** nati_ueno has joined #openstack-meeting17:02
*** tkay has joined #openstack-meeting17:03
*** harlowja has joined #openstack-meeting17:03
*** mspreitz has joined #openstack-meeting17:03
*** rossella_ has quit IRC17:04
*** morganfainberg_Z is now known as morganfainberg17:04
*** colinmcnamara has joined #openstack-meeting17:06
*** rossk has joined #openstack-meeting17:07
*** patelna has joined #openstack-meeting17:08
*** balajiiyer has joined #openstack-meeting17:09
*** dcramer_ has quit IRC17:09
*** kgriffs is now known as kgriffs_afk17:10
*** manishg has joined #openstack-meeting17:10
*** safchain has quit IRC17:11
*** nermina has joined #openstack-meeting17:11
*** beagles is now known as beagles_brb17:12
*** arnaud has joined #openstack-meeting17:13
*** balajiiyer has quit IRC17:13
*** digambar has quit IRC17:13
*** arnaud has quit IRC17:14
*** s3wong has quit IRC17:15
*** ygbo has quit IRC17:15
*** nacim has quit IRC17:15
*** arnaud has joined #openstack-meeting17:15
*** balajiiyer has joined #openstack-meeting17:19
*** Fdot has quit IRC17:20
*** MaxV has quit IRC17:20
*** zns has quit IRC17:21
*** mspreitz has quit IRC17:23
*** bdpayne has joined #openstack-meeting17:23
*** andreaf has joined #openstack-meeting17:25
*** balajiiyer has left #openstack-meeting17:29
*** phil__ has quit IRC17:29
*** balajiiyer has joined #openstack-meeting17:29
*** amotoki_ has quit IRC17:29
*** salv-orlando has joined #openstack-meeting17:30
*** skraynev is now known as skraynev_afk17:32
*** jprovazn has quit IRC17:32
*** gyee has joined #openstack-meeting17:32
*** zns has joined #openstack-meeting17:35
*** Sukhdev has joined #openstack-meeting17:35
*** tomoe_ has quit IRC17:35
*** troytoman-away is now known as troytoman17:36
*** markmcclain1 has quit IRC17:36
*** imsurit has quit IRC17:39
*** comay has quit IRC17:39
*** flaper87 is now known as flaper87|afk17:41
*** mrunge has quit IRC17:41
*** fmarco76 has joined #openstack-meeting17:42
*** mspreitz has joined #openstack-meeting17:44
*** markmcclain has joined #openstack-meeting17:46
*** SumitNaiksatam has quit IRC17:47
*** epim has joined #openstack-meeting17:48
*** mestery_ has joined #openstack-meeting17:48
*** mestery has quit IRC17:48
*** lbragstad has joined #openstack-meeting17:48
*** mspreitz_ has joined #openstack-meeting17:48
*** amcrn has joined #openstack-meeting17:49
*** mspreitz_ has left #openstack-meeting17:49
*** SumitNaiksatam has joined #openstack-meeting17:50
*** mspreitz has left #openstack-meeting17:50
*** mestery_ is now known as mestery17:50
*** dcramer_ has joined #openstack-meeting17:51
*** nermina has quit IRC17:52
*** lcheng_ has quit IRC17:53
*** comay has joined #openstack-meeting17:54
*** mrunge has joined #openstack-meeting17:55
*** derekh has quit IRC17:55
*** rbowen has left #openstack-meeting17:55
*** jgallard has quit IRC17:56
*** markmcclain has quit IRC17:58
*** mspreitz has joined #openstack-meeting17:58
*** changbl has quit IRC18:00
*** thedodd has quit IRC18:00
dolphmayoung, bknudson, dstanek, jamielennox, morganfainberg, stevemar, gyee, henrynash, topol, marekd, lbragstad, joesavak, shardy, fabiog, fmarco76: ping!18:00
lbragstadhey18:01
bknudsondolphm: hi18:01
gyee\o18:01
henrynashhi18:01
fmarco76hi18:01
dolphm#link https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting18:01
ayoung  \m/_ (>.<) _\m/18:01
topolo/18:01
marekdo/18:01
*** colinmcnamara has quit IRC18:01
dolphmtopol: we're now caught up to your future timezone savings time18:01
*** balajiiyer has left #openstack-meeting18:01
ayoungLets get this party started18:02
*** dstanek has joined #openstack-meeting18:02
stevemaro/18:02
*** eguz has joined #openstack-meeting18:02
*** kgriffs_afk is now known as kgriffs18:02
dstanekhi18:02
dolphm#startmeeting keystone18:02
openstackMeeting started Tue Mar 25 18:02:53 2014 UTC and is due to finish in 60 minutes.  The chair is dolphm. 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: keystone)"18:02
openstackThe meeting name has been set to 'keystone'18:02
*** cath6184 has left #openstack-meeting18:03
dolphm#topic Reminder: Design summit session proposals open until April 20th18:03
*** openstack changes topic to "Reminder: Design summit session proposals open until April 20th (Meeting topic: keystone)"18:03
*** jamielennox has joined #openstack-meeting18:03
dolphmi saw that david chadwick had a request on list for the summit - anyone know if that was captured on summit.openstack.org as well?18:03
*** beagles_brb is now known as beagles18:03
marekdayoung: told him to do so.18:03
marekdayoung told him to do so.*18:04
stevemardolphm, i think he's just interested in adding on to federation, my topic should cover it 'future enhancements to federation'18:04
ayoungdolphm, what he wants to discuss is in stevemar 's session anyways18:04
dolphmmarekd: awesome, thanks - i haven't caught up on the mailing list recently18:04
dolphmayoung: cool18:04
stevemarayoung, thanks for that reply btw18:04
ayoungNP18:04
lbragstad#link http://summit.openstack.org/cfp/details/7218:04
dolphmstevemar: s/future enhancements// # it's the design summit, anything else would be rejected :P18:05
*** dkranz has quit IRC18:05
dolphm#topic icehouse-rc118:05
*** openstack changes topic to "icehouse-rc1 (Meeting topic: keystone)"18:05
* dolphm CONGRATS EVERYONE18:05
dolphmour list of release blockers is clear as of this morning:18:05
dolphm#link https://launchpad.net/keystone/+milestone/icehouse-rc118:05
*** eghobo has quit IRC18:05
stevemarnice18:06
dolphmif anyone has any release-critical issues that need to be addressed, target them to icehouse-rc1, stab me, and wave lots of flags18:06
dolphmotherwise, we should be cutting RC1 tomorrow morning18:06
*** saurabhs1 has joined #openstack-meeting18:06
bknudsonwhen does juno get cut?18:06
bknudsoni mean when is juno open18:06
dolphmbknudson: opened?18:06
dolphmbknudson: as soon as we have a milestone-proposed branch for icehouse (which RC1 is created from)18:07
*** brich1 has joined #openstack-meeting18:07
dolphmso, tomorrow hopefully18:07
dolphmand on a related note...18:07
dolphm#topic keystoneclient v0.7.0 release18:07
*** openstack changes topic to "keystoneclient v0.7.0 release (Meeting topic: keystone)"18:07
morganfainbergo/18:08
dolphmi'm aiming to release keystoneclient 0.7.0 tomorrow morning, along with RC1 (by coincidence)18:08
gyeew00t!18:08
morganfainbergwhoopse :P18:08
*** troytoman is now known as troytoman-away18:08
dolphmwe have a wishlist of reviews on the meeting agenda that we wanted to see merged prior to stamping out 0.7.018:08
*** banix has quit IRC18:08
dolphmas of now, they're all approved except for a couple nice-to-haves18:08
dolphm#link https://review.openstack.org/#/c/82527/18:09
dolphm#link https://review.openstack.org/#/c/82886/18:09
ayoungI really wanted to get compressed tokens in there but getting shut down by Python33 issues18:09
jamielennoxthough if anyone is looking there are always a bunch of nice to haves up for review18:09
ayoungregion API is a nice to have18:09
dolphmayoung: ack, we'll open juno with a 0.8.0 then :)18:09
dolphmjamielennox: feel free to extend the list on the meeting agenda with your top picks18:10
*** _nadya_ has joined #openstack-meeting18:10
ayoungrevoke events needs to be resynced as well18:10
dolphmi need to clean up the 0.7.0 block list on LP as well, and push things to 0.7.1 / 0.8.0 as appropriate18:10
*** vkozhukalov has joined #openstack-meeting18:10
jamielennoxcool, i've still got a lot of general client reviews open so if people can spend some time on them this week that would be appreciated as i know we'll all want to get back to server when juno opens18:10
morganfainbergjamielennox, on my list of things to do since we're looking good on RC18:11
dolphmmorganfainberg: ++ everyone should do the same this week18:11
ayoungdolphm, On the client side,  I'd be interested in people's opions about including the examples scripts such as : https://review.openstack.org/#/c/82687/18:11
ayoungstevemar was working on some oauth ones, and I am doing the same with revocation events18:11
jamielennoxexcellent, i'm around now so ping me with any questions18:11
bknudsonI'd be interested in feedback on not using md5 -- https://review.openstack.org/#/c/80398/18:11
dolphmayoung: i'd love to have smaller snippets in docs, like a tutorial18:12
*** emagana has quit IRC18:12
dolphmayoung: a bunch of big scripts require maintenance, etc18:12
ayoungbknudson, looking18:12
*** emagana has joined #openstack-meeting18:12
morganfainbergdolphm, ++18:12
*** banix has joined #openstack-meeting18:12
bknudsonayoung: after our discussion on irc I changed the server to return the hash algorithm18:13
gyeedolphm, ayoung, is this different from keystone/tools/sample_data.sh?18:13
morganfainbergayoung, i think there is def. value to have the examples, but we should probably either gate on them working or make it docs18:13
gyeeI mean use case18:13
morganfainbergbknudson, i like moving to a better algorithm18:13
ayounggyee, I think it is the same use case18:13
morganfainbergayoung, gating on the scripts working would be my preference if we're including them as good examples.18:14
bknudsonthere are some security standards don't allow md518:14
ayoungbknudson, I'll have to go through the patch in depth, but it looks right on a quick glance18:14
gyeebknudson, there are some don't even allow sha1 :)18:14
jamielennoxbknudson: so is the server returning the algorithm or is it being set by config? i prefer the server set method18:14
bknudsonayoung: yes, please look closely!18:14
*** sushils has quit IRC18:14
bknudsonjamielennox: the server is returning the algorithm in the revocation list18:15
dolphmbknudson: that seems hacky :(18:15
morganfainbergdolphm, the server should specify the algorithm to the client18:15
bknudsondolphm: which is hacky? server includes algorithm or config setting?18:15
morganfainbergdolphm, not just a config that needs to be in sync18:16
dolphmmorganfainberg: as part of the revocation list?18:16
jamielennoxbknudson: so do we need the CONF.hash_algorithm?18:16
morganfainbergdolphm, probably. it's a clear indication of what we used18:16
bknudsonthe algorithm also applies to the tokens.18:16
gyeebknudson, I am fine with baking the info into meta data18:16
morganfainbergdolphm, there is prior art (look at passwords in ldap, {SSHA}<password>18:16
dstanekwhy does the algorithm matter in the revocation list? aren't we just comparing the token we have to the list of revoked tokens?18:16
morganfainbergdolphm, it clearly identifies what the client should expect.18:16
bknudsonnot just the tokens in the revocation list... I mean the cached tokens.18:16
dolphmmorganfainberg: ack, it's the same challenge with compressed tokens18:16
ayoungdolphm, it is not hacky, it is essential.18:16
jamielennoxdolphm: no i think it is better that we have it in the response than to keep the value in sync in CONF on client/server18:17
morganfainbergdolphm, ++ yep and the same argument18:17
bknudsondstanek: the revocation list contains token hashes18:17
ayoungthe MD5 Hash algorithm was based on an assumption that both side used it.  Making it explicit is correct, and it needs to be driven by the server18:17
dolphmi'm more concerned about which response the data is being crammed into, and what that affects18:17
dolphmor is intended to affect18:17
dstanekbknudson: ah i see, and i'm assuming we do that because it's shorter18:18
bknudsonI've got to admit I like the config option, it was simple to implement.18:18
bknudsondstanek: the token hash is a lot shorter than the PKI token!18:18
lbragstad++18:18
morganfainbergdstanek, yeah less data to transit usign the hashes18:18
*** jasondotstar has quit IRC18:18
*** imsurit has joined #openstack-meeting18:18
dolphmbknudson: the challenge of distributing configuration is a larger problem than just old pki vs new pki or md5 vs sha118:19
dolphmthere was a proposal a summit or two ago about a centralized configuration service for things like this18:19
*** dkranz has joined #openstack-meeting18:19
jamielennoxbknudson: the first use of conf._hash_algorithm there is just for caching purposes - we don't necessarily need that to be the same as the revocation list algorithm18:19
dolphmyou could GET a configuration on startup, and then listen on the message bus for changes in real time, etc18:19
*** changbl has joined #openstack-meeting18:19
bknudsonyou can store config in our policy backend.18:20
*** _nadya_ has quit IRC18:20
morganfainbergdolphm, being explicit about this stuff to the client also means that non-auth_token clients could understand it18:20
gyeemorganfainberg, fine point18:20
gyeetake x.509 certs for example, signing and hash algorithm are part of the cert18:20
dolphmmorganfainberg: yeah, i like that for sure18:20
jamielennoxdolphm: i always liked that idea but last time i tried it people suggested sticking with puppet etc18:20
dolphmis the next default algorithm sha1?18:21
morganfainbergdolphm, in cases like the compressed tokens, the TRL, etc, we should make it not auth_token specific (we control auth_token so we can do cool things with it, but being open to other tools is better)18:21
*** jasondotstar has joined #openstack-meeting18:21
dolphmjamielennox: the proposal i saw was to complement puppet/etc, not replace them18:21
brich1dolphm, sha256 is a more durable choice than sha118:21
dolphmbrich1: of course, but it might not be the best choice today18:22
morganfainbergbrich1, i would argue sha1 is sufficient in most cases, but as long as we allow for sha256 (limit data transit where possible unless more durable is needed)18:22
bknudsonafter the comments I got on the keystoneclient hashing, you can use any hash algorithm that hashlib supports18:22
gyeemorganfainberg, your customers, whom had to deal with industry compliance, will tell you what is sufficient and what's not18:22
bknudsonhash_ = hashlib.new(mode) -- where mode is the config option (or hash algorithm from revocation list)18:23
dolphmbrich1: and sha512 is more durable than sha256 :)18:23
gyeewe don't often get to decide unfortunately18:23
morganfainberggyee, and the default should be best general use-case18:23
morganfainberggyee, as long as the better options are easily supportable, i see no issues18:23
*** rramirez has quit IRC18:23
gyeemorganfainberg, sure, pick a reason default and allow it to be configurable18:23
morganfainberggyee, many deployments don't need the overhead of sha25618:23
gyeereasonable18:23
dolphmmorganfainberg: ++18:23
morganfainberggyee, so i'd say sha1, and we can evaluate the default each release :)18:23
gyeethat's what bknudson's patch is all about18:24
brich1dolphm, sha256 is already required by NIST (as of end of 2013), so US federal customers would be happier with that canonical choice18:24
morganfainbergbut i would like to see MD5 no longer be the default w/ bknudson's patch going live.18:24
ayoungI think bknudson 's approach is correct.   Lets give it asolid review after the meeting.  Shall we move on?18:24
brich1morganfainberg, agree that md5 is history18:24
dolphmayoung: ++18:24
bknudsonthanks!18:24
ayoungmorganfainberg, md5 dies in Juno18:24
dolphm#topic API/Compatibility expectations for auth_token middleware18:25
*** openstack changes topic to "API/Compatibility expectations for auth_token middleware (Meeting topic: keystone)"18:25
morganfainbergayoung, +++++++++++18:25
dolphm#link https://review.openstack.org/#/c/77748/18:25
dolphm(not sure who put this on the agenda? dstanek?)18:25
jamielennoxso this came out of a public variable change in the above link18:25
jamielennoxme18:25
*** shakamunyi has joined #openstack-meeting18:25
*** shakamunyi has quit IRC18:25
dstanekjamielennox probably18:25
morganfainbergis this the auth_token doesn't have a stable interface?18:25
morganfainbergconvo18:25
dolphmgyee: just saw your comment - that's the first time i've heard of anyone extending auth_token at all18:25
morganfainbergerm public18:25
jamielennoxdo we care about people subclassing auth_token middleware and keeping a stable interface for them?18:25
dolphmmorganfainberg: yes18:25
ayoungI think that one is safe18:26
*** shakamunyi has joined #openstack-meeting18:26
jamielennoxmy impression has always been no18:26
*** shakamunyi has quit IRC18:26
jamielennoxso long as we maintain the config options and the ENV variables we set the actual implementation of the middleware was fair game18:26
ayoungauth_token should not have a stable interface, as it is a wsgi pipeline component18:26
morganfainbergI feel like we should break up auth_token into comething more consumable18:26
jamielennoxbut i realize i've never had that clarified18:26
morganfainbergbut the middleware should be a blackbox18:26
*** mrunge has quit IRC18:26
ayoungI guess in theory we could be breaking someone that extends it18:26
gyeeayoung, meh :)18:26
dolphmmy suggestion to solve this particular review is to add a @property def request_uri that logs a warning to use self.identity_uri instead18:26
bknudsonif we're going to have a documented interface then split that out and have keystone auth_token implement it18:26
jamielennoxayoung: in theory yes - i don't know anoyone who does18:26
gyeethat's fine, a small change anyway18:27
dstanekyeah, we would be :-)18:27
dolphmmorganfainberg: ++ delete most of it and replace it with the regular client!18:27
jamielennoxdolphm: yea this one is easy, it's the principal i'm wondering about18:27
morganfainberggyee, that would let you pull in the bits you need and extend, but not be restricted to what the internals look like18:27
morganfainbergdolphm, :)18:27
dolphmjamielennox: ++18:27
gyeemorganfainberg, ++18:27
ayoungjamielennox, I think we have to draw the line somewhere.  Internal variables are probably it.  But then again, last time I decided something like this I made thingy at Dreamhost sad.18:27
dstaneki brought it up in the review because i didn't know if a policy existed for kc api compat18:27
gyeelets tag the public interfaces18:27
morganfainberggyee, __call__18:27
jamielennoxdolphm: right - i would like to rip auth_token apart and if i'm stuck with a public interface that's going to get way more difficult18:27
morganfainberggyee, the rest are private18:27
morganfainberg:P18:27
morganfainbergjamielennox, this should be something communicated to the community (not that i think anyone would really have an issue with it)18:28
gyeemorganfainberg, sure, add _ in front of them18:29
morganfainbergjamielennox, just so we're not ripping the carpet out from under anyone18:29
*** ildikov_ has quit IRC18:29
morganfainbergjamielennox, but i would like to claim auth_token doesn't have a public interface18:29
*** ominakov has quit IRC18:29
jamielennoxgyee: right, i don't mind going through auth_token and making the whole thing private18:29
*** doron_afk has quit IRC18:29
jamielennoxmorganfainberg: i agree18:29
dolphmthe only public interface i've ever considered auth_token to have is A) X-Auth-Token, B) all the environment headers passed down to the consuming service18:30
morganfainbergdolphm, ++18:30
dolphmand that's fairly well documented in the module's docstr18:30
ayoungdolphm, ++18:30
dolphmif you're going to start replacing parts of the internals of the module, i'm not sure it's in the community's best interest to support you18:30
ayoungdolphm, unless "you" is jamielennox of course18:31
bknudsonand X-Storage-Token18:31
dolphmbknudson: ++18:31
morganfainberglets aim for 0.8 release to switch the interfaces to _ prefixed and communicate this change to the community18:31
jamielennoxmorganfainberg: ++ works for me18:32
morganfainbergand clarify the documents as well18:32
morganfainbergif someone balks we can work with them to address the concerns18:32
dolphmif we find as result that it's common to extend parts of auth_token with alternative behaviors, we can take a more conservative approach moving forward18:32
jamielennoxmorganfainberg: as far as i can see there is nothing on auth_token that would be public18:32
morganfainbergdolphm, ++18:32
bknudsonwhat would people want to override in auth_token?18:33
morganfainbergbknudson, no clue. i don't see a point to it18:33
bknudsonnew headers?18:33
jamielennoxbknudson: i've never heard of it in practice18:33
dolphmgyee: ?18:33
gyeebknudson, ssl auth18:33
*** zoresvit has joined #openstack-meeting18:33
*** yassine has quit IRC18:33
*** manishg_ has joined #openstack-meeting18:33
gyeewe don't use username/password for the admin token18:33
morganfainberggyee, that seems like something that can be addressed with auth_plugin magic18:34
gyeewe override it to use 2-way ssl18:34
dolphmgyee: is that not relevant to contribute back to the community?18:34
bknudsonthat's a good one... different methods of getting username.18:34
morganfainberggyee, and contributable back up18:34
gyeedolphm, yes, I am trying to contribute it back18:34
dolphmgyee: in that case, you can contribute it back and we can maintain it for you :) no public interface required18:34
dstanekauth_token is just a way for applications to talk to keystone so i would imagine that there are deployments with special needs there18:34
jamielennoxgyee: that will be fixed with client + auth plugins + the loading from conf stuff18:34
ayounggyee, ssl auth should be in conjunction auth auth_token.  Not to replace it.18:34
gyeedolphm, absolutely!18:34
*** cath6184 has joined #openstack-meeting18:35
gyeeayoung, its the same user18:35
ayoungauth_token should be seen as authorization, where as SSL is authentication18:35
gyeewhy go through two stage auth18:35
*** cath6184 has quit IRC18:35
ayoungcert auth should only be used for Keystone itself18:35
*** alazarev has quit IRC18:35
morganfainberggyee, this really isn't different than how we handle external auth in keystone.18:35
dstanekmy thought is that we should have have an explicit policy or name varibles using _ (Python convention) to make this a non-issue18:36
*** johnthetubaguy has quit IRC18:36
dolphmayoung: it's never made much sense to me to require auth_token to have much in the way of authorization on keystone -- it should only be reading from keystone18:36
*** cath6184 has joined #openstack-meeting18:36
ayoungdolphm, ++18:36
dolphmdstanek: ++18:36
morganfainbergdstanek, i think we're getting better about that18:36
morganfainbergdstanek, but total agreement ++18:36
gyeemorganfainberg, we don't want to request a token and then use the it to validate other tokens18:36
morganfainberggyee, no meant functionally18:36
ayounggyee, right.  Agreed.  100 cement.18:36
morganfainberggyee, just where the type of check is done.18:36
*** manishg has quit IRC18:37
*** manishg_ is now known as manishg18:37
morganfainberggyee, it is a similar method, just in auth_token vs keystone :) [impl is obv different]18:37
dolphmalrighty, moving on...18:37
dolphm#topic Remove Eventlet + new non-httpd wsgi18:37
*** openstack changes topic to "Remove Eventlet + new non-httpd wsgi (Meeting topic: keystone)"18:37
dolphmmorganfainberg: o/18:37
morganfainbergSo had a chat w/ -infra18:37
*** alazarev has joined #openstack-meeting18:37
morganfainbergi was told to consider eventlet dead for py3318:37
morganfainbergthey specifically were asking if we were going to remove eventlet dep or remove py33 check job18:38
dstanekyay18:38
bknudsonevery other project is also dropping eventlet?18:38
morganfainbergso, the general answer is we should move to wsgiref for basic standalong18:38
morganfainbergand trollius for async/eventet/coroutine work18:38
morganfainbergbknudson, ideally trollius / tulip is the way forward18:38
dolphmtrollius in 2.7 == tullip in 3.2 == asyncio in 3.3 (did i get that right?)18:38
morganfainbergdolphm, trollius should work for all three afaik18:39
bknudsonwhat about 2.6?18:39
gyee++ with dropping eventlet18:39
*** yassine has joined #openstack-meeting18:39
morganfainbergbknudson, trollius = py2 i think18:39
dolphmhttps://pypi.python.org/pypi/trollius Trollius works on Python 2.6-3.4.18:39
morganfainbergbut in keystone we don't use eventlet (really)18:39
gyeeactually, ++++++++++++++++++++++++++++++++++++++++++++18:39
dolphmquote unquote18:39
dolphmmorganfainberg: so we should *really* get rid of the dep lol18:39
morganfainbergdolphm, ++18:39
morganfainbergwsgiref is there for a reason18:40
dstanekon that note i have been working on a review based on bknudson's finding - to make our py33 build work18:40
morganfainbergboth trollius and wsgiref are in the global reqs18:40
*** venkatesh has joined #openstack-meeting18:40
dstanekwon't trollius change the application design to be more callback based?18:40
bknudsonseems like an easy change early in juno is stop using eventlet & don't worry about the async18:40
*** mspreitz has left #openstack-meeting18:40
*** cath6184 has quit IRC18:40
morganfainbergdstanek, sure, but we don't use the coroutine-like stuff in eventlet18:41
*** cath6184 has joined #openstack-meeting18:41
bknudsonI don't think the monkeypatching got us much anyways since it'd block on sql18:41
ayoung2.6 can die, I think18:41
jamielennoxi like the dropping of eventlet, lets leave trollius alone until there is more consensus on how to use it18:41
ayoung2.6 was needed for RHEL6, but I think with collections we can get away from that.18:41
morganfainbergthe basic premise is either remove eventlet or remove py33 check for keystone in the near-term18:41
morganfainbergbut we can drop eventlet from keystone if we use a different wsgi impl18:42
bknudsonLet's drop the py33 check for stable/icehouse18:42
ayoungApache HTTPD18:42
dstanekwhat about our use of subprocess?18:42
morganfainbergbknudson, no question for I, this is for Juno18:42
*** bdpayne has quit IRC18:42
ayoungdstanek, we'd need a trollius compatable hach18:42
ayounghack18:42
*** cath6184 has quit IRC18:42
dolphmbknudson: stable won't have it, i don't think18:42
morganfainbergdolphm, ++ stable shouldn't18:42
*** cath6184 has joined #openstack-meeting18:42
dolphmit would be non-voting anyway, which is pointless18:42
bknudsondstanek: what's wrong with the use of subprocess?18:43
jamielennoxdstanek: i don't think that pyopenssl has the CMS stuff we need does it?18:43
*** cath6184 has quit IRC18:43
dstanekmorganfainberg: in the patch i'm working on we would not need to drop eventlet - certain tests would not run until it was dropped though18:43
dolphmthere's also pycrypto18:44
*** cath6184 has joined #openstack-meeting18:44
jamielennoxdstanek: i'm longer term hoping that python cryptography will be the way we do that in a library but it will be a while18:44
*** overlayer has quit IRC18:44
dstanekjamielennox: not as far as i know18:44
jamielennoxdolphm: i don't think pycrypto does cms, but could be wrong18:44
*** devlaps1 has joined #openstack-meeting18:44
ayoungdoesn't yet18:44
morganfainbergdstanek, it is still a requirements, if it18:44
dstanekbknudson: we use eventlet's patching so that we don't block on subprocess calls (or at least as much)18:44
morganfainberg's in requirements it would fail check18:44
ayoung#link https://www.dlitz.net/software/pycrypto/api/current/18:44
morganfainbergdstanek, because eventlet can't be installed in py3318:45
dolphmas far as i could tell one of either pycrypto or pyopenssl did everything we needed it to, but choked when it came to the arbitrary string manipulation we were doing in the middle18:45
jamielennoxayoung: yep that's what i though pycrypto never really dealt with certs18:45
dstanekmorganfainberg: it won't be in the requirements :-) bknudson found a neat trick that oslo seems to be using18:45
ayoungonly signature it does is  PKCS#1  which is not CMS18:45
*** cath6184_ has joined #openstack-meeting18:45
*** alazarev has quit IRC18:45
bknudsonwithout trollius we'll block on subprocess calls. I assume that we'll have figured out what will work for us by end of juno18:45
*** mattgriffin has quit IRC18:45
morganfainbergdstanek, i look forward to seeing it, but i'm skeptical of it not being in requirements18:45
morganfainbergdstanek, i think that is going to cause us issues w/ deployments unless we really drop the dep on eventlet18:46
ayoungbknudson, Apache HTTPD preform blocking on subprocess calls is OK18:46
*** egallen has quit IRC18:46
dstanekbknudson: i don't think tollius help us there which i why i brought it up; it would be nice to just get rid of them anyway18:46
bknudsonayoung: but it forks a few keystones?18:46
*** devlaps has quit IRC18:46
dolphmayoung: the choice to use CMS is fairly arbitrary right? why not use something that is built into a popular python package?18:46
ayoungNo18:46
ayoungCMS is the closest thing to a standard signature algorithm there is18:47
jamielennoxdolphm: not really - and there isn't much else18:47
*** crc32 has joined #openstack-meeting18:47
dolphmPKCS1 v1.5? RSA + SHA1 signatures18:48
gyeeCMS is not an algorithm, it is a spec18:48
dolphmgyee: correct18:48
ayoungOK...I promise to do a blog post enumerating all of the details around CMS.18:48
*** cath6184 has quit IRC18:48
*** thuc has quit IRC18:48
gyeein theory, you can sign anything in any format, just may not be *standard*18:48
dolphmor it's a different arbitrary "standard"18:48
ayoungPKCS1 is not a very well supported approach.  I was surprised to see it in pycrypto18:48
*** thuc has joined #openstack-meeting18:49
ayoungCMS is S/MIME and pretty much the widest deployed signature approach18:49
morganfainbergi know, lets make our own new standard... everyone will switch to it..because..... /xkcd18:49
gyeesigning basically means, 1) canonicalized the data, 2) hash, 3) encrypt with private key18:49
dolphmayoung: do you have any data to back that up with regard to consumers that we care about?18:49
ayoungPKCS #7  Is a standard.18:49
*** dcramer_ has quit IRC18:50
*** kgriffs is now known as kgriffs_afk18:50
gyeexkcd ftw! :D18:50
*** _nadya_ has joined #openstack-meeting18:50
ayoungdolphm, PKCS1 is not a signature standard per-se, it is well: http://en.wikipedia.org/wiki/PKCS_118:50
*** shakayumi has joined #openstack-meeting18:50
*** shakayumi has quit IRC18:50
dstanekwhat system besides keystone (including kc middlware) cares about the encryption spec?18:51
jamielennoxi never reallised that pycrypto had pkcs118:51
*** thuc has quit IRC18:51
*** thuc_ has joined #openstack-meeting18:51
ayounghttp://en.wikipedia.org/wiki/S/MIME18:51
jamielennoxgiven that we don't embed the certificates in the token it really is no different18:51
morganfainbergdstanek, this is the open standard argument i just made18:51
dolphmdstanek: ++18:51
*** shakayumi has joined #openstack-meeting18:51
morganfainbergdstanek, for hashing algorithm18:51
bknudsonkeystone cms isn't really standard either? it strips off the header/footer -- http://git.openstack.org/cgit/openstack/python-keystoneclient/tree/keystoneclient/common/cms.py#n14418:51
morganfainbergdstanek, we want to be as open to not using "our method" as possible.18:51
ayoungdstanek, yeah...we have end users that kinds of care about this stuff18:51
dstanekmorganfainberg: but tokens are opaque and only keystone needs to know their details right?18:51
morganfainbergdstanek, auth_token needs to know it18:52
morganfainbergdstanek, and if auth_token needs to, non-keystoneclient tools might18:52
dolphmayoung: as far as i can tell, you're obfuscating their interests rather than advocating for them18:52
gyeedstanek, java clients need to understand it too18:52
ayoungbknudson, I could probably make due with straight RSA calls instead of using the CMS call.18:52
gyeeso yeah, guys like jcloud may want us to use a standard approach18:52
*** novas0x2a|laptop has joined #openstack-meeting18:52
dolphmgyee: http://stackoverflow.com/questions/7611383/generating-rsa-keys-in-pkcs1-format-in-java18:53
ayoungonce we start talking compressed tokens...18:53
morganfainbergayoung, moving to straight RSA calls might be a good alternative18:53
ayoungactually, there is more than just that18:53
ayoungthere is the format of the Data, including where to find the certificate sin side18:53
dstanekgyee: that may be a good cenversation to start having then - to see what they really need/want18:53
jamielennoxayoung: well it means that we loose the CA18:53
jamielennoxwhich given the distribution method may be a problem18:53
ayoungyep18:53
jamielennoxmay = will18:53
ayoungno, we want to stay with CMS as the basic format18:54
ayoungdrop the custom base64 butchery18:54
morganfainbergayoung, ++18:54
jamielennoxayoung: ++18:54
ayoungbut we need to be able to tell "who signed this" from the doc itself18:54
jamielennoxayoung: straight to DER and then base64 it ourself18:54
ayoungjamielennox, with a little zlib in between18:55
gyeethen what are we gaining from this?18:55
ayounghttps://review.openstack.org/#/c/71181/24/keystoneclient/common/cms.py18:55
dolphmayoung: the choice to use CMS is still undefended and arbitrary18:55
dstanekif we are stuck with cms then someone should dust off their C skills!18:55
morganfainbergdolphm, lets use gpg and expect to interact with the gpg binary18:55
ayoungdolphm, its like democracy.  The worst option except for all the rest18:55
morganfainbergdstanek, M2Crypto yo! i mean...18:55
gyeedstanek, extra $$ on the consulting side :)18:55
jamielennoxi dont see CMS as a problem other than python crypto libraries are crap18:56
gyeem2crypto!18:56
morganfainbergcan we have a new lib: YUNoCrypto18:56
*** nermina has joined #openstack-meeting18:56
ayoungdstanek, I actually have enlisted jdennis as the python-nss maintainer to get better CMS support there18:56
dstanekgyee: you're welcome to it18:56
dolphmif you use m2crypto and pyopenssl and pycrypto together then you get security++18:56
ayoungpython-cms?  python-smime?18:56
morganfainbergayoung, probably a good idea, smime18:57
*** cath6184_ has left #openstack-meeting18:57
gyeedolphm, security++++18:57
dolphmjamielennox: and unfortunately our primary consumers are in python18:57
dolphmjamielennox: making the arbitrary choice rather poor18:57
morganfainbergayoung, don't like python-cms, it's not really descriptive of waht you're doing, cms is the standard smime is the impl18:57
ayoungdolphm, the Python crypto story is not clear at this point18:57
dstanekpython-cms would be too confusing - not another content management system!18:57
*** doug_shelley66 has quit IRC18:57
morganfainbergdstanek, ++18:58
ayoung++  python-smime then18:58
morganfainbergayoung, i18:58
gyeek man, this thing is getting out of hand18:58
dolphmayoung: the python crypto story is that i can't validate tokens in the client due to a lack of library support for the arbitrary choice in standards18:58
*** doug_shelley66 has joined #openstack-meeting18:58
morganfainbergve been meaning to dust off c/c++18:58
*** mdurnosvistov_ has joined #openstack-meeting18:58
ayoungdolphm, its worse than that18:58
*** zhiyan is now known as zhiyan_18:58
dolphmayoung: but that part is quite clear18:58
* dolphm 2 min18:58
ayoungand the choice was not aribitrary.  It is PKCS 718:58
morganfainbergayoung, maybe we should roll python-smime as under stackforge and get it published18:58
*** che-arne has quit IRC18:59
jamielennoxayoung: i would prefer that to be in python cryptography - they'll get there18:59
ayoungThat is the only "signing" standard I know of18:59
ayoungjamielennox, ++18:59
*** derekh has joined #openstack-meeting18:59
gyeeayoung, lets start issuing x.509 certs instead of tokens18:59
*** _nadya_ has quit IRC18:59
ayounggyee, no18:59
dolphmayoung: why not?18:59
ayoungthey serve different needs18:59
ayoungcerts are authN  tokens AuthZ18:59
dolphmyeah, you still need authz18:59
*** thedodd has joined #openstack-meeting18:59
dolphmtime!18:59
morganfainbergjamielennox, the question is, would it be easier to publish a lib and then get it superseded by pycrypto or aim to get it in pycrypto to begin with18:59
ayoungthere are X509 stnadards for it, but they are no better supported19:00
ayoungSAML would make more sense19:00
morganfainbergjamielennox, my guess is the former19:00
*** jlibosva has quit IRC19:00
*** Duane_ has quit IRC19:00
morganfainberganyway.19:00
morganfainbergmore to discuss19:00
*** nermina has left #openstack-meeting19:00
* dolphm back to #openstack-keystone!19:00
dolphm#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
jamielennoxmorganfainberg: the question is does it matter when we call still subprocess out?19:00
openstackMeeting ended Tue Mar 25 19:00:26 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-03-25-18.02.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-03-25-18.02.txt19:00
gyeelunch time19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-03-25-18.02.log.html19:00
*** fmarco76 has left #openstack-meeting19:00
*** dstanek has left #openstack-meeting19:00
jeblairhello infra folks?19:00
fungihey-o19:00
SergeyLukjanovo/19:00
*** bgorski has quit IRC19:00
*** Duane has joined #openstack-meeting19:00
clarkbhi there19:00
*** brich1 has quit IRC19:01
jeblair#startmeeting infra19:01
openstackMeeting started Tue Mar 25 19:01:27 2014 UTC and is due to finish in 60 minutes.  The chair is jeblair. 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: infra)"19:01
openstackThe meeting name has been set to 'infra'19:01
zaro0o/19:01
jeblair#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting19:01
jeblairagenda ^19:01
jeblair#link http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-03-18-19.02.html19:01
jeblairlast meeting ^19:01
jeblair#topic Agenda19:01
*** openstack changes topic to "Agenda (Meeting topic: infra)"19:01
*** lbragstad has left #openstack-meeting19:02
jeblairthere's no agenda, so anyone have anything they want to discuss?19:02
*** jprovazn has joined #openstack-meeting19:02
jeblairpuppetboard19:02
sdaguejeblair: I think I noticed something out of the corner of my eye the other day on you doing multinode nodepool?19:03
*** zhiyan_ is now known as zhiyan19:03
jeblairmultinodepool19:03
clarkbwhen do RCs happen and does infra need to soft freeze for that?19:03
jeblairokay, throw other things out if you think of them, otherwise, this may be short (which is no bad thing)19:03
jeblair#topic puppetboard19:04
fungioh, i guess the openstack-attic namespace might be worth some deliberation too19:04
*** openstack changes topic to "puppetboard (Meeting topic: infra)"19:04
jeblairyay we haz puppetboard!19:04
fungiit released?19:04
SergeyLukjanovyay!19:04
jeblairon the only slightly inaccurately named http://puppetdb.openstack.org/19:04
*** msdubov has quit IRC19:04
fungioh, puppetboard. i had storyboard in my head19:04
fungiyes, puppetboard!19:04
jeblairso what's the story with the name anyway?19:05
clarkbjeblair: it has been suggested we make a CNAME for it19:05
*** _nadya_ has joined #openstack-meeting19:05
jeblairhostname19:05
*** mtanino has quit IRC19:05
*** shakayumi has quit IRC19:05
clarkbjeblair: puppetdb runs on that node and puppetboard depends on puppetdb so they were colocated19:05
*** Duane has quit IRC19:05
jeblairshould puppetboard and puppetdb be on the same host?19:05
*** syerrapragada has joined #openstack-meeting19:05
fungiit seems fine using the server hostname to me, but if people want a different fqdn for the url that's easy enough to fix19:05
clarkbjeblair: I don't see a problem with them being colocated19:05
anteayaI think they have to be19:06
jeblairokay, if we think they belong on the same host, then yeah, let's cname that19:06
*** noslzzp has quit IRC19:06
jeblairfor discoverability, etc19:06
SergeyLukjanov+119:06
zaro+119:06
fungiso should we move puppet-dashboard.o.o to be a cname to that then?19:07
jeblairfungi: not a bad idea; though of course if anyone has a stale bookmark, it would be to port 300019:07
fungior retire the old name now that we can tear down the old server and use puppetboard.o.o or something?19:07
jeblairso given the port issue, i'd be okay just dropping puppet-dashboard19:07
anteayaI like puppetboard.o.o19:07
clarkbI think we should tear down the old server and use puppetboard19:07
*** Duane has joined #openstack-meeting19:07
clarkbit wasn't a highly used external service anyways (I don't image many people will have to update bookmarks)19:08
*** markwash has quit IRC19:08
fungithere may be a handful of docs which need updating in the config repo now when pointed at it19:08
fungigit grep ought to find them in short order19:08
jeblair#agreed cname puppetboard.o.o and delete puppet-dashboard.o.o server and dns19:08
jeblairi reckon i can do that19:09
*** zns has quit IRC19:09
jeblair#action jeblair cname puppetboard.o.o and delete puppet-dashboard.o.o server and dns19:09
anteayafungi: 9 instances of puppet-dashboard in /config19:09
zaroquestion about gerrit upgrade when done with this topic19:09
jeblairand i guess we can start merging the refactoring patches, though we might want to confirm that aarongr, etc, are around to fix anything19:09
pleia2yay :)19:09
*** bdpayne has joined #openstack-meeting19:10
*** dkranz has quit IRC19:10
*** jamielennox has left #openstack-meeting19:10
jeblair#topic multinode nodepool19:10
*** openstack changes topic to "multinode nodepool (Meeting topic: infra)"19:10
SergeyLukjanov++ for puppetboard19:10
jeblair#link https://review.openstack.org/#/q/status:open+project:openstack-infra/nodepool+branch:master+topic:multi,n,z19:11
jeblairsdague: ^ there's a 4 patch series to add multi-node support to nodepool19:11
* anteaya sees 7 patches19:11
jeblairit's a pretty naive implementation, but it can be refined/extended/replaced later19:11
sdaguejeblair: awesome19:11
*** SumitNaiksatam has quit IRC19:11
jeblairanteaya: there are some other unrelated patches later on in the series19:12
anteayaah19:12
clarkbjeblair: I think for a naive implementation it has quite a bit of flexibility19:12
jeblairi just didn't bother to change the topic19:12
clarkbgranted I havne't tried to spin up any subnodes yet so can't speak from experience19:12
*** SumitNaiksatam has joined #openstack-meeting19:13
jeblairsdague: there isn't any L2 connectivity yet; but the nodes will be able to ssh into each other19:13
sdagueso when do we think we could try to kick the tires with a job that uses it?19:13
*** slagle_ has joined #openstack-meeting19:13
jeblairsdague: they could set up an openvpn..., or soon we should have neutron support in hp and rax, and when that happens, we can have nodepool create an l2 network19:13
fungidepends on what else the job needs to build on top of it (like vpn)19:13
*** dcramer_ has joined #openstack-meeting19:13
fungier, what jeblair said19:13
jeblairbut if we can do something that doesn't require L2, it should be pretty easy19:14
sdaguewhat code is going to run pre-job start the do something like lay down the vpn19:14
sdagueyeh, well the start point for me is multinode devstack19:14
sdagueso I'm trying to figure out how I could hack this into making that work19:14
clarkbsdague: it is arbitrary, you give nodepool a script to run on each node and all nodes can ssh to each other19:14
jeblairbasically, nodepool is going to run a script on all the nodes in a group after spinning them up and before attaching them to jenkins19:14
jeblairso we can do whatever we want there19:15
*** slagle has quit IRC19:15
*** noslzzp has joined #openstack-meeting19:15
sdagueit's going to run the same script in all nodes? or run a script ahead of time19:15
clarkband each node knows what its role is so you can distinguish between the node connected to jenkins and the subnodes19:15
jeblairsdague: does multinode devstack need l2 connectivity, or can we just give it some ip addresses and let it talk over L3?19:15
sdagueI'm mostly thinking about cert generation to create the L2 connect19:15
sdaguejeblair: good question19:16
clarkbsdague: you would probably have each node do their own cert generation then ssh to all of the others to copy it across19:16
sdagueactually we could probably get away with L319:16
sdaguewhat's the firewall situation between hosts?19:16
clarkbthen start the openvpn service19:16
*** alazarev has joined #openstack-meeting19:16
jeblaircool, i'd like to avoid investing too much in creating openvpn stuff if we're going to end up with neutron in the not too distant future19:16
sdagueclarkb: well openvpn is hub and spoke, so we'd build the certs on one box, and distribute them19:16
clarkbsdague: as is completely locked down, only ssh is allowed in19:16
fungiis this where we need heat to gather things like signatures and then enroll on other nodes in the group?19:17
jeblairbut if we need it, it's an option19:17
clarkbjeblair: ++19:17
jeblairfungi: we could, but this is all doable with ssh19:17
clarkbsdague: right so assuming we don't need L219:17
sdagueI'm not convinced doing that in heat is actually any easier than with ssh19:17
clarkbsdague: I imagine the script on each node would update the iptables to allow whichever ports you need in the mesh19:17
jeblairfungi: the nodes all know each other, and the controller node is deterministically the last one to run the ready script19:18
fungiyeah, i think neutron's desperation for multi-node assumes l2 connectivity but that can presumably come later19:18
sdagueclarkb: we'll have firewall control inside the nodes ourselves?19:18
clarkbsdague: yup you have root19:18
clarkbsdague: and we only do local firewalls19:18
sdagueI thought that previously there was an issue with punching holes19:18
sdaguethat heat was running into19:18
*** slagle_ is now known as slagle19:18
clarkbsdague: there was, but heat fixed it by updating the rules on those nodes19:18
sdagueok19:18
jeblairso i image the ready script pokes holes in iptables, adds the controller node's ssh key on all the subnodes, then on the controller node, it can ssh back out to the controller to do any key distribution, etc.19:19
*** balajiiyer has joined #openstack-meeting19:19
jeblairer "ssh back out to the subnodes"19:19
*** balajiiyer has quit IRC19:19
*** balajiiyer has joined #openstack-meeting19:19
jeblairanyway, that script is the last part of this that hasn't been written19:19
sdagueok, cool19:20
sdaguewell once that part is in place, let me know19:20
sdagueI think an experimental devstack sanity check job would be a good place to start after that19:20
sdagueand then we'll get to see a whole new level of failure in the gate :)19:20
jeblairsdague: from a jenkins POV, it's just a single node attached to jenkins.  it just happens that the job jenkins runs on that node will have access to a set of other machines.19:20
sdaguejeblair: cool19:21
jeblairsdague: hehe19:21
*** kgriffs_afk is now known as kgriffs19:21
*** denis_makogon_ has joined #openstack-meeting19:21
jeblair#topic openstack-attic19:21
*** openstack changes topic to "openstack-attic (Meeting topic: infra)"19:21
jeblairi registered this on github in case we need it19:21
fungiwhen last the conversation wound down, it sounded like the tc had basically already approved policy that we would archive things we no longer care about into a separate namespace19:22
fungithus something we need to plan for. i guess when we do the next round of renames19:22
*** denis_makogon_ is now known as denis_makogon19:22
jeblairi missed that tc meeting19:22
*** dkranz has joined #openstack-meeting19:22
jeblairfungi: do you have a reference?19:23
fungii missed that the policy patch was stating that, or i'd have suggested not doing so19:23
fungittx linked to the change in governance. i'll dig it back up19:23
*** BrianB__ has quit IRC19:23
mordredo/19:24
mordred(sorry late)19:24
pleia2welcome mordred19:24
SergeyLukjanovmordred, hey19:24
*** bdpayne_ has joined #openstack-meeting19:25
fungi#link http://git.openstack.org/cgit/openstack/governance/commit/reference/programs.yaml?id=7044c1719:25
zaromordred: your appearance made everything quiet.19:26
* mordred is the quiet maker19:26
*** zul has quit IRC19:26
*** bdpayne has quit IRC19:27
fungiin the commit message, which was apparently part of what's voted on along with the patch itself, "openstack-dev/openstack-qa, openstack/melange, openstack/openstack-chef, and openstack/python-melangeclient which should move to some attic ... openstack-dev/sandbox and openstack/python-openstackclient which should be in stackforge"19:27
jeblairhrm19:27
jeblairi'm not sure a commit message makes policy19:27
fungithat was more or less what the discussion ended with at any rate19:27
jeblairespecially a vague one like that19:27
ttxo/19:28
jeblairi mean, i think it's the actions on files in the repo that are the policy and what people are voting on19:28
jeblairi see the commit message as more like the speech you would give to the committee about the motion, not the motion itself19:28
mordredjeblair: ++19:29
fungiin which case, more clarification needed after all19:29
mordredI would consider that to be the case19:29
ttxfungi: commit message @ http://git.openstack.org/cgit/openstack/governance/commit/?id=7044c177dcc02d44321660db8b909483dad68be319:29
*** venkatesh has quit IRC19:29
ttxyes, that was not a "resolution", more of a default understanding19:29
fungittx: righth, that's what i linked above19:29
ttxmissed link sorry19:30
fungiokay, so it'19:30
fungier19:30
*** zul has joined #openstack-meeting19:30
ttx(hence the "should" language which is far from perscriptive)19:30
jeblairit probably does represent what most of us think anyway, at least generally19:30
jeblairas in, i think we could probably all get behind moving melange to openstack-attic19:30
ttxI think there is the idea that all projects under openstack*/ should be accounted for19:31
fungii was less convinced that openstack-dev/sandbox belongs in stackforge19:31
jeblairfungi: ++19:31
ttxnot really forcing the implemntation19:31
clarkband in general I am not sure stackforge is a dumping ground so ++ to attic19:31
ttxthe commit message reflects the discussion we had about those orphans19:31
clarkbstackforge isn't a default. It is specificlly a way for community members to leverage the tools we provide for active development19:32
jeblairso i think our open questions are: a) what to do with melange? should we initialize openstack-attic and move it there?  or leave it in openstack and categorize it as abandoned?19:32
fungithough i guess the gantt and openstackclient moves to stackforge are more in line with what we expect to do in the case of an aborted incubation19:32
jeblairand b) what to do with gantt19:32
*** Duane has quit IRC19:32
*** luqas has quit IRC19:32
*** balajiiyer has left #openstack-meeting19:33
jeblairi would say under normal conditions, that's an easy one, we move it to stackforge, except people keep saying it might come back to life again later19:33
fungiin which case, the compute program deciding to no longer foster gantt is actually an aborted incubation right?19:33
*** hub_cap has joined #openstack-meeting19:33
*** Duane has joined #openstack-meeting19:33
jeblairfungi: i think so.  i just hope they know that if they move it to stackforge, they're giving up the right to use the name gantt.  :)19:33
jeblairbecause i think it would be mean to rename a stackforge project because openstack likes the name19:34
clarkb++19:34
fungior is there some other class of projects which might get spun out of an official program into unofficial space?19:34
jeblair(that is unless they want to rename it _back_ to openstack in the future)19:34
*** baoli has quit IRC19:35
*** Sukhdev has quit IRC19:35
jeblairfungi: i think once they are unofficial, they're unofficial; we don't care anymore19:35
sdaguegantt is going to be fully reinitialized when it happens again19:35
fungibasically wondering if gantt was incubated and is now being un-incubated, in which case we have initial precedent for the process19:35
*** zhiyan is now known as zhiyan_19:36
jeblairsdague: what's it going to be called?19:36
sdaguegantt19:36
sdaguebasically the forklift failed19:36
jeblairsdague: so there's a group of people that want to keep working on the current forklift19:36
sdaguemy understanding is it will be a new forklift19:36
sdagueafter cleaning up some nova scheduler parts to make the forklift doable19:37
clarkbright, which leads to the issue jeblair points out above19:37
sdagueagreed19:37
*** vhoward has joined #openstack-meeting19:37
jeblairsdague: i think if nova has decided to mothball gantt, but wants to revive it in the future.... there are two least-bad choices19:37
*** jecarey has quit IRC19:37
*** Duane has quit IRC19:37
clarkbkeep gantt as openstack/gantt >_>19:37
jeblaira) rename openstack/gantt -> something/notgantt; this gives nova devs a clean start19:38
*** mrmartin has joined #openstack-meeting19:38
sdaguejeblair: honestly, I have no idea why we're not just deleting gantt. I think the people that want to play with the code should do so off in github if they really want to. Because there is no path forward from the current codebase to the eventual project19:38
*** baoli has joined #openstack-meeting19:38
fungis/delete/mothball/ but otherwise agree19:38
sdaguefungi: sure19:38
sdagueopenstack-attic/gantt-mark119:38
jeblairb) keep openstack/gantt and disable the acls; when it is restarted, people can merge a new branch over the current one; we won't do a force push, but we can do a wholesale replacement in one commit like we did with keystone (it preserves history too)19:39
jeblairsdague: yeah, that's closest to option (a) (actual deletion isn't an option)19:39
jeblairsdague: thanks for that clarification, i think it helps a lot19:40
*** vhoward has left #openstack-meeting19:40
jeblairanyone have preferences on option a vs b?19:40
fungii think b is a little more genuine and preserves what went on19:41
clarkb++ to b19:41
jeblairi still have my notes from when i did that for keystone, so it should be pretty easy to do19:41
clarkbcontinuing work on what was gantt can continue wherever the devs like19:41
fungiwith a we sent a signal that it's okay to etch-a-sketch projects by just renaming them out of the way and trying harder next time19:42
*** mrmartin has quit IRC19:42
jeblairfungi: yeah, i agree, that makes me uneasy19:42
fungis/sent/send/19:42
jeblairttx: it seems like we think the best thing to do with gantt is to leave it where it is but disable access for now, until it is either revived (most likely), or it is certain that it will not be revived.19:43
jeblairttx: maybe we should have a mothball status for projects19:44
*** _nadya_ has quit IRC19:44
jeblairanyone object to moving melange to -attic ?19:44
*** shakayumi has joined #openstack-meeting19:45
anteayaI do not object19:45
fungiif we are agreed on wanting openstack-attic, then .*melange.* are good fodder19:45
*** shakayumi has quit IRC19:45
anteayait isn't like there hasn't been adequate discussion19:45
SergeyLukjanovfungi, ++19:46
*** mattgriffin has joined #openstack-meeting19:46
jeblairfungi: i think that's implicit in the question; i am also asking if you think moving it elsewhere or not moving it are preferable19:46
*** jecarey has joined #openstack-meeting19:46
sdagueit would be a good initial signal as well19:47
sdaguesee what other dead projects people propose moving to the attic19:47
sdagueis your intent to move stackforge there as well?19:47
sdagueor should there be a stackforge-attic?19:47
fungii'm fine with moving stuff into an attic as a low-priority task when we're already doing other more urgent renames, since there seems to be tc consensus that we should not keep things around in the openstack/.* namespace indefinitely19:47
jeblairi'll send an email to the infra list suggesting dispositions for these tricky projects, and we can verify that we agree with them, and if so, i'll forward to the tc to see if it's agreeable to them19:47
jeblairand if they object, then we'll start writing policy i guess.  :)19:48
* clarkb returns to following meeting19:48
jeblair(by writing policy i mean proposing changes to governance to make this explicit)19:48
jeblair#action jeblair propose organizational cleanup repo renames to infra and then tc lists19:49
jeblair#topic freeze and release schedule19:49
*** openstack changes topic to "freeze and release schedule (Meeting topic: infra)"19:49
jeblairclarkb: just in time19:49
*** IlyaE has quit IRC19:49
*** MaxV has joined #openstack-meeting19:49
jeblair#link https://wiki.openstack.org/wiki/Icehouse_Release_Schedule19:49
jeblairmilstones start thursda19:50
*** egallen has joined #openstack-meeting19:50
clarkbI saw that the first RCs are starting to come out19:50
clarkband was curious if we needed to institute a soft freeze around that happening19:50
jeblairoh that seems earl19:50
jeblairy19:50
sdagueit's later than you think19:50
sdaguemonday is april19:50
*** jmontemayor has quit IRC19:50
jeblairi guess that calendar means rc's start at the beginning of the week that has the 27th19:51
fungioh, and related to release stuffs, i should get started on the grizzly eol i meant to start yesterday19:51
ttxjeblair: RCs may start anytime now19:51
jeblairi initially read it as rcs start on the 27th19:51
ttxtheer is no start date for them, the schedule just shows when they are ~expected19:51
sdagueyeh19:51
jeblairi don't think a 1 month freeze is tenable19:51
ttxthe first one shall happen tomorrow fwiw19:51
clarkbjeblair: agreed, perhaps we be nice during the first part of freezing (this week) then go backto business as usual?19:52
ttxjeblair: soft freeze, everyone works on storyboard instead ! :)19:52
*** dcramer_ has quit IRC19:52
krotscheckyay!19:52
anteayasorry what are we freezing?19:52
sdaguethis week and next week are probably the sensitive times19:52
jeblairttx: i started breaking/fixing storyboard things this morning!19:52
clarkbanteaya: infra19:52
sdaguewhen the likelyhood of rc critical bugs still flowing at a good rate exist19:53
jeblairsdague, ttx: right, but there aren't any hard deadlines right now19:53
ttxjeblair: the RCS are not that time-sensitive. I'd rather softfreeze the week before release so that we can respin RCs quickly if need be19:53
sdaguesure19:53
ttxif a RC has to wait another day due to wreckage, not that big of a deal19:53
sdagueand what do we really mean by soft freeze? basically no zuul or nodepool upgrades?19:54
sdagueit's definitely on the soft size19:54
sdagueside19:54
jeblairsdague: unless we really want to, yes.  :)19:54
*** shakayumi has joined #openstack-meeting19:54
ttxso I'd say, hold off on weird changes (like Gerrit 2.8), and softfreeze from apr10 to Apr1719:54
clarkbsdague: basically we tend to spend more time evaluating things (eg FFE)19:54
sdaguebasically just try to reduce high risk changes19:54
fungiand not schedule outages unless they're absolutely needed to get things un-broken19:54
sdaguettx: well gerrit is already pushed past that, so that's all good19:54
ttxsdague: yes, using it as an example19:55
jeblairso yeah, let's be cautious now, but not defer significant work yet, and instead expect a soft freeze around april 10-1719:55
clarkb++19:55
fungiso for example, not doing project renames while we're in a soft freeze19:55
*** emagana has quit IRC19:55
sdaguefungi: yeh, that seems solid19:55
ttxfrankly speaking, the following two weeks are less sensitive infra-wise than FeatureFreeze week19:55
sdagueprobably worth actually figuring out what soft freeze means :)19:55
sdaguetrue19:55
*** shakamunyi has joined #openstack-meeting19:56
ttxso if you give me two weeks for freezing infra changes, I'd pick feature freeze week and release week19:56
jeblair#topic gerrit upgrade19:56
*** openstack changes topic to "gerrit upgrade (Meeting topic: infra)"19:56
jeblairzaro: ?19:56
clarkbttx: good to know thanks19:56
zaroyou asked me about using WIP plugin for gerrit 2.8.  still interested in that?19:57
jeblairzaro: yes, especially if we have a bit of extra time to look into it19:57
jeblairzaro: if the patch needed has landed in master, i think we can consider backporting it to 2.819:57
*** joshuamckenty has joined #openstack-meeting19:57
zarook.  i'll ask _david_ about which patches are necessary.19:58
*** shakayumi has quit IRC19:58
jeblairzaro: cool, thanks!19:58
*** eglynn has joined #openstack-meeting19:58
jeblairthanks everyone!19:58
jeblair#endmeeting19:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:58
openstackMeeting ended Tue Mar 25 19:58:45 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-03-25-19.01.html19:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-03-25-19.01.txt19:58
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-03-25-19.01.log.html19:58
pleia2thanks jeblair19:58
jeblairhrm, meetbot and my clock don't agree19:59
*** zehicle_at_dell has joined #openstack-meeting19:59
pleia22 seconds off my time19:59
anteayaI have 2 seconds difference19:59
pleia2actually, it's correct for when jeblair hit #endmeeting19:59
fungintp tells me 19:59:45 now19:59
*** _nadya_ has joined #openstack-meeting19:59
anteayaes19:59
anteayayes even20:00
fungi(at teh sound of the tone, the time will be...)20:00
annegentle2 seconds!20:00
*** changbl has quit IRC20:00
jeblairat the beginning of the lag, the time was ....20:00
annegentle:)20:00
*** armax has quit IRC20:00
ttxo/20:00
dhellmannhi, all20:00
*** caleb_ has quit IRC20:00
sdagueo/20:01
jgriffitho/20:01
*** lukego has quit IRC20:01
*** armax has joined #openstack-meeting20:01
mordredo/20:01
zehicle_at_dello/20:01
*** caleb_ has joined #openstack-meeting20:01
*** syerrapragada has left #openstack-meeting20:01
*** tjones has joined #openstack-meeting20:01
ttxrussellb, markmc, jgriffith, vishy, markmcclain, lifeless : around ?20:02
lifelessfor my sins20:02
jgriffithpresent20:02
ttxI think markmcclain may miss20:02
ttxmikal is absent20:02
devanandao/20:02
ttx#startmeeting tc20:02
openstackMeeting started Tue Mar 25 20:02:37 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:02
*** openstack changes topic to " (Meeting topic: tc)"20:02
openstackThe meeting name has been set to 'tc'20:02
ttxOur agenda for today:20:02
SergeyLukjanovo/20:02
ttx#link https://wiki.openstack.org/wiki/Governance/TechnicalCommittee20:02
*** MaxV has quit IRC20:03
ttxmay have to adapt it since Mark asked to push back on the Neutron plan review20:03
*** shakamunyi has quit IRC20:03
ttxwe'll talk about future meetings in election season in the open discussion section at the end of the meeting20:03
ttx#topic Integrated projects and new requirements: Gap analysis for Cinder20:03
*** openstack changes topic to "Integrated projects and new requirements: Gap analysis for Cinder (Meeting topic: tc)"20:03
ttxjgriffith: did you prepare a base document to support our discussion ?20:04
jgriffithttx: no but I can, real quick20:04
jgriffithstand by20:04
*** markmc has joined #openstack-meeting20:04
markmcsorry20:04
*** baoli has quit IRC20:04
russellbo/20:04
zehicle_at_dellttx, can we add a sliver into the agenda to confirm the DefCore/TC meeting is on Friday?20:04
jgriffithhttps://etherpad.openstack.org/p/cinder-gap-analysis20:05
ttxzehicle_at_dell: sure, we can talk about that in open discussion at the end, but I think it's confirmed already20:05
zehicle_at_dellthanks20:05
russellbttx: zehicle_at_dell other than the time20:05
vishyo/20:05
russellbthat wasn't clear on list, it was 8pm UTC, and then "7 8 UTC"20:05
*** derekh has quit IRC20:05
*** lblanchard has quit IRC20:05
jgriffithttx: you copy paste faster than I :)20:06
*** lblanchard has joined #openstack-meeting20:06
*** shakamunyi has joined #openstack-meeting20:06
zehicle_at_dellrussell, sorry that was just a typo.20:07
zehicle_at_dellit's 8 UTC20:07
russellbzehicle_at_dell: no problem, just want to make sure i'm available at the right time20:07
ttxjgriffith: any area where you identified a gap ?20:07
*** IlyaE has joined #openstack-meeting20:07
russellbnot sure it's a gap, but in general there's probably better code sharing we could do between nova and cinder still20:07
jgriffithttx: docs20:07
jgriffithttx: as in documenting the items20:07
jgriffithttx: as russellb pointed out a month ago :(20:08
ttxon the minor side, we also need to formalize a cinder-coresec group20:08
jgriffithDefined scope20:08
ttx(contact points for handling vulnerability bugs)20:08
jgriffithI'm striking through the items that I *believe* are covered20:08
ttxjgriffith: sounds good20:08
jgriffithshout if I'm wrong anyone20:08
jgriffithttx: yes, secgropu is a gap for sure20:08
jgriffithI've been relying on the sec team20:08
ttxI'll strike a few for you on the release management side20:08
russellbread through it, i don't think i have any concerns personally20:09
russellbcurious how you feel the heath of your core team is these days?20:09
russellbreviews look more balanced than they used to be a long time ago, so seems good?20:10
jgriffithrussellb: I think it's good20:10
russellbcool20:10
sdaguejgriffith: while clearly not a blocking item, one thing that I'd like to see in juno is some additional functional testing on the volumes code. It seems like when we get to a certain number of volumes tests we end up tripping up, and would be nice to be able to beat on it harder some how in juno.20:10
jgriffithrussellb: review balance is MUCH better20:10
russellbawesome20:10
jgriffithsdague: fair, and agreed20:10
jgriffithsdague: so that's a comment to add to the analysis here?  Or a seperate topic?20:11
sdaguebut honestly, I find the cinder team is very responsive to issues that we hit there20:11
ttxsdague: add under "decent functional tests coverage" ?20:11
russellbjgriffith: really, in general, very nice work to the whole cinder team20:11
jgriffithnow that I just crossed that setion out :)20:11
jgriffithrussellb: we've got some good dedicated folks now20:11
jgriffithstable20:11
sdaguettx: yeh, probably an addendum there. Honestly, things are in pretty good shape, so I could go either way about recording it there or saying "we should do more"20:11
jgriffithI'd like to have a section for notes/suggestions at the bottom20:12
russellbjgriffith: +120:12
russellbi can think of some minor things for that, but no real gaps20:12
jeblairthey're especially great at dealing with the fact that we blame them for lots of bugs because their tests happen to be the ones that actually error out.  :)20:12
sdagueheh20:12
*** yassine has quit IRC20:12
jgriffithjeblair: haah20:12
mordredjeblair: ++20:12
jgriffithoh, there's a fantastic point20:13
mordredjeblair: dosen't that mean that they should then fix other people's bugs? if it's their tests that fail?20:13
ttxhttp://russellbryant.net/openstack-stats/cinder-reviewers-90.txt looks good to me20:13
jgriffith"code sharing between nova and cinder"20:13
annegentlejgriffith: my only input would be that you have a good docs bridge in thingee20:13
sdagueit would actually be interesting if we could get some high io nodes for tests to be able to beat on20:13
annegentlejgriffith: so maybe lean on Mike to fill in the docs gaps20:13
russellbjgriffith: that's the biggest thing i can think of, and it's not a huge deal20:13
jgriffithannegentle: I have been :)  Don't want to take advantage of him20:13
annegentlejgriffith: yup :)20:14
ttxhttp://www.stackalytics.com/?release=icehouse&metric=commits&project_type=all&module=cinder-group&company=&user_id= looks sane too20:14
russellbnice balance there20:15
*** jprovazn has quit IRC20:15
russellbjgriffith: you guys going to push for driver CI?20:15
russellbjust curious really20:16
jgriffithrussellb: indeed20:16
jgriffithrussellb: we are20:16
jgriffithrussellb: but there's already some angst20:16
russellbheh, i'm sure20:16
jgriffithI'm leaning towards opt in for Juno and see how it goes20:16
jgriffithI'd like to think folks will step up on their own20:17
* mordred predicts it will not go anywhere until it's mandatory, based on past experience20:17
jgriffithno threats etc20:17
ttxjgriffith: so it looks like gap is just public docs and coresec team20:17
* mordred hopes jgriffith is right20:17
ttxthe remaining ones are just recommendations20:17
jgriffithttx: I can live with that20:17
jgriffithyeah, probably shouldn't turn it into a design summit session :)20:17
ttxjgriffith: what would be your plan to tackle both ?20:17
jgriffithThe doc part is easy20:18
*** mattgriffin has quit IRC20:18
ttxI guess we can solve cinder-coresec in a matter of days20:18
jgriffithwiki page with the official stuff20:18
ttxjust find a couple volunteers we can hassle20:18
jgriffithcoresec that's sort of hard20:18
jgriffith^^  the volunteers part :)20:18
russellbjust make it you :-p20:18
ttxI have names I can suggest from the past :)20:18
jgriffithrussellb: might not be very secure20:18
jgriffithttx: that would be great20:18
ttxanyway, I think we can even solve that one prerelease20:18
dhellmannjgriffith: it's just an initial contact, right? you can pull in help20:19
ttxwill be in touch20:19
jgriffithdhellmann: I would hope so yes20:19
ttxyes, it's just the set of folks we add to bugs in the first step20:19
russellbyep that's the idea20:19
jgriffithdhellmann: but I would like to have folks that are more security minded than I keeping an eye on things20:19
ttxthen those can add more to the ACL20:19
dhellmannjgriffith: sure20:19
sdaguemordred: it will be interesting data to see if voluntary works20:19
ttx"doc part is easy": do you have an ETA on that ? pre-release ? juno-1 ?20:20
russellbnobody did it for nova until it was mandatory20:20
sdagueand actually really good to have data on the various approaches for driver testing from nova, neutron, and cinder20:20
russellbfwiw20:20
*** alazarev has quit IRC20:20
jgriffithsdague: I'm not sure I want to do a blast call for volunterrs20:20
mordredsdague: ++20:20
*** jasondotstar has quit IRC20:20
ttx#info two gaps identified: public docs and cinder-coresec team20:20
*** _nadya_ has quit IRC20:20
ttxjgriffith: "doc part is easy": do you have an ETA on that ? pre-release ? juno-1 ?20:20
jgriffithMonday20:21
ttxok, pre-release20:21
jgriffithI'll quit putting it off finally20:21
ttx#info Both gaps shall be addressed before icehouse release20:21
*** Swami has joined #openstack-meeting20:21
ttxOK, I think that covers it for me. More comments/suggestions ?20:21
*** dcramer_ has joined #openstack-meeting20:22
jgriffiththanks for the input everyone20:22
jgriffithI'd like to focus on some of those suggestions for juno20:22
annegentledoc deadlines are good! :)20:23
ttxLast question on this: any suggestion on which project we should cover next ?20:23
*** colinmcnamara has joined #openstack-meeting20:23
ttxwe emptied our list of TC+PTL projects20:23
ttx(although we still need to reveiw and bless neutron's plan)20:24
*** vkmc has joined #openstack-meeting20:24
*** vkmc has quit IRC20:24
*** vkmc has joined #openstack-meeting20:24
russellbpython -c 'import random ; print random.choice['swift', 'ceilometer', ...]'20:24
russellbsyntax fail20:24
sdagueheh20:24
russellbhow about ceilometer?20:25
ttxok, nothing urgent ? I heard some people wanting we do ceilometer next20:25
russellbthere we go :)20:25
ttxOK20:25
sdaguewell, what about asking existing PTLs for volunteers20:25
lifelesscrickets20:25
sdaguebecause there will need to be prep work for a bunch of them20:25
dhellmannyeah, it's going to take some time to put together the docs, we should give them a heads-up20:25
ttxsdague: there is a bit of a timing issue with PTL elections, which we'll discuss in open discussion at the end of meeting20:26
sdagueand making sure they are able to schedule the prep work would be good20:26
sdaguettx: sure20:26
*** banix has quit IRC20:26
ttxok, let's go back to this at end of meeting20:26
ttx#topic New graduation / post-graduation requirements20:26
*** openstack changes topic to "New graduation / post-graduation requirements (Meeting topic: tc)"20:26
ttxThis has been split into three separate changes:20:26
ttx* Add API graduation/post-graduation requirements (https://review.openstack.org/#/c/68258/)20:26
ttx* Add Heat integration post-graduation expectation (https://review.openstack.org/#/c/81773/)20:26
ttx* Add Horizon integration post-graduation expectation (https://review.openstack.org/#/c/81774/)20:26
ttxI think they all "officialize" defacto policy20:27
ttxI'm personally fine with all of those. Any more discussion needed on that ?20:27
mordredI think they're great- except I think that the horizon one is too vague/loose20:27
dhellmannis the plan to list each project like that? for example, should jd__ or I propose one to add ceilometer?20:27
*** MaxV has joined #openstack-meeting20:27
mordrednot enough to suggest a change - just saying, I think it's too friendly20:27
sdagueI'm still a little skeptical on heat at this point, just because even though it's integrated, it's really minimally tested and documented compared to other projects20:27
annegentleI still feel like we have a lost opportunity for better user experience by better defining the Dashboard or CLI requirements from an end-user perspective20:28
*** vkozhukalov has quit IRC20:28
ttxdhellmann: if you think ceilometer integration should be a post-graduation pre-release thing, yes20:28
russellbwe can always make it more strict later20:28
russellbthe heat/horizon stuff is listed as post-graduation right now20:28
russellbbetter than not listed at all20:28
annegentleso yea, concerns with vagarity, but are we actually relying too heavily on Horizon the project when there's a larger design need?20:28
sdagueI'm personally bootstrapping on heat right now to help on the testing front, and you run into walls pretty quick unless you go and read the heat source code20:28
*** rockyg has joined #openstack-meeting20:28
devanandanot to be pedantic, but I'd like to understand what determines whether a given project "makes sense" to integrate with existing projects (heat, ceilometer, horizon, etc)20:29
ttxmordred, devananda: so you'd rather keep case-by-case intgegration guidelines ?20:30
ttxmordred, devananda: because there is no one-size-fits-all wrt integration ?20:30
devanandattx: or perhaps merely be more explicit about when it is / isn't expected20:31
mordredI'm not saying that at all20:31
mordredI'm saying "projects should have support in horizon" not "projects should be supported in horizon if it makes sense"20:31
devanandattx: if "it makes sense to teh TC at the time the project applies to incubation" is clearer, taht's fine.20:31
mordredI think "if it makes sense" makes the statement meaningless20:31
devanandaeg, heat integration for ironic does not make sense /to me/, because I think we get that via nova20:31
dhellmannthat goes to what markmc said in  one of the review comments about requiring an API and tripleo -- it feels weird to me to say that only API projects are integrated, especially if that means our deployment tool won't be20:32
*** Leonr has quit IRC20:32
dhellmannat the same time, I don't know if tripleo needs to be integrated with horizon, so...20:32
dhellmann(at least not in the sense that we mean for these other projects)20:32
sdaguedevananda: ironic is never expected to be called directly without nova?20:33
ttxdhellmann: I wouldn't call tripleo a deployment tool, but I see your underlying point20:33
devanandabut the current wording does not specify to whom a given project integration should make sense20:33
*** mtanino has joined #openstack-meeting20:33
*** dprince has quit IRC20:33
mordredI think I could reword my opposition to the current wording based on what devananda just said20:33
devanandasdague: not never -- but it makes no sense to me for heat to do node enrollment20:33
dhellmanndevananda: isn't it implied that judgement is left up to the TC?20:33
markmcdhellmann, the idea is definitely for tripleo to be integrated with horizon - i.e. as a UI for managing OpenStack itself20:33
devanandadhellmann: the whole point of these changes is to make explicit what is currently implicit :)20:34
dhellmannmarkmc: so there will be a horizon UI page to talk to tripleo?20:34
markmcdhellmann, right20:34
lifelessdhellmann: 'tuskar' specifically20:34
dhellmannah20:34
lifelessdhellmann: which is one of the projects under tripleo.20:34
markmcthe "makes sense" part was mostly about whether Heat integration always "makes sense"20:34
lifelessdhellmann: tuskar builds on heat/nova/neutron/glance20:34
markmce.g. is there any resource in ceilometer that should be provisionable via Heat20:34
*** lukego has joined #openstack-meeting20:35
lifelessdhellmann: and tuskar-ui - the horizon code to do this - is *already* in the horizon programme20:35
mordredI could also see there being horizon integration for ironic that makes sense20:35
dhellmannlifeless: ok, I'm behind in my tracking of tripleo so thanks for filling that in :-)20:35
lifelessits not in the main repo yet AIUI but thats because tuskar isn't incubated yet20:35
lifelesshorizon pages for Ironic totally makes sense20:35
markmcfor me, the precise wording isn't a big deal20:35
lifelessfor admins20:35
sdagueso maybe my concerns will all be addressed when we do the heat project review and get a gap plan in place20:35
mordredmarkmc: wasn't there an idea that ceilometer would inform heat about things to be able to make scaling decisions on things?20:36
markmcit's about getting it onto the radar of prospective projects that we will look at their level of heat and horizon integration20:36
sdaguemordred: it does that20:36
ttxsdague: we should do heat next!20:36
dhellmannmordred: alarms are already implemented, yes20:36
mordredyah. so that woudl be the ceilometer heat integration, no?20:36
markmcmordred, yeah, that's different from the kind of integration described by the requirement, though20:36
mordredperhaps calling out explicitly that integrated projects should integrate with each other, rather than enumeration or specific projects then?20:36
*** alazarev has joined #openstack-meeting20:37
ttxtimeboxing this to 4 more minutes, then we should continue discussion on the review itself20:37
*** vijendar has quit IRC20:37
mordredttx: I can shut up and move this offline20:37
markmcI think we're over-thinking this :)20:37
dhellmannmordred: I thought about that too, but we need a matrix *somewhere* for the reviews, so might as well put it here20:37
mordredI'm mostly happy with the sentiment20:37
mordreddhellmann: kk20:37
sdagueI'm 100% good with openstack stuff should integrate well with other openstack stuff. Like the fact that glance and cinder use swift when appropriate (and would expect other things that want to store data to do the same)20:37
ttxmordred: no no 4 more minutes is fine :)20:37
sdaguedo we really want to call out only heat and horizon in this regard20:37
*** vijendar has joined #openstack-meeting20:37
*** adalbas has quit IRC20:38
markmcwe're calling out some obvious/likely integration points, that's all20:38
sdagueok20:38
mordredsdague: I think that's the question - do we want to make a matrix? or do we want to perhaps make a list at incubation time of things we expect a project to integrate with?20:38
ttxsdague: I think the idea was to acknowledge that horizon panels won't land in horizon until the project is graduated and in the integration cycle20:38
mordredso that it's custom-fit for each project at a time20:38
dhellmannsdague: I'd like to add ceilometer, at least for metering resources managed by the project -- where appropriate20:38
markmcwhat else would be on the list?20:38
devanandattx: that seems backwards20:38
markmcas obvious integration points that most projects should consider?20:38
dhellmannmordred: a list at incubation time is another good way to handle it20:38
devanandattx: eg, nova.virt.ironic has to land befoer ironic graduates. why would a horizon ironic panel have to land *after* graduation?20:39
*** otherwiseguy has joined #openstack-meeting20:39
*** Mandell_ has quit IRC20:39
ttxdevananda: it's different, because you're replacing functionality that exists in nova20:39
devanandaah20:39
ttxso you fall under the "replacing stuff" guidelines20:39
*** vijendar has quit IRC20:39
dhellmanndevananda: the work might be done before graduation, but not committed until after20:39
mordredI think that, since it's possible to have external horizon panels20:40
ttxdhellmann: it's usually done before and shipped as an add-on20:40
mordredthat one could argue that having a horizon panel could be a graduation requirement20:40
dhellmannttx: right, I meant committed to horizon20:40
mordredbut having it inside of horizon is a post-graduation action20:40
ttxmordred: it actually is. As an add-on20:40
mordredright. I'm saying as a policy clarification20:40
devanandaright. otherwise, I'll postpone work on integration with horizon until after Juno, which seems to be the opposite of what this change says20:40
* dhellmann loves it when we all agree20:40
ttxawesome, let's move on then :)20:40
mordredhorizon panel good. four legs bad20:40
devananda:)20:41
ttxcontinue on the review if needed20:41
sdagueso I think there was something else that got lost previously as well about upgrade jobs20:41
ttx#topic Add the requirements repo to the release program20:41
*** openstack changes topic to "Add the requirements repo to the release program (Meeting topic: tc)"20:41
sdagueI'll propose that as another review20:41
ttx#link https://review.openstack.org/#/c/82167/20:41
ttxThis was proposed following the discussion from last week20:41
ttxI'm fine with it but since it used to be an orphaned project under the TC supervision, I'll wait for this to reach the normal approval threshold (7 YES) before approving it20:41
ttxComments on that one ?20:41
dhellmannone point that was raised was what this would do to the list of people who vote on the release manager position20:42
jeblairit has >7 yes now.  :)20:42
ttxjeblair: dammit20:42
mordredttx: does that mean that you're now the person who nominates and manages core?20:42
dhellmannI don't think that matters myself, but I wanted to point it out20:42
ttxmordred: I delegated that to dhellmann successfully :)20:42
mordredttx: nicely done20:43
jeblairnice20:43
* dhellmann feels tricked20:43
*** dburmistrov has quit IRC20:43
ttxmordred: I don't feel comfortable editing and suggesting with my petty number of requirements-core reviews20:43
ttxarguably I wasn't even core myself a week ago20:43
ttxI'm happy to select the right person though20:43
dhellmannI've only proposed removing a few inactive members, with no response afaict20:44
annegentleoh good point, hadn't thought of that20:44
ttxi'm also happy that we get requirements patch authors to vote in the release management program PTL election now20:44
annegentleyeah sounds like ttx has himself a core team20:44
ttxadds a bit of diversity20:44
ttxdhellmann: cool, nuke'em20:44
anteaya#link https://wiki.openstack.org/wiki/Release_Cycle_Management20:44
dhellmannok20:44
mordredwoot! I get to vote on ttx20:45
anteayafor release cycle electorate20:45
russellbgo go ttx20:45
ttxwe also consider PTLs as release program members fwiw20:45
ttx(integrated projects ptls)20:45
ttxAnyway.. next topic then20:46
ttx#topic Minor governance changes20:46
*** openstack changes topic to "Minor governance changes (Meeting topic: tc)"20:46
ttx* Add nova-specs to the Compute program [https://review.openstack.org/#/c/81374/]20:46
ttxRussell +1ed so I'll approve now unless someone objects20:46
ttx* Add ironic-python-agent to Ironic program [https://review.openstack.org/#/c/82157/]20:46
ttxDevananda +1ed so i'll approve now unless someone objects20:46
ttx* Adds incubated and integrated release names to programs.yaml [https://review.openstack.org/#/c/81859/]20:46
ttxI think this one needs a few format changes and iterations before landing20:46
ttxannegentle: feel free to rebut my rebuttal.20:47
dhellmannannegentle: thanks, I updated the wiki page20:47
dhellmannoops, I mean anteaya20:47
anteayadhellmann: thanks20:47
anteayawe get each others mail all the time20:47
annegentleheh20:47
dhellmannauto-complete fails again20:48
ttx#topic Open discussion20:48
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:48
*** bdpayne_ has quit IRC20:48
ttxWanted to quickly discuss whether we should hold TC meetings during the PTL election season, which starts Friday20:48
ttxWe still have two potential meetings before the TC election process starts20:48
anteaya#link election timing: http://lists.openstack.org/pipermail/openstack-dev/2014-March/030444.html20:48
ttxBut I wonder if we should have more "integrated projects vs. new requirements" reviews while the PTL elections are running20:48
mordredttx: I'd say yes - we can still review current state20:48
ttxmarkmcclain asked that we postpone the plan review until mid-April20:48
jeblairi think so, we have so many of those to do i don't want to get further behind20:49
ttxso that would be for the new committee20:49
mordredand running for PTL isn't exactly like running for president in the US20:49
*** markwash has joined #openstack-meeting20:49
lifelessmeetings should keep going IMO20:49
lifelesswe have a full plate20:49
dhellmann+1 to continuing20:49
markmcand we should be nervous if a new PTL means a radically different direction for a project20:49
*** imsurit has quit IRC20:49
mordred++20:49
ttxOK, so let's continue during the PTL election season20:49
jeblairif you are running for president in the us, i think we can excuse you from the meetings.20:49
russellbmarkmc: +120:50
ttxwe'll still skip the two weeks of the TC election process, right ?20:50
mordredjeblair: bah. an hour a week is not that much time to ask :)20:50
mordredttx: why?20:50
ttxmordred: dunno, that's what we used to do in the past20:50
ttxtradition, you know20:50
mordredttx: we skipped meetings a lot in the past20:50
russellbi think we have too much to do20:50
ttxlike killing turkeys20:50
mordredI think we should potentially meet more, not less20:50
russellb+120:50
* dhellmann has some patches mordred could write if he needs more to do20:50
sdagueyeh, might as well push forward20:50
russellbkeep pushing through, if the group changes the next week, so be it20:50
russellbbut push forward20:50
sdagueagree20:51
russellbwe can't skip 4 weeks every 6 months20:51
russellbIMO20:51
sdagueat least 6 of us will be here through it anyway20:51
*** colinmcnamara has quit IRC20:51
ttxOK, I just didn't want having TC meetings during election giving undue exposure to current members seeking reelection20:51
dhellmannsdague: good point20:51
ttxbut if everyone is fine with that, let's just do it20:51
dhellmannttx: anyone can come to these meetings, right?20:51
*** changbl has joined #openstack-meeting20:51
ttxdhellmann: yes20:51
annegentlettx: yeah continuity is valuable20:52
mordred++20:52
ttxok, great. That's all I had20:52
sdagueI think if people have a grudge against a tc member, it's not going to dramatically get better or worse during election week20:52
ttxanything else anyone ?20:52
*** mrda_away is now known as mrda20:52
ttxzehicle_at_dell: did you get all the clarification you wanted for the defcore meeting time ?20:52
zehicle_at_dellttx, yes20:53
ttxzehicle_at_dell: I'll miss it, I have a real-life city council to attend20:53
jeblairrussellb: did you get the clarification you wanted for the meeting time?20:53
* ttx is elected to too many official positions20:53
russellbyes20:53
russellb8pm UTC20:53
ttxzehicle_at_dell: you have 6minutes if you want to quickly expose defcore progress. From what I saw you made great progress recently20:54
ttxmikal is absent but I think annegentle could corroborate20:54
annegentlereal life city council!20:54
ttxannegentle: small city.20:55
annegentleI do apologize for derailing the email thread there.20:55
zehicle_at_dellttx, ok20:55
zehicle_at_dellBasically, we've almost completed the first pass on the capabilities scoring20:55
ttxzehicle_at_dell: what do you think about the suggestion to hold all the discussion on defcore list ?20:55
zehicle_at_dellI think that's one of the critical things for people to review20:55
ttxcross-posting to TC list makes it a bit weird to follow20:55
*** ttrifonov_zZzz is now known as ttrifonov20:56
ttxespecially with delayed moderation :)20:56
zehicle_at_dellbecause it gives early guidenance about some of the must-pass categories and gaps20:56
zehicle_at_dellI've been trying to add people to the DefCore list w/o moderation if I get to the request first20:56
ttxzehicle_at_dell: that's great -- I think we can remove openstack-tc from the cc: now20:57
zehicle_at_dell+120:57
*** colinmcnamara has joined #openstack-meeting20:57
sdaguezehicle_at_dell: any chance of getting some sample data for the tests off of real clouds in the near term. I feel like that would help inform the rest of the conversation with seeing what the wilds actually look like right now20:57
*** ArxCruz has quit IRC20:58
zehicle_at_dellyes, we're working actively on that w/ RefStack20:58
zehicle_at_dellthat's the idea w/ TCUP20:58
zehicle_at_delland uploading the results to RefStack as a site20:58
sdagueyep, just curious if you had an ETA for some initial sample set20:58
*** Duane has joined #openstack-meeting20:58
zehicle_at_dellsdague, soonest possible.  we're working on it.  merging some code together20:59
russellbuploading to a site?20:59
russellbcurious what that means20:59
russellbcollection of results for all these different things it has been run against?20:59
russellblooks like we're out of time21:00
ttxok, time is up...21:00
russellbcan talk friday21:00
ttxmore on friday!21:00
ttxThanks everyone21:00
annegentlethanks all21:00
ttx#endmeeting21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
openstackMeeting ended Tue Mar 25 21:00:25 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-03-25-20.02.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-03-25-20.02.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-03-25-20.02.log.html21:00
*** manishg has quit IRC21:00
ttxdhellmann, dolphm, notmyname, jd__, markwash, jgriffith, russellb, stevebaker, david-lyle, markmcclain, hub_cap: (still) around ?21:00
dolphmo/21:00
russellbo/21:00
jgriffithyessir21:00
david-lyleo/21:00
notmynamehere (for a little bit)21:01
* SergeyLukjanov sleeping near the irc client21:01
jd__looks like it21:01
dhellmanno/21:01
*** IlyaE has quit IRC21:01
ttxSergeyLukjanov: does it emit an audible ping every time we say your name to wake you up ?21:01
ttx#startmeeting project21:01
openstackMeeting started Tue Mar 25 21:01:35 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: project)"21:01
openstackThe meeting name has been set to 'project'21:01
SergeyLukjanovttx, yup21:01
ttxAgenda:21:01
ttx#link http://wiki.openstack.org/Meetings/ProjectMeeting21:01
SergeyLukjanovttx, it helps ;)21:01
*** radez is now known as radez_g0n321:01
ttxSergeyLukjanov: that calls for a cron script21:02
stevebaker\o21:02
ttx#topic Progress towards RC1s21:02
*** openstack changes topic to "Progress towards RC1s (Meeting topic: project)"21:02
*** MaxV has quit IRC21:02
ttxWe are slowly making progress to wards the first release candidates21:02
hub_caphi ttx21:02
ttxLet me list the ETAs21:03
hub_capttx we have one more we put in trove, fyi21:03
ttx#info Keystone expected tomorrow21:03
ttx#info Trove also expected tomorrow21:03
ttx#info Cinder, Glance expected Thursday21:03
hub_capmaybe thr ttx ;)21:03
*** manishg has joined #openstack-meeting21:04
*** topol has quit IRC21:04
ttx#info Nova, Ceilometer expected Friday21:04
ttx#info Neutron, Swift, Horizon expected early next week21:04
*** banix has joined #openstack-meeting21:04
stevebakerand heat21:04
ttx#info Heat also expected early next week21:04
ttxI think I have everyone21:05
*** dcramer_ has quit IRC21:05
ttxThat also doubles as dates we expect to open Juno development on21:05
ttxand un-feature-freeze the frozen projects21:05
*** bdpayne has joined #openstack-meeting21:06
ttxThen if new release-critical issues are found we open RC windows and spin new release candidates21:06
ttx...until release day21:06
dolphmusing backports from master to milestone-proposed?21:06
ttxdolphm: exactly21:07
*** aysyd has quit IRC21:07
ttxThat's why it's important to nail the release-critical bugs now. After, it's more painful to do so with backports and reviewers distracted by Juno21:07
*** pdmars has quit IRC21:07
ttx(nothing impossible, just more painful)21:07
ttxQuestions on that ?21:08
dolphm++ everyone is chomping at the bit to land changes for juno21:08
hub_capunderstatement :)21:08
ttx#topic Dependency freeze21:08
*** openstack changes topic to "Dependency freeze (Meeting topic: project)"21:08
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2014-March/030729.html21:08
*** shakayumi has joined #openstack-meeting21:08
ttxIn summary we'll soft-freeze openstack/requirements changes to master until we cut all the RC1s21:08
*** joshuamckenty has quit IRC21:09
ttxAt which point we'll cut a milestone-proposed branch there for release branches to consume21:09
*** Leonr has joined #openstack-meeting21:09
*** shakayumi has quit IRC21:09
ttxWe are cleaning up the requirements-core group and will make sure the core reviewers are aware of this policy21:09
sdagueyeh, I think everything that we need for the release besides the saraha client change is in21:09
sdagueso I'd recommend no other changes at this point unless there is an rc bug they are attached to21:09
ttxyes, will send an email about this early tomorrow to requirements-core21:10
ttxQuestions on that ?21:10
dolphmi haven't gotten a clear understand of how this affects dependencies ON clients21:10
dolphmspecifically, horizon's dependency on a minimum keystoneclient version?21:11
sdaguedolphm: that should be frozen at this point21:11
sdagueunless it's an rc bug21:11
*** shakamunyi has quit IRC21:11
dolphmi believe there's an RC bug for this issue21:11
ttxdolphm: I think david-lyle un-RCed it21:11
ttxthe change password thing ?21:12
dolphmregardless, it'd be an exception if we release a keystoneclient tomorrow (0.7.0) and horizon wanted to require it?21:12
dolphmttx: yes21:12
sdaguedolphm: yes21:12
ttxdolphm: I would consider that an exception yes21:12
sdaguebecause that forces the new version on everyone21:12
dolphmttx: i think the RC target got restored this afternoon21:12
*** rfolco has quit IRC21:12
ttxwe must just weigh the benefits with the drawbacks, and make sure packagers are aware of it21:12
*** sridhar has quit IRC21:12
ttxdolphm: hah!21:12
ttxthings happen while I have dinner21:12
sdaguedolphm: so the minimum client issue is something we need a better story on21:13
dolphm#link https://bugs.launchpad.net/horizon/+bug/123975721:13
uvirtbotLaunchpad bug 1239757 in python-keystoneclient "Let users update their own password with Identity API v3" [Wishlist,Fix committed]21:13
dhellmannttx: the sun never sets on openstack21:13
dolphmsdague: ++21:13
sdaguebecause it seems like every time there is a client bump, everyone wants to pull up min version21:13
sdagueeven if it will work perfectly fine with the old version21:13
*** ildikov_ has joined #openstack-meeting21:13
sdagueor as fine as it used to, with known bugs21:13
ttxsdague: in that case it probably wouldn't, but agree on the general case21:14
sdaguesure so this is a major bump21:14
ttxthis is the first time we do this freeze, so there may be some rough edges and dark areas left21:14
dolphmsdague: generally, i assume the community wants to consume new client features across projects, right?21:14
sdaguedolphm: sure, but you can let users upgrade21:14
sdaguewe don't dump the min on sqla every time a new release comes out21:15
ttxsdague: they want to rely on a new feature of the client and expose it -- it's even arguably a feature21:15
ttxsdague: which is why I supported un-RCing it21:15
dolphmconversely, i could see keystoneclient wanting to *push* new features to be consumed by other projects (say, a new implementation of something under the hood)21:15
sdaguettx: relying on a new feature is a different thing21:15
sdagueand actually something we shouldn't be doing at this point in the cycle21:15
ttxthat said it's really a gap with some security impact21:15
ttxso it's a bit grey21:15
ttxdavid-lyle: around ?21:15
david-lylethis would be nice functionality to have in Horizon for Icehouse, but we've supported keystone v3 since Havana without it21:16
dolphmttx: i'd like to understand the less-gray area first :)21:16
ttxdavid-lyle: would you consider it a new feature ?21:16
dolphmi mean, keystoneclient 0.7.0 is coming this week whether horizon requires it or not21:16
david-lyleit's a descrepency between v2.0 and v321:17
*** noslzzp has quit IRC21:17
dolphmttx: technically, it's restoring a feature that was available in grizzly21:17
ttxdolphm: and it will contain a security fix that everyone will want to have anyway21:17
dolphmttx: ++21:17
ttxso in that case the min dep bump might be warranted for security reasons21:17
*** Duane has quit IRC21:17
david-lylebut we won't enable it without bumping the required client version21:17
sdaguedavid-lyle: and there is no way to conditionally support it?21:18
ttxI think in that case we'll just accept the bump, but it's a bit of a special case (new version to close a CVE)21:18
dolphmif keystoneclient.__version__ > (0, 7) ?21:18
dhellmanndavid-lyle: are you checking the version of the installed client to see whether to enable it, or are you removing the code if the version doesn't go up?21:18
sdaguedolphm: yeh21:18
*** doug_shelley66 has quit IRC21:18
david-lylewe have the functionality blocked now, would reenable21:18
david-lylewe could add such a check if that's what it comes down to21:19
ttxanyway, let's move on. By thursday everything should be clearer there21:20
ttxdolphm: let's try this and come up with updated rules once we're done21:20
dolphmttx: ack21:21
ttx#topic keystone v3 and plans for v2 (and how that affects other projects)21:21
*** openstack changes topic to "keystone v3 and plans for v2 (and how that affects other projects) (Meeting topic: project)"21:21
ttxrussellb: floor is yours21:21
*** jmontemayor has joined #openstack-meeting21:21
russellbah yes21:21
russellbso there was confusion in our last nova meeting, so i figured i'd bring it up here21:21
russellbi was able to catch up with dolphm a bit async from that21:21
*** lblanchard has quit IRC21:21
russellbbut basically, there was confusion about the lifecycle of the keystone APIs and what it meant for projects like nova21:22
russellbv2 deprecated?  if so, what does that mean for other projects, as well as deployers?21:22
russellbis that written out anywhere?21:22
russellbbasically hoping dolphm can provide some clarity on what keystone folks have been thinking on this topic21:22
annegentleI share these concerns21:23
dolphmso, i think most of our strategy has gone undocumented so far, but our highest goal is to not break everyone :)21:23
david-lyleI'm concerned v2 is deprecated but v3 support is minimal21:23
sdaguedavid-lyle: similar concerns21:23
sdagueespecially as it moves us from something we test a ton in the gate21:23
russellbi have a general bad feeling toward ever calling something deprecated unless you have a very specific timeline defined for when it can go away21:24
dolphmat russellb's suggestion, i filed https://blueprints.launchpad.net/keystone/+spec/document-v2-to-v3-transition to follow up on that early in juno so we have something to share & talk about21:24
sdaguebeing unsupported, and something we only test a little being official21:24
dolphmsdague: deprecated != unsupported21:24
stevebakerfwiw, heat is fully on v321:24
dhellmanndolphm: is it "frozen" then?21:24
dolphmsdague: i consider v2 to be fully supported, and will continue to be fully supported until it's removed -- likely in pieces21:24
david-lylestevebaker: in the default domain only, I assume?21:24
russellbfrozen different than deprecated to me21:24
russellbsends a different message21:25
dolphmdhellmann: save for serious issues, yes21:25
dhellmannrussellb: right, I thought this might be a word-choice issue21:25
*** egallen has quit IRC21:25
russellbdhellmann: yeah, sounds like it could be ...21:25
dolphmrussellb: we freeze v3 at milestone 2 every cycle as well... so i agree21:25
stevebakerdavid-lyle: sort of, we also have a special domain and create a project per stack, and a user per (some) resources21:25
dhellmanndolphm: maybe frozen isn't quite right either -- you're just not adding new features to v2?21:26
russellbso, 1) v2 still fully supported, 2) no timeline yet for when v2 would go away21:26
russellbis that correct?21:26
dolphmdhellmann: correct21:26
dhellmannI would call that "normal". Why is it marked as deprecated?21:26
russellbheh21:26
morganfainbergrussellb, isn't the typical nomenclature, deprecated -> obsoleted -> removed?21:26
russellbwe typically use "deprecated" to mean that it has been replaced and is scheduled to go away21:27
dolphmrussellb: 1) correct 2) one of our motivations for deprecating v2 in icehouse was that A) v3 has parity with v2, B) that gives us two full releases until we have the option to *start* removing unused bits21:27
jogorussellb: Deprecated: v2 API is deprecated as of Icehouse in favor of v3 API and may be removed in K.21:27
jogohttp://logs.openstack.org/55/82255/4/gate/gate-tempest-dsvm-full/b819624/logs/screen-key.txt.gz?level=WARNING21:27
russellbi don't see how it could be called deprecated when the majority of openstack itself doesn't use the new thing yet21:27
dolphmi expect things like public-facing auth to be supported in some capacity for quite a while, even if under the hood it's just middleware rewriting requests for the v3 app21:27
russellbjust all sounds premature i guess21:28
russellband confusing21:28
devanandadolphm: is marking it deprecated more a way to encourage projects to start moving away from it, rather than indicate that projects have already done so?21:28
dolphmdevananda: ++21:28
*** ameade has quit IRC21:28
devanandai think that disticntion is confusing some people, since AIUI, nova uses the latter terminology21:29
russellbfwiw, i consider the primary burden of that move to be on keystone itself21:29
ttxdolphm: I think there are other ways to encourage openstack projects to move away from it21:29
jogoI think that is backwards21:29
russellbi don't think a stick is helpful here21:29
dolphmrussellb: agree21:29
ttxdeprecation is more for users we don't control21:29
ttxnot for projects we can encourage to move internally21:29
dolphmrussellb: fwiw, keystoneclient 0.7.0 will finally let us start replacing code in other clients/services with much less code that will likely be accepted by those projects :)21:29
*** mattgriffin has joined #openstack-meeting21:29
ttxI think we should have a cross-project workshop on aligning to latest versions of APIs internally21:30
ttxISTR other projects also being hit21:30
russellbso i think most people think of the status of the API as you describe it as not actually deprecated21:30
russellband we shouldn't call it that until we have a specific timeline for when *external* users will be affected21:30
annegentlestevebaker: can heat not use v2 due to a need for domains? or roles?21:30
russellbincluding a clear timeline and migration plan for them21:30
sdaguewell the current deprecation does state "may be removed in K"21:30
sdagueso that's pretty specific21:30
annegentlestevebaker: and how does heat use v3 when nova doesn't?21:30
sdagueperhaps we remove that part of the deprecation message at least?21:31
lifelessannegentle: you can use v2 and v3 concurrently21:31
david-lylehorizon had to back from having v3 as the default because of lack of cross service support21:31
annegentlelifeless: so it's a matter of service catalog config?21:31
lifelessannegentle: heat needs domains to let non-admins use waitconditions21:31
jogolifeless: only the v3 logic that was from v221:31
lifelessannegentle: yes, list both.21:31
ttxdolphm: I tend to agree with russellb on that one. Would rather remove the deprecation message and then advocate for v2->v3 moves at Juno design summit21:31
ttxthen deprecate when you want users of the Api (not internal services) to move on21:32
*** gokrokve has quit IRC21:32
sdagueat least until the official clients get support21:32
*** colinmcnamara has quit IRC21:32
*** thomasem has joined #openstack-meeting21:32
dolphmttx: on that note, what v2 *doesn't* have yet, is a way to advertise it's deprecated status to api end users -- i consider that a potential blocker to removing support later on that needs to be seriously considered21:32
dolphmfor example, a deprecated HTTP header in responses21:32
dolphmall the deprecation advertising we're doing is really only within the openstack community, and for deployers21:32
russellblargely a terminology / communication issue21:33
russellbdifferent uses of the terminology has caused some confusion here i think21:33
stevebakerannegentle: we need it for domains. There is a v2 shim which has the old limitation of requiring the stack launching user to be an admin21:33
russellbrequire it?21:33
russellbor can use it?21:33
russellbi think we've failed at some coordination here for some project(s) to require it, and others to not support it at all21:33
dolphm(lots of sudden IRC lag for me)21:33
russellbdolphm: same here21:33
ttxdolphm: same here21:33
ttxecho, too21:33
dhellmanndolphm: does any API have a way to advertise its deprecated status?21:34
annegentlestevebaker: lifeless: thanks, that's helpful21:34
stevebakerannegentle: the credentials we use in the non-default domain are only for a very few heat API operations (for nova server -> heat communication)21:34
ttxdolphm: if it's not targeted to users, should we remove that deprecation message ?21:34
david-lyleyou can't use non-default domain users with services that don't support v321:34
annegentledolphm: yes I think the user-facing communication needs to not mention deprecation21:34
dolphmdhellmann: i've seen proposals to alert clients at runtime, but haven't worked with anything functional myself21:34
dhellmanndolphm: ok, I wasn't sure if you were worried about following some sort of precedent21:35
*** banix has quit IRC21:35
ttxdavid-lyle: everything openstack should absolutely move to v3. But marking it deprecated for openstack admins to see won't really make that happen21:35
dhellmanndolphm: I do like the idea of communicating with the client somehow, fwiw21:35
russellbttx: i think that's the crux of this conversation21:35
jogottx: playing devils advocate here, why should we adopt keystone v3?21:35
ttxjogo: because users like things like domains ?21:36
david-lylemy argument is, you can't really use v3 fully so to mark v2.0 deprecated is flat wrong21:36
jogowhat benifits does it provide? (re: incentive vs stick)21:36
SergeyLukjanovjogo, trusts support21:36
dolphmttx: the deprecation message is still relevant... and i don't think it's doing any harm. the choice of language in it was fairly careful as well (*may* be removed)21:36
*** dkranz has quit IRC21:36
SergeyLukjanov(not related to domains)21:36
jogottx: what about the hierarchial militancy? thats what I want21:36
morganfainbergSergeyLukjanov, trusts are in V2.21:36
dolphmdhellmann: i'd love to have a precedent to follow, if there's a good one :-/21:36
dhellmanndolphm: how often does the deprecation message show up in logs?21:36
SergeyLukjanovmorganfainberg, oops21:37
dolphmdhellmann: should be once21:37
david-lylejogo: so move from v2 directly to v4 bypassing v3?21:37
dhellmanndolphm: no, but the sdk team might want to collaborate on setting up a protocol21:37
ttxdolphm: maybe "deprecated" is an overloaded term in that message21:37
russellbdolphm: thoughts on all this?  willing to drop the deprecation title for now to avoid the mass confusion?21:37
* russellb curses irc lag21:37
dolphmdhellmann: that'd be great21:37
jogoI bring this up becasue of the recent nova v3 discussion -- where we had trouble coming up with a strong reason to make a major API rev21:37
dolphmdhellmann: also great for a cross-project workshop :)21:37
dhellmanndolphm: +121:37
david-lyle+121:37
ttxdhellmann: one on API versions ?21:37
* dhellmann is looking forward to cross-project day in atlanta21:37
ttxin general ?21:37
morganfainbergdhellmann, ++21:38
dhellmannttx: on advertising api version deprecation21:38
dolphmrussellb: ttx: is there a better choice of words than "deprecated"?21:38
russellband what deprecation means?  :)21:38
dolphm"pending deprecation"?21:38
russellbi don't think it's actually deprecated based on the discussion21:38
ttx+1 for on API version deprecation in general21:38
russellbit's a fully supported thing even if you're not adding stuff21:38
russellbwe just have work to do across openstack to migrate to it21:38
dhellmannyeah, it really seems like it's "stable" and we're still doing v3 development21:38
ttxdhellmann: file while you think about it21:38
ttxdolphm: "we are migrating away" ?21:39
dhellmannttx: I'll leave that to dolphm, I don't want to run that session :-)21:39
morganfainbergdhellmann, i would classify v3 as stable, it is receiving new features, but it's not being broken.21:39
ttxit's almost 11pm here don't expect me to get creative21:39
morganfainbergdhellmann, stable, deprecated, etc all overloaded terms at this point21:39
russellband once *that* is done, we can talk deprecation21:39
russellbdeprecation means people outside of openstack itself have to take some action21:39
russellbsome migration path21:39
russellband i don't think we're quite at that point yet right?21:39
russellbi'm a little sore on marking things deprecated without a schedule to actually remove, i guess21:39
dolphmif there's a summit session on this, i'd like to start by defining "deprecated" :)21:39
dhellmannmorganfainberg: true21:39
devanandarussellb: ++21:40
ttxrussellb: ++21:40
*** codekobe has quit IRC21:40
dhellmannbut a schedule was given, right? K?21:40
jogodhellmann: heh yup21:40
ttxdhellmann: was it?21:40
dhellmannthe question is, is that a real schedule because the other projects are going to be ready?21:40
morganfainbergdhellmann, that is the default, it would be easy to change that.21:40
dolphmdhellmann: havana shipped v2 and v3 side by side, both being labeled as "stable" (grizzly may have too)21:40
morganfainbergdhellmann, (default is +2)21:40
jogottx "Deprecated: v2 API is deprecated as of Icehouse in favor of v3 API and may be removed in K."21:40
ttxbasically, the deprecation mechanism woirks for end user migration, not so well for internal API migration21:41
jogohttp://logs.openstack.org/55/82255/4/gate/gate-tempest-dsvm-full/b819624/logs/screen-key.txt.gz?level=WARNING21:41
russellbok well step back, we need to remove that schedule21:41
russellbbecause if stuff isn't migrated, that's unreasonable21:41
russellbIMO21:41
dhellmannit sounds like what we're asking is for the keystone team to *not* deprecate the V2 API until the rest of us are consuming it21:41
dhellmannand so we need to see about making *that* a priority21:41
ttxinternal API migration has to happen prior to user-side deprecation21:41
jogodhellmann russellb: ++21:41
jogothat is the model glance is taking as well21:41
jogothey are deprecating old API after nova switches over21:42
devanandai was just trying to word that well21:42
devanandaseems odd for keystone to set a schedule before other projects have migrated21:42
* markwash nods21:42
*** eharney has quit IRC21:42
ttxdevananda: hence the "may"21:42
ttxdevananda: because they have no real control over that21:42
devanandathe deprecation message is telling users "you need to migrate by K becayse we may remove it"21:42
*** jeblair_ has joined #openstack-meeting21:42
ttxwhich is why I think internal API migration has to happen prior to user-side deprecation21:42
*** tsekiyama has joined #openstack-meeting21:42
morganfainbergdhellmann, i lied, can't remove the "removed in" part, need to update oslo-incubator for that.21:43
*** tris- has joined #openstack-meeting21:43
morganfainbergdhellmann, sorry.21:43
ttxbecause otherwise you just can't have a realistic schedule21:43
*** jeblair_ is now known as corvus21:43
morganfainbergdhellmann, easy fix in either case.21:43
dhellmannmorganfainberg: we can update the incubator :-)21:43
morganfainbergdhellmann, yesh.21:43
ttxrussellb: looks like you could argue that in a thread, I'm pretty sure there will be suggestions of alternate wording there21:43
*** IlyaE has joined #openstack-meeting21:43
ttxrussellb: it's kind of urgent though since keystone was about to tag RC1 tomorrow21:44
*** olkonami has left #openstack-meeting21:44
*** alexpilotti has joined #openstack-meeting21:44
ttxmarkwash: your input for how you do glance will be wanted on that thread -- consistency is good21:44
markwashsounds fair21:44
dhellmannmorganfainberg: I'd even consider a concurrent change, rather than changing the incubator and then syncing21:44
morganfainbergdhellmann, ++21:45
morganfainbergdhellmann, was going to recommend that for ease of getting this through for RC.21:45
*** codekobe has joined #openstack-meeting21:45
dolphmrussellb: is K* not a reasonable schedule?21:45
* dolphm is about to give up due to IRC lag21:45
dhellmannmorganfainberg: just mention it in the commit message21:45
russellbi think a documented migration plan + implementation of replacement across openstack is a prerequisite to setting that timeline21:45
*** jeblair has quit IRC21:45
*** tris has quit IRC21:45
*** tris- is now known as tris21:45
*** marcoemorais1 has joined #openstack-meeting21:45
dhellmannrussellb: +121:45
lifelessdolphm: its not reasonable to spam operator logs for a year21:45
*** corvus is now known as jeblair21:45
jogorussellb: +121:45
markwashin that vain I'm a bit concerned about running "both v2 and v3 in the catalog" since that seems. . inconsistent with what glance is doing. . but that's a different can of worms21:45
lifelessdolphm: whether the timeframe is reasonable is entirely separate21:45
ttxHopefully we'll get better at communicating cross-project priorities -- classic deprecation mechanism is not the way to push internal API migrations imho21:46
markwashand maybe I'm confused21:46
ttxrussellb: continue on ML thread ?21:46
*** jbryce has quit IRC21:47
*** russellb has quit IRC21:47
*** metral has quit IRC21:47
*** doug_shelley66 has joined #openstack-meeting21:47
ttxah, we lost russell21:47
*** MineHarry01 has joined #openstack-meeting21:47
ttxok, let's quickly move on21:47
*** zigo has quit IRC21:47
*** wendar has quit IRC21:47
*** jbryce has joined #openstack-meeting21:47
*** marcoemorais has quit IRC21:47
*** dolphm has quit IRC21:47
dhellmannttx: that reminds me, I do have something to mention quickly when we get to open discussion21:48
ttx#action russellb to quickly start a thread on keystone v2 deprecation21:48
*** MineHarry01 has left #openstack-meeting21:48
ttxquick let's action russellb and dolphm on plenty of things21:48
morganfainbergttx ++21:48
ttxas lonas the bot is on my side of the split21:48
*** russellb has joined #openstack-meeting21:48
ttxarh, he's back21:48
ttxrussellb: fyi #action russellb to quickly start a thread on keystone v2 deprecation21:48
*** mwagner_lap has quit IRC21:49
ttx#topic Red Flag District / Blocked blueprints21:49
*** openstack changes topic to "Red Flag District / Blocked blueprints (Meeting topic: project)"21:49
*** jmh_ has quit IRC21:49
ttxAny other inter-project blocked work that this meeting could help unblock ?21:49
*** metral has joined #openstack-meeting21:49
dhellmannis anyone waiting on anything to land in oslo-incubator?21:49
*** wendar has joined #openstack-meeting21:49
*** zigo has joined #openstack-meeting21:49
ttxthat's a good one21:49
* russellb stabs IRC21:49
russellbI got the action21:49
*** dolphm has joined #openstack-meeting21:50
ttxdolphm: fwiw we moved to next topic, russell will start a thread asap to continue the discussion21:51
ttxnetsplit rt: Any other inter-project blocked work that this meeting could help unblock ?21:51
ttxnetsplit rt: <dhellmann> is anyone waiting on anything to land in oslo-incubator?21:51
dhellmannesp. oslo-incubator changes21:51
ttxLooks like not21:51
jogodhellmann: https://review.openstack.org/#/c/82675/21:52
jogojust responded to your comment as well21:52
sdaguejogo: did you get the oslo.messaging log=INFO patches around?21:52
dhellmannjogo: ack21:52
markwashI think we got our oslo-db utf8 stuff in, so glance is good AFAICT21:52
dhellmannjogo: +2 and sent to the rest of oslo-core for review21:52
jogosdague: nova landed, cinder and ceilo are pending .. neutron doesn't use oslo.messaging yet21:53
ttxOh, makes me think21:53
sdagueok21:53
jogodhellmann: thank you21:53
ttxAll: don't forget to sync relatively recent translations before cutting RC1s21:53
stevebakerheat not using oslo.messaging yet21:53
*** lukego has quit IRC21:54
ttxdolphm: do you have translations merges in keystone ?21:54
jogoso I am a bit concerned about ceilometer's polling of APIs  ( http://openstack-in-production.blogspot.com/2014/03/cern-cloud-architecture-update-for.html )21:54
ttxdolphm: answering my own quetsion: https://review.openstack.org/#/c/78525/21:55
ttxjogo: maybe that would make a valid bug to bring to ceilo folks attention21:56
ttxjogo: not sure it's been turned into a bug yet though21:56
dhellmannttx: +121:56
* jogo files a bug 21:56
ttxjogo: ping jd__ when done and start discussion there ?21:57
ttxit's not completely too late yet :)21:57
* ttx quickly moves on21:57
ttx#topic Incubated projects21:57
*** openstack changes topic to "Incubated projects (Meeting topic: project)"21:57
sdaguehonestly, I think it's too late to work on that for release :)21:57
SergeyLukjanovo/21:57
SergeyLukjanovre sahara https://launchpad.net/sahara/+milestone/icehouse-rc121:57
ttxdevananda, SergeyLukjanov, kgriffs: o/21:57
SergeyLukjanovrenaming finished, we'll be ready for rc1 next week21:57
*** caleb_ has quit IRC21:57
ttxyou still have a couple weeks before you really need to cut RC1s21:58
ttxbut as always the sooner the better21:58
SergeyLukjanovttx, yup, I think next week should be ok, Thu is the plan21:58
*** thomasem has quit IRC21:58
SergeyLukjanovttx, Apr 321:58
ttxjust ping me when you want them21:58
ttxi'll be around21:58
SergeyLukjanovttx, yup, thank you21:58
ttx#topic Open discussion21:58
*** openstack changes topic to "Open discussion (Meeting topic: project)"21:58
*** topol has joined #openstack-meeting21:58
ttxanything anyone?21:59
*** ivasev has quit IRC21:59
dhellmannI plan to send a message to the ML tomorrow about the plan for oslo library releases in juno21:59
dhellmann#link https://wiki.openstack.org/wiki/Oslo/JunoGraduationPlans21:59
SergeyLukjanovdhellmann, sounds interesting22:00
ttxwow more complex than I'd have thought :)22:00
*** caleb_ has joined #openstack-meeting22:00
*** stevemar has quit IRC22:00
dhellmannthere are still some issues to resolve about alpha releases, but I think we have everything else worked out22:00
ttxdhellmann: sounds good (the message)22:00
SergeyLukjanovttx, ++22:00
kgriffsttx: we are close on rc1, have one more bug that I am checking on22:00
kgriffsit may slip to juno22:00
*** markmc has quit IRC22:01
ttxkgriffs: you have plenty of time, your callreally22:01
ttxok, we need to clear the room22:01
ttxthanks everyone!22:01
ttx#endmeeting22:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:01
openstackMeeting ended Tue Mar 25 22:01:35 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2014/project.2014-03-25-21.01.html22:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2014/project.2014-03-25-21.01.txt22:01
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2014/project.2014-03-25-21.01.log.html22:01
russellbthanks ttx22:01
*** bknudson has quit IRC22:03
*** RobinJoe has joined #openstack-meeting22:04
*** RobinJ has joined #openstack-meeting22:04
*** armax has quit IRC22:05
*** stevemar has joined #openstack-meeting22:06
*** zehicle_at_dell has quit IRC22:06
*** zehicle_at_dell has joined #openstack-meeting22:08
*** shwetaap has quit IRC22:09
*** tjones has left #openstack-meeting22:09
*** kevinconway has quit IRC22:11
*** markwash_ has joined #openstack-meeting22:12
*** sushils has joined #openstack-meeting22:13
*** markwash has quit IRC22:14
*** markwash_ is now known as markwash22:14
*** mattgriffin has quit IRC22:14
*** schwicht has joined #openstack-meeting22:15
*** alazarev has quit IRC22:16
*** devlaps1 has quit IRC22:17
*** changbl has quit IRC22:17
*** caleb_ has quit IRC22:17
*** devlaps has joined #openstack-meeting22:17
*** dims_ has quit IRC22:18
*** alazarev has joined #openstack-meeting22:18
*** alazarev has quit IRC22:18
*** zns has joined #openstack-meeting22:19
*** mattgriffin has joined #openstack-meeting22:20
*** alazarev has joined #openstack-meeting22:20
*** prad has quit IRC22:22
*** alazarev has quit IRC22:22
*** Leonr has quit IRC22:23
*** alex-sick is now known as Alexandra22:24
*** balajiiyer has joined #openstack-meeting22:24
*** IlyaE has quit IRC22:24
*** zns has quit IRC22:25
*** zns has joined #openstack-meeting22:25
*** neelashah1 has quit IRC22:26
*** Leonr has joined #openstack-meeting22:27
*** balajiiyer has quit IRC22:28
*** ttrifonov is now known as ttrifonov_zZzz22:29
*** Swami has quit IRC22:30
*** Gordonz has quit IRC22:31
*** ItSANg___ has joined #openstack-meeting22:32
*** ItSANg___ has quit IRC22:33
*** dims_ has joined #openstack-meeting22:34
*** tanisdl has quit IRC22:34
*** ItS______ has joined #openstack-meeting22:34
*** ItSANgo has quit IRC22:35
*** Leonr has quit IRC22:43
*** jergerber has quit IRC22:44
*** denis_makogon has quit IRC22:46
*** colinmcnamara has joined #openstack-meeting22:48
*** colinmcnamara has quit IRC22:48
*** mattgriffin has quit IRC22:51
*** mdurnosvistov_ has quit IRC22:51
*** fawadkhaliq has joined #openstack-meeting22:52
*** henrynash has quit IRC22:53
*** jpeeler has quit IRC22:54
*** banix has joined #openstack-meeting22:54
*** zoresvit has quit IRC23:00
*** epim has quit IRC23:01
*** _1_overlayer has joined #openstack-meeting23:01
*** mwagner_lap has joined #openstack-meeting23:02
*** MaxV has joined #openstack-meeting23:02
*** _1_overlayer has quit IRC23:04
*** cdub has quit IRC23:05
*** MaxV has quit IRC23:05
*** david-lyle has quit IRC23:08
*** markmcclain has joined #openstack-meeting23:10
*** markmcclain1 has joined #openstack-meeting23:11
*** erlon has quit IRC23:12
*** thang_ has quit IRC23:12
*** otherwiseguy has quit IRC23:13
*** ArxCruz has joined #openstack-meeting23:13
*** markmcclain has quit IRC23:15
*** rockyg has quit IRC23:16
*** eglynn has quit IRC23:17
*** thedodd has quit IRC23:17
*** ArxCruz has quit IRC23:17
*** thuc_ has quit IRC23:18
*** thuc has joined #openstack-meeting23:18
*** andreaf has quit IRC23:22
jgriffithwindow 2223:22
*** thuc has quit IRC23:23
*** krtaylor has quit IRC23:23
*** ArthurBerezin has joined #openstack-meeting23:24
*** henrynash has joined #openstack-meeting23:24
*** jgrimm has quit IRC23:25
*** julim has quit IRC23:30
hub_capjgriffith: i think u forgot your slash23:30
*** markmcclain1 has quit IRC23:30
*** banix has quit IRC23:33
*** bdpayne_ has joined #openstack-meeting23:33
*** caleb_ has joined #openstack-meeting23:33
*** bdpayne has quit IRC23:34
*** jmontemayor has quit IRC23:35
*** sushils has quit IRC23:41
*** baoli has joined #openstack-meeting23:46
*** whenry has joined #openstack-meeting23:50
*** cdub has joined #openstack-meeting23:50
*** devlaps1 has joined #openstack-meeting23:50
*** brucer has joined #openstack-meeting23:51
*** noslzzp has joined #openstack-meeting23:51
*** devlaps has quit IRC23:53
*** mwagner_ has joined #openstack-meeting23:54
*** lcheng has quit IRC23:54
*** carl_baldwin has quit IRC23:57

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