Tuesday, 2012-11-06

*** openstack has joined #openstack-meeting06:37
*** ChanServ sets mode: +o openstack06:37
*** bourke has quit IRC06:41
*** bourke has joined #openstack-meeting06:41
*** jfriedly has quit IRC06:50
*** zhuadl_ has joined #openstack-meeting07:00
*** zhuadl has quit IRC07:02
*** zhuadl_ is now known as zhuadl07:02
*** markwash has quit IRC07:06
*** eglynn has joined #openstack-meeting07:06
*** garyk has joined #openstack-meeting07:10
*** metral has joined #openstack-meeting07:27
*** zhuadl has quit IRC07:32
*** markwash has joined #openstack-meeting07:33
*** metral_ has joined #openstack-meeting07:35
*** metral has quit IRC07:39
*** metral_ is now known as metral07:39
*** markwash has quit IRC07:39
*** anniec has joined #openstack-meeting07:57
*** eglynn has quit IRC08:07
*** littleidea has quit IRC08:22
*** afazekas has joined #openstack-meeting08:25
*** uncleofthestick has joined #openstack-meeting08:25
*** eglynn has joined #openstack-meeting08:27
*** afazekas has quit IRC08:29
*** metral has quit IRC08:33
*** salv-orlando has joined #openstack-meeting08:34
*** eglynn_ has joined #openstack-meeting08:34
*** eglynn has quit IRC08:35
*** eglynn_ has quit IRC08:41
*** alexpilotti has joined #openstack-meeting08:42
*** reed has joined #openstack-meeting08:43
*** reed has quit IRC08:45
*** reed has joined #openstack-meeting08:45
*** danwent has quit IRC08:49
*** jakedahn is now known as jakedahn_zz08:56
*** alexpilotti has quit IRC09:04
*** nijaba has quit IRC09:08
*** nijaba has joined #openstack-meeting09:08
*** nijaba has quit IRC09:08
*** nijaba has joined #openstack-meeting09:08
*** jhenner has joined #openstack-meeting09:16
*** derekh has joined #openstack-meeting09:18
*** Mandell has quit IRC09:20
*** darraghb has joined #openstack-meeting09:24
*** rafaduran has joined #openstack-meeting09:36
*** anniec has left #openstack-meeting09:42
*** lianhao has quit IRC09:44
*** rafaduran1 has joined #openstack-meeting09:57
*** rafaduran has quit IRC09:58
*** rafaduran has joined #openstack-meeting10:00
*** rafaduran has left #openstack-meeting10:00
*** asalkeld is now known as asalkeld_afk10:01
*** rafaduran1 has quit IRC10:02
*** eglynn_ has joined #openstack-meeting10:09
*** reed has quit IRC10:22
*** reed has joined #openstack-meeting10:25
*** alexpilotti has joined #openstack-meeting10:29
*** rushiagr1 has joined #openstack-meeting10:41
*** rafaduran has joined #openstack-meeting10:43
*** rushiagr has quit IRC10:43
*** davidha has quit IRC10:48
*** nsavin has quit IRC10:59
*** maurosr has joined #openstack-meeting11:02
*** rushiagr1 is now known as rushiagr11:16
*** rafaduran has left #openstack-meeting11:30
*** goldfish has quit IRC11:31
*** davidha has joined #openstack-meeting11:38
*** goldfish has joined #openstack-meeting11:46
*** gongysh has quit IRC12:08
*** roadTripper has joined #openstack-meeting12:11
*** EmilienM has joined #openstack-meeting12:12
*** salv-orlando has quit IRC12:16
*** gongysh has joined #openstack-meeting12:35
*** littleidea has joined #openstack-meeting12:49
*** goldfish has quit IRC12:50
*** littleidea has quit IRC12:50
*** markvoelker has joined #openstack-meeting13:00
*** jrd has joined #openstack-meeting13:00
*** jaypipes has joined #openstack-meeting13:01
*** tgall_foo has joined #openstack-meeting13:22
*** samkottler is now known as samkottler|bbl13:28
*** dwcramer has joined #openstack-meeting13:30
*** sandywalsh has joined #openstack-meeting13:35
*** tgall_foo has quit IRC13:43
*** annegentle__ has joined #openstack-meeting13:46
*** annegentle___ has joined #openstack-meeting13:47
*** dendrobates is now known as dendro-afk13:48
*** annegentle__ has quit IRC13:51
*** salv-orlando has joined #openstack-meeting14:00
*** samkottler|bbl is now known as samkottler14:01
*** mtreinish has joined #openstack-meeting14:03
*** jfriedly has joined #openstack-meeting14:03
*** dhellmann has joined #openstack-meeting14:05
*** salv-orlando has quit IRC14:05
*** salv-orlando has joined #openstack-meeting14:06
*** littleidea has joined #openstack-meeting14:07
*** jfriedly has quit IRC14:13
*** ryanpetrello has joined #openstack-meeting14:17
*** dwcramer has quit IRC14:17
*** rkukura has joined #openstack-meeting14:19
*** dwcramer has joined #openstack-meeting14:31
*** tgall_foo has joined #openstack-meeting14:32
*** tgall_foo has joined #openstack-meeting14:32
*** rushiagr has quit IRC14:32
*** jfriedly has joined #openstack-meeting14:40
*** sandywalsh has quit IRC14:40
*** dprince has joined #openstack-meeting14:40
*** Hitesh has joined #openstack-meeting14:47
*** dwcramer has quit IRC14:57
Hiteshalexpilotti: Hi14:59
*** primeministerp has joined #openstack-meeting15:02
*** jhenner1 has joined #openstack-meeting15:04
*** jhenner has quit IRC15:04
*** Gordonz has joined #openstack-meeting15:04
*** john5223 has joined #openstack-meeting15:06
*** luis_fdez has joined #openstack-meeting15:06
*** Gordonz has quit IRC15:09
*** Gordonz has joined #openstack-meeting15:10
*** markmcclain has joined #openstack-meeting15:11
*** dolphm has joined #openstack-meeting15:16
*** dolphm has quit IRC15:16
*** dolphm has joined #openstack-meeting15:20
*** cp16net is now known as cp16net|away15:20
*** cp16net|away is now known as cp16net15:20
*** Hitesh has quit IRC15:23
*** cp16net is now known as cp16net|away15:30
*** cp16net|away is now known as cp16net15:30
*** gongysh has quit IRC15:34
*** dwcramer has joined #openstack-meeting15:36
*** jfriedly has quit IRC15:37
*** littleidea has quit IRC15:39
*** colinmcnamara has joined #openstack-meeting15:53
*** colinmcnamara has quit IRC15:57
primeministerp#startmeeting hyper-v15:59
openstackMeeting started Tue Nov  6 15:59:42 2012 UTC.  The chair is primeministerp. Information about MeetBot at http://wiki.debian.org/MeetBot.15:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:59
openstackThe meeting name has been set to 'hyper_v'15:59
primeministerphi everyone15:59
primeministerpthere's a bunch of things to discuss today16:00
EmilienMo/16:00
primeministerpEmilienM: yes?16:00
primeministerpEmilienM: something to add?16:00
EmilienMnothing, good morning :)16:00
*** markwash has joined #openstack-meeting16:00
primeministerpo hi16:00
primeministerp;)16:00
primeministerpok16:01
primeministerplet's begin16:01
primeministerp#topic Current issues16:01
*** openstack changes topic to "Current issues"16:01
primeministerpso people have experiencing problems with cloudinit on linux16:01
primeministerpI was hoping the folks from ibm could share16:01
*** pnavarro has joined #openstack-meeting16:01
primeministerppnavarro: pedro16:02
pnavarrohi all !16:02
primeministerphi pedro16:02
*** josecastroleon has joined #openstack-meeting16:02
primeministerpjosecastroleon: hi jose16:02
josecastroleonprimeministerp: hi16:03
pnavarrohola josecastroleon16:03
josecastroleonpnavarro: hola :)16:03
alexpilottihi everybody!16:03
primeministerpjosecastroleon: we were just about talk about the magic ip/cloudinit issues16:03
ociuhanduhi all16:03
josecastroleoncool16:03
primeministerpI was hoping to have the others from ibm16:04
primeministerpon the channel16:04
primeministerpjosecastroleon: I know you were thinking about using a vswitch plugin to deal with the problem16:04
alexpilottijosecastroleon: you giuy are curently running cloud-init on Linux instances on Hyper-V?16:04
josecastroleonprimeministerp: I think it's less intrusive16:05
*** maurosr has quit IRC16:05
josecastroleonalexpilotti: not on hyperv16:05
alexpilottijosecastroleon: did u try on hyper-v?16:05
primeministerpthey are running only windows on hyperv16:05
josecastroleonalexpilotti: I didn't have time to build the sample16:05
alexpilottijosecastroleon: ok tx16:05
josecastroleonbut it should be the same16:06
alexpilottiIMO we can already starting supporting it, I don't see many issues there.16:06
alexpilottiociuhandu is testing it16:06
josecastroleoncool16:06
josecastroleoni was checking the code in cloud-init, and i didn't find any hardware specific part16:07
alexpilottithe magic IP is now a Quantum L3 thing16:07
primeministerpalexpilotti: do you mind laying out the key issues16:07
primeministerpalexpilotti: you've been working w/ the ibm folks on16:07
alexpilottiprimeministerp: the IBM folks are going to test it tomorrow, today they just asked about the status16:08
alexpilottiprimeministerp: for now we'll just go with the ugly route, as we have no nova-network and no quantum… for the next 2 weeks :-)16:08
primeministerpok16:08
alexpilottimy proposal is to go with the KVP extensions we talked about in SD and in josecastroleon's email16:09
alexpilottiwe can just read the metadata host / port and inject it into the guest16:10
*** maurosr has joined #openstack-meeting16:10
primeministerpok16:11
alexpilottihas anybody other ideas on the subject?16:11
primeministerpjosecastroleon: anything to add?16:11
pnavarroalexpilotti: another idea would be to use configdriveV216:11
josecastroleonit's not difficult to include it on cloud-init16:11
josecastroleonbut there is no HW specific stuff on it16:12
pnavarroalexpilotti: but I've never used it16:12
alexpilottipnavarro: sounds good16:12
primeministerpultimately we probably should support config drive correct?16:12
primeministerpok16:13
primeministerpare we all good on the status16:13
primeministerpof the cloudinit bits16:13
alexpilottipnavarro: I'm going to look at it16:13
primeministerpshould we talk more on the implementation of the windows side while on the topic?16:14
primeministerpi'll take that as a no...16:15
primeministerp;)16:15
primeministerpok16:15
alexpilottiI'd check the config drive 2 and see how OS independent it is etc16:15
primeministerp#topic cinder16:15
*** openstack changes topic to "cinder"16:15
primeministerppnavarro: have you commited the new wmi based cinder work?16:16
primeministerppnavarro: if not when can we expect to see it get commited?16:16
*** markwash has quit IRC16:16
primeministerppnavarro: ping16:17
pnavarroprimeministerp: well, the code is committed in my repository, let me some days to test it with grizzly16:17
primeministerppnavarro: ok16:17
alexpilottipnavarro: great, can't wait16:18
primeministerppnavarro: I'd love to see it in for the g1 timeframe16:18
primeministerppnavarro: hopefully we can have that and the  inital quantum bits in time16:18
*** dendro-afk is now known as dendrobates16:18
alexpilottipnavarro: what do we do with teh old one? We just deprecate it?16:18
alexpilottipnavarro: g-1 is in 2 weeks! :-)16:19
alexpilottipnavarro: the fix for teh current Cinder client just went through: https://review.openstack.org/#/c/15337/16:19
pnavarroalexpilotti: yes, the evenlet issues makes us to have no choice but to deprecate it16:20
alexpilottipnavarro: yeah, as soon as we can commit it we can even remove the fix16:20
pnavarroalexpilotti: I got it16:20
alexpilottipnavarro: problem is that we'll need that fix anytime we will need to use subprocess.Popen16:21
alexpilottipnavarro: with pipes16:21
pnavarroalexpilotti: We hope to not use it anymore16:21
*** danwent has joined #openstack-meeting16:21
alexpilottipnavarro: in all the openstack projects? hmmm16:21
primeministerpinteresting16:22
alexpilottipnavarro: I started a bug in eventlet16:22
primeministerpalexpilotti: good16:22
primeministerpshould we discuss the quantum doc alessandro sent around?16:22
*** mnewby has joined #openstack-meeting16:23
primeministerp#topic quantum16:23
*** openstack changes topic to "quantum"16:23
primeministerpalessandro circulated a document w/ outlining ideas on quantum16:23
alexpilottihttps://bitbucket.org/which_linden/eventlet/issue/132/eventletmonkey_patch-breaks16:23
primeministerp#link https://bitbucket.org/which_linden/eventlet/issue/132/eventletmonkey_patch-breaks16:24
primeministerppnavarro: thoughts on quantum?16:24
alexpilottithere's more to add on the implementation side16:24
*** woodspa has joined #openstack-meeting16:24
alexpilottibeside the high level ideas in the doc16:24
pnavarroprimeministerp: well... in general I agree Dan that the we should have an incremental approach16:25
primeministerppnavarro: i agree as well16:25
*** maoy has joined #openstack-meeting16:27
pnavarroit's a good document to start talking but we should plan a meeting to talk about implementation details16:27
alexpilottipnavarro: when do you want to meet? I plan to release the first version in max 2 weeks16:27
pnavarrothursday it's ok for me16:28
alexpilottipnavarro: with an ambitious idea to make it for g-1 :-)16:28
alexpilottipnavarro: great! time?16:28
*** dolphm has quit IRC16:28
primeministerppnavarro: send a meeting request if possible16:29
pnavarrolate at night16:29
*** hemna has joined #openstack-meeting16:29
pnavarrowhen my children are sleeping16:29
pnavarroI'll send a meeting request16:29
alexpilottiis there anybody elese that would like to join me and pnavarro?16:29
pnavarrook16:29
primeministerp#topic general discussion16:29
*** openstack changes topic to "general discussion"16:29
*** glauaguiar has joined #openstack-meeting16:29
primeministerpanyone have anything else to add16:29
*** jfriedly has joined #openstack-meeting16:29
pnavarroguys, I have to leave16:29
primeministerpjosecastroleon: how are things at cern these days16:30
alexpilottiif not pnavarro just call me on Skype whenever you wish and we set it up :-)16:30
primeministerppnavarro: thx pedro16:30
josecastroleonsee you16:30
pnavarrociao16:30
alexpilottibye!16:30
EmilienMbye pedro16:30
luis_fdezprimeministerp: I´ve a small patch to fix the disk stats16:30
primeministerpluis_fdez: great16:30
pnavarrojust a quick note, yesterday I presented Hyper-V in the meetup Paris16:30
primeministerppnavarro: o awesome!16:30
alexpilottipnavarro: did they like it? :-)16:31
EmilienMwe actually did :)16:31
alexpilottilol16:31
pnavarroyeah, there were even some people interesed as an alternative to MS private cloud16:32
alexpilottiluis_fdez: can you past the fix?16:32
EmilienMpeople was quite curious16:32
primeministerpgreat16:32
luis_fdezyes alexpilotti, i´ll send you the patch file and take a look16:32
alexpilottipnavarro EmilienM: how many people showed up?16:32
primeministerpEmilienM: were there slides?16:32
pnavarrosorry, I'll lose my bus if i'm not leaving now16:32
alexpilottiluis_fdez: consider also that there's a fix for the stats16:32
EmilienMalexpilotti: about 25 people was here.16:32
primeministerppnavarro: go16:32
primeministerpEmilienM: that's good16:33
*** blamar has joined #openstack-meeting16:33
alexpilottiguys I have also a meeting right now16:33
primeministerpok gues16:33
primeministerper guys16:33
primeministerpending the meeting then16:33
primeministerp#endmeeting16:33
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"16:33
openstackMeeting ended Tue Nov  6 16:33:42 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:33
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2012/hyper_v.2012-11-06-15.59.html16:33
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2012/hyper_v.2012-11-06-15.59.txt16:33
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2012/hyper_v.2012-11-06-15.59.log.html16:33
*** josecastroleon has quit IRC16:35
*** woodspa has quit IRC16:35
luis_fdez\quit16:35
*** luis_fdez has quit IRC16:36
*** rnirmal has joined #openstack-meeting16:36
*** pnavarro has quit IRC16:37
*** dwcramer has quit IRC16:37
*** jrd has quit IRC16:38
*** heckj has joined #openstack-meeting16:40
*** zbitter has quit IRC16:41
*** dolphm has joined #openstack-meeting16:43
*** garyk has quit IRC16:43
*** samkottler is now known as samkottler|bbl16:45
*** mtreinish has quit IRC16:56
*** edgarmagana has joined #openstack-meeting16:58
*** rushiagr has joined #openstack-meeting16:59
*** garyk has joined #openstack-meeting17:01
edgarmaganaall: is the LBaaS meeting in this channel?17:02
*** jfriedly has quit IRC17:05
*** jfriedly has joined #openstack-meeting17:05
*** woodspa has joined #openstack-meeting17:06
*** lloydde has joined #openstack-meeting17:06
*** edgarmagana has quit IRC17:07
*** EmilienM has left #openstack-meeting17:08
*** edgarmagana has joined #openstack-meeting17:11
*** gyee has joined #openstack-meeting17:11
*** dwcramer has joined #openstack-meeting17:14
edgarmaganaall: still wondering where is the LBaaS meeting  :-)17:14
*** markwash has joined #openstack-meeting17:17
*** rushiagr has quit IRC17:17
*** jfriedly has quit IRC17:19
alexpilottijgriffith: hi!17:19
alexpilottijgriffith: I noticed that python-cinderclient doesn't have a openstack-common.conf17:20
alexpilottijgriffith: sorry, wrong chat room :-)17:20
*** jfriedly has joined #openstack-meeting17:20
*** woodspa has quit IRC17:23
*** dolphm has quit IRC17:24
*** dolphm has joined #openstack-meeting17:25
*** jfriedly has quit IRC17:28
*** shengjie has joined #openstack-meeting17:29
*** shengjie has quit IRC17:29
*** shengjie has joined #openstack-meeting17:32
edgarmagana..17:42
*** SumitNaiksatam has joined #openstack-meeting17:46
*** s0mik has joined #openstack-meeting17:47
garykedgarmagana: http://wiki.openstack.org/Quantum/LBaaS#Mettings17:48
*** lloydde has quit IRC17:48
edgarmaganagaryk: thanks!17:50
enikanorovedgarmagana:17:51
edgarmaganagoing to openstack-dev17:51
enikanorovin 5mins at #openstack-dev17:51
*** edgarmagana has quit IRC17:51
*** marek_ has joined #openstack-meeting17:52
*** SumitNaiksatam has quit IRC17:53
*** SumitNaiksatam has joined #openstack-meeting17:53
*** mtreinish has joined #openstack-meeting17:55
*** markwash has quit IRC17:58
*** davidha has quit IRC17:59
dolphmheckj: time change?18:00
heckjyep18:00
heckjKeystone meeting!!!18:00
heckjo/18:00
heckj#startmeeting keystone18:00
openstackMeeting started Tue Nov  6 18:00:46 2012 UTC.  The chair is heckj. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
openstackThe meeting name has been set to 'keystone'18:00
*** SumitNaiksatam has quit IRC18:00
heckjagenda at http://wiki.openstack.org/Meetings/KeystoneMeeting18:01
heckj#link http://wiki.openstack.org/Meetings/KeystoneMeeting18:01
*** jfriedly has joined #openstack-meeting18:01
heckj#topic high priority issues18:02
*** openstack changes topic to "high priority issues"18:02
heckjWe've got some reviews passing through to fix inadvertant breakage after we merged the V3 keystoneclient branch18:02
ayoung\O/18:02
*** samkottler|bbl is now known as samkottler18:02
heckjyeah!!!18:02
*** jog0 has joined #openstack-meeting18:02
heckjdolphm will be back in a minute or so18:03
ayoung#link https://review.openstack.org/#/c/15516/118:03
ayoung#link https://review.openstack.org/#/c/15513/118:03
heckjwhile we're chilling - ayoung, what's the hierarchical data that's current in attributes? I thought that was mostly flat18:03
ayoung#link https://bugs.launchpad.net/keystone/+bug/107537618:03
uvirtbot`Launchpad bug 1075376 in keystone "keystoneclient unit tests fails on update tenants and users" [Critical,In progress]18:03
ayoungheckj, let me look,  I think it is the role assignments18:03
*** markwash has joined #openstack-meeting18:04
heckjayoung: ahh.. yeah, it think that gets populated out in lists, good point - would be good to do that separately18:04
dolphmo/18:04
ayoungheckj, regardless, getting password and enabled out in one patch along with the other normalized fields would be a good thing (tm)18:04
ayounglets not ask for a 100% solution up front18:05
ayoungIf we can go completely normalized in one pass, great18:05
dolphmayoung: migrations on existing data will be the tricky part there, especially for enabled18:05
heckjayoung: definitely18:05
*** bme has joined #openstack-meeting18:06
ayoungdolphm, nah, it should be pretty straightforward.  Once we accept that we are parsing JSON, which are the True values for enabled should be pretty clear18:06
heckjdolphm: yep - we'll want to make sure we can smoothly migrate that out18:06
*** jrd has joined #openstack-meeting18:06
heckjayoung: I was triaging bugs yesterday - at least a few that you files are better as blueprints - made note of such in the bug18:07
*** eglynn_ has quit IRC18:07
ayoungheckj, that is fine18:07
dolphmayoung: enabled='mondays'18:07
*** debo_os has joined #openstack-meeting18:07
heckjenabled="every third thursday"18:08
gyeewtf?18:08
ayoungdolphm, I'm more of the Arthur Dent school disabled="Thursdays"18:08
gyeeyou  serious?18:08
dolphmgyee: exactly18:08
dolphmlol18:08
heckjgyee: sure! Why not :-)18:08
dolphmgyee: users are creative18:08
heckjsorry, getting back to topics18:08
gyeeI mean you seen such data?18:08
dolphmand the client is like "awesome, Enabled: Thursdays... got it."18:08
heckj#topic Keystone-v3 feature branch merge18:09
*** openstack changes topic to "Keystone-v3 feature branch merge"18:09
heckjso aside from screwing the tests in keystone, we have the python-keystoneclient updated with V3 parts in place18:09
* dolphm apologizes for not testing client feature/keystone-v3 against server master :(18:09
heckjtests (and bad assumptions) getting fixed up now - so now we're just pending getting keystone V3 into place18:09
heckjdolphm: since you submitted most of those change sets, how would you like to move that forward?18:10
heckjdolphm: do you want to merge what we can, and then re-submit the remaining against master, or do it all in a feature branch and update that?18:10
*** derekh has quit IRC18:10
*** jhenner1 has quit IRC18:10
*** garyk has quit IRC18:11
heckjgyee: I'm assuming getting that merged into master is blocking you on the stop-id components18:11
dolphmheckj: fix current issues ASAP, merge keystone server feature/keystone-v3, fix any unknowns, rebase pending v3 changes on master and re-review them18:11
gyeeheckj, I can do it in master18:11
*** garyk has joined #openstack-meeting18:12
dolphmgyee: there's no v3 API in server master..?18:12
heckjgyee: not yet anyway18:12
dolphmgyee: middleware fix or something?18:12
gyeeboth middleware and backend18:12
dolphmgyee: can you give a quick rundown on your approach?18:13
gyeemiddleware set the token in the header for token validation18:13
gyeebackend get it from the header18:13
heckjgyee: we'll want to time the middleware so that we don't screw up henrynash' work in moving auth_token into keystoneclient18:13
gyeeshould be pretty trivial change18:13
dolphmgyee: ah, i was thinking middleware on top of the keystone server (not referring to auth_token)18:13
gyeeshould I do it in the v3 branch?18:14
heckjgyee: probably easiest to do it in master after we land the V3 branch18:14
dolphmgyee: keystone server changes, yes18:14
gyeek, I'll wait then18:14
heckjif you can do the middleware separately (auth_token, yes), then if you have that ready to go ASAP, that might be worthwhile - get it in before we start trying to shift that to keystonelcient18:15
dolphmgyee: are you using X-Subject-Token? (is that what it's called in the v3 spec? lol)18:15
gyeedolphm, how about I make the header configurable?18:15
gyeeX-Thuesday if you want :)18:16
dolphmgyee: it needs to be spec'd18:16
dolphmgyee: and actually, support in keystoneclient v3 auth is where this should really go :-/18:16
dolphmgyee: auth_token should just be refactored to support the client, and not care about the api details18:16
gyeeI need to be very careful about refactoring middleware again as HP is extending them18:17
gyeeI am sure there are others18:17
ayoungso gyee what kind of extensions?  Is this generalizable stuff?18:18
dolphmgyee: keystone.middleware.auth_token won't be refactored necessarily, it should just be deprecated and eventually removed, in favor of keystoneclient.middlware.whatever_the_new_name_is which utlizes the client itself18:18
gyeewe are extending middleware class interface18:19
dolphmgyee: auth_token's or keystone.wsgi.Middlware?18:19
gyeeauth_token18:19
gyeedolphm, right, namespace change is a lot easier than class interface change18:20
ayounggyee, so once this moves to keystoneclient, it should just require you to update the import18:20
dolphmgyee: i'm thinking both at once18:20
*** sharis has joined #openstack-meeting18:20
ayoungwhat are we changing in the interface?18:20
gyeedolphm, you mean pluggable auth?18:21
gyeeI am trying to understand  what "both" means18:22
dolphmthere's a couple interfaces here... gyee is concerned about auth_token's class interface18:22
*** bme has left #openstack-meeting18:22
*** sarob has joined #openstack-meeting18:23
dolphmauth_token's interface to the wsgi pipeline is stable and won't break backwards-compatibility18:23
ayoungdolphm, whew18:23
ayoungI was worried I missed something key there.18:23
dolphmmoving auth_token into the client means new namespace and freedom to refactor the class itself... though, i don't have anything in mind18:24
*** eglynn_ has joined #openstack-meeting18:24
ayoungheckj, did you incorporate everyone's input into some sort of overall development scheme?18:24
dolphmgyee: and i'm sure HP would have some feedback on how that class interface should be structured to be more easily extensible?18:25
gyeedolphm, yes, should I create a BP?18:25
heckj#topic Upcoming contribution plans for Grizzly18:25
*** openstack changes topic to "Upcoming contribution plans for Grizzly"18:25
dolphmgyee: that'd be awesome18:25
heckj#link https://etherpad.openstack.org/keystone-grizzly-plans18:25
ayoungdolphm, we have a load of work in the queue.  I would avoid adding18:25
dolphmayoung: it needs to happen in grizzly anyway, to support v318:26
*** cp16net is now known as cp16net|away18:26
heckjyeah, we've got a serious pile of work building up here18:26
heckjI took everyone's feedback and tossed it all into that etherpad18:26
heckjThierry is asking for a generalized "what folks are doing" from all the PTLs - that's why I'm trying to consolidate that18:27
heckjI also went through bugs yesterday, triaged them up to a first pass, and nailed some of the blueprints against milestones for an initial cut18:27
ayoungheckj, so  Alvaro Lopez is helping on the refactoring for Authenticate .18:28
ayoungLet me update that18:28
gyeewe have some more requirements for delegation18:28
heckjI have some pieces targetted against grizzly-1 https://launchpad.net/keystone/+milestone/grizzly-118:28
heckj#link https://launchpad.net/keystone/+milestone/grizzly-118:28
gyeesomeone from HP will create a BP, just a heads up18:28
*** jfriedly has quit IRC18:28
heckjayoung: thanks18:29
heckjWe have a couple of blueprints that need to be created yet18:29
*** Mandell has joined #openstack-meeting18:29
heckjneed one around: authentication & token validation abstraction18:29
gyeemeh18:29
heckjgyee: you were talking about creating one for service and endpoint scoping I think18:30
gyeeyes18:30
gyeethat too18:30
heckjdolphm: and you had one pending around schema validation18:30
dolphmheckj: pending creating a bp?18:30
heckjdolphm: do you already have a BP around the schema validation work you proposed a meeting or two back?18:30
dolphmheckj: no, drafting it now :)18:31
heckjdolphm: just meant that a BP was needed, but didn't exist yet18:31
heckjcool18:31
gyeedolphm, having schema validation will be awesome18:31
*** mnewby_ has joined #openstack-meeting18:32
heckjpluggable auth, moving auth_token, and the merging of V3 is all the earliest pre-req stuff as far as I can see18:32
ayoungheckj, that is my take on it18:32
heckjsounds right18:32
heckjayoung: you had some general elements under PKI moving forward - pieces that can be done in parallel - should that be a BP to track it?18:33
heckj(add signing user, policy rules for enforcing signed user, etc)18:33
ayoungheckj, PKI future should cover it. I don't think it calls for another BP18:33
heckjPKI Future - cool - will add that link in etherpad18:34
ayoungBut instead probably should add the details18:34
gyeePKI is a big umbrella18:34
*** danwent has quit IRC18:34
ayounghttps://etherpad.openstack.org/keystone-pki-future18:34
heckjayoung: uh - being blind - not seeing BP in https://blueprints.launchpad.net/keystone18:35
heckjdid you create on there, or is it just in the etherpad link?18:35
ayoungheckj, hmm...thought It was there18:35
*** mnewby has quit IRC18:35
*** mnewby_ is now known as mnewby18:35
heckjayoung: that list is *huge* - I think it really needs to be broken down if we want to get you help with it and lay it out against milestones in grizzly...18:35
heckjI'd be happy to break it apart for you if you want...18:36
heckjsome others have already put in blueprints that overlap with some of this18:36
ayoungGuess I didn't add it18:36
ayoungheckj, True.18:37
heckjpre-auth, keystone-explicit-impersonation, delegation18:37
dolphm#link https://blueprints.launchpad.net/keystone/+spec/client-side-request-response-validation18:37
ayoungheckj, lot of it is under delegation18:37
ayoung#link https://blueprints.launchpad.net/keystone/+spec/delegation18:37
*** eglynn_ has quit IRC18:37
heckjkk - I'll start with it under delegation, and we can break out pieces that don't fit from there if we need18:37
ayoungwhich should then link the the etherpad on PKI future18:37
ayoungheckj, yeah18:37
gyeewe have more requirements for delegation18:38
heckjjust added to whiteboard18:38
gyeeprobably will add our comments there18:38
gyeeyeah18:38
*** sandywalsh has joined #openstack-meeting18:38
heckjthere's also a wiki page that David added linked up : http://wiki.openstack.org/keystone/Delegation18:38
*** jfriedly has joined #openstack-meeting18:39
heckjgiven how much is laid out in delegation, looks like that's Grizzly-2 or grizzly-3.18:40
ayoungheckj, yes, that is the link for the full specification.  I Need to move things from the Etherpad to there18:40
heckjWe probably need to pick some specific milestone deliverable for it to step forward between the two milestones18:40
heckjkk18:41
ayoungheckj, perhaps.  A lot depends on how much churn we have in other bugs, and whether I can get some time working on it heads down18:41
ayoungI knew that wehen we flipped to PKI tokens it would cause some new issues to rise to the surface18:41
heckjayoung: would you like me to start with asserting it as grizlzly-2 and being aggressive with the planning for it?18:41
heckjayoung: or defer to grizzly-3 and give us a few more weeks in there18:41
dolphmheckj: link to dates on those?18:42
ayoungheckj, what are the cut off dates?18:42
heckj#link http://wiki.openstack.org/GrizzlyReleaseSchedule18:42
heckjgrizzly-1 is basically thanksgiving18:42
heckjgrizzly-2 is jan 10th18:42
heckjgrizzly-3 is feb 21st18:42
heckjfeature ingest freeze is feb 21st18:43
ayoungNOt going to have it by -1 that is for sure18:43
*** danwent has joined #openstack-meeting18:43
heckjayoung: yeah, that was clear - figured it was 2 or 3 - don't have to assign it yet - but the more I can get laid out, the easier it'll be to coordinate changes later18:43
dolphmheckj: when is auth_token moving to the client?18:43
heckjdolphm: henrynash is starting to work on that ASAP - just got CLA, so I'm hoping in the next 2 weeks (grizzly-1)18:44
ayoungheckj, OK,  so the whole thing  will be -3  but let me see which pieces we can push for in -218:44
dolphmheckj: oh awesome18:44
heckjkk18:44
heckj#topic open discussion18:45
*** openstack changes topic to "open discussion"18:45
ayoungheckj, can we clear out the people on Core that never review patches?18:46
heckjyep18:47
*** sharis has quit IRC18:47
ayoungI'd like to eventually get some new names in there, but for now, we should show who is active18:47
ayoung#link https://launchpad.net/~keystone-core/+members#active18:47
*** markmcclain has quit IRC18:47
heckjayoung: I'll clear that out later today - I'll do keystone-core,keystone-drivers, and keystone-bugs maintenance all together18:47
ayoungheckj, +218:48
ayoungheckj, also, I'd like to have a couple items part of our current operating guidelines.  1.  Make sure all changes will work in an HTTPD deployment.  We put a lot of effort in heading toward that, and I'd hate to backtrack18:49
ayoung2.  We are considering auth_token locked down except for security /critical fixes until the migration is done.  We need to expediate that18:50
heckjayoung: "expediate"?18:51
ayoung3.  service.py authenticate is locked down until refactoring is done.  Don't waste time writing code against the old layout18:51
ayoungexpediafy?18:51
ayoungmake fast!18:51
*** adjohn has joined #openstack-meeting18:51
ayoungLightning McQueen it!18:51
heckjayoung: ah - yep, Henry asked some questions in email and was starting to roll on it18:51
heckjayoung: how do you propose to verify we don't backtrack on #118:51
gyeea boat-load of tests :)18:52
gyeeunit and functional18:52
ayoungheckj, well, the three active approvers should keep it in mind when reviewing patches.  For the most part, be aware of eventlet specific additions18:52
heckjgyee: are tests sufficient, or does it also need to be in devstack gating?18:52
gyeetests are the best way to guard against these things18:52
ayoungheckj, I think we need to start working toward tests run in HTTPD18:53
heckjgyee: agreed, but only if they're run18:53
gyeehaha18:53
heckjayoung: I think that's the only way to make sure they're run.18:53
ayoungheckj, yeah.18:53
*** cp16net|away is now known as cp16net18:53
heckjayoung: alternately, we can work with CI to talk about how to test an alternate deployment and see if they have suggestions18:53
ayoungheckj, I suspect that first step is normalizing the user table.18:54
ayoungThen we can use the REMOTE_AUTH in conjunction with the mod_auths in apache to run in HTTPD18:54
*** MarkAtwood has joined #openstack-meeting18:54
ayoungNeed devstack support.  Perhaps first off is an option to deploy Keystone in HTTPD along side the Horizon code.  Can be optional to start18:55
heckjayoung: makes sense18:55
ayoungHeh, that would let me finally close the IPv6 ticket, too18:55
heckjayoung: does devstack use httpd now? Thought it was a different config...18:55
heckjayoung: nevermind - just was told it does18:55
ayoungheckj, devstack uses httpd for Horizon, and eventlet for the rest of the services18:56
ayoungheckj, they do some neat things in there to make it developer friendly, so you run as yourself and not as root or the httpd user18:56
ayoungI had some problem getting logging working, which was making dev a PITA.18:56
ayoungSince I am waiting on the refactoring for other work, I can do a spike on the normalization.18:57
heckjayoung: sounds good18:57
ayoungSo who is full time coding on Keystone now:  /me, dolph, gyee, soon to be nash,18:57
*** zaneb has joined #openstack-meeting18:58
heckjI'm part time only - and mostly on client at the moment18:58
heckjI think that's it18:58
heckjJose part time too18:58
ayoungheckj, I don't know if we'll get any more of boden's time either18:58
*** darraghb has quit IRC18:59
heckjI think that's it for now18:59
heckjOk - wrapping up meeting18:59
heckj#endmeeting18:59
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"18:59
openstackMeeting ended Tue Nov  6 18:59:24 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-11-06-18.00.html18:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-11-06-18.00.txt18:59
*** Shengjie_Min has joined #openstack-meeting18:59
ayoungOK,  the four of us can do enough damage on our own18:59
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-11-06-18.00.log.html18:59
heckj:-)18:59
*** marek_ has left #openstack-meeting19:00
heckjI'll kick a note to David - had hoped to see him here today, but I don't think he ever popped in19:00
*** eglynn_ has joined #openstack-meeting19:01
*** debo_os has quit IRC19:04
ayoungheckj, that is OK they have there own agenda, and if it is dependent on our changes, they will come around19:05
ayoungOK, my wife needs to go vote.  Gotta go kid-watch19:05
*** ayoung is now known as ayoung-afk19:05
*** dolphm has quit IRC19:06
*** gyee has quit IRC19:09
*** uncleofthestick has quit IRC19:10
*** milner has quit IRC19:10
*** ayoung-afk is now known as ayoung19:12
*** novas0x2a|laptop has joined #openstack-meeting19:12
*** mnewby_ has joined #openstack-meeting19:13
*** littleidea has joined #openstack-meeting19:16
*** mnewby has quit IRC19:16
*** mnewby_ is now known as mnewby19:16
*** boden has joined #openstack-meeting19:20
bodenayoung -- can't stay for keystone meeting but wanted to point out a bug I just opened related to REMOTE_USER change: https://bugs.launchpad.net/keystone/+bug/107571019:22
uvirtbot`Launchpad bug 1075710 in keystone "Keystone REMOTE_USER with no metadata causes 404 on auth" [Undecided,New]19:22
*** jfriedly has quit IRC19:27
*** samkottler is now known as samkottler|call19:28
*** anniec has joined #openstack-meeting19:30
*** danwent has quit IRC19:31
*** anniec has quit IRC19:31
*** anniec has joined #openstack-meeting19:31
*** glauaguiar has quit IRC19:35
*** jakedahn_zz is now known as jakedahn19:36
*** dprince has quit IRC19:36
*** dolphm has joined #openstack-meeting19:37
*** jakedahn is now known as jakedahn_zz19:38
*** samkottler|call is now known as samkottler19:42
*** milner has joined #openstack-meeting19:42
*** rkukura has quit IRC19:44
*** dolphm has quit IRC19:45
*** dolphm has joined #openstack-meeting19:48
*** jfriedly has joined #openstack-meeting19:50
*** koolhead17 has joined #openstack-meeting19:50
*** shardy has joined #openstack-meeting19:51
*** mnewby_ has joined #openstack-meeting19:54
*** gabrielhurley has joined #openstack-meeting19:55
*** mnewby has quit IRC19:57
*** mnewby_ is now known as mnewby19:57
*** jfriedly has quit IRC20:00
*** danwent has joined #openstack-meeting20:00
ttxhola20:00
*** markmc has joined #openstack-meeting20:00
notmynamehi20:00
ttxTC members: who's around ?20:01
markmchey20:01
russellbhi20:01
danwenthi20:01
jaypipeso/20:01
ttx(That makes 6, we need a minimum of 7 members to hold the meeting)20:01
jaypipesmordred: ?20:01
annegentle___o/20:01
jaypipes\o/20:02
ttxand..; 720:02
gabrielhurleyo/20:02
russellb8 \o/20:02
notmynamewell, we need vishy and mordred for most of the discussions, I think20:02
ttxyes20:02
ttxhopefully they will join20:02
ttx#startmeeting tc20:02
openstackMeeting started Tue Nov  6 20:02:47 2012 UTC.  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
openstackThe meeting name has been set to 'tc'20:02
bcwaldonhello!20:02
ttxThe agenda for the meeting is at:20:02
ttx#link http://wiki.openstack.org/Governance/TechnicalCommittee20:03
ttxWe'll probably have to defer some of those to next week any way20:03
heckjo/20:03
ttx#topic Motion: Heat application for incubation20:03
*** openstack changes topic to "Motion: Heat application for incubation"20:03
ttx#link http://lists.openstack.org/pipermail/openstack-tc/2012-October/000039.html20:03
ttxWe need to decide if we grant Heat the additional resources and focus that come with the Incubated status20:03
ttxLike for Ceilometer I'd like to organize the discussion of this in 3 parts20:03
ttxTechnical quality / code maturity, Project management / openness / collaboration, and core scope / OpenStack feature complementarity20:04
ttxLet's talk Technical quality / code maturity first20:04
ttxdo we have the Heat people around ?20:04
shardyyup20:04
stevebakeo?20:04
zanebyep20:04
ttxyay20:04
stevebakeo/20:04
bcwaldonttx: I did want to ask if we should hit the last topic in your agenda before this20:04
gabrielhurleynot to digress but wouldn't this discussion be better *after* we resolve what incubation means (as per the Board's request)?20:04
ttxah.20:05
notmynamettx: doesn't this depend on a large part about the BoD request to refine the incubator process (and the points raised last week on a lack of definition for overall openstack core goals)?20:05
ttxI fear we may not go to the bottom of their request soon enough though20:05
ttxbut ok, let's discuss that first20:05
notmynamesoon enough for what?20:05
gabrielhurleyI was wondering the same thing20:06
ttxwell, they want us to start discussing it in a joint committee starting November 2620:06
ttxif you want to wait for the result of that, it delays the Heat incubation process accordingly20:06
annegentle___the heat original request was in July http://www.mail-archive.com/openstack@lists.launchpad.net/msg14506.html20:06
markmcand Heat gave us plenty of notice20:06
ttxright20:06
markmcright, July20:06
ttxbut I'm ok to discuss what we should do of the BoD request first, if tat makes more sense20:07
* markmc can't find a link to the mail now20:07
ttx#topic Preliminary discussion: Incubator process update20:07
*** openstack changes topic to "Preliminary discussion: Incubator process update"20:07
ttxThat topic is a formal request from the BoD20:07
ttx#link http://lists.openstack.org/pipermail/openstack-tc/2012-November/000072.html20:07
ttxIn summary they want to form a joint committee to discuss the future of the Incubation process20:07
markmcthanks20:07
ttxkeyword is "future".20:08
*** maurosr has quit IRC20:08
ttxSome of it is about setting better expectations, some of it is about creating new long-lasting classes of non-Core OpenStack projects20:08
ttxA reduced number of TC members interested to discuss that would join that committee, with a deadline for selection on November 2620:08
ttxPersonally I see a number of issues with that20:08
ttxFirst, unless we define a common position on that topic first, it will be hard for a subset of the TC to "represent" the TC's view20:08
markmcit seems to be about making incubator more inclusive than just "makes sense for core" ?20:08
ttxmarkmc: that seems t obe their intent yes20:09
ttxSecond, I think a lot of TC members feel strongly on the issue so we might end up dispatching a too-large group to that joint committee (they mentioned "select 2" to me)20:09
ttxThird, I'm not sure a committee (text/voice) meeting is the right way to build consensus around this, I would prefer to flesh out the idea on mailing-lists first.20:09
ttxThoughts ?20:09
markmcagree on mailing list discussion20:09
russellb+1 to that20:10
vishyo/ (btw)20:10
markmckind of thing I'd like to mull over as the discussion goes on20:10
ttx(I also think that in the mean time we can make a provisional decision on Heat)20:10
notmynamebased on the bylaws, isn't it a TC decision? seems that what the BoD is asking for is some clarification and to be kept abreast of the discussions20:10
markmcnotmyname, certainly an important part of the discussion20:10
*** pabelanger has joined #openstack-meeting20:11
ttxnotmyname: the idea is to avoid the case of an incubation process where the BoD applies veto on the core project promotion at the very end20:11
*** markmcclain has joined #openstack-meeting20:11
ttxwhich is I think bad for all20:11
ttxbut they also want the notion of "Incubation" to be revisited apparently20:11
markmcveto against "core project promotion" as distinct from "promoted to being a part of openstack"20:11
ttxthe email hints at a new class of project that would not be core, too20:12
gabrielhurley"being a part of openstack" is very amorphous in that context20:12
ttxWe could call the whole joint committee idea a bad idea, but that's how the BoD does things...20:12
notmynamettx: sure, that makes sense. and I agree that we need to actually define the stages. since they are approving what we decide, I'm glad they are giving some direction on what they want to see. but the decision is something we make, right? not something a subcommitee makes (for the reasons you gave)20:12
ttxAlternatively we /could/ start the ML discussion (where ?) and try to converge to a common position and then select a reduced number of TC members to represent it on that joint committee.20:12
jaypipesttx: like what? we already have library, supporting, core and incubated, right?20:12
russellbsounds like "core, but not as core as core"20:13
ttxjaypipes: I suspec they want to use "core" to mean not just "important", but "necessary" for smoe definition of what an openstack cloud is20:13
jaypipeswtfdtm? :)20:13
russellb(i don't really get it)20:13
notmynamerussellb: all projects are equal but some are more equal than others? ;-)20:13
*** nati_ueno has quit IRC20:13
markmcrussellb, agree, but core has a specific definition in the bylaws20:14
ttxin which case you would have the "openstack projects, a subset of which would be core20:14
markmcrussellb, a definition that folks seem to want to be precious about20:14
russellbaround trademark usage?20:14
jaypipesI continue to define core in terms of "infrastructure vs. platform".20:14
bcwaldonjaypipes: +1, it seems like thats what this discussion is really about, drawing the line there20:14
russellbjaypipes: that's an interesting way to put it20:14
bcwaldonopenstack is essential infrastructure20:15
jaypipesI also very much like the language notmyname used when differentiating between "product" and the underlying project when talking about Cloud Files vs. Swift, etc20:15
markmcsee http://wiki.openstack.org/Governance/Foundation/Bylaws#ARTICLE_IV._BOARD_OF_DIRECTORS20:15
markmc4.1 (b)20:15
markmcso the bylaws are quite specific about all this stuff20:15
ttxnotmyname: the TC defines what it cares about... what "core" or "openstack" or "official" exactly means is the BoD decision20:15
markmcwhat classes of project apart from core make up the OpenStack release etc.20:15
ttxi.e. they get to choose the label, we get to choose the stuff we work on as a community20:16
jaypipesmarkmc: right, but the bylaws also say that the TC decides what is core and what isn't..20:16
*** pabelanger has left #openstack-meeting20:16
ttxor a tleast that's my understqanding of it20:16
markmc"The Technical Committee shall have the authority to determine the modules for addition, combination, split or deletion from the OpenStack Project except for modules of the Core OpenStack Project"20:16
markmcah, yes20:16
ttxin all cases I don't think that affects our ability to decide if Heat is a good candidate and ready for Incubation20:16
markmcttx, agree20:17
ttxit may affect which label may be attached to it in the end20:17
bcwaldonttx: don't we need to decide if Heat should be core? It doesnt make sense to incubate without that plan in mind, yes?20:17
bcwaldonI was assuming incubated was solely a path to core20:17
ttxbcwaldon: that's the core (eh) of the BoD request. Make incubation not be linked to the concept of core20:17
markmcbcwaldon, how do non-core projects get added then?20:17
ttxi.e. you need to be inclubated to be core20:18
ttxbut you could be incubated and become something else20:18
russellbwhat is something else?20:18
bcwaldonwe don't need to go through an incubation process for non-core20:18
bcwaldonwe dont need to control it so closely20:18
markmcrussellb, at the moment "library projects, gating projects and supporting projects"20:18
russellbother than library, supporting, and gating20:18
ttxrussellb: their emali wouldn't say. Up to tha tjoint committtee to define I guess20:18
annegentle___currently incubation is required to become core (or get a split-off-core-one-time-fastpass)20:18
markmcrussellb, but I think the assumption is we add more classes20:18
russellbok.20:19
annegentle___or discover/study whether incubation is valuable20:19
markmcbcwaldon, we still need to evaluate them, similar criteria for incubation acceptance I thinik20:19
jaypipesmarkmc: I'd prefer NOT to add more classes, frankly...20:19
bcwaldonmarkmc: yes, I agree that, I just want to be clear about what class of project we're evaluating for20:19
ttxIf I had to guess I'd say they want a "core" and "main" class of openstack projects20:19
russellbwe either need another class, or need to make core not so precious20:19
markmcrussellb, that's my take20:19
russellbttx: that makes sense20:20
bcwaldoncore has to stay precious - it partially defines what an openstack cloud is20:20
jaypipesmarkmc: because as soon as we do, we end up in the "so is this a 'recommended OpenStack project' ... " arena and the product guys start seeing monetization.20:20
ttxboth would receive attention, but they would place requirements like "an openstack cloud" is one that implements all core and any main20:20
annegentle___core also requires the most resources20:20
markmcbcwaldon, assuming core and trademark usage are linked20:20
markmcannegentle___, why?20:21
ttxSo I'd like to propose we start the discussion on the ML (-dev ?)20:21
gabrielhurleyI'm definitely not a fan of "curated but not core"... I've seen that go wrong in lots of projects. they turn into ghettos and/or stifle community becuase people think something's blessed when it's not really. Better to just foster the ecosystem and let natural selection take its course.20:21
notmynamemarkmc: which they are in the bylaws20:21
bcwaldonmarkmc: I don't really want to care about trademark usage right now, this is a technical committee ;)20:21
jaypipesmarkmc: they are linked... per 4.1 above.20:21
ttxand keep on considering incubation old-style in the mean time20:21
*** anniec has quit IRC20:21
annegentle___markmc: does "requires the most non-dev resources" clarify? Core has certain expectations of release, test, doc, etc.20:21
markmcnotmyname, bcwaldon, yep20:21
jaypipes"The other modules which are part of the OpenStack Project, but not the Core OpenStack Project may not be identified using the OpenStack trademark except when distributed with the Core OpenStack Project"20:21
ttxwith e caveat that the game rules may well change soon20:21
bcwaldonjaypipes: we might want to disconnect that relationship20:22
*** anniec has joined #openstack-meeting20:22
notmynameaccording to the bylaws, core == can use the trademark and is part of the combined release.20:22
jaypipesnotmyname: precisely.20:22
jaypipesbcwaldon: we don't have the ability to do that... :(20:22
Daviey.win 26520:22
bcwaldonwhy do *we* need to care about trademark usage?20:22
notmynamebut that's not a very good guide to use to determine if something should be core20:22
markmcbcwaldon, because we care about "core" and they're currently linked :)20:22
jaypipesnotmyname: agreed... just pointing out the boundaries of this discussion. :)20:23
* ttx reposts his suggestion20:23
ttx<ttx> So I'd like to propose we start the discussion on the ML (-dev ?)20:23
ttx<ttx> and keep on considering incubation old-style in the mean time20:23
markmcttx, agree20:23
bcwaldonttx: yes20:23
jaypipeslol, agreed.20:23
russellbagree20:23
ttx<ttx> with thee caveat that the game rules may well change soon20:23
jaypipesttx: all fine and good but I still think this needs to be resolved before any decision on Heat would be applied.20:24
markmcso, part of this will be considering whether we think it's a candidate for core20:24
bcwaldonlet's Move On™20:24
*** gyee has joined #openstack-meeting20:24
russellbbut it could also be, is it worth additional resources right now understanding that could be core, or some other new class of project, pending the result of this (probably lengthy) discussion20:25
ttxjaypipes: that's a valid remark... maybe we can cover it in the Heat discussion ?20:25
ttxBut if you see incubation as a resorce investment to support a promising project, more than a pre-stamp for core...20:25
ttxI think we can decide now20:25
ttxnothing prevents us from removing a project from incubation basically20:25
markmcyeah20:26
ttx#agreed Start discussion on BoD request on -dev ML20:26
*** nachi_ has joined #openstack-meeting20:26
*** nachi has joined #openstack-meeting20:26
*** nachi_ has quit IRC20:26
ttxBack to Heat20:26
ttx#topic Motion: Heat application for incubation20:26
*** openstack changes topic to "Motion: Heat application for incubation"20:26
ttxSo.. Technical quality / code maturity first20:26
jaypipesso what is the difference between a project we think has promise to become a non-core supporting OpenStack project and an incubated project that we think has promise to become a non-core supporting OpenStack project!? ...20:26
ttxI need to read that a few times now20:27
notmynamejaypipes: I think eventlet is a promising project that supports openstack ;-)20:27
*** davidha has joined #openstack-meeting20:27
russellbttx: i think the ? was, what does incubation mean.20:27
jaypipesnotmyname: I think swift is a promising project that supports glance. :)20:27
jaypipesrussellb: precisely.20:28
*** jrd has quit IRC20:28
markmcjaypipes, it means we hope it will be officially included as a supporting project in the H release20:28
ttxIncubation is: do we care e nough about Heat to give it extra attention20:28
heckj#link http://stackmeat.org <-- open community of openstack-related projects that *just* started this past week20:28
creihtjaypipes: isn't glance infrastructure then? ;)20:28
notmynamejaypipes: and linux is promising too!20:28
creihterm not infrastructure :)20:28
ttxnotmyname: yeah, I like linux too20:28
jaypipesmarkmc: and what does the incubation actually entail then vs. just people thinking it's got promise? access to CI team and other stuff?20:28
*** markwash has quit IRC20:28
russellbbtw, eventlet is *not* promising.20:28
jaypipeshehe20:28
markmcjaypipes, what does it mean for potential core projects?20:28
ttxjaypipes: CI, release management20:28
jaypipescreiht: :)20:29
jaypipesttx: ok, that's fine then. just wanted some clarification on what incubation means if it doesn't mean "will likely become core20:29
annegentle___jaypipes: ttx: docs and test too?20:29
ttxjaypipes: it's perfectly valid to abstain to the Heat thing saying it's not the right time20:29
* markmc hopes the heat guys are "enjoying" this20:29
russellbmarkmc: i was thinking that too :)20:29
ttxmarkmc: yeah a bit of bad timing for them20:29
annegentle___traditionally incubation doesn't give you extra docs resources20:30
stevebake:)20:30
jaypipesttx: well, no, I'll be voting against Heat because I don't think it's infrastructure, not because it's not the right time ;)20:30
creihtmarkmc: doesn't every incubation request always start with a spirited discussion about what core should be? :)20:30
ttxjaypipes: twice as many reasons, awesome20:30
bcwaldonjaypipes: same20:30
* jaypipes would like to point out he really likes HEAT.20:30
markmccreiht, you'd hope we'd be over that by now20:30
jaypipesjust not as core IaaS20:30
ttxArh, technical discussion on the merits of Heat firs tplace20:30
ttxcore scope will be discussed last20:30
jaypipesttx: k, sorry20:30
ttxHad a question about the choice of CloudFormation template format (probably showing the extent of my ignorance of it)20:30
ttxDoes that restrict us in terms of resources that we can effect ? For example, would it support Quantum-like resources ? Or do you embrace/extend it ?20:31
danwentttx: stevebake says they already added native quantum type resources to heat20:31
jaypipesright.20:31
danwentso I think the answer is that they are not limited in this fashion20:31
ttxjaypipes: should we read your "I really like HEAT" as no opposition on technical grounds ?20:31
stevebakeI've just implemented a full set of Quantum resources, announcement will be going out to os-dev list today20:31
jaypipesttx: that is correct. no opposition at all on technical grounds.20:31
zanebttx: we can add whatever resources we like20:32
ttxstevebake: so the template format is extensible, cool20:32
zanebjust put them in a separate namespace20:32
zanebamazon ones start with AWS::20:32
shardyttx: intention is to move to openstack-native resource names, which will be a superset of AWS named resources20:32
ttxthen no issue on the technical side for me20:32
stevebakeCloudFormation format is just json. We're considering an additional native format like YAML as an alternative20:32
ttxany other question on the technical side ?20:32
ttxOK, let's talk Project management / openness / collaboration then20:33
ttxA few random remarks on that...20:33
ttxThe gap to cover is slightly bigger than with Ceilometer, which was already using launchpad / openstack meetings / mailing-lists etc... which means this incubation is slightly more costly20:33
ttxbut nothing impossible20:33
zanebheat has moved to launchpad and the os mailing list already20:33
ttxOh, recently ?20:34
markmce.g. https://bugs.launchpad.net/heat20:34
ttxsaw github issues being referenced, was confused20:34
zaneblaunchpad move happened last week I think20:34
shardyWe've discussed moving meetings here too last week20:34
russellbhave been doing openstack-style meetings, at least, too.  i've seen meeting notes on the list in the past20:34
ttxlooks like you read my mind20:34
zanebwe've been on openstack-dev for ages20:34
jaypipes++20:34
ttxAlso I'm a bit worried by the lack of external contributions. The team is AFAICT all-RedHat and almost all new contributors20:34
ttxI hope that's more a visibility issue than an interest issue...20:35
shardyttx: github issue tracker now removed20:35
ttxotherwise collaboration wit hother core projects seems to be going well... no other remark from me20:35
jaypipesttx: I'm less concerned about that after seeing the openness with which communication has occurred.20:35
zanebyes, meetings are all on IRC in #heat, but we could move easily here20:35
*** mnewby_ has joined #openstack-meeting20:35
markmcsome openstack-common contribs have come from heat guys, which is cool20:36
ttxanything else before we move to core scope ?20:36
ttxOK, then lets' talk core scope / OpenStack feature complementarity20:36
ttxwanted to make sure the ohter bases were covered before we go on the most problematic point20:37
jaypipesttx: I'm more concerned about disambiguating some of the apparent cross-project code between Ceilo, Synaps, and HEAT, and ensuring each of those projects has a clear path to sharing of common code.20:37
markmcI think it's a really solid addition - ties together all of OpenStack APIs20:37
ttxOn that topic I would have preferred if we moved up the stack a bit more slowly...20:37
ttx...though I recognize that there is a need for a one-stop shop for orchestration of several openstack services20:37
russellbi don't really think it moves up the stack that much..20:37
shardySo to be clear, we've been working with ceilometer guys (asalkeld primarily) such that we can use their metric collection infrastructure20:38
markmceven a simple "launch instance, assign floating IP" thing is possible through Heat20:38
shardywe have no intention of long-term overlap20:38
jaypipesshardy: ++20:38
jaypipesshardy: good to hear. (more concerned re: Synaps, but that's a different discussion ;)20:38
*** mnewby has quit IRC20:38
*** mnewby_ is now known as mnewby20:38
shardyjaypipes: IMO synaps is not really relevant to this discussion20:38
*** mnewby has quit IRC20:39
jaypipesshardy: because of its implementation or something else?20:39
zanebsynaps is a tricky one because it has not been developed in the open with involvement from the community20:39
stevebakewe'll use whatever monitoring solution emerges, we just need it to support autoscaling etc20:39
ttxso fro mprevious mentions in the meeting some (bcwaldon, jaypipes) have reservations based on Heat not being IaaSy enough ?20:39
shardyie perhaps the CW api might end up in ceilometer or somewhere else, it's not a core part of our orchestration20:39
jaypipesk, gotcha.20:39
ttxwould like them to voice them more clearly now, since I think tat's the heart of the decision we have to take20:39
jaypipesshardy: HEAT is more the CF part, less the CW part...20:40
shardyYep, we just need a monitoring service, it can be whatever ends up working20:40
jaypipesk20:40
shardyjaypipes: exactly, we just need metrics for HA/autoscaling decisions20:40
shardyI just bolted on a partial CW api for easier testing really20:40
danwentI personally like the idea of an orchestration service like heat, otherwise people try to shove orchestration into indvidual services (where it makes less sense, in my opinion).20:40
shardyand becuse I thought it might be useful20:40
jaypipesright. well, you saying you're working with the other folks to align towards a common codebase for collection/monitoring is good enough for me.20:41
ttxdanwent: in tha tsense it could be seen as up the stack as Horizon20:41
markmcjaypipes, they could have chosen not to implement auto-scaling because OpenStack doesn't have an API for it20:41
jaypipesdanwent: totally agreed.20:41
markmcjaypipes, but they saw it as pretty essential20:41
jaypipessure, understood20:41
zanebjaypipes: http://julien.danjou.info/blog/2012/openstack-synaps-exploration see conclusion20:42
jaypipesmarkmc: it's my duty to bring up these kinds of things, that's all :)20:42
shardymarkmc: there are several places where we've done our own impementations, but longer term would like to use external aaS implementations (e.g LBaaS)20:42
danwentttx: yes20:42
jaypipeszaneb: ah, cheers, thx for that link. very helpful.20:42
markmcjaypipes, sure, I wondered too - but it's all good20:42
ttxjaypipes, bcwaldon: so is it seufficiently off your vision of what "openstack core" should be to be denied incubation ?20:42
jaypipesttx: I believe that totally is dependent on the outcome of our previously discussed topic for the ML about what is core, no?20:43
bcwaldonttx: I'm becoming increasingly concerned with what 'incubation' and 'core' mean20:43
bcwaldonttx: so I would say 'no' until I understand that better20:43
jaypipesttx: I've stated this opinion before.. I believe core == infrastructure. and infrastructure == <crap won't run without it>20:43
ttxPersonally I think we could grant it, with the clear caveat that the rules of the game are in the process of changing so this may be reverted soon in another meeting once those rules are defined20:43
jaypipesttx: this is why I voted no on Horizon being in core originally.20:43
ttxjaypipes: agreed, that's consistent20:44
ttxbut would you support a motion to REMOVE horizon from core now ?20:44
jaypipesttx: it's a great project, it just didn't meet the "won't run without it" factor.20:44
gabrielhurleyI agree with the comparison to Horizon and the question to me is does it add enough value20:44
gabrielhurleythere's a clear uptick in adoption based on Horizon's inclusion20:44
jaypipesttx: no, I would NOT support that. just saying what the basis of my opinion is.20:44
ttxgabrielhurley: do you see Horizon making use of Heat if it ever becomes a core project ?20:44
gabrielhurleywould the same be true of HEAT?maybe20:44
gabrielhurleyHorizon-Heat integration would absolutely happen20:45
jaypipesgabrielhurley: good point re: the addition of value vs. infrastructure over platform.20:45
gabrielhurleyalthough amusingly you could also use Heat to deploy Horizon20:45
stevebakeFYI an external contributor is working on a Horizon Heat ui20:45
jaypipesgabrielhurley: I guess it all boils down to what is core...20:45
gabrielhurleyyeah20:45
gabrielhurleyI'm still undecided, FWIW20:45
shardyttx: heat plugin for horizon in-progress20:45
markmcstevebake, got the link?20:45
markmcit's on github20:45
* markmc can't find it20:45
gabrielhurleyI've seen it20:45
gabrielhurleyit's very nascent, but does exist20:45
shardyhttps://github.com/heat-api/heat-horizon20:45
jaypipesshardy: shouldn't that be "mirage"? :)20:46
gabrielhurleyheh20:46
gabrielhurley+120:46
notmynameI agree with bcwaldon and jaypipes (except I would support removing current core non-IaaS projects)20:46
stevebakeI think this is an older screencast http://radez.fedorapeople.org/thermal1.ogv20:46
shardythere is also a screencast demo from radez around somewhere, not got the link to hand20:46
ttxDoes anyone need extra information before deciding ? Note that the decision needs 5 "yes" or 5 "no"... so if enough people abstain the decision is pushed back (vote "abstain" if you want to delay decision)20:46
stevebakehttps://github.com/heat-api/heat-horizon20:46
markmcgabrielhurley, part of heat templates are almost a UI description - i.e. the list of parameters to prompt a user for, including defaults, lists to select from, etc.20:47
gabrielhurleyyep20:47
*** jpich has joined #openstack-meeting20:47
gabrielhurleyI'm familiar with cloudformation and how it's all supposed to work20:47
gabrielhurleyit's an interesting challenge20:47
gabrielhurleywhat Amazon ended up with is awful20:47
gabrielhurleywe'd have to do better ;-)20:47
markmcheh20:47
zanebgabrielhurley: we'd love to hear your input about that on the ML :)20:47
gabrielhurleyfor sure20:47
stevebakelots of potential for autogenerated ui20:48
gabrielhurleydefinitely20:48
*** adam_g has quit IRC20:48
*** adam_g has joined #openstack-meeting20:48
* ttx repeats: <ttx> Does anyone need extra information before deciding 20:48
bcwaldonnope20:48
jaypipesno20:48
markmcnot me20:48
danwentno20:48
ttxor can we move on to vote (abstain being an option)20:48
ttxok then, let's vote, for the decision to be final at least 5 yes or 5 no need to be obtained20:49
ttx#startvote Approve Heat application for incubation? yes, no, abstain20:49
openstackBegin voting on: Approve Heat application for incubation? Valid vote options are yes, no, abstain.20:49
openstackVote using '#vote OPTION'. Only your last vote counts.20:49
jaypipes#vote abstain20:49
markmc#vote yes20:49
gabrielhurley#vote abstain20:49
notmyname#vote no20:49
russellb#vote yes20:49
vishy#vote abstain20:50
danwent#vote yes20:50
bcwaldon#vote abstain20:50
ttx#vote yes20:50
annegentle___#vote yes20:50
heckj#vote abstain20:50
ttxouch, that's close20:50
gabrielhurleywow20:50
ttx30 more seconds, unlikely to chnag ethe results anyway20:51
heckjI think we're sending a poor message approving for incubation and what it implies20:51
jaypipesnotmyname: just curious, you voted no instead of abstain because you aren't concerned about the outcome of the discussion on "what is core" or you think you know what the decision will be?20:51
ttxnote that you can change your vote.20:51
* annegentle___ is only voting for incubation, core is in the future20:51
ttxheckj: if most abstain switch to "no" then they beat the "yes" (you need more "yes" than there is "no")20:52
* ttx is only voting for incubtaion with the caveat that we may revisit the decision soon20:52
markmcthat's a long 30 seconds :)20:52
jaypipesnotmyname: or because you are saying that core is for infrastructure and incubation is for going into core and HEAT isn't infrastructure and so shouldn't be incubated? :)20:52
bcwaldonI don't know how we can reasonably vote for this without understanding what this means20:52
russellbannegentle___: that was my thought.  incubation now, the rest is obviously up in the air20:52
ttxbasically, start pushing the resources but be ready to pull them out20:52
notmynamejaypipes: yes that (the "old" or "current" definition)20:52
jaypipes:) k20:52
heckjttx: understood, but I'm abstaining because I think it's important to nail down what incubation means first.20:53
ttxmarkmc: as long as people discuss...20:53
ttxheckj: I respect that, almost abstained myself20:53
* markmc basically thinks "if this isn't the kind of project we want to welcome into OpenStack, what is?"20:53
ttxok then 20 seconds20:53
gabrielhurleyOn the plus side, giving them some resources for now will help them build a better project either way so we've done a good deed.20:53
markmctalk about sending a bad message ...20:53
bcwaldonmarkmc: we need to define what it means to 'welcome into openstack'20:53
ttx#endvote20:53
openstackVoted on "Approve Heat application for incubation?" Results are20:53
bcwaldonmarkmc: I'm more than happy for the project to exist and be associated20:53
russellbgabrielhurley: +1 to that20:53
markmcrejecting would be an awful message of exclusivity IMHO20:54
openstackyes (5): markmc, ttx, russellb, danwent, annegentle___20:54
openstackabstain (5): heckj, gabrielhurley, jaypipes, bcwaldon, vishy20:54
openstackno (1): notmyname20:54
jaypipesmarkmc: only if you assume that not going into incubation is somehow bad (which it isn't)20:54
markmcbcwaldon, yeah, we suck we don't know what that means yet20:54
heckjbcwaldon: +120:54
creihtlol20:54
bcwaldonmarkmc: we need to be exclusive - we can't just accept anybody20:54
markmcbcwaldon, we're not20:54
bcwaldonmarkmc: I wrote a project that spins up vms based on a script, should that be OpenStack™20:54
danwentit seems like the logic being applied here is not consistent with the ceilometer vote last time20:54
markmcbcwaldon, I thought we weren't talking about trademarks :)20:55
notmynamedanwent: FWIW, I voted the same way :-)20:55
danwentI voted yes for the same reason I voted yes for ceilometer20:55
danwentnotmyname: fair :)20:55
bcwaldonmarkmc: I've had to come down to your level ;)20:55
bcwaldondamn trademarks20:55
jaypipesdanwent: would I be inconsistent20:55
jaypipesdansmith: ?20:55
markmcbcwaldon, trademarks are the last thing I want to talk about!20:55
jaypipesgah. danwent ...20:55
bcwaldonmarkmc: me too! blah20:55
russellbi think voting yes to ceilometer and abstain to heat is inconsistent.20:55
danwentjaypipes: :)  to me there was uncertaintly about the definition of "core" and "incubation" in both cases20:55
jaypipesrussellb: is that what I did?20:55
russellbi don't know, just making a general statement, we had almost all yes to ceilometer20:56
jaypipesrussellb: if so, yes, I was inconsistent and should not have been.20:56
gabrielhurleyI think they ceilometer/heat land at somewhat different levels in the stack... also ecosystem competition and level of integration are very different between the two.20:56
ttxbcwaldon++20:56
* ttx lags20:56
danwentI don't remember individual votes, but the end result is certainly different.  I was just curious if people saw a major difference that I was missing20:56
ttxerr, just was off network for a bit20:56
ttxdid the bot record the results and my #endvote ?20:57
jaypipesyes20:57
ttxok, I guess I'll read the log20:57
ttx#topic Preliminary discussion: Third-party APIs20:57
notmynamettx: 5-5-120:57
*** openstack changes topic to "Preliminary discussion: Third-party APIs"20:57
markmcshardy, stevebake, zaneb, welcome :)20:57
heckjttx: with 3 minutes remaining?20:57
russellbwhat does 5-5-1 mean, basically abstain?20:57
russellbor what?20:57
ttxThe thread is in full swing on the mailing-list... Would be good if it could distill down into a clear motion to be discussed and proposed at the next meeting20:57
ttxrussellb: it means yes20:57
Davieya user sevice orchestration tool and a metering/billing centralised project is very differnet.. I can see how one is infra, and the other is an end user tool20:57
russellbttx: ok, thanks.20:58
ttxrussellb: more yes than no, and at least 5 yes or no20:58
markmcheckj, this is an easy conversation :)20:58
markmcttx, I can summarise the motion20:58
ttxNB: Motions to be voted on need to be posted for public discussion before the end of day on Wednesday the week before20:58
markmcvishy, you agree that it's just a "we agree with the apis-should-be-external-aspiration, but we're not ready for that in Nova yet" motion?20:58
ttx#action markmc to summarize and propose a clear motion by EOD tomorrow20:59
ttxfor next meeting20:59
ttx#action ttx to start discussion on the incubation/core process on -dev ML20:59
vishymarkmc: yes20:59
markmcvishy, thanks20:59
ttxok, no time for more today, see you all next week ?21:00
*** davidha has quit IRC21:00
*** Vek has joined #openstack-meeting21:00
bcwaldonyep, thanks ttx21:00
annegentle___thanks ttx21:00
ttx#endmeeting21:00
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"21:00
openstackMeeting ended Tue Nov  6 21:00:34 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2012/tc.2012-11-06-20.02.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2012/tc.2012-11-06-20.02.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2012/tc.2012-11-06-20.02.log.html21:00
stevebakethanks all!21:00
*** davidha has joined #openstack-meeting21:01
ttxmarkmc, heckj, notmyname, bcwaldon, jgriffith, vishy, gabrielhurley, danwent: around ?21:02
*** salv-orlando_ has joined #openstack-meeting21:02
markmcyep21:02
notmynamehere21:02
danwento/21:02
gabrielhurleyo/21:02
heckjo/21:02
bcwaldonttx: yes21:02
*** salv-orlando has quit IRC21:03
*** salv-orlando_ is now known as salv-orlando21:03
ttx#startmeeting project21:03
openstackMeeting started Tue Nov  6 21:03:30 2012 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:03
openstackThe meeting name has been set to 'project'21:03
ttxAgenda @ http://wiki.openstack.org/Meetings/ProjectMeeting21:03
ttx#topic Actions from previous meeting21:03
*** openstack changes topic to "Actions from previous meeting"21:03
ttxAll done except21:03
ttx* ttx to discuss oslo versioning with mordred and markmc21:03
ttxWe still need to have that discussion, delayed by ETOOMUCHTRAVEL21:04
markmcoh, versioning21:04
markmchmm, it's not top of my list to figure out with oslo21:04
vishyo/21:04
markmcthinking it'll be a week or two more before it becomes really important21:04
markmci.e. when we go to release oslo-config21:04
ttxmarkmc: still something we need to find a solution for, early enough21:04
markmc(blocked on argparse re-write)21:04
markmcttx, yep, totally21:04
ttx#topic Oslo status21:04
*** openstack changes topic to "Oslo status"21:04
*** nachi has quit IRC21:05
jgriffith0/21:05
eglynn_o/ (covering for nijaba on ceilo)21:05
markmcso, I've begun the renaming from openstack-common21:05
ttx#action markmc/ttx/mordred to discuss oslo versioning21:05
markmcproject and teams created, bugs and blueprints moved over21:05
ttx#link https://blueprints.launchpad.net/oslo/grizzly21:05
markmcI've mostly gone over the blueprints apart from ttx's latest ones21:05
markmcwhich I'm sure are fine21:05
ttxLooks like a pretty good plan... is it complete from your perspective ?21:05
markmclast renaming task is moving openstack-common.git to oslo-incubator.git21:06
markmcttx, yeah, I think it's pretty complete21:06
markmcttx, will double check against design summit decisions21:06
ttxWould be good to get people to indicate which milestone they intend to see their stuff drop21:06
markmcttx, yep, that's next on my list to chase down21:06
ttxLooking into grizzly-1 now (which is two weeks from now)21:06
ttx#link https://launchpad.net/oslo/+milestone/grizzly-121:06
markmc#action markmc get milestone targets for oslo blueprints21:06
ttxOnly cfg-argparse is on the map, which sounds pretty conservative to me21:06
ttx(in the good sense of conservative, I know it's election day somewhere)21:07
markmctrue21:07
markmcand some of them are pretty much done21:07
markmcservice-infrastructure at least21:07
ttxmarkmc: ok, just target the ones that are likely to hit, helps setting expectations right21:07
*** annegentle___ has quit IRC21:07
markmcelection day? somewhere interesting?21:07
bcwaldononly America21:07
* markmc chuckles21:07
ttxmarkmc: Anything you wanted to mention ?21:07
markmcttx, yep, will do21:07
markmcI think that's it21:08
bcwaldonmarkmc: what is 'oslo-incubator'?21:08
ttxQuestions on Oslo ?21:08
*** Tushar has joined #openstack-meeting21:08
markmcwill send out an email when the renaming is complete21:08
markmcbcwaldon, where APIs go on the way to being ready for a library release21:08
markmcbcwaldon, https://etherpad.openstack.org/grizzly-oslo21:08
bcwaldonokay21:08
bcwaldonthanks21:08
markmcbcwaldon, i.e. what the current openstack-common repo is21:08
markmcnp21:08
ttxclarifies that it's only temporary21:08
ttxOther questions ?21:09
ttx#topic Keystone status21:09
*** openstack changes topic to "Keystone status"21:09
ttxheckj: o/21:09
ttx#link https://blueprints.launchpad.net/keystone/grizzly21:09
heckjgetting stuff written up based on those status - just cleaned them up in the past few hours21:09
ttxheckj: is that a complete plan from where you sit ?21:09
heckjttx: at this point, best estimate - yep21:10
*** Tushar_Patil has joined #openstack-meeting21:10
ttxLooking at recently-targeted grizzly-1 stuff...21:10
ttx#link https://launchpad.net/keystone/+milestone/grizzly-121:10
ttxSounds reasonable and on track to me21:11
ttxheckj: anything else ?21:11
heckjemail coming soon summarizing all that21:11
ttxawesome21:11
ttxQuestions about Keystone ?21:11
ttx#topic Swift status21:12
*** openstack changes topic to "Swift status"21:12
ttxnotmyname: hi!21:12
notmynamehi21:12
ttx#link https://launchpad.net/swift/+milestone/1.7.521:12
ttxOriginal plan was to QA-cut on November 5 and release on November 821:12
ttxany update on that ?21:12
notmynameyes21:12
notmynameI was told yesterday that the QA env was being phsically moved and therefore QA wouldn't be ready until at least tomorrow21:12
notmynameall patches required for 1.7.5 have been merged21:13
notmynamewe may have one more land this afternoon21:13
notmynameand the 1.7.5 release should be cut either tonight or tomorrow21:13
ttxnotmyname: ok, just ping me when I can cut milestone-proposed21:13
notmynametentative changelog update is https://github.com/notmyname/swift/commit/cd4ede501f7c616bf80264a9f3e1a9d9d8e9983921:13
notmynametons of good stuff in this release21:14
notmynamettx: I will let you know as soon as I know21:14
ttxIs the milestone page reflecting the major changes in Swift 1.7.5 ? Or could it use a bit more work ?21:14
*** alexpilotti has quit IRC21:14
notmynameit could probably use a bit more work, but I did spend some time on LP bugs and blueprints this morning.21:14
ttxnotmyname: Final release is still tentative to Nov 8 or should we already move it back ?21:14
notmynameI didn't change any targeting, though21:14
notmynamettx: probably need to move it back21:15
ttxNov 9 ? Nov 12 ?21:15
notmynamehow about next tuesday (Nov 13)?21:15
ttxWorks for me21:15
ttxwe can adjust if we know better soon21:15
*** milner has quit IRC21:15
ttxnotmyname: anything else ?21:16
*** boden has quit IRC21:16
notmynameI don't have anything else21:16
ttxupdated to Nov 1321:16
ttxQuestions on Swift ?21:16
ttx#topic Glance status21:16
*** openstack changes topic to "Glance status"21:16
ttxbcwaldon: o/21:17
bcwaldonttx: hey21:17
ttx#link https://blueprints.launchpad.net/glance/grizzly21:17
ttxLooks good to me21:17
ttxYou should set a priority to streaming-server21:17
bcwaldonwhy thank you21:17
bcwaldonttx: I'm not sure if streaming-server will happen, but I'll figure that out this week21:17
ttxYou should still be able to say how critical it is for a successful grizzly cycle though21:18
bcwaldonsure21:18
ttxoh. "if"21:18
ttxnot "when"21:18
ttxok, sure, keep it as it is until you know21:18
ttxIn general would be good to get a better indication of what milestone each feature is likely to land21:19
ttxi.e. grizzly-2, grizzly-3 etc21:19
ttx#link https://launchpad.net/glance/+milestone/grizzly-121:19
ttxAll implemented, anything else that will probably land in the next two weeks that we could target to grizzly-1 ?21:20
bcwaldonpossibly21:20
bcwaldonglance-domain-logic-layer21:20
bcwaldonI'll talk with markwash about that21:20
ttxok, adjust-at-will21:21
bcwaldonep21:21
ttxbcwaldon: Anything else ?21:21
bcwaldonand I just sent out my grizzly planning email that you requested21:21
bcwaldonsubject 'Glance Grizzly Planning'21:21
ttxcool, haven't had time to read it yet, but I will soon21:21
bcwaldonwell, Planing21:21
bcwaldonthat's great21:21
ttxQuestions on Glance ?21:21
ttx#topic Quantum status21:22
*** openstack changes topic to "Quantum status"21:22
danwento/21:22
ttxdanwent: hey21:22
ttx#link https://blueprints.launchpad.net/quantum/grizzly21:22
danwentbtw, am about to send out note to ML about quantum in grizzly21:22
ttxyay 38 blueprints21:22
danwenthehe… quantum team is always BP happy21:22
ttxdanwent: would be great to prioritize the "undefined priority" blueprints soon21:22
ttxdanwent: How complete is that list from your perspective ?21:23
danwentnearly everything we covered at the summit is there, with one possible exception21:23
ttxYou have A proposed @ https://blueprints.launchpad.net/quantum/grizzly/+setgoals21:23
ttxs/A/1/21:23
ttxLooking into grizzly-1 targets now21:24
ttx#link https://launchpad.net/quantum/+milestone/grizzly-121:24
danwentyeah, i actually just updated the whiteboard of that BP indicating that I didn't want to target for grizzly until i had a better understanding of what it meant21:24
ttxOK, with two weeks left, this looks even more unlikely than usual...21:24
ttxFeeling lucky ? Or have secret plans to start deferring stuff to grizzly-2 ?21:24
danwentwe've sunk a lot of cycles into sevice insertion + LBaaS design review21:25
danwentwork on those will start in G-1, but will definitely not land21:25
danwentI expect about 1/3 of BPs to be deferred21:25
danwentI'm just not sure which 1/3 :-/21:25
ttxdanwent: you can target them to g2 while starting on them on g121:25
*** sarob has quit IRC21:26
ttxthe idea is to give an indication on when feature land... being pessimistic is better than optimistic21:26
danwentttx: sure.  by next meeting, they will either be likely, or moved out.21:26
ttxok21:26
*** sarob has joined #openstack-meeting21:26
danwenthello?21:27
danwenti guess i bored ttx to sleep21:27
ttxcisco-plugin-enhancements is in grizzly-1 but not in grizzly series goal21:27
ttxno just a script that took too long to run21:27
danwenthehe, will clean that up.21:27
ttxdanwent: Anything else ?21:27
danwentnope.  just trying to push the team to finish talking and start coding :)21:28
ttxQuestions on Quantum ?21:28
*** jog0 has quit IRC21:28
ttx#topic Cinder status21:28
*** openstack changes topic to "Cinder status"21:28
ttxjgriffith: o/21:28
jgriffithyo21:28
ttx#link https://blueprints.launchpad.net/cinder/grizzly21:28
jgriffithttx: getting there21:29
jgriffithttx: awaiting a few things from chuck and from the folks at HP21:29
ttxYes, I see. Would be great to set a priority on each of those21:29
jgriffithttx: yeah, I've started that21:29
jgriffithttx: been a bit distracted past couple days :)21:29
ttxjgriffith: so it's almost complete as far as you can tell ?21:29
jgriffithttx: Yes21:30
ttxYou have two proposed at https://blueprints.launchpad.net/cinder/grizzly/+setgoals21:30
jgriffithttx: I don't know of any large additions coming in other than those I mentioned21:30
ttxprobably worth going through them too21:30
ttx#link https://launchpad.net/cinder/+milestone/grizzly-121:30
ttxNot looking good with only two weeks left... and some blocked21:31
ttxjgriffith: Could you set an explicit status on the "unknown" ones ?21:31
jgriffithYep, I'll update21:31
ttxI suspect they are "not started" which makes me pessimistic :)21:31
jgriffithttx: non-believer!21:31
ttxjgriffith: maybe adjust g1 goals by next week ?21:31
*** annegentle__ has joined #openstack-meeting21:31
ttxAlso one of them is unassigned, and therefore a bit unlikely to land in this milestone21:32
ttx(volume-type-scheduler)21:32
jgriffithttx: actually that one is about done21:32
ttxah! an unknwon almost done21:32
jgriffithttx: There was some flopping in who was working on it21:32
ttxiscsi-chap and cinder-protocol-enhancements should have their series goal set to grizzly, too, if you intend to include the min the general plan21:33
jgriffithttx: You'll notice some of those aren't approved21:33
jgriffithttx: for a reason :)21:33
ttxhmkay, maybe remove the milestone target on them so that they don't pollute your g1 roadmap then21:34
jgriffithgotya21:34
ttxcool21:34
ttxit's actually not looking that bad now21:34
ttxjgriffith: Anything else ?21:34
jgriffithJust trying to get the gate tests to work again :)21:34
ttxaw.21:34
*** gatuus has joined #openstack-meeting21:35
markmcwas about to ask - is that all down to cinder?21:35
markmcor just the likely culprit?21:35
ttxjgriffith: how is that going ?21:35
jgriffithmarkmc: no21:35
jgriffithttx: markmc I don't think it's cinder TBH21:35
ttxmarkmc: it's actually a kernel issue fwiw21:35
markmcjgriffith, ok, good to know21:35
markmcoh21:35
jgriffithttx: markmc it's not that either I don't believe21:35
* markmc can offer a decent kernel to try :)21:35
ttxbut jgriffith is helping narrowing it down21:35
jgriffiththis is something *new*21:35
markmc(sorry)21:36
ttxjgriffith: a mutant ?21:36
jgriffithand I believe it's keystone issue21:36
ttxjgriffith: oh, it's not the thing I think it is then21:36
jgriffitha patch was merged that was hoped to fix it, but doesn't look like it21:36
jgriffithttx: nope21:36
ttxjgriffith: any bug reference where the action is happening ?21:36
jgriffithttx: but I have a patch in to quit messing with that stupid thing too21:36
jgriffithttx: Not yet, it's been more trying to get to root than anything else21:37
jgriffithttx: In other words not even sure what to log it against :(21:37
*** asalkeld_afk is now known as asalkeld21:37
dolphmhttps://bugs.launchpad.net/devstack/+bug/1075630 ?21:37
uvirtbot`Launchpad bug 1075630 in devstack "Keystone 'invalid user token' on default devstack installation" [Undecided,New]21:37
ttxjgriffith: ok, when you have a bug ref, sent it my way so that I follow progress there21:37
jgriffithdolphm: to the rescue21:38
ttxOther questions on Cinder ?21:38
dolphmjgriffith: same issue?21:38
jgriffithyep, pretty much21:38
ttxok cool21:38
jgriffithbut there's all sorts of interesting details in jenkins21:38
jgriffithI should sync up with dolphm after this21:39
ttx#topic Nova status21:40
ttxvishy: o/21:40
ttx#link https://blueprints.launchpad.net/nova/grizzly21:40
ttxvishy: That looks quite good... is it near-complete ?21:40
*** openstack changes topic to "Nova status"21:40
ttxoops lag again21:40
vishyttx yeah21:40
*** markwash has joined #openstack-meeting21:40
vishyI suspect a few things might be missing21:40
ttxOne left @ https://blueprints.launchpad.net/nova/grizzly/+setgoals21:40
ttxuser-configurable-rbac is marked obsolete, can I remove it from list ?21:41
vishybut there is a lot in there already21:41
vishyyes21:41
ttxYou should encourage assignees to set a milestone target too.21:41
ttx#link https://launchpad.net/nova/+milestone/grizzly-121:41
ttxWould be great to have updated status on grizzly-hyper-v-nova-compute21:42
ttxAbout server-count-for-nova-flavors...21:42
ttxit's se tto grizzly-1 but not formally approved for grizzly series goal21:43
ttxyou might want to fix it one way or another21:43
*** gabriel has joined #openstack-meeting21:43
ttxOtherwise this milestone looks in pretty good shape.21:43
vishyyeah just got it21:43
ttxOh, and nova-v2-api-audit needs an updated status too (sdague)21:44
ttxvishy: Anything else ?21:44
vishyttx: no. Update coming soon21:44
sdaguettx: yeh, sure, I just moved to grizzly-1 today, it may be tight for that, but wanted to set myself something agressive21:44
ttxCool. Questions on Nova ?21:45
ttxsdague: just set to anoything but "unknown" which means we lost contact with the assignee21:45
sdaguesure21:45
sdagueset to started21:45
ttxsdague: thx!21:45
*** rkukura has joined #openstack-meeting21:45
ttx#topic Horizon status21:46
*** openstack changes topic to "Horizon status"21:46
ttxgabrielhurley: hey21:46
ttx#link https://blueprints.launchpad.net/horizon/grizzly21:46
gabrielhurleyhey21:46
ttxLooks good, is it complete from where you stand ?21:46
gabrielhurleyit is, as far as I know21:47
ttx#link https://launchpad.net/horizon/+milestone/grizzly-121:47
gabrielhurleymight see one or two blueprints come out fo the quantum team21:47
gabrielhurleybut that'll be at their discretion21:47
gabrielhurleyG1 is coming along21:47
gabrielhurleyI'll roll most of the bugs into the next milestone21:47
ttxgabrielhurley: sure, that's ok, just need to reflect the current knowledge, which is sometimes hard to do after the summit :)21:47
gabrielhurleybut the high priority stuff is done21:47
ttxWould be good to set status on define-flavor-for-project, otherwise looks on track to me21:48
gabrielhurley'will do21:48
ttxgabrielhurley: anything else ?21:48
gabrielhurleynope, just keep up the good work21:48
ttxQuestions for Horizon ?21:48
ttx#topic Incubated projects21:48
*** openstack changes topic to "Incubated projects"21:48
ttxAnyone to talk Ceilometer ?21:48
eglynn_o/21:48
jd__o/21:48
ttxhere you are :)21:48
eglynn_so the team is still working on distilling outputs from summit discussion into roadmap items21:49
eglynn_and prioritizing according to needs/interests21:49
ttxYes, I'd recommend you start working on a Grizzly plan here21:49
ttxCreating milestones, and targeting blueprints there21:49
ttxWe are planning on trying to be release-managed by me for G2 ?21:49
eglynn_yep, that work is in train21:49
eglynn_#link http://wiki.openstack.org/EfficientMetering/RoadMap21:49
eglynn_(still a WIP)21:50
*** MarkAtwood has quit IRC21:50
eglynn_plan is to get in train with the milestone releases by G-3, latest21:50
ttx#action ttx to look into what's missing in CI to support integrated releases21:50
ttx(for ceilometer)21:50
ttxeglynn_: anything else on your mind ?21:50
eglynn_also awaiting a gerrit reboot to reflect renaming (stackforge/ceilo -> openstack/ceilo)21:50
eglynn_IIUC to be batched up with the common -> oslo renaming21:51
ttxright, any eta on that ?21:51
jd__depends on -infra I guess?21:51
eglynn_not a concrete ETA as yet21:51
ttxsure, wondering if they gave you one21:51
fungiany idea who in ci you were working with on that?21:51
*** jfriedly has joined #openstack-meeting21:51
*** ryanpetr_ has joined #openstack-meeting21:51
ttxfungi: jeblair methinks21:52
eglynn_yep jeblair21:52
fungiokay, i'll ping him but he's somewhat out of pocket21:52
ttxeglynn_: anything else you wanted to mention ?21:52
eglynn_still some unknowns we need to clarify, e.g. requirements for detailed instrumentation21:52
eglynn_also I'm working on getting my hands around Synaps21:52
eglynn_(a big ol' beast with some awkward dependencies)21:52
eglynn_that's about it ...21:53
ttxWill include Heat in that slot for next week21:53
*** arosen has quit IRC21:53
ttx(since it was just accepoted for incubation as well)21:53
ttx#topic Other Team reports21:54
*** openstack changes topic to "Other Team reports"21:54
ttxQA, Docs, CI: anyone ?21:54
fungijust one quick item for ci21:54
* annegentle__ sent my updates to the mailing list21:54
fungiannegentle__ can go first21:54
ttxannegentle: anything to add on top of your email update ?21:55
*** ryanpetrello has quit IRC21:55
annegentle__nope, go ahead fungi21:55
fungiokay21:55
*** markmc has quit IRC21:55
fungimordred and jeblair just wanted me to raise visibility for the issue jgriffith was discussing above21:55
*** gabriel has quit IRC21:55
fungibasically to note that it's resulting in some nondeterminism in the devstack gate21:56
ttxhte keystone one, not the kernel one, right ?21:56
fungiright21:56
ttxyes, it's a high priority to fix that one21:56
fungiso if volume creation results in a "ERROR: n/a (HTTP 401)" it's that issue21:56
fungia recheck *may* get you back on track21:56
fungianyway, that was all for us as far as i know21:57
ttxjgriffith should ping us all if he's blocked on progress on that issue21:57
*** dwcramer has quit IRC21:57
ttxAny other team lead with a status report ?21:57
fungiseems to be #link https://bugs.launchpad.net/devstack/+bug/1075630 as dolphm said earlier21:57
uvirtbot`Launchpad bug 1075630 in devstack "Keystone 'invalid user token' on default devstack installation" [Undecided,New]21:57
ttx#link https://bugs.launchpad.net/devstack/+bug/107563021:58
ttx#info CI borked by above bug, top prio to fix21:58
ttx#topic Open discussion21:58
*** openstack changes topic to "Open discussion"21:58
ttxAnything else, anyone ?21:58
* ttx wonders if with the addition of oslo and new incubated projects we should reorganize this meeting to have more time21:59
ttxmaybe have release guys participate to inclubated projects meetings rather than the other way around21:59
ttxit's getting harder to fit in one hour21:59
ttx#action ttx to look into ways to fit all projects in the release meeting22:00
eglynn_good to have the incubated projects involved at the big boy's table tho'22:00
eglynn_(IMO)22:00
ttxyeah, maybe we hsould just say the meeting lasts 75 min22:01
eglynn_yep, that could work22:01
ttxok well, not this time22:01
ttx#endmeeting22:01
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"22:01
openstackMeeting ended Tue Nov  6 22:01:51 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2012/project.2012-11-06-21.03.html22:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2012/project.2012-11-06-21.03.txt22:01
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2012/project.2012-11-06-21.03.log.html22:01
notmynamettx: the reality is that the only person that needs the full 75 minutes is you. the independent project updates aren't as important22:01
*** gabrielhurley has quit IRC22:01
ttxthanks everyone22:01
*** Vek has left #openstack-meeting22:02
notmynamettx: a schedule for each project may allow more organized discussions, even if it all takes 75-90 minutes cumulatively22:02
ttxnotmyname: yes, hat's true. maybe reorganize so that the common stuff is scheduled more at the start than at the end22:02
*** koolhead17 has quit IRC22:03
ttxoh, you mean, swift at 21:15 UTC etc ?22:03
notmynameIOW, eg, 10 minues common, 10 minutes keystone, 5 minutes swift, 20 minutes nova, etc22:03
notmynameya, exactly22:03
notmynameand whatever works22:03
ttxthat's a good idea. Kinda not good for me because this meeting is late, but...22:03
notmynamethe disadvantage is being flexible over time and on different weeks depending what's going on in the project22:03
ttxIt's still valuable that i.e. keystone PTL can raise a question during Nova's time22:04
ttxbut that doesn't really prevent that22:04
notmynameagreed22:04
ttxI'll think a bit more about it22:05
ttxbut we can't double the number of projects and still have the same ole meeting :)22:05
*** patelna has joined #openstack-meeting22:05
notmynameindeed22:06
*** jpich has quit IRC22:08
*** Mr_T has joined #openstack-meeting22:10
*** markvoelker has quit IRC22:10
*** anniec has quit IRC22:12
*** anniec has joined #openstack-meeting22:13
*** ryanpetr_ has quit IRC22:14
*** ryanpetrello has joined #openstack-meeting22:14
*** dolphm has quit IRC22:15
*** lloydde has joined #openstack-meeting22:17
*** gatuus has quit IRC22:18
*** shardy is now known as shardy_afk22:18
*** dprince has joined #openstack-meeting22:20
*** heckj has quit IRC22:23
*** tgall_foo has quit IRC22:24
*** ayoung has quit IRC22:26
*** metral has joined #openstack-meeting22:28
*** ayoung has joined #openstack-meeting22:40
*** mtreinish has quit IRC22:42
*** dprince has quit IRC22:46
*** lloydde has quit IRC22:50
*** samkottler is now known as samkottler|out22:51
*** john5223 has quit IRC22:57
*** Gordonz has quit IRC23:00
*** metral has quit IRC23:01
*** rnirmal has quit IRC23:02
*** cp16net is now known as cp16net|away23:09
*** littleidea has quit IRC23:17
*** littleidea has joined #openstack-meeting23:18
*** annegentle__ has quit IRC23:19
*** s0mik has quit IRC23:32
*** tgall_foo has joined #openstack-meeting23:37
*** s0mik has joined #openstack-meeting23:38
*** gongysh has joined #openstack-meeting23:40
*** mnewby_ has joined #openstack-meeting23:41
*** maurosr has joined #openstack-meeting23:47
*** tgall_foo has quit IRC23:51
*** jrodom has joined #openstack-meeting23:52
*** maurosr has quit IRC23:53

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