Tuesday, 2014-10-28

*** MaxV has joined #openstack-meeting00:00
*** elo has quit IRC00:03
*** MaxV has quit IRC00:05
*** marcoemorais has joined #openstack-meeting00:06
*** marcoemorais has quit IRC00:07
*** roampune has quit IRC00:07
*** pritesh has quit IRC00:07
*** marcoemorais has joined #openstack-meeting00:07
*** dneary has joined #openstack-meeting00:12
*** stevemar has joined #openstack-meeting00:13
*** stevemar is now known as notstevemar00:13
*** mattgriffin has joined #openstack-meeting00:14
*** barclaac|2 has joined #openstack-meeting00:14
*** cjellick has quit IRC00:15
*** kebray has quit IRC00:16
*** oomichi has joined #openstack-meeting00:17
*** marcoemorais has quit IRC00:18
*** yassine has quit IRC00:18
*** barclaac has quit IRC00:18
*** rob_ has quit IRC00:21
*** noelbk has quit IRC00:23
*** padkrish_ has quit IRC00:23
*** noelbk has joined #openstack-meeting00:24
*** weshay has joined #openstack-meeting00:24
*** dt has quit IRC00:24
*** bhavdiddy has quit IRC00:26
*** bhavdiddy has joined #openstack-meeting00:27
*** s3wong has quit IRC00:28
*** rmoe has quit IRC00:28
*** mtanino has quit IRC00:29
*** SridharRamaswamy has quit IRC00:30
*** Gabriel_ has joined #openstack-meeting00:30
*** mattgriffin has quit IRC00:31
*** bhavdiddy has quit IRC00:31
*** marcoemorais has joined #openstack-meeting00:32
*** achanda has quit IRC00:32
*** Gabriel_ is now known as Gabriel_Laupre00:32
*** achanda has joined #openstack-meeting00:33
*** amcrn has quit IRC00:33
*** ayoung-dadmode is now known as ayoung00:33
*** marcoemorais has quit IRC00:36
*** Tross has quit IRC00:37
*** achanda has quit IRC00:37
*** padkrish has joined #openstack-meeting00:40
*** Tross has joined #openstack-meeting00:41
*** markwash__ has quit IRC00:41
*** yamamoto has joined #openstack-meeting00:41
*** glebo has quit IRC00:41
*** markwash__ has joined #openstack-meeting00:45
*** bhavdiddy has joined #openstack-meeting00:45
*** yamamoto has quit IRC00:46
*** david-lyle has joined #openstack-meeting00:46
*** fnaval has quit IRC00:47
*** IanGovett has quit IRC00:47
*** ignacio-scopetta has joined #openstack-meeting00:48
*** rmoe has joined #openstack-meeting00:49
*** ignacio-scopett1 has quit IRC00:50
*** Tross has quit IRC00:51
*** david-lyle has quit IRC00:51
*** elo has joined #openstack-meeting00:51
*** sarob has joined #openstack-meeting00:51
*** sarob has quit IRC00:52
*** sarob has joined #openstack-meeting00:53
*** yamahata has joined #openstack-meeting00:53
*** Mandell has quit IRC00:55
*** vijendar has quit IRC00:56
*** sarob has quit IRC00:58
*** markwash__ has quit IRC00:59
*** padkrish has quit IRC00:59
*** badveli has quit IRC01:03
*** barclaac has joined #openstack-meeting01:04
*** oanufriev has quit IRC01:04
*** fnaval has joined #openstack-meeting01:06
*** barclaac|2 has quit IRC01:07
*** dneary has quit IRC01:07
*** freemanbrandon has joined #openstack-meeting01:10
*** noslzzp has quit IRC01:13
*** Longgeek has joined #openstack-meeting01:13
*** vivek-ebay has quit IRC01:16
*** baoli has joined #openstack-meeting01:16
*** julim has quit IRC01:17
*** Longgeek has quit IRC01:17
*** leeantho has quit IRC01:18
*** topol has joined #openstack-meeting01:22
*** MeganR has joined #openstack-meeting01:24
*** MeganR has quit IRC01:25
*** david-lyle has joined #openstack-meeting01:31
*** david-lyle has quit IRC01:36
*** vkmc has joined #openstack-meeting01:37
*** jdurgin1 has quit IRC01:38
*** haomaiwa_ has joined #openstack-meeting01:46
*** scotm has joined #openstack-meeting01:48
*** weshay has quit IRC01:51
*** rob_ has joined #openstack-meeting01:54
*** xuhanp has joined #openstack-meeting01:54
*** haomaiwa_ has quit IRC01:55
*** haomaiwang has joined #openstack-meeting01:56
*** nosnos has joined #openstack-meeting01:59
*** bhavdiddy has quit IRC02:07
*** ramishra has joined #openstack-meeting02:09
*** freemanbrandon has quit IRC02:11
*** baoli has quit IRC02:13
*** BrianB_ has quit IRC02:18
*** vivek-ebay has joined #openstack-meeting02:19
*** rfolco has quit IRC02:19
*** VijayTripathi has quit IRC02:19
*** VijayTripathi has joined #openstack-meeting02:20
*** bdpayne has joined #openstack-meeting02:22
*** bdpayne has quit IRC02:22
*** notstevemar has quit IRC02:24
*** mberlin1 has joined #openstack-meeting02:24
*** VijayTripathi has quit IRC02:24
*** mberlin has quit IRC02:24
*** emagana has joined #openstack-meeting02:26
*** ivar-laz_ has joined #openstack-meeting02:30
*** sankarshan is now known as sankarshan_away02:32
*** rfolco has joined #openstack-meeting02:33
*** ivar-lazzaro has quit IRC02:34
*** david-lyle has joined #openstack-meeting02:36
*** ivar-laz_ has quit IRC02:39
*** alex_xu has joined #openstack-meeting02:39
*** david-lyle has quit IRC02:41
*** marun_ has quit IRC02:42
*** epico has joined #openstack-meeting02:43
*** dims_ has quit IRC02:44
*** vivek-ebay has quit IRC02:45
*** sgordon_ has quit IRC02:47
*** dims__ has joined #openstack-meeting02:47
*** vijendar has joined #openstack-meeting02:49
*** dims__ has quit IRC02:49
*** fnaval has quit IRC02:53
*** fnaval has joined #openstack-meeting02:53
*** liusheng has quit IRC02:55
*** liusheng has joined #openstack-meeting02:56
*** vijendar has quit IRC02:56
*** dguitarbite has quit IRC02:56
*** yamamoto_ has joined #openstack-meeting02:56
*** sarob has joined #openstack-meeting02:56
*** dguitarbite has joined #openstack-meeting02:57
*** vkmc has quit IRC02:59
*** timrc is now known as timrc-afk02:59
*** sarob has quit IRC03:01
*** alex_xu has quit IRC03:01
*** tsekiyam_ has joined #openstack-meeting03:02
*** Mandell has joined #openstack-meeting03:02
*** emagana has quit IRC03:03
*** emagana has joined #openstack-meeting03:04
*** spzala has joined #openstack-meeting03:04
*** alexpilotti has quit IRC03:04
*** killer_prince is now known as lazy_prince03:06
*** tsekiyama has quit IRC03:06
*** alexpilotti has joined #openstack-meeting03:06
*** tsekiyam_ has quit IRC03:07
*** imsurit has joined #openstack-meeting03:07
*** alexpilotti has quit IRC03:07
*** ignacio-scopetta has quit IRC03:09
*** emagana has quit IRC03:09
*** markvoelker1 has quit IRC03:09
*** alexpilotti has joined #openstack-meeting03:10
*** ignacio-scopetta has joined #openstack-meeting03:10
*** sunil_ has quit IRC03:11
*** alexpilotti has quit IRC03:11
*** alexpilotti has joined #openstack-meeting03:12
*** alexpilotti has quit IRC03:12
*** alex_xu has joined #openstack-meeting03:13
*** alexpilotti has joined #openstack-meeting03:14
*** armax has quit IRC03:14
*** spzala has quit IRC03:15
*** armax has joined #openstack-meeting03:15
*** liusheng has quit IRC03:15
*** alexpilotti has quit IRC03:16
*** liusheng has joined #openstack-meeting03:17
*** JRobinson__ is now known as JRobinson__afk03:19
*** Longgeek has joined #openstack-meeting03:21
*** freemanbrandon has joined #openstack-meeting03:22
*** ddieterly has quit IRC03:23
*** ddieterly has joined #openstack-meeting03:24
*** emagana has joined #openstack-meeting03:25
*** Longgeek has quit IRC03:26
*** nelsnelson has quit IRC03:26
*** freemanbrandon has quit IRC03:26
*** haomai___ has joined #openstack-meeting03:27
*** harlowja is now known as harlowja_away03:27
*** ddieterly has quit IRC03:28
*** haomaiwang has quit IRC03:30
*** harlowja_away is now known as harlowja03:30
*** MaxV has joined #openstack-meeting03:33
*** sankarshan_away is now known as sankarshan03:35
*** mattoliverau has quit IRC03:35
*** zns has joined #openstack-meeting03:35
*** mattoliverau has joined #openstack-meeting03:35
*** nosnos has quit IRC03:36
*** nosnos has joined #openstack-meeting03:37
*** MaxV has quit IRC03:37
*** wwallnrr__ has quit IRC03:38
*** mattoliverau has quit IRC03:38
*** Poornima has joined #openstack-meeting03:38
*** miqui has quit IRC03:38
*** mattoliverau has joined #openstack-meeting03:39
*** marcoemorais has joined #openstack-meeting03:40
*** nosnos has quit IRC03:41
*** fnaval has quit IRC03:43
*** terryw has quit IRC03:43
*** fnaval has joined #openstack-meeting03:44
*** marcoemorais has quit IRC03:48
*** fnaval has quit IRC03:48
*** otherwiseguy has joined #openstack-meeting03:50
*** dims__ has joined #openstack-meeting03:50
*** VijayTripathi has joined #openstack-meeting03:51
*** VijayTripathi1 has joined #openstack-meeting03:54
*** dims__ has quit IRC03:55
*** ddieterly has joined #openstack-meeting03:56
*** VijayTripathi1 has quit IRC03:57
*** VijayTripathi has quit IRC03:57
*** ddieterly has quit IRC04:01
*** achanda has joined #openstack-meeting04:01
*** ayoung has quit IRC04:04
*** zns has quit IRC04:06
*** david-lyle has joined #openstack-meeting04:06
*** zns has joined #openstack-meeting04:06
*** gyee has joined #openstack-meeting04:11
*** JRobinson__afk is now known as JRobinson__04:12
*** tsekiyama has joined #openstack-meeting04:13
*** AzherKhan has joined #openstack-meeting04:14
*** nosnos has joined #openstack-meeting04:15
*** Khaazher has joined #openstack-meeting04:16
*** Khaazher has quit IRC04:17
*** tsekiyama has quit IRC04:17
*** fnaval has joined #openstack-meeting04:18
*** armax has quit IRC04:20
*** scotm has quit IRC04:22
*** bthurber has quit IRC04:25
*** ramishra has quit IRC04:25
*** ngoswami has joined #openstack-meeting04:27
*** vsilva is now known as victsou04:28
*** rajeshr has joined #openstack-meeting04:31
*** paragan has joined #openstack-meeting04:33
*** MaxV has joined #openstack-meeting04:34
*** victsou is now known as vsilva04:35
*** vivek-ebay has joined #openstack-meeting04:35
*** otherwiseguy has quit IRC04:37
*** MaxV has quit IRC04:38
*** epico has quit IRC04:42
*** stevemar has joined #openstack-meeting04:44
*** epico has joined #openstack-meeting04:47
*** rajeshr has quit IRC04:49
*** ppai has joined #openstack-meeting04:49
*** ngoswami has quit IRC04:50
*** ramishra has joined #openstack-meeting04:52
*** sarob has joined #openstack-meeting04:54
*** mrmartin has joined #openstack-meeting04:54
*** achanda has quit IRC04:54
*** vivek-ebay has quit IRC04:55
*** achanda has joined #openstack-meeting04:56
*** s3wong has joined #openstack-meeting04:56
*** sarob has quit IRC04:58
yamahatahello05:00
*** natarajk has joined #openstack-meeting05:01
s3wonghello05:01
natarajkhi05:01
yamahata#startmeeting servicevm-device-manager05:02
openstackMeeting started Tue Oct 28 05:02:10 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: servicevm-device-manager)"05:02
openstackThe meeting name has been set to 'servicevm_device_manager'05:02
yamahatabob doesn't seem here...05:02
yamahataanyway05:02
yamahata#topic Announcement05:02
*** openstack changes topic to "Announcement (Meeting topic: servicevm-device-manager)"05:03
yamahata#info neutron session schedule is announce05:03
yamahata#link http://kilodesignsummit.sched.org/overview/type/neutron#.VE7A73WUd1y05:03
yamahataThere is a session for LT.05:03
yamahataLT poll page is created05:03
s3wongtacker will be discussed (hopefully) here: http://kilodesignsummit.sched.org/event/8a0b7c1d64883c08286e4446e163f1a6#.VE8jjJPF9j405:03
yamahata#link https://www.surveymonkey.com/s/RLTPBY605:03
s3wong#link http://kilodesignsummit.sched.org/event/8a0b7c1d64883c08286e4446e163f1a6#.VE8jjJPF9j405:04
yamahatas3wong: thanks for link.05:04
*** sdake_ has joined #openstack-meeting05:04
*** simon-AS559 has joined #openstack-meeting05:04
s3wonghow does tacker affect Neutron advanced services? and how will advanced services' inevitable spinning out affect tacker?05:04
yamahata#link http://kilodesignsummit.sched.org/event/8a0b7c1d64883c08286e4446e163f1a6#.VE8jjJPF9j4 Advanced Services Spin Out servicevm project seems also subject to discuss05:04
s3wongI think those are some discussion points we need to prepare before that session05:05
yamahatas3wong: +105:05
yamahataLet's discuss at open discussion.05:05
*** nelsnelson has joined #openstack-meeting05:06
s3wongyamahata: sure05:06
yamahataany other to annouce?05:06
*** aepifanov has joined #openstack-meeting05:06
yamahataokay, let's move on05:07
yamahata#topic Action Items from the last week05:07
*** openstack changes topic to "Action Items from the last week (Meeting topic: servicevm-device-manager)"05:07
*** manishg has joined #openstack-meeting05:07
yamahataI created poll page for servicevm time slot poll.05:08
yamahataand announce it on ML05:08
yamahataThe current best candidate seems Tue.05:08
yamahataGiven Advanced service spin out session is Thursday, November 6 • 11:50 - 12:30, the lunch after the session is also good candidate.05:09
*** manishg_ has joined #openstack-meeting05:09
yamahataMaybe we can have more than one meeting.05:09
natarajkthursday sounds better for me05:10
s3wongyamahata: Tuesday @12:05pm I need to attend the Group-based-policy design session (as does several people who care about services)05:10
yamahataOkay, I revised the page. Thursday Lunch time is best.05:11
*** manishg__ has joined #openstack-meeting05:11
*** manishg has quit IRC05:11
*** Hareesh has joined #openstack-meeting05:12
yamahataLet's schedule it on Thu 6 1:15 for now.05:12
yamahataIf it conflicts with NFV or something, rethink at that time.05:12
s3wongyamahata: right after the advanced service spin-off session?05:12
yamahata#info servicevm BoF on Thursday 6 1:15pm-05:12
s3wongyamahata: trying to catch those that are interested in continuing the conversation? :-)05:13
yamahatas3wong: Yes. So that we can catch other candidate hopefully05:13
*** manishg has joined #openstack-meeting05:13
*** bill_az has joined #openstack-meeting05:13
*** manishg_ has quit IRC05:14
yamahataDo we want to have another BoF before the session?05:14
*** manishg__ has quit IRC05:15
s3wongyamahata: perhaps we want to do some cross-project stuff with NFV (Tuesday has a lot of cross-project workshop)05:15
s3wong?05:15
s3wongyamahata: though at this point I haven't found anything on NFV actually having work on project (other than proposing stuff)05:16
s3wongyamahata: another possibility is to work with Neutron advanced services folks on "cross-project" session to see how we can create a common framework05:16
yamahatas3wong: sounds good idea.05:17
yamahataAt this point, I don't see which slot for cross project is NFV-related.05:17
yamahataProbably we will recognize it there.05:18
yamahatas3wong: I think at least VLAN trunking is driven as NFV requirement05:18
*** gyee has quit IRC05:19
yamahatawe could arrange  gathering ad-hoc way in Paris as usual.05:19
s3wongyamahata: definitely --- now closer into the summit, there was a lot of noise on the VLAN trunking piece05:19
s3wongmestery has made it one of Neutron Kilo priorities to gather requirements from NFV working grop05:20
s3wonggroup05:20
*** manishg has quit IRC05:20
*** fifieldt__ has quit IRC05:20
yamahatawe have 10min left. let's move on to discussion point05:21
yamahata#topic Open Discussion05:21
*** openstack changes topic to "Open Discussion (Meeting topic: servicevm-device-manager)"05:21
Hareeshyamahata: sorry a little late to this. have we agreed to a common time to meet in paris? what is the conclusion from the doodle?05:21
yamahataHareesh: For now it's planned on Thu 6 1:1505:21
*** markwash__ has joined #openstack-meeting05:21
s3wongyamahata: for open discussion, I would advocate reading the Neutron meeting log from today: http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-10-27-21.01.log.html05:22
yamahataAfter the session of Advanced Services Spin Out05:22
*** ramishra has quit IRC05:22
yamahatahttp://kilodesignsummit.sched.org/event/8a0b7c1d64883c08286e4446e163f1a6#.VE8jxXWUd1x05:22
s3wongsome discussion on advanced services spinoff05:22
yamahataservicevm stuff would be also discussed, so we can catch related people.05:22
Hareeshyamahata: thanks05:22
yamahata#action yamahata put meeting schedule at wiki and etherpad05:23
*** manishg has joined #openstack-meeting05:23
s3wongOur good friend from LBaaS side, dougwig, also mentioned something about having common framework for service VM (which the LBaaS is working on their own VM mgmt framework in Octavia)05:23
yamahatas3wong: cool.05:23
dougwigmy ears are burning.05:23
* s3wong thinks dougwig is really in Hawaii instead of Central timezone05:24
yamahataMy current thinking is that to create new project and to have other project use it would be difficult.05:24
*** ildikov has quit IRC05:24
yamahataAs a first tiny step, small library based on the current CSR1kv will be created. and put it in Neutron.05:24
yamahataIn fact CSR1kv routervm code is already there.05:25
s3wongyamahata: so the one item that everyone agrees on w.r.t. advanced service spinoff is that L3/routers is NOT service05:25
yamahataSo just cleanup/refactor it and move it common place05:25
*** scotm has joined #openstack-meeting05:25
s3wongNeutron will at least maintain the responsibility of L2/L3 plumbing05:25
yamahatas3wong: Does it mean l3 router will remain in Neutron?05:26
s3wongyamahata: current discussion seems to point that way05:26
*** ddieterly has joined #openstack-meeting05:26
dougwigi believe it will, along with dhcp services.05:26
yamahatas3wong: I see.05:26
s3wongL2/3 in Neutron, L4+ may (likely will) get the spinoff05:27
yamahataI see.05:27
*** manishg has quit IRC05:27
dougwigi would bet that a few l4 exceptions will be made for nova-network like things, like dhcp.05:28
*** comay has quit IRC05:28
yamahataOnce common library in Neutron is proved useuful, the code further can be moved from Neutron to Oslo.05:28
yamahata(Or its own rep.)05:28
s3wongyamahata: I think it is good to reach out to various advanced service folks and see if tacker can help --- given how frustrating service insertion has been, perhaps we can roll them into tacker as well05:29
s3wongs/them/that05:29
yamahatas3wong: That's very great.05:29
Hareesh+105:30
dougwigit's probably worth having lbaas and tacker meet next week; we might be a good first use case.  we have some members that don't want the risk of outside involvement getting in the way of delivery, but i think it's worth a conversation.05:30
yamahataI suppose those people would like to try just simple library which calls nova. then try to tacker or something.05:30
*** ddieterly has quit IRC05:31
s3wongyamahata: got to know the requirements though --- so far, insertion "into the router" is something that may require some additional Neutron APIs05:31
s3wongdougwig: +1 --- would like to see if there is common stuff we can do w.r.t. tacker now to aide Octavia delivery05:31
yamahata+1. good to know the requirement05:32
*** nelsnelson has quit IRC05:32
yamahataIs LBaaS BOF or something planned?05:32
yamahataor Octavia BoF05:32
*** topol has quit IRC05:33
dougwigBoF?05:33
*** mrmartin has quit IRC05:33
yamahataa sort of ad hoc meeting in addition to official design summit session.05:33
*** comay has joined #openstack-meeting05:34
dougwigwe've talked about it, but nothing firm yet.  there will be something.05:34
s3wongdougwig: we can find a cross-project session sometimes on Tuesday to have a cross-project session between Octavia and Tacker05:35
dougwigthat sounds good.05:35
dougwigif anyone wants to look, start here:  https://blueprints.launchpad.net/octavia05:36
yamahata#link  https://blueprints.launchpad.net/octavia05:36
dougwigthe nova driver and network driver interfaces are the "service vm" stuff, and "amphora" is our term for the vm image (roman "container").  don't get me started on how long that name took the group to agree on.05:36
*** ramishra has joined #openstack-meeting05:36
*** stevemar has quit IRC05:37
*** natarajk has left #openstack-meeting05:37
*** harlowja is now known as harlowja_away05:37
s3wongdougwigL let me see how we can sign up the cross-project sessions on Tues05:37
s3wongs/dougwigL/dougwig05:38
dougwigor even a pod meeting on friday could also work.05:38
*** SridharRamaswamy has joined #openstack-meeting05:38
s3wongsince it is Octavia and Tacker, we can involve the service folks from Neutron also --- because it can be classified as "cross-project" :-)05:38
dougwigthat might be easier to schedule.05:38
*** JRobinson__ has quit IRC05:38
*** lazy_prince is now known as killer_prince05:38
yamahataha ha05:38
s3wongdougwig: that is a good idea. since we would get some idea due to having been to the advanced service spinoff session05:39
*** Longgeek has joined #openstack-meeting05:39
*** SridharRamaswamy has quit IRC05:39
s3wongTBH, 40 minutes of adv. service spinoff discussion will likely lead to nowhere...05:39
dougwigyes, there is no way that is going to get resolved in 40 minutes.05:39
s3wongOh well...05:40
Hareesh:)05:40
s3wongdougwig: anyway, let's connect on when/where to meet in Paris for advanced service folks05:40
*** neeti has joined #openstack-meeting05:40
dougwig#action dougwig coordinate time for paris adv.services/tacker/lbaas meeting05:41
dougwig#action s3wong coordinate time for paris adv.services/tacker/lbaas meeting05:41
s3wongdougwig, yamahata: I will also try to work with SumitNaiksatam and SridarK to get them to join05:41
yamahatas3wong: sure. Firewall people.05:42
*** emagana has quit IRC05:42
s3wongdougwig, yamahata: let's hopefully get some concrete planning of work for Kilo (instead of stalling stuff for another cycle)05:42
yamahatas3wong: +1 definitively05:43
s3wongnow that all our projects are on stackforge, we should be able to iterate quicker05:43
yamahatathe discussion seems to conclude. any other topic? or can we close the meeting?05:45
s3wongyamahata: sounds good. See you next week!05:45
*** rakesh_hs has joined #openstack-meeting05:45
s3wongdougwig: see you next week in Paris also!05:46
*** bill_az_ has joined #openstack-meeting05:46
dougwiglooking forward to it!05:46
yamahatathank you. see you in Paris.05:46
yamahata#endmeeting05:46
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"05:46
openstackMeeting ended Tue Oct 28 05:46:42 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/servicevm_device_manager.2014-10-28-05.02.html05:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/servicevm_device_manager.2014-10-28-05.02.txt05:46
openstackLog:            http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/servicevm_device_manager.2014-10-28-05.02.log.html05:46
Hareeshsee you in paris05:46
*** bill_az has quit IRC05:47
*** bill_az_ is now known as bill_az05:48
*** chandankumar has joined #openstack-meeting05:48
*** bill_ibm has quit IRC05:48
*** topol_ has joined #openstack-meeting05:49
*** reed has quit IRC05:49
*** topol_ is now known as topol05:49
*** markwash__ has quit IRC05:50
*** enikanorov__ has joined #openstack-meeting05:50
*** sdake_ has quit IRC05:52
*** markwash__ has joined #openstack-meeting05:52
*** s3wong has quit IRC05:52
*** Hareesh has quit IRC05:53
*** ddieterly has joined #openstack-meeting05:56
*** lpeer_ has joined #openstack-meeting05:57
*** scotm has quit IRC06:00
*** markwash__ has quit IRC06:00
*** ddieterly has quit IRC06:01
*** yamamoto_ has quit IRC06:01
*** bill_az has quit IRC06:01
*** topol has quit IRC06:02
*** slong has quit IRC06:03
*** markwash__ has joined #openstack-meeting06:03
*** bmelande has joined #openstack-meeting06:04
*** alex_xu has quit IRC06:05
*** slong has joined #openstack-meeting06:05
*** yamahata has quit IRC06:06
*** adahms has quit IRC06:07
*** achanda has quit IRC06:08
*** afazekas_drunk is now known as afazekas06:08
*** enikanorov__ has quit IRC06:08
*** ajo has joined #openstack-meeting06:09
*** fnaval has quit IRC06:10
*** fnaval has joined #openstack-meeting06:11
*** fnaval has quit IRC06:15
*** ppai has quit IRC06:16
*** noelbk has quit IRC06:17
*** ildikov has joined #openstack-meeting06:18
*** alex_xu has joined #openstack-meeting06:19
*** david-lyle has quit IRC06:20
*** ivar-lazzaro has joined #openstack-meeting06:24
*** ppai has joined #openstack-meeting06:30
*** alex_xu has quit IRC06:32
*** ivar-lazzaro has quit IRC06:32
*** ivar-lazzaro has joined #openstack-meeting06:33
*** sdake_ has joined #openstack-meeting06:34
*** akamyshnikova_ has quit IRC06:34
*** markwash__ has quit IRC06:34
*** yamahata has joined #openstack-meeting06:34
*** ramishra has quit IRC06:34
*** MaxV has joined #openstack-meeting06:35
*** viveknarasimhan has joined #openstack-meeting06:37
*** viveknarasimhan has quit IRC06:39
*** ivar-lazzaro has quit IRC06:39
*** MaxV has quit IRC06:40
*** enikanorov__ has joined #openstack-meeting06:41
*** SridharG has joined #openstack-meeting06:42
*** sdake_ has quit IRC06:43
*** alex_xu has joined #openstack-meeting06:44
*** dims__ has joined #openstack-meeting06:44
*** ajo has quit IRC06:45
*** ajo has joined #openstack-meeting06:45
*** ppai has quit IRC06:45
*** rajeshr has joined #openstack-meeting06:46
*** sdake_ has joined #openstack-meeting06:46
*** killer_prince is now known as lazy_prince06:46
*** ajo_ has joined #openstack-meeting06:47
*** dims__ has quit IRC06:49
*** ajo has quit IRC06:50
*** david-lyle has joined #openstack-meeting06:50
*** doron_afk has joined #openstack-meeting06:53
*** david-lyle has quit IRC06:54
*** ddieterly has joined #openstack-meeting06:56
*** mrunge has joined #openstack-meeting06:56
*** markwash__ has joined #openstack-meeting06:57
*** k4n0 has joined #openstack-meeting06:57
*** ppai has joined #openstack-meeting06:58
*** rakhmerov_ is now known as rakhmerov06:58
*** ramishra has joined #openstack-meeting06:59
*** e0ne has joined #openstack-meeting07:01
*** ddieterly has quit IRC07:01
*** alex_xu has quit IRC07:02
*** SridharG1 has joined #openstack-meeting07:04
*** fifieldt has joined #openstack-meeting07:06
*** simon-AS5591 has joined #openstack-meeting07:07
*** simon-AS559 has quit IRC07:07
*** achanda has joined #openstack-meeting07:09
*** simon-AS559 has joined #openstack-meeting07:10
*** simon-AS5591 has quit IRC07:11
*** bmelande has quit IRC07:12
*** evgenyf has joined #openstack-meeting07:13
*** elo has quit IRC07:15
*** cody-somerville has quit IRC07:16
*** ramishra_ has joined #openstack-meeting07:16
*** cody-somerville has joined #openstack-meeting07:16
*** _nadya_ has joined #openstack-meeting07:16
*** achanda has quit IRC07:17
*** oomichi has quit IRC07:19
*** ramishra has quit IRC07:19
*** elo has joined #openstack-meeting07:20
*** david-lyle has joined #openstack-meeting07:21
*** samcdona has quit IRC07:23
*** ddieterly has joined #openstack-meeting07:24
*** david-lyle has quit IRC07:25
*** enikanorov__ has quit IRC07:27
*** rushiagr_away is now known as rushiagr07:27
*** e0ne has quit IRC07:29
*** ddieterly has quit IRC07:29
*** bagackiz has quit IRC07:29
*** simon-AS559 has quit IRC07:31
*** nellysmitt has joined #openstack-meeting07:33
*** leopoldj has joined #openstack-meeting07:36
*** e0ne has joined #openstack-meeting07:38
*** alex_xu has joined #openstack-meeting07:39
*** e0ne has quit IRC07:40
*** yamamoto_ has joined #openstack-meeting07:40
*** andreykurilin_ has joined #openstack-meeting07:41
*** sdake_ has quit IRC07:41
*** kobis has joined #openstack-meeting07:44
*** MaxV has joined #openstack-meeting07:47
*** markwash__ has quit IRC07:48
*** ngoswami has joined #openstack-meeting07:50
*** markwash__ has joined #openstack-meeting07:50
*** e0ne has joined #openstack-meeting07:50
*** e0ne has quit IRC07:52
*** pradipta_away is now known as pradipta07:54
*** _nadya_ has quit IRC07:55
*** vivek-ebay has joined #openstack-meeting07:56
*** yeungp has quit IRC07:57
*** mrmartin has joined #openstack-meeting07:58
*** scotm has joined #openstack-meeting08:01
*** vivek-ebay has quit IRC08:01
*** matrohon has joined #openstack-meeting08:01
*** jhenner has joined #openstack-meeting08:05
*** scotm has quit IRC08:06
*** markwash__ has quit IRC08:06
*** bagackiz has joined #openstack-meeting08:09
*** alex_xu has quit IRC08:14
*** jckasper_ has quit IRC08:17
*** jckasper has joined #openstack-meeting08:17
*** shohel02 has joined #openstack-meeting08:17
*** nellysmitt has quit IRC08:19
*** david-lyle has joined #openstack-meeting08:21
*** zz_ttrifonov is now known as ttrifonov08:22
*** haomai___ has quit IRC08:22
*** yamahata has quit IRC08:22
*** bagackiz has quit IRC08:23
*** shohel02 has quit IRC08:23
*** haomaiwang has joined #openstack-meeting08:23
*** nellysmitt has joined #openstack-meeting08:24
*** oanufriev has joined #openstack-meeting08:26
*** david-lyle has quit IRC08:26
*** slashme has quit IRC08:26
*** simon-AS5591 has joined #openstack-meeting08:33
*** dguitarbite has left #openstack-meeting08:34
*** phil__ has joined #openstack-meeting08:35
*** doude has joined #openstack-meeting08:36
*** bagackiz has joined #openstack-meeting08:38
*** rushiagr is now known as rushiagr_away08:40
*** jgallard has joined #openstack-meeting08:40
*** ajo_ has quit IRC08:42
*** ndipanov_gone is now known as ndipanov08:43
*** yamamoto_ has quit IRC08:51
*** imsurit has quit IRC08:51
*** Longgeek has quit IRC08:54
*** Longgeek has joined #openstack-meeting08:54
*** andreykurilin_ has quit IRC08:56
*** slashme has joined #openstack-meeting08:57
*** liusheng has quit IRC09:02
*** ygbo has joined #openstack-meeting09:03
*** JRobinson__ has joined #openstack-meeting09:03
*** stannie1 has joined #openstack-meeting09:07
*** zz_johnthetubagu is now known as johnthetubaguy09:08
*** jtomasek has joined #openstack-meeting09:09
*** achanda has joined #openstack-meeting09:15
*** safchain has joined #openstack-meeting09:15
*** derekh has joined #openstack-meeting09:16
*** achanda has quit IRC09:19
*** pradipta is now known as pradipta_away09:20
*** xuhanp has quit IRC09:20
*** wuhg has joined #openstack-meeting09:20
*** zhhuabj has quit IRC09:21
*** david-lyle has joined #openstack-meeting09:22
*** JRobinson__ has quit IRC09:23
*** eglynn-officeafk is now known as eglynn-office09:24
*** david-lyle has quit IRC09:26
*** ZiGMaX has joined #openstack-meeting09:30
*** shohel02 has joined #openstack-meeting09:34
*** zhhuabj has joined #openstack-meeting09:34
*** pnavarro has joined #openstack-meeting09:35
*** pelix has joined #openstack-meeting09:36
*** scheuran has joined #openstack-meeting09:36
*** andreaf has joined #openstack-meeting09:36
*** pnavarro has quit IRC09:38
*** shohel02 has quit IRC09:38
*** pnavarro has joined #openstack-meeting09:38
*** andreaf_ has joined #openstack-meeting09:39
*** zns has quit IRC09:43
*** niclem_ has quit IRC09:44
*** matiu has quit IRC09:45
*** ramishra has joined #openstack-meeting09:50
*** ajo_ has joined #openstack-meeting09:50
*** ramishra_ has quit IRC09:50
*** simon-AS5591 has quit IRC09:51
*** Longgeek has quit IRC09:51
*** slashme has quit IRC09:54
*** fayablazer has joined #openstack-meeting09:54
*** zhhuabj has quit IRC09:59
*** yeungp has joined #openstack-meeting10:00
*** scotm has joined #openstack-meeting10:01
*** epico has quit IRC10:04
*** ozamiatin has joined #openstack-meeting10:04
*** paragan has quit IRC10:04
*** Longgeek has joined #openstack-meeting10:04
*** _nadya_ has joined #openstack-meeting10:06
*** sankarshan is now known as sankarshan_away10:07
*** scotm has quit IRC10:07
*** _nadya_ has quit IRC10:08
*** IanGovett has joined #openstack-meeting10:14
*** b3nt_pin is now known as beagles10:14
*** zhhuabj has joined #openstack-meeting10:16
*** slashme has joined #openstack-meeting10:18
*** simon-AS5591 has joined #openstack-meeting10:18
*** dims__ has joined #openstack-meeting10:19
*** adahms has joined #openstack-meeting10:19
*** nellysmitt has quit IRC10:20
*** daneyon_ has joined #openstack-meeting10:21
*** epico has joined #openstack-meeting10:23
*** david-lyle has joined #openstack-meeting10:23
*** dims__ has quit IRC10:23
*** aepifanov has quit IRC10:23
*** david-lyle has quit IRC10:28
*** obondarev has quit IRC10:31
*** obondarev has joined #openstack-meeting10:31
*** e0ne has joined #openstack-meeting10:34
*** markmcclain has joined #openstack-meeting10:36
*** slashme has quit IRC10:37
*** sankarshan_away has quit IRC10:39
*** haomaiwang has quit IRC10:39
*** _nadya_ has joined #openstack-meeting10:41
*** dims__ has joined #openstack-meeting10:43
*** AzherKhan has quit IRC10:51
*** ppai has quit IRC10:52
*** markmcclain has quit IRC10:53
*** markmcclain has joined #openstack-meeting10:53
*** epico has quit IRC10:54
*** simon-AS5591 has quit IRC10:55
*** andreaf has quit IRC10:55
*** andreaf_ is now known as andreaf10:55
*** beagles is now known as beagles_biab10:57
*** baoli has joined #openstack-meeting11:00
*** haomaiwa_ has joined #openstack-meeting11:01
*** nellysmitt has joined #openstack-meeting11:01
*** BharatK has joined #openstack-meeting11:03
*** ppai has joined #openstack-meeting11:04
*** baoli has quit IRC11:04
*** baoli has joined #openstack-meeting11:05
*** weshay has joined #openstack-meeting11:07
*** markwash__ has joined #openstack-meeting11:07
*** haomaiwa_ has quit IRC11:09
*** IanGovett has quit IRC11:09
*** markwash__ has quit IRC11:12
*** shohel02 has joined #openstack-meeting11:15
*** shohel02 has quit IRC11:16
*** IanGovett has joined #openstack-meeting11:23
*** david-lyle has joined #openstack-meeting11:24
*** shohel02 has joined #openstack-meeting11:24
*** nellysmitt has quit IRC11:25
*** shohel02 has quit IRC11:25
*** yeungp has quit IRC11:27
*** paragan has joined #openstack-meeting11:27
*** paragan has quit IRC11:27
*** paragan has joined #openstack-meeting11:27
*** david-lyle has quit IRC11:28
*** aepifanov has joined #openstack-meeting11:32
*** js1123_ has joined #openstack-meeting11:33
*** aysyd has joined #openstack-meeting11:34
*** _nadya_ has quit IRC11:35
*** Poornima has quit IRC11:38
*** marrusl has quit IRC11:39
*** marrusl has joined #openstack-meeting11:41
*** pnavarro has quit IRC11:46
*** yamahata has joined #openstack-meeting11:47
*** nellysmitt has joined #openstack-meeting11:48
*** yamamoto has joined #openstack-meeting11:50
*** pelix has quit IRC11:50
*** pelix has joined #openstack-meeting11:52
*** vkmc has joined #openstack-meeting11:52
*** vkmc has quit IRC11:52
*** vkmc has joined #openstack-meeting11:52
*** pelix has quit IRC11:53
*** yamamoto has quit IRC11:54
*** wwallnrr__ has joined #openstack-meeting11:55
*** shohel02 has joined #openstack-meeting11:55
*** cdub has quit IRC11:58
*** igordcard has joined #openstack-meeting11:58
*** samuelms has joined #openstack-meeting11:59
*** sgordon_ has joined #openstack-meeting11:59
*** shohel02 has quit IRC12:00
*** markmcclain has quit IRC12:00
*** weshay has quit IRC12:03
*** stannie1 has quit IRC12:03
*** dkranz has joined #openstack-meeting12:03
*** beagles_biab is now known as beagles12:06
*** rajeshr has quit IRC12:06
*** pnavarro has joined #openstack-meeting12:07
*** dims__ has quit IRC12:07
*** dims__ has joined #openstack-meeting12:07
*** mwagner_lap has quit IRC12:10
*** bradjones has quit IRC12:12
*** bradjones has joined #openstack-meeting12:13
*** jckasper has quit IRC12:13
*** yamahata has quit IRC12:15
*** dneary has joined #openstack-meeting12:15
*** weshay has joined #openstack-meeting12:16
*** BharatK has quit IRC12:16
*** ppai has quit IRC12:23
*** david-lyle has joined #openstack-meeting12:24
*** pnavarro has quit IRC12:26
*** slashme has joined #openstack-meeting12:27
*** igordcard has quit IRC12:27
*** jecarey has joined #openstack-meeting12:27
*** slashme has quit IRC12:28
*** slahsme has joined #openstack-meeting12:29
*** david-lyle has quit IRC12:29
*** dprince has joined #openstack-meeting12:35
*** miqui has joined #openstack-meeting12:36
*** phil_h has quit IRC12:39
*** freemanbrandon has joined #openstack-meeting12:40
*** jehb has joined #openstack-meeting12:40
*** weshay has quit IRC12:43
*** alexpilotti has joined #openstack-meeting12:45
*** noslzzp has joined #openstack-meeting12:45
*** alexpilotti has quit IRC12:45
*** alexpilotti has joined #openstack-meeting12:46
*** neeti has quit IRC12:46
*** k4n0 has quit IRC12:46
*** jecarey has quit IRC12:48
*** jecarey has joined #openstack-meeting12:48
*** jckasper has joined #openstack-meeting12:49
*** _nadya_ has joined #openstack-meeting12:49
*** moha_hunt has joined #openstack-meeting12:50
*** vhoward has left #openstack-meeting12:52
*** mwagner_lap has joined #openstack-meeting12:52
*** simon-AS559 has joined #openstack-meeting12:55
*** ramishra has quit IRC12:56
*** rakesh_hs has quit IRC12:58
*** ZiGMaX has quit IRC12:59
*** yassine has joined #openstack-meeting13:00
*** obondarev has quit IRC13:01
*** obondarev has joined #openstack-meeting13:02
*** weshay has joined #openstack-meeting13:03
*** sankarshan has joined #openstack-meeting13:04
*** aysyd has quit IRC13:05
*** haomaiwang has joined #openstack-meeting13:05
*** bknudson has quit IRC13:05
*** derekh has quit IRC13:06
*** igordcard has joined #openstack-meeting13:07
*** alex_xu has joined #openstack-meeting13:07
*** rook has joined #openstack-meeting13:09
*** rook has left #openstack-meeting13:09
*** julim has joined #openstack-meeting13:10
*** markmcclain has joined #openstack-meeting13:11
*** markmcclain1 has joined #openstack-meeting13:12
*** rushiagr_away is now known as rushiagr13:12
*** markmcclain1 has quit IRC13:12
*** nati_ueno has joined #openstack-meeting13:13
*** markmcclain has quit IRC13:16
*** fnaval has joined #openstack-meeting13:17
*** achanda has joined #openstack-meeting13:18
*** aysyd has joined #openstack-meeting13:21
*** munish has joined #openstack-meeting13:21
*** ramishra has joined #openstack-meeting13:21
*** achanda has quit IRC13:23
*** nellysmitt has quit IRC13:24
*** nati_uen_ has joined #openstack-meeting13:25
*** bknudson has joined #openstack-meeting13:25
*** david-lyle has joined #openstack-meeting13:25
*** paragan has quit IRC13:25
*** jecarey has quit IRC13:26
*** fnaval has quit IRC13:27
*** nati_ueno has quit IRC13:28
*** david-lyle has quit IRC13:29
*** paragan has joined #openstack-meeting13:30
*** thedodd has joined #openstack-meeting13:32
*** munish has quit IRC13:32
*** zns has joined #openstack-meeting13:33
*** sarob has joined #openstack-meeting13:34
*** changbl has quit IRC13:35
*** marun_ has joined #openstack-meeting13:36
*** timrc-afk is now known as timrc13:39
*** aysyd has quit IRC13:40
*** aepifanov has quit IRC13:40
*** marun_ has quit IRC13:41
*** marun has joined #openstack-meeting13:41
*** bill_az has joined #openstack-meeting13:43
*** zehicle has quit IRC13:44
*** marun has quit IRC13:46
*** ramishra has quit IRC13:47
*** zns has quit IRC13:47
*** topol has joined #openstack-meeting13:48
*** freemanbrandon has quit IRC13:48
*** armax has joined #openstack-meeting13:49
*** marun has joined #openstack-meeting13:49
*** doron_afk is now known as doron13:49
*** balajiiyer has joined #openstack-meeting13:50
*** ramishra has joined #openstack-meeting13:51
*** pelix has joined #openstack-meeting13:51
*** gholler has joined #openstack-meeting13:51
*** pradipta_away is now known as pradipta13:52
*** aysyd has joined #openstack-meeting13:52
*** zns has joined #openstack-meeting13:52
*** freemanbrandon has joined #openstack-meeting13:52
*** adahms has quit IRC13:52
*** zns has quit IRC13:53
*** markwash__ has joined #openstack-meeting13:53
*** |pep| has joined #openstack-meeting13:53
*** FJB has joined #openstack-meeting13:55
*** doron is now known as doron_afk13:56
*** vijendar has joined #openstack-meeting13:57
*** markwash__ has quit IRC13:57
*** thangp has joined #openstack-meeting13:58
*** zns has joined #openstack-meeting14:00
*** tbarron has joined #openstack-meeting14:01
*** eharney has joined #openstack-meeting14:02
*** jckasper has quit IRC14:02
*** rbak has joined #openstack-meeting14:02
*** dims__ has quit IRC14:04
*** haomaiwang has quit IRC14:04
*** haomaiwang has joined #openstack-meeting14:04
*** cdub has joined #openstack-meeting14:05
*** nosnos has quit IRC14:06
*** nosnos has joined #openstack-meeting14:07
*** vhoward has joined #openstack-meeting14:07
*** chandankumar has quit IRC14:07
*** aepifanov has joined #openstack-meeting14:08
*** shohel02 has joined #openstack-meeting14:09
*** nelsnelson has joined #openstack-meeting14:09
*** nelsnelson has quit IRC14:09
*** nelsnelson has joined #openstack-meeting14:10
*** lpeer_ has quit IRC14:11
*** nosnos has quit IRC14:11
*** ddieterly has joined #openstack-meeting14:11
*** jecarey has joined #openstack-meeting14:12
*** pradipta is now known as pradipta_away14:12
*** scotm has joined #openstack-meeting14:14
*** ddieterly has quit IRC14:14
*** jckasper has joined #openstack-meeting14:15
*** ddieterly has joined #openstack-meeting14:15
*** DuncanT- has joined #openstack-meeting14:15
*** markwash__ has joined #openstack-meeting14:20
*** cdub has quit IRC14:20
*** kebray has joined #openstack-meeting14:21
*** ZiGMaX has joined #openstack-meeting14:22
*** otherwiseguy has joined #openstack-meeting14:23
*** spzala has joined #openstack-meeting14:24
*** markwash__ has quit IRC14:24
*** FJB has quit IRC14:24
*** miqui has quit IRC14:25
*** sarob has quit IRC14:25
*** sarob has joined #openstack-meeting14:25
*** david-lyle has joined #openstack-meeting14:26
*** radez_g0n3 is now known as radez14:29
*** sarob has quit IRC14:29
*** david-lyle has quit IRC14:31
*** jckasper has quit IRC14:33
*** thedodd has quit IRC14:33
*** yaguang has joined #openstack-meeting14:34
*** nati_uen_ has quit IRC14:35
*** zns has quit IRC14:36
*** lazy_prince is now known as killer_prince14:36
*** miqui has joined #openstack-meeting14:37
*** jckasper has joined #openstack-meeting14:40
*** PaulMurray has joined #openstack-meeting14:40
*** alex_xu has quit IRC14:41
*** ayoung has joined #openstack-meeting14:42
*** yamahata has joined #openstack-meeting14:42
*** chandankumar has joined #openstack-meeting14:43
*** zns has joined #openstack-meeting14:43
*** dpaterson has joined #openstack-meeting14:45
*** ayoung has quit IRC14:46
*** ptoohill_ has quit IRC14:48
*** garyh has joined #openstack-meeting14:48
*** achanda has joined #openstack-meeting14:48
*** mattgriffin has joined #openstack-meeting14:50
*** imsurit has joined #openstack-meeting14:50
*** markmcclain has joined #openstack-meeting14:50
*** balajiiyer has left #openstack-meeting14:55
*** neelashah has joined #openstack-meeting14:57
*** zz_jgrimm is now known as jgrimm14:58
*** mjturek has joined #openstack-meeting14:59
*** dane_leblanc has joined #openstack-meeting15:00
*** fnaval has joined #openstack-meeting15:00
*** ayoung has joined #openstack-meeting15:00
*** haomaiw__ has joined #openstack-meeting15:02
*** niclem has joined #openstack-meeting15:03
*** carl_baldwin has joined #openstack-meeting15:04
*** david-lyle has joined #openstack-meeting15:05
*** Mandell has quit IRC15:05
edleafeSO I'm guessing that there's no Gantt meeting today?15:05
jaypipesedleafe: oops, sorry...15:05
jaypipes#startmeeting gantt15:05
openstackMeeting started Tue Oct 28 15:05:46 2014 UTC and is due to finish in 60 minutes.  The chair is jaypipes. Information about MeetBot at http://wiki.debian.org/MeetBot.15:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:05
*** openstack changes topic to " (Meeting topic: gantt)"15:05
openstackThe meeting name has been set to 'gantt'15:05
jaypipesedleafe, PaulMurray, anybody else here for the scheduler meeting?15:06
jgallardhi!15:06
jaypipesjgallard: hi! :)15:06
*** haomaiwang has quit IRC15:06
edleafejgallard: o/15:06
jaypipes#topic review of scheduler blueprints15:06
*** openstack changes topic to "review of scheduler blueprints (Meeting topic: gantt)"15:06
jaypipesso, one minute...15:08
jaypipes#link https://review.openstack.org/#/c/127609/15:08
jaypipes#link https://review.openstack.org/#/c/127610/15:09
jaypipes#link https://review.openstack.org/#/c/127612/15:09
*** achanda has quit IRC15:09
*** elo has quit IRC15:09
*** SumitNaiksatam has quit IRC15:09
jaypipesThe above three need to have a second patch pushed that addresses some minor spec layout comments from johnthetubaguy15:09
jaypipesI will try to get to that today or tomorrow... been busy working on conference slide/session material :(15:10
jaypipesthere are also blueprints that edleafe is involved in:15:10
jaypipesedleafe: mind linking your detach compute node frmo service BP?15:11
edleafejaypipes: Busy? You??15:11
jaypipeshttps://review.openstack.org/#/c/126895/15:11
jaypipes#link https://review.openstack.org/#/c/126895/ <-- detach service from compute node15:11
*** beagles is now known as beagles_brb15:11
jaypipesand finally, there is the isolate scheduler DB blueprint: https://review.openstack.org/#/c/89893/15:11
jaypipes#link https://review.openstack.org/#/c/89893/15:11
jaypipeswhich really should be split up into aggregates and instance group handling blueprints.15:12
*** nellysmitt has joined #openstack-meeting15:12
jaypipesI've asked Sylvain to split that up, but I might just do that for him since he's on holiday and we're short on time.15:12
edleafejaypipes: I can probably work on that15:13
edleafes/probably//15:13
jaypipesI know that n0ano doesn't have confidence that we can get an etherpad together with a good amount of discussion topics *before* the summit, but I'd really like do that.15:13
jaypipesedleafe: split up the isolate db bp you mean?15:13
edleafejaypipes: yes15:13
*** freemanbrandon has quit IRC15:14
jaypipesedleafe: that would be awesome if you could do that. ++15:14
edleafetake a little off your plate15:14
jaypipesedleafe: really appreciate it.15:14
*** eglynn-office has quit IRC15:14
jaypipesedleafe: I'm finishing up some slides for one of my talks this morning, and then I'll send an email out to the group cc'ing the ML with a link to the etherpad to start our discussion topics on.15:14
edleafe#action edleafe to handle BP split in https://review.openstack.org/#/c/89893/15:15
jaypipesedleafe: other than that, I don't have much news other than to say I have been able to refactor a whole bunch of unit tests in the scheduler and RT in the last week or so, which should *hopefully* help with the blueprints involved in splitting out the scheduler.15:15
jaypipesthx edleafe15:15
jaypipes#topic open discussion15:16
*** openstack changes topic to "open discussion (Meeting topic: gantt)"15:16
jaypipesanybody have anything to add?15:16
jaypipes#action jaypipes to send an update to ML including link to etherpad for summit discussion points.15:16
*** nati_ueno has joined #openstack-meeting15:17
*** sdake_ has joined #openstack-meeting15:17
*** Riddhi has joined #openstack-meeting15:17
edleafe<crickets>15:19
jaypipesheh15:19
*** |pep| has quit IRC15:19
jaypipesOK, ending meeting. thx edleafe :)15:19
jaypipes#endmeeting15:19
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:19
openstackMeeting ended Tue Oct 28 15:19:49 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:19
openstackMinutes:        http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-10-28-15.05.html15:19
*** nati_ueno has quit IRC15:19
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-10-28-15.05.txt15:19
openstackLog:            http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-10-28-15.05.log.html15:19
*** sdake_ has quit IRC15:20
*** SridharRamaswamy has joined #openstack-meeting15:20
*** ptoohill_ has joined #openstack-meeting15:21
*** sdake_ has joined #openstack-meeting15:21
*** moha_hunt has quit IRC15:23
*** jorge_munoz has joined #openstack-meeting15:25
*** jckasper has quit IRC15:29
*** zns has quit IRC15:31
*** SridharG1 has left #openstack-meeting15:33
*** jckasper has joined #openstack-meeting15:34
*** rmoe has quit IRC15:34
*** SridharG has quit IRC15:34
*** bill_az has quit IRC15:36
*** zns has joined #openstack-meeting15:37
*** cjellick has joined #openstack-meeting15:38
*** cjellick has quit IRC15:39
*** noelbk has joined #openstack-meeting15:40
*** tsekiyama has joined #openstack-meeting15:41
*** SridharRamaswamy has quit IRC15:42
*** aepifanov has quit IRC15:42
*** cjellick has joined #openstack-meeting15:43
*** SumitNaiksatam has joined #openstack-meeting15:44
*** lpeer_ has joined #openstack-meeting15:47
*** andreaf has quit IRC15:48
*** bitblt has joined #openstack-meeting15:49
*** padkrish has joined #openstack-meeting15:49
*** PaulMurray has left #openstack-meeting15:51
*** Tross has joined #openstack-meeting15:53
*** drankis has joined #openstack-meeting15:54
*** otherwiseguy has quit IRC15:54
*** terryw has joined #openstack-meeting15:54
*** hemna has joined #openstack-meeting15:54
*** rmoe has joined #openstack-meeting15:55
*** slahsme has quit IRC15:56
*** beagles_brb is now known as beagles15:57
*** zns has quit IRC15:58
*** daneyon_ has quit IRC15:59
*** schwicht has quit IRC15:59
*** miqui has quit IRC15:59
*** miqui_ has joined #openstack-meeting15:59
*** daneyon has joined #openstack-meeting16:00
*** ramishra has quit IRC16:00
*** fesp has joined #openstack-meeting16:01
*** ramishra has joined #openstack-meeting16:01
*** virmitio has joined #openstack-meeting16:02
*** fesp is now known as flaper8716:02
*** flaper87 has joined #openstack-meeting16:03
*** ivar-lazzaro has joined #openstack-meeting16:03
*** ivar-laz_ has joined #openstack-meeting16:04
*** gyee has joined #openstack-meeting16:04
*** amotoki has joined #openstack-meeting16:05
*** jmontemayor has joined #openstack-meeting16:05
*** marcoemorais has joined #openstack-meeting16:08
*** ivar-lazzaro has quit IRC16:08
*** jgriffit1 has joined #openstack-meeting16:09
*** jgriffit1 is now known as jdg16:09
*** jgriffith has quit IRC16:10
*** jdg is now known as jgriffith16:10
*** VijayTripathi has joined #openstack-meeting16:10
*** jgriffith is now known as Guest5826716:10
*** carl_baldwin has quit IRC16:11
VijayTripathiHello everyone16:11
*** Guest58267 is now known as jdg16:14
*** emagana has joined #openstack-meeting16:15
*** niclem has quit IRC16:15
*** ajo_ has quit IRC16:17
*** samcdona has joined #openstack-meeting16:17
*** samcdona has quit IRC16:20
*** killer_prince has quit IRC16:21
*** stevemar has joined #openstack-meeting16:21
*** zns has joined #openstack-meeting16:22
*** ildikov has quit IRC16:22
*** ivar-lazzaro has joined #openstack-meeting16:22
*** killer_prince has joined #openstack-meeting16:22
*** killer_prince is now known as lazy_prince16:22
*** freemanbrandon has joined #openstack-meeting16:24
*** ivar-laz_ has quit IRC16:25
*** miqui_ has quit IRC16:26
*** zns has quit IRC16:26
*** reed has joined #openstack-meeting16:27
*** freemanbrandon has quit IRC16:28
*** gduan has quit IRC16:29
*** pberis has quit IRC16:29
*** garyduan has joined #openstack-meeting16:30
*** ramishra has quit IRC16:31
*** manishg has joined #openstack-meeting16:32
*** manishg has left #openstack-meeting16:32
*** marcoemorais has quit IRC16:32
*** marcoemorais has joined #openstack-meeting16:32
*** yamahata has quit IRC16:32
*** dims__ has joined #openstack-meeting16:33
*** thedodd has joined #openstack-meeting16:33
*** jaypipes is now known as jaypipes-afk16:33
*** padkrish has quit IRC16:34
*** padkrish has joined #openstack-meeting16:35
*** dsetia has joined #openstack-meeting16:35
*** pballand has joined #openstack-meeting16:35
*** ttrifonov is now known as zz_ttrifonov16:36
*** mtanino has joined #openstack-meeting16:36
*** bill_az has joined #openstack-meeting16:37
*** ivar-lazzaro has quit IRC16:37
*** zns has joined #openstack-meeting16:38
*** vivek-ebay has joined #openstack-meeting16:38
*** ivar-lazzaro has joined #openstack-meeting16:38
*** scheuran has quit IRC16:39
*** marcoemorais has quit IRC16:41
*** amaretskiy has joined #openstack-meeting16:42
*** pballand has quit IRC16:44
*** scotm has quit IRC16:44
*** vivek-ebay has quit IRC16:44
*** leeantho has joined #openstack-meeting16:45
*** vivek-ebay has joined #openstack-meeting16:45
*** markmcclain has quit IRC16:45
*** harlowja_away is now known as harlowja16:46
*** evgenyf has quit IRC16:47
*** vivek-ebay has quit IRC16:47
*** Longgeek has quit IRC16:47
*** intr1nsic has quit IRC16:48
*** vivek-ebay has joined #openstack-meeting16:48
*** intr1nsic has joined #openstack-meeting16:48
*** intr1nsic has quit IRC16:50
*** tnurlygayanov has joined #openstack-meeting16:51
*** s3wong has joined #openstack-meeting16:51
*** juzuluag has joined #openstack-meeting16:51
*** oanufriev has quit IRC16:53
*** yassine has quit IRC16:53
*** ngoswami has quit IRC16:53
*** jgriffit1 has joined #openstack-meeting16:54
*** Mandell has joined #openstack-meeting16:54
*** VijayTripathi has quit IRC16:54
*** msdubov has joined #openstack-meeting16:54
*** olkonami has joined #openstack-meeting16:55
*** jgriffit1 is now known as jgriffith16:55
*** jgriffith is now known as Guest1501816:56
*** sarob has joined #openstack-meeting16:56
*** intr1nsic has joined #openstack-meeting16:56
*** jgriffith has joined #openstack-meeting16:57
*** oanufriev has joined #openstack-meeting16:57
*** pballand has joined #openstack-meeting16:57
*** fayablazer has quit IRC17:00
*** marcoemorais has joined #openstack-meeting17:01
*** ivar-laz_ has joined #openstack-meeting17:01
*** marcoemorais has quit IRC17:01
*** doron_afk has quit IRC17:01
*** marcoemorais has joined #openstack-meeting17:01
*** Rajini_Ram has quit IRC17:02
*** zns has quit IRC17:02
*** freemanbrandon has joined #openstack-meeting17:02
*** Rajini_Ram has joined #openstack-meeting17:02
*** ildikov has joined #openstack-meeting17:02
*** mattgriffin has quit IRC17:02
boris-42#stratmeeting Rally17:03
boris-42msdubov olkonami amaretskiy ping17:03
amaretskiyboris-42 hi17:04
msdubovboris-42, hi!17:04
*** ivar-lazzaro has quit IRC17:04
*** marcoemorais has quit IRC17:05
olkonamihi!17:05
*** marcoemorais has joined #openstack-meeting17:05
tnurlygayanovhi!17:06
boris-42#startmeeting Rally17:07
openstackMeeting started Tue Oct 28 17:07:02 2014 UTC and is due to finish in 60 minutes.  The chair is boris-42. Information about MeetBot at http://wiki.debian.org/MeetBot.17:07
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:07
*** openstack changes topic to " (Meeting topic: Rally)"17:07
openstackThe meeting name has been set to 'rally'17:07
*** zns has joined #openstack-meeting17:07
*** marcoemorais has quit IRC17:07
boris-42#topic discuss DOCstring of benchmark scenarios + possible ways to auto generate doc samples17:07
*** openstack changes topic to "discuss DOCstring of benchmark scenarios + possible ways to auto generate doc samples (Meeting topic: Rally)"17:07
*** rook has joined #openstack-meeting17:07
boris-42amaretskiy as you were interested in this17:07
*** marcoemorais has joined #openstack-meeting17:07
rookin17:07
boris-42rook hi there17:07
rookhey17:07
*** marcoemorais has quit IRC17:07
boris-42amaretskiy so what was your idea?17:08
amaretskiymy idea is save samples in class properties or in method properties, not in docstrings17:08
*** marcoemorais has joined #openstack-meeting17:08
*** marcoemorais has quit IRC17:08
*** ignacio-scopett1 has joined #openstack-meeting17:08
amaretskiyadvantages:17:08
amaretskiy* no need to parse17:08
amaretskiy  * easy to check17:08
amaretskiy  * ready for using as templates17:08
*** ignacio-scopetta has quit IRC17:08
*** marcoemorais has joined #openstack-meeting17:09
boris-42msdubov ^17:09
*** phil__ has quit IRC17:09
*** carl_baldwin has joined #openstack-meeting17:10
msdubovamaretskiy, I definitely need some clarifications on this17:10
msdubovamaretskiy, How would you store it - as a whole string or split?17:10
msdubovamaretskiy, It would be great if you'd write up a small sample class17:10
msdubovamaretskiy, To illustrate your idea17:10
tnurlygayanovamaretskiy why we need this? you suggest to save 'help' messages and 'examples' in properties/methods instead of doc strings?17:10
msdubovamaretskiy, As of now, it's not obvious for me why this is going to be easier to parse17:10
tnurlygayanovdoc string it is the property too.17:10
msdubovtnurlygayanov, +117:11
amaretskiyfor example:17:11
amaretskiyclass Foo(...):17:11
amaretskiy     """ ... """17:11
amaretskiy    SAMPLE = """{ JSON }"""17:11
amaretskiyno need to parse17:12
amaretskiyeasy to check/validate/etc...17:12
msdubovamaretskiy, Okay so we leave docstrings as is and just add these SAMPLE attributes?17:12
*** scotm has joined #openstack-meeting17:12
msdubovamaretskiy, Okay, but SAMPLE is unique for the whole class17:12
amaretskiyyes17:12
msdubovamaretskiy, How would you store samples for each scenario?17:13
*** simon-AS559 has quit IRC17:13
amaretskiyif we need to add a sample for method, we can use 2 ways:17:13
boris-42amaretskiy NO I dislike SAMPLE17:13
*** wuhg has quit IRC17:13
boris-42amaretskiy we were talking about decorator17:13
*** kobis has quit IRC17:13
boris-42amaretskiy or adding to function field directly17:14
boris-42amaretskiy as far as I remember17:14
*** paragan has quit IRC17:14
*** changbl has joined #openstack-meeting17:14
amaretskiyclass FooScenario(...):17:14
amaretskiy   def barScenario(...): ...17:14
amaretskiy   barScenario_sample = """{JSON}"""  # 1st way17:14
amaretskiy  barScenario.SAMPLE = """{JSON}""" # 2nd way17:14
*** marcoemorais has quit IRC17:15
amaretskiyyes, decorator is ok, but it seems to have extraordinary size17:15
amaretskiyso. 3rd way - decorator17:16
amaretskiynot docstring17:16
*** ygbo has quit IRC17:16
*** mattgriffin has joined #openstack-meeting17:16
amaretskiyas for me I would prefer 2nd way17:16
*** SridharRamaswamy has joined #openstack-meeting17:16
amaretskiysame property name17:16
amaretskiyfor all required objects17:16
*** yaguang has quit IRC17:17
msdubovamaretskiy, I'm a bit worried about the code getting very huge... (SLOC) Although it will be of course easier for anyone to quickly understand how a particular scenario should be configured17:17
msdubovamaretskiy, boris-42 Maybe we could store only sample arguments, without the "runner"/"context" section?17:17
msdubovamaretskiy, To make it a bit shorter17:18
msdubovand then quickly compose a valid JSON sample out of that17:18
boris-42msdubov but what about cases when it makes sense?17:18
amaretskiynot sure, everything should be explicit17:18
msdubovboris-42, You're right17:18
msdubovboris-42, amaretskiy I had an idea of storing the JSON samples in doc/sample/tasks, but adding a link to those files in the docstrings17:19
amaretskiynot sure - means - include complete data17:19
boris-42msdubov wtf17:19
msdubovsomething like :sample: doc/sample/tasks17:19
boris-42msdubov no idea was to generate task samples17:19
msdubovboris-42, Well we still can generate them117:19
msdubov!17:19
msdubovin files17:19
boris-42msdubov hm17:19
msdubovboris-42, I believe that JSON samples in files are easier to navigate17:20
msdubovthan those in code17:20
*** zns has quit IRC17:20
*** marcoemorais has joined #openstack-meeting17:20
msdubovbecause they are stored in a neat compact way17:20
boris-42msdubov there will be in files...17:20
boris-42msdubov I am talking about removing them from files17:20
msdubovboris-42, ok17:20
boris-42msdubov i am talking about generating them from code17:20
amaretskiyso, if we want to generate JSON, then: 1) parsing source is bad 2) templating is good - so docstrings are not good for that17:20
*** zns has joined #openstack-meeting17:20
boris-42amaretskiy so basically having one @base.sampe() is good choose17:21
boris-42choice*17:21
boris-42for "rally info" and generation of doc/samples/tasks/17:21
amaretskiyyes, decorator is good :)17:21
msdubovamaretskiy, boris-42 agree17:22
*** VijayTripathi has joined #openstack-meeting17:23
boris-42Okay so then I think17:23
boris-42we will add @sample()17:23
*** ZiGMaX has quit IRC17:23
*** virmitio has left #openstack-meeting17:23
boris-42btw it can be reused for Context/Runner/Scenarios17:23
boris-42and SLA stuff17:24
tnurlygayanovwe want to generate samples based on parameters of functions/methods?17:24
boris-42so I think it should be in common place17:24
*** pberis has joined #openstack-meeting17:24
boris-42tnurlygayanov nope we don't want17:24
boris-42tnurlygayanov it's impossible17:24
*** MaxV has quit IRC17:25
tnurlygayanovok, how we will generate samples? we need to stroe some information about each benchmark/scenario and generate samples based on this info17:25
*** MaxV has joined #openstack-meeting17:25
boris-42tnurlygayanov ...17:26
amaretskiyproperty17:26
*** kebray has quit IRC17:26
boris-42tnurlygayanov whole discussion above was about that17:26
tnurlygayanovok17:26
boris-42tnurlygayanov we will have @sample17:26
*** padkrish has quit IRC17:26
boris-42tnurlygayanov that adds property to class/method in different cases17:26
boris-42tnurlygayanov and that can be reused by SLA/Context/Runners/Scenarios17:26
*** kebray has joined #openstack-meeting17:26
*** dprince has quit IRC17:27
tnurlygayanovboris-42  ok, now it is clear :) thank you.17:27
*** stevemar is now known as notstevemar17:29
*** MaxV has quit IRC17:30
boris-42Okay let's move17:31
boris-42#topic Rally info updates and future steps17:31
*** openstack changes topic to "Rally info updates and future steps (Meeting topic: Rally)"17:31
boris-42msdubov go on17:31
rookFuture : way to disable cleanup  =)17:32
*** achanda has joined #openstack-meeting17:32
rookkambiz is not here to talk more to that :D17:32
msdubovSo there are two major updates on this, both in one patch: https://review.openstack.org/#/c/126421/17:32
rookhowever, i agree boris-42 it is a "nice to have"17:32
boris-42rook I mean it will be17:32
boris-42rook it's already in our road map17:32
boris-42rook https://github.com/stackforge/rally/blob/master/doc/feature_request/persistence_benchmark_env.rst17:33
msdubov1. Typing just "rally info" or "rally info list" results in printing out a list of scenarios/engines/... that can be queried by rally info17:33
boris-42rook this is our roadmap17:33
msdubov2. "rally info find <...>" now has more info about scenario groups17:33
boris-42rook but it will take some amount of time to implement it17:33
*** tzabal has joined #openstack-meeting17:33
*** amotoki has quit IRC17:33
*** balajiiyer has joined #openstack-meeting17:33
msdubove.g. "rally info find NovaServers" -> you have info about what benchmark scenarios are there17:33
msdubovin a neat table-like output17:33
msdubovAlso there is a test that checks that Rally is covered with docstrings: https://review.openstack.org/12719217:34
msdubovAs soon as we make it pass, we can be sure that "rally info" works well too :)17:34
boris-42msdubov so17:35
boris-42msdubov what about SLA plugins?17:35
msdubovboris-42, What do you mean?17:36
*** vivek-ebay has quit IRC17:36
boris-42msdubov I mean SLA plugins17:37
*** vivek-ebay has joined #openstack-meeting17:37
boris-42msdubov can I find them using rally info17:37
*** balajiiyer has left #openstack-meeting17:37
*** terryw has quit IRC17:37
boris-42msdubov this https://github.com/stackforge/rally/blob/master/rally/benchmark/sla/base.py#L85-L13517:37
msdubovboris-42, So say you type "rally info find max_seconds_per_iteration"17:38
msdubovboris-42, What do you expect to get?17:38
msdubovboris-42, Config sample?17:38
boris-42msdubov infromation about it17:38
boris-42msdubov I would like to type rally info find sla17:38
boris-42msdubov and find all sla's17:38
msdubovboris-42, Ah I see17:38
boris-42then type rally info find max_seconds_per_iteration17:39
boris-42and see information about it more detailed17:39
boris-42and probably in future samples17:39
boris-42when we finish @sample stuff17:39
*** matrohon has quit IRC17:39
msdubovboris-42, that actually doesn't work for scenarios/engines as well "rally info find engines" will be an invalid input17:39
msdubovboris-42, I want fix that17:39
msdubovboris-42, But as for SLA17:39
boris-42msdubov ya17:39
boris-42msdubov as well as a end user if you type rally info NovaServers17:39
boris-42msdubov output is quite misleading17:40
*** markwash__ has joined #openstack-meeting17:40
msdubovboris-42, Why?17:40
msdubovit is just a list of scenarios with one-line description17:40
*** vhoward has left #openstack-meeting17:40
boris-42msdubov you are getting output of "rally info"17:40
msdubovquite compact17:40
boris-42msdubov read one more time what I wrtoe17:40
boris-42msdubov "rally info NovaServers"17:40
msdubovboris-42, Of course you are getting the output of rally info17:40
boris-42msdubov that sux17:40
msdubovboris-42, We discussed that multiple times17:40
msdubovboris-42, I even made a patch that fixed this...17:41
msdubovboris-42, But it involved some dirty code17:41
boris-42msdubov you should specify17:41
boris-42msdubov Mike17:41
boris-42msdubov when I type "rally info NovaServers" I would like to see ouptut17:41
boris-42"Probably you thought to specify rally info find NovaServers"17:41
msdubovboris-42, You forgot what I told you about the command parsers...17:42
*** achanda has quit IRC17:42
msdubovboris-42, They don't support such stuff17:42
boris-42msdubov you should find the way17:42
msdubovboris-42, I implemented that "default" method17:42
boris-42msdubov =)17:42
msdubovboris-42, The only way is to remove common cliutils/argparse17:42
boris-42msdubov you should make one more IF conditions in it17:42
boris-42msdubov in default method17:42
boris-42msdubov like if there is third argument17:43
msdubovboris-42, There is no default method as of now, I removed it17:43
boris-42msdubov do helper17:43
msdubovboris-42, Take a look at the code17:43
msdubovboris-42, it just has a patched docstring17:43
boris-42msdubov I don't care actually about code17:43
boris-42msdubov I am talking about result17:43
boris-42msdubov result is misleading for end users17:43
boris-42msdubov it is not what we want17:43
msdubovboris-42, Well then I don't understand you17:44
boris-42msdubov I just said17:44
msdubovboris-42, You suggested removing that default method and leaving this "rally info find ..." syntax as is17:44
msdubovboris-42, And now ou require the opposite17:44
boris-42msdubov one more time17:45
boris-42rally info17:45
*** freemanbrandon has quit IRC17:45
boris-42<PRint pretty help>17:45
boris-42rally info find NovaServers17:45
boris-42<print info about NovaServers>17:45
boris-42rally info NovaServers17:45
*** ndipanov is now known as ndipanov_gone17:45
boris-42<say you probably think that run rally info find >17:45
boris-42^ msdubov  what is unclear?17:46
*** amcrn has joined #openstack-meeting17:46
*** morganfainberg is now known as alsonotstevemar17:46
*** alsonotstevemar is now known as morganfainberg17:47
*** achanda has joined #openstack-meeting17:47
boris-42msdubov okay just keep it in mind17:47
*** jckasper_ has joined #openstack-meeting17:47
boris-42msdubov and let's move17:47
boris-42#topic cleanup17:47
*** openstack changes topic to "cleanup (Meeting topic: Rally)"17:47
boris-42rook =)17:47
boris-42Okay I am working on pretty big patch that makes our cleanup system more production ready17:48
boris-42https://review.openstack.org/#/c/129060/17:48
*** simon-AS559 has joined #openstack-meeting17:48
boris-42I am going to finish it maybe today =)17:48
rookboris-42++17:48
boris-42So now cleanuping is quite simple, plugable, safe and parallel17:49
*** garyh has quit IRC17:49
boris-42only thing that you need is to create sublass17:49
*** achanda has quit IRC17:49
boris-42https://review.openstack.org/#/c/129060/16/rally/benchmark/context/cleanup/projects_resources.py17:49
*** jgallard has quit IRC17:49
boris-42for your resoruce17:49
boris-42everything else will be covered by cleanup stuff17:49
*** achanda has joined #openstack-meeting17:49
boris-42without end user (dev) attention which is nice=)17:50
boris-42rook about turning off cleanup17:50
*** jckasper has quit IRC17:50
boris-42rook actually making it as a separated command17:50
rookor a option in the yaml/json17:50
*** rbak has quit IRC17:50
*** simon-AS5591 has joined #openstack-meeting17:50
*** sarob_ has joined #openstack-meeting17:50
*** rbak has joined #openstack-meeting17:50
*** freemanbrandon has joined #openstack-meeting17:50
*** markmcclain has joined #openstack-meeting17:51
boris-42rook ya maybe)17:51
boris-42rook in any case we will find some solution17:51
boris-42rook after few more patches=)17:51
boris-42rook and refactorings17:51
*** raildo has joined #openstack-meeting17:52
boris-42#topic Docker imags17:52
*** openstack changes topic to "Docker imags (Meeting topic: Rally)"17:52
boris-42So we will have job that will create docker image on every merged patch17:52
*** emagana has quit IRC17:52
*** simon-AS559 has quit IRC17:52
boris-42https://review.openstack.org/#/c/131389/17:53
boris-42which will simplify life of end users a lot17:53
boris-42cause they won't need to install it=)17:53
boris-42by hands17:53
*** emagana has joined #openstack-meeting17:53
boris-42so17:55
*** markmcclain has quit IRC17:55
boris-42#topic Imprvoments in functional testing17:55
*** openstack changes topic to "Imprvoments in functional testing (Meeting topic: Rally)"17:56
boris-42Andrey Kurilin add patch that runs "rally verify" on every patch17:56
boris-42And checks that at least half of tests passed17:56
*** jdg has quit IRC17:56
boris-42So at least we have some basic function testing for rally verify commands, that won't allow us to break everything17:56
boris-42#topic New Rally report17:57
*** openstack changes topic to "New Rally report (Meeting topic: Rally)"17:57
*** emagana_ has joined #openstack-meeting17:57
*** Mandell has quit IRC17:57
*** emagana has quit IRC17:57
*** htruta has joined #openstack-meeting17:57
boris-42amaretskiy is continue work on this part17:58
*** henrynash has joined #openstack-meeting17:58
boris-42so a lot of new improments https://review.openstack.org/#/c/128991/ that I hope we will merge soon17:58
boris-42so we need to finish meeting17:58
boris-42Glad to see you guys17:58
boris-42#endmeeting17:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:58
openstackMeeting ended Tue Oct 28 17:58:39 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-10-28-17.07.html17:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-10-28-17.07.txt17:58
openstackLog:            http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-10-28-17.07.log.html17:58
*** sdake_ has quit IRC17:59
*** badveli_ has joined #openstack-meeting17:59
*** chandankumar has quit IRC17:59
*** tzabal has left #openstack-meeting17:59
*** zns has quit IRC17:59
*** marcoemorais has quit IRC17:59
*** marcoemorais has joined #openstack-meeting17:59
*** leonchio_ has joined #openstack-meeting18:00
*** olkonami has left #openstack-meeting18:00
*** amaretskiy has left #openstack-meeting18:00
morganfainbergdolphm, ayoung, bknudson, dstanek, jamielennox, morganfainberg, stevemar, gyee, henrynash, topol, marekd, lbragstad, joesavak, shardy, fabiog, nkinder, lloydm, shrekuma, ksavich, hrybacki, rharwood, grantbow, vdreamarkitex, raildo, rodrigods, amakarov, ajayaa, hogepodge, breton, lhcheng https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting18:00
henrynashhi18:00
dolphm\o/18:00
bknudsonhi18:00
lbragstadmorganfainberg: o/18:00
dstaneko/18:00
bknudsonbonjour18:00
*** otherwiseguy has joined #openstack-meeting18:00
ayoungI'm here.18:01
henrynashmorganfainberg: fyi, you should probably change the chair in:https://wiki.openstack.org/wiki/Meetings#Keystone_team_meeting18:01
*** imsurit has quit IRC18:01
morganfainberglol18:01
morganfainbergok18:01
gyee\o18:01
*** marcoemorais has quit IRC18:01
marekdgood evening!18:01
*** marcoemorais has joined #openstack-meeting18:01
henrynashsalut18:01
*** nonameentername has joined #openstack-meeting18:01
*** marcoemorais has quit IRC18:01
*** marcoemorais has joined #openstack-meeting18:02
rodrigodso/18:02
raildo\o18:02
htrutao/18:02
*** jamielennox has joined #openstack-meeting18:02
hogepodgeo/18:03
morganfainberg#startmeeting Keystone18:03
openstackMeeting started Tue Oct 28 18:03:07 2014 UTC and is due to finish in 60 minutes.  The chair is morganfainberg. Information about MeetBot at http://wiki.debian.org/MeetBot.18:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:03
*** openstack changes topic to " (Meeting topic: Keystone)"18:03
openstackThe meeting name has been set to 'keystone'18:03
*** nkinder has joined #openstack-meeting18:03
morganfainbergSo we're headed to Paris!18:03
*** ivar-laz_ has quit IRC18:03
morganfainbergwoot18:03
*** Mandell has joined #openstack-meeting18:03
dolphmwait what18:03
*** Haneef has joined #openstack-meeting18:03
marekdppl arriving Sat or Sun?18:03
lbragstadI'll be there Saturday18:03
marekd(some Monday i heard)18:03
bknudsonSun18:03
morganfainbergI'll be there on saturday morning18:04
dstanekSunday18:04
*** ivar-lazzaro has joined #openstack-meeting18:04
gyeeSat morning18:04
ayoungSun early...overnight Saturday night18:04
dolphmsaturday morning18:04
*** lhcheng has joined #openstack-meeting18:04
raildoSunday18:04
bknudsonflying through MSP?18:04
lbragstadI am!18:04
* marekd Sunday 18:04
lbragstadbknudson: ^18:04
dstaneki arrive at 7am give or take18:04
*** drankis has quit IRC18:04
jamielennoxSunday night18:04
bknudsonlbragstad: you'll be on the flight the day before.18:04
lbragstadbknudson: yeah, friday night arriving Saturday morning18:05
topolo/18:05
topolIll be there Sunday18:05
dstanekfor international fights is it better to carry-on or check baggage?18:05
bknudsonlbragstad: smart!18:05
*** jckasper_ has quit IRC18:05
topolSunday morning18:05
nonameenternameo/18:05
lbragstadbknudson: we'll see18:05
morganfainbergtopol, nice - first round of cognac on you? :P18:05
topoldstanek always best to carry on18:05
marekddstanek: both? :-)18:05
dolphmdstanek: always carry on! but i'm doing both18:05
nonameenternameSaturday18:05
dolphmcritical stuff stays on my back :)18:06
morganfainbergdstanek, depends on how long you'll be there18:06
morganfainbergsince i'm staying for an extra week i'll be checking clothing mostly.18:06
gyeeis there good place to get lub?18:06
dstanekmorganfainberg: only a week18:06
*** brich1 has joined #openstack-meeting18:06
morganfainbergfor 1wk i'd do carry on unless you need lots of stuff18:06
dstaneki almost always carry on, but i've never done international18:06
topolI carried on even for 7 days to Hong Kong. I wont go back to checking bags18:06
bknudsonI'm also staying an extra week.18:06
topolHad them get ripped to shreds in the past18:06
dolphmtopol: ++18:06
topoldstanek if you can carry on definetly do that18:07
dolphmi only brought my backpack to atl18:07
morganfainbergtopol, it's when you start hitting ~12-20 days it's hard to do as a single carryon internationally18:07
dolphmmorganfainberg: bring detergent18:07
dolphmproblem solved18:07
henrynashmorganfainberg: or hard to keep friends18:07
topolmorganfainberg if I leave for 12 days my wife will kill me. wont be a problem18:07
morganfainbergdolphm, *or* abuse my friends in Lyon when i'm visiting for their washing mashine18:07
marekdhenrynash: unless they did the same.18:07
morganfainberg;)18:07
morganfainberghenrynash, haha18:08
topoldolphm, they sell it at the laundromats18:08
topolwe do that when we goto Italy18:08
ayounghenrynash, you are sleeping at home each night, right?18:08
ayoungjust commuting via train?18:08
henrynashayoung: no..but nice idea!18:08
dolphmtravel size laundry soap http://www.amazon.com/dp/B001TUZS98/18:08
bknudsonI wouldn't want to spend my time in paris washing clothes.18:09
ayoungCuz crashing with you was my backup sleeping plan18:09
henrynashayoung: ah!18:09
bknudsonI can do that here.18:09
morganfainbergbknudson, pay the hotel to do it for you. most will (even internationally)18:09
*** sarob has quit IRC18:09
morganfainbergok so.18:09
morganfainberg#topic Review of Keystone Blueprints for "Trivial" Status18:09
*** openstack changes topic to "Review of Keystone Blueprints for "Trivial" Status (Meeting topic: Keystone)"18:09
topolayoung how come you can never afford a room?18:09
*** pballand has quit IRC18:10
*** dprince has joined #openstack-meeting18:10
jamielennoxayoung: if you're looking at backup plans i'm well and truly screwed18:10
morganfainbergWe're going to try something new here. mostly this is just to cover the plan once we hit the swing of things.18:10
marekdjamielennox: ?18:10
*** _nadya_ has quit IRC18:10
jamielennoxmarekd: he organized my accom18:10
ayoungtopol,  "Backup"  meaning when jamielennox kicks me out.  once again he is subjected to sharing a room with me18:10
marekdjamielennox: ayoung ?18:10
ayoungmarekd, same company, trying to keep down costs18:10
morganfainberg#undo18:11
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x3577510>18:11
marekdayoung: i was a studnent not so long time ago - i know what you are talking.18:11
*** noelbk has quit IRC18:11
morganfainbergok we can discuss accomodations in -keystone18:11
morganfainberg:)18:12
marekdyes18:12
morganfainberg#topic Review of Keystone Blueprints for "Trivial" Status18:12
*** openstack changes topic to "Review of Keystone Blueprints for "Trivial" Status (Meeting topic: Keystone)"18:12
bknudsonwhat are the blueprints to review?18:12
ayoungActually, morganfainberg you want to explain what is going on with backlog etc?18:12
morganfainbergThis is basically the way we're going to handle BPs that *dont* have a spec going forward, we will do a quick review each meeting and classify as "trivial" meaning no Spec needed18:12
topolcool18:13
morganfainbergif they are trivial they're approved and can be targeted for *this* milestone (or any)18:13
bknudsonmaybe I'd get more reviews if I wrote up a bp.18:13
gyeecriteria for trivial status?18:13
morganfainbergan example of trivial: Fix documents18:13
henrynashmorganfainberg: I have one: https://blueprints.launchpad.net/keystone/+spec/remove-role-metadata18:13
morganfainberggyee,  i'm working on full details, but basically stuff that doesn't change the REST API, is something "we should just do"18:14
henrynashmorganfainberg: this might be a good test…it’s not as trivial as documentation18:14
bknudsonhenrynash: doesn't affect the API?18:14
morganfainbergand is self explanitory18:14
morganfainberge.g. CADF everywhere18:14
henrynashbknduson: teh manager-driver api, yes, not the controller-manager api18:14
*** noelbk has joined #openstack-meeting18:14
morganfainbergyes we all agree we should make all notifications cadf, but do we need a big heavy formalized spec for it? probably not18:14
gyeesounds reasonable18:14
henrynashbknudson: which we may say, menas it’s not trivial?18:14
morganfainbergso lets take a look at keystone-client ( henrynash we'll use yours in a sec )18:15
morganfainberg#link https://blueprints.launchpad.net/python-keystoneclient18:15
bknudsonhttps://blueprints.launchpad.net/keystone/+spec/remove-role-metadata seems basic enough to me.18:15
bknudsonI hate to call it trivial.18:15
henrynashbknudson: :-)18:15
morganfainbergif you look at the list ^ we're only interested in "undefined, new, and untargeted" BPs18:15
bknudsonkeystoneclient bp isn't going to affect the rest api18:15
morganfainbergfor ksc there are 6.18:16
morganfainbergbknudson, exactly and also because the list is short, i'm using it to explain things18:16
bknudsonI've got code for https://blueprints.launchpad.net/python-keystoneclient/+spec/keystoneclient-i18n , just didn't know there was a bp.18:16
jamielennoxkeystoneclient has always been a little weird about blueprints - i don't think it's just me18:16
morganfainbergbknudson, that is also why reviewing these helps :)18:16
*** kylek3h has quit IRC18:16
morganfainbergjamielennox, yeah.18:16
dolphmjamielennox: ++18:17
morganfainbergso we're not oging to go through all of these this meeting. we'll pick just a couple ( like henry's ) and I'll finish cleaning everything up so the first meeting post summit we can start this process.18:17
dolphmstory board should unify the approach between clients & server18:17
morganfainbergdolphm, ++18:17
dolphm*excited*18:18
morganfainbergand storyboard will help make this waaaaay better18:18
*** tellesnobrega has joined #openstack-meeting18:18
morganfainbergok so lets look at henry's bp now.18:18
morganfainberg#link https://blueprints.launchpad.net/keystone/+spec/remove-role-metadata18:18
jamielennoxnot to derail again but do we expect storyboard soon?18:18
morganfainbergjamielennox, not this cycle18:18
krotscheckjamielennox: nope.18:18
morganfainbergit's in beta for -infra to use18:18
morganfainbergjamielennox, help krotscheck get storyboard in shape for everyone else :)18:19
krotscheckjamielennox: Come to the lighting talk at the summit on monday to get an update.18:19
bknudsonwe need a storyboard demo at the summit18:19
morganfainberg^^ lightning talk18:19
marekdbknudson: what's a storyboard?18:19
krotscheckThe lightning talk is titled “Storyboard: Lightning Walkthrough"18:19
jamielennoxi'd be keen to see it, i saw some of the beta but didn't really look at all the features18:19
lbragstadmarekd: a new tracking tool to replace launchpad18:19
marekdlbragstad: thanks.18:19
rodrigodslbragstad, marekd, wow18:19
morganfainbergok18:20
morganfainbergso Henry's BP18:20
morganfainberghttps://blueprints.launchpad.net/keystone/+spec/remove-role-metadata18:20
henrynashso this is non-trivial in that it isn’t, say, just documentation....18:21
morganfainbergthis looks like something that doesn't affect the API contract18:21
*** ignacio-scopett1 has quit IRC18:21
gyeebut involves migration18:21
gyeedata migration I mean18:21
henrynashit does affect the manager->driver API….but not the controller->manaager API18:21
henrynashgyee: no18:21
gyeeso the meta are leftovers?18:22
*** ignacio-scopetta has joined #openstack-meeting18:22
*** mjturek has left #openstack-meeting18:22
morganfainberghenrynash, this might be a case because it affects more things that we want a spec, but i'm open for anything to be classified as "no spec needed" (as long as it doesn't change API contract)18:22
topolhenrynash you can just remove the role metadata and all is well?18:22
ayoungIs there any demand to PKI signe CADF messages? Or sign at log rotation?18:22
ayoungah..sorry, I'm behind18:22
morganfainbergayoung, different topic18:22
henrynashgyee: yes…a few old manager APIs use it…and the drivers “fake up” the metadata from the underlying data18:22
gyeehenrynash, k, I see18:23
*** garyh has joined #openstack-meeting18:23
dolphmtopol: it's about changing the "metadata" construction in the manager->driver API and replacing it with something more explicit18:23
morganfainbergi could see this one go either way tbh.18:23
ayoungthen lets go spec18:23
ayoungif there is a question...it probably means non-trivial18:24
henrynashso I’m open to doing a spec if people think it needs it….I think this one is a good test of the border line18:24
ayoungwe can always downgrade if there isn't enough there18:24
topolfeels like it needs a spec18:24
henrynashok, done18:24
morganfainbergi think this one would be better as a spec because there is a question of the more-explicit metadata -> other things18:24
*** carl_baldwin has quit IRC18:24
topolspecs dont really help the dolphs and morgans of the world.  but as a member of the unwashed masses they really help me to understand keystone arch and direction18:25
henrynashI think this one is probably the type that you people needs to see a spec before they could agree you didn;t need a spec :-)18:25
ayoungLet me make this explicit:  if you are reviewing one of my specs, and you want to rewrite a section of it, please do so, and add yourself as a contributor/author18:25
*** bobt has joined #openstack-meeting18:25
morganfainbergayoung, i'll circle back on the backlog thing18:25
*** vivek-ebay has quit IRC18:25
ayounguntil a spec is approved, lets treat them as collaborative documents18:26
henrynashmorganfainberg: let’s try and find one that we can agree that’s trivial so we can hone in where the boundry is18:26
*** zns has joined #openstack-meeting18:26
morganfainberghenrynash, looking for one now18:26
morganfainbergactually18:26
ayoungIf it is a one line change already written18:26
*** vivek-ebay has joined #openstack-meeting18:26
henrynashtopol: unwashed?  is that a continuation of the “do i packa carry on or not for paris"?18:27
morganfainberghenrynash, https://blueprints.launchpad.net/keystone/+spec/deprecate-ssl-functions18:27
*** zns has quit IRC18:27
ayoungNone of mine are Trivial18:27
topolhenrynash I refused to answer on the basis that I may incriminate myself18:27
*** SridharRamaswamy has quit IRC18:27
morganfainbergthis one is likely something that we "don't" care about a spec for.18:27
morganfainberg#link https://blueprints.launchpad.net/keystone/+spec/deprecate-ssl-functions18:27
morganfainbergit's mostly affecting testing18:28
*** zns has joined #openstack-meeting18:28
*** jckasper has joined #openstack-meeting18:28
*** pballand has joined #openstack-meeting18:28
morganfainbergif we make the mechanism for handling the "self signed CA" better, everyone wins18:28
ayoungmorganfainberg, I have a solution to that!18:28
morganfainbergbut it wont have massive impact on too many things outside of devstack18:28
gyeedogtag? :)18:28
morganfainbergand/or toy setups.18:28
morganfainbergso.18:28
morganfainbergthoughts on https://blueprints.launchpad.net/keystone/+spec/deprecate-ssl-functions ?18:29
dolphmany blueprint that only affects keystone developers should be second guessed for necessity18:29
bknudsonnot sure what the point is of making self signed CA more complicated.18:29
ayoungUse Certmonger18:29
henrynashayoung: so on this one, we would explain how to set up certmonger (in the place of wherever we explain pki_setup)?18:29
ayoungyep18:29
morganfainbergbasically.18:29
henrynashayoung: ok18:29
jamielennoxmorganfainberg: so as much as i think yes trivial the advantage of a spec there is that later we can point someone to it and say why we did it18:29
ayoungand...for the selfsign, we would use certmaster.18:29
ayoungits a trivial CA18:29
bknudsonopenssl is a trivial ca18:29
dolphmor just get certs from anywhere not keystone18:30
jamielennoxmorganfainberg: because as much as i consider that obvious it's used by enough deployments that someone will notice it missing18:30
morganfainbergdolphm, exactly18:30
morganfainbergjamielennox,  i'm not saying we want this bp18:30
dolphmi don't see any reason at all why keystone should be advocating for certmonger18:30
*** thedodd has quit IRC18:30
morganfainbergin fact i think it's not worth the effort18:30
topolso here is a question. what I liked about the specs is I can always go and do a review and see what needed to be reviewed.  With trivial BPs now I have to look another place as well and do a merge/diff18:30
dolphmthere's an argument to make for devstack, i suppose18:30
*** safchain has quit IRC18:30
morganfainbergbut, this is a case where the BP if we wanted it doesn't need a spec18:30
jamielennoxdolphm: ++ keystone doesn't care, just configure it with certs18:30
bknudsonit would be interesting to see it in devstack18:30
ayounghttps://fedorahosted.org/certmaster/18:30
morganfainbergso in short, i'd say ditch this BP for keystone.18:31
morganfainbergbut it's not worthy of a spec even if we wanted it.18:31
ayoungis XML RPC, in a stand alone server18:31
dolphmjamielennox: and actually half of keystone's ssl / pki config options are so that it can generate it's own certs... so all those can go away18:31
morganfainbergi'm actually a fan of repurposing this spec to "remove self-signed SSL options from keystone"18:31
jamielennoxdolphm: yep, cause they are really confusing options when you come to it with a cert already18:31
morganfainbergand not care *how* we get there.18:31
bknudsonthey can be changed to cli options on keystone-manage18:32
morganfainberge.g. "here is where you stick your certs"- how devstack works is not really keystone's scope.18:32
jamielennoxbknudson: remove the whole command from -manage18:32
topolmorganfainberg, because in real deployments the self-signed is never used correct?18:32
bknudsonif we still want to make it somewhat easy18:32
jamielennoxmorganfainberg: ++18:32
morganfainbergtopol, , exactly18:32
bknudsonI'm also fine with removing the function18:32
jamielennoxmorganfainberg: devstack already has a CA and cert generating component18:32
ayoungI'd leave the command in manage and make it call certmonger functions instead18:32
*** cbouch has joined #openstack-meeting18:32
*** pnavarro has joined #openstack-meeting18:32
ayoungbut this discussion ios beyond the scope of this meeting18:32
jamielennoxayoung: nope - kill it18:32
morganfainbergok, so proposal: make this BP "remove self-signed cert generation options"18:33
morganfainbergand call it a "no-spec needed" BP18:33
topoljamielnnox ++ less code to learn/maintain :-)18:33
*** garyh has quit IRC18:33
bknudsonI don't know if we need to deprecate the function18:33
bknudsonor if we can just remove it18:33
jamielennoxmorganfainberg: +1 to change purpose, -1 to no spec - it doesn't need to be long but i think it's more about documenting why we removed it18:34
dolphmthis could just be merged into the deprecated-for-kilo bp wherever that is18:34
topolbknudson may be right. how do we know some one didnt find a crazy use for it?18:34
morganfainbergdolphm, i like that18:34
jamielennoxor merged into deprecated would be fine18:34
bknudsonour products use it.18:34
bknudsonbut we can adapt to this one pretty easily18:34
*** otherwiseguy has quit IRC18:34
morganfainbergok will kill this BP, with the comment that we should merge this topic into "removed-in-kilo"18:35
henrynashso I agree this doesn’t need a spec, but just becasue it is a no-spec BP,  shoudl not mean it is any more likely to achieve agreement….we need to allow people to object just as a full spec BP18:35
morganfainberghenrynash, we can discuss in code review and on the BP.18:35
jamielennoxi think pki_setup was my first keystone contribution - it seemed like a good idea at the time18:35
*** SridharRamaswamy has joined #openstack-meeting18:36
morganfainberghenrynash, largely if there is a question it wont be "approved"18:36
morganfainberghenrynash, and we can say "no agreement that this is trivial"18:36
henrynashmorganfainberg: yep18:36
morganfainbergah here is one18:37
morganfainberg#link https://blueprints.launchpad.net/keystone/+spec/alembic18:37
morganfainberghonestly, probably doesn't need a spec.18:37
*** padkrish has joined #openstack-meeting18:37
bknudsonthere are lots of questions around the conversion to alembic18:37
morganfainbergit could help to have one but i think the spec will be "migrate data to alembic"18:37
morganfainbergbut i don't think a spec will answer them18:38
morganfainbergin any meaningful way18:38
ayoungI think there are a lot of devils hiding in the weeds with the migrations18:38
bknudsonis it only for new migrations,or is it existing ones, too?18:38
morganfainbergthis isn't a trivial bp, it is a "there isn't a lot of ways to do this, but lots of things to change?18:38
morganfainberg"18:38
ayoungwhat if we accect a hybrid18:38
dolphmbknudson: i think ceilometer (?) did the transition successfully mid cycle using only new migrations18:38
ayoungsql-a up to now, alembic assumes that SQL has been run first18:39
bknudsonseems like we do have to move away from sqlalchemy-migrate at some point since I think it's abandoned.18:39
jamielennoxmorganfainberg: agreed, i don't think the spec will tell anything about the code direction - so BP is good for tying it together but i'm ok with a BP only18:39
morganfainbergdolphm, that is the general direction we would like to go is possible18:39
*** pnavarro has quit IRC18:39
ayoungwhen we get to the point that we can collapse the migrations, and drop all of the sql-a ones, we drop sql-a18:39
bknudsonayoung: I like that plan.18:39
dolphmayoung: ++18:39
*** ddieterly has quit IRC18:39
*** dane_leblanc has quit IRC18:40
morganfainbergi'll change the topic in the meeting from "Trivial" to "No-Spec-Required"18:40
ayoungshould i #action that?18:40
*** marcoemorais has quit IRC18:40
morganfainbergayoung, sure!18:40
*** ddieterly has joined #openstack-meeting18:40
*** carl_baldwin has joined #openstack-meeting18:40
bknudsonwe should make the decision that kilo is alembic or not before we get a migration18:41
ayoung#action  Current SQl migrations will stay in SQL Alchemy.  New migrations will be done in Alembic.  We will have a Hybrid solution for a couple of releases until we can collapse all of the SQL-Alchemy ones into Alembic.18:41
dolphmbknudson: well we need the support in db_sync to run both18:41
dolphmbknudson: (first)18:41
dolphmbknudson: when we accept that, the rest of kilo becomes alembic18:41
ayoung++18:41
*** ddieterly has quit IRC18:41
*** ddieterly has joined #openstack-meeting18:42
*** padkrish has quit IRC18:42
dstanekall these great details should get pushed into the blueprint or spec18:42
ayoungdstanek, Agreed18:42
lbragstad++18:42
morganfainbergok18:43
morganfainbergso lets move on. we have other topics to cover18:43
morganfainbergayoung, mind updating the spec?18:43
*** sdake_ has joined #openstack-meeting18:43
morganfainbergerm bp18:43
ayoung"When in doubt, spec it out."18:43
henrynashmaybe the spec-less BP is an urban myth?18:43
ayoungWill do18:43
*** pballand has quit IRC18:43
topolayoung +++18:43
*** neelashah has quit IRC18:43
morganfainberg#topic QA Liason18:43
*** openstack changes topic to "QA Liason (Meeting topic: Keystone)"18:43
gyeehenrynash, nice!18:43
henrynash(or maybe just a lot rarer than we thought)18:43
morganfainberg#link https://wiki.openstack.org/wiki/CrossProjectLiaisons#QA18:43
morganfainbergwe need someone to take the role on.18:44
morganfainberg(please)18:44
*** cdub has joined #openstack-meeting18:44
morganfainbergthis is the same as oslo and VMT liasons18:44
dstanekhenrynash: there is always something to argue about18:44
morganfainbergjust for QA18:44
dstanekmorganfainberg: as in tempest like stuff?18:44
morganfainbergdstanek, yep18:44
lbragstadso, same things as oslo liason?18:44
morganfainbergdstanek, and the gate etc.18:44
dstanekmorganfainberg: i'll do that18:44
bknudsoneveryt time the gate breaks you know they're going to blame keystone!18:45
lbragstadI'll be backup18:45
dstanekunless someone else wants to18:45
morganfainbergdstanek,awesome please add yourself tot he wiki18:45
morganfainberg#action dstanek QA Liason, lbragstad backup18:45
morganfainberg#topic Keystone IRC Meeting Cancelled November 3rd and November 10th18:45
*** openstack changes topic to "Keystone IRC Meeting Cancelled November 3rd and November 10th (Meeting topic: Keystone)"18:45
morganfainbergwe'll be at the summit and the post-summit one we likely don't have a lot to talk about18:45
morganfainbergso next keystone meeting will be the 17th18:46
gyeebefore thanksgiving18:46
marekdNov 10th is a monday ?18:46
morganfainbergplus lots of people will either still be in France or jet lagged18:46
morganfainbergsorry 11th18:47
morganfainbergmarekd, , good catch18:47
morganfainberg#topic Keystone IRC Meeting Cancelled November 3rd and November 11th18:47
*** openstack changes topic to "Keystone IRC Meeting Cancelled November 3rd and November 11th (Meeting topic: Keystone)"18:47
morganfainbergand the next meeting is actually tyhe 18th18:47
bknudsonworks for me.18:47
henrynasherr…can’t be the 3rd then either18:47
*** kebray has quit IRC18:47
morganfainberg#undo18:47
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x366ff10>18:48
henrynash4th & 11th cancelled18:48
morganfainberg#topic next keystone meeting is 18th. (yes i can't do date math--morganfainberg)18:48
*** openstack changes topic to "next keystone meeting is 18th. (yes i can't do date math--morganfainberg) (Meeting topic: Keystone)"18:48
morganfainbergok18:48
morganfainberg#topic Scoping federated tokens with 'token' identity method18:48
*** openstack changes topic to "Scoping federated tokens with 'token' identity method (Meeting topic: Keystone)"18:48
morganfainbergmarekd, o/18:48
marekdo/18:48
marekdso that should be quick18:48
bknudsondoesn't it work now?18:49
marekdwe spoke with jamielennox last week about it, and it turns out that there is a relatively simple way to unify scoping federated classic tokens. No need to add extra method name 'saml2' or 'mapped'.18:49
marekdjust wanted to hear your opinions18:49
marekdit's is now: https://github.com/openstack/identity-api/blob/master/v3/src/markdown/identity-api-v3-os-federation-ext.md#request-a-scoped-os-federation-token-post-authtokens18:49
marekdand looks like we could use 'token' which would simplyfy few things, let us remove some code from keystoneclient18:50
bknudsony, it's the same as getting a token from a token18:50
bknudsonwhat has to change, though?18:50
morganfainbergbknudson, keystoneclient code/18:51
morganfainberg?18:51
marekdno, keystonecode18:51
gyeeif the payloads are the same, then yes18:51
marekdkeystone code18:51
gyeeauth payloads I mean18:51
topoldo you change the info sent in on the restful APIs?18:51
marekdgyee: payload are not the same18:51
ayoungUm...that is not why we were doing that in the past18:51
jamielennoxbknudson: ++ that's kind of the point, i don't know why it was ever a different auth method anyway, it should have always just been token18:51
marekdwe need to differencitate if that a federated or 'classic' token18:51
ayoungthe "method" is what the client sets...like "kerberos"18:51
ayoungas you recall, I didn't even want that...18:51
gyeeif the auth  payloads are not the same, then we need different identifications18:51
*** kebray has joined #openstack-meeting18:51
ayoungcan we just drop the methods all together?18:51
*** pnavarro has joined #openstack-meeting18:51
dolphmayoung: not really18:51
marekdhttps://review.openstack.org/#/c/130593/1/keystone/auth/plugins/token.py18:52
ayoungdidn't think so, but worth asking18:52
marekdi made a super quick fix18:52
*** oanufrie1 has joined #openstack-meeting18:52
morganfainbergoh that is kindof slick marekd18:52
*** oanufrie1 has left #openstack-meeting18:52
morganfainbergmeta programing without metaprogramming.18:52
marekdmorganfainberg: i don't say it's the best way - we could do some upper object TokenBase that would call either Mapped or Token classes18:53
* morganfainberg wonders how that can break things18:53
gyeethat's kindda chaotic though, have to parse the payload in order to figure what it is18:53
morganfainbergprobably should do that.18:53
morganfainbergif we're parsing payload18:53
marekdbut this is somewhere where this 'switch' needs to be done, as we must enter Token.authenticate() method18:53
morganfainbergwe're actually doubling the validate in this case18:53
gyeewe need something unambiguous18:54
ayoungso method name should indicate what was used to request the token18:54
jamielennoxit would make the client side a whole lot easier - there is no reason that an unscoped federation token should be any different from a regular unscoped token18:54
ayoungbut, I'd be ok with the method being added to the token after the fact, and not be part of the token request18:54
ayoungIN fact, I'd prefer iot18:54
ayoungit18:54
dolphmjamielennox: ++18:54
morganfainbergmy only concern here is we're doubling the validate call (very expensive)18:54
morganfainberg(6 mins)18:54
morganfainbergwe can talk about this a little further in -keystone, but i think tokens should be tokens18:55
*** dane_leblanc has joined #openstack-meeting18:55
morganfainbergnot "federated tokens are special"18:55
gyeeunscoped token is unscoped token, there shouldn't be any differece18:55
ayoungThe issue I have is that I need different AUTH_URLS for Kerberos etc18:55
marekdmorganfainberg: it's a pure wip as i didn't know if its worth working on that18:55
*** baoli has quit IRC18:55
marekdmorganfainberg: but looks like validation doesn't need to be done twice.18:55
morganfainbergok18:55
morganfainbergneed to move on18:56
marekdanyway, is it worth working on that? no -2 objections?18:56
gyeemethod and scope are two different thing18:56
morganfainbergno objections from me :)18:56
ayoungmarekd, lets talk next week18:56
morganfainberg#topic Hierarchical Multitenancy API spec18:56
marekdayoung: sure18:56
*** openstack changes topic to "Hierarchical Multitenancy API spec (Meeting topic: Keystone)"18:56
morganfainbergrodrigods, o/18:56
ayoungwe might be able to go even further18:56
rodrigodso/18:56
topoldoes it break anything if someone was already using this?18:56
morganfainberg(sorry you only have a couple mins)18:56
raildoo/18:56
marekdayoung: yes yesyes!18:56
rodrigodsok18:56
rodrigodsquick one: please please review  https://review.openstack.org/#/c/130103/ , it's a dependency from https://review.openstack.org/#/c/117786/ (once we had a plan that everything would be merged by the summit or just after it)18:56
rodrigodsthat's it =)18:56
raildo++18:56
*** andreykurilin_ has joined #openstack-meeting18:56
*** rook has quit IRC18:57
morganfainbergplease aim to get them reviewed merged as close to summit/post summit as possible18:57
bknudsonseems strange that an extension is modifying the core API18:57
gyeek18:57
rodrigodswill be here to do fix as soon we have -1s18:57
morganfainbergbknudson, i want to talk about extensions at the summit18:57
morganfainberghallwaytrack/pod18:57
morganfainberg#topic Splitting up Assignments18:57
*** openstack changes topic to "Splitting up Assignments (Meeting topic: Keystone)"18:57
morganfainberghenrynash, o/18:57
morganfainbergreal quick!18:57
bknudsony, another way to put it is why is HMT an extension18:58
henrynashok , wanted to get a quick read on if people are gnerally supprotinve of this18:58
rodrigodsbknudson, it isn't, just the inherited roles part is18:58
dolphm(2 min)18:58
gyeehenrynash, yes18:58
morganfainberghenrynash, it makes logical sense to me.18:58
*** cbouch has quit IRC18:58
henrynashany violent objections?18:58
ayoungLets make Domains into projects and nest projects and call them tenants18:59
ayoungdamn...too slow again18:59
henrynashayoung: we can do that nicely once we have split this up!18:59
*** scotm has quit IRC18:59
ayounghenrynash, do roles stay with domains?18:59
henrynashyes….domains, project and roles are the “base entities”18:59
*** marcoemorais has joined #openstack-meeting18:59
dstanekTrivial question that came up in a review. LOG.warn vs LOG.warning? Should we standardize?18:59
morganfainbergand thats time., take it to -keystone please19:00
morganfainberg#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
*** bswartz has joined #openstack-meeting19:00
openstackMeeting ended Tue Oct 28 19:00:04 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-10-28-18.03.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-10-28-18.03.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-10-28-18.03.log.html19:00
*** zns has quit IRC19:00
clarkbo/19:00
hogepodgeo/19:00
fungiyo19:00
nibalizero/19:00
mmedvedeo/19:00
*** bknudson has left #openstack-meeting19:00
pleia2o/19:00
ianwo/19:01
jeblair#startmeeting infra19:01
openstackMeeting started Tue Oct 28 19:01:20 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
jeblair#link agenda https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting19:01
jeblair#link previous meeting http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-10-21-19.00.html19:01
*** raildo has left #openstack-meeting19:01
*** jaypipes-afk is now known as jaypipes19:01
*** jamielennox has left #openstack-meeting19:01
jeblair#topic  Actions from last meeting19:01
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:01
zaroo/19:01
jeblairclarkb figure out gerrit per project third party voting ACLs and third party accounts via openid19:01
*** pelix has quit IRC19:02
clarkbI have not started that19:02
*** wenlock has joined #openstack-meeting19:02
jeblairclarkb: still want to do it?19:02
clarkbyup I can do it19:02
jeblair#action clarkb figure out gerrit per project third party voting ACLs and third party accounts via openid19:02
*** emagana_ has quit IRC19:02
jeblairclarkb write py26 deprecation email19:02
clarkbthat was written and sent19:02
jeblairi think that one happened?19:02
clarkband we deprecated py26 on th eserver projects already19:02
cody-somervilleo/19:03
jeblairclarkb: is there more deprecation that needs doing?19:03
krtayloro/  sorry I'm late19:03
*** emagana has joined #openstack-meeting19:03
fungideprecation for other projects (e.g. infra) and also stackforge19:03
clarkbjeblair: ya, potentially some stuff to sort out around oslo projects (thought we may just leave them as is)19:03
*** tellesnobrega has left #openstack-meeting19:03
*** rms_13 has quit IRC19:03
clarkbthen infra and stackforge19:03
jeblairdoes infra need 2.6 for anything?19:03
fungithe other projects review was waiting for confirmation from impacted projects' ptls right?19:03
jeblairmaybe jjb?19:03
clarkbjeblair: any code that runs on centos will need it so zuul should keep it probably19:04
clarkb(for the zuul-cloner)19:04
clarkbjjb is probably reasonable to keep as well19:04
pleia219:04
clarkbeverything else probably doesn't need it19:04
*** dane_leblanc has quit IRC19:04
jeblairclarkb: oh, that's a really good point re zuul-cloner19:04
fungi#link https://review.openstack.org/#/q/status:open+project:openstack-infra/project-config+branch:master+topic:python26,n,z19:04
fungifor the reviews in question19:04
clarkband we are going to give stackforge projects a lot of time (fungi was uncomfortable with quick switching them especially with all the summit goings on)19:05
*** emagana_ has joined #openstack-meeting19:05
*** emagana has quit IRC19:05
fungischeduled for november 30th according to the announcement19:05
*** sdake_ has quit IRC19:06
*** topol has quit IRC19:06
jeblairok19:06
jeblairfungi draft third-party testing liaisons section for wiki19:06
fungithat was a tentative item pending clarkb's testing19:06
*** lhcheng has left #openstack-meeting19:07
*** dprince has quit IRC19:07
*** padkrish has joined #openstack-meeting19:07
fungineed to know whether we actually need liasons for requests to disable/reenable accounts, or whether we can engineer that in per-project acls as well19:07
fungie.g. preventing them from commenting at all19:07
*** AJaeger has joined #openstack-meeting19:07
*** mestery has quit IRC19:07
jeblairfungi: oh, i thought we wanted liasons anyway19:08
fungiso no action there yet19:08
* AJaeger is sorry for beeing late19:08
*** cjellick has quit IRC19:08
jeblairat least, i asked that last meeting and thought i got an affirmative response19:08
fungier, right, as rallying points for the third-party ci operators testing the respective projects19:08
jeblair19:44:36 <fungi> but beyond that, the liaisons idea acts as a rallying point for the third-party testers on those projects in place of our infra team19:08
jeblair19:44:42 <krtaylor> third-party liaisons would also be helpful for third-party systems, a point of contact for systems with questions19:08
jeblair19:44:56 <jeblair> so it sounds like liasons may still be useful even if we go to self-service, both for us (disabling for abuse, and facilitating onboarding of new ci systems with the projects themselves)19:08
krtayloryes, I think it was needed either way19:08
fungiso the question is whether they'll be needed for just that, or for additional tasks19:09
*** dane_leblanc has joined #openstack-meeting19:09
*** mestery has joined #openstack-meeting19:09
krtaylorit is a starting point for additional tasks19:09
jeblairfungi: yep.  so you want to wait until we know what we're asking of them before we starting asking it of them?19:09
fungii'll get the initial writeup knocked out in that case and we can amend it with further needs as they become apparent19:09
jeblairfungi: that sounds like a reasonable plan19:09
krtaylor+119:09
fungii'm indifferent there, but wouldn't be a bad idea before actually making it official19:09
hogepodgefungi I'd like to be involved and as helpful as I can be.19:10
*** marcoemorais has quit IRC19:10
jeblair#topic Priority Efforts: Swift logs19:10
*** openstack changes topic to "Priority Efforts: Swift logs (Meeting topic: infra)"19:10
fungi#action fungi draft initial third-party liaisons description, to later be amended as needed before publication19:10
*** manishg has joined #openstack-meeting19:10
*** scotm has joined #openstack-meeting19:10
fungihogepodge: thanks--i'll keep you in the loop19:10
jeblairjhesketh: are you around?19:11
*** sankarshan is now known as sankarshan_away19:11
*** juzuluag has quit IRC19:11
krtaylorfungi, I'll be glad to help as well19:11
*** johnthetubaguy is now known as zz_johnthetubagu19:11
fungikrtaylor: appreciated19:11
*** novas0x2a|laptop has joined #openstack-meeting19:12
fungii'm assuming either some of us are lagging badly or jhesketh is not present19:13
jeblairlast week we discussed that we may need a jenkins plugin to do log uploads regardless of job status19:14
clarkbin order to capture logs when jobs fail19:14
jeblairseparately, an internal hp discussion brought up this plugin: https://wiki.jenkins-ci.org/display/JENKINS/PostBuildScript+Plugin19:14
jeblairwhich is a way less insane way of doing that than the last time i looked19:14
*** markwash__ has quit IRC19:14
*** dpaterson has quit IRC19:15
jeblair(there was a plugin where you needed to regex match on .* in the console log to have it run -- weird)19:15
fungiprobably makes more sense than hacking together yet-another-java-project19:15
jeblairso at some point, i expect we'll want to look into using that19:15
*** darvon has quit IRC19:15
*** pnavarro has quit IRC19:15
jeblairand if hp uses it, hopefully we can get some feedback there too19:15
*** darvon has joined #openstack-meeting19:16
clarkbthat plugin looks reasonable19:16
jeblairyeah, it _seems_ like it shouldn't have any sync points or other jenkins things that make us unhappy19:16
*** sdake_ has joined #openstack-meeting19:16
jeblairthat's all i have on this one19:16
fungi#link https://wiki.jenkins-ci.org/display/JENKINS/PostBuildScript+Plugin19:16
jeblairoh thanks :)19:17
jeblair#topic Priority Efforts: Puppet module split19:17
*** openstack changes topic to "Priority Efforts: Puppet module split (Meeting topic: infra)"19:17
jeblairasselin: ping19:17
jeblair" asselin is working on Jenkins module split, when should we schedule the freeze and split?" is in the agenda19:17
*** andreykurilin_ has quit IRC19:17
krtaylorhere is the link to the topic19:17
krtaylorhttps://review.openstack.org/#/q/branch:master+topic:module-split,n,z19:17
*** andreykurilin_ has joined #openstack-meeting19:18
fungii think this spun out of yesterday's discussions about the next ways to coordinate the switch-over step so as to minimize module-specific freeze periods19:18
fungis/next/best/19:18
jeblairokay, let's talk about that then :)19:18
krtaylormmedvede, ^^^19:18
fungianteaya: this was something you asked to have on the agenda i think?19:18
fungioh, right, she may be travelling today19:19
clarkbwe accidentally merged half of a split's changes19:19
fungiso, i think it was the puppet-kibana module19:19
clarkbyup19:19
fungithe new project creation change got approved/merged19:19
fungiwith minimal fanfare19:19
*** garyh has joined #openstack-meeting19:19
jeblairthen what did not get merged?19:20
fungiluckily someone (anteaya?) noticed and pointed out we should refrain from making changes to the copy of that module in system-config now19:20
clarkbjeblair: the system-config change I asked you guys to review really quickly yesterday19:20
nibalizerya anteaya is out right now19:20
clarkbwhich did merge iirc19:20
*** jecarey has quit IRC19:20
*** nati_ueno has joined #openstack-meeting19:20
jeblairclarkb: and that change was to add it to testing, the modules env file, and remove the old code?19:21
fungiso i believe this meeting topic was in hopes of bringing some sane recommendations to the authors and approvers of those changes for better coordination19:21
clarkbjeblair: yup19:21
nibalizerfungi: exactly19:21
clarkbI suggseted that we try to communicate the coupling a bit better. changes should be proposed and WIP'd and very clearly specify the relationships between changes19:22
fungioptions proposed were to schedule the approvals of those, or to seek out infra-core shepherds to work with the authors proposing them and handle the final coordination19:22
jeblairso perhaps we should: wait until both changes are staged; link the system-config change to the project-config change with "Depends-On:"19:22
mmedvedewhat we have left off at yesterday is that there should be a core who would coordinate each individual split, correct?19:22
*** brich1 has quit IRC19:23
fungiin my opinion, i think making it clear in the commit messages that they depend on one another and core reviewers making sure to pay attention to commit messages should help most of this19:23
clarkbagreed. I don't think we need a specific core to coordinate around each of these changes19:23
nibalizerhow does that deal with lag?19:23
fungibut -2 or wip is another potential safeguard (though it does mean the author needing to actively troll for reviews)19:24
nibalizerlag between the initial submodule spilt and the series of patching lags is the freeze period19:24
jeblairi think the thing getting a core on-board with it gives is is a commitment from someone to be around in a few hours to ensure #2 doesn't sit outstanding for too long19:24
jeblairor what nibalizer said :)19:24
*** sankarshan_away is now known as sankarshan19:24
nibalizerya19:24
jeblairhowever, i don't think it needs to be the same core...19:24
nibalizerwe could even do the other thing anteaya said19:24
*** nati_ueno has quit IRC19:24
*** pballand has joined #openstack-meeting19:25
nibalizerwhich is friday after project rename we do split outs for the week19:25
fungiright, so i don't know it has to be an assigned core reviewer the entire way through, just when it comes time to approve things together19:25
clarkbright whoever does approve one should approve the other19:25
jeblairso maybe it's a matter of whoever approves the first one, they at least make sure it's likely that they or someone else will be around for the second?19:25
fungiseems fair19:25
jeblairwant to try that for a bit?  and if we need more structure, maybe we do split-out friday? :)19:26
*** nkinder has left #openstack-meeting19:26
clarkbwfm19:26
nibalizerwfm19:27
fungiproposed agreement: when dependent puppet-module splits are completely ready to merge, a core reviewer will commit to approving them in the appropriate order or coordinate with another reviewer to take over19:27
jeblairfungi: wfm; i'm going to add a second item19:27
fungioh, i had a second one too, but go ahead19:27
jeblairproposed agreement: system-config module removals should include Depends-On: in commit message referencing corresponding project-config module adds19:28
jeblairanyone disagree with fungi's statement?19:28
fungiheh, that was essentially my second agreement item ;)19:28
wenlockseems like a good plan, its what we've been doing too btw19:29
krtaylorshould commit message include the core working it?19:29
jeblairkrtaylor: no, i don't think we want that kind of fixed structure19:29
nibalizerworks!19:29
wenlockthe commit message should include a link to the other commit thats dependent IMO19:29
fungii think the point of these is to serve as a reminder that we should communicate, pay attention, and stick around if we approve part of something to do the rest19:29
jeblairfungi: yep19:29
asselinasselin's here now19:30
jeblairwenlock: should we add a third item: "project-config module add commit messages should link to system-config module removals with "Needed-By:" in commit message" ?19:30
fungii hear a resounding tacit approval19:30
jeblair#agreed when dependent puppet-module splits are completely ready to merge, a core reviewer will commit to approving them in the appropriate order or coordinate with another reviewer to take over19:30
jeblair#agreed system-config module removals should include Depends-On: in commit message referencing corresponding project-config module adds19:31
wenlockjeblair +119:31
mmedvedeSo both related patches should have Depends-On, or the project-config one should have something else, e.g. reminder that merging it would imply a need to merge the second one19:31
* fungi is good with all three19:31
jeblairthat's a little extra work on the commit side (it will require a git commit --amend in one of the repos)19:31
*** gyee has quit IRC19:31
jeblairor, i guess, clicking that little icon in gerrit :)19:31
fungior ctrl-d in gertty19:32
*** SridharRamaswamy has quit IRC19:32
jeblair#agreed project-config module add commit messages should link to system-config module removals with "Needed-By:" in commit message19:32
SergeyLukjanov+119:33
jeblair#link review these module splits: https://review.openstack.org/#/q/branch:master+topic:module-split,n,z19:33
fungiand i think if those are in there, wip/-2 aren't really needed to keep sanity. core reviewers caught ignoring commit messages will be summarily flogged with a fish19:33
jeblairfungi: a wet fish?19:33
fungii was thinking perhaps a smoked mackeral19:33
krtaylorbetter than a wet cat19:33
fungimackerel19:33
jeblairmordred is always very specific about the moisture content of his felines19:34
clarkbkrtaylor: mordred can get the wet cats19:34
krtaylorlol19:34
jeblair#topic Priority Efforts: Nodepool DIB19:34
*** openstack changes topic to "Priority Efforts: Nodepool DIB (Meeting topic: infra)"19:34
jeblairanything we should be doing on this?19:34
jeblairi'm starting to think this needs an owner19:35
*** cjellick has joined #openstack-meeting19:35
*** bobt has quit IRC19:35
*** cjellick has quit IRC19:35
fungiwhere did we get to last with it?19:36
jeblairit seems like it's been round-robining amongst mordred, clarkb, and yolanda19:36
*** amakarov has joined #openstack-meeting19:36
fungiwe reverted the centos7 dib change because we need newer tar right?19:36
*** cjellick has joined #openstack-meeting19:36
jeblairoh19:36
jeblairfrom last meeting:19:36
clarkbwe need to upgrade nodepool.o.o to trusty, fix nodepool's label can only build one type of image issue, and then kill whatever new things we discover19:36
ianwyes, clarkb is looking at upgrading nodepool host19:36
fungiso next step was going to be rebuilding the nodepool server on trusty i think?>19:36
jeblair19:17:16 <clarkb> the dib mutliple outputs change merged \o/19:36
jeblair19:17:23 <clarkb> shoudl release tomorrow if dib sticks to their schedule19:36
clarkbfungi: yup, and I think we have everything we need to do that now19:36
*** amakarov has left #openstack-meeting19:37
clarkbdib released, I tested the TMPDIR override locally19:37
jeblairclarkb: i have a gap in my knowledge -- why upgrade to trusty?19:37
fungi0.1.35 tagged 5 days ago19:37
ianwi also have an issue with image labels that i will look at (been saying that for a few days)19:37
ianwjeblair: newer tar that supports xattr for building centos images19:37
clarkbjeblair: centos7 images ship a qcow2 with extended fs attributes19:37
clarkbjeblair: for whatever reason dib converts that image to a tar19:37
jeblairah ok19:38
clarkbthen later untars that into the dir it will chroot into19:38
clarkb(I still think dib should just mount the image and chroot over that but I can't get anyone to tell me why that is a bad idea)19:38
jeblairwe need to review this change too19:38
jeblair#link https://review.openstack.org/#/c/126747/19:38
fungiand precise's tar is too old tu support extended attribs19:38
clarkbI can rebase that change today19:38
clarkband I also wrote https://review.openstack.org/#/c/130878/19:39
clarkbjeblair: if you look at https://review.openstack.org/#/c/130878/ that might be helpful. I got the test passing but it isn't doing what I wanted so it is WIPed19:39
*** Rajini_Ram has left #openstack-meeting19:39
jeblair#link wip nodepool test change https://review.openstack.org/#/c/130878/19:40
clarkboh I think I may see a problem there19:40
clarkbso maybe I just needed to do something else for a day or two :)19:40
jeblairclarkb: how do you want to handle the nodepool trusty upgrade?19:40
*** Tross has quit IRC19:40
clarkbits a bit tricky19:41
clarkbthe lazy in my wants to just spin up a new node, swap DNS then cleanup old slaves and images via the alien listing19:41
clarkbbut I think alien listing only works for slaves not images?19:41
*** e0ne has quit IRC19:42
jeblairclarkb: there's an 'alien-image-list'19:42
fungii think we had determined that they can run in parallel for a bit if demand is low (so that we don't overrun quotas, or we cut max-servers on them for the duration), then delete alien nodes after the old one is stopped19:42
clarkboh perfect than ya I think we just sort of do it without a db migratin and clean up aliens19:42
clarkbfungi: ya19:42
jeblairclarkb: zuul gearman will firewall the new server19:43
clarkbya so the dns update is important19:43
jeblairclarkb: you could ignore that and just let it supply min-ready for a while to make sure it's working19:43
clarkbit will basically be our cutover19:43
fungithat seems pretty safe then19:43
*** cdub has quit IRC19:43
*** marcoemorais has joined #openstack-meeting19:43
jeblairclarkb: more or less, yeah.  it should be that whichever has iptables access will do the bulk of the work19:43
jeblairthe other should only do min-ready19:44
jeblair(and replacements thereof when nodes are used)19:44
clarkbshould I possibly just go ahead and spin up the replacement this afternoon?19:44
clarkband we can let it build images and make min-ready nodes?19:44
jeblairclarkb: oh no!  we'll reset the node id counter :)19:44
clarkbactually that may not be entirely safe19:44
clarkbbecause those nodes will end up in jenkins but we won't get the node used events19:44
clarkb(maybe that is ok, the node will still be single use)19:45
jeblairclarkb: they come from zmq... does zmq have a firewall rule too?19:45
clarkbya19:45
clarkbon the jenkins side19:45
fungioh, hrm, yeah that might get messy19:45
clarkbI think in that case we will have "ready" nodes that have been used19:45
jeblairclarkb: then if you want to run both in parallel, we probably need to manually open the firewalls19:45
clarkbbut jenkins will only use them once19:45
clarkbso it should still be safe19:45
jeblairclarkb: yeah, but they won't ever be deleted19:45
clarkbthey will after 8 hours right?19:46
jeblairclarkb: nope, ready sticks around for a while19:46
jeblairforever, i think?19:46
*** simon-AS559 has joined #openstack-meeting19:46
clarkbgotcha19:46
clarkbdo we want to try doing this before the summit? I will also be afk week after summit19:47
jeblairclarkb: so i think either manually add iptables rules for the new server, or shut it all down and do it on a saturday.  :)19:47
clarkbI like the idea of shutting it all down simply because there is so much other stuff going on19:47
*** simon-AS559 has quit IRC19:47
jeblairmy last pre-summit day is tomorrow19:47
*** simon-AS559 has joined #openstack-meeting19:48
fungii'll actually be on my way to paris tomorrow and the day after19:48
clarkbfungi's too iirc19:48
clarkbya so lets post summit this and do it right?19:48
fungileaving for the airport tomorrow morning19:48
jeblairclarkb: sounds like a plan19:48
fungii agree19:48
jeblair#agreed upgrade nodepool to trusty after summit19:48
*** julim has quit IRC19:48
jeblair#topic Priority Efforts: Jobs on trusty19:49
*** openstack changes topic to "Priority Efforts: Jobs on trusty (Meeting topic: infra)"19:49
ianwso can we organise a restart to at least get hp centos7 jobs going?19:49
ianwthey're currently failing on login19:49
jeblairianw: shouldn't be a problem19:49
jeblair#link https://etherpad.openstack.org/p/py34-transition19:49
*** simon-AS5591 has quit IRC19:50
fungiyeah, inching closer19:50
fungiheat-translator fixed their issues, python-heatclient has a working change series up19:50
*** mwagner_lap has quit IRC19:50
fungipython-glanceclient is still stagnant19:50
jeblairfungi: did you bring that up at the project meeting?19:51
fungiand no new word on the two outstanding ubuntu bugs we need an sru to fix. hopefully ubuntuites are over their release hangovers now19:51
fungijeblair: i did not bring it up at the last project meeting, no, but now that it's been sitting for a week, probably a good idea19:51
jeblairfungi: cool (if anyone shows up for it this week ;)19:52
fungi#link https://launchpad.net/bugs/138258219:52
uvirtbotLaunchpad bug 1382582 in python-glanceclient "untestable in Python 3.4" [Medium,Confirmed]19:52
fungii guess that's been 11 days19:52
fungianyway, nothing else new on this front for now19:52
jeblair#topic  puppet-apache19:53
*** openstack changes topic to "puppet-apache (Meeting topic: infra)"19:53
jeblairianw: i think this is yours?19:53
jeblair#link https://review.openstack.org/#/c/129496/19:53
ianwyes, i'm happy to do this as an exercise in puppet19:53
ianwthere has been disagreement over the name19:54
ianwpossibly disagreement over forking puppet-apache, but AFAICS we're pretty stuck if we don't19:54
fungii thought the primary proposal was to fork puppet-apache simply by renaming it, and then work to incrementally migrate19:55
ianwyes, that is it19:55
clarkbfungi: what does incrementally migrate mean?19:55
clarkbmigrate to it or away from it?19:55
ianwalthough if we want to migrate remains an open question19:55
nibalizeri want to fork the apache mod19:56
fungiclarkb: switch modules from the fork to latest upstream bit by bit19:56
jeblairclarkb: one .erb at a time; migrate from 0.0.4 (or our fork of it) to upstream19:56
clarkbfungi: see I am almost a -2 on doing that :)19:56
jeblairnibalizer: you want to fork it and stay on the fork?19:56
*** padkrish has quit IRC19:56
*** gholler has quit IRC19:56
hogepodgepuppet-apache is a pain point for PL from what I understand.19:56
clarkbit will make our apache vhosts much harder to reconsume by not puppet19:56
nibalizerjeblair: kindof19:56
clarkbas we will essentially model everything in more native puppet types19:56
nibalizercertainly i think that is a thing we can get consensus on19:56
*** otherwiseguy has joined #openstack-meeting19:56
nibalizersince clarkb loves his 0.0.4 apache mod19:56
clarkbwhich apparently makes puppet happy but files are files and should be treated as such imo19:56
nibalizerand honestly the design there, which is to weakly model apache, isn't bad19:57
nibalizerso we could keep using apache 0.0.4 on our fork, then we and our downstreams have the option to bring in a newer apache if we want19:57
nibalizerbut at least we have the option19:58
nibalizerand if we want to set up a service that already had a puppet module , we wouldn't be boxed out of it19:58
jeblairdoes upstream have the capability to do things that we do in our vhosts?  eg, mod_rewrite certain urls, etc?19:58
nibalizerif you remember i had to remove the apache dependency in the puppetboard module19:58
fungiwell, if it's proposed as a permanent fork and not a temporary stepping-stone, i take it there's no hope of getting templated vhost support readded to latest apache module?19:58
jeblairi think doing so would end up with essentially a second configuration language for apache :/19:59
nibalizerim not sure what the extent of the capabilities of the new apache mod it19:59
nibalizeris*19:59
jeblairi expect we may talk about this over some beer19:59
nibalizerbut yea, the problem with the upstream apache module is you have to learn two things19:59
nibalizersince the puppet mod exposes apache configs into the puppet language19:59
nibalizerforking is nice because it says loudly that we do not expect to upgrade to latest apache20:00
nibalizerand if latest apache ends up in -infra for some ancillary service, im ok with that20:00
fungiyeah, we're out of time now anyway20:00
jeblairin all cases, https://review.openstack.org/#/c/129496/ seems to support any of the choices before us while getting us out of the dead-end of 0.0.4.20:00
jeblairso is certainly worth our review20:00
jeblairianw: thanks!20:00
jeblairand thanks everyone else; i hope to see you next week!20:00
jeblair#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Oct 28 20:00:49 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-10-28-19.01.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-10-28-19.01.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-10-28-19.01.log.html20:00
*** wenlock has left #openstack-meeting20:00
jeblairttx: i took my minute back from last week20:01
mikalHeh20:01
*** samcdona has joined #openstack-meeting20:01
ttxhah20:01
*** emagana_ has quit IRC20:01
*** markwash__ has joined #openstack-meeting20:01
ttxAnyone here for the TC meeting ?20:01
mikalYep20:01
dhellmanno/20:01
sdagueo/20:01
russellbo/20:02
jeblairo/20:02
*** emagana has joined #openstack-meeting20:02
ttxone more, one more20:02
ttxjgriffith, annegentle, mordred, devananda, vishy, markmcclain, jaypipes : around ?20:02
*** zns has joined #openstack-meeting20:02
jaypipeso/20:02
ttxhere we go20:03
mikalAnne had a doctor's appointment20:03
ttx#startmeeting tc20:03
openstackMeeting started Tue Oct 28 20:03:06 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:03
*** openstack changes topic to " (Meeting topic: tc)"20:03
openstackThe meeting name has been set to 'tc'20:03
ttxOur agenda for today:20:03
ttx#link https://wiki.openstack.org/wiki/Governance/TechnicalCommittee20:03
ttx#topic Board/TC joint meeting agenda20:03
*** openstack changes topic to "Board/TC joint meeting agenda (Meeting topic: tc)"20:03
*** baoli has joined #openstack-meeting20:03
*** jecarey has joined #openstack-meeting20:03
ttxOur first item is the agenda for the Board/TC joint meeting at 2:30pm on Sunday20:03
vishyo/20:03
ttxThe agenda proposed by the board is:20:03
ttx- Introductions20:04
ttx- Followup from last joint meeting (travel support program & code review backlog)20:04
ttx- The need for project structure reform (Ring 0 and the big tent approach)20:04
ttx- Tempest and it's use to drive interoperability and DefCore20:04
ttx- mid cycle meetups - is there a way to reduce travel strain?20:04
ttxI called for topics at http://lists.openstack.org/pipermail/openstack-tc/2014-October/000847.html20:04
ttxdhellmann wondered if we should put the CLA question on the meeting agenda20:04
ttxjaypipes suggested we discuss how the process by which we check for name/copyright issues for new projects can be streamlined20:04
mikalI think its more important than some of the other things listed there20:04
mikalThe CLA that is20:05
*** zns has quit IRC20:05
ttxAfter a few checks I'm not sure the legal namechecks one is relevant to the board, since this is currently handled by Foundation staff, so it may be better to talk to them about it first20:05
dhellmannI'd like an update on the CLA, but that doesn't have to happen in person.20:05
ttxwe can discuss it in a TC meeting directly with them20:05
sdagueyeh, the CLA seems like a thing that we need the board to take an action on, and it's been 7 or 8 months since this conversation started20:05
jaypipesdhellmann: ++20:05
jeblairsince we passed a resolution about the cla, we should probably put it on the agenda to continue to indicate we are interested in it, even if we do so in a way structured to avoid having it take the whole meeting :)20:05
sdagueyeh20:06
dhellmannjeblair: ++20:06
ttxjeblair: we can place it as the last item20:06
ttxso that it's mentioned but doesn't take the whole time20:06
sdaguemostly, I think bringing it up will demonstrate seriousness that the TC thinks it's important20:06
jeblairttx: or timebox it20:06
ttxyes20:06
*** emagana has quit IRC20:06
mikalI am a bit confused by some of the other board items there to be honest20:06
ttxI proposed a discussion of how much OpenStack (in general) should embrace Containers/Docker, as well as an update on the proposed bylaws change20:06
ttxThoughts on what we should push forward ?20:06
jeblairsdague: yeah, and i think that's a point worth making since the board explicitly wondered whether that was the case (thus prompting the resolution)20:06
ttx(The meeting is only 3 hours so we might need to prioritize)20:07
mikalLike, do we really think mid cycle meetups is one of the biggest problems we face at the moment?20:07
russellbonly 320:07
sdaguettx: the containers thing seems odd to me for this forum.20:07
*** ayoung has quit IRC20:07
russellbsdague: that's how i felt, too20:07
sdagueit's good beer chat, but does it really need to be a TC / Board thing?20:07
ttxsdague: maybe not20:07
dhellmannmikal: who is complaining, the person doing the travel or the person paying?20:07
ttxI mean, I won't push it unless someone else at the TC wants it20:07
jaypipesI think it does, because it goes to the general direction that we wish OpenStack to drive towards.20:08
mikaldhellmann: I dunno, its just on the boards list up above20:08
*** freemanbrandon has quit IRC20:08
jaypipesand I'm not just talking about technical direction.20:08
*** thedodd has joined #openstack-meeting20:08
dhellmannmikal: yeah, this isn't the first time I've seen it come up20:08
ttxjaypipes: yes, that was my idea20:08
ttxjaypipes: checking for general alignment on where we should go20:08
russellbi don't mind the business side input on direction20:08
jaypipescontainers bring with them a paradigm shift that matters more than technology. it shapes the way app developers visualize and work with the cloud.20:08
russellbyeah, that seems sensible20:08
*** markmcclain has joined #openstack-meeting20:09
jaypipeseverybody run.. markmcclain is here.20:09
russellbrun ... up to markmcclain and say hi!20:09
ttxjaypipes: are you fine with tabling the legal namechecks discussion to a future TC meeting with Foundation staff ? The board is not really involved with those20:09
*** AJaeger has left #openstack-meeting20:10
jaypipesttx: isn't Mark Radcliffe involved in those discussions? I remember Mark being at the last Board meeitng...20:10
ttxjaypipes: no, the lawyer doing those checks is not Radcliffe. I fear we won't get clarification, but more confusion20:10
jaypipesboard/TC meeting that is.20:10
*** markmcclain1 has joined #openstack-meeting20:10
markmcclain1jaypipes: haha20:10
jaypipesttx: ok, no problem. i don't want more confusion.20:10
*** freemanbrandon has joined #openstack-meeting20:11
*** ajo_ has joined #openstack-meeting20:11
ttxso, I'll ask for CLA timeboxed20:11
*** emagana has joined #openstack-meeting20:11
ttxMaybe a temperature check on the Docker world20:11
ttxanything else ?20:12
russellbmay need to timebox docker too20:12
dhellmann++20:12
ttxack20:12
*** carl_baldwin has quit IRC20:12
*** Haneef has quit IRC20:12
mikalttx: I think we should drop the mid-cycle thing, or at least move it later in the list20:12
mikalIt just doens't seem that important to me20:12
ttxmikal: I'll suggest that. It's not on my part of the agenda :)20:12
*** markmcclain has quit IRC20:12
*** _nadya_ has joined #openstack-meeting20:13
mikalttx: ok20:13
ttxNote that we can probably adjust the agenda in person when the meeting starts if we havbe a brand-new idea20:13
sdaguettx: was that board added?20:13
mikalDo we need daa for the code review backlog thing?20:13
mikaldata even20:13
ttxsdague: yes20:13
sdaguettx: ok20:13
ttxmikal: it wouldn't hurt20:13
mikalIts just a silly item20:13
*** markmcclain has joined #openstack-meeting20:13
jeblairi do see this summit as an experiment in how we can reduce the need for midcycles; i'm not sure we're ready to discuss it again until after this summit20:13
russellbsdague: rob h. brought it up at a recent board meeting20:13
russellbi'm not sure who raised it to him20:13
ttxat least from Nova / Neutron who had the largest backlog20:13
russellbjeblair: ++20:13
*** emagana_ has joined #openstack-meeting20:14
mikalIts also just penny pinching20:14
mikalTravel is a tiny fraction of salary spend20:14
sdaguejeblair: yeh, agreed, so maybe just make sure the time box is small on it20:14
mikalSure, we should be frugal20:14
russellbmikal: it's more than the $20:14
mikalBut if its efficient, we should do it20:14
russellbbut let's not get into it here20:14
*** emagana has quit IRC20:14
ttxmikal: being all relocated in the same office would be efficient, but we don't do it either20:14
*** MaxV has joined #openstack-meeting20:14
russellbright20:15
jeblairi second us not getting into it here :)20:15
jaypipesttx: one thing that might be interesting to get the BoD feedback on is the recent Neutron core team's proposal to do peer reviews for core committers.20:15
*** MaxV has quit IRC20:15
*** kebray has quit IRC20:15
* markmcclain resorts to using crappy irc client on his phone20:15
*** aysyd has quit IRC20:15
jaypipesttx: just to get their feedback, nothing more. I'm just curious what they think.20:15
mikaljaypipes: it would be interesting to get feedback on how that is working out before going too far with it20:15
*** markmcclain1 has quit IRC20:15
dhellmannmikal: +120:15
ttxyeah, I agree with mikal, let's let the experiment play out20:15
mikaljaypipes: as in, does Kyle feel is working? Was the feedback useful?20:16
ttxWe can give feedback on various experiments like specs now20:16
jaypipesmikal: they haven't started it yet :)20:16
russellbdefinitely not something i see we should push more broadly until we see how it works for them20:16
ttxas part of the "review backlog" discussion I guess20:16
jeblairwith a time constraint on the agenda, i don't think that's the kind of feedback we need from the board20:16
jaypipesmikal: I'm more interested in just the board members thoughts on it (same with the user committee's thoughts)20:16
russellbttx: sure20:16
sdagueyeh, I'm also a little concerned with just bringing up technical policy stuff to the board to get their view on if we don't have enough time to set context20:16
jaypipesmikal: but, fine, it's a beer topic :)20:16
* devananda pops in while waiting for boarding to start20:16
*** mrmartin has quit IRC20:17
*** MaxV has joined #openstack-meeting20:17
*** spzala has quit IRC20:17
ttxok, let's move on20:17
*** padkrish has joined #openstack-meeting20:17
ttxIf you sudenly have new ideas, push them to the thread. I'll compose an answer to Alan tomorrow morning20:17
*** juzuluag has joined #openstack-meeting20:17
ttx#topic Cross-project workshop final agenda20:17
*** openstack changes topic to "Cross-project workshop final agenda (Meeting topic: tc)"20:17
ttxrussellb, markmcclain: care to present the short list ?20:17
russellbsure, i'll cover this20:18
russellbso we have a couple of things to cover on this20:18
russellbfirst, review the list of sessions and the proposed schedule for them20:18
russellband if that looks good, we need to collect session leads and have the leads write up a session description that can be used on sched.org20:18
russellbproposed schedule:20:18
russellb#link http://kilodesignsummit.sched.org/overview/type/cross-project+workshops#.VE_2XHVGjUY20:18
dhellmannrussellb: I went through and did the math for the votes so far20:18
russellband then for collecting leads and descriptions:20:18
russellb#link https://etherpad.openstack.org/p/kilo-crossproject-summit-topics20:18
russellbdhellmann: yeah we did all that this morning20:19
russellband by we, i mean myself, markmcclain, and ttx20:19
dhellmannoh, I didn't see it in the etherpad20:19
russellbbased on action from last week20:19
*** otherwiseguy has quit IRC20:19
russellbnah, it was done in another spreadsheet20:19
dhellmannk20:19
russellbsorry20:19
mikalSo, that cells one confuses me20:19
dhellmannmeh, I was bored and curious20:19
russellbso first, does anyone see any obvious issues with the list of sessions or conflicts in schedule?20:19
russellbmikal: yeah, it made the cut *shrug*20:20
mikalrussellb: so, that makes three cells sessions a tthe summit20:20
russellbi think the cells one was to talk about how it impacts other projects20:20
mikalWhich seems like too many to me20:20
russellbnot just the nova part20:20
mikalEspecially for a feature nova might drop20:20
ttxmikal: the idea was to give some outlet for epople to discuss various ways to scale out in 40min. hopefully they will meet each other and stop inventing parallel ways ?20:20
sdaguemikal: well not if it means people actually work on it :)20:20
russellbanother part of that was merging in the huawei thing20:20
mikalOk, so rename it then20:21
russellbthere's a double session in the nova track too, i know20:21
*** SridharRamaswamy has joined #openstack-meeting20:21
ttxall the similar topics were merged, so I don't expect it to be a cells thing. More of a Cells vs. Cascade vs. Z20:21
mikalI'd be ok with it if it was called "scaling openstack" or something20:21
mikalBut its named "...with cells"20:21
mikalWhich is the bit that confuses me20:21
ttxyes, name should change20:21
russellbk20:21
*** freemanbrandon has quit IRC20:21
ttxI'd say "Scaling out: Cells, Cascading, Alliance, etc"20:22
mikalOr name none20:22
mikal"Proposals for scaling out OpenStack"20:22
russellbApproaches for Scaling Out ?20:22
ttxrussell++20:22
mikalYeah, that would do20:22
markmcclainRather name none20:22
*** markwash__ has quit IRC20:22
russellbk, sched updated20:23
ttxwell, sched caches, so ymmv20:23
mikalTa20:23
russellbi had john g. listed as leading that, since he proposed the cells one in the etherpad20:23
russellbhe's also listed on at least one other, though20:23
ttxwho can lead the API WG one ? jaypipes ?20:23
mikalrussellb: John would do a good job of it, depends if we think two is too many for one person20:23
ttxthough you already have the technbical debt one I suspect20:24
russellbmikal: ok, I can ask him what he thinks, will CC you20:24
jaypipesyes, though I'd love it if the part 1 and part 2 were separated... I really wanted to attend the functional tesst in projects session.20:24
mikalrussellb: works for me20:24
jaypipesheck i'd love to go to the common approach to ha one too :)20:25
*** pnavarro has joined #openstack-meeting20:25
russellbjaypipes: yeah, scheduling this stuff is fun.20:25
*** aepifanov has joined #openstack-meeting20:25
jaypipesrussellb: yeah, i know :)20:25
russellbif anyone has proposed leads for any of the stuff on the etherpad, fill it in20:25
*** sdake_ has quit IRC20:25
russellbsome may have it later in the etherpad and i just haven't gone back to find it yet20:25
jaypipesrussellb: suggestion... perhaps we could swap the api wg part 2 with the growth challenges part 1?20:26
jeblairi don't think the intent there is to actually have two parts, but rather combine them into one long session20:26
*** vivek-ebay has quit IRC20:26
jaypipesrussellb: and have a morning and afternoon session on those topics?20:26
russellbyeah, was thinking it was one long session20:26
jaypipesjeblair: yes, I know... but ... just offering an alternative.20:26
ttxyes, it's one long session20:26
jeblairi think breaking them up would disrupt the idea of being able to have longer-form sessions on some topics20:26
sdaguejeblair: ++20:26
ttx90min instead of 2x40min20:27
*** vivek-ebay has joined #openstack-meeting20:27
ttxI think it needs 90min in one block20:27
russellbwe could maybe move "moving testing ot projects" elsewhere20:27
russellbit's a bad conflict no matter where it moved to20:28
*** jecarey has quit IRC20:28
devanandaI'm wondering who else feels that the necesity of attending the cross project sessions pretty nearly trumps all the sessions and panels on Tuesday20:28
russellbdevananda: that's my general feeling, yes20:28
ttxrussellb: maybe swap it with the reaquirements session ?20:28
sdaguedevananda: yep20:28
jeblairdevananda: i feel that way for the whole summit, but yes :)20:28
devanandathankfully i don't have any speaking commits on tuesday20:28
*** nelsnelson has quit IRC20:28
devanandabut a bunch of panels that I really want to attend are on tuesday ...20:28
*** nelsnelson has joined #openstack-meeting20:29
russellbjaypipes: if we do the swap ttx suggests, it conflicts with the "scaling out" thing20:29
*** MaxV has quit IRC20:29
russellband docs20:29
russellbjaypipes: that better?20:29
jaypipesdevananda: unfortunately, I have to give a presentation at the conf side on tues...20:29
*** _nadya_ has quit IRC20:29
jaypipesand monday, and wednesday...20:29
russellbjaypipes: sucker20:29
russellb:-p20:29
ttxjaypipes: one would think you would know to avoid the CFP by now20:29
jaypipesrussellb: lookign...20:30
devananda16:40 gerrit third-party CI && growth challenges p1.20:30
russellbhonestly, it's a shame more people from dev community don't present because of the pressure we have to attend design summit stuff20:30
devanandaare there people who need to be in both of those?20:30
sdaguerussellb: well that was one of the reasons for the offset20:30
russellbsdague: true, speak on monday20:30
*** MaxV has joined #openstack-meeting20:30
*** MaxV has quit IRC20:30
fungigerrit third-party ci does in fact seem related to growth challenges20:30
jaypipesrussellb: yeah, unfortunately I'd love to be at the scaling out session :) it's ok, i'll just deal with it. I do every time anyway.. we all do. :)20:31
jaypipestry and catch a bit of each.20:31
sdaguejaypipes: ++20:31
*** vivek-ebay has quit IRC20:31
*** dkranz has quit IRC20:31
russellbdepends on what the 3rd party meetup is about20:31
jaypipesttx: I'm happy to lead the first part of the API WG, and maybe etoews will take up the latter part so I can catch some of the func testing session20:31
russellbbut yeah, definite overlap20:31
devanandanone of the other design things on tuesday stand out as single-person conflicts within the design track20:32
ttxfungi: unfortunately there is little ways to avoid that one.20:32
devananda*to me20:32
ttxfungi: We want that one at a moment where only one other workshop runs. That's either at the start or the end of the day20:32
fungifair enough, just agreeing with devananda's point20:33
russellbwho would lead "moving tests to projects" ?20:33
ttxI run that session and I also need to be at the Design Summit 10120:33
devanandafungi: ttx: could we move gerrit 3rd party one slot earlier?20:33
devanandarussellb: mtreinish or sdague?20:33
* annegentle lurks after appointment and catches up20:33
devanandathat seems related to tempest-lib IIUC20:33
ttxdevananda: then we have 3 parallel workshops at the same time as the beginning of the growth discussion20:34
ttxdevananda: what would you swap it with ?20:34
jaypipesrussellb, ttx: crap... no, that won't work. I'm giving my talk on tuesday at 11:15 :( so I would not be able to attend the API WG session.20:34
russellbjaypipes: :(20:34
russellbyeah, definitely hoped you could be at that one20:34
jaypipesrussellb: sorry: https://openstacksummitnovember2014paris.sched.org/event/0a602a57f19a73c9995dfb88f22a1538#.VE_90R8aekA20:34
ttxjaypipes: you can still ask to move to another time on the conf side20:34
fungidevananda: i think the only critical timing concern on third-party testing cross-project discussion was that it come before project-specific third-party testing sessions, but that will be the case regardless20:34
russellbttx: ++ :)20:34
annegentlejaypipes: I can help with API WG and ask Everett Toews if he's available.20:34
mtreinishdevananda: the functional testing one, I think dkranz put it in the list20:34
jaypipesttx: k, lemme see what I can do.20:34
ttxlike on Monday or Wednesday20:34
devanandatime for me to board a plane ...20:34
russellbdevananda: o/20:35
jaypipesannegentle: that would be swell. i can make the second half of the API WG session (or most of it at least)20:35
sdagueyeh, do we have existing session leaders for most of these? (defaulting to proposer I'd assume)20:35
ttxfungi: I think anteaya wants the 3rd-party CI discussion as a feedback session20:35
russellbsdague: trying to sort that out20:35
russellbetherpad is kind of a mess20:35
sdagueok20:36
annegentlejaypipes: okay, sounds good, what's the time again? for API WG?20:36
russellbmost of them don't have a proposer listed20:36
sdaguerussellb: oh, bummer20:36
ttxAnyway, I propose we push that schedule publicly and we see what conflicts people start to report20:36
russellbbasically i added a new section at the top of the pad to try to clarify it20:36
russellbstill missing a bunch20:36
ttxbecause I expect some PTLs to complain too20:36
jaypipesannegentle: 11:15am on Tues20:36
sdagueI'm pleading ignorance as this is second day back, so still getting up to speed on the schedule :)20:36
russellbsdague: wb!20:37
*** markmcclain1 has joined #openstack-meeting20:37
*** zns has joined #openstack-meeting20:37
*** markmcclain1 has quit IRC20:37
jaypipesindeed, wb sdague20:37
russellbso, should we sort out session leads async?  i can post to -dev list asking for volunteers ...20:37
russellbor we can try to burn through it now20:37
annegentleshoot I'm in the Design Summit 101 also with ttx20:37
jaypipesrussellb: I think that's the best bet.20:37
annegentleguess it's on Everett20:37
ttxannegentle: yay!20:37
sdagueyeh, ML might be good to flush out the original proposers20:37
russellbsdague: ++20:37
russellbttx: can you raise this at the next meeting, too?20:38
jaypipesrussellb: so did the scheduler/gantt proposed session get nixed? not enough interest? :(20:38
sdagueand if there are still gaps tomorrow this time, play a game of who's it20:38
ttxrussellb: sure20:38
russellbjaypipes: score of 020:38
*** eglynn has joined #openstack-meeting20:38
russellbjaypipes: lack of interest, and a few -1s ... mainly that for now, it's a nova concern20:38
*** johnpur has joined #openstack-meeting20:38
ttxI think Nova scheduled two sessions on that topic20:39
russellbget the split done ... too many people only want to talk about steps 12-18, and not the work that needs to get done first20:39
russellbIMO20:39
*** jecarey_ has joined #openstack-meeting20:39
sdaguerussellb: +100020:39
*** markmcclain1 has joined #openstack-meeting20:39
*** dkranz has joined #openstack-meeting20:39
annegentleonly steps 1-7 may be discussed :)20:40
ttxOK, let's move on -- russellb: post the selection to the ML and ask for leads ?20:40
jaypipesrussellb: k, understood (and I agree with you on that)20:40
russellbcool20:40
russellbttx: wfm20:40
jeblairafter that, any session without a lead gets mordred as the lead20:40
jaypipesrussellb: course, that doesn't mean I won't be inundated with NFV people asking me about it... but whatevs :)20:40
russellbjaypipes: ha, i feel your pain.20:40
ttx#topic Governance for the openstack-specs repo20:40
*** openstack changes topic to "Governance for the openstack-specs repo (Meeting topic: tc)"20:40
ttxA few weeks ago we allowed the creation of an openstack-specs repo for truly cross-project specs, and it was created as a TC-owned repository20:41
ttxThe question left is... how should we manage this repo ? who should get +1/+2... ?20:41
jeblairwell, everyone should get +1 i think :)20:41
russellbjeblair: +120:41
annegentlegreat starting point jeblair20:41
annegentle:)20:41
russellbI think starting with TC as the group with +2 seems sane20:41
russellband see how it goes20:41
jeblairmaybe even -1? :)20:41
sdagueyeh tc as -core group seems sane20:42
russellbnot that we have *ALL* the expertise, but can work toward consensus, take all the inputs, etc, just like other cross project issues20:42
sdagueand normal review criteria for everyone else20:42
jeblairshould we put specs on the agenda before final approval?20:42
jogothere is also the question of what it means for a spec to be approved there. Do all projects have to implement it now? etc.20:42
dhellmannyeah, we may also want a different approval policy for that repo20:43
ttxjogo: I guess it depends on the content of the spec20:43
mikalI like the idea of an in-meeting check point before approving20:43
jeblairlike "this spec is ready for approval, put it on the tc meeting agenda for a final call for tc review, and approve in more or less the normal tc way?"20:43
russellba doc on expectations around this sounds like a ncie idea20:43
russellbperhaps even a spec on specs!20:43
sdagueis that something we can have in the specs cross project session ?20:43
russellbsdague: ++20:43
*** baoli has quit IRC20:44
mtreinishwe try to do the meeting check in for qa specs, it's only moderately successful there...20:44
jaypipeswhy can't we handle it similarly to how we handle openstack/governance?20:44
*** markwash__ has joined #openstack-meeting20:44
*** kebray has joined #openstack-meeting20:44
dhellmannjaypipes: yeah, that's more or less how we do oslo specs20:44
annegentleone final vote?20:44
sdaguejaypipes: and have ttx approve it all?20:44
*** baoli has joined #openstack-meeting20:44
jaypipesand have ttx (or someone else?) be the only +2/+W'er, and have a policy of quorum or consensus that is enforced by ttx.20:44
dhellmannsdague: right20:44
ttxjaypipes: depends on how "similar" it is20:44
jaypipessdague: yeah.20:44
ttxsomeone else++20:44
jaypipesdoesn't have to be ttx of course.20:45
* jaypipes nominates annegentle 20:45
sdagueI kind of like the idea that cross project specs have the ability for any community member to +1/-1 feedback20:45
jaypipessdague: of course, that wouldn't change...20:45
annegentleheh20:45
sdaguewell it's not the way governance works20:45
jaypipessdague: ? sure it is.20:45
russellbnah20:45
sdaguenope20:45
dansmithnope20:45
ttxjaypipes: only TC members can +120:45
russellbonly TC can +1/-120:45
annegentleit has to get as least as many votes as the TC election :)20:46
ttxand I just tally the votes20:46
dansmithI was disappointed I couln't +1 things in governance20:46
jaypipesoh...20:46
jaypipeswell I be darned.20:46
dhellmannsdague: it's more like oslo-specs, where anyone can vote, cores can vote 2, and by agreement only I approve things20:46
jeblairanyone can leave a message of course20:46
russellbwe could revisit that idea i guess20:46
*** e0ne has joined #openstack-meeting20:46
russellbbut anyway, i like everyone having +1/-1 on the specs20:46
annegentleI think for cross project you're gonna need to gather more consensus20:46
jaypipeswell, sorry about that. I was misinformed.20:46
ttxjeblair: could we have TC members do +2 and I would tally +2 with Workflow+1 instead ?20:46
russellbin theory governance has the same cross project impact20:46
annegentleso everyone +1/-1 is a good thing20:46
ttxthat would allow "normal people" to +120:46
sdaguettx: yeh, that might be fine20:46
jeblairttx: -2 is a problem20:46
sdaguejeblair: is it?20:47
ttxsdague: I think we suggested that back then20:47
russellbanyone remember why we did that for governance?20:47
mikalI think we could all just agree that only ttx +A's20:47
jeblairmay i have the floor? :)20:47
* ttx passes the mike to jeblair20:47
russellbjeblair takes the meeting lock20:47
* markmcclain1 wonders why that is not a feature of meetbot20:47
jeblairpart of why governance is structured the way it is is due to limitations in a previous version of gerrit, and partially to make sure that the voting (since we _actually_ vote) is clear20:47
jeblairsince we have upgraded gerrit, we do have more options than before20:48
*** david-lyle has quit IRC20:48
vishyhot spec on spec action: http://cdn.vectorstock.com/i/composite/66,23/spectacles-vector-6623.jpg20:48
jeblairso if we would like to enable +/-1 for everyone while maintaining the ability to discern tc votes, i believe we can come up with a proposal for that20:48
annegentlevishy: SNORT20:48
*** asalkeld has joined #openstack-meeting20:48
jeblairit will still be something different than the process used for other repos, but i think we can work it out20:48
jeblairis that something the tc would like us to do?20:49
russellbnew column for TC votes or something?20:49
sdaguejeblair: so I think it's also OK to use normal core rev rules. TC members -1 things for 'needs more work' and -2 for 'hell no'20:49
ttxbeing able to record random +1/-1 sounds like a good thing, yes20:49
jeblairrussellb: that may be an option20:49
jeblairsdague: -2s block20:49
sdaguejeblair: yes20:49
jeblairsdague: no tc member gets a veto20:49
russellbi think so yes, i'd love to see a proposal for it20:49
sdaguefor specs?20:49
jeblairsdague: i believe governance is the repo under discussion?20:49
dhellmannyeah, I think in this case blocking is a feature20:49
ttxsdague: we are discussing governance now20:49
sdagueoh... sorry20:49
sdagueI missed a context switch20:50
*** scotm has quit IRC20:50
jaypipesjeblair: I'm certainly interested in a proposal to do that.20:50
*** markmcclain has quit IRC20:50
* dhellmann missed the context switch to20:50
fungi-1..+1 for peanut gallery, -1..+2 for tc members, 0..+1 workflow for tc chair?20:50
russellbyeah, tangent20:50
ttxwe can workl something out for governance, but that's pretty off-topic20:50
ttxfungi: something like that yes20:50
jeblairfungi: that still doesn't work20:50
sdagueyeh, governance repo discussion to tc list?20:50
jeblairsdague: please no20:51
*** scotm has joined #openstack-meeting20:51
fungimeh, right, tc -1 is different from peanut gallery -120:51
russellbbecause tc -1 is different than general -120:51
*** radez is now known as radez_g0n320:51
annegentleit's pretty relevant though to cross project and api wg repos20:51
*** vivek-ebay has joined #openstack-meeting20:51
jeblairwhat i would like to do is come back to the tc with a proposal that meets the requirements20:51
jeblairrather than designing something in this meeting20:51
ttxso.. back to openstack-specs20:51
ttxjeblair: can you propose something for that as well ?20:51
russellbwhat are the requirements for specs though20:51
markmcclain1jeblair: +120:52
dhellmannI'm happy with the way the governance repo works now, and I think we can manage the openstack-specs repo by consensus that only the appointed person approves20:52
russellbliek any other repo?20:52
russellband tc as -core ?20:52
jeblairyeah, i think i know the requirements for governance, but i don't know them for specs20:52
russellbi think ^^^ works for me for specs20:52
ttxworks for me too20:52
dhellmannrussellb: +120:52
sdaguerussellb: yeh, +120:52
jeblairthat gives tc members veto20:52
ttxmaybe with some rule that we want more than 2 approvers, but taht can be figured out as we go20:53
dhellmannjeblair: yes, that's what we want for specs20:53
ttxjeblair: sounds reasonable for specs20:53
jeblairsounds like a starting point i guess :)20:53
ttxso we don't really need a secretary to tally votes like for govrenance20:53
russellbyeah20:53
sdagueyep20:53
russellb(re: starting point)20:53
jeblairi do still think that final approval should happen after it hits the meeting agenda20:54
ttxjust do the usual core dance20:54
russellbjeblair: ++20:54
*** hashar has joined #openstack-meeting20:54
dhellmannjeblair: ++20:54
markmcclain1jeblair: ++20:54
*** carl_baldwin has joined #openstack-meeting20:54
russellbbut only 2 +2s before +W?20:54
russellbor more?20:54
annegentleseems like you need +2 from affected PTLs?20:54
russellbor just let people use good sense?20:54
dhellmannrussellb: I look for broad consensus on oslo-specs before I approve them20:54
jeblairannegentle: affected ptls may not have +220:54
annegentlebut that's gaterhing consensus20:54
dhellmannannegentle: yeah, I'd look for a +120:54
ttxmaybe +1s forom affected ptls20:54
*** markwash__ has quit IRC20:54
jeblairyeah20:54
annegentleokay that works too as long as they're aware, voting, we know there is consensus gathered20:55
ttxjeblair: you up for proposing a technical solution for both ?20:55
*** zns has quit IRC20:55
*** baoli has quit IRC20:55
sdagueor you just talk to people and be reasonable20:55
russellbsdague: that.20:55
sdaguewhich is typically what happens in the specs today20:55
dhellmannsdague: we could do with more of that20:55
jaypipessdague: be reasonable? what's wrong with you! :P20:56
jeblairttx: it sounds like we have what we need for specs; or do you want me to write the process doc?20:56
*** baoli has joined #openstack-meeting20:56
*** thingee has joined #openstack-meeting20:56
jeblairttx: and yes, i will make a proposal for governance20:56
russellbyeah, sounds like specs is just like everything else20:56
*** matrohon has joined #openstack-meeting20:56
*** markwash__ has joined #openstack-meeting20:56
ttx#action jeblair to propose some novel Gerrit rules solution for governance repo20:56
ttxjeblair: maybe write it up ?20:56
jeblairttx: can do20:56
russellbbut we could probably still use a general guidelines doc on cross project specs to clarify for people what kind of consensus we'll be looking for20:56
ttx(the openstack-specs rules)20:56
jeblairyep.  should i propose that to openstack-specs or governance?20:57
ttx#action jeblair to write up proposed Gerrit rules for openstack-specs repo20:57
ttxjeblair: openstack-specs I'd say20:57
russellbcool.20:57
annegentlejeblair: ttx: okay to also consider the api wg repo as well in your proposal? Seems more efficient20:57
ttxself-documentation20:57
dhellmannannegentle: I thought we said the wg would have +2 in that repo20:57
russellbapi wg repo deserves its own consideration20:57
russellbmaybe we can just cover that next week?20:57
ttxannegentle: api wg is a bit of another beast, I'd like them to self-organize first20:57
russellbttx: ++20:58
ttxno need to impose process externally20:58
ttxlet's see what they come up with20:58
ttxok, let's run through the other items in agenda20:58
ttx#topic Other governance changes20:58
*** openstack changes topic to "Other governance changes (Meeting topic: tc)"20:58
ttxI have two changes from mordred that are blocked, couldn't really get hold of him, but I'll soon corner him physically20:59
ttx* Remove support for vendor extensions from our code (https://review.openstack.org/122968)20:59
ttx* Add a docs environment to the testing interface (https://review.openstack.org/119875)20:59
ttx#topic Open discussion20:59
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:59
ttxAnything urgent to discuss, anyone ?20:59
russellblooking forward to seeing you all in person soon!20:59
ttxQuestion about upcoming BoD/TC meeting, Design Summit etv ?20:59
dhellmannsame!20:59
ttxetc20:59
sdagueyep, definitely20:59
markmcclain1yeah.. will be good to get in same room21:00
russellbesp for the big governance changes discussion ...21:00
ttxaround the same dinner table too21:00
russellbreally need some real-time chat time on that21:00
*** spzala has joined #openstack-meeting21:00
markmcclain1food for thought… but don't want to discuss now: should we be considering an in person TC meetup 2015 Q1?21:00
ttxok then, safe travels21:00
jeblairsee you in paris!21:00
annegentlewhere are the pods ttx?21:00
dhellmannrussellb: maybe we should plan to have lunch together once or twice so we can cover that?21:00
dhellmann(everyone, not just the 2 of us :-)21:00
ttxannegentle: in the Design Summit space (Le Meridien)21:00
mikalmarkmcclain1: I like the idea21:00
annegentleokay thanks21:00
* jaypipes will come to TC dinner dressed in a giant tent.21:00
ttx#endmeeting21:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:01
openstackMeeting ended Tue Oct 28 21:01:00 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-10-28-20.03.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-10-28-20.03.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-10-28-20.03.log.html21:01
mesteryjaypipes: lol21:01
dhellmannttx: is there a project meeting today?21:01
russellbi'm coming as a Tipi21:01
* marun is disappointed that nova/neutron integration didn't make the cut for a cross-project summit session :(21:01
markmcclain1jaypipes: making halloween a full weekend?21:01
ttxdhellmann: quick one21:01
jeblairttx: do you have a handy link to venue maps?21:01
jaypipesmarkmcclain1: you know it.21:01
russellbmarun: it wasn't even on the list IIRC21:01
russellbnobody proposed it.21:01
dhellmannttx: ok, I need to drop off soon21:01
ttxjeblair: no handy link21:01
mikalI need to drop off now21:01
mikalLaters21:01
*** marcoemorais has quit IRC21:01
*** marcoemorais1 has joined #openstack-meeting21:01
ttxdhellmann, morganfainberg, notmyname, eglynn, nikhil_k, thingee, asalkeld, david-lyle, mestery, SlickNik, SergeyLukjanov: around ?21:01
SergeyLukjanovo/21:01
dhellmanno/21:01
mesteryo/21:01
* marun looks pointedly at markmcclain1, who made noises about proposing such a session21:01
asalkeldo/21:01
nikhil_ko/21:01
notmynamehere21:01
eglynnhola21:01
ttx#startmeeting project21:02
openstackMeeting started Tue Oct 28 21:02:01 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:02
*** openstack changes topic to " (Meeting topic: project)"21:02
openstackThe meeting name has been set to 'project'21:02
dhellmannmarun: if it was only 2 projects, it wouldn't have made the list anyway21:02
ttxOur agenda for today:21:02
ttx#link http://wiki.openstack.org/Meetings/ProjectMeeting21:02
*** Tross has joined #openstack-meeting21:02
ttx#topic Final Design Summit scheduling21:02
*** openstack changes topic to "Final Design Summit scheduling (Meeting topic: project)"21:02
russellbdhellmann: likely, yes ... though those 2 projects usually have packed agendas and a hard time getting together21:02
ttxWe seem to have everything on the agenda at this point, except...21:02
russellbso would have been worth considering ...21:02
* ttx refreshes21:02
*** hashar has quit IRC21:02
dhellmannrussellb: we should call it "all projects" instead of "cross projects"21:02
SergeyLukjanovttx, I've pushed sahara sessions21:02
russellbdhellmann: heh21:02
ttxexcept TripleO21:03
russellbdhellmann: cross project, with preference for all project21:03
russellbdoesn't have a good ring to it21:03
* russellb gets out of ttx's meeting ...21:03
ttxNote that I changed a few titles so that it's clearer which project each session belongs to21:03
ttxsince they won't appear in cheerful colors in the mobile app21:03
dhellmannttx: I have to drop off, but I'll look at the logs tonight in case there's something you need from me21:04
*** sdake_ has joined #openstack-meeting21:04
ttxdhellmann: sure!21:04
jeblairttx: thank you for that21:04
ttxOne session is unassigned in QA21:04
SergeyLukjanovttx, yeah, it's a good idea, last time there were some very unclear titles (one of them were sahara session :) )21:04
ttxwe just published the tentative cross-project workshops21:04
*** david-lyle has joined #openstack-meeting21:04
jeblairttx: mtreinish and i have a plan for that21:04
* asalkeld goes to look at cross projects21:04
ttxmtreinish: do you plan to make use of that unassigned session ?21:05
ttxjeblair: oh21:05
david-lyleo/21:05
notmynamettx: thanks for fixing the titles21:05
jeblairttx: iiuc, we have put a joint infra/qa topic on formalizing gating strategies in there21:05
ttxnotmyname: feel free to refix them if they look bad21:05
russellbcross project stuff: http://kilodesignsummit.sched.org/overview/type/cross-project+workshops#.VFAFFXVGjUa21:05
notmynamettx: looks fine from my perspective21:05
eglynnhmmm, the cross-project session on notifications made the cut21:05
eglynnhttp://kilodesignsummit.sched.org/event/0b6e7e23da3d4fdcdc5cec0777b92c6a#.VFAE-opziVo21:05
jeblairttx: it was contingent on functional testing being approved as a cross project (which it was), so i believe it's spoken for and mtreinish should be able to push the updated schedule21:05
ttxeveryone: note that if you want to edit scheduled sessions in my crappy UI, you'll have to unschedule slots before you can edit them21:06
*** marun has quit IRC21:06
ttxthen schedule them again and push to sched21:06
*** marun has joined #openstack-meeting21:06
russellbeglynn: and still need a session lead for that btw21:06
*** curtis_p has joined #openstack-meeting21:06
*** niclem has joined #openstack-meeting21:06
mtreinishttx: yeah I'm going to update the schedule nowish21:06
* eglynn wonders if we need the ceilometer-specific session on notifications-as-a-contract also21:06
russellbeglynn: would you be interested in leading it?21:06
eglynnrussellb: jd__ is leading the ceilo session21:06
russellbah OK21:06
thingeettx: I have verified firefox works for me, but not the latest chrome. re: my email earlier about pushing the sched21:06
asalkeldrussellb, who leads these?21:06
russellbasalkeld: still trying to figure that out21:07
ttxWe need leads for all the cross-project sessions, to make sure they are going somewhere21:07
russellbmost sessions didn't have obvious proposers listed21:07
*** markwash__ has quit IRC21:07
asalkeldI fleshed 2 out21:07
russellbasalkeld: i have you down for the upgrades one, as i think you proposed it?21:07
ttxrussellb: etherpad link for that ?21:07
*** zns has joined #openstack-meeting21:07
asalkeldha and upgrades21:07
russellbhttps://etherpad.openstack.org/p/kilo-crossproject-summit-topics21:07
eglynnrussellb: I'll chat with jd__ about it tmrw, we could decide to "repurpose" the ceilo session21:07
asalkeldbut big topics21:07
asalkeldhappy for others to get involved21:07
russellbasalkeld: i know dansmith is willing to help on the upgrades one, to give info on what nova has been doing, and some related things coming21:07
asalkeldgreat21:07
*** niclem has quit IRC21:08
ttxSo, please check the proposed schedule for conflicts, maybe we can move things around to facilitate your life21:08
asalkeldit's a shame beekhof is not coming to summit21:08
russellbasalkeld: indeed, i've never met him in person21:08
*** niclem has joined #openstack-meeting21:08
jeblairttx: if mtreinish doesn't update the qa slot, here's text that could go into it: http://paste.openstack.org/show/126134/21:08
ttxAlthough the cross-project workshops current schedule is alkready the result of a lot of tweaks and we have trouble changing it at this point without breaking someone21:09
mtreinishjeblair: I just pushed the update21:09
ttxjeblair: mtreinish said he would update nowish21:09
eglynnbreaking someone == causing conflicts?21:09
ttxeglynn: yes21:09
*** niclem has quit IRC21:09
eglynncool, got it21:09
asalkeldrussellb / ttx, will there be some kind of ml thread to figure out who is leading the cross project sessions21:09
jeblairttx, mtreinish: cool, thanks.  sorry i missed that, it wasn't in yellow.  :)21:09
*** shohel02 has quit IRC21:10
ttxasalkeld: we have an etherpad, and russellb will push a thread about it21:10
*** niclem has joined #openstack-meeting21:10
ttx#link https://etherpad.openstack.org/p/kilo-crossproject-summit-topics21:10
asalkeldcool, thx21:10
russellbasalkeld: yes, starting a thread now-ish21:10
russellbfor the future, should really have some more formatting around idea proposals21:10
russellbincluding a lead for every proposal21:10
russellbthis was a mess21:11
*** yjiang5 has quit IRC21:11
asalkeldyip21:11
russellbdownside of using an etherpad instead of the system from before21:11
asalkeldso I happy to help with both upgrades and ha21:11
ttxrussellb: yes, the etherpad-driven thing works well until you reach critical mass of proposers21:11
russellbasalkeld: anyone else that should be listed for HA?21:11
eglynnalso, how about including the PTL group in the session voting?21:11
eglynn(as opposed to just the TC)21:11
asalkeldrussellb, you could ask for interested parties21:12
russellbOK21:12
*** markwash__ has joined #openstack-meeting21:12
asalkeldlots of RHT and miratis folk are interested in HA21:12
* russellb nods21:12
ttxeglynn: yes, I agree21:12
ttxno need to limit voting21:12
russellbeglynn: +121:13
*** sdake_ has quit IRC21:13
russellbasalkeld: fabio will be there21:13
asalkeldnice21:13
eglynnyeah just gonna suggest fabio also21:13
jeblairi don't think there's a need to limit feedback.  i do think there's a need to limit voting.  we are asking the tc to exercise some judgement and discretion here.21:13
*** markstur has quit IRC21:14
eglynnjeblair: well, I think the PTLs have plenty of judgement and discretion21:14
ttxjeblair: the selection is not necessarily the highest votes, depends on what gets selected and what can be merged, too21:14
ttxso we exercise discretion when we make the final selection, not necessarily when we vote :)21:15
jeblairttx: you said "no need to limit voting" i was responding to 'voting' :)21:15
jeblairttx: that works :)21:15
jeblairand is in fact what we did in infra21:15
jeblairi also don't believe ptls or anyone was excluded this time21:16
jeblairi believe i saw quite a bit of feedback on the etherpad21:16
*** nellysmitt has quit IRC21:16
ttxthe preamble at the top discouraged non-TC-members from voting though21:16
ttxwhich is I think what eglynn is referring to21:16
ttxheck, we should use Gerrit for this21:17
ttx:)21:17
eglynnyeah I assumed it was a TC-only deal on the voting, apols if I misread that21:17
ttxanyway, that's a tangent again21:17
jeblairi have this natural inclination not to call something "voting" if the tally of results doesn't count.  ttx, i think we're getting hung up on terminology :)21:18
ttxany other question/ urgent action to take wrt: Design Summit ?21:18
ttxjeblair: that's a thing we do indeed21:18
mtreinishttx: is it a good time to bring up scheduling conflicts?21:18
ttxmtreinish: as good as any21:18
eglynnttx: when does the schedule need to be absolute finalized?21:19
SergeyLukjanovttx, do we have a venue map? (what's the distance between design summit sessions and summit itself)21:19
ttxit's literally across the street21:19
*** neelashah has joined #openstack-meeting21:19
ttxI don't have a handy map21:19
mtreinishwell I haven't seen mikal, but there is overlap with nova's functional testing and the qa track21:19
jeblairi could only find one for the conference21:19
SergeyLukjanovttx, ok, across the street is enough to know, thx21:19
jeblairmtreinish: mikal said he had to drop21:20
ttxeglynn: in theory, today, but if we push changes they should be picked up until the end of the week21:20
mtreinishjeblair: ah, ok21:20
ttxthe mobile app does async updates with sched21:20
ttxso the sooner we are final the less confusion we generate21:20
eglynncool21:20
*** harlowja is now known as harlowja_away21:21
* ttx looks for a venue map21:21
*** pnavarro has quit IRC21:21
jeblairhttps://www.openstack.org/summit/openstack-paris-summit-2014/venue-maps/ seems to be conference only21:21
*** mrunge has quit IRC21:21
SergeyLukjanovttx, jeblair, I'll join infra/qa/release meetup only afternoon, so, I hope not to miss something important21:21
*** enikanorov__ has joined #openstack-meeting21:21
jeblairSergeyLukjanov: good to know, thanks21:21
ttxSergeyLukjanov: ok21:22
*** mtanino has quit IRC21:22
SergeyLukjanov(due to the sahara meetup before afternoon)21:22
curtis_ppwd21:24
asalkeld /tmp21:24
asalkeld:)21:24
ttxok, any other question ?21:24
jeblairttx: i guess that's still a no on the design summit map?21:25
asalkeldall good, looking forward to getting to paris21:25
ttxjeblair: asking21:25
jeblairttx: also, is there an indoor passage between the two?21:26
ttxjeblair: no indoor passage for sure21:26
ttxit's two separate buildings.21:26
jeblairso bring our umbrellas to lunch :)21:26
*** MaxV has joined #openstack-meeting21:27
ttxyou can survive crossing the street in open air, I think :)21:27
ttxok, next topic21:27
*** armax has quit IRC21:27
ttx#topic Explicitly state which projects can add requirements21:27
*** openstack changes topic to "Explicitly state which projects can add requirements (Meeting topic: project)"21:27
ttx#link https://review.openstack.org/#/c/13024521:27
ttxNot exactly sure what we need to discuss there21:27
*** rushiagr is now known as rushiagr_away21:27
*** markmcclain1 has quit IRC21:27
jeblairdhellmann, sdague: ?21:28
asalkeldso "including stackforge" is new?21:28
jeblairit's a major proposed policy change, yes21:28
ttxI think the idea was to check it with all PTLs21:28
jeblairit even has a cross-project summit session21:28
ttxbefore it gets accepted and it's a pain to rollback21:28
thingee:q21:28
sdaguethere is also some infrastructure being added to devstack to make it probably not needed, so that should postpone21:29
SergeyLukjanovIMO due to the crossproject session it should be postponed to summit / after summit21:29
jeblairi think it would have less impact on ptls than the requirements reviewers and distros, whare are actually the primary audience for the requirements repo21:29
*** MaxV has quit IRC21:29
ttxmaybe we should all do our homework and read that, and keep the discussion about that for the cross-project session ?21:29
asalkeldyeah21:29
asalkeldbig impact to distros21:29
SergeyLukjanov+121:29
asalkeldalso do we have a policy on what gets accepted21:30
asalkeldor is it open21:30
jeblairasalkeld: https://wiki.openstack.org/wiki/Requirements21:30
asalkeldjeblair, so that part is staying the same then21:31
SergeyLukjanovone more issue - for now if we have some lib in global req. than we're trying to avoiding alt. lib too instead of using the first one21:31
SergeyLukjanovbut in case if we'll open global reqs. it'll start looking like pypi.python.org eventually21:31
SergeyLukjanovI'm feeling myself disconnected from IRC21:32
eglynndon't we already accept requirements from stackforge projects? ... is this just making that policy explicit?21:32
asalkeldeglynn, not to my knowledge21:32
*** manishg has joined #openstack-meeting21:32
jeblaireglynn: we do not accept requirements from stackforge, and for good reason21:33
*** armax has joined #openstack-meeting21:33
asalkeldjeblair, are you against this then?21:33
*** markwash__ has quit IRC21:33
asalkeldjust seeing the "and for good reason"21:33
jeblairasalkeld: yes, i agree with sdague, both in the review, and in the alternate proposal to resolve the issue21:34
asalkeldok21:34
*** armax has quit IRC21:34
* jeblair reviews that change :)21:34
eglynnjeblair: I was thinking specifically of posix_ipc for stackforge/tooz21:34
eglynnjeblair: ... but I see now that was originally added for oslo lockutils21:34
*** noelbk has quit IRC21:35
asalkeldi like the "soft updating"21:35
jeblairi reviewed the other ones (that implement soft update)21:35
*** noelbk has joined #openstack-meeting21:35
*** daneyon has left #openstack-meeting21:35
jogoI wonder how global-requirements would work in the big tent proposal21:35
asalkeldjogo, "big tent" still doesn't mean totally unfiltered surely21:36
eglynnjeblair: similarly for dependency version lower bounds that are motivated by stackforge usage?21:36
*** e0ne has quit IRC21:36
jeblairjogo: yeah, definitely worth talking about.  i believe the main thing we get from it is the ability for distros to sanely, well, distribute "openstack"21:36
ttxPart of the issue is that we use global-requirements for multiple things21:37
asalkeldhopefully it is sensible but more open acceptance21:37
ttxone of them is general dependency convergence21:37
eglynn(... where the same dependency is also used by another project under openstack/ )21:37
ttxothers are more integration/testing related21:37
jeblairso i think the answer to that is probably something like "it's small, for the stuff we think is really the core of openstack" or "it's big and anyone who wants to be part of the big tent uses it"21:37
*** emagana_ has quit IRC21:37
*** adahms has joined #openstack-meeting21:37
*** emagana has joined #openstack-meeting21:38
jeblairttx: i think integration/testing is still part of the primary use -- dependency convergence + compatability21:38
ttxFYI Maps of Le Meridien shall be uploaded tonight, so that "venue maps" thing should hopefuly look better tomorrow21:38
jeblairit's not to select a version of something we test with, it's so that we're testing with the set of dependencies we have selected for the project as a whole21:38
*** zns has quit IRC21:39
*** matrohon has quit IRC21:39
*** moha_hunt has joined #openstack-meeting21:39
jeblairttx: thanks!21:40
asalkeldunless everyone uses docker this is going to get messy21:40
jeblairasalkeld: what's going to get messy?21:40
asalkeld(big tent and global requirements)21:40
dims__asalkeld: fyi, heat already uses docker-py, just not in requirements21:40
asalkelddims__, i mean to distribute openstack services21:41
*** shohel02 has joined #openstack-meeting21:41
*** andreykurilin_ has quit IRC21:41
*** emagana_ has joined #openstack-meeting21:41
asalkelddocker-py stuff is in contrib/21:41
dims__asalkeld: ack21:41
ttxOK, so I think the next step on that one is the cross-project workshop on requirements at the summit21:41
*** emagana has quit IRC21:41
jeblairasalkeld: maybe?  or maybe part of the big tent is taking a hard line on requirements to prevent it from getting messy... enough non-openstack projects want requirements enforcement that it seems like a possibility to me.21:41
ttxI'll leave a note on the review21:42
*** khaldrogox has joined #openstack-meeting21:42
*** enikanorov__ has quit IRC21:42
asalkeldjeblair, maybe21:42
eglynnjeblair: just to clarify on the version lower bounds ... not kosher to require redis>=2.10.0 if motivated by tooz usage of redis, but kosher if say motivated by zaqar?21:42
*** marcoemorais1 has quit IRC21:42
*** dkranz has quit IRC21:43
jeblaireglynn: correct.  (and that's why we're talking about tents)21:43
ttx#topic Open discussion21:43
*** openstack changes topic to "Open discussion (Meeting topic: project)"21:43
ttxAnything else, anyone ?21:43
asalkeldnope21:44
fungier, python 3.4!21:44
ttxWe should almost all be together in a few days21:44
fungi#link https://etherpad.openstack.org/p/py34-transition21:44
fungiwe're waiting for a couple of bugs to clear through an ubuntu sru to trusty21:44
fungibut also i'm worried glanceclient won't get their tests working in time for us to cut them over from 3.3 to 3.421:45
*** marcoemorais has joined #openstack-meeting21:45
asalkeldseeing lots of client related patches21:45
fungi#link http://lists.openstack.org/pipermail/openstack-dev/2014-October/048659.html21:45
*** MeganR has joined #openstack-meeting21:45
fungi#link https://launchpad.net/bugs/138258221:45
uvirtbotLaunchpad bug 1382582 in python-glanceclient "untestable in Python 3.4" [Medium,Confirmed]21:45
*** shohel02 has quit IRC21:45
fungiasalkeld: yes, the glanceclient patches are great. i've already tested them and they're working21:46
ttxnikhil_k: ^21:46
fungier, heatclient21:46
*** harlowja_away is now known as harlowja21:46
*** dims__ has quit IRC21:46
asalkeldcool21:46
ttxLooks like Glance is on the critical path21:46
fungiso i think heatclient is on track21:46
*** rockyg has joined #openstack-meeting21:46
*** atan8 has joined #openstack-meeting21:46
fungibut yeah, glanceclient may end up delaying our switch off the old py3k-precise nodes, or we might have to temporarily drop py3k testing for that project21:47
ttxfungi: not sure nikhil_k is around. Looks like you should pay a visit to the Glance crew next week21:47
jeblairor we enforce python3.4 testing for it :)21:47
fungii'll lurk in their team pod menacingly21:47
*** jckasper has quit IRC21:47
* fungi makes sure to pack his most menacing hawaiian shirt21:47
*** lhcheng has joined #openstack-meeting21:47
*** marcoemorais has quit IRC21:48
*** marcoemorais has joined #openstack-meeting21:48
asalkeld:-)21:48
ttxok, one more minute for questions before I close the shop21:48
* nikhil_k jumping between channels21:48
ttxfungi: grab nikhil_k while he is here!21:48
funginikhil_k: just asking for the glanceclient devs to bump priority on https://launchpad.net/bugs/1382582 if possible21:49
uvirtbotLaunchpad bug 1382582 in python-glanceclient "untestable in Python 3.4" [Medium,Confirmed]21:49
*** marun has quit IRC21:49
nikhil_kfungi: noted21:49
fungiand planning for contingencies if needed21:49
nikhil_kfungi: would that be sufficient on master or need a version?21:49
funginikhil_k: master will be fine21:50
fungijust want to make sure we can get it passing 3.4 tests before we drop 3.3 tests in infra21:50
*** markwash__ has joined #openstack-meeting21:50
nikhil_kfungi: I'm sure I'd your email on my to-do list21:50
*** garthb_ has joined #openstack-meeting21:51
funginikhil_k: thanks!21:51
nikhil_kwill bring this up in the meeting21:51
*** thangp has quit IRC21:51
*** moha_hunt has quit IRC21:51
ttxalrighty then. See you all in a few days!21:51
ttx#endmeeting21:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:51
openstackMeeting ended Tue Oct 28 21:51:24 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2014/project.2014-10-28-21.02.html21:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2014/project.2014-10-28-21.02.txt21:51
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2014/project.2014-10-28-21.02.log.html21:51
*** curtis_p has left #openstack-meeting21:51
*** david-lyle has quit IRC21:52
*** andreykurilin_ has joined #openstack-meeting21:53
*** david-lyle has joined #openstack-meeting21:53
SergeyLukjanovttx, thx21:53
*** slong has joined #openstack-meeting21:55
*** rockyg has quit IRC21:56
*** js1123_ has quit IRC21:56
*** simon-AS5591 has joined #openstack-meeting21:57
*** jehb has quit IRC21:58
*** rockyg has joined #openstack-meeting21:58
*** neelashah has quit IRC21:59
*** MeganR has quit IRC21:59
*** simon-AS559 has quit IRC22:00
*** neelashah has joined #openstack-meeting22:00
*** tbarron has quit IRC22:01
morganfainberghogepodge, ping22:01
morganfainberghogepodge, you in-charge of "other project" sessions?22:01
morganfainbergor is that ttx ?22:01
*** neelashah has quit IRC22:04
*** simon-AS5591 has quit IRC22:07
*** kebray has quit IRC22:09
*** thedodd has quit IRC22:09
*** kebray has joined #openstack-meeting22:10
*** rockyg has quit IRC22:11
*** badveli_ has quit IRC22:13
*** khaldrogox has quit IRC22:13
*** garyduan has quit IRC22:14
*** asalkeld has quit IRC22:14
*** garyduan has joined #openstack-meeting22:14
*** e0ne has joined #openstack-meeting22:15
*** armax has joined #openstack-meeting22:16
*** thedodd has joined #openstack-meeting22:19
*** julim has joined #openstack-meeting22:20
*** ptoohill_ has quit IRC22:21
*** zehicle has joined #openstack-meeting22:23
*** scotm has quit IRC22:26
*** changbl has quit IRC22:26
*** emagana_ has quit IRC22:26
*** juzuluag has quit IRC22:27
*** sarob_ has quit IRC22:27
*** ajo_ has quit IRC22:30
*** IanGovett has quit IRC22:30
*** jmontemayor has quit IRC22:32
*** david-lyle_ has joined #openstack-meeting22:33
*** vivek-ebay has quit IRC22:33
*** thedodd has quit IRC22:35
*** david-lyle has quit IRC22:36
*** andreaf has joined #openstack-meeting22:37
*** matrohon has joined #openstack-meeting22:38
*** zns has joined #openstack-meeting22:39
*** gyee has joined #openstack-meeting22:39
*** jckasper has joined #openstack-meeting22:40
*** david-lyle has joined #openstack-meeting22:41
*** shohel02 has joined #openstack-meeting22:41
*** vijendar has quit IRC22:42
*** jorge_munoz has quit IRC22:42
*** JRobinson__ has joined #openstack-meeting22:43
*** vivek-ebay has joined #openstack-meeting22:43
*** zns has quit IRC22:44
*** rbowen has quit IRC22:44
*** nelsnelson has quit IRC22:44
*** jgrimm is now known as zz_jgrimm22:44
*** zns has joined #openstack-meeting22:44
*** david-lyle_ has quit IRC22:45
*** dane_leblanc has quit IRC22:45
*** shohel02 has quit IRC22:46
*** dims__ has joined #openstack-meeting22:46
*** oanufriev1 has joined #openstack-meeting22:47
*** khaldrogox has joined #openstack-meeting22:49
*** dims__ has quit IRC22:52
*** manishg has quit IRC22:52
*** matrohon has quit IRC22:52
*** amcrn has quit IRC22:52
*** leeantho has quit IRC22:53
*** thingee has left #openstack-meeting22:54
*** dims__ has joined #openstack-meeting22:55
*** dims__ has quit IRC22:55
*** emagana has joined #openstack-meeting22:55
*** dims__ has joined #openstack-meeting22:56
*** henrynash has quit IRC22:56
*** dims__ has quit IRC22:57
*** dims__ has joined #openstack-meeting22:57
*** Riddhi has quit IRC22:59
*** pballand has quit IRC23:00
*** jhenner has quit IRC23:00
*** timrc is now known as timrc-afk23:01
*** aepifanov has quit IRC23:01
*** pballand has joined #openstack-meeting23:01
*** baoli has quit IRC23:01
*** bagackiz has quit IRC23:03
*** tsekiyam_ has joined #openstack-meeting23:04
*** matiu has joined #openstack-meeting23:05
*** kebray has quit IRC23:07
*** rbak has quit IRC23:07
*** timrc-afk is now known as timrc23:07
*** tsekiyama has quit IRC23:07
*** andreaf has quit IRC23:08
*** tsekiyam_ has quit IRC23:08
*** mattgriffin has quit IRC23:09
*** henrynash has joined #openstack-meeting23:10
*** ddieterly has quit IRC23:10
*** ddieterly has joined #openstack-meeting23:11
*** manishg has joined #openstack-meeting23:11
*** andreaf has joined #openstack-meeting23:11
*** mattgriffin has joined #openstack-meeting23:12
*** vivek-ebay has quit IRC23:14
*** khaldrogox has quit IRC23:15
*** ddieterly has quit IRC23:15
*** emagana has quit IRC23:16
*** andreaf has quit IRC23:16
*** emagana has joined #openstack-meeting23:17
*** andreaf has joined #openstack-meeting23:17
*** manishg has quit IRC23:20
*** vivek-ebay has joined #openstack-meeting23:20
*** emagana_ has joined #openstack-meeting23:21
*** emagana has quit IRC23:21
*** khaldrogox has joined #openstack-meeting23:21
*** emagana_ has quit IRC23:22
*** emagana has joined #openstack-meeting23:23
*** bagackiz has joined #openstack-meeting23:24
*** emagana has quit IRC23:27
*** emagana has joined #openstack-meeting23:28
*** vivek-ebay has quit IRC23:31
*** emagana has quit IRC23:32
*** pballand has quit IRC23:32
*** vivek-ebay has joined #openstack-meeting23:33
*** s3wong has quit IRC23:33
hogepodgemorganfainberg I'm in charge of the dev, I think ttx is doing the other23:35
morganfainberghogepodge: this is on the dev side. But I think there isn't enough room to get in everything anyway. So... Don't worry about it.23:35
hogepodgewhat were you thinking?23:36
*** bill_az has quit IRC23:36
*** rushiagr_away is now known as rushiagr23:36
*** carl_baldwin has quit IRC23:37
*** marun has joined #openstack-meeting23:39
*** andreykurilin_ has quit IRC23:40
*** henrynash has quit IRC23:40
*** shohel02 has joined #openstack-meeting23:41
*** matjazp has joined #openstack-meeting23:41
*** matjazp has left #openstack-meeting23:41
*** amcrn has joined #openstack-meeting23:42
*** andreaf has quit IRC23:43
*** sarob has joined #openstack-meeting23:44
*** jckasper has quit IRC23:44
*** jckasper has joined #openstack-meeting23:45
*** johnpur_ has joined #openstack-meeting23:45
*** johnpur has quit IRC23:45
*** johnpur_ is now known as johnpur23:45
*** shohel02 has quit IRC23:46
*** nati_ueno has joined #openstack-meeting23:47
*** igordcard has quit IRC23:47
*** mattgriffin has quit IRC23:47
*** SumitNaiksatam has quit IRC23:48
*** david-lyle has quit IRC23:50
*** nati_ueno has quit IRC23:50
*** niclem has quit IRC23:51
*** mwagner_lap has joined #openstack-meeting23:51
*** khaldrogox has quit IRC23:55
*** samcdona has quit IRC23:55
*** atan8 has quit IRC23:58

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