Tuesday, 2013-07-30

*** luis_ has quit IRC00:01
*** luis_ has joined #openstack-meeting00:02
*** nachi has quit IRC00:04
*** JJoa has joined #openstack-meeting00:05
*** JJoa has quit IRC00:05
*** hemna is now known as hemnafk00:06
*** IlyaE has quit IRC00:07
*** SenK9 has joined #openstack-meeting00:07
*** jackmccann has quit IRC00:08
*** diogogmt has quit IRC00:08
*** alrs has joined #openstack-meeting00:10
*** mberwanger has quit IRC00:12
*** sarob_ has joined #openstack-meeting00:14
*** jlucci has quit IRC00:15
*** nati_ueno has quit IRC00:16
*** emagana has quit IRC00:16
*** sarob has quit IRC00:17
*** alrs has quit IRC00:18
*** nati_uen_ has quit IRC00:18
*** nati_ueno has joined #openstack-meeting00:19
*** tanisdl has quit IRC00:22
*** colinmcnamara has quit IRC00:22
*** epim has quit IRC00:23
*** jecarey has quit IRC00:25
*** gyee has quit IRC00:27
*** rwsu is now known as rwsu-away00:27
*** fallenpegasus has joined #openstack-meeting00:27
*** markwash has quit IRC00:28
*** nati_uen_ has joined #openstack-meeting00:29
*** armax has joined #openstack-meeting00:29
*** armax has quit IRC00:31
*** galstrom is now known as galstrom_zzz00:35
*** nati_uen_ has quit IRC00:40
*** lastidiot has joined #openstack-meeting00:44
*** bdpayne has quit IRC00:44
*** IlyaE has joined #openstack-meeting00:45
*** nati_ueno has quit IRC00:47
*** nati_ueno has joined #openstack-meeting00:51
*** nati_ueno_2 has joined #openstack-meeting00:52
*** dkranz has joined #openstack-meeting00:53
*** nati_ueno_2 has quit IRC00:56
*** dosaboy has quit IRC00:59
*** schwicht has joined #openstack-meeting01:00
*** alexb_ has joined #openstack-meeting01:01
*** dkranz has quit IRC01:04
*** troytoman is now known as troytoman-away01:05
*** troytoman-away is now known as troytoman01:06
*** schwicht has quit IRC01:09
*** jrodom has quit IRC01:11
*** dani4571 has quit IRC01:11
*** yaguang has joined #openstack-meeting01:11
*** fallenpegasus has quit IRC01:11
*** esker has quit IRC01:12
*** yaguang has quit IRC01:16
*** rods has quit IRC01:19
*** Mandell has quit IRC01:22
*** nati_ueno has quit IRC01:25
*** ItSANgo has quit IRC01:26
*** anteaya has quit IRC01:30
*** benonsoftware has quit IRC01:30
*** jrodom has joined #openstack-meeting01:32
*** neelashah has joined #openstack-meeting01:35
*** spzala has quit IRC01:40
*** yaguang has joined #openstack-meeting01:40
*** ItSANgo has joined #openstack-meeting01:41
*** jrodom has quit IRC01:45
*** SumitNaiksatam has quit IRC01:47
*** fnaval_ has joined #openstack-meeting01:49
*** sarob_ has quit IRC01:51
*** thomasm has joined #openstack-meeting01:59
*** mirrorbox has quit IRC02:05
*** mirrorbox has joined #openstack-meeting02:06
*** alexpilotti has quit IRC02:08
*** markmcclain has quit IRC02:15
*** novas0x2a|laptop has quit IRC02:15
*** dguitarbite has joined #openstack-meeting02:17
*** SumitNaiksatam has joined #openstack-meeting02:19
*** nati_ueno has joined #openstack-meeting02:22
*** woodspa_ has quit IRC02:23
*** michchap has quit IRC02:27
*** colinmcnamara has joined #openstack-meeting02:37
*** lbragstad has joined #openstack-meeting02:38
*** colinmcnamara has quit IRC02:39
*** jlucci has joined #openstack-meeting02:40
*** colinmcnamara has joined #openstack-meeting02:42
*** asalkeld is now known as asalkeld_food02:46
*** ayoung has quit IRC02:56
*** mberwanger has joined #openstack-meeting03:08
*** Tross has joined #openstack-meeting03:09
*** HenryG has quit IRC03:10
*** sarob has joined #openstack-meeting03:18
*** martine_ has joined #openstack-meeting03:19
*** Mandell has joined #openstack-meeting03:26
*** bdpayne has joined #openstack-meeting03:29
*** Tross has quit IRC03:33
*** martine_ has quit IRC03:38
*** marun has quit IRC03:38
*** anniec has joined #openstack-meeting03:45
*** mberwang_ has joined #openstack-meeting03:45
*** afazekas__ has quit IRC03:48
*** mberwanger has quit IRC03:48
*** asalkeld_food has quit IRC03:49
*** jrodom has joined #openstack-meeting03:56
*** vkmc has quit IRC04:00
*** afazekas has joined #openstack-meeting04:03
*** edmund has quit IRC04:03
*** asalkeld has joined #openstack-meeting04:04
*** yamahata has quit IRC04:05
*** martine has joined #openstack-meeting04:06
*** martine is now known as Guest9350404:06
*** benonsoftware has joined #openstack-meeting04:07
*** SumitNaiksatam has quit IRC04:11
*** SumitNaiksatam has joined #openstack-meeting04:12
*** kebray has joined #openstack-meeting04:13
*** yamahata has joined #openstack-meeting04:17
*** krtaylor has joined #openstack-meeting04:20
*** dguitarbite has quit IRC04:27
*** dguitarbite has joined #openstack-meeting04:29
*** cyeoh has left #openstack-meeting04:30
*** anniec has quit IRC04:33
*** jrodom has quit IRC04:34
*** yamahata has quit IRC04:34
*** bdpayne has quit IRC04:36
*** dguitarbite has quit IRC04:36
*** yamahata has joined #openstack-meeting04:36
*** Guest93504 has quit IRC04:36
*** garyk has quit IRC04:37
*** colinmcnamara has quit IRC04:40
*** vipul is now known as vipul-away04:41
*** SergeyLukjanov has joined #openstack-meeting04:42
*** vipul-away is now known as vipul04:47
*** terriyu has joined #openstack-meeting04:50
*** neelashah has quit IRC04:51
*** bdpayne has joined #openstack-meeting04:54
*** mrunge has joined #openstack-meeting04:57
*** mrunge has quit IRC04:57
*** mrunge has joined #openstack-meeting04:57
*** haomaiwa_ has joined #openstack-meeting05:03
*** haomaiwang has quit IRC05:03
*** mberwang_ has quit IRC05:03
*** jrodom has joined #openstack-meeting05:05
*** michchap has joined #openstack-meeting05:08
*** lastidiot has quit IRC05:09
*** alrs has joined #openstack-meeting05:10
*** IlyaE has quit IRC05:13
*** bdpayne has quit IRC05:15
*** nati_ueno has quit IRC05:16
*** IlyaE has joined #openstack-meeting05:16
*** shang has quit IRC05:16
*** nati_ueno has joined #openstack-meeting05:18
*** enikanorov-w_ has quit IRC05:19
*** obondarev has quit IRC05:19
*** enikanorov-w has joined #openstack-meeting05:20
*** obondarev has joined #openstack-meeting05:21
*** emagana has joined #openstack-meeting05:23
*** sarob has quit IRC05:23
*** sarob has joined #openstack-meeting05:24
*** haomaiwa_ has quit IRC05:24
*** sarob_ has joined #openstack-meeting05:25
*** afazekas is now known as afazekas__05:25
*** haomaiwang has joined #openstack-meeting05:25
*** sarob has quit IRC05:26
*** haomaiwang has quit IRC05:27
*** haomaiwang has joined #openstack-meeting05:28
*** afazekas__ has quit IRC05:30
*** nati_ueno has quit IRC05:31
*** sarob_ has quit IRC05:36
*** sarob has joined #openstack-meeting05:36
*** dguitarbite has joined #openstack-meeting05:38
*** jlucci has quit IRC05:38
*** devananda has quit IRC05:39
*** sarob has quit IRC05:40
*** emagana has quit IRC05:42
*** bdpayne has joined #openstack-meeting05:42
*** jlucci has joined #openstack-meeting05:47
*** markpeek has quit IRC05:49
*** afazekas has joined #openstack-meeting05:49
*** cwolferh_ has joined #openstack-meeting05:50
*** salv-orlando has joined #openstack-meeting05:51
*** dguitarbite has left #openstack-meeting05:53
*** cwolferh has quit IRC05:54
*** emagana has joined #openstack-meeting05:58
*** stevemar has quit IRC05:58
*** SenK9 has quit IRC06:02
*** jrodom has quit IRC06:04
*** michchap has quit IRC06:04
*** michchap has joined #openstack-meeting06:05
*** garyk has joined #openstack-meeting06:05
*** abaron has joined #openstack-meeting06:06
*** jlucci has quit IRC06:07
*** emagana has quit IRC06:08
*** jhenner has joined #openstack-meeting06:10
*** SergeyLukjanov has quit IRC06:10
*** troytoman is now known as troytoman-away06:11
*** schwicht has joined #openstack-meeting06:11
*** shang has joined #openstack-meeting06:25
*** sushils has joined #openstack-meeting06:26
*** kebray has quit IRC06:27
*** michchap has quit IRC06:28
*** bdpayne has quit IRC06:28
*** otherwiseguy has quit IRC06:37
*** sushils has quit IRC06:38
*** sushils has joined #openstack-meeting06:38
*** emagana has joined #openstack-meeting06:41
*** sarob has joined #openstack-meeting06:47
*** emagana has quit IRC06:47
*** nati_ueno has joined #openstack-meeting06:51
*** sarob has quit IRC06:52
*** IlyaE has quit IRC06:57
*** slavayssiere has joined #openstack-meeting07:00
*** jhenner has quit IRC07:00
*** egallen has joined #openstack-meeting07:01
*** abaron has quit IRC07:06
*** sarob has joined #openstack-meeting07:09
*** SergeyLukjanov has joined #openstack-meeting07:10
*** nati_ueno has quit IRC07:10
*** abaron has joined #openstack-meeting07:22
*** rpodolyaka has joined #openstack-meeting07:32
*** egallen has quit IRC07:32
*** michchap has joined #openstack-meeting07:33
*** slavayssiere has quit IRC07:35
*** jcoufal has joined #openstack-meeting07:38
*** egallen has joined #openstack-meeting07:40
*** sarob has quit IRC07:41
*** sarob has joined #openstack-meeting07:42
*** sarob has quit IRC07:46
*** slavayssiere has joined #openstack-meeting07:47
*** ruhe has joined #openstack-meeting07:48
*** jhenner has joined #openstack-meeting07:52
*** newptone has joined #openstack-meeting07:53
*** emagana has joined #openstack-meeting07:58
*** slavayssiere has quit IRC07:58
*** psedlak has joined #openstack-meeting08:01
*** SergeyLukjanov has quit IRC08:02
*** emagana has quit IRC08:03
*** SergeyLukjanov has joined #openstack-meeting08:05
*** slavayssiere has joined #openstack-meeting08:14
*** shang has quit IRC08:22
*** erwan_ta- is now known as erwan_taf08:23
*** ruhe has quit IRC08:24
*** derekh has joined #openstack-meeting08:38
*** shang has joined #openstack-meeting08:42
*** jhenner has quit IRC08:42
*** jhenner has joined #openstack-meeting08:42
*** slavayssiere has quit IRC08:49
*** sarob has joined #openstack-meeting08:52
*** bashok has joined #openstack-meeting08:52
*** comay has joined #openstack-meeting08:55
*** koolhead17 has quit IRC08:57
*** sarob has quit IRC08:57
*** giovannone has joined #openstack-meeting09:05
*** egallen has quit IRC09:06
*** yaguang has quit IRC09:06
*** egallen has joined #openstack-meeting09:07
*** slavayssiere has joined #openstack-meeting09:10
*** abaron has quit IRC09:11
*** yaguang has joined #openstack-meeting09:15
*** ruhe has joined #openstack-meeting09:17
*** mrunge has quit IRC09:18
*** abaron has joined #openstack-meeting09:24
*** mrunge has joined #openstack-meeting09:32
*** Yada has joined #openstack-meeting09:34
*** egallen has quit IRC09:43
*** egallen has joined #openstack-meeting09:45
*** sushils has quit IRC09:47
*** sushils has joined #openstack-meeting09:52
*** SenK9 has joined #openstack-meeting10:02
*** johnthetubaguy has joined #openstack-meeting10:02
*** michchap has quit IRC10:04
*** michchap has joined #openstack-meeting10:04
*** ruhe has quit IRC10:06
*** rods has joined #openstack-meeting10:11
*** SenK9 has quit IRC10:17
*** sushils has quit IRC10:20
*** pcm_ has joined #openstack-meeting10:20
*** pcm_ has quit IRC10:20
*** pcm_ has joined #openstack-meeting10:21
*** sushils has joined #openstack-meeting10:23
*** egallen has quit IRC10:24
*** asalkeld is now known as asalkeld_afk10:29
*** martine has joined #openstack-meeting10:32
*** martine is now known as Guest9555910:32
*** Guest95559 has quit IRC10:36
*** shang has quit IRC10:37
*** giovannone has quit IRC10:39
*** ruhe has joined #openstack-meeting10:39
*** slavayssiere has quit IRC10:50
*** topol has joined #openstack-meeting10:53
*** yaguang has quit IRC10:56
*** martine_ has joined #openstack-meeting11:07
*** tedross has joined #openstack-meeting11:13
*** newptone has quit IRC11:16
*** dosaboy has joined #openstack-meeting11:17
*** ruhe has quit IRC11:17
*** zul has quit IRC11:18
*** zul has joined #openstack-meeting11:18
*** Yada has quit IRC11:18
*** jaimegil has joined #openstack-meeting11:22
*** egallen has joined #openstack-meeting11:36
*** vkmc has joined #openstack-meeting11:42
*** vkmc has quit IRC11:42
*** vkmc has joined #openstack-meeting11:42
*** zul has quit IRC11:53
*** zul has joined #openstack-meeting11:55
*** mrunge has quit IRC11:57
*** alexb_ has quit IRC11:57
*** zul has quit IRC12:01
*** topol has quit IRC12:01
*** Fdot has joined #openstack-meeting12:02
*** abaron has quit IRC12:02
*** alexb_ has joined #openstack-meeting12:06
*** zul has joined #openstack-meeting12:10
*** noslzzp has joined #openstack-meeting12:12
*** abaron has joined #openstack-meeting12:17
*** asalkeld_afk is now known as asalkeld12:19
*** zul has quit IRC12:24
*** zul has joined #openstack-meeting12:24
*** sandywalsh has quit IRC12:26
*** ruhe has joined #openstack-meeting12:27
*** thomasm has left #openstack-meeting12:28
*** slavayssiere has joined #openstack-meeting12:31
*** ruhe has quit IRC12:32
*** ruhe has joined #openstack-meeting12:39
*** rods1 has joined #openstack-meeting12:39
*** sandywalsh has joined #openstack-meeting12:40
*** rods has quit IRC12:41
*** dkranz has joined #openstack-meeting12:42
*** topol has joined #openstack-meeting12:44
*** jaimegil has quit IRC12:47
*** Fdot has quit IRC12:48
*** abaron has quit IRC12:50
*** oz_akan_ has joined #openstack-meeting12:52
*** oz_akan_ has left #openstack-meeting12:53
*** meteorfox has quit IRC12:53
*** eharney has joined #openstack-meeting12:54
*** lbragstad has quit IRC12:55
*** ruhe has quit IRC12:58
*** alexpilotti has joined #openstack-meeting12:59
*** edmund has joined #openstack-meeting13:00
*** anteaya has joined #openstack-meeting13:01
*** ruhe has joined #openstack-meeting13:02
*** abaron has joined #openstack-meeting13:04
*** topol has quit IRC13:05
*** Yada has joined #openstack-meeting13:06
*** bashok has quit IRC13:16
*** enikanorov has quit IRC13:16
*** changbl has quit IRC13:16
*** alexpilotti has quit IRC13:19
*** cdub_ has joined #openstack-meeting13:22
*** alexpilotti has joined #openstack-meeting13:25
*** lbragstad has joined #openstack-meeting13:28
*** jecarey has joined #openstack-meeting13:28
*** neelashah has joined #openstack-meeting13:29
*** rods has joined #openstack-meeting13:31
*** mestery has quit IRC13:32
*** mestery has joined #openstack-meeting13:33
*** vijendar has joined #openstack-meeting13:34
*** rods1 has quit IRC13:35
*** troytoman-away is now known as troytoman13:35
*** krtaylor has quit IRC13:36
*** emagana has joined #openstack-meeting13:36
*** fnaval_ has quit IRC13:37
*** Fdot has joined #openstack-meeting13:39
*** meteorfox has joined #openstack-meeting13:40
*** stevemar has joined #openstack-meeting13:44
*** markpeek has joined #openstack-meeting13:49
*** martine has joined #openstack-meeting13:50
*** martine is now known as Guest2629813:50
*** martine_ has quit IRC13:51
*** iccha_ has quit IRC13:51
*** michchap has quit IRC13:52
*** iccha has joined #openstack-meeting13:52
*** markmcclain has joined #openstack-meeting13:55
*** markmcclain has quit IRC13:55
*** jcoufal has quit IRC13:56
*** ndipanov has quit IRC13:59
*** ivasev has joined #openstack-meeting14:00
*** ndipanov has joined #openstack-meeting14:00
*** ayoung has joined #openstack-meeting14:01
*** MIDENN_ has joined #openstack-meeting14:04
*** fnaval_ has joined #openstack-meeting14:06
*** DuncanT- has quit IRC14:08
*** cp16net is now known as cp16net|away14:08
*** Swaminathan has quit IRC14:08
*** mdenny has quit IRC14:08
*** Swami has joined #openstack-meeting14:08
*** DuncanT- has joined #openstack-meeting14:09
*** mrodden has joined #openstack-meeting14:09
*** lastidiot has joined #openstack-meeting14:13
*** krtaylor has joined #openstack-meeting14:18
*** devananda has joined #openstack-meeting14:18
*** dkranz has quit IRC14:19
*** markmcclain has joined #openstack-meeting14:20
*** otherwiseguy has joined #openstack-meeting14:21
*** spzala has joined #openstack-meeting14:22
*** Tacho has joined #openstack-meeting14:22
*** spzala has quit IRC14:24
*** spzala_ has joined #openstack-meeting14:24
*** ruhe has quit IRC14:24
*** spzala_ is now known as spzala14:24
*** cp16net|away is now known as cp16net14:24
*** litong has joined #openstack-meeting14:27
*** lastidiot has quit IRC14:28
*** ruhe has joined #openstack-meeting14:31
*** burt has joined #openstack-meeting14:31
*** euanh has quit IRC14:34
*** dkranz has joined #openstack-meeting14:34
*** sushils has quit IRC14:36
*** changbl has joined #openstack-meeting14:38
*** derekh has quit IRC14:39
*** sushils has joined #openstack-meeting14:40
*** jgallard has joined #openstack-meeting14:42
*** dhellmann_ is now known as dhellmann14:44
*** jrodom has joined #openstack-meeting14:49
*** jgallard has quit IRC14:49
*** jgallard has joined #openstack-meeting14:49
*** markvan has joined #openstack-meeting14:52
*** johnpur has joined #openstack-meeting14:52
*** boris-42 has joined #openstack-meeting14:53
*** dkranz has quit IRC14:55
*** galstrom_zzz is now known as galstrom14:57
*** boris-42 has quit IRC14:57
*** rods has quit IRC14:57
*** rods has joined #openstack-meeting14:58
*** dscannell has joined #openstack-meeting14:59
n0ano#startmeeting scheduler14:59
openstackMeeting started Tue Jul 30 14:59:45 2013 UTC and is due to finish in 60 minutes.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.14:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:59
*** openstack changes topic to " (Meeting topic: scheduler)"14:59
openstackThe meeting name has been set to 'scheduler'14:59
n0anoshow of hands, anyone here for the scheduler meeting?15:00
*** dkranz has joined #openstack-meeting15:01
n0anojog0, just you & me so far, this could be quick :-)15:02
*** lpabon has joined #openstack-meeting15:02
*** euanh has joined #openstack-meeting15:02
*** Fdot has quit IRC15:02
*** jrodom has quit IRC15:02
*** jrodom has joined #openstack-meeting15:02
*** jrodom has quit IRC15:02
*** jrodom has joined #openstack-meeting15:03
n0anowell, while we're waiting for people...15:03
n0ano#topic administrivia15:04
*** openstack changes topic to "administrivia (Meeting topic: scheduler)"15:04
*** lastidiot has joined #openstack-meeting15:04
*** boris-42 has joined #openstack-meeting15:04
*** writerDi_ has joined #openstack-meeting15:04
n0anoI will be out the months of Sept & Oct (back in time for Hong Kong), anyone want to chair this meeting during those 2 months?15:04
*** writerDi_ is now known as dianefleming15:04
jog0n0ano: I would offer but, the time of day doesn't always work for me15:05
*** glikson has joined #openstack-meeting15:05
*** krtaylor has quit IRC15:05
alaskikind of the same for me.  I can take it sometimes, but I know I'll be out a few of those weeks.15:05
n0anowe don't need an asnwer today, I just wanted to get it out and we'll find someone, I don't want the meeting to die on the vine.15:06
*** alexb_ has quit IRC15:06
n0anomoving on to more interesting stuff15:06
*** dscannell has quit IRC15:06
boris-42hi all15:06
n0ano#topic multiple active scheduler policies/drivers15:06
*** openstack changes topic to "multiple active scheduler policies/drivers (Meeting topic: scheduler)"15:06
jgallardn0ano, to remember this point, can you "action" it?15:07
n0anoglikson, jog0 I believe you've been active on the list on this, can you summarize?15:07
*** Mr_T has joined #openstack-meeting15:07
*** johnpur has left #openstack-meeting15:07
*** esker has joined #openstack-meeting15:07
*** edmund has quit IRC15:07
gliksonI can try15:07
n0ano#action need new moderator for months of Sept & Oct15:07
n0anojgallard, tnx, good point15:07
jgallardn0ano, thanks :)15:08
*** colinmcnamara has joined #openstack-meeting15:08
*** dscannell1 has joined #openstack-meeting15:08
gliksonwe have a blueprint and a patch submitted. there have been several concerns with the current design approach.15:08
*** ruhe has quit IRC15:08
*** haomaiwang has quit IRC15:08
gliksonseems that the main one was whether we need API-driven management of policies, or we can start with something more simple for Havana15:09
*** abaron has quit IRC15:09
n0anoespecially given the short timeline remaining for Havana seems like starting simple with the option to make it more flexible in future would be the way to go15:10
*** resker has joined #openstack-meeting15:10
*** haomaiwang has joined #openstack-meeting15:10
n0anois the issue config files?15:10
*** eharney has quit IRC15:10
jog0simple isn't always good either.  we have to keep in mind that any 'simple' short term solution will have to have a migration path to the next thing  etc15:11
*** jgallard has quit IRC15:11
gliksonyes (I think). whether defining policies in nova.conf is good enough for Havana (similarly to cinder multi-backed support)15:11
*** jgallard has joined #openstack-meeting15:11
jog0IMHO, defining policies in nova.conf is not good enough for Havana15:11
*** esker has quit IRC15:12
*** alexb_ has joined #openstack-meeting15:12
gliksonjog0: agree, but I don't expect major issues with migration..15:12
n0anoare they really going to be so dynamic that this is an unreasonable restriction?15:12
gliksonI don't expect them to be dynamic in most cases15:12
*** kebray has joined #openstack-meeting15:12
jog0sure, they may not be dynamic but we don't want more config options in nova.conf15:13
gliksonadding policies typically means adding new kinds of hardware, or changing overall cloud management policies..15:13
n0anojog0, give the config file has well defined sections, what's wrong with putting them there15:13
jog0adding this to nova.conf means making nova.conf even more complex15:13
jog0n0ano: its not about the right section or not.  We want things to use the REST APIs when possible15:14
jgallardjog0, +115:14
gliksonin fact, adding APIs and DB support adds a lot to the overall complexity..15:14
n0anojog0, yes, APIs are the ultimate goal but is using the config file that much of a problem for Havana15:14
jog0well I think this is missing a big piece, cross project policies15:15
jog0such as cinder  and neutron related15:15
gliksonjog0: fully agree, but it shouldn't prevent us from solving an important subset of the problem in Havana15:15
jog0I disagree, I would like to see a plan for a better solution, and how this gets us on the right track15:16
*** tanisdl has joined #openstack-meeting15:16
n0anoseems to me we all want the APIs but think that's too complex a change for Havana15:16
jog0If there is a roadmap for how to get to the better solution, and this is an temporary solution then sure.  Also what about russellb's idea of using flavors15:17
gliksonjog0: do you think we can come up with such a plan without a discussion at the summit?15:17
n0anomaybe this is something that should be targeted for Icehouse and not Havana15:17
jog0glikson: true15:17
*** shanewang1 has joined #openstack-meeting15:17
gliksonjog0: I accepted his idea15:17
jog0glikson: so using flavors sounds likea good first step15:17
gliksonthe patch under review uses flavor extra specs15:18
jog0its doesn't change things in any major way15:18
jog0and addresses most of your basic requirments as far as I can tell15:18
gliksonthe extra spec specifies the policy15:18
gliksonjog0: in theory, we can specify all the scheduler parameters (driver, filters, etc) in the flavor -- but I think it would be an abuse..15:19
gliksonalso much harder in terms of compatibility and migration going forward15:19
jog0glikson: yeah15:19
jgallardglikson, yes, and complicated in term of flavors management and update too15:20
jog0well I think there is a bigger issue at hand.  Which is there are several competing scheduler blueprints and no overall plan15:20
n0anojog0, that should be handled by a session at the next summit, trying to come up with a comprehensive plan15:21
gliksonjog0: IMO, the proposed design is flexible enough to seamlessly move to different mechanism for persistency and lifecycle of policies, when we know what exactly we are trying to achieve.15:21
jog0glikson: the issue is when there are a bunch of BPs pulling the scheduler in different directions we end up with a mess15:22
n0anowe kind of had that at the last summit but it just wound up being a quick review of multiple BPs, not an overall plan15:22
gliksonjog0: in general, I agree that some sort of overall architecture and roadmap would be useful15:22
jog0yes, its too late to work on agree before the summit.  but its a good time to figure out the proposal for the summit15:22
*** bismigalis has joined #openstack-meeting15:23
shanewang1the duedate for feature proposal is Aug 23?15:23
*** resker has quit IRC15:23
jog0Some of the best summit sessions are the ones where there is a well thought out proposal that gets discussed15:23
jog0shanewang1: no new BPs already15:23
gliksonjog0: I will surely vote for having a discussion on this at the summit15:23
jog0glikson: a discussion over a fully proposed plan15:23
*** haomaiwang has quit IRC15:23
n0anolet's not get too side tracked, we're diverting from multiple schedulers into overall scheduler design15:23
*** esker has joined #openstack-meeting15:23
*** shanewang1 has left #openstack-meeting15:24
jog0n0ano: sorry, I just think its hard to have this discussion without the overall one15:24
*** shanewang1 has joined #openstack-meeting15:24
n0anoboth are good topics but let's finish the multiple scheduler discussion first15:24
n0anojog0, we're not going to finalize the overall picture today so I think it's still useful to discuss the specific issues15:25
n0anotrust me, I'm adding a `overall scheduler plan' as a topic (most likely for next week when we have a chance to think about it).15:26
jog0n0ano: no we aren't but we can start that discussion, perhaps schedule it off meeting15:26
gliksonjog0: the question is whether this particular BP, which has been discussed at high level at the last summit and approved, should be the one to "suffer" from this. It doesn't introduce any revolutionary changes, and does not seem to be contradicting any other major design goal that we may potentially want to enforce..15:26
n0anojog0, +1 (we're in violent agreement)15:26
jog0glikson: can you link to the patch15:26
*** markmcclain has quit IRC15:27
jog0glikson: I thought you said this used the flavors, not a list of policies15:28
gliksonjog0: flavor specifies the policy15:29
*** IlyaE has joined #openstack-meeting15:29
n0anoglikson, then where are the actual policies defined15:29
gliksonthe details of each policy is in nova.conf15:29
n0anoahh, now I see the issue, that does seem to be a bit of an abuse of the nova.conf15:30
jog0n0ano: yup15:30
gliksonspecify the default driver/filters is ok, but adding couple of extra ones is not?15:31
n0anoyou are now putting a potentially unbounded amount of info in the config file, not what it was defined for15:31
*** vijendar has quit IRC15:31
jog0n0ano: we want things like policies to be controlled via APIs when possible15:31
jog0this makes things like RBAC and  domains work nice15:32
gliksonn0ano: in theory..15:32
jgallardhummm, it's not the same thing for instance when you configure several cinder backend into cinder.conf ? (multiple sections into cinder.conf)15:32
gliksonjgallard: indeed, it is15:32
jgallardin that case, its not an issue15:32
jog0jgallard: isn't that saying this machine has these backends15:32
jog0and this is different per machine, and is only local.15:33
gliksonthat's where we 'stolen' the idea15:33
jog0while here we are saying I have these global policies and I am defining them in the nova.conf file15:33
*** ruhe has joined #openstack-meeting15:33
jog0where an admin API user cannot touch them even if the cloud operator wanted that15:33
n0anoI'm with jog0 on this one (he's expressing my concerns better)15:33
gliksonjog0: not really -- you can potentially control all of your storage pools via a single machine running cinder-volume15:33
*** cdub_ has quit IRC15:34
gliksonin fact, having a lot of storage pools, with dynamics, is a much more reallistic scenario than having lots of scheduling policies..15:34
jog0glikson: sure, but that is an edge case of this?  and adding new hardware is different than changing a policy15:34
n0anonote, just because cinder works this way doesn't mean we agree with that design, I'd say cinder is wrong in this case15:36
gliksonjog0: can you have an example, what kind of scheduling policies do you have in mind when thinking about having lots of them?15:36
*** jgallard has quit IRC15:36
*** rnirmal has joined #openstack-meeting15:37
jog0glikson: who knows, but why can't I as a owner of a cloud say, you as a seperate domain and maybe a virtual private cloud inside of mine cannot set your own arbitrary scheduling policies15:37
*** jgallard has joined #openstack-meeting15:37
*** sandywalsh has quit IRC15:37
gliksonjog0: you surely can, but it is not supported by the patch we've submitted. we support many other use-cases, which do not require this kind of programmability. we don't need to support all the possible policy-related use-cases in a single patch, right?15:38
n0anoglikson, as long as you have a way of ultimately supporting all the use cases starting simple is fine15:39
gliksonI am not aware of any inherent problems with our implementation that would prevent anyone from extending it to support better progammability15:39
jog0glikson: anyway, I think the next step here is:15:39
*** markwash has joined #openstack-meeting15:40
jog0clearly explain your current patch in great detail, and push to the ML thread and see what happens15:40
gliksonon ther other hand, I am also not aware of any alternative implemetation that would solve the bigger problem in Havana time frame..15:40
*** jcoufal has joined #openstack-meeting15:40
*** hk_peter has joined #openstack-meeting15:41
jog0glikson: this isn't always about the first implementation proposal wins, its about the 'right one,' however that is defined15:41
gliksonjog0: you mean, use cases or implementation?15:41
jog0glikson: implementation15:41
jgallarddoes this patch was not already discussed on the ML?15:42
*** Fdot has joined #openstack-meeting15:42
jog0jgallard: the patch has had several revisions since then, not sure if that has changed anything major15:42
gliksonthere is no single "right one" in most cases. if this solves a real problem, and it seems to be flexible enough to extend to support additional use-cases -- this should be enough, IMO..15:42
jgallardjog0, ok15:42
gliksonjog0: we addressed some of Russell's suggestions.15:43
hk_peterit is a nova meeting or a ceilometer meeting?15:43
n0anohk_peter, nova15:43
*** pnavarro has joined #openstack-meeting15:43
russellbglikson: needs to be re-reviewed now?15:43
hk_peter@n0ano thx15:43
gliksonhi russel. yes, would appreciate if you could take another look (and maybe remove your -2)15:43
jog0glikson: well for one thing the commit msg needs work15:44
russellback, will look15:44
*** danwent has joined #openstack-meeting15:44
hk_peteris there anybody can help to design the screen for nova's schduler setup?15:44
gliksonrussellb: you may also take a look at the discussion we just had here, in the last 1/2 hour..15:44
gliksonjog0: ok15:46
n0anoso, are we winding down on this subject (subject to mailing list activity coming up)?15:47
*** zehicle_at_dell has joined #openstack-meeting15:47
*** dkranz has quit IRC15:47
n0anotaking silence as assent...15:48
n0ano#topic opens15:48
*** openstack changes topic to "opens (Meeting topic: scheduler)"15:48
n0anoI wanted to talk about instance groups (but gary doesn't seem to be here) and/or simple way to improve the scheduler but I don't think there's enough time15:48
n0anowe'll defer those to next week.15:48
n0anoanyone have anything new to bring up toda?15:49
hk_petercan i say something about my project pandora? i scare i am disturbing15:49
*** topol has joined #openstack-meeting15:49
n0anohk_peter, is this scheduler related?15:49
hk_peterkind of15:49
n0anogo ahead15:49
hk_peterbut i really want to say something about pandora background first15:49
gliksonhk_peter, got a link?15:50
n0anohk_peter, I was going to say, is this something you should start on the dev mailing list first?15:50
*** AlanClark has joined #openstack-meeting15:50
hk_peterpandora is a admin console http://peter.kingofcoders.com  , we are *NOT* forking horizon, we have the horizon API. We want to create a better GUI, so customer is easier to make the decision to purchase openstack15:50
jog0hk_peter: is this opensource?15:51
hk_peteryes, completely open source, apache license15:51
jog0why not push code up into horizon?15:52
n0anohk_peter, sounds to me like you `are` trying to replace horizon, you'd better expect a certain amount of controversy15:52
hk_petertwo days ago, hong kong openstack community chairman want to submit our news to openstack blog, but refused, we are very down.15:52
n0anohk_peter, why not just enhance/change horizon15:52
hk_peterI just want to say, pandora rely on horizon, we are not forking it.15:52
hk_peterPandora is java, hard to push code into horizon15:52
hk_peterPandora is not web base, i think our team can do better in a standalone app.15:53
*** zehicle_at_dell has quit IRC15:53
jgallardwhat is the link with scheduling?15:53
*** sandywalsh has joined #openstack-meeting15:53
n0anohk_peter, do you have a detailed design you can point us to (I'm not liking what I'm hearing so far I have to tell you)15:53
hk_peterHonestly, i still not sure how to submit code review to horizon team, we want to enhance the scheduler, give it a nice UI15:53
*** egallen has quit IRC15:53
hk_peterhere you go http://peter.kingofcoders.com/?p=44215:54
*** egallen has joined #openstack-meeting15:55
n0anohk_peter, we don't have time to discuss this more today, I strongly suggest you raise this on the dev mailing list15:55
hk_peterthanks n0ano15:55
n0anoanything else new anyone want to raise?15:55
hk_petertake you time15:55
jog0hk_peter: the short of it is you can't adjust QOS scheduling today via any REST APIs15:56
jog0well there are a few ways starting to show up, but we are discussing that here15:56
hk_peterif we give it a REST APIs, letting people/third party program to reprogram the scheduler, isn't it great?15:57
jog0hk_peter: see above15:57
n0anohk_peter, in a word, no, that's not necessarily a good idea15:57
*** ociuhandu has joined #openstack-meeting15:58
n0anoanyway, times up, so I'll thank everyone and we'll talk again next week.15:58
*** openstack changes topic to "OpenStack meetings || https://wiki.openstack.org/wiki/Meetings"15:58
openstackMeeting ended Tue Jul 30 15:58:27 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-07-30-14.59.html15:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-07-30-14.59.txt15:58
openstackLog:            http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-07-30-14.59.log.html15:58
*** neelashah has quit IRC15:58
*** luis_fdez has joined #openstack-meeting15:58
*** shanewang1 has left #openstack-meeting15:58
jgallardthanks all!15:58
*** Mandell has quit IRC15:58
hk_peterthanks, forgive my bad english :)15:59
*** jlucci has joined #openstack-meeting15:59
*** garyk has quit IRC15:59
*** dkranz has joined #openstack-meeting16:00
n0anohk_peter, no problem, your english is fine (I dealt with much worse :-)16:01
*** sushils has quit IRC16:01
hk_peternova guys, when is the next meeting? where i can find the meeting schedule?16:02
primeministerp#startmeeting hyper-v16:02
openstackMeeting started Tue Jul 30 16:02:26 2013 UTC and is due to finish in 60 minutes.  The chair is primeministerp. Information about MeetBot at http://wiki.debian.org/MeetBot.16:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:02
*** openstack changes topic to " (Meeting topic: hyper-v)"16:02
openstackThe meeting name has been set to 'hyper_v'16:02
primeministerphi guy16:02
*** zehicle_at_dell has joined #openstack-meeting16:03
primeministerpzehicle_at_dell: hi rob16:03
pnavarrohi primeministerp16:03
alexpilottihi guys16:03
primeministerphey pedro16:03
pnavarrohi everybody !16:03
primeministerphey luis16:04
primeministerpwe have quorum16:04
*** sushils has joined #openstack-meeting16:04
primeministerplet's begin16:04
*** openstack changes topic to " (Meeting topic: hyper-v)"16:04
primeministerp#topic new patches16:04
*** openstack changes topic to "new patches (Meeting topic: hyper-v)"16:04
primeministerpI know alex has been hard at work16:05
primeministerpbunch of patch have submitted for wmi v216:05
primeministerpand vhdx is on the way16:05
primeministerpalexpilotti: any additoinal comments, on that16:05
schwichthi everyone!16:05
alexpilotti#link https://review.openstack.org/#/c/39195/16:05
primeministerpschwicht: hello frank16:06
alexpilotti#link https://review.openstack.org/#/c/39194/16:06
alexpilotti#link https://review.openstack.org/#/c/39164/16:06
*** sarob has joined #openstack-meeting16:06
alexpilotti#link https://review.openstack.org/#/c/38160/16:06
alexpilotti#link https://review.openstack.org/#/c/38791/16:06
alexpilottiplus we have a bug fix that got merged16:07
alexpilotti#link https://bugs.launchpad.net/nova/+bug/120305916:07
uvirtbotLaunchpad bug 1203059 in nova "Hyper-V versions before 2012 are not properly recognized" [Undecided,Fix committed]16:07
primeministerpalexpilotti: thank for the infomation16:07
pnavarrofrom my side, nothing new, I'd like to start coding this week16:07
alexpilottiI'm trying to back port it to Grizzly as well16:07
alexpilottiVHDX is on the way16:07
zehicle_at_dellwhat version(s) of HyperV are being targeted?16:08
alexpilottiwe have to fix the tests and it's ready for review16:08
primeministerpzehicle_at_dell: 2012 up16:08
zehicle_at_dellkk, thanks for confirming16:08
*** jgallard has quit IRC16:08
*** mrodden has quit IRC16:08
schwicht(I assume that is becaise of WMI v2?)16:08
alexpilotti2012 R2 does not have V116:09
alexpilottialso we needed V2 for VHDX and other stuff introduced in 201216:09
schwichtyep we need to look forward16:09
*** lexinator has joined #openstack-meeting16:10
primeministerppnavarro: do you have any updates on the cinder works16:10
pnavarrono, I'd like to start this week16:10
*** hanrahat has joined #openstack-meeting16:10
primeministerppnavarro: ok16:10
primeministerppnavarro: keep us posted on your progress16:10
pnavarrosure !16:11
*** matiu_ is now known as matiu16:11
primeministerppnavarro: are you still interested in ephermal storage?16:11
*** resker has joined #openstack-meeting16:12
*** marun has joined #openstack-meeting16:12
primeministerppnavarro: will you have time to do work on the ephermal storage as well?16:12
pnavarrowell, I shouldn't be very difficult..16:13
pnavarroI'd like to try16:13
primeministerppnavarro: ok, we want to get in for sept, let us know if you need help16:14
pnavarroperfect, thanks !16:14
*** hk_peter has quit IRC16:14
alexpilottipnavarro: tx!16:14
*** diogogmt has joined #openstack-meeting16:15
primeministerpare we good on active development bits?16:15
*** esker has quit IRC16:15
primeministerp#topic summit sessions16:15
*** openstack changes topic to "summit sessions (Meeting topic: hyper-v)"16:15
primeministerpthe summit deadline was I belive friday16:16
primeministerphopefully everyone got thier sessions in16:16
primeministerpwho was planning on giving one16:16
primeministerpI know alexpilotti has submitted 2 sessions16:16
primeministerpand I also submitted 2 sessions16:17
*** hemna has joined #openstack-meeting16:17
alexpilottiyep, one workshop on windows + cloudbase-init, all possible deployments16:17
primeministerpso first question to the group are any of the other hyper-v folks planning on attending the summit?16:17
alexpilottiand an entry level one, on CentOS + RDO + Hyper-V16:17
alexpilotti(see latest blog post)16:17
zehicle_at_dellwe're talking about it - ours are still going through the corporate machine16:17
primeministerpok good16:18
primeministerpI haven't booked anything yet16:18
primeministerpbut need to16:18
zehicle_at_dellDell will have a small team (5 engineers - if you count me)16:18
primeministerpI know others have16:18
primeministerpbooked already16:18
alexpilottizehicle_at_dell: let me know if you'd like us to join you on stage for a Crowbar / Hyper-V demo :-)16:18
pnavarroI'm planning to attend too16:18
zehicle_at_dellI believe SUSE too16:18
primeministerppnavarro: execellent!16:18
zehicle_at_dellalexpilotti: thinking......16:18
*** IlyaE has quit IRC16:18
zehicle_at_dellyes ;)16:19
alexpilottiyeiii :-)16:19
primeministerpso looks like there will be a good group16:19
primeministerpzehicle_at_dell: I like the idea of that16:19
*** eharney has joined #openstack-meeting16:20
primeministerpluis_fdez: who's attending from the CERN camp?16:20
zehicle_at_dellwanted to talk about CB demos when we get to that topic16:20
*** Mr_T has left #openstack-meeting16:20
luis_fdezJose and Belmiro are attending... and... I'm not sure if Jan or Tim16:20
primeministerpluis_fdez: gotcha16:20
*** vijendar has joined #openstack-meeting16:20
*** mrodden has joined #openstack-meeting16:21
primeministerpany other discussion for the summit16:21
zehicle_at_dellquestion on the target distro: I'm assuming Havana.  We're starting to work on Havana using pull-from-source in September16:21
primeministerpzehicle_at_dell: you can use grizzly16:21
*** cdub_ has joined #openstack-meeting16:21
zehicle_at_dellgood, that's what I'd like to be testing on right now16:22
zehicle_at_dellHavana will take some baking - could be interesting at the summit16:22
*** SergeyLukjanov has quit IRC16:23
primeministerp#topic puppet-openstack-hyper-v16:23
*** openstack changes topic to "puppet-openstack-hyper-v (Meeting topic: hyper-v)"16:23
primeministerpluis_fdez: so16:23
primeministerpluis_fdez: it's been a while since we've cought up16:23
*** glikson has quit IRC16:23
primeministerpluis_fdez: is that pull ready to be merged?16:23
primeministerpluis_fdez: you said wait in your comments16:23
luis_fdezyes, I think so... more testing is neede but it should work16:23
luis_fdezyes, I updated today16:23
primeministerpluis_fdez: ok perfect16:24
luis_fdezI'll work the rest of the week on the refactoring16:24
luis_fdeznext week I'll be out of the office16:24
primeministerpI'll be able to test it w/in the next couple days16:24
luis_fdezI'd to have the python environment polished and ready16:24
primeministerpluis_fdez: is the python part ready?16:24
*** stevemar has quit IRC16:24
*** bdpayne has joined #openstack-meeting16:25
luis_fdezwell, with this refactoring it should be ready16:25
*** jodom has joined #openstack-meeting16:25
luis_fdezit supports installing from exe, msi, pip...16:25
primeministerpluis_fdez: can you make sure there's a from source option16:25
primeministerpthat's part is coming16:25
primeministerpi'm getting some help16:25
zehicle_at_dellcan someone explan the python / puppet integration?16:25
*** cp16net is now known as cp16net|away16:26
primeministerpzehicle_at_dell: so16:26
primeministerpto install openstack16:26
primeministerpon hyper-v you need python16:26
primeministerpyou have a bunch of options on how to get that16:26
primeministerpif we use the public binaries16:26
primeministerpfrom the python community16:26
primeministerpfor the base msi16:26
primeministerpof python 2.716:26
primeministerpwe need to then16:26
zehicle_at_dellah, ok.  I get it.  it's about evironment prep.16:27
primeministerpwhen I did my last refactor16:27
primeministerpI had it auto pull everything from the web16:27
alexpilottizehicle_at_dell: it's very similar to how we do it in Crowbar16:27
primeministerpluis_fdez: is taking my brute force and cleaning it up to something more flexible16:27
*** jrodom has quit IRC16:27
zehicle_at_dellI'm familiar w/ the problem - it's a pain to solve16:27
zehicle_at_dellesp if you assume no route to the internet from the hosts admin network (which is what we assume)16:28
schwichtyou can have local pip sources ...16:28
luis_fdezyeps we want to allow the user specify the sources or pull it from the web16:29
zehicle_at_dellyy, that's what we do.  We have an approach for that (pull-from-source), but this is getting off topic16:29
zehicle_at_delldid not mean to derail us16:29
zehicle_at_dellgtr in 15 minutes16:30
*** krtaylor has joined #openstack-meeting16:30
*** willOchanda has joined #openstack-meeting16:32
*** markmcclain has joined #openstack-meeting16:32
primeministerpany thing else on the puppet side16:34
primeministerpluis_fdez: ?16:34
luis_fdezummm, no, that's all...16:34
primeministerpanyone else to go on?16:34
primeministerpanything else add?16:35
zehicle_at_dellI'm here16:35
primeministerpzehicle_at_dell: what's up16:36
primeministerpzehicle_at_dell: anything else from your side?16:36
zehicle_at_dellwanted to talk about setting up a CB HyperV demo w/ the cloudbase team16:36
primeministerpzehicle_at_dell: let's talk16:36
alexpilottizehicle_at_dell: sure16:36
primeministerpzehicle_at_dell: did you submit the session yet?  ;)16:36
zehicle_at_dellwas thinking to do it during the community CB design meeting next wed (8/7)16:37
zehicle_at_dellnot yet, but soon16:37
*** cp16net|away is now known as cp16net16:37
alexpilottizehicle_at_dell: do you have some sponsors sessions that you can submit after the 31th?16:38
zehicle_at_dellI've got two people from our OS team ready to test the CB-HyperV work on some servers - waiting for all the pulls to pass16:38
*** pentameter has joined #openstack-meeting16:38
zehicle_at_dellyes, we have 116:38
alexpilottizehicle_at_dell: ok, let me know how you want to handle it16:38
zehicle_at_dellI'll em you to set it up, the time is on the CB calendar (wed @ 10am central)16:39
zehicle_at_dellI'm excited to see the integration pulls accepted and start testing on physical gear16:40
*** ruhe has quit IRC16:40
zehicle_at_dellGrizzly btw16:40
zehicle_at_dellalexpilotti: I'll introduce you to the team16:41
alexpilottigreat, tx!16:41
zehicle_at_dellsince I'm expecting they will work directly w/ you16:41
alexpilottisounds good16:41
*** sushils has quit IRC16:41
zehicle_at_dellthat was my main topic - still recovering from OSCON16:42
primeministerpzehicle_at_dell: i pob should have put that on the list of confs16:42
primeministerpany other topics?16:42
primeministerpschwicht: ?16:42
primeministerpschwicht: anything to add?16:43
schwichtprimeministerp: not for today16:43
primeministerpok then16:43
primeministerpi'm calling it16:43
*** openstack changes topic to "OpenStack meetings || https://wiki.openstack.org/wiki/Meetings"16:43
openstackMeeting ended Tue Jul 30 16:43:21 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-07-30-16.02.html16:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-07-30-16.02.txt16:43
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-07-30-16.02.log.html16:43
alexpilottibye guys!16:43
*** neelashah has joined #openstack-meeting16:44
primeministerpthanks everyone16:44
*** IlyaE has joined #openstack-meeting16:44
*** hanrahat has quit IRC16:45
*** sushils has joined #openstack-meeting16:45
*** alexb_ has quit IRC16:47
*** zehicle_at_dell has quit IRC16:49
*** jlucci has quit IRC16:50
*** Yada has quit IRC16:50
*** SergeyLukjanov has joined #openstack-meeting16:51
*** emagana has quit IRC16:52
*** enikanorov has joined #openstack-meeting16:53
*** spzala has quit IRC16:53
*** enikanorov has quit IRC16:53
*** enikanorov has joined #openstack-meeting16:53
*** tjones has joined #openstack-meeting16:55
*** sdague has quit IRC16:56
*** ndipanov is now known as ndipanov_gone16:57
*** emagana has joined #openstack-meeting16:57
*** Yada has joined #openstack-meeting16:57
*** garyk has joined #openstack-meeting16:57
*** Yada has quit IRC16:57
*** sarob_ has joined #openstack-meeting16:57
*** tjones has left #openstack-meeting16:58
*** alexpilotti has quit IRC16:58
*** tjones has joined #openstack-meeting16:58
*** lexinator has quit IRC16:58
*** bismigalis has quit IRC16:58
*** jrodom has joined #openstack-meeting16:59
*** sarob has quit IRC17:00
*** sarob__ has joined #openstack-meeting17:00
*** sarob_ has quit IRC17:01
*** lexinator has joined #openstack-meeting17:02
*** gyee has joined #openstack-meeting17:02
*** jodom has quit IRC17:02
*** reed has joined #openstack-meeting17:03
*** jrodom has quit IRC17:03
*** jhenner has quit IRC17:04
*** tanisdl has quit IRC17:04
*** glikson has joined #openstack-meeting17:05
*** alexb_ has joined #openstack-meeting17:08
*** mrunge has joined #openstack-meeting17:09
*** tjones has left #openstack-meeting17:09
*** psedlak has quit IRC17:10
*** ruhe has joined #openstack-meeting17:11
*** sdague has joined #openstack-meeting17:13
*** jpich has joined #openstack-meeting17:15
*** SumitNaiksatam has quit IRC17:19
*** anniec has joined #openstack-meeting17:21
*** ruhe has quit IRC17:23
*** [1]glikson has joined #openstack-meeting17:24
*** epim has joined #openstack-meeting17:24
*** glikson has quit IRC17:25
*** [1]glikson is now known as glikson17:25
*** spzala has joined #openstack-meeting17:26
*** cdub_ has quit IRC17:27
*** markmcclain has quit IRC17:28
*** jrodom has joined #openstack-meeting17:29
*** sushils has quit IRC17:29
*** markwash_ has joined #openstack-meeting17:30
*** jodom has joined #openstack-meeting17:30
*** jrodom has quit IRC17:30
*** markmcclain has joined #openstack-meeting17:30
*** sdague has quit IRC17:32
*** danwent has quit IRC17:32
*** markwash has quit IRC17:32
*** markwash_ is now known as markwash17:32
*** nati_ueno has joined #openstack-meeting17:34
*** glikson has quit IRC17:35
*** sushils has joined #openstack-meeting17:36
*** danwent has joined #openstack-meeting17:36
*** sdague has joined #openstack-meeting17:36
*** glikson has joined #openstack-meeting17:36
*** Haneef has joined #openstack-meeting17:37
*** sdague has quit IRC17:41
*** sdague has joined #openstack-meeting17:42
*** johnthetubaguy has quit IRC17:43
*** sarob__ has quit IRC17:43
*** sarob has joined #openstack-meeting17:44
*** SumitNaiksatam has joined #openstack-meeting17:44
*** resker has quit IRC17:45
*** esker has joined #openstack-meeting17:46
*** vipul is now known as vipul-away17:46
*** johnpur has joined #openstack-meeting17:46
*** vijendar has quit IRC17:46
*** sarob has quit IRC17:48
*** vijendar has joined #openstack-meeting17:53
*** [1]fabio has joined #openstack-meeting17:55
*** benl has joined #openstack-meeting17:56
*** bknudson has joined #openstack-meeting17:57
*** sushils has quit IRC17:57
*** hk_peter has joined #openstack-meeting17:57
*** hk_peter has quit IRC17:57
*** henrynash has joined #openstack-meeting17:58
*** sarob has joined #openstack-meeting17:59
henrynash#meeting keystone18:00
ayoungdolphm is out this week, so I'll start it.18:00
*** [1]fabio is now known as fabiog18:00
ayounghenrynash, I think you want #startmeeting keystone18:00
ayounghenrynash, you want to run this one?18:00
henrynash#startmeeting keystone18:00
openstackMeeting started Tue Jul 30 18:00:58 2013 UTC and is due to finish in 60 minutes.  The chair is henrynash. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: keystone)"18:01
openstackThe meeting name has been set to 'keystone'18:01
*** sarob has quit IRC18:01
*** sarob has joined #openstack-meeting18:01
henrynashok, first off reminder that Havana m3 cut in Sept 4th18:01
ayoungall present and accounted for18:01
henrynash#info Havana m3 cut in Sept 4th18:01
*** sushils has joined #openstack-meeting18:02
*** hk_peter has joined #openstack-meeting18:02
henrynashis anyone working on a bp that ISN't already tagged as heading for m3 ?18:02
ayounghmm , I may be18:02
henrynash(i.e. they are expecting it to land for m3_18:02
bknudsonhenrynash: yes...18:02
ayoungmulti repos18:02
ayoung#link https://launchpad.net/keystone/+milestone/havana-318:02
*** koolhead17 has joined #openstack-meeting18:03
bknudson#link https://blueprints.launchpad.net/keystone/+spec/user-locale-api18:03
ayoung#link https://blueprints.launchpad.net/keystone/+spec/multiple-sql-migrate-repos18:03
henrynash#action all to make sure any bps they are planning for m3 are tagge as such18:03
ayounghenrynash, ^^ should be a prereq for any extensions going in that need sql schema updates\18:04
henrynashthat way, we'll have a good picture as we burn down18:04
bknudsonhenrynash: Is that something I do myself?18:04
*** sarob has quit IRC18:04
henrynashbknudson: as core, yes you can do that (Dolphm might change it…but you should set it)18:04
*** sarob has joined #openstack-meeting18:04
bknudsonhenrynash: that was easy18:05
henrynashayoung: re we targeting the sql migrate at Havana…thought i saw a discussion about it going to iceHouse?18:05
henrynashbknudson :-)18:05
* topol sql migrate seems scary18:05
morganfainbergayoung / henrynash: I'm going to write up an updated BP based upon my conversations w/ dolph about caching layer instead of the revocation-list caching18:06
morganfainberghenrynash / ayoung: this should be tagged for h318:06
bknudsoncaching revocation list makes sense since it doesn't change that much18:06
morganfainbergbknudson: the revocation-list caching will be implementing the same way.18:07
*** danwent_ has joined #openstack-meeting18:07
henrynashmorganfainberg: Ok, but get it in their quick so you can get comment….as the clock ticks down we'll not want too many new Bps flowing in18:07
*** danwent has quit IRC18:07
*** danwent_ is now known as danwent18:07
morganfainberghenrynash: i'll write it up today.18:07
henrynashayoung: back to migrate, so you are planning this for m3?18:07
topolmorganfainberg, no API changes required for that?18:07
henrynashmorganfainberg: thx18:07
gyeewe should fix migrate in m318:08
*** danwent has quit IRC18:08
morganfainbergtopol: no.  it'll be just caching on top of current driver/manager calls18:08
morganfainbergtopol: and config options to make it functional.18:08
topolmorganfainberg. cool. I look fwd to reading the BP18:08
morganfainbergtopol: nod.18:08
gyeemorganfainberg, you caching it at the driver level?18:08
ayounghenrynash, yes18:08
ayounghenrynash, migrtate should go in ASAP18:09
henrynashgyee: fix, as in fix anything we have broken?18:09
ayounghenrynash, the Alembic migration should wait until icehouse18:09
morganfainberggyee: there is a WIP that dolph put up as an example. it'll work a lot like that18:09
gyeehenrynash, we need to get migration straighten out ASAP18:09
ayoungmorganfainberg, you mean the one I did?18:09
topolbesides the Alembic migration what are you referring too?18:09
morganfainbergayoung: you did that and dolph posted it?18:09
henrynashgyee: are you referring to young's patch, or just tables we have mucked up18:09
ayoungtopol, migrations for extensions in their own repos18:10
gyeehenrynash, sorry, I mean migration for the extensions18:10
ayoungI'll post an example here in a second18:10
henrynashguee: Ok18:10
morganfainbergayoung: https://review.openstack.org/#/c/38866/18:10
morganfainbergusing dogpile.cache18:10
topolayoung, I remember you mentioning those. I thought they were tied to Alembic migration..18:10
gyeedogpile? w00t!18:10
morganfainberggyee:  :)18:10
henrynashok, so let's get the meeting back to an agenda!18:11
*** kpel has joined #openstack-meeting18:11
ayounghenrynash, I am referring to https://review.openstack.org/#/c/36731/18:11
morganfainbergyeah sorry.  didn't mean to derail.18:11
henrynashwe'll pick up discussion on the migrate items under high priority code reviews18:11
ayoungthe comments say it needs documentation18:11
morganfainbergthought i was jumpin in ontime for h3 ...18:11
bknudsonayoung: I'd like docs too, but can go in a separate commit.18:11
henrynash#topic HIgh priority bugs or immediate issues?18:12
*** openstack changes topic to "HIgh priority bugs or immediate issues? (Meeting topic: keystone)"18:12
henrynashanything hot?18:12
ayoungNo bugs marked as Critical18:12
*** marun has quit IRC18:12
bknudsonbuilds were broken by a dependency over the weekend but that's fixed.18:12
ayoungcan we change that Agenda item to "Critical Priority bugs" in the future?18:13
henrynashayoung: agreed…think we are Ok shape18:13
* topol maybe we can all go on that hawaii vacation for m3 like I suggested before...18:13
henrynash#action henrynash to change item to "Critical Priority bugs"18:13
*** [1]fabio has joined #openstack-meeting18:13
henrynashtopol: there's a plan...18:13
henrynash#topic Reducing the default token duration in support of abandoning token revocation18:14
*** openstack changes topic to "Reducing the default token duration in support of abandoning token revocation (Meeting topic: keystone)"18:14
*** brich1 has joined #openstack-meeting18:14
bknudsonwhat do we need to cache token revocations for if we have this?18:14
henrynashwho's item is this?18:14
topoldolphm, I believe18:14
henrynashtopol: I had a feeling someone would say that18:15
gyeeto 1 hour?18:15
topolHe wanted to start stress testing the idea of tokens expiring to see what breaks18:15
henrynash#link https://review.openstack.org/#/c/38672/18:15
topolI put a comment in that said, did you inform the other PTLs???18:15
*** glikson has quit IRC18:16
ayounghenrynash, I want to do that, but it is not in H3 time frame18:16
morganfainbergbknudson: we still need to cache, people can ask for longer tokens.18:16
*** fabiog has quit IRC18:16
morganfainbergand limiting the backend impact… is good.18:16
henrynashdo we expect it to break (I know if we set it to minutes it definitely breaks)18:16
*** [1]fabio is now known as fabiog18:16
topolmorganfainberg, but when you change the default and folks find out by surprise....18:17
ayoungany work flow that lasts longer than the token duration will break.18:17
henrynashayoung: yep18:17
morganfainbergtopol: right. don't surprise people ;18:17
bknudsonassuming you can't get another token18:17
ayoungBut a 1 hour token duration was too long to avoid the need for revocation, according to backlash from the community18:17
topolayoung, I thought folks were supposed to code such that they reauthenticate if the token expires... Not true???18:17
ayoungwe need something like this18:17
gyeeayoung, that's where to pluggable token providers come in handy, you can customize expiration base on account :)18:17
morganfainbergtopol: that was my understanding18:18
gyeejust saying18:18
ayoung#link https://blueprints.launchpad.net/keystone/+spec/delegation-workplans18:18
henrynashOk, sounds like need to circle back with dolphm on this one….to see how he plans to "experiment" with this.18:18
topolgyee, no. its a matter of correct expectations... Either we are allowed to assume folks can code properly to this or we need to back it out18:18
*** sarob has quit IRC18:18
ayoungthat way, you can say "use this trust or oauth request token to get the token you need whne you need it"18:18
*** jodom has quit IRC18:19
*** sarob has joined #openstack-meeting18:19
*** haomaiwang has joined #openstack-meeting18:19
bknudsonclients need to be able to handle tokens becoming invalid for other reasons already18:19
*** luis_fdez has quit IRC18:19
brich1topol: if you code such that you can re-authenticate, you risk leaving the "secret" (password) out in the clear where bad things can happen...18:19
gyeetopol, client behaves the same way, regardless of expiration policy18:19
topolif he other projects arent ready to handle this I need to change my vote...18:19
*** nachi_ has joined #openstack-meeting18:20
*** nachi has joined #openstack-meeting18:20
ayoungbrich1, that is why we have ecure delgation mechanisms now18:20
gyeeif token expires, get a new one18:20
ayoungecure -> secure18:20
*** luis_fdez has joined #openstack-meeting18:20
topolugg... forcing folks to adopt something new by changing a default that nows screws them is not how we should do this..18:20
henrynash#action dolphm to explain approach to rolling this out and discussion with other projects18:20
ayoungtopol, they will just change it back in the puppet module anyway18:21
* topol need to go change my vote18:21
henrynash#topic High priority code reviews18:21
*** openstack changes topic to "High priority code reviews (Meeting topic: keystone)"18:21
gyeetopol, if client code is so depended on the default expiration, something is fundamentally wrong18:21
ayoungClient reviews!18:21
henrynashok, so what's in most need of pushing ahead18:21
topolayoung, yeah after getting pissed off at us18:21
*** danwent has joined #openstack-meeting18:21
ayoungAs jamielennox's daytime voice, I need to push people to do more client reviews18:21
ayoungfear not the client18:22
bknudsonthose client reviews are always so scary because everybody seems to want to rewrite it.18:22
*** IlyaE has quit IRC18:22
henrynashayoung: ok, so migration,18:22
ayoungI have a WIP to show18:22
ayoung#link https://review.openstack.org/#/c/39351/18:22
ayoungthis is based on simo'18:22
ayoungs kds patch18:23
*** kebray has quit IRC18:23
topolgyee, either we have a plan for success for our stakeholders for using shorter token expiration or we dont. sounds like we dont18:23
*** afazekas has quit IRC18:23
ayoungtopol, Icehouse18:23
*** ociuhandu has quit IRC18:23
topolayoung, K. then change default *in icehouse*18:23
*** sarob has quit IRC18:23
gyeetopol, I am more worried on other issues, like performance18:24
*** stevemar has joined #openstack-meeting18:24
ayoungon migrations, the question is whether I should contineu on with the sql migrations as is, or wshould we do the alembic move before we split out the extension repos18:24
ayoungI think that Alembic support is going to require some thinking18:24
henrynashtopol, gyee: have set action for dolphm to come back with the plan….let's move on18:24
morganfainbergayoung: i am for doing the migration work now.18:24
ayoungand I don't really want to force that through18:24
henrynashayoung: agred18:24
*** stevemar has quit IRC18:24
ayoungmorganfainberg, I do to18:24
topolayoung, avoid death or glory. go crawl walk run18:24
morganfainbergand hit alembric in Icehouce18:24
topolmorganfainberg +118:24
ayoungdolph had the objection, so if we drive on, we have to be ready to convince him when he comes back.  Do we have unanimous support for it?18:25
topolsupport for doing it in stages???18:25
*** otherwiseguy has quit IRC18:25
bknudsonI think his problem was that we now have to do alembic on multiple repos18:25
henrynashayoung: I'd just like clarification of how a "complex" extension work work with a separate repo?18:25
ayoungtopol, for doign the migrations per extension in the existing technology18:25
ayounghenrynash, see the above link18:25
topolayoung, yes that to me means stages.  Unless thatmakes alembic 10 times harder later...18:26
ayounghenrynash, the short of it is you need a migrate_repo subdir, a versions subdir under that, a config file, and a couple empty __init__.puy files18:26
gyeeayoung, is alembic required for separating out the extension migration?18:26
henrynashayoung: so I posted a question on patch 11 to this end18:26
bknudsonif we have multiple repos and have alembic, we have to decide how we're going to do the sqlalchemy -> alembic change.18:26
ayounghenrynash, yep,. just got to the point that I had one to show, and I will convert that to documentation in both the commit message and in the doc dir18:26
*** vipul-away is now known as vipul18:27
ayoungbknudson, we need to do that anyway, and I think the migration will be no more complex with or without the split18:27
ayounggyee, alembic is not required18:27
gyeeayoung, I would vote for getting the extension migration done first18:28
bknudsonayoung: ok, I don't know how the sqlalchemy -> alembic migration works. Other projects always have a point where they consolidate migrations18:28
henrynashayoung: my question is much more fundamental…my initial reaction is that complex extensions will no long rbe possible since we won't have the DB changes sequenced with core…any sometimes I think you need to….so I am yet to be convinced over the whole approach18:28
ayounggyee, doing alembic support after the split means that we will have to deal with multiple migrate repos in the conversion, but that should be only slightly more complex than what we are doing now18:28
bknudsonbut keystone hasn't done that (consolidation)18:28
*** atiwari has joined #openstack-meeting18:28
ayounghenrynash, if an extension needs to talk to the db, and change the core schema, it  can still do that in common18:28
ayoungwe just should not allow that in a review with out serious justification18:28
*** stevemar has joined #openstack-meeting18:28
henrynashayoung: I'd suggest we need a better BP that explains what will and won't be possible…like before we start coding it18:28
*** marun has joined #openstack-meeting18:29
*** Guest26298 has quit IRC18:29
*** dianefleming has quit IRC18:29
*** Fdot_ has joined #openstack-meeting18:29
ayounghenrynash, extension , by definition, are defined to be split out from the main keystone server.  I don't want any more extesnions going in until we resolve this18:30
morganfainbergayoung:  +118:30
*** IlyaE has joined #openstack-meeting18:30
ayounghenrynash, credentials should have had its own repo, hell, Identity and token stuff should be in their own repos18:30
ayoungcatalog and policy should certainly be in their own repos, too18:30
gyeeayoung, amen brother18:30
*** sarob has joined #openstack-meeting18:31
ayoungSo, henrynash do you really think an extension should be allowed to communicate with the underlying sql schema?18:31
*** linggao has joined #openstack-meeting18:31
henrynashayoung: so i get those suggestions….I thought the primary point of an extension was to allow API changes that we are not necessarily committing to support long ter,18:32
gyeeayoung, you sure you didn't work on OSGi before?18:32
gyeehenrynash, having sql-specific schema dependencies is pretty messy18:33
gyeeespecially we are supporting different backend drivers18:33
ayounggyee, I've worked on everything before18:33
henrynashayoung: I (think what I ) am advocating is that often an extension might need to change a core schema.  The schema change might be done in core (and not part of the extension) as long as it is benign….but "private" sql extension changes would be in their own repo18:33
morganfainberggyee: yes, it makes sense especially with the pluggable nature/mutiple backends.18:34
ayounghenrynash, I would argue that if you are modifying a set of tables, all the changes to those should be in a single repo.  Extensions *can* and *should* have their own sql repos, but because some extensions are already munged into the common repo, we can't make that a *must* at least not yet18:34
henrynashayoung: otherwise I don't see how our dependencies will work, we'll break extensions at the drop of a hat18:34
*** hk_peter has quit IRC18:34
ayounghenrynash, so, the rule is "no new extension that requires a new sql schema goes into the common repo"18:35
*** Fdot has quit IRC18:35
bknudsonhenrynash: we should have unit tests to ensure extensions work18:35
gyeebknudson, at the minimal18:35
ayoungbknudson, and those will be part of the sql upgrade test with that extensions patch18:35
bknudsonand we need a real sql in the gate18:36
henrynashayoung: so I'm not arguing that should not be able to have a repo….I'm just skeptical it is the right solution for all extension (in the future) to be wholly contained within their repo18:36
morganfainbergyes, real SQL in gate (or something that emulates it cleanly) is important.18:36
*** armax has joined #openstack-meeting18:36
*** jrodom has joined #openstack-meeting18:37
*** koolhead17 has quit IRC18:37
ayounghenrynash, it is a code standard, but one that we can address when the time comes.  For example, the ec2 extensions are currently based on code in the common repo.  THat won't be broken by this18:37
topoldo we expect to have enough extensions in the future to merit supporting multiple repos?18:37
ayounghenrynash, it just provides a missing mechanism18:37
ayoungtopol, yes18:37
ayoungtopol, 3 have 3 right now18:37
topoleverybody loves adding to our database...18:38
gyeeayoung, don't forget endpoint filtering18:38
henrynashayoung: and that's my point, I don't see where we have planned out how different types of extensions will work….I really want to see it described how the dependencies will work, be obvious to those working on core etc.18:38
bknudsonso today an extension can't really count on the identity sql, since identity could be ldap.18:38
ayounggyee, make that four18:38
ayoungbknudson, right18:38
gyeepho for pho!18:38
henrynashayoung: you probably have it all worked out….I just need to be able read it and think through how it would work in practice18:39
ayounghenrynash, fair enough.18:39
ayoung#action ayoung to properly document split repos as part of the patch18:39
henrynashayoung: if you could do that, it would be great18:39
henrynashOk, other high priority code reviews18:39
bknudsonone thing we might need is a more extensible way to notify extensions of events.18:40
bknudsonmore comprehensive might be a better word18:40
*** stevemar has quit IRC18:40
gyeebknudson, can you translate that in plain english?18:40
henrynashbknudson:  do we ahem any way implemented today?  I didn't think so?18:40
ayoungbknudson, that statement scares me18:41
bknudsonmore of a thought, but you use foreign keys for example to delete rows from a table when the user goes away.18:41
* topol plz be thinkijng of something lightweight :-)18:41
bknudsonand now we don't have foreign keys for that.18:41
bknudsonso some way to tell an extension that the user has gone away and it should clean up.18:41
ayoungbknudson, LDAP does not notify anyway18:42
*** marun has quit IRC18:42
ayoungusers never "go away"18:42
ayoungnow, projects, OTOH,18:42
bknudsonusers was an example... not sure if there's another one.18:42
ayoungroles get removed, and tokens get revoked18:42
ayoungintegration happens at the component to component level18:42
topoldoes openstack have a common event listening mechanism?18:43
bknudsonwe've got a discussion of notifications later on the agenda already.18:43
gyeebknudson, you thinking of an internal message queue or something?18:43
ayoungwirth extensions, we should try to keep integration to a minimum.  Ideally, different extensjhions should be able to run on different servers, and Keystone can then just act as a n incubatoer for new services with them all living in a single server18:43
*** marun has joined #openstack-meeting18:43
bknudsongyee: yes, it could be through an internal mechanism to register for events.18:44
*** mrunge has quit IRC18:44
*** kmartin has quit IRC18:44
henrynashbknudson: Ok, think we need to table that topic, to make sure we get through the agent - maybe add it to next week?18:44
topolanyway we can avoid not invented here and rolling our own for this???18:44
henrynashany other high priority reviews?18:44
henrynashprobably a bit early in the cycle18:45
ayoungImplement apiclient library18:45
henrynashayoung: ahh!18:45
henrynashayoung: indeed18:45
*** doron has joined #openstack-meeting18:45
ayoungwe need to solve the common authentication mechanism problem18:45
bknudsonit's only 3000 lines18:45
bknudsonseems like common authentication mech wouldn't take 3k loc18:46
topolwith lots of -1s to boot18:46
ayoungagreed, so what do we do about moving this ahead?18:46
ayoungI think we need to work with him18:46
ayoungbut scope down this into multiple, independent blueprints18:46
ayoungwith auth being the highest priority18:46
morganfainbergayoung: +118:46
bknudsonayoung: +118:46
gyeeayoung +118:46
henrynashayoung: are any clients "signed up" to use such a think…or is it that if build (we hope) they shall come?18:47
*** edmund has joined #openstack-meeting18:47
topoldoes ti have stakeholders lined up? Will folks jump to this once its avail or say, what I have works... leave me alone?18:47
bknudsonso novaclient already has this plugin mechanism18:47
ayounghenrynash, I think cinder already pullins the keystone client18:47
ayoungI know at least one client does,18:47
henrynashayoung:I think that is true, yes18:47
ayounghenrynash, it is in cinder's pip-requires but not in python-cinderclient18:48
ayoungglance has it , though18:49
henrynashayoung: ahh. that might be just that it wants the middleware18:49
*** stevemar has joined #openstack-meeting18:49
bknudsonall the clients will need keystoneclient to get a token18:50
ayoungbknudson, they do direct calls right now18:50
topolthe safe thing to do would be to confirm what the stakeholders really need in this space, that they are willing to move to the new code base and to make sure the 3000 lines are trimmed down to deliver only what the stakeholders need.  could waste a lot of time if not real agile dvelopment is used on this one18:50
bknudsonayoung: oh, so we've got some work ahead of us!18:51
*** epim has quit IRC18:51
ayoungbknudson, so we want them to consume the python-keystoneclient in order to manage how the authenticate both when they get a token and when they pass that token to aremote service, assuming the remote services can handle SPNEGO or CLient certs.  Down the road of course18:51
henrynash#action cores (at least) to take some the to work on this issue this week…..18:51
ayoungbknudson, yeah, I would say so, and it is going to take some joint engagement.  Thus, the first challenge to the core devs is to get comfortable with the client code, and get a common vision of how it should look and work.18:52
henrynashwe need to make progress or we still won't have a v3 nova client by Havana ship18:52
henrynashv3 auth18:52
gyeehenrynash, who's working on this?18:52
ayoungWe need to work with the other projects to up the minimum version, too18:52
gyeeayoung, what kind of help you need from on this front?18:53
ayoungwe should be able to use the latest keystone client in all projects18:53
topolayoung, +1 and if not to understand why not18:53
ayounggyee, jamielennox has been working on it18:53
henrynashyoung, guee: so I raised this at the project meetinga few weeks ago (when deputising for Dolphm) and the reaction was…use the mailing list!18:53
ayounghenrynash, or submit patches18:53
gyeehenrynash, yup18:54
henrynashayoung: always better18:54
gyeejust do it18:54
henrynashyoung, gyee: ..and I coming round to thinking that this is what we must do18:54
gyeehenrynash, yes, we'll have to write the code18:54
*** kebray has joined #openstack-meeting18:55
*** pabelanger has joined #openstack-meeting18:55
henrynashgyee, ayoung, bknudson: let's chat after the meeting on this one18:55
bknudsonhenrynash: ok18:55
henrynash#topic Oslo unified logging patch landing soon? (https://review.openstack.org/#/c/34834/)18:55
*** openstack changes topic to "Oslo unified logging patch landing soon? (https://review.openstack.org/#/c/34834/) (Meeting topic: keystone)"18:55
*** Mandell has joined #openstack-meeting18:55
lbragstad#link https://review.openstack.org/#/c/34834/18:55
topolgyee, plz find a stakeholder from each project that needs to adopt.  My rule of thumb would be if you cant get a stakeholder its a recipe for a waste of time..18:55
ayounghenrynash, I'll OK the approach once we are certain it doens't mess up apache18:56
*** koolhead17 has joined #openstack-meeting18:56
*** koolhead17 has joined #openstack-meeting18:56
lbragstadhoping that this lands soon, and this change was purposed for keystone a while ago to implement a unified logging solution but concerns were raised about eventlet18:56
gyeetopol, sure, make sense18:56
lbragstadjust wanted to give everyone a heads up on this, and once it lands in Oslo I'll plan to implement the unified logging solution to keystone18:56
bknudsonso do we want to wait for the oslo change before we get notifications or stick with where we were before?18:56
ayoungbknudson, does it require changes to the config file?18:57
*** jrodom has quit IRC18:57
henrynashlbragstad: and the question of apache?18:57
ayoungIf so, that breaks the feature freeze rule.  Otherwise, I am OK with it going in to H3.18:57
lbragstadjsut about to test it in apache.18:57
lbragstadhenrynash: ^18:57
bknudsonayoung: do notifications require changes to the config file? I'm sure there's config options to tell it what notifier to use.18:57
ayounglbragstad, can you file that as an Agenda item for next week, then, to make sure we close it on out?18:58
lbragstadayoung: bknudson^18:58
*** glikson has joined #openstack-meeting18:58
ayoungbknudson, optional changes are OK18:58
lbragstad#link http://docs.openstack.org/trunk/openstack-network/admin/content/ch_adv_notification_overview.html18:58
ayoungbknudson, required changes are not18:58
henrynashayoung: I didn't think changes to config file where verboten…just that we can't break anything that is in there already18:58
bknudsonright, it has to have a sensible default.18:58
*** ruhe has joined #openstack-meeting18:58
*** markmcclain has quit IRC18:58
ayounghenrynash, think of it as an integration problem.  API's are fixed to keep from breaking iother apps.  Config files are fixed to keep from breaking the puppet modules and installers18:59
bknudsonpeople are going to think we're on vaca in Hawaii if we don't make work by breaking other apps.18:59
ayoung1 minute remaining18:59
fabioghenrynash, endpoint filter is ready for review18:59
ayoungfabiog, add me to the review, please19:00
henrynashayoung: hmm, agree we can't change existing values…take offline19:00
fabiog#link https://review.openstack.org/#/c/33118/19:00
henrynash#topoc open discussion !19:00
fabiogayoung, added19:00
henrynashbut we are out of time!19:00
topolfabiog, dolph has a red x on it. why would we review???19:00
*** openstack changes topic to "OpenStack meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Tue Jul 30 19:00:54 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-07-30-18.00.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-07-30-18.00.txt19:00
fabiogtopol, he had it because he wanted the extension implemented19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-07-30-18.00.log.html19:01
fabiogand now it is compliant to that19:01
*** brich1 has left #openstack-meeting19:01
topolfabiog ok19:01
jeblairare infra people around?19:01
clarkbhey there19:01
*** IlyaE has quit IRC19:02
*** fabiog has quit IRC19:02
jeblair#startmeeting infra19:02
openstackMeeting started Tue Jul 30 19:02:47 2013 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
*** openstack changes topic to " (Meeting topic: infra)"19:02
openstackThe meeting name has been set to 'infra'19:02
jeblair"and is due to finish in 60 minutes" ! neato :)19:02
fungitoo cool19:03
jeblair#topic asterisk server19:03
*** openstack changes topic to "asterisk server (Meeting topic: infra)"19:03
jeblairmost of the topics from last meeting were around the asterisk server anyway...19:03
*** vipul is now known as vipul-away19:03
*** vipul-away is now known as vipul19:03
jeblairincluding that i signed up for a DID, so it has a phone number now...19:03
* mordred bows down to the new asterisk server overlord19:03
* fungi missed the last meeting19:03
*** slavayssiere has quit IRC19:04
* fungi forgot to see what got assigned to him in absentia19:04
jeblairfungi: i don't think you did; at least based on irc logs19:04
jeblairit looks like there was no meeting last week19:04
*** BStokes has quit IRC19:04
jeblairpabelanger, russellb: should we all dial in?19:04
*** markmcclain has joined #openstack-meeting19:04
jeblairto see if we can stress test the conf server a bit?19:04
russellbjeblair: sure19:04
pabelangershould be able too19:05
* fungi has a telegraph^H^H^H^H^Hphone handy19:05
*** IlyaE has joined #openstack-meeting19:05
russellbpabelanger: going to use g722?19:05
clarkbI will need a real number as android's clients are derpy and I am still without a proper headset19:05
jeblairthere's that, and the phone number is 512-808-575019:05
pabelangerno, was going to use DID19:05
russellbi'll probably just use the DID as well ...19:05
pabelangerrussellb: no client19:06
russellbi have a client, but i like my desk phone more, heh19:06
fungiconference id number?19:06
pabelangerasterisk CLI looks good19:06
*** doron is now known as doron_afk19:06
*** stevemar has quit IRC19:06
*** rnirmal has quit IRC19:07
russellb6 people on19:07
*** rnirmal has joined #openstack-meeting19:07
*** otherwiseguy has joined #openstack-meeting19:07
pabelangerload is nothing19:07
*** egallen has quit IRC19:08
anteayaI can get on with skype and the phone number19:08
pabelangerconfbridge list19:09
anteayausing the sip client, Jitsi still fails for me19:09
pabelangeranteaya: likely a codec issue19:09
anteayapabelanger: probably19:09
*** rnirmal has quit IRC19:09
russellbjeblair: *CLI> core show channels ... shows all channels as calls from the SIP provider19:09
*** rnirmal has joined #openstack-meeting19:10
anteayayes a little choppy for me too19:10
mordredcell phone19:11
anteayaI am just listening, not transmitting19:11
*** changbl has quit IRC19:12
anteayawho was that?19:12
russellbpbx*CLI> channel originate Local/6000@public application playback spam19:13
jeblairi have silence now...19:14
clarkbjeblair: we are still talking19:14
*** sarob has quit IRC19:14
fungisilence huh?19:14
fungiwe have more callspam19:15
*** glikson has quit IRC19:15
pabelangerCPU is spiking, so we'd need to see why19:15
*** sarob has joined #openstack-meeting19:15
russellbshe will say anything.19:15
russellbalmost anything.19:15
anteayaha ha ha19:15
pabelangertt-monkeys FTW19:15
*** novas0x2a|laptop has joined #openstack-meeting19:17
anteayajust with the small group, the sound is about equivalent to one of the board meeting conference calls, as a listener19:18
anteayafungi has good sound19:18
* ttx lurks19:18
* mordred waves at ttx19:18
*** danwent has quit IRC19:18
mordredttx: you want to dial in from france?19:18
*** vipul is now known as vipul-away19:18
* mordred got dropped19:18
ttxmordred: i'll pass, unless you REALLY need that tested19:19
anteayaskype is charging me money to listen in19:19
* ttx multitasks19:19
anteayaso far I have paid 40 cents19:19
jeblairttx: not yet; i think we'd get a local number later19:19
*** sarob has quit IRC19:20
*** changbl has joined #openstack-meeting19:21
jeblair#action clarkb add pbx to cacti19:21
davidlenwellwhat is the conf number ?19:21
anteayathat actually was quite good19:21
jeblairwe all just hung up19:21
davidlenwelloh .. too late19:21
anteayawe just ended the session19:21
*** willOchanda has quit IRC19:21
jd__what? are we having a party on the phone or something?19:21
* jd__ hides19:22
davidlenwelljd__:  we missed it19:22
fungiwe can try to bum-rush it again next week once we have it in cacti to see what the impact is19:22
russellbi documented it!19:22
pabelangeryou could totally hook the meeting room bot into asterisk too, once the meeting start, a new conference room is create and password outputted19:22
pabelangerdon't think that would be too hard19:22
*** Fdot_ has quit IRC19:22
jeblairneat :)19:22
russellbpabelanger: it's only software19:22
ttxrussellb: "on his spare time, the hero of cloud computing sets up asterisk"19:22
*** epim has joined #openstack-meeting19:22
russellbttx: heh19:23
fungittx: like you're one to talk, writing your own bug tracker19:23
ttxrussellb: not jealous at all.19:23
pabelangerrussellb: would be a fun integration19:23
*** IlyaE has quit IRC19:23
jeblairso i think next we want to get a handle on resource usage there... fwiw asterisk is currently almost idle now that we've hung up.19:24
*** gyee has quit IRC19:24
jeblairso i'm guessing the high cpu usage is related to our call19:24
clarkbI think fail2ban is probably a reasonable thing to try as well19:24
clarkbit will act as a rate limiter for badness19:24
anteayaor spammers just target us when there is something going on19:24
jeblairshall we move on?19:25
*** danwent has joined #openstack-meeting19:25
russellbthere was no spam while we were on the call fwiw19:25
russellbso it was just conference related19:25
pabelangerjeblair: yes.  Transcoding was the hit19:25
pabelangerbut I wouldn't expect it to be spiking19:26
russellbpabelanger: dangit, should have looked to see what codecs were being used ...19:26
pabelangerya, I was trying to see that19:26
pabelangerI think I seen some gsm with ulaw19:26
russellbthey were all from the provider, so i can just call back and check19:26
russellbulaw (which is good)19:27
russellbk, can move on19:27
pabelangermight just be confbridge19:27
fungitoo attractive to spend the whole hour on a phone system ;)19:27
jeblair#topic multiple jenkins masters19:27
*** openstack changes topic to "multiple jenkins masters (Meeting topic: infra)"19:27
jeblairthe multi-step process to get to the point where we can have multiple masters is almost complete...19:28
jeblairwe just need to do something to ensure that the bitrot jobs only run one place (and also that their logs are correctly processed)19:28
zarodo we also need this? https://bugs.launchpad.net/openstack-ci/+bug/108280319:29
uvirtbotLaunchpad bug 1082803 in openstack-ci "Manage jenkins global config and plugin list" [Medium,Triaged]19:29
jeblairto that end, I think i can have a working timer trigger for zuul today, which means zuul/gearman can dispatch those jobs, and we can stop using the jenkins timer triggers for them19:29
clarkbjeblair: reviewing your multiple triggers zuul change is on my list of things to do once we are done with bugs19:29
jeblairzaro: that would be nice, but i think i will defer it for now...19:29
jeblairbecause i'd like to have multiple masters within a few days (or weeks at the most)19:29
clarkbjeblair: I agree. There is a pressing need for multiple masters which we can manage by hand until we have the automagic to do it with tools19:30
fungiespecially since multiple will initially be just two19:30
funginot counting the old one19:30
jeblairi believe we're hitting performance problems related to the rate at which we are adding/removing slaves from jenkins for the devstack tests19:30
jeblairso being able to scale that up is the motivating factor for this19:30
clarkbjeblair: yes, the slave launch logs indicate it is taking up to a minute to add each slave19:31
fungithat certainly sounds like the sort of unusual use case the jenkins devs wouldn't have optimized for19:31
clarkbwhich is really really slow19:31
jeblairafter we have multiple masters, i plan on looking at more efficient and reliable ways of managing slaves.19:31
*** IlyaE has joined #openstack-meeting19:31
zarothat is awsome.  i am talking about the gearman-plugin at this year's jenkins conf. will having something good to show!19:31
jeblairzaro: cool!19:32
jeblairwhen is that?19:32
zarooct 23-2419:32
zarowant to come down?19:32
mordredjeblair: on the efficient and reliable ways of managing slaves - I'd love to chat about that once you're there19:32
zaroit's in palo alto.19:33
jeblairmordred: my thoughts so far are that d-g should be a daemon instead of a bunch of jenkins jobs, and that gearman-plugin should (optionally) handle offlining slaves when jobs are done (since it's in a good place to do that)19:33
mordredah yes. that. totally with you19:33
jeblairmordred: the daemon will be able to manage the nova boots in a better way.  we may still have bottlenecks adding and removing slaves...19:34
jeblairhowevever, we'll have a better handle on that in that we'll be able to tune how many api calls happen in parallel, etc...19:34
jeblairalso, we won't be making all these api calls at the same time jenkins itself is managing 16 running jobs (which are making the api calls)19:35
mordred_after_ that, clarkb and I were supposing about kexec re-purposing of slaves, so that there would be less adds/removes19:35
clarkbusing a daemon will definitely make a lot of pain points less insane19:35
mordredbut I agree that tuning what we have first19:35
mordredwill let us grok the other things sanely19:35
jeblairah yeah, that could be cool.  the only thing about that is that i don't think we can count on always doing that19:35
jeblairsome jobs will completely break the node and it will need to be destroyed and replaced19:36
jeblairbut 90% of them may be able to be reused, which could be a huge win19:36
clarkbjeblair: yup19:36
clarkbjeblair: and a daemon should be smart enough to know when it can and cant make use of kexec19:36
jeblairthat could be the normal case, and then if we fail to kexec after a minute or two, we kill it and let, say, a hypothetical future low-watermark load based system decide that it needs to replinish the pool.19:37
mordredjeblair: yup. and a hung-kexec probably will not respond to health pings :)19:37
jeblair(and hopefully, we can apply a bunch of this to the regular nodes too)19:37
clarkbthat would be amazing19:38
fungisounds great19:38
*** linggao has left #openstack-meeting19:38
jeblaircool, sounds like we have general consensus on a very long road ahead :)19:39
*** markmcclain has quit IRC19:39
jeblair#topic requirements and mirrors19:39
*** openstack changes topic to "requirements and mirrors (Meeting topic: infra)"19:39
jeblairmordred: you want to talk about about what's going on in this area?19:39
mordrednot really19:39
mordredcan I just close my eyes and make it go away?19:39
mordredso ... there are several issues19:39
*** diogogmt has quit IRC19:39
jeblair(it's worth a shot)19:40
mordredone is that pip installs things not in a dependency graph order19:40
mordredbut in a strange combo of first takes precedence and sometimes highest takes precedence19:40
*** kpel has quit IRC19:41
mordredwhich makes things gigantically problematic for devstack when things change, because sequencing will cause not what you expected to be installed19:41
clarkbI did open a bug against this problem with upstream pip dstufft thought it may be fixed in 1.519:41
mordredcurrent things on tap to fix this19:41
clarkbbut that doesn't help us today19:41
mordredsdague and I are working on getting the requirements update.py script in good shape19:41
mordredwith the idea that in setup_develop in devstack19:41
mordredthe first step will be to run the update.py script from requirements on the repo to be setup_develop'd19:42
sdagueyes, we're close, except for the fact that update.py doesn't handle oslo tarball urls19:42
mordredthis will ensure a consistent worldview of which packages should be installed19:42
sdagueI think that's actually the only missing piece19:42
clarkb#link https://github.com/pypa/pip/issues/988 there is apparently some undocumented feature that may be useful in mitigating this19:42
mordredsdague: grab most recent trunk - I think that's fixed now19:42
sdaguemordred: really?19:42
sdagueif so I can kick my devstack job again19:42
jeblairmordred: setup_develop sounds like a good idea19:43
mordredthen - once that's happening, we should be able to gate requirements on devstack running with requirements19:43
mordredso we can know if a new req will bork devstack19:43
mordredand then, with the two of those in place, we sohuld be in good shape to auto-propose patches to projects on requirements changes landing19:43
mordredincidentally, I also just wrote a patch to update.py to make it sync the setup.py file19:43
mordredso those really will be managed boilerplate19:43
clarkbmordred: maybe you can get dstufft to give us a tl;dr on the undocumented feature referred to in the pip bug19:44
clarkband see if that actually does help us19:44
mordredI'll ask him19:44
sdaguealso, I've got unit testing for update.py inbound, as soon as mordred does a pbr fix19:44
mordredyup. we have a pbr bug to bug folks about to help this19:44
sdaguebecause tox in requirements/ is fun :)19:44
mordredthen I'm also going to get per-branch mirrors up19:44
*** nati_uen_ has joined #openstack-meeting19:44
mordredand finally- I think we should ditch installing from pip and figure out a way to auto-create debs and install from those - because we're spending WAY too much time on this19:45
sdagueI think that just moves the pain elsewhere19:46
mordredbut I am not working on that19:46
jeblairmordred: won't that put us in the "can't use python-foo version X because it's not packaged yet" boat again?19:46
*** nati_uen_ has quit IRC19:46
clarkbjeblair: yes, that was my worry when we were discussingthis the other day19:46
mordredpossibly to both of you ... but we are spending a LOT of effort on this19:46
*** ruhe has quit IRC19:46
jeblairmordred: which i'm okay with, if we think we're in a better place to deal with that new (less churn, more packagers, cloud archive, etc)19:46
mordredand turning up every corner case in python19:46
mordredI don't think it's the right thing to work on right now19:47
mordredbut I do think perhaps at the summit, we should discuss what it might look like in earnest19:47
sdagueI think it's a summit session, honestly19:47
jeblairsounds good to me19:47
*** markmcclain has joined #openstack-meeting19:47
*** nati_ueno has quit IRC19:47
mordredI still agree that we do not want to be in the business of shipping debs or rpms19:47
jeblairmordred: (and i agree with you in principle)19:47
*** nati_ueno has joined #openstack-meeting19:47
mordredbut like we've talked about for infra packages, operationally helpful packages might be helpful19:47
jeblairwe're at a very different place than we were 2 years ago19:48
mordredvery much so19:48
mordredhttps://review.openstack.org/39363 btw19:48
jeblairanything else on this topic?19:48
mordredfor those who feel like looking at a pbr change related to helping the requirements work19:49
jeblair#top Gerrit 2.6 upgrade (zaro)19:49
*** sarob has joined #openstack-meeting19:49
jeblair#topic Gerrit 2.6 upgrade (zaro)19:49
*** openstack changes topic to "Gerrit 2.6 upgrade (zaro) (Meeting topic: infra)"19:49
jeblairzaro: how's it going?19:49
zaroohh.  it's going..19:49
zaroi think i have gerrit with WIP votes working now.19:49
*** diogogmt has joined #openstack-meeting19:50
clarkbwith one small asterisk right?19:50
jeblairis that with a patch?19:50
zaronope! just figured out the bit of prolog..19:50
clarkbzaro: but it requires the patch for the change owner right?19:50
zaroyes, it's gerrit core.19:50
mroddenclarkb: thanks, didn't realize the check_uptodate.sh was just nova19:50
jeblairzaro: have you proposed it upstream yet?19:50
*** markmcclain has quit IRC19:51
zaroi just got it all to work.  will submit a patch to upstream this week.19:51
fungipleia2 found an internet19:51
sdagueso couldn't we get WIP equiv by making APROV -1,0,+1 and letting an author -1 APROV his/her own patches?19:51
jeblairzaro: neat! :)19:51
zarolet's see what they say.19:51
jeblairsdague: that's actually the plan we discussed...19:51
sdagueoh... ok :)19:51
mordredif they're amenable to the patch in general19:51
*** willOchanda has joined #openstack-meeting19:51
mordreddo we think we'd be willing to roll out a 2.6 with only that patch19:52
jeblairsdague: and i believe the "let an author..." bit is what zaro was patching to support19:52
zaroi have been in discussions with mfink?  and i did it on his suggestion.19:52
mordredoh awesome19:52
clarkbjeblair: and/or adding a WIP category, but both changes need the patch zaro wrote to be expressible in the ACLs19:52
jeblairsdague: (existing gerrit acls don't support that operation)19:52
sdagueok, I had thought that permission was already in,19:52
zarook.  that's it for now.19:52
mordredI think, given a history of carrying a whole string of patches, carrying one patch for a cycle would not be as terrible19:53
jeblairzaro: i think mfink has a very strong voice in the gerrit community, so if he likes it, that's great.  :)19:53
zarogood to hear.19:53
jeblairmordred: let's give this "develop upstream" thing a shot, eh? :)19:53
*** vipul-away is now known as vipul19:53
mordredjeblair: sure!19:53
* mordred just wasn't sure what the 2.7 schedule was looking like19:54
jeblairzaro: i'm very excited, thanks!19:54
clarkbme too19:54
jeblair#topic cgit server status (pleia2)19:54
*** openstack changes topic to "cgit server status (pleia2) (Meeting topic: infra)"19:54
jeblairpleia2: welcome!19:54
pleia2so, the one thing I wanted to talk about is addressing for grabbing git repos19:54
* mordred welcomes our new git.o.o overlords19:54
*** afazekas has joined #openstack-meeting19:55
pleia2the plan right now is to do what fedora does (it's easy) and do git://git.o.o/heading/project and http://git.o.o/cgit/heading/project19:55
pleia2so they aren't the same :(19:55
pleia2git.kernel.org makes it so they are both git.kernel.org/prod/19:55
mordredI think jeblair has convinced me that I can get over my issues with the cgit in the url19:55
pleia2err /pub19:55
clarkbpleia2: I think we can lie and put them all under /cgit19:55
clarkbeven though cgit doesn't do git protocll19:55
pleia2clarkb: yeah, that's really easy19:55
jeblairpleia2: i'm okay with that because you have indicated cgit really wants to be set up like that, fedora and kernel work that way...19:56
mordredI do not want to add cgit to the git:// url19:56
fungidoes kernel.org use rewrites or something? (if first node in the path matches an org, rewrite the url)19:56
jeblairyou want to put the git-protocol repos under 'cgit/'? that doesn't sound good to me19:56
mordredif we lie about anything, I want the cgit to go away from the urls in places19:56
pleia2fungi: probably, I clicked down into a project to see what urls they provide visually and:19:56
*** willOchanda has quit IRC19:56
mordredbut I'm fine with having the web and the clone be different19:56
pleia2^^ ie19:56
uvirtbotpleia2: Error: "^" is not a valid command.19:56
jeblairhttps://git.kernel.org/pub/scm/bluetooth/bluez.git  is not cgit19:57
jeblairit's regular git19:57
pleia2ah, interesting19:57
*** epim has quit IRC19:57
clarkbso maybe that is what we do, put regular git http daemon behind /pub put git:// behind /pub then cgit can have /cgit?19:57
mordredright- I think git clone http:// and git clone git:// should have the same urls19:57
jeblairso i think it makes sense to serve cgit from /cgit19:57
clarkbmordred: I agree19:57
*** lorin1 has joined #openstack-meeting19:57
clarkband I agree with jebalir19:58
fungiworth noting, you don't have to clone from cgit, you can clone from http(s) published copies of the git trees19:58
*** spzala has quit IRC19:58
fungier, that19:58
mordredand I don't think we need pub - I think that can go in root19:58
jeblairand let's serve http and git protocols without a prefix19:58
mordredgit clone git://git.openstack.org/openstack/nova.git19:58
jeblairmordred: +119:58
jeblair#topic Py3k testing open for business (fungi, zul, dprince, jd__, jog0)19:58
*** openstack changes topic to "Py3k testing open for business (fungi, zul, dprince, jd__, jog0) (Meeting topic: infra)"19:58
jeblairfungi: 1 minute!19:58
fungijust a quick update19:58
*** noslzzp has quit IRC19:58
fungiwe're basically ready19:58
fungicouple of reviews which need last-minute attention...19:59
fungi#link https://review.openstack.org/#/q/status:open+project:openstack-infra/config+branch:master+topic:py3k,n,z19:59
jeblair(plug for my new gate test which will catch missing jobs!)19:59
fungibut that's all the updates i have time for in here. we can pickit up i #-infra19:59
jd__what's missing?20:00
jeblairso close!20:00
fungijd__: see link20:00
fungijd__: we missed that when reviewnig your change earlier20:00
* ttx whistles innocently20:00
*** markmc has joined #openstack-meeting20:00
jd__too bad20:00
jeblairthanks everyone!20:00
*** openstack changes topic to "OpenStack meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Jul 30 20:00:54 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-07-30-19.02.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-07-30-19.02.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-07-30-19.02.log.html20:01
ttxWho is around for the TC meeting ?20:01
ttxshardy, galstrom, annegentle, mikal, mordred, markwash, jgriffith, gabrielhurley, markmcclain: around ?20:01
ttxnotmyname won't be around, vishy might be late20:01
galstromttx: yo20:01
*** noslzzp has joined #openstack-meeting20:01
ttxFYI Justin Shepherd (galstrom) is proxying for dolphm20:01
markwashI'm here on behalf of vishy and myself20:01
*** Haneef has quit IRC20:01
*** gabrielhurley has joined #openstack-meeting20:02
*** markmcclain has joined #openstack-meeting20:02
ttxok, we have quorum now20:02
ttx#startmeeting tc20:02
openstackMeeting started Tue Jul 30 20:02:24 2013 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:02
*** openstack changes topic to " (Meeting topic: tc)"20:02
openstackThe meeting name has been set to 'tc'20:02
ttxAgenda for today is at:20:02
ttx#link https://wiki.openstack.org/wiki/Governance/TechnicalCommittee20:02
ttxdo we have Rob Hisrschfeld around ?20:02
ttxok, let's start with devstack then20:03
*** anniec has quit IRC20:03
ttx(Rob told me he would be present only the first 30min so we might switch to him if he appears20:03
ttx#topic New program application: Devstack20:03
*** openstack changes topic to "New program application: Devstack (Meeting topic: tc)"20:03
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2013-July/011896.html20:04
*** luis_fdez has quit IRC20:04
ttx(1) Scope, mission statement, how "essential" the effort is to OpenStack20:04
ttxSo this is mostly an oversight when we set up the original list of already-accepted programs20:04
ttxDevstack was an official project in the old taxonomy, so there is no question of it being official/essential or not20:04
ttxThe question was more in the scope, should it land in QA, Infra, or in its own program20:04
ttxPersonally, since the core people caring about devstack are a separate set of the people caring for Infra or QA, it makes sense as a separate program20:04
mordredI agree20:04
russellbis it really a separate group?20:05
markmcI see it as a developer tool, would like the mission statement to say something about that20:05
markmcseems like a different group to me20:05
russellbit seems sdague and dtroyer are the main reviewers, and they are both in qa-core20:05
*** willOchanda has joined #openstack-meeting20:05
mordredalso, again, the fact that we use devstack for infra or qa is an implementation detail. it's not devstack's primary purpose in life20:05
dtroyerI am?20:05
markmce.g. would dtroyer identify himself as infra or QA?20:05
ttxrussellb: enough for QA and infra not wanting to sheperd it20:05
russellbdtroyer: grenade?20:05
dtroyerI didn't think I was in either team20:05
*** hub_cap has joined #openstack-meeting20:05
dtroyerah, right20:05
*** bknudson has left #openstack-meeting20:06
dtroyerdoes wearing one hat affect the other?20:06
ttxrussellb: in the end if neither program adopts it, that means it's a separate group20:06
markmcI think that answers the "would dean identify himself as QA?" question :)20:06
ttxeven if it has people in common20:06
russellbttx: yep, guess so20:06
ttx<markmc> I see it as a developer tool, would like the mission statement to say something about that20:06
*** rwsu-away is now known as rwsu20:06
mordredI dont' think it's about dean's self-identification - I see it as that ^^20:06
mordredthat's not the mission of qa20:06
mordredand it's not the mission of infra20:06
ttxcurrent mission statement is:20:06
markmcoh, it does say that20:06
ttx"To provide an installation of OpenStack from git repository master, or specific branches, suitable for development and operational testing.  It also attempts to document the process and provide examples of command line usage."20:06
*** jecarey_ has joined #openstack-meeting20:06
markmcyeah, sorry20:07
markmcmissed "suitable for development"20:07
ttxmarkmc: does that work for you ?20:07
ttxMore comments/questions on the  Scope, mission statement part ?20:07
*** dklyle is now known as david-lyle20:07
* mordred thinks dtroyer is great20:08
ttx(2) Team/effort/community maturity20:08
ttxThat effort is pretty mature by now. It's even almost in stable mode :)20:08
ttxdtroyer: is there more to do rather than maintain it ? Any short-term / mid-term objectives for the devstack "program" ?20:09
ttxAt this point it's a bit of a catch-all project with a lot of pass-by contributors20:09
*** changbl has quit IRC20:09
*** pabelanger has left #openstack-meeting20:09
dtroyerThe bulk of the work right now is making it all fit together but there is a lot of room for improvement20:10
dtroyermostly incremental though, no plans for radical changes20:10
ttxdtroyer: and constant work to integrate more projects, i suppose20:10
*** jecarey has quit IRC20:10
ttxComments / Questions on the  Team/effort/community maturity aspect ?20:11
dtroyerright.  a lot of that work comes out of the projects though as they know how their code should run20:11
*** adjohn has joined #openstack-meeting20:11
ttxOK, ready to vote ?20:12
*** doron_afk is now known as doron20:12
markmc#vote yes20:12
ttxwait for the signal20:12
markmc#vote ok20:12
markwash#vote lol20:12
ttx#startvote Accept Devstack as an official OpenStack program? yes, no, abstain20:12
openstackBegin voting on: Accept Devstack as an official OpenStack program? Valid vote options are yes, no, abstain.20:12
openstackVote using '#vote OPTION'. Only your last vote counts.20:12
mikal#vote yes20:12
markmc#vote yes20:12
galstrom#vote yes20:12
russellb#vote yes20:12
ttx#vote yes20:12
jgriffith#vote yes20:12
shardy#vote yes20:12
mordred#vote yes20:12
* markwash votes for two20:12
jd__#vote yes20:12
markwash#vote yes20:13
markmcclain#vote yes20:13
ttxmarkwash: you need to switch nicks before voting a second time.20:13
markwashttx: we can probably just let this one slide20:13
gabrielhurley#vote yes20:13
ttx30 more seconds20:13
*** changbl has joined #openstack-meeting20:14
openstackVoted on "Accept Devstack as an official OpenStack program?" Results are20:14
openstackyes (12): markmc, ttx, galstrom, shardy, jd__, russellb, jgriffith, mikal, mordred, gabrielhurley, markwash, markmcclain20:14
ttxSo that's a yes.20:14
dtroyerThanks all...I promise not to rewrite it all in Go.20:14
ttxdtroyer: congrats. Not that it changes anything, but congrats still.20:14
jgriffithdtroyer: haha!20:14
ttxdtroyer: right, I missed that question.20:14
mordreddtroyer: oh. wait. I thought you were going to do the opposite20:14
markmcwait, did we just approve a non-python project?20:14
mordredmarkmc: my friend - infra has several java repos...20:15
markmcmordred, burn!20:15
ttx#topic Open discussion20:15
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:15
ttxFirst thing I wanted to mention, I submitted a "Meet the Technical Committee" panel session for the next OpenStack Summit20:15
ttxThe idea being to explain what the TC does, our recent changes and decisions, and field questions from the audience20:15
gabrielhurleymordred: you better hope the board don't make you use the common python API code for all that...20:15
ttxWe don't really know who will be in the TC by then, some people will probably not be available at the time it's scheduled (if it's accepted), and we don't really need EVERYONE to be present...20:15
ttxbut I wanted to give you an early heads-up in any case20:15
mordredgabrielhurley: I'll implement it as a plugin20:15
ttx& "plug-in"20:16
mordredttx: I'll be there - I have no idea if I'll still be TC - but I'll be there20:16
ttxmordred: trying to crash ALL the panels ?20:16
gabrielhurleyttx: +1, the "meet the core devs" sessions are always useful and well-attended at other open source conferences.20:16
markmcttx, sounds like a good idea (the TC panel thing)20:16
ttxThe other thing I wanted to mention is that some of us mentioned the idea of considering non-voting tempest integration as a prerequisite before graduation from incubation20:16
ttxHistorically we asked projects to set up QA/gating/tempest integration in the first months after graduation...20:16
mikalgabrielhurley: should we have a meet the core devs session at the summit then?20:16
*** lorin1 has left #openstack-meeting20:17
mordredttx: ++20:17
ttxBut in some cases that came back to bite us as other priorities tend to interfere20:17
mordredI would very much like to have this be a real thing20:17
ttxIf we take that stance, it should be communicated. Trove might find it difficult to set up such thing in the time left before the end-of-cycle graduation review (end of August)20:17
gabrielhurleymikal: that's called "the entire summit". just getting the TC together and answering questions is good enough.20:17
mordredgraduation from incubation should have as a requirement demonstrable non-voting gate jobs20:17
mordredthat work20:17
markmctempest requirement sounds reasonable ... but there's some minimal bar of test coverage too20:17
markmcnot just "a single tempest test to ping the API endpoint"20:17
*** adjohn has quit IRC20:17
*** lexinator has quit IRC20:17
mordrednope. it should make us say "yes, when we turn that on as a gate, it will matter"20:18
*** stevemar has joined #openstack-meeting20:18
*** doron is now known as doron_afk20:18
mordredand have been running long enough that it doesn't seem flaky20:18
ttxmarkmc: sure, we always had that test coverage question... askign that they set up some CI gate is new though20:18
mikalgabrielhurley: well, we discourage conference attendees from coming to design summit sessions now, so that's not entirely true20:18
markmcthe CI gate has to test something though20:18
mordredthing is - one of the things they get out of incubation is that infra will talk to them20:18
gabrielhurleymikal: damn. you've got me there... propose it if you like. ::shrug::20:18
mordredso I'd see that they should make use of that during their incubation20:18
ttxIt /MIGHT/ make Trove fail graduation if they can't make it happen in the remaining time.20:18
ttxhub_cap: fair warning ^20:19
markmcmordred, what, at a minimum, should the gate for a new project test?20:19
hub_capoh im watching20:19
hub_capthx ttx20:19
hub_capbut i do have a Q20:19
hub_caphow come im alerted to this < 2mo in20:19
mordredmarkmc: I don't know - I think quality of the gate might need to be  ajugdgement call from us for a bit20:19
ttxhub_cap: given that you're the first project to be held to that standard, feel free to raise questions20:19
hub_capand required :) cant it be for /new/ projects?20:19
markmcmordred, right - we need to give fair warning that it's not just a single API ping test20:19
hub_capi feel it'd be fair if i knew it from teh start, since heat integration was my requirement20:19
mordredhub_cap: to be fair - you DO have a devstack-based integration gating test right now - so I betcha a single person could get that transitioned to the devstack gate if they were motivated20:20
mordredbut it's a fair question20:20
hub_capim _totally_ interested in tempest, and its #2 on the list of things for me to do20:20
hub_capbut heat being #1 i dont want to skimp on it :)20:20
mordredI'm fine with not adding the hard requirement this cycle - especially because I know that trove does have testing automation based on devstack-gate already20:21
hub_capsure mordred but motivated != pressured ;)20:21
mordredbut I do want it to be a thing that we consider important20:21
hub_cap+1 mordred as soon as im done w/ heat integration im doing it20:21
ttxhub_cap: it's a bit unfair to sump the requirement after so many months of incubation, yes20:22
hub_capheh ttx20:22
mordreddevananda: ^^ also, this may or may not apply to you too20:22
hub_capwe are diligently trying to get out of incubation this cycle fwiw20:22
ttxI'm fine with considering a good work in progress sufficient in the Trove case, if we have insurance it's really top priority for the team20:22
hub_caperr, graduate incubation ;)20:22
hub_capttx: guaranteed its my prio after heat integration20:23
ttxmordred, others: thoughts ?20:23
hub_capim not a fan of having tests that are different from the community20:23
hub_capbut we have tests :) and a ton of em20:23
ttxNext on the open discussion we have Trove scope expansion to NRDB. It was raised a bit late to be formally considered by the TC, but we can still discuss it20:24
*** IlyaE has quit IRC20:24
hub_capyea i figured ttx20:24
hub_capid be happy to start the discusion now and finish it next wk20:24
ttxannegentle wanted to make sure her mission statement was ok, too, before she runs with it20:24
hub_capok /me waits20:24
markmcheh, a schedule for the open discussion :)20:25
markmcagenda, rather20:25
*** atiwari has quit IRC20:25
ttx"open discussion" just means "in parallel" for me :)20:25
hub_capok then ill go!20:25
*** diogogmt_ has joined #openstack-meeting20:25
*** IlyaE has joined #openstack-meeting20:26
ttxhub_cap: go for it20:26
*** diogogmt has quit IRC20:26
*** diogogmt_ is now known as diogogmt20:26
hub_capso our redis POC makes no changes to the core api+core infrastructure. its just another _impl_. there are 2 extensions that are tied a bit to the guest impl but the redis guys are making those extensions in the guest as well. the guest already has a notion of 'im service X', so it can pretty easily get extensions from the codebase as well20:26
hub_capand the /clusters api will also have 'cluster flavors' as we call it20:26
hub_capso if you upgrade your redis instance, you will have a list of avail flavors so to speak, to upgrade to (not many for redis, mysql has many more)20:27
markmchub_cap, is the POC code posted anywhere?20:27
hub_capmarkmc: sooooo it is, pre rename20:27
hub_caplet me push it into the codebase20:27
hub_capor at least put up a WIP review20:27
hub_capim sick as a dog today but ill rip it out tomorrow20:27
mordredput up a WIP review I think would be great20:27
markmcit'd be great to do that, fire a mail to openstack-dev and let folks take a look20:27
* markmc doesn't have much of an opinion20:28
hub_capabsolutely. ill reply to the email i sent20:28
hub_capi like your opinion markmc :)20:28
ttxanything else hub_cap could do in preparation for next week's decision ?20:28
markmcbut maybe there's someone out there who has started working on something like this and has good insights20:28
mordredso - my concern is20:28
*** gyee has joined #openstack-meeting20:28
mordredwhat do we do if now trove has mysql + redis + cassandra + mongodb + bearddb20:28
mordredand we end up with the virt-layer problem in nova20:29
hub_cap+1 to bearddb20:29
mordredof not-well-tested backends or backends that are abandoned20:29
hub_capwell mordred i wont accept any impl w/o sufficient tests20:29
hub_capand i will deprecate / remove them if they are not used20:29
hub_capi dont like bitrot20:29
mordredbut are you going to expect the infra to test all the different backend combos?20:29
russellbmordred: i'm moving to requiring public CI for all of them by the release of Icehouse (even if it's third party testing, as long as results are public)20:30
mordredrussellb: ++20:30
hub_cap+1 russellb ill do the same20:30
russellbi'd like to see a similar requirement everywhere20:30
mordredyeah. I could totally live with that20:30
hub_capwell mordred ill fire up clusters, mysql or _blah_20:30
*** lexinator has joined #openstack-meeting20:30
russellbi know jgriffith is wanting to do something along those lines as well, based on recent ML posts20:30
jgriffiththis sounds vaguely familiar :)20:30
russellbjgriffith: :-)20:30
mordredmy main concern was explosive backends20:30
jgriffithI think it's a natural progression20:30
* mordred looks away in shame20:31
jgriffithmordred: ha!!!20:31
hub_cap:D i liked it20:31
* hub_cap channels my inner markwash20:31
*** schwicht has quit IRC20:31
* markwash lold20:31
jgriffithI think coffee just came out my nose20:31
hub_capso, mordred given that i wont allow code w/o sufficient tests20:32
jgriffithwhich is still better than what happened to mordred20:32
hub_captempest tests, since they are new20:32
hub_capand that ill work w/ you to make sure that your infinite cloud resources are not wasted :P20:32
*** schwicht has joined #openstack-meeting20:32
hub_capfwiw, we will be doign the same testing w/ mysql, for clusters.. so, i think its a natural progression. and cluster testing will be in tempest as well20:32
hub_capand we could say the same w/ RDB systems, im sure we could impl a ton of those as well and end up w/ teh same issues20:33
hub_capclustered sqlite anyone?20:33
* hub_cap assumes its not really possible ;)20:34
mordredoh god20:34
ttxok, any more questions on trove nrdb ? More next week about this anyway20:34
hub_capyes ttx. ill have the POC shot to the ML tomorrow20:34
hub_capfor your perusing20:34
ttxannegentle: want to raise your program description, or the consequences of it ?20:34
hub_capme annegentle?20:35
annegentlettx: I'll just point out the summary20:35
annegentleSince we cannot govern all documentation equally with the resources available, our focus is core first and users first…20:35
hub_capoh sry ttx... i thought annegentle said that to me, the fever is getting the best of me20:35
annegentleoh dear :)20:36
ttxannegentle: I think prioritization is fair.20:36
annegentleI think I'll be shaping and honing further as we work on release documents, but I think that we'll continuously publish all the time.20:36
*** litong has quit IRC20:37
annegentleit's just that continuous release doesn't mean "all the documented procedures all the time"20:37
ttxannegentle: I still think if someone wants to work on some integrated project and document that, he should still be able to do so within the docs team20:37
*** vijendar has quit IRC20:37
annegentlettx: absolutely, we'll coach and assist as much as possible20:38
ttxbut mentioning priorities sounds good to me20:38
ttxcomments on that ? Can annegnetly run with her program description ?20:38
ttxannegentle, even20:38
annegentlecan I run gently? :)20:38
annegentleI believe perfection is the enemy of good.20:39
* markwash thinks you should /nick annerunsgently20:39
mikalI'm ok with focussing on core and users20:39
annegentleso we will continuously improve to collaborate wider, and we've gotten many more contributors even in the last three months20:39
*** annegentle is now known as anneisgentle20:40
markmcI'd be a little wary of using "core" as the basis for prioritization, but absolutely some projects should be prioritized over others20:40
ttxmarkmc: as long as it's not exclusive, i don't mind so much20:40
markwashI guess I pretty much trust the docs people to know the correct prioritization20:40
markmce.g. "what users care most about"20:41
anneisgentlemarkmc: yeah and I specifically took the user committee's definitions of users20:41
ttxagree that documenting ceilometer is less important than documenting heat, for example20:41
anneisgentlettx: the great thing is, ceilometer has a great dev doc site20:41
ttxLast thing I had on the agenda, although it's a bit emply if Rob is not around, is the Spider "what is core" thing20:42
markmcso, on the "what is core" thing20:42
markmcI feel like the conversation has progressed on into the far distance20:42
markmcand I'm still stuck back trying to figure out what problem we're addressing20:43
markmce.g. I thought it was about using the trademark as a lever to ensure compatibility between public clouds20:43
markmcand help form a market place of public clouds20:43
markmcyet, rob's "why we care about core" blog:20:43
markmcdoesn't mention any of that20:43
ttxmarkmc: so I'm not sure it makes any progress to solve the question of inclusive vs. limited number of projects20:43
markmcit's all about ensuring we have a healthy project or something20:43
markmcthis is just occurring to me now, really20:44
ttxsome people apparently think that interop is easier if you limit the number of projects20:44
markmcI'm just curious what other TC members make of the discussion20:44
ttxI kinda think the opposite20:44
jgriffithIt's kind of all over the board IMO20:44
ttxif we let every "openstack cloud" implement their own version of designate... we lose in interop20:44
jgriffithmarkmc: My opinion was intially a better/tighter definition of OpenStack20:44
mikalmarkmc: I think public cloud interop is important, but I'm not convinced that a big trademark hammer is the way to do it20:45
jgriffithbut I don't think that's the direction any longer20:45
mikalmarkmc: but I don't have an alternate proposal either20:45
gabrielhurleyI'm with jgriffith: everyone want's a different problem addressed. We're no longer trying to achieve any one thing with it (if we ever were).20:45
markwashmarkmc: +1 let's reaffirm the problem statement20:45
ttxif we say "an openstack cloud must have DNSaaS and it must be Designate" then the end result is more interoperable20:45
*** schwicht has quit IRC20:45
ttxI think the tradeoff is between "a lot of openstack clouds, somehow interoperable" and " a few very interoperable openstack clouds"20:46
markmcbut like20:46
markmcwhat does e..g "Velocity – the rate of progress and quality of the code base.  "20:46
markmcor "Culture – open source culture strongly encourages sharing and collaboration."20:46
markmchave to do with any of this?20:46
mordredmarkmc: the stuff that rob is collecting and putting together20:46
jgriffithmarkmc: I can't speak for Rob but I had some conversations about that unrelated to the interop question20:46
AlanClarkis it kosher for me to jump into the conversation since I am not on the TC?20:47
mordredare supposed to be basis for discussion and not the definitoin of it20:47
mordredAlanClark: please do20:47
ttxmarkmc: where is that ?20:47
mordredthis is all open sores and stuff in here20:47
jgriffithmarkmc: we talked a bit about how to keep components like Nova, Neutron etc focused and continuing to get better20:47
gabrielhurleyI'd also like to point out that ""an openstack cloud must have DNSaaS and it must be Designate" then the end result is more interoperable" is not actually true. How often do you try to make the existing OS services talk to themselves across clouds?20:47
jgriffithwith the explosion of *other* things being introduced20:47
ttxmarkmc: I've been looking at http://robhirschfeld.com/2013/07/24/what-is-core-strawman/ and it doesn't mention velocity or culture20:47
gabrielhurleyI'd argue that competing implementations of the same standard improves interop20:47
jgriffithgabrielhurley: interesting point, which makes me suggest we need to define better the *what*20:48
markmcttx, http://robhirschfeld.com/2013/07/22/making-openstack-meaningful/ is framed as "why core is important"20:48
mordredgabrielhurley: well, that's one of the things that we keep coming back to - we are not a standards body20:48
markmcttx, from http://robhirschfeld.com/2013/07/22/kicking-off-core/20:48
gabrielhurleywe don't know what we are20:48
mordredwe are and always have been, a body where implementation is the definition20:48
shardygabrielhurley: we are trying to do exactly that with heat in standalone mode20:48
mordredwe do20:48
jgriffithgabrielhurley: +1000020:48
mordredknow that we are not a standards body20:48
ttxmarkmc: I skipped that one and jumped directly to the strawman20:48
gabrielhurleysays who?20:48
mordredwe've said that strongly since day one20:48
gabrielhurleythere's a lot of language in what Rob sent out that borders on being a standards body20:48
mordredat no point have we ever said differnetly20:48
mordredwell, we'll fix that20:49
mordredthat's why the focus on running the code20:49
markmcttx, I'm note sure the strawman details the problem being addressed either20:49
mordredand not just being api compat20:49
mordredif all you need is api compat to be openstack20:49
mordredthen we're a standards body - just a poorly organized one20:49
gabrielhurleymordred: that's why *you* focus on running the code... there are still a lot of folks in the community who are more concerned with API specs.20:49
mordredbut we're not - we ship software20:49
mordredabsolutely. api specs are important20:49
mordredand I gotta well you - when clouds diverge we all lose20:49
gabrielhurleyagreed on that20:50
mordredbut I'm not interested in specs that are there to allow some jackass to go rewrite openstack in java because he just doesn't like python20:50
ttxpersonally I have 3 gripes with the thing: (1) the use of "plug-in" term (solved), (2) it doesn't address the hard question of inclusive vs. limited approach, and (3) it relies a lot on tempest testing which will not just happen by magic20:50
jd__that could be a song20:50
mordredbecuse that doesn't help anyone20:50
jgriffithmordred: I agree with that, but I think there's a spot in the middle20:50
mordredjgriffith: I agree with you :)20:50
mordredI just think that we have to have code - if all we have is a spec, then we're not very interesting20:51
mordredttx: it's not intended to address 220:51
gabrielhurleymordred: you'd rather cling to python than accept some jackass' rewrite even if it's better, faster, and more reliable? (hypothetically speaking)20:51
mordredgabrielhurley: if the TC decides that the jackass rewrite is better and that we should switch to it, then fine20:52
*** willOchanda has quit IRC20:52
mordredbut until then, whatever that thing is, it's not openstack20:52
*** Vek has joined #openstack-meeting20:52
markwashmordred: that's not really how consensus evolves :-)20:52
gabrielhurleyI'm not arguing for not having code, I just don't want to us to write bylaws that specify coding practices or languages20:52
hub_capis that not already implicit?20:52
mordredI also do not want that - and don't want to imply that20:52
mordredbut I think that openstack is quite specifically the output of those of us who form openstack20:52
jgriffithNo offense but aren't we getting a bit sideways on this?20:52
gabrielhurleyand yep20:53
markmcjgriffith, aresways is the precise term20:53
markmcheh, typo20:53
jgriffithmarkmc: haha20:53
markmcsad, failed joke20:53
mordredttx: it's intended to provide framing for 220:53
jgriffithintent was received :)20:53
ttxmarkwash: at the heart of the project is a community of developers. You won't turn them into Java devs overnight20:53
mordredwith the idea that, like judgements about technical things, there's always going to be judgement calls to be made, and you can't just constitution a defition up20:53
gabrielhurleysoooo... we should refine/restate the problem definition and then cut everything from the "what is core" document that's not addressing that problem?20:54
jgriffithgabrielhurley: might be a good way to start20:54
ttxmarkwash: so I'm with lordred on that one, whatever that thing is, it's not openstack20:54
*** apevec has joined #openstack-meeting20:54
mordredI think that the point of the document is still being very poorly communicated20:54
*** danwent has quit IRC20:54
gabrielhurleylordred... he's been upgraded20:54
markwashwhos trying to make people into java devs?20:54
ttxmarkwash: <gabrielhurley> mordred: you'd rather cling to python than accept some jackass' rewrite even if it's better, faster, and more reliable? (hypothetically speaking)20:54
galstromgabrielhurley: ++20:55
markwashI just think reboots are healthy and it looks like a cohesive community would never do them20:55
jgriffithttx: mordred gabrielhurley so last spring we started having this disucssion among the TC IIRC (what is core) and punted it to the board20:55
*** hemanth has joined #openstack-meeting20:55
jgriffithIIRC we were trying to think about "what is OpenStack"20:55
gabrielhurleythat ^^^. it's not something you should be proscriptive against. just trust that if you do the right thing you won't ever need to.20:55
jgriffithso we punted20:55
ttxI was happy to punt20:55
mordredthis document is an attempt to collect all of the various fibers that are running around this topic20:55
mordredit turns out that there are MANY20:55
gabrielhurleytoo many20:56
jgriffithttx: yes, now I remember why we did so :)20:56
mordredas the basis to frame a real discussion20:56
markmcway too many20:56
markmcis this discussion purely about using the trademark to ensuring interoperability clouds which call themselves OpenStack?20:56
ttxjgriffith: I think we should keep it punted20:56
mordredit's not intended to be a definition of core20:56
*** danwent has joined #openstack-meeting20:56
jgriffithttx: I'm mixed, only because I'd like some false sense of my destiny :)20:56
ttxand just make sure they don't insert tech language in wahetever they come up with20:56
mordredalso, I think the word core needs to diaf20:56
mordredit's become useless20:56
jgriffithttx: that may be the best approach20:56
markmcmordred, we should call this discussion "how our trademark program for public clouds should work"20:56
anneisgentlemordred: (or lordred, whatevs) what's diaf?20:57
jgriffithttx: I don't think we necessarily have the same perspective/interests20:57
mordredanneisgentle: 'die in a fire'20:57
hub_capfire fire fire20:57
med_die in a fire20:57
jgriffithttx: ^^ I mean TC versus board20:57
ttxmarkmc: jgriffith has a point. Should we care, as the TC ?20:57
gabrielhurleyI say we should care, yes.20:57
*** Guest10612 has quit IRC20:57
mordredmarkmc: I think it's "What does the word OpenStack mean?"20:57
markmcwhat's in the strawman is an awful lot of stuff we care about20:57
jgriffithmarkmc: ttx that's a great point, and I'm mixed20:57
gabrielhurleyexpecially to make sure they're not inserting extra stuff into it like they clearly are20:57
ttxgabrielhurley: care about trademark rules ?20:57
mordredmarkmc: which I think is broader and more relevant than trademark law, but certainly informs that20:57
markwashI mean, as much as this has to do with how api specs work, I think we care20:57
markwashdoes it have nothing to do with api specs?20:58
mordredI do not believe it's intended to have anything do to with api specs20:58
*** topol has quit IRC20:58
markmcmordred, if that's the discussion, I think it's doomed20:58
gabrielhurleyttx: if they were *only* and I mean really *only* talking about trademark rules I think we should be aware but it's totally their right to ignore us. But they're not at all.20:58
ttxgabrielhurley: I agree we need to watch the process to make sure it doesn't go west20:58
mordredmarkmc: that has to be answered. full stop.20:58
markmcmordred, start with "what does the word Cloud mean?" then :)20:58
mordredmarkmc: becuase without an answer to that, the question of how the trademark around it can be used is meaningless20:58
mordredmarkmc: no, this is very specific and very important20:58
jgriffithmarkmc: ha!!  I just solved that one the other day :)20:58
ttxgabrielhurley: *that* is what we need to address I think.20:59
*** aclark_ has joined #openstack-meeting20:59
mordredbecause if a person is going to interact with a thing named "OpenSTack" they need to know what they can and cannot expect from that thing20:59
mordredwhich is why we name things with proper names20:59
*** michchap has joined #openstack-meeting20:59
ttxgabrielhurley: not sure where they go beyond trademark rules though20:59
*** danwent has quit IRC20:59
ttxone minute left20:59
jgriffithmordred: +120:59
mordredto give htem defining characterstics20:59
*** AlanClark has quit IRC20:59
markmcmordred, "a thing named OpenStack" == a public OpenStack cloud20:59
jgriffithmordred: that's the part I'm interested in20:59
markmcmordred,  or the project, or ... ?20:59
markmcOpenStack is a lot of things20:59
mordredmarkmc: the product20:59
jgriffithmarkmc: no20:59
gabrielhurleymarkmc: "public"?20:59
*** hemanth_ has joined #openstack-meeting20:59
mordredmarkmc: if I want to interact with an openstack cloud - what can I expect from it20:59
ttxlast minute thing: I'm not very hapopy we have that discussion on openstack-tc btw21:00
jgriffithmarkmc: framwork for building/managing public and private clouds21:00
gabrielhurleythere are a lot of private openstack clouds that care about the trademark21:00
mordredmarkmc: it's entirely possible...21:00
*** carl_baldwin has joined #openstack-meeting21:00
mordredmarkmc: that we need to be more specific21:00
mordredsimilar to java21:00
jgriffithgabrielhurley: +1000021:00
mordredJava VM21:00
mordredJava Language21:00
ttxwould like Rob to push it to a public list if it is to continue21:00
jgriffithautomate all things!21:00
ttxOK, we are out of time21:00
gabrielhurleyugh... 'cuz that'll narrow it down21:00
*** nati_ueno_2 has joined #openstack-meeting21:00
ttxmore next week maybe21:00
markmcOpenStack the word is more than just what the expectations of the interface to an OpenStack install looks like21:00
ttxor on the list21:00
*** michchap has quit IRC21:00
mordredmarkmc: I agree21:00
markmcwhich is why I thought "the word" thing was too broad21:00
*** openstack changes topic to "OpenStack meetings || https://wiki.openstack.org/wiki/Meetings"21:01
jgriffithgabrielhurley: agreed, but that seems to be where we're heading :)21:01
openstackMeeting ended Tue Jul 30 21:00:59 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-07-30-20.02.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-07-30-20.02.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-07-30-20.02.log.html21:01
* markmc got the last word :-P21:01
mordredmarkmc: I thought we had enough context in the conversation to know that I wasn't trying to talk about definitoin of openstack the commnunity of people21:01
*** michchap has joined #openstack-meeting21:01
mordredmarkmc: never!!!21:01
markmcmordred, the context is lost on me now, honestly21:01
gabrielhurleymy head hurts21:01
ttxnext meeting21:01
ttxgabrielhurley: 50 minutes to recover21:01
ttxmarkmc, henrynash, jd__, markwash, jgriffith, russellb, shardy, gabrielhurley, markmcclain: around ?21:01
*** epim has joined #openstack-meeting21:02
gabrielhurley2:52 PM, I'll be back21:02
aclark_and I didn't get to jump in Freenode chose to dump me ;-(21:02
*** tedross has quit IRC21:02
ttxaclark_: more next week !21:02
ttx#startmeeting project21:02
openstackMeeting started Tue Jul 30 21:02:36 2013 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
ttx#link http://wiki.openstack.org/Meetings/ProjectMeeting21:02
*** alrs has quit IRC21:02
ttxBack in business after last week pause, we'll have a look at havana-3 plans and how reasonable they are (or not)21:02
ttx#info feature freeze is on *September 4*21:03
ttxNote that some projects implement a feature proposal freeze a few weeks before21:03
ttx#topic General stuff21:03
*** openstack changes topic to "General stuff (Meeting topic: project)"21:03
*** hemanth has quit IRC21:03
ttxI don't have anything specific21:03
ttxOh. Yes I have21:03
apevecttx, I'd like to repeat that we have planned stable/grizzly freeze on Aug 1st21:04
ttxIf you have generic contraints you'd like applied to desig nsummit topics, like "no QA session at the same time as Infra sessions" please send them my way ASAp21:04
apevecand release 2013.1.3 on Aug 8th21:04
shardyapevec: heat has several outstanding reviews FYI21:04
ttxapevec: how is it doing so far ?21:04
*** boris-42 has quit IRC21:05
apevecadam_g has sent status yesterday, there were two exceptions discussed on the stable-maint21:05
apevecshardy, so you want to have heat 2013.1.3 ?21:05
ttxsdague, annegentle, mordred: news from QA/Docs/Infra programs ?21:06
shardyapevec: yes please, but we can discuss that offline :)21:06
sdagueso the neutron job is in really bad shape21:06
mordredttx: we're having fun issues with requirements - but we're working on making them more solid21:06
ttxsdague: we'll talk about Neutron testing in the Neutron section21:06
shardyor after the mtg rather21:06
mordredttx: this is going to lead to more aggressive alignment on the requirements repo21:06
anneisgentleWe're holding Docs Boot Camp in Mountain View Sept 9 and 10, thanks to Mirantis for playing host.21:06
anneisgentle#link wiki.openstack.org/wiki/Docs_Bootcamp_201321:06
sdagueok, requirements chasing is getting interesting... not there yet21:07
mordredttx: because doing otherwise is killing us21:07
markmcmordred, any more details? the issues, the changes?21:07
ttxmordred: aggressivity++21:07
mordredmarkmc: the issues have to do with the fact that pip installs wind up with state based on the arbitrary sequence21:07
mordredrather than the graphe of needs21:07
mordredso the first thing that sdague and I are working on21:07
markmcyeah, think I saw something go by21:08
shardyanneisgentle: any way to participate remotely?21:08
mordredis getting devstack to run the update.py script in setup_develop21:08
mordredso that we have the same current behavior as devstack, but aligned to what's in requirements21:08
mordredalong with that we'll start gating changes to requirements on devstack21:08
anneisgentleshardy: sorry, not at this point21:08
mordredthen, we'll start auto-creating and proposing changes to projects on changes to requirements repo21:08
shardyanneisgentle: OK, thanks21:08
anneisgentleshardy: we're always here for you :) Monday office hours.21:09
mordredbecause, well, we will have already tested that they work21:09
ttxok, time to get into the specifics21:09
ttx#topic Oslo status21:09
*** openstack changes topic to "Oslo status (Meeting topic: project)"21:09
ttxmarkmc: hi!21:09
ttx#link https://launchpad.net/oslo/+milestone/havana-321:09
markmcit's all looking pretty fine21:10
*** dkranz has quit IRC21:10
ttxYou have 8 tracked blueprints targeted to h3, which is pretty reasonable21:10
markmcapart from messaging21:10
ttxoh, 5 now21:10
markmcbasically, oslo.messaging is in gerrit etc.21:10
markmcand now has working kombu and qpid drivers21:10
markmcnot thoroughly tested, but the basics work21:10
markmcthe big question is whether we can complete their testing and get e.g. nova switched over to using it21:11
ttxMost of your stuff is already under review, which is good news21:11
*** tanisdl has joined #openstack-meeting21:11
markmcwe've set ourselves a deadline of August 16th for a go/no-go21:11
ttxsounds a bit risky to do it, and a bit risky not to do it21:11
*** tanisdl has quit IRC21:11
markmci.e. unless nova is using oslo.messaging at that point, we punt to icehouse21:11
ttxmarkmc: +121:11
markmcnot doing it shouldn't have an impact on havana21:11
ttxI think it's good to wrap up oslo changes a few weeks before H3 anyway, so that we have time to push oslo-incubator syncs at the end of the milestone21:11
markmcany messaging features we want for havana will go in through oslo-incubator anyway21:11
*** johnpur has left #openstack-meeting21:12
markmcthe other big messaging one is the message security patches21:12
markmcwhich look in great shape21:12
markmcand the keystone KDS patches look pretty well advance too21:12
markmcso I'm fairly confident that will make it for havana21:12
markmca fair bit of work to make nova etc. use it, though21:12
ttxmarkmc: anything else you wanted to raise ?21:13
*** pnavarro has quit IRC21:13
markmcit begs the question whether we should have e.g. nova blueprints for "use oslo.messaging" and "use oslo message security"21:13
markmcnot just nova, all rpc-using projects21:13
*** ilyashakhat has quit IRC21:13
ttxmarkmc: does that sound fair to say that oslo should be finished with its features a few weeks before feature freeze ?21:13
markmcttx, yes21:14
ttxmarkmc: sounds like you want blueprints that affect multiple projects!21:14
markmca blueprint with tasks for multiple projects21:14
markmci.e. like launchpad bugs21:14
ttxmarkmc: your wishes may soon be granted.21:14
markmcin the meantime?21:15
*** ilyashakhat has joined #openstack-meeting21:15
ttxin the meantime, tracking as a separate blueprint makes sense to me21:15
markmcwould filing blueprints help track stuff?21:15
*** sarob_ has joined #openstack-meeting21:15
ttxQuestions about Oslo ?21:15
markmcthanks ttx21:15
ttx#topic Keystone status21:15
*** openstack changes topic to "Keystone status (Meeting topic: project)"21:15
ttxhenrynash: around ?21:15
*** ruhe has joined #openstack-meeting21:16
*** stevemar has quit IRC21:16
ttxlooks like henrynash is not around, jd__ you up ?21:16
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x20a3f50>21:17
ttx#topic Ceilometer status21:17
*** openstack changes topic to "Ceilometer status (Meeting topic: project)"21:17
ttxjd__: hey21:17
ttx#link https://launchpad.net/ceilometer/+milestone/havana-321:17
ttxYou have 13 tracked blueprints, which is slightly optimistic compared to your usual velocity21:17
ttxIt's also highly dependent on Eoghan and yourself, representing 9 of those 1321:17
ttxHow are you both going to make it ?21:17
jd__we believe!21:18
jd__though one of my blueprint "Alarming" isn't a real one21:18
jd__it's just one final to track a bunch of others21:18
jd__I don't know if we can change it status so it's clearer for you to track21:18
ttxok, we'll track that closely21:18
*** sarob has quit IRC21:19
ttxuse-new-rpc-messsage is marked Blocked. Could you explain what it is blocking on ?21:19
jd__ttx: yes, check its dependency graph actually21:19
jd__we're waiting for https://blueprints.launchpad.net/oslo/+spec/trusted-messaging21:19
ttxstacktach-integration depends on logging-uses-notifications and remove-instance-fault-table, but those have been targeted to "next"21:20
jd__these are Nova bp I think21:20
*** sarob_ has quit IRC21:20
ttxjd__: still sounds difficult to complete your ceilometer bp in h3 if nova's deferred on their side :)21:20
jd__all I can do is remove stacktach-integration, not sure sandywalsh will be happy21:21
ttxrussellb: ^could you look into that with sandywalsh and jd__  ?21:21
jd__maybe these aren't reall dep, I'll check with sandywalsh21:21
ttxjd__: anything you wanted to mention ?21:21
jd__all good21:21
ttxQuestions on Ceilometer ?21:21
ttx(We'll skip Swift since notmyname is not around)21:21
ttx#topic Glance status21:22
*** openstack changes topic to "Glance status (Meeting topic: project)"21:22
markwashnot fair21:22
ttxmarkwash: busted21:22
markwashwas almost done :-)21:22
ttx7 tracked blueprints so far, that sounds pretty reasonable21:22
ttxglance-tests-code-duplication still needs triaging :P21:22
markwashindeed it does21:22
*** spzala has joined #openstack-meeting21:22
markwashand there is one more that needs to be added to the list21:22
*** russellb has quit IRC21:22
ttxAbout api-v2-property-protection, we've been carrying it over for the last 12 months now...21:22
ttxIs there any reason to think that it will hit in the next weeks ?21:23
markwashttx but now people are working on it! :-)21:23
markwashthere has been some activity on the list as well21:23
ttxmarkwash: I heard that one before I think :)21:23
ttxmarkwash: so this time it's for real ?21:23
markwashthis time, its personal21:23
ttxok, I'll track that one closely :)21:24
markwashI'm not sure if it will make it, but there is active development and folks I trust21:24
ttxmarkwash: we pushed an advisory (OSSA-2013-018) for Glance python client today21:24
ttxmarkwash: how about we tag a new client release to get that out to the crowds ?21:24
markwashsounds good, will do21:24
ttxmarkwash: anything you wanted to mention ?21:24
markwashnothing from me, one question though21:24
markwashwhat is "Beta Available" ?21:25
ttx"Implementation is almost complete, code is available in a branch or a draft review now"21:25
ttxQuestions on Glance ?21:25
ttxDo we have markmcclain in the house ?21:26
ttx#topic Neutron status21:26
*** openstack changes topic to "Neutron status (Meeting topic: project)"21:26
ttxmarkmcclain: hi!21:26
ttx#link https://launchpad.net/neutron/+milestone/havana-321:26
* ttx refreshes ttx.py output, takes time21:26
*** russellb has joined #openstack-meeting21:26
ttx42 targeted blueprints... about twice as many as the total implemented in havana-221:27
ttxThis sounds a very unlikely goal, and could lead to issues prioritizing reviews and get the important stuff in21:27
ttxThat said, 22 of those 42 are implemented or under code review already...21:27
*** vijendar has joined #openstack-meeting21:27
*** vijendar has quit IRC21:27
ttxSo I guess if you pulled an enormous code review effort early on, and pushed back a few of those 43 to "Low" priority... the picture could look a bit more doable21:27
*** vijendar has joined #openstack-meeting21:27
ttxThere are a few without an assignee in there, which in my book could have been plain refused: auto-associate-floating-ip, ml2-multi-segment-api21:28
ttx(you should require an assignee to be set before triaging a blueprint)21:28
ttxmarkmcclain: openvswitch-kernel-vxlan is marked "Deferred"... should it be set to "next" milestone instead ?21:28
*** adjohn has joined #openstack-meeting21:29
markmcclainI need to doable check with the subteam working on vxlan21:29
markmcclainmight remove it all together21:29
ttxYou also have 12 "undefined" blueprints in there that need a priority. Ideally none of them would get higher than "Low" and add to the improbability above :)21:29
markmcclainI'll fix up the 2 unassigned that I missed21:29
ttxnachi, markmcclain, sdague: I wanted to talk about the Neutron gating tests21:29
ttxWe made the neutron gate non-voting due to bug 119402621:30
uvirtbotLaunchpad bug 1194026 in neutron "check_public_network_connectivity fails with timeout" [Critical,In progress] https://launchpad.net/bugs/119402621:30
ttxI'd like to have those tests re-enabled ASAP so that they don't bitrot to the point where we can't use them anymore21:30
ttxWhat's the status of that ? Are we now hitting bug 1206307 instead ?21:30
uvirtbotLaunchpad bug 1206307 in neutron "neutron-adv-test.sh:773 [Fail] Couldn't ping server in Gating" [Critical,Confirmed] https://launchpad.net/bugs/120630721:30
ttxsdague had to drop off -- markmcclain do you have news on that side ?21:31
markmcclainyeah.. I was chatting with nati_ueno yesterday about it and still have problems reproducing outside of the gate21:31
markmcclainI know that nati_ueno is actively working on the issue21:31
*** markvan has quit IRC21:31
ttxboth bugs are still active ? Or the first one was solved ?21:32
markmcclainthe patch we pushed for the first one didn't fully solve the problem21:32
*** alrs has joined #openstack-meeting21:32
markmcclainso the bug was reopened21:32
ttxok, so both bugs are active at this point21:32
markmcclainin the investigation he found the 2nd one21:32
*** vipul is now known as vipul-away21:33
*** adjohn has quit IRC21:33
ttxnachi: feel free to send me an update on your progress... and if you need any help21:34
ttxmarkmcclain: anything you wanted to raise ?21:34
*** Toshi has joined #openstack-meeting21:34
ttxQuestions on Neutron ?21:34
*** nachi has left #openstack-meeting21:34
*** nachi_ has left #openstack-meeting21:34
ttx#topic Cinder status21:34
*** openstack changes topic to "Cinder status (Meeting topic: project)"21:34
*** kebray has quit IRC21:34
ttxjgriffith: hola!21:34
ttx#link https://launchpad.net/cinder/+milestone/havana-321:35
ttxjgriffith: yt ?21:35
ttxrussellb: you there ?21:36
hub_caphes riding a horse21:36
*** meteorfox has quit IRC21:36
openstackRemoving item from minutes: <ircmeeting.items.Link object at 0x23b9110>21:36
ttx#topic Nova status21:36
*** openstack changes topic to "Nova status (Meeting topic: project)"21:36
ttxrussellb: hey21:36
*** benl has quit IRC21:36
ttx#link https://launchpad.net/nova/+milestone/havana-321:36
russellb#link http://lists.openstack.org/pipermail/openstack-dev/2013-July/012323.html21:36
* jgriffith snoozes he looses his turn21:37
russellbso .... yeah.21:37
*** SergeyLukjanov has quit IRC21:37
russellbi've deferred 10-15 blueprints or so21:37
ttxrussellb: so looking at tracked (>Low) blueprints, you are at 5121:37
ttxcompared to 25 delivered during h221:37
ttxI suspect you'll need to push more to "Low" (a.k.a. "may land, who knows") priority21:37
*** henrynash has quit IRC21:37
russellbttx: that's a good idea21:37
ttxeasier than deferring21:38
ttxesp. when you don't know what might make it21:38
russellbi'm also expecting a whole bunch to miss the proposal deadline21:38
*** neelashah has quit IRC21:38
ttxWhen is your "proposed feature freeze" ?21:38
russellbaug 2121:38
russellbi will work on dropping priority of some21:39
russellbhadn't thought of that21:39
ttxit's an easy trick21:39
russellbbut otherwise i feel like the best i can do is try to encourage review priorities, and wait to see what code actually shows up21:39
ttxbasically helps prioritizing reviews on one side... and lower expectations on the other21:39
ttximage-multiple-location depends on effective-template-base-image-preparing which was not targeted to any milestone21:39
ttxnew-hypervisor-docker is marked Blocked... what is it blocking on ?21:40
russellboh, sorry for not updating whiteboard21:40
russellbhe's adding devstack support21:40
*** noslzzp has quit IRC21:40
russellbi wanted to have a clear path to being able to test it21:40
ttxok, that is sort of implied in the current explanation, but wanted to be sure21:40
ttxwouldn't it be nice if we had tasks on blueprints ?21:41
russellbok, yes, that's all it is21:41
russellbthere's Work Items i guess ...21:41
ttxbut not for multiple projects.21:41
ttxrussellb: anything else you wanted to mention ?21:41
ttxOh, you may have missed the ping earlier21:41
russellbnot really, just thinking about what we can do better to avoid this kind of situation in the future21:42
russellbi guess it's being more aggressive with using Low21:42
ttx<ttx> russellb: ^could you look into that with sandywalsh and jd__21:42
russellbi did miss that, my connection dropped for a bit21:42
russellbso i don't know what that's referring to21:42
ttx<ttx> stacktach-integration depends on logging-uses-notifications and remove-instance-fault-table, but those have been targeted to "next"21:42
ttxstacktach-integration is a ceilo bp21:42
ttxthe other two are nova's21:42
russellbyeah, they hadn't started AFAIK21:42
russellbso i pushed them off21:42
ttxwhich made my inconsistency detector go bleep21:42
ttxthe answer might be to defer the ceilo one as well21:43
russellbso either someone needs to yell at me to say "wait, i'm doing it!" or defer the ceilo one, yeah21:43
ttxcould you look into it with sandywalsh and jd__  ?21:43
russellbmy deferring triggered some yelling :-)21:43
ttxAny question on Nova ?21:43
*** markmc has quit IRC21:43
ttx#topic Cinder status21:43
*** openstack changes topic to "Cinder status (Meeting topic: project)"21:43
jgriffithhosre is back in teh barn21:44
ttx#link https://launchpad.net/cinder/+milestone/havana-321:44
*** armax has left #openstack-meeting21:44
ttx17 tracked blueprints, which is more than you delivered in h221:44
*** benl has joined #openstack-meeting21:44
*** vipul-away is now known as vipul21:44
ttxYou might want to push some of these "Medium" to "High" or "Low" to help prioritizing the review effort, same suggestion than for russellb21:44
jgriffithYeah, but this time we're going to hit them21:44
jgriffithI'll comb through next week21:44
ttxbare-metal-volumes and cinder-nfs-driver-qos need an assignee21:44
jgriffithmost are in progress pushes from H221:44
ttx(you should require an assignee to be set before giving a blueprint a priority)21:44
jgriffiththose will likely be dropped due to lack of interest21:45
ttxcinder-volume-driver-optional-iscsi-support needs to be triaged too21:45
jgriffithbut I need to give folks a chance to speak up tomorrow21:45
ttxsounds good21:45
ttxfinally, db-cleanup (Medium) depends on db-archiving (Low) ?21:45
jgriffithquite frankly that whole thing is a bit of a mess21:45
ttxmaybe adjust prio or remove link if it doesn't make sense21:45
*** alrs has quit IRC21:46
ttxdb-cleanup might be an "ongoing" task21:46
jgriffithI'll adjust, but I'm also not convinced any longer on the whole thing21:46
ttxunless it has clear objectives :)21:46
jgriffithgood point21:46
ttxjgriffith: we have one Nova blueprint blocked on https://review.openstack.org/#/c/30974/ so please give that one some review priority21:46
jgriffithI have reviewed21:46
ttxjgriffith: anything on your mind ? apart from horses breaking out of the barn ?21:47
*** resker has joined #openstack-meeting21:47
jgriffithI'm concerened about encryption and db stuff21:47
jgriffithalso the quota stuff21:47
jgriffiththat merged into oslo before merging in Cinder or noava21:47
jgriffithwhich seems backwards21:47
jgriffithother than that21:47
jgriffithnothing really21:48
ttxonce the code is separated, it doesn't sound backward to implement improvements in oslo and sync them back21:48
*** danwent has joined #openstack-meeting21:48
ttxQuestions on Cinder ?21:48
jgriffithsure, if the code works21:48
ttxjgriffith: indeed21:48
ttx#topic Heat status21:48
*** openstack changes topic to "Heat status (Meeting topic: project)"21:48
ttxshardy: o/21:49
ttx#link https://launchpad.net/heat/+milestone/havana-321:49
shardyI know I need to start bumping (a lot) of stuff21:49
* ttx refreshes21:49
ttx31 tracked blueprints, while you implemented 8 during h1 and 8 during h221:49
ttxThat no longer qualifies as optimism, it's pure madness :)21:49
shardyNot been ready to burst new-contributors bubbles just yet, but yeah21:49
ttxYou definitely need to more liberally use the "Low" priority to designate stuff that "may" make it21:49
shardyto be fair, a lot of stuff has been carried over, specifically the HOT functionality21:50
ttxThat will help in communicating which features are the most likely to land to the rest of the world21:50
shardywhich is all starting to come together, combined with the watch-ceilometer stuff21:50
ttxBecause it's a quite unlikely those 30 will make it, and I prefer to be pleasantly surpised than doing bulk deferrals on feature freeze day21:50
*** esker has quit IRC21:50
*** kspear has joined #openstack-meeting21:50
shardyttx: agree, I'll start getting it into shape after discussions at our meeting tomorrow21:50
ttxYou also have a few waiting to have a priority set:21:50
*** alexb_ has quit IRC21:50
ttxsoftware-configuration-provider, update-stack-new-resource-state, heat-multicloud, oslo-db-support21:50
shardyttx: that is deliberate - those appeared while I was on holiday and I need to discuss whether they just get bumped immediately21:51
ttxIf you push things to "Low" they will disappear from my radar and i'll stop complaining about crazy goals :)21:51
ttxshardy: anything else you want to raise ?21:51
* shardy sets everything to low21:51
ttxthat would be cheating.21:52
shardyno, not atm, will try to get things more realistic for next week :)21:52
ttxQuestions about Heat ?21:52
shardyseem to have herded the cats into a corner atm ;)21:52
*** nati_ueno_2 has quit IRC21:52
ttx#topic Horizon status21:52
*** openstack changes topic to "Horizon status (Meeting topic: project)"21:52
ttxgabrielhurley: feeling better ?21:52
ttx#link https://launchpad.net/horizon/+milestone/havana-321:53
ttx16 tracked blueprints while you got 7 implemented in h2 (and 8 in h1)21:53
ttxSo that's pretty optimistic... though you have about half of them implemented or in review already21:53
gabrielhurleyyeah. I expect some will slip21:53
gabrielhurleythere's a lot with priority "low"21:53
ttxSo you might make it if you do a big review push early on21:53
*** spzala has quit IRC21:53
gabrielhurleycertainly possible21:53
gabrielhurleybut probably optimistic21:54
gabrielhurleyI will refine as we go21:54
ttxHas work started on https://blueprints.launchpad.net/horizon/+spec/rbac ?21:54
gabrielhurleydavid-lyle has it in his head. he may have started code, but he's generally on it.21:54
ttxgabrielhurley: some will slip, but ideally those who slip should be Low ones :)21:55
gabrielhurleythat's the goal21:55
ttxthat's what the roadmap is about: setting expectations as good as we can21:55
ttxgabrielhurley: anything you wanted to mention ?21:55
gabrielhurleynot off the top of my head21:55
*** gyee has quit IRC21:55
ttxQuestions on Horizon ?21:55
ttxLooks like we don't have henrynash, who was supposed to replace dolphm this week21:56
ttxanyone else feeling like defending keystone ?21:56
ttxok, short update for the record21:57
ttx#topic Keystone status21:57
*** openstack changes topic to "Keystone status (Meeting topic: project)"21:57
ttx6 tracked blueprints in havana-3, which is reasonable21:57
ttxendpoint-filtering needs an assignee (or be removed from havana-3)21:57
ttx#topic Incubated projects21:58
*** openstack changes topic to "Incubated projects (Meeting topic: project)"21:58
ttxhub_cap, devananda: news ?21:58
* NobodyCam for devananda "we are still working on it. no real news yet"21:58
ttxhub_cap: how is it going ?21:58
hub_capno real news. ive got the rpm integration almost done as a POC21:58
hub_capa guy from mirantis and someone else both offered to finish it up21:59
hub_capso we shoudl be able to run on ubuntu or fedora images now21:59
hub_capwell, once the reviews land ;)21:59
ttx"Impl Cinder Volume extend for resize volume" is marked essential for your havana release, is it really essential ? As in "won't release without it" ?21:59
hub_capand heat integration is next21:59
hub_capwell ttx, our cli tool and api already have it21:59
hub_capand we impl'd it internally at rax, FAIL22:00
ttxok. Assigning someone to that BP is probably a good idea then :)22:00
hub_capand haomaiwang said he wants to do it i believe22:00
ttxok, time is up, anything else you wanted to mention ?22:00
hub_capill make sure its assigned this wk22:00
* hub_cap hugs everyone22:00
*** apevec has left #openstack-meeting22:00
hub_capthat is all22:00
*** openstack changes topic to "OpenStack meetings || https://wiki.openstack.org/wiki/Meetings"22:00
openstackMeeting ended Tue Jul 30 22:00:37 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2013/project.2013-07-30-21.02.html22:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2013/project.2013-07-30-21.02.txt22:00
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2013/project.2013-07-30-21.02.log.html22:00
ttxThanks everyone!22:00
*** timductive has joined #openstack-meeting22:00
*** ayoung has quit IRC22:01
med_t t x  i s  a  w e l l  o i l e d   m a c h i n e.22:01
*** absubram has joined #openstack-meeting22:01
*** burt has quit IRC22:02
*** kebray has joined #openstack-meeting22:02
*** pcm_ has quit IRC22:03
*** ffive has joined #openstack-meeting22:03
gabrielhurley#startmeeting horizon22:04
openstackMeeting started Tue Jul 30 22:04:02 2013 UTC and is due to finish in 60 minutes.  The chair is gabrielhurley. Information about MeetBot at http://wiki.debian.org/MeetBot.22:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:04
*** openstack changes topic to " (Meeting topic: horizon)"22:04
openstackThe meeting name has been set to 'horizon'22:04
*** ffive has quit IRC22:04
gabrielhurleyhello happy horizoneers22:04
jcoufalhey everybody, hey gabrielhurley22:04
gabrielhurleyI'm thinking this can maybe be a short meeting. I have relatively little to say, but I'll stick around if y'all have topics.22:04
gabrielhurleyI'll take care of the usual business real fast22:05
gabrielhurley#topic overview22:05
*** openstack changes topic to "overview (Meeting topic: horizon)"22:05
*** Vek has left #openstack-meeting22:05
gabrielhurleyLooks like progress is going on track so far for where we're at in the cycle.22:05
gabrielhurleyIdeally we'd see preliminary code for all the big stuff by two weeks from now. That would leave lots of time for review and polish.22:06
gabrielhurleyI'll make sure to spend some time on my blueprints before then.22:06
gabrielhurleyI also did some triage on bugs and blueprints today just to make sure everything's in order. Nothing new or startling to report. All's well.22:06
gabrielhurley#topic blueprints22:06
*** openstack changes topic to "blueprints (Meeting topic: horizon)"22:06
gabrielhurleyme... nothing to report. who else would like to go?22:06
*** meteorfox has joined #openstack-meeting22:07
gabrielhurleydavid-lyle, lcheng, jpich, timductive, etc...?22:07
jcoufalAs for table inline editation BP22:07
timductiveHeat Topology, is up in code review but I haven't had much time to figure out why Jenkins keeps failing, looks like a bug maybe22:07
david-lylestarting rbac, not very far yet, but I'll try to have a pass at it in a week or two22:07
absubramCisco N1K dashboard - I'm just doing some final testing on mine before getting it ready for review22:08
jcoufalAfter various dicussions (thanks for feedback to all) I delivered final design for it22:08
*** changbl has quit IRC22:08
*** alexb_ has joined #openstack-meeting22:08
jcoufalAnd the development on that will (re-)start in next few days22:09
gabrielhurleyjcoufal: yep, I saw your posts to the ML today but haven't read and absorbed yet22:09
gabrielhurleyeveryone else, that all sounds very reasonabe22:09
gabrielhurleyreasonable, even22:09
lchengI've been working on the role assignment to groups.  https://blueprints.launchpad.net/horizon/+spec/group-domain-role-assignment  Split the bp into two, to tackle project and domain role assignment separately. Working on the project role assignment now.22:09
jcoufalgabrielhurley: yeah, in ML are UX discussion oriented things, will talk about them later22:10
gabrielhurleylcheng: I saw that review this morning. it was bigger than I expected so I wanna pull it down and spend a little time with it, but at a glance it looked good22:10
lchengI've realized that I could re-use the JS and template from the Project-User membership step.22:10
lchengBut the would require some time making the JS and template more flexible.22:10
*** rwsu has quit IRC22:11
*** ruhe has quit IRC22:11
*** vipul is now known as vipul-away22:11
gabrielhurleyit might be worth it, given that we still have time and that I assume you'd reuse it again on the domain role BP22:11
lchenggabrielhurley: what's your thought on making changes on the JS/template as part of this bp?22:11
jpichlcheng: We're also reusing it for the security group edit on the instances page, for reference22:11
gabrielhurleyI'd rather see the refactor to make it usable. the more generic that code gets the better22:12
*** meteorfox has quit IRC22:12
lchengjpich: Thanks for the heads-up. I'll make sure it still works after the refactoring.22:12
lchengAnywhere else it is used?22:12
*** vipul-away is now known as vipul22:12
jpichlcheng: I don't believe so. I had to move workflow JS around a bit recently and that's the only 2 places I saw it22:12
kspearlcheng: some of the code is used for a networking component, can't remember which22:13
lchengkspear: okay, I'll check that out.22:13
gabrielhurleycool cool22:14
jpichkspear, lcheng: Probably the NIC selection on the create instance workflow I reckon, though it should be separate now22:14
gabrielhurleyI think that's separate offhand22:14
gabrielhurley'cuz that has all the ordering code, etc.22:14
kspearjpich: ah right, good to know22:14
gabrielhurleyanybody else on blueprints or should I open it up for general discussion?22:15
* kspear has been meaning to fix the js/template naming for a while now22:15
gabrielhurley#topic open discussion22:16
*** openstack changes topic to "open discussion (Meeting topic: horizon)"22:16
gabrielhurleywho wants the floor?22:16
lchenggabrielhurley: do you have update on the release of django_openstack_auth? :-)22:16
gabrielhurleyoh damn.22:17
gabrielhurleyI totally forgot about that22:17
gabrielhurleythank you for asking.22:17
gabrielhurleyI will look into that today22:17
*** jecarey_ has quit IRC22:17
jcoufalIf I can take small place...22:18
jcoufalUX discussions tool22:18
jcoufalthere was no more suggestions for other tools, so I did some more research and posted 2 more tools22:18
lchenggabrielhurley: thanks22:18
jcoufalbased on discussion with Thierry I found out that one of he best candidates might be same tool as aks.openstack.org22:19
gabrielhurleyah, an answerbot/stackoverflow clone. not a bad idea.22:19
*** lbragstad has quit IRC22:20
gabrielhurleycould we even piggyback on ask.openstack.org and use a tag/category/section of some sort?22:20
gabrielhurleyavoid setting up another tool entirely?22:20
jcoufalyeah, something similar, from what I have discovered it matches the best22:20
jcoufalI was thinking about that22:20
jcoufalit might work22:20
jcoufalhowever what I really love is having multiple labels22:20
*** lbragstad has joined #openstack-meeting22:21
jpichFrom my xp with ask.openstack.org it makes conversation difficult if you want to iterate on a concept22:21
jpichCommenting on an answer is limited to 200 characters or something and can't be formatted (or images added)22:21
gabrielhurleytrue, it does keep comments on a particular answer short...22:21
jpichif you make a new reply based on a previous answer, it gets a bit lost as answers move up and down22:21
jcoufaljpich: but can't the discussion happen in answers and comments used really like short 'additions'?22:22
jcoufaljust wondering22:22
jpichI like the rest and the email made good points, but there are downsides, it's not great for conversations, more for "this is THE answer"22:22
jpichjcoufal: Sure, but an answer can only reply to the question, not to each other22:22
gabrielhurleythough it is nice to be able to capture *the* answer once consensus is reached22:22
*** lastidiot has quit IRC22:23
jpichso if you want to add additional informational you have to edit your initial question or answer22:23
gabrielhurleyI don't see that as being so bad22:23
gabrielhurleyI'm not convinced the preservation of all the history is crucial22:23
jcoufalneither do I22:23
jcoufalbut good point, jpich22:23
jpichFair enough :)22:23
jcoufalI didn't think of this before22:23
gabrielhurleyIf we can collectively arrive at a reasonably documented consensus that's pretty good. not perft, but pretty good.22:23
*** michchap has quit IRC22:24
*** michchap has joined #openstack-meeting22:24
jcoufalgabrielhurley: I will wait for Thierry's answer and if it is positive, I will wrap up everything in ML22:24
gabrielhurleyyeah, other opinions are welcome, but this may be the best idea I've heard so far if we're willing to accept that our criteria is more about successful outcomes than the ability for anyone to go revisit the process of how we got there22:25
jcoufalgabrielhurley: we can still make voting happen between discourse and ask.openstack.org what others prefer in the end22:26
jcoufalgabrielhurley: sounds good22:26
*** rwsu has joined #openstack-meeting22:26
*** markmcclain has quit IRC22:26
*** asalkeld has quit IRC22:26
*** sushils has quit IRC22:27
gabrielhurleyother topics?22:27
kspeargabrielhurley: could you ask vishy/russellb nicely for a novaclient release? we have a couple of patches up that need a newer version22:27
absubramgabrielhurley: quick question about the icehouse summit.. do we already have a list of topics/discussions for the design summit?22:27
gabrielhurleyk. will do.22:27
*** dscannell1 has quit IRC22:27
gabrielhurleyabsubram: nope22:27
*** asalkeld has joined #openstack-meeting22:27
*** lbragstad has quit IRC22:27
gabrielhurleythe call for proposals for the design summit will open fairly soon22:27
kspeargabrielhurley: thanks22:28
gabrielhurleyI'll announce it in this meeting plus it'll obviously go out from Thierry on the ML, etc. when it happens22:28
russellbkspear: ack, i haven't done one in forever.  can you email me about it so it's in my queue?22:28
absubramoh ok.. what's tomorrows deadline then? that's different?22:28
gabrielhurleyabsubram: I believe that's for the conference portion22:28
kspearrussellb: will do. noticed the last tag was quite old :)22:28
gabrielhurleykspear: russellb: now I don't have to do anything! yay!22:29
*** dosaboy has quit IRC22:29
kspeargabrielhurley: the system works!22:29
*** dosaboy has joined #openstack-meeting22:30
gabrielhurleyI do still have to cut a django_openstack_auth release for lcheng though..22:30
russellbi lurk in here for things like this, heh22:30
jpichgabrielhurley: Any update/thing I can help with for https://bugs.launchpad.net/horizon/+bug/1182011?22:30
uvirtbotLaunchpad bug 1182011 in horizon "djangojs.po not available on Transifex" [High,Confirmed]22:30
gabrielhurleyjpich: do you have admin access on transifex? if not it shouldn't be hard to get it so you could add the "resource" as transifex calls it22:31
jpichgabrielhurley: I don't. I guess I need to talk to Daisy?22:31
gabrielhurleyif you tell me what you transifex account name is I can probably add you22:31
*** rnirmal has quit IRC22:32
jpichProbably jpichon *checks*22:32
jpichIs there any trickstiness associated with adding a new file?22:32
*** obondarev has quit IRC22:32
gabrielhurleyoh, probably. but I haven't done it in ages22:33
gabrielhurleyyour guess is as good as mine22:33
jpichYep, jpichon22:33
jpichFair enough, I'll poke22:33
kspearwe have some software engineering grad student groups that may be interested in working on openstack for an 11-week course project. if anyone has ideas for blueprints that might fit that schedule please suggest them. horizon or elsewhere22:33
gabrielhurleyjpich: you are added as a maintainer on the Horizon transifex22:34
*** eharney has quit IRC22:34
jpichkspear: Cool! Is that 11 weeks full time or in addition to other coursework?22:34
gabrielhurleykspear: nice!22:34
jpichgabrielhurley: Thanks22:34
*** obondarev has joined #openstack-meeting22:34
kspearjpich: in addition to other coursework22:35
kspearthe main thing i'm looking for is some flexibility in design and a decent block of work22:35
kspearand low spin-up22:35
kspearnothing in the horizon list currently jumps out at me22:35
jcoufalkspear: great, how experienced are they? what type of work would you expect?22:36
gabrielhurleykspear: I'll have a look to. could you email me so I have it in my todo list?22:36
jpichinbox as todo list :)22:36
kspeargabrielhurley: sure22:36
*** ivasev has quit IRC22:36
gabrielhurleysad but true. thanks.22:37
kspearjcoufal: i still need to talk to the supervisor to get more detail. fairly experienced though i would think22:37
*** sushils has joined #openstack-meeting22:37
jcoufalkspear: ok, could you include me in the list of receivers of further information as well, please :)22:38
kspeargabrielhurley: i'll email myself to remind me to email you and russellb22:38
jpichlol :P22:38
kspearjcoufal: will do22:38
*** vipul is now known as vipul-away22:39
jpichFYI, there are now a couple of basic horizon tests in the tempest gate so hopefully stuff like https://bugs.launchpad.net/horizon/+bug/1203001 will be caught before it breaks us from now on22:39
uvirtbotLaunchpad bug 1203001 in python-novaclient "TypeError: __init__() got an unexpected keyword argument 'project_id'" [Undecided,Fix committed]22:39
gabrielhurleyyep, that's excellent22:39
kspearjpich: nice22:40
jcoufaljpich: sweet22:41
gabrielhurleygreat. this has been a very productive meeting. I'll let you folks in other timezones get back to your normal lives. thanks for everything!22:42
*** openstack changes topic to "OpenStack meetings || https://wiki.openstack.org/wiki/Meetings"22:42
openstackMeeting ended Tue Jul 30 22:42:28 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-07-30-22.04.html22:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-07-30-22.04.txt22:42
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-07-30-22.04.log.html22:42
jcoufalThanks, see you later all22:43
kspearbye all22:43
absubramthanks.. later!22:43
kspearha, now i get to go to work22:43
*** vipul-away is now known as vipul22:43
*** jpich has quit IRC22:44
*** jcoufal has quit IRC22:44
*** gabrielhurley has quit IRC22:44
*** timductive has left #openstack-meeting22:44
*** anteaya has quit IRC22:45
*** galstrom is now known as galstrom_zzz22:46
*** kspear has quit IRC22:46
*** EmilienM has quit IRC22:47
*** EmilienM has joined #openstack-meeting22:52
*** ffive has joined #openstack-meeting22:55
*** rods has quit IRC22:56
*** lbragstad has joined #openstack-meeting22:57
*** otherwiseguy has quit IRC22:57
*** krtaylor has quit IRC22:57
*** gyee has joined #openstack-meeting22:59
*** danwent has quit IRC23:00
*** sushils has quit IRC23:00
*** vipul is now known as vipul-away23:01
*** sushils has joined #openstack-meeting23:02
*** carl_baldwin has left #openstack-meeting23:02
*** emagana has quit IRC23:05
*** aclark_ has quit IRC23:08
*** gyee has quit IRC23:10
*** nati_ueno_2 has joined #openstack-meeting23:12
*** sandywalsh has quit IRC23:14
*** Tacho has quit IRC23:14
*** gyee has joined #openstack-meeting23:16
*** sushils has quit IRC23:16
*** IlyaE has quit IRC23:16
*** IlyaE has joined #openstack-meeting23:17
*** salv-orlando has quit IRC23:19
*** sushils has joined #openstack-meeting23:19
*** Mandell has quit IRC23:19
*** alexpilotti has joined #openstack-meeting23:20
*** Mandell has joined #openstack-meeting23:20
*** Mandell has quit IRC23:21
*** gyee has quit IRC23:22
*** gyee_ has joined #openstack-meeting23:22
*** reed has quit IRC23:23
*** reed has joined #openstack-meeting23:24
*** sean_s has joined #openstack-meeting23:26
*** mrodden has quit IRC23:27
*** IlyaE has quit IRC23:32
*** ffive has quit IRC23:32
*** markwash has quit IRC23:32
*** nati_ueno_2 has quit IRC23:33
*** bill has joined #openstack-meeting23:34
*** Toshi has quit IRC23:34
*** bill is now known as Guest9414523:34
*** fnaval_ has quit IRC23:35
*** vipul-away is now known as vipul23:35
*** diogogmt_ has joined #openstack-meeting23:36
*** benl has quit IRC23:36
*** diogogmt has quit IRC23:36
*** diogogmt_ is now known as diogogmt23:36
*** colinmcnamara1 has joined #openstack-meeting23:37
*** absubram has quit IRC23:38
*** colinmcnamara has quit IRC23:38
*** mrodden has joined #openstack-meeting23:39
*** sean_s has quit IRC23:40
*** gyee_ has quit IRC23:45
*** sean_s has joined #openstack-meeting23:46
*** sandywalsh has joined #openstack-meeting23:46
*** dhellmann is now known as dhellmann_23:50
*** lbragstad_ has joined #openstack-meeting23:51
*** alrs has joined #openstack-meeting23:53
*** virajh has quit IRC23:56
*** armax has joined #openstack-meeting23:59

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