Tuesday, 2012-05-01

*** joearnold has joined #openstack-meeting00:00
*** dendro-afk is now known as dendrobates00:11
*** edygarcia_ has joined #openstack-meeting00:12
*** edygarcia_ has quit IRC00:15
*** edygarcia has quit IRC00:15
*** edygarcia has joined #openstack-meeting00:21
*** edygarcia_ has joined #openstack-meeting00:25
*** edygarcia has quit IRC00:27
*** edygarcia_ has quit IRC00:29
*** edygarcia_ has joined #openstack-meeting00:31
*** pengyong has joined #openstack-meeting00:38
*** pengyong has quit IRC00:43
*** s0mik has quit IRC00:46
*** mnewby has quit IRC00:46
*** joearnold has quit IRC00:47
*** edygarcia_ has quit IRC00:53
*** blamar has quit IRC00:53
*** jakedahn is now known as jakedahn_zz00:54
*** joearnold has joined #openstack-meeting00:54
*** reed has quit IRC01:03
*** blamar has joined #openstack-meeting01:06
*** blamar has quit IRC01:06
*** blamar has joined #openstack-meeting01:07
*** ayoung has quit IRC01:13
*** pengyong has joined #openstack-meeting01:23
*** joearnold has quit IRC01:29
*** hggdh has quit IRC01:36
*** hggdh has joined #openstack-meeting01:38
*** Mandell has quit IRC01:42
*** adjohn has quit IRC01:46
*** adjohn has joined #openstack-meeting01:47
*** novas0x2a|laptop has quit IRC01:49
*** jakedahn_zz is now known as jakedahn01:51
*** anderstj has joined #openstack-meeting02:23
*** jaypipes has quit IRC02:28
*** mdrnstm has quit IRC02:28
*** adjohn has joined #openstack-meeting02:31
*** s0mik has joined #openstack-meeting02:33
*** jaypipes has joined #openstack-meeting02:35
*** s0mik has quit IRC02:39
*** jakedahn is now known as jakedahn_zz02:46
*** adjohn has quit IRC02:50
*** mnewby has joined #openstack-meeting02:52
*** jdurgin has quit IRC02:58
*** reed has joined #openstack-meeting02:59
*** reed has quit IRC02:59
*** Mandell has joined #openstack-meeting03:02
*** edygarcia has joined #openstack-meeting03:08
*** edygarcia has quit IRC03:09
*** sandywalsh_ has quit IRC03:11
*** lloydde has joined #openstack-meeting03:12
*** garyk has joined #openstack-meeting03:42
*** jgriffith has quit IRC03:42
*** joearnold has joined #openstack-meeting03:43
*** oubiwann has quit IRC03:55
*** lloydde has quit IRC03:56
*** adjohn has joined #openstack-meeting04:01
*** adjohn has quit IRC04:04
*** adjohn has joined #openstack-meeting04:04
*** mnewby has quit IRC04:05
*** mnewby has joined #openstack-meeting04:09
*** lloydde has joined #openstack-meeting04:21
*** gyee has quit IRC04:25
*** joearnold has quit IRC04:25
*** dolphm has joined #openstack-meeting04:34
*** dolphm has quit IRC04:49
*** Yak-n-Yeti has quit IRC04:59
*** dtroyer is now known as dtroyer_zzz05:01
*** mnewby has quit IRC05:05
*** anderstj has quit IRC05:18
*** blamar has quit IRC05:26
*** littleidea has quit IRC05:33
*** jacky has quit IRC05:36
*** jalcine has joined #openstack-meeting05:38
*** jakedahn_zz is now known as jakedahn06:02
*** Mandell has quit IRC06:02
*** jakedahn is now known as jakedahn_zz06:17
*** lloydde has quit IRC07:29
*** lloydde has joined #openstack-meeting07:29
*** lloydde has quit IRC07:34
*** openstack has joined #openstack-meeting07:45
*** ChanServ sets mode: +o openstack07:45
*** darraghb has joined #openstack-meeting07:54
*** GheRivero_ has joined #openstack-meeting08:06
*** adjohn has quit IRC08:12
*** derekh has joined #openstack-meeting08:15
*** derekh has quit IRC08:18
*** derekh has joined #openstack-meeting08:18
*** pengyong has quit IRC08:58
*** pengyong has joined #openstack-meeting08:59
*** chilung__ has joined #openstack-meeting09:10
*** chilung__ has quit IRC09:12
*** GheRivero_ has quit IRC11:22
*** dolphm has joined #openstack-meeting11:56
*** GheRivero_ has joined #openstack-meeting12:17
*** dprince has joined #openstack-meeting12:22
*** sandywalsh has joined #openstack-meeting12:22
*** deshantm has joined #openstack-meeting12:39
*** tong has joined #openstack-meeting12:45
*** markmcclain has quit IRC12:58
*** littleidea has joined #openstack-meeting13:00
*** ayoung has joined #openstack-meeting13:21
*** dtroyer_zzz is now known as dtroyer13:27
*** galstrom has joined #openstack-meeting13:36
*** jalcine is now known as jacky13:37
*** edygarcia has joined #openstack-meeting13:46
*** rackerjoe has joined #openstack-meeting13:50
*** sandywalsh_ has joined #openstack-meeting13:52
*** sandywalsh has quit IRC13:52
*** markmcclain has joined #openstack-meeting13:59
*** oubiwann has joined #openstack-meeting14:05
*** ryanpetrello has joined #openstack-meeting14:07
*** blamar has joined #openstack-meeting14:10
*** Amw3000 has joined #openstack-meeting14:14
*** anderstj has joined #openstack-meeting14:19
*** joesavak has joined #openstack-meeting14:24
*** mattray has joined #openstack-meeting14:25
*** dtroyer is now known as dtroyer_zzz14:26
*** dendrobates is now known as dendro-afk14:26
*** Yak-n-Yeti has joined #openstack-meeting14:30
*** edygarcia has quit IRC14:39
*** edygarcia has joined #openstack-meeting14:40
*** edygarcia has quit IRC14:42
*** s0mik has joined #openstack-meeting14:44
*** Yak-n-Yeti has quit IRC14:47
*** s0mik has quit IRC14:49
*** edygarcia has joined #openstack-meeting14:50
*** Gordonz has joined #openstack-meeting14:56
*** jsavak has joined #openstack-meeting15:00
*** rnirmal has joined #openstack-meeting15:01
*** joesavak has quit IRC15:02
*** markmcclain has quit IRC15:06
*** markmcclain has joined #openstack-meeting15:10
*** edygarcia_ has joined #openstack-meeting15:18
*** Yak-n-Yeti has joined #openstack-meeting15:20
*** edygarcia has quit IRC15:21
*** edygarcia_ is now known as edygarcia15:21
*** jsavak has quit IRC15:21
*** oubiwann has quit IRC15:22
*** markmcclain has quit IRC15:23
*** ryanpetrello has quit IRC15:24
*** garyk has quit IRC15:32
*** Gordonz has quit IRC15:33
*** jsavak has joined #openstack-meeting15:38
*** Gordonz has joined #openstack-meeting15:38
*** Gordonz has quit IRC15:39
*** Gordonz has joined #openstack-meeting15:40
*** lloydde has joined #openstack-meeting15:41
*** jgriffith has joined #openstack-meeting15:52
*** primeministerp has joined #openstack-meeting16:01
*** primeministerp has quit IRC16:08
*** primeministerp has joined #openstack-meeting16:08
*** garyk has joined #openstack-meeting16:09
*** joesavak has joined #openstack-meeting16:17
*** jsavak has quit IRC16:19
*** dtroyer_zzz is now known as dtroyer16:21
*** Mandell has joined #openstack-meeting16:25
*** heckj has joined #openstack-meeting16:25
*** sandywalsh_ has quit IRC16:26
*** oubiwann has joined #openstack-meeting16:27
*** ryanpetrello has joined #openstack-meeting16:27
*** s0mik has joined #openstack-meeting16:28
*** markmcclain has joined #openstack-meeting16:29
*** Mandell has quit IRC16:33
*** pengyong has quit IRC16:35
*** mnewby has joined #openstack-meeting16:39
*** mnewby has joined #openstack-meeting16:39
*** dendro-afk is now known as dendrobates16:49
*** dolphm has quit IRC16:53
*** oubiwann has quit IRC17:00
*** adjohn has joined #openstack-meeting17:06
*** derekh has quit IRC17:07
*** jdurgin has joined #openstack-meeting17:07
*** oubiwann has joined #openstack-meeting17:09
*** adjohn has quit IRC17:10
*** primeministerp has quit IRC17:15
*** primeministerp has joined #openstack-meeting17:17
*** gyee has joined #openstack-meeting17:21
*** mdrnstm has joined #openstack-meeting17:36
*** rackerjoe has left #openstack-meeting17:37
*** dolphm has joined #openstack-meeting17:43
*** ewindisch has joined #openstack-meeting17:44
*** heckj_ has joined #openstack-meeting17:51
*** heckj_ has joined #openstack-meeting17:51
*** heckj has quit IRC17:52
*** heckj_ is now known as heckj17:52
* heckj wanders in for the keystone meeting in a few minutes...17:57
dolphmheckj: o/17:57
*** lcheng has joined #openstack-meeting17:57
ayoung\O/17:58
gyeethat's a big head17:58
ayoung\_/  ^^ \_/17:58
ayoung\_/  ^_^ \_/17:59
ayoungMetal17:59
ayoung\m/  ^_^ \m/17:59
*** bcwaldon has joined #openstack-meeting17:59
*** joearnold has joined #openstack-meeting17:59
heckjmorning all18:01
heckj#startmeeting18:01
openstackMeeting started Tue May  1 18:01:49 2012 UTC.  The chair is heckj. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** liemmn has joined #openstack-meeting18:02
heckjmoving slow today - gimme a sec to get the topics together18:02
*** rafaduran has joined #openstack-meeting18:02
heckj#topic Status and Progress18:03
*** openstack changes topic to "Status and Progress"18:03
heckjI've been going through blueprints, trying to identify who's working on what18:03
gyeeI'll be starting the domains BP shortly18:04
heckjayoung: haven't caught up with you yet. What's your general plans re: multiprocess-keystone-service18:04
liemmnYou can mark me down for tempurl one18:04
heckj#link https://blueprints.launchpad.net/keystone18:04
ayoung /me on IPv6 and PKI via HTTPD18:04
heckjgyee: what milestone are you aiming at for implementation? From our chat yesterday, I'm thinking F2 or F3.18:05
ayounghttps://blueprints.launchpad.net/keystone/+spec/multiprocess-keystone-service18:05
gyeeyes F2 if I work weekends18:05
heckjliemn: same question for you - what milestone are you aiming at for having an implementation18:05
ayoungheckj, I have a working prototype of Keystone running in HTTPD18:05
gyeeF3 is more realistic18:05
ayoungWrote up my notes here:18:05
ayounghttp://adam.younglogic.com/2012/04/keystone-httpd/18:05
ayoungthe two things I'd like to get eyeballs on are the locations for the wsgi enabling files and the HTTPD config18:06
heckjgyee: milestone F3 set18:06
gyeethank you sir18:06
heckjayoung: will look18:07
heckj#link http://adam.younglogic.com/2012/04/keystone-httpd/18:07
heckj#action - please give feedback to ayoung re: http://adam.younglogic.com/2012/04/keystone-httpd/18:07
ayoungheckj, realted to that is the discussion of deconflicting the URLS for Openstack in general18:07
ayoungrelated18:07
heckjayoung: what's your thought around implementation time for the PKI work - and are you leading that up?18:07
dolphmheckj: i think i'm down for rbac, unless termie sleepsonthefloor is already on it (bp is unassigned)18:08
*** atiwari has joined #openstack-meeting18:08
ayoungIE:  do we want https://hostname/keystone or  https://hostname/identity18:08
heckjdolphm: thanks - will assign. Thoughts on milestone?18:08
dolphmheckj: f218:08
ayoungheckj, again,  once I have HTTPD,  PKI becomes a lot easier18:08
dolphm(do we have a release schedule out yet? ..)18:08
*** kevin-lewis-9 has joined #openstack-meeting18:08
dolphmooh we do! http://wiki.openstack.org/FolsomReleaseSchedule18:09
heckjayoung: makes sense18:10
heckjayoung: I'm going to mark PKI for F3 at this point18:10
ayoungheckj, OK18:10
heckjayoung: can move as needed18:11
gyeeheckj, I think Liem's tempURL work depended on access key CRUD18:11
ayoungI'll try to have it done before then, but that is a safe bet18:11
gyeedo I get the green light for access key BP?18:11
heckjgyee: I thought we agreed to a yes at the summit, and that the idea was to rework the EC2 API CRUD pieces to be more generic and use that.18:12
heckjliemn: are you doing that work? gyee18:12
heckj?18:12
gyeegotcha18:12
heckjthere's no blueprint to that at this point...18:12
liemmnheckj, yeah, I will do the tempurl18:12
gyeeI'll pay Liem to do that work :)18:12
liemmnheckj, so the access key stuff still remains an extenstion?18:13
heckjliemn: is https://blueprints.launchpad.net/keystone/+spec/access-key-authentication what you're doing then?18:13
liemmnyes18:13
heckjliemmn: I'm drafting an v3 API now to drag these things into core - I'm expecting to have it up for comments by18:14
heckjF118:14
liemmnI don't think F1, probably F218:14
heckjgyee: would you create a blueprint to cover working EC2 to be generic to support general key access?18:15
heckjliemmn: I put you in F3 for now, can totally move in up if you'd prefer18:15
gyeeheckj, will do18:15
dolphmheckj: i assume you're covering all the BP's that will depend on a revised api?18:15
heckj#action: gyee to create BP to cover making access key storage EC2 more generic18:16
ayoungliemmn, how does that interact with PKI Blueprint?18:16
heckjdolphm: trying, but I'm sure I'll miss something in the first cut - or several. AIming to get that up ASAP so we can move on the impl work form there18:16
dolphmheckj: no worries18:17
ayounggyee, heckj I think we should ensure that PKI and Key access solutions are complementation18:18
ayoungcomplementary18:18
gyeeayoung, access is different from PKI18:18
ayounggyee, yes and no.18:18
gyeeaccess key auth is just like password auth, while PKI requires handshake18:18
ayoungUnderstood18:18
ayounggyee, you and I understand the distinctions,  but most people will not18:19
ayoungadditionally, there are overlapping concerns regarding key management etc18:19
ayoungkey generation...18:19
gyeegood luck with that :)18:19
ayounggyee, well, I do have a little bit of experience in dealing with it...18:20
ayoungheckj, I think we need an action Item something along the lines of "map out the whole PKI approach"18:20
gyeeI am putting in the requirement for OCSP, just for you18:20
ayoungsomething that connects the dots18:20
ayounggyee, stapling or server call?18:21
heckjayoung: definitely18:21
gyeereal time18:21
heckjayoung: would you create a blueprint to lay out the PKI approach? Document, etc18:21
*** galstrom has quit IRC18:22
*** novas0x2a|laptop has joined #openstack-meeting18:22
heckjayoung: we can do that like the V3 api - document & feedback in F1, impl in F2/F318:22
heckj#action: ayoung to create blueprint to document PKI approach for feedback18:22
ayoungheckj, will do, if gyee promises to help18:22
gyeesure18:22
heckj#action: gyee to help ayound with it18:22
heckj:-)18:22
liemmnayoung, I can help review too... I did the 2-way auth a while back for keystone diablo...18:23
ayoungliemmn, thanks.  I was planning on asking for your help, too.18:23
heckjOkay - any other work for Keystone that we don't have tracked as yet?18:25
heckjliemmn: are you set up as an openstack contributor? signed CLA and all that rot?18:26
liemmnheckj, yes18:26
liemmnFYI... separate topic... I filed a validation bug:  https://bugs.launchpad.net/keystone/+bug/99221418:26
uvirtbotLaunchpad bug 992214 in keystone "GET /tenants XSD schema validation fails" [Undecided,New]18:26
liemmnwe need to decide what the source of truth is... XSD or code :)18:27
*** Haneef has joined #openstack-meeting18:27
heckjliemmn: at the moment, it's code. Although we need to have integrated tests that verify the code against the API description (WADL, XSD, etc)18:28
heckjthe only way we can guarantee interop is with tests18:28
heckjTempest is still getting traction, so for now I'm in favor of getting integration tests like these into Keystone's testing framework - once they're in, we'll automatically gate on them with code updates.18:29
heckjliemmn: is that something you're interested in doing?18:29
ayoungIt seems to me that the XSD should be generated from the code18:29
gyee+118:29
dolphmliemmn: xsd:id should definitely be a string18:30
*** sandywalsh has joined #openstack-meeting18:30
heckjayoung: ideally - but in practice it turns out ot be a PITA. If you guys want to take that on as a prototype to try it out, I'm all game.18:30
dolphmayoung: additionally, some parts of the xsd are optional and keystone does not (and probably will never) implement them18:30
*** reed has joined #openstack-meeting18:30
ayoungdolphm, then why carry them?18:30
dolphmayoung: we're not the only implementation on the block18:30
*** joearnold has quit IRC18:31
heckjjust the only public one18:31
gyees/public/public and free/g18:31
gyee:)18:31
ayoungyou RAX folks holding out on us?18:31
*** Yak-n-Yeti has quit IRC18:31
heckjgyee: fair 'nough18:32
liemmnIMO... it should be the other way around... start out with XSD and then generate code...  That way, you don't let language specifics "leak" into the XSD...18:32
ayoungliemmn, +118:32
ayoungif, in fact, the XSD is the public contract18:32
ayoungand it sounds like it is.18:32
heckjliemmn: I disagree - the resulting code is horrific to maintain, and what we just crawled out from underneath18:32
*** Comet1 has joined #openstack-meeting18:32
*** Comet1 has quit IRC18:32
heckjI totally agree that need to match, and I think the way to verify that is with tests.18:32
heckjAn API without a concrete implementation that you can verify against is worse than useless18:33
liemmnyeah, in reality, code generation tools vary from language bindings to language bindings...18:33
heckjPersonally, I don't care about the XSD outside of providing a means to document the api.openstack.org site. To me, that's the primary value.18:33
liemmnheckj, I think both are important... tests and XSD serving as contracts for other implementers.18:34
dolphmheckj: +118:34
heckjliemmn: I agree that it's an important contract, but that wasn't the earlier assertion. Hence my suggestion of tests to verify.18:34
* gyee memo to self: write a lot of tests18:34
liemmnheckj: +118:34
dolphmi know rax adopted keystone's old integration tests at some point, worked well for them -- not sure what they're doing post-redux18:34
joesavako\18:35
heckjjoesavak!18:35
joesavakwe are using python keystone client in some of the integration tests against rax impl.18:35
dolphmjoesavak: awesome18:35
joesavakwe aren't using the keystone tests though against rax impl18:35
heckjjoesavak: totally your choice in maintaining a separate implementation.18:36
joesavakyuppers18:36
joesavakalso - while i'm not in a meeting -18:36
heckjjoesavak: unrelated to XSD contracts and such, there's a pile of BPs on the list with your name. What's the plan with implementing those? Who's working on those elements, and when are they aiming to have it implemented?18:36
joesavakMost likely, it'll be dolph working on those18:37
*** joearnold has joined #openstack-meeting18:37
joesavak2 highest priorities for RAX is RBAC and MFA18:37
dolphmjoesavak: not all of em!18:37
heckjjoesavak: I've got dolphm on RBAC18:37
heckjjoesavak: nothing on multifactor - who's doing that work?18:37
joesavakwe'll add the extension contract for MFA - but probably not do the keystone impl.. need help on that18:38
dolphmheckj: does multifactor need to land beyond supporting spec changes?18:38
*** lloydde_ has joined #openstack-meeting18:38
dolphmjoesavak: *18:38
joesavakfrom my perpsecitve, i'm ok with mfa being an OS-KS* extension that I can implement within RAX.18:39
heckjdolphm: I don't want to claim support in the API for anything that isn't in code. How complex it is, I don't care - but we need something to verify interop.18:39
ayoungjoesavak, what two factors do you consider most important?18:39
joesavaksms & email18:39
joesavakoutside of password/api-key auth support (first level auth)18:40
joesavakhi ayoung, dolphm, heckj, liemn, and gyee, by the way. ; )18:40
heckjjoesavak, dolph: if you want it to just be a private RS extension, there's no trouble with that - it just won't be part of the official KS release. I thought the intention from the summit was to have a simple multifactor implementation in the public Keystone though.18:40
gyeeI was going to refactor the keystone auth as part of access key impl18:41
gyeemake it a plugin style18:41
*** lloydde has quit IRC18:41
joesavakcool18:41
gyeebut if RAX wants to do it, you can have it :)18:41
joesavakgyee, be our guest. ;018:41
joesavak;)18:41
heckjgyee: it already is "plugin style" - could you be more specific with your plans?18:42
gyeenot really, I mean PAM style18:42
gyeelike JAAS18:42
dolphmgyee: plugin to the identity plugin?18:42
gyeethat way, you can add you own auth module based on auth type18:42
heckjgyee: you want to add another plugin layer for identity instead of simply writing an alternate backend driver for it?18:42
gyeewell, I want to be able to load different plugins based on auth type18:43
gyeei.e. passwordCredential -> password auth module18:43
heckjgyee: if you want to make a configurable backend, have at, but be aware the canonical API is at the keystone.identity.core.Driver class18:43
heckjgyee: okay by me18:44
gyeeI haven't dive into that part of the code that much, was just a brain fart18:44
liemmnI think we should keep it simple, and configurable whenever needed... I can discuss it with gyee...18:44
heckjgyee: no worries - dig in and holler w/ questions onto IRC or the list18:44
gyeewill do18:45
ayoungI think that the issue is we currently equate authentication with issuing a token.  We could easily split that18:45
dolphmin legacy, we talked about supporting a configurable list of auth methods, sorted by priority in the configuration -- the idea being each plugin would be passed the incoming auth blindly, and they could either return False or a successful auth (stopping on the first success)18:45
heckjjoesavak: what's your plan re: multifactor at this point? Or is that getting assigned to gyee?18:45
ayoungthen authenticate is authenticate.  requesting a token requires authentication18:45
*** edygarcia_ has joined #openstack-meeting18:46
joesavakgyee - will your plans support a half-token (indicating further auth to get a full token)?18:46
*** joearnold has quit IRC18:46
gyeeI can add a generic table to store the state information18:47
gyeejust a string, you can call it a half token18:47
gyeeI mean the plugins can make use of it18:47
joesavakok - we may be a rax extension on top of that to get us to what we need18:47
joesavakso mfa --> gyee. Additional bp will be created if that impl needs rax extension to get rax to work18:47
heckjgyee: do you agree?18:48
gyeeI am not doing mfa, just the refactoring of the auth part18:48
gyeenot the full monty, just half :)18:48
*** lcheng has quit IRC18:48
*** edygarcia has quit IRC18:48
*** edygarcia_ is now known as edygarcia18:48
heckjjoesavak: you're the one with it assigned. I'll leave it off the milestones for now - get back to me later?18:48
joesavakok - target mfa to me for now. gyee - are you targetting folsom 2/3?18:48
joesavakyup - i'll try to build off of what gyee does around folsom418:49
gyeejoesavak, f2 perhaps18:49
joesavakcool, thanks18:49
heckjupdated18:50
joesavakAlso - we've cleaned some of the contract out in https://github.com/carlosmarin/identity-api and are discussing here if it looks good to push back into gerrit. Take a look  - if you see anything odd let me know. I know that even cleaning a contract could cause uproar.18:50
heckj#action - feedback needed on https://github.com/carlosmarin/identity-api18:50
heckjWe have something like 8-9 minutes left18:51
dolphmjoesavak: tell him to push it -- feedback happens in gerrit :)18:51
heckj#topic open questions/issues18:51
*** openstack changes topic to "open questions/issues"18:51
*** lcheng has joined #openstack-meeting18:52
ayoungdo people prefer https://hostname/keystone  or https://hostname/identity for the unified URL scheme?  Informal poll.18:52
joesavakdolphm - i will by end of day18:52
rafaduranhttps://review.openstack.org/#/c/6425/ still needs approval18:52
joesavakhttps://hostname/identity18:52
heckjayoung: slight pref to 'identity', but I don't honestly care that mch18:52
dolphm /identity18:53
rafaduranI'm aslo thinking about starting a draft for https://bugs.launchpad.net/keystone/+bug/96309818:53
uvirtbotLaunchpad bug 963098 in keystone "Keystone isn't acting on consecutive failed logins" [High,Triaged]18:53
rafaduranany suggestion would be appreciated18:53
gyeeayoung, my magic 8 ball says identity18:53
dolphmrafaduran: a bp you mean?18:53
dolphmthat's a pretty strong informal consensus lol18:53
ayoungdolphm, I think that is the way that things are going to fo18:53
ayounggo18:53
rafadurandolphm: I mean gerrit review18:54
rafadurandolphm: review draft18:54
*** Shrews has joined #openstack-meeting18:57
heckjrafaduran: https://review.openstack.org/#/c/6425/ approved18:57
heckjWrappin' this up for today - back next week, same bat channel, same bat time18:57
rafaduranheckj: ok, thanks18:57
heckj#endmeeting18:57
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"18:57
heckj#endmeeting18:57
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"18:57
mtaylorhrm18:58
heckjwhere's the damn logs?18:58
mtaylorclarkb: ^^18:58
heckjgrrrr18:58
mtaylorheckj: we'll find em for ya18:58
heckj*sob* *sob* OK *sob*18:58
heckj(thank you)18:58
* mtaylor pats heckj on the back18:58
clarkbhmm, I don't think I touched the endmeeting code ... /me looks18:58
mtaylorit worked earlier today18:59
*** comstud_ is now known as comstud18:59
*** dolphm has quit IRC18:59
heckjbot being difficult, ah yeah.18:59
*** Transformer has joined #openstack-meeting18:59
mtaylordarned robots18:59
clarkbmtaylor: did meetingLocalConfig.py change? that is managed by puppet19:00
heckjnot seeing anything in http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/ beyond Apr 27th...19:00
*** Transformer has left #openstack-meeting19:00
*** pengyong has joined #openstack-meeting19:00
sorenCI meeting, no?19:01
mtaylor#startmeeting19:01
openstackmtaylor: Error: Can't start another meeting, one is in progress.19:01
*** jsavak has joined #openstack-meeting19:01
sorenPredictable :)19:01
heckjoooh - now we're screwed19:01
mtaylorclarkb: I didn't19:01
*** Mandell has joined #openstack-meeting19:01
mtaylorso, #endmeeting has just stopped working altogether. neat19:02
ayoungwhat happens if you try and set status?  Does it start a new meeting?19:02
*** joesavak has quit IRC19:02
sorenkill -HUP `pidof meetbot`19:02
*** rafaduran has quit IRC19:02
ayoung#end-meeting \19:02
ayoung#end-meeting19:02
sorensudo #endmeeting19:02
mtaylorhehe19:02
sorenOh.19:03
sorensudo \#endmeeting19:03
sorenHm.19:03
sorenI give up.19:03
sorenThat's all I had.19:03
mtaylorwhen sudo commands fail soren, I believe the world is ending19:03
ayoungsoren is not in the sudoers file.  This incident will be reported.19:03
sorenmtaylor: I've made arrangements. It's ok.19:03
LinuxJedimtaylor: want me to restart the bot?19:04
heckjI just saw a rocket leaving earth...19:04
clarkbLinuxJedi: made a change ~5 hours ago to update the mimetype19:04
sorenheckj: I've seen that movie. It turns out to be seafaring ships instead.19:04
soren</spoiler>19:04
LinuxJediclarkb: that was to nginx19:04
clarkbcould that have borked it?19:04
clarkbah19:04
soren#ENDMEETING19:05
sorenendmeeting, please.19:05
* LinuxJedi sshing into it now19:05
heckjhere come the big guns...19:05
mtaylorsee, this is better than a ci meeting ...19:05
LinuxJedicrap, it can't write the log file19:06
mtaylorperms?19:06
LinuxJediyep19:06
LinuxJedidon't know why this is hitting us now though19:06
mtaylorcan you grant dir perms for now and have heckj try #endmeeting again?19:06
heckjwilling19:06
mtaylordidn't we add control of that dir recently to puppet?19:07
sorenIf only there was a way to find out.19:07
* mtaylor stabs soren with a salmon19:07
sorenLike, some kind of system to track changes to code.19:07
heckjdon't waste good fish!19:08
* LinuxJedi wonders why it is all owned by mordred all of a sudden19:08
mtaylorhrm.19:08
* mtaylor also wonders that19:08
LinuxJedi#endmeeting19:08
*** openstack has joined #openstack-meeting19:09
*** ChanServ sets mode: +o openstack19:09
heckjnow?19:09
heckj#endmeeting19:10
heckjderp, guess not19:10
LinuxJedi#startmeeting19:10
openstackMeeting started Tue May  1 19:10:22 2012 UTC.  The chair is LinuxJedi. Information about MeetBot at http://wiki.debian.org/MeetBot.19:10
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:10
heckjOk - might have lost #keystone logs, but looks like it's working now19:10
sorenLinuxJedi: Try ending it. Just for giggles.19:11
LinuxJediI think the log did save on the restart19:11
LinuxJedi#endmeeting19:11
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"19:11
openstackMeeting ended Tue May  1 19:11:21 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:11
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-01-19.10.html19:11
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-01-19.10.txt19:11
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-01-19.10.log.html19:11
sorenWhoo!19:11
LinuxJedi#startmeeting19:11
openstackMeeting started Tue May  1 19:11:29 2012 UTC.  The chair is LinuxJedi. Information about MeetBot at http://wiki.debian.org/MeetBot.19:11
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:11
mtaylorwhee!19:11
*** jaypipes is now known as jaypipes-afk19:11
sorenThanks everyone. SEe yo unext week.19:11
mtaylorgreat!19:11
mtaylorso - first item, as you may have noticed, we did some work on meetbot19:12
LinuxJedihttp://eavesdrop.openstack.org/irclogs/%23openstack-meeting/%23openstack-meeting.2012-05-01.log appears to be the previous meeting19:12
heckjfound'em19:12
LinuxJedidoh, I mean http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-01-18.01.log.txt19:12
heckjLinked into the wiki - I thin the MIME types at eavesdrop aren't working for the HTML though - it's forcing my browser to download rather than display directly for the HTML19:13
LinuxJediheckj: already a bug open for that19:14
clarkbthings are just going to break today for LinuxJedi I think19:14
heckjcool, thanks LinuxJedi!19:14
LinuxJediheckj: I'm already doing a 12-14 hour day today though so unlikely it will get fixed before tomorrow morning19:14
heckjno worries19:15
mtaylorLinuxJedi: bah. I thought you usually did 20 hour days!19:15
LinuxJedimtaylor: I'm slipping ;)19:15
mtaylorhehe19:15
*** s0mik has quit IRC19:16
LinuxJedimtaylor: plus my wife gets pissed if I work too much now19:16
LinuxJedimtaylor: anyway, meeting is running :)19:16
clarkbbut yes voting has been added. use the '#startvote some question? option1 option2' command to begin a voting session then vote using #vote option119:16
mtaylorclarkb: ++19:16
clarkbcheck vote status with #showvote and end voting with #endvote19:17
mtaylorthis makes me happy. thanks clarkb19:17
*** kevin-lewis-9 has quit IRC19:17
LinuxJedi#startvote do we love voting? yes no19:17
openstackBegin voting on: do we love voting? Valid vote options are yes, no.19:17
openstackVote using '#vote OPTION'. Only your last vote counts.19:17
LinuxJedi#vote yes19:18
mtaylor#vote yes19:18
clarkb#vote no19:18
clarkb#showvote19:18
openstackyes (2): mtaylor, LinuxJedi19:18
openstackno (1): clarkb19:18
*** heckj_ has joined #openstack-meeting19:18
LinuxJediawesome19:18
soren#vote whuh?19:18
LinuxJedi#endvote19:18
Shrews#vote yes19:18
openstacksoren: whuh? is not a valid option. Valid options are yes, no.19:18
Shrews#vote yes19:18
openstackVoted on "do we love voting?" Results are19:18
Shrews#vote yes19:18
openstackyes (2): mtaylor, LinuxJedi19:18
openstackno (1): clarkb19:18
sorenAw.19:18
Shrews#showvote19:18
mtaylorLinuxJedi ended the vote already19:18
Shrewsdamn19:18
* Shrews wanted to break it19:19
LinuxJedianyway, that was a quick demo ;)19:19
*** joearnold has joined #openstack-meeting19:19
LinuxJediShrews: I believe clarkb has a test channel to break it on19:19
clarkb#testmeetbot here on freenode19:19
*** joearnold has quit IRC19:19
*** lcheng has quit IRC19:19
clarkbI dno't promise the bot will always be listening through :)19:19
*** heckj has quit IRC19:19
*** heckj_ is now known as heckj19:19
*** darraghb has quit IRC19:19
*** anderstj has quit IRC19:20
*** heckj has quit IRC19:20
mtaylorjeblair is hiking in the utah desert this week, but he's going to be looking at some improvements to the gerrit trigger plugin when he gets back19:20
LinuxJediI also brought the irclogs back to meetbot today and knocked up a quick 30 second homepage on http://eavesdrop.openstack.org/ to be themed at a later date19:20
mtaylorspecifically, support for matrix jobs, dependent jobs, and optimistic branch prediction-based building (all of which kind of tie in together)19:21
mtaylorand in addition to beating his head against a brickwall trying to get new trystack machines properly stood up, devananda is going to poke at openvz support on our build slaves19:22
mtaylorLinuxJedi: what're you up to these days?19:22
LinuxJedimtaylor: so, we not have meetbot under puppet control, which mostly works great apart from the logging blip just now19:23
LinuxJediI've done lots of CI docs19:23
LinuxJediincluding a couple of useful howtos for people wanting to work with CI stuff19:23
LinuxJediJenkins job filler has had a lot of work done to it, but there are still a few things to be sorted out19:24
LinuxJediStackforge gerrit managed to run out of disk which was a barrel of fun19:24
mtaylorwhee!19:24
mtaylor(Shrews is adding some logrotation there)19:25
LinuxJediyes, it was all mysql backups19:25
LinuxJediand the puppet server on stackforge fell over which caused some more fun19:25
*** justinsb has quit IRC19:25
LinuxJediI've worked on adding the Ceilometer project to Stackforge, that should be ready tomorrow19:25
LinuxJediand that is about all I remember off the top of my head19:26
mtaylorsounds like a good week19:26
*** justinsb has joined #openstack-meeting19:26
LinuxJedimtaylor: two things that came up, lists and whether or not to do translations for logs19:26
LinuxJedimtaylor: I argued for translations for logs with error codes, but I'm not sure if that is a CI thing or a "something else" thing19:27
mtayloryes... someone from dreamhost is going to help with mailinglists, right?19:27
clarkbI was looking at nova and its use of gettext and it looks like nova will currently attempt to put translations in the logs19:27
clarkbwith error codes19:27
LinuxJedimtaylor: I believe so, I'm a little behind catching up on that to be honest.19:27
*** jakedahn_zz is now known as jakedahn19:29
mtaylorwe've had a few issues arise with the wiki over the last week, which brings up that we need to actually manage it19:31
mtaylorannegentle requested that we migrate to mediawiki, and suggested that our friends at wikipedia might be interested in helping us with that19:31
annegentlewoo woo19:31
LinuxJedimtaylor: we inherited another server?19:32
mtaylorwell, we have it now already - we just don't do anything with it19:32
LinuxJediah, fair enough19:33
LinuxJedimtaylor: this also falls into "what should be docs and what should be wiki"19:33
LinuxJedisimilar problem to what we had in Drizzle19:33
mtaylorI don't have any specific action plan at the moment - just that it's one of those things we should probably actually, you know, care for19:33
LinuxJedi:)19:34
mtayloralso "manage the wiki" really menas "ensure that someone is managing the wiki"19:34
LinuxJediah, like the mailing lists then ;)19:35
mtayloryup19:35
* LinuxJedi is less concerned now19:35
mtaylorgoal for this week from me is to try to finish getting the tox alignment done and then turning jenkins job filler on for the rest of the projects19:35
mtaylorour jenkins job divergence is a little silly at the moment19:35
LinuxJedimtaylor: is that wise considering Jim just turned it off for everything?19:36
mtayloras part of that, we're also making sure that when jenkins runs the tests it grabs xunit output19:36
mtaylorLinuxJedi: well, what I mean is...19:36
mtaylorLinuxJedi: get the tox alignment done this week _so_that_ we _could_ turn on the jenkins job filler19:36
LinuxJediah! ok then :)19:36
mtaylorLinuxJedi: now that you bring it up though... the bit we can't do in puppet at the moment (override messages)19:37
mtaylorLinuxJedi: did jeblair talk to you about his idea to just have a python script do that bit?19:37
LinuxJedimtaylor: I'm planning on fixing the remaining issues with the job filler this week19:37
LinuxJedimtaylor: no19:37
mtaylorLinuxJedi: idea: rather than implementing all of the things directly inside of ruby/puppet extension ... just drop a python script on the box and run that19:38
LinuxJediI'm sure I could do it in ruby, but I'm also sure I will kill someone in the process19:38
LinuxJedimtaylor: cool :)19:38
mtayloranyway - if you get that stuff going, and I get the projects ready for it19:39
mtaylormaybe next week we can actually move them all to puppet/git management19:39
LinuxJedi++19:39
*** anderstj has joined #openstack-meeting19:39
mtayloroh - one more thing...19:41
mtayloralthough it's mildly hp specific... we finally got our internal legal stuff done which allowed those of us who work for hp to sign the google cla for gerrit19:41
mtaylorwhich means our patches to gerrit are finally starting to go upstream19:41
LinuxJediyay :)19:42
* LinuxJedi upstreams a patch to re-write it in Python ;)19:42
mtaylorhehe... that's actually just a git reset command ...19:42
LinuxJedilol :)19:42
mtaylorthat would be a re-re-write19:42
LinuxJediindeed :)19:43
mtaylorthat's all I've got ... anybody else out there have anything?19:43
LinuxJediI really do plan on having the stackforge www up this week19:44
* clarkb is working on getting i8ln working now19:44
LinuxJediif only as a basic holding page19:44
mtaylorw00t to both things19:44
clarkblooks like Horizon is pushing hard to use transifex so it looks like we will be starting there19:44
mtaylorfine by me19:44
sorenWhat, Gerrit used to be written in Python?19:44
mtaylorsoren: yup19:45
sorenHm. Interesting.19:45
mtaylorsoren: check out the v1.0 tag in the repo19:45
mtaylorit's a django app19:45
sorenNeat.19:45
clarkbalso, to fix nova i8ln whats the easiest way to stand up a quick dev/test environment for nova/openstack19:45
clarkbdevstack?19:45
* LinuxJedi can only guess it because Android is Javaish (depending on your side of the Oracle suit)19:45
sorenI wonder what motivated the rewrite.19:45
mtaylorclarkb: devstack19:45
sorenLinuxJedi: There's probably a connection there, yeah.19:46
mtayloralso, jgit19:46
*** anderstj has quit IRC19:47
mtayloralthough python-git is pretty good these days19:47
LinuxJedianyway, anyone have anything else before I find out that meetbot is broken again?19:48
mtaylornope19:49
LinuxJediok then19:49
LinuxJedi#endmeeting19:49
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"19:49
openstackMeeting ended Tue May  1 19:49:39 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-01-19.11.html19:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-01-19.11.txt19:49
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-01-19.11.log.html19:49
clarkbit didnt break this time :)19:50
LinuxJediafter meeting note: I'll fix the mime types on those links tomorrow ^19:50
mtaylorw00t19:50
LinuxJediclarkb: it is no longer all owned by mtaylor (I can't even see in any bash history or log how that happened either)19:51
clarkbwas the bot running under mtaylor at some point?19:51
LinuxJedinope, clean server installed using puppet19:52
clarkbweird19:52
LinuxJediah, I know what happened19:52
*** tong has quit IRC19:52
LinuxJediI migrated the old logs over, they must have been owned by mtaylor, the cp command must have changed the dir ownership19:52
LinuxJedior they must have the same uid as mtaylor19:52
LinuxJedidamn19:52
* LinuxJedi is an idiot for not thinking of that19:53
clarkbwell at least we know what broke now. I am off to find lunch now.19:53
*** Shrews has left #openstack-meeting19:55
*** dendrobates is now known as dendro-afk19:55
*** heckj has joined #openstack-meeting19:59
*** anotherjesse_zz is now known as anotherjesse20:00
ttxo/20:00
heckjo/20:00
vishyo/20:00
anotherjesseo/20:01
ttxdid anyone hear from jbryce ?20:01
* heckj nopes20:01
*** danwent has joined #openstack-meeting20:01
ttxthis is starting to look like a recurrent bad joke20:02
bcwaldonbut waldon's here this time!20:02
heckjyeah!!!20:02
vishy5 ppb members?20:03
vishythat's all we got?20:03
heckjyeps20:04
anotherjesseI only came because vishy said to - I assumed no email from jbryce == no meeting20:04
*** devcamcar_ has joined #openstack-meeting20:04
heckjdevcamcar is probably out in the Seattle riots having fun20:05
*** rnirmal has quit IRC20:05
devcamcar_o/20:05
heckjer, guess not20:05
vishyI sent an email requesting a meeting last week and it was pushed to this week20:05
devcamcar_just set a cop car on fire20:05
vishybut oh well20:05
anotherjesseglad that is on the record20:05
danwentanotherjesse: are IRC logs admissible in court?20:06
notmynameI'mhere20:06
bcwaldongod I hope not20:06
ttxwe might need to select a more... available chair. And no, I'm not volunteering.20:06
bcwaldonI propose vishy20:06
notmynameheh, I'm sure he doesn't have enough free time already ;-)20:07
* vishy hides20:07
devcamcar_I propose anotherjesse :)20:07
cloudflydanwent yes20:07
cloudflyish20:07
*** s0mik has joined #openstack-meeting20:07
* anotherjesse hides20:07
ttxwell, anotherjesse or johnpur would make sense, since they are appointed :P20:07
mtaylorheckj: there are riots in seattle?20:07
ttxor joshua, but he isn't even around :)20:08
heckjthe riots are busting windows a block away from the office20:08
mtaylorREALLY?20:08
notmynamemtaylor: the indie music coffee shop closed early, but you probably haven't heard of it20:08
mtaylorwow20:08
heckjand there go the cops after them..20:08
mtaylornotmyname: haha20:08
heckjif you're bored: http://www.kirotv.com/videos/news/live-event-from-kiro-7-eyewitness-news/vC4c3/20:09
mtaylorheckj: here in nyc there's helicopters going overhead a lot, but I dont' think it's turned into rioting20:09
cloudflyoccupy related.20:09
heckjmtaylor: just a few of the usual suspects doing stupid shit. Most of the protest downtown looks to be quite peaceful.20:09
cloudflysurprising lack of rioting in sf20:09
anotherjesseoccupy openstack meeting20:09
termiecloudfly: uh, there was a bunch of rioting20:10
cloudflywhere?20:10
heckjThere's jesse! Quick, tag him at chair!20:10
termiecloudfly: http://www.missionmission.org/20:10
termiecloudfly: in the mission20:10
cloudflyi missed it all apparently.20:10
termiecloudfly: today there are protests all over20:10
termiebut also mayday != occupy20:10
termiethey just using the same day20:10
cloudflycould be a cinco de mayo event early.20:10
termiemayday is a traditional protest day, it is international worker's day20:10
ttxan holiday in France.20:11
heckjSo we're bagging the PPB meeting without a chair, or carrying on?20:11
mtaylorttx: isn't every day a traditionaly protest day in france?20:11
bcwaldonI could go play some ping poing20:11
notmynamedo we have enough people here for a meeting?20:12
ttxheckj: we should appoint anotherjesse so that next week we have a meeting ?20:12
devcamcar_Yup20:12
vishyi think we do have enough now20:12
* mtaylor doesn't have a seat, so don't count him20:12
notmynamethen we should have a meeting20:12
* vishy appoints mtaylor a seat20:12
bcwaldonare there 9 or 12 of us?20:12
bcwaldonor 1420:12
mtaylorneat!20:12
* notmyname is very interested in a 3rd party policy20:13
mtaylorwe should have just started appointing people a while ago...20:13
ttxwe are 15. Needs 820:13
*** mattray has quit IRC20:13
ttxwe are only 720:13
ttxoh dan is here. 8.20:13
danwent:)20:14
vishyttx, heckj, devcamcar, bcwaldon, anotherjesse, vishy, notmyname, danwent!20:14
bcwaldonok, and we have clear goals for this meeting?20:14
vishywoo20:14
vishyyes20:14
bcwaldonok, then lets get going20:14
vishydecide if we have a policy about 3rd party apis20:14
bcwaldonwho wants to chair this20:14
heckj#startmeeting20:14
openstackMeeting started Tue May  1 20:14:45 2012 UTC.  The chair is heckj. Information about MeetBot at http://wiki.debian.org/MeetBot.20:14
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:14
bcwaldonthank you20:14
notmynameheckj: thanks :-)20:14
vishythanks heckj!20:14
heckj#topic: 3rd party API policy20:15
*** openstack changes topic to ": 3rd party API policy"20:15
mtaylorheckj: try not to break #endmeeting again20:15
heckjmtaylor: pbbbbbbbbbbbb20:15
notmynameso we can either have a general policy or let project decide right? and if it's a general policy, what is it?20:15
heckjwho has proposals?20:15
vishyso i think the first question is do we have a 3rd party api policy20:15
notmynameI don't think we do right now20:15
vishyshould we have one?20:15
notmynameI think we should :-)20:16
vishyi think it is important that the ppb has an opinion20:16
bcwaldonguidelines, at least20:16
devcamcar_what does it mean to have one?20:16
mtaylorfor the sake of the peanut gallery, what is meant by 3rd party api policy?20:16
vishyeven if we say up to the ptls20:16
vishymtaylor: so other apis esp. open standards20:16
vishydo we include them in core projects20:16
mtaylorkk20:16
cloudflya generic api rules of conformity would be nice.20:16
anotherjessedevcamcar_: it means if someone whats to build another API to openstack, they would know how to do it …  (eg, if we aren't going to accept it into the core projects they would know they should build a proxy or external plugin)20:16
* mtaylor now understands the conversation20:17
ttxso the question is: is each project free to add a new external API, or does it need to go through PPB approval ?20:17
*** russellb has joined #openstack-meeting20:17
anotherjessewe currently have AWS interop APIs in the projects.  one thought is that openstack should only expose the openstack API, but have external projects that provide translation to the openstack api20:17
ttxor is it more complex than that ?20:17
vishyttx: that is one of the quesions20:18
bcwaldonanotherjesse: not necessarily tranlation to the OpenStack API, but even able to plug into the compute API (nova/compute/api.py)20:18
vishywe have stated in the past that openstack is about the apis, not the implementation20:18
anotherjessebcwaldon: no, I was saying one proposal is that we don't do that, we just have http proxies20:18
mtaylorttx: I think the first question is "should openstack have a policy on this at all" ... then "should it be global or per project" ... then, if global "what should the policy be"20:18
vishyif so does that mean that core openstack should only include the openstack api20:18
anotherjessebcwaldon: another is that it is a 3rd party plugin20:18
bcwaldonanotherjesse: ok, loud 'n clear20:18
anotherjesseanother is that we have a contrib folder with alternative APIs20:18
*** heckj_ has joined #openstack-meeting20:19
anotherjessettx: I think the issue is that multiple groups care about different apis but using openstack implementation - so it would be good for them to know how we want them to interact with us20:19
devcamcar_contrib implies python only?20:19
vishyalso, if we decide that apis are external, is there a process by which they can become part of core20:19
mtaylorvishy: ++20:19
bcwaldonvishy: would becoming core mean OpenStack has full control over that contract?20:19
vishyor do we just say, not our problem, talk to the distributions20:19
bcwaldonvishy: thinking about EC2 here...20:19
anotherjessemtaylor / vishy - what advantage would having a way of becoming core ?20:20
vishybcwaldon: no, i mean, included in the core tarballs with the release20:20
bcwaldonok20:20
*** heckj has quit IRC20:20
*** heckj_ is now known as heckj20:20
anotherjesseI personally lean towards making openstack have one api that others proxy against20:20
vishybcwaldon: no advantage for us, lots of advantage for the 3rd parties :)20:20
notmynamedevcamcar_: not really. contrib could simply be a list of compatible plugins manages separately20:20
* mtaylor leans towards anotherjesse20:20
vishyer anotherjesse: ^^20:20
anotherjessekeeps the surface area of the project smaller from a security and complexity point of view20:20
* bcwaldon leans towards mtaylor20:20
bcwaldonthe proxy approach is the easiest for us, but we'd have to bite the bullet performance-wise20:21
anotherjessevishy: what is the advantage?  that we are now in charge of keeping it up-to-date and working?20:21
mtayloralso means external api proxies are themselves easier to verify in isolation20:21
anotherjesseit also has the disadvantage of coupling release20:21
vishyanotherjesse: the advantage for them is that they gain visibility20:21
*** troytoman-away is now known as troytoman20:22
devcamcar_anotherjesse: did that just become a proposal to remove ec2 API?20:22
*** ryanpetrello has quit IRC20:22
*** ryanpetrello has joined #openstack-meeting20:22
vishydevcamcar_: unfortunately that is not so easy20:22
devcamcar_I know20:22
vishydevcamcar_: after rpc versioning it is possible, but we still have to figure out what to do with the mapping tables.20:22
anotherjessedevcamcar_: long term yes - it would require a project to exist and the APIs to fully expose the required features20:22
anotherjessebut that would be good to do ;)20:22
mtaylor++20:23
heckjdevcamcar_: while I'd prefer any *additional* APIs be external myself, I think asserting the removal of EC2 support would send a very poor message publicly20:23
jog0heckj: +120:23
mtaylorwell, if we talk about it in terms of elevating it to a core (separate) project rather than "removing it"20:23
devcamcar_I'm not proposing it20:23
ttxWe should treat EC2 as a historical corner case20:23
mtaylorit might could be shaped to not send the wrong message20:23
anotherjesseheckj: there is a group already working on a http-proxy based aws implementation -- if that got traction we might we able to "remove it"20:23
notmynameremoval of AWS APIs doesn't mean that it doesn't exist. it would be moved into an external proxy/plugin right?20:23
mtayloryeah. kind of like we're "removing nova-volume" right now20:24
ttxrather than having it influence the decision on how to treat additional ones20:24
cloudflythe phasing out of major components should have a formal process20:24
anotherjessettx: ++20:24
mtaylorttx: ++20:25
ttxbut yes, the decision we'll take will influence where EC2 might end up one day.20:25
heckjanotherjesse: sorry, I missed your original bits - lost connectivity for a bit. Do you have a discrete proposal that's in the logs?20:25
notmynamecloudfly: not really. the way swift has done it in the past is to provide the pieces in another location20:25
ttxs/EC2/EC2 APi support/20:25
notmynames/EC2/AWS/20:25
anotherjesseheckj: I was saying I propose 3rd party APIs be done as http proxies20:25
heckjanotherjesse: thanks20:25
ttxi don't have strong feelings either way. I'd lean towards considering 3rd party APIs as optional  add-ons20:26
ttxbe them magic plug-ins that plug into the internal compute API... or proxies20:26
anotherjessettx: I'm not against that, it requires us to stabilize a plugin api - which we haven't done20:26
devcamcar_anotherjesse: +120:26
vishyis there any way that we can provide a process for a 3rd party api to be shipped as "part" of openstack?20:26
ttxthe second option sounding a lot more doable in the short term20:26
heckjanotherjesse: +120:26
vishydoes it mean applying for incubation?20:26
anotherjessevishy: no20:26
devcamcar_vishy: could also20:26
anotherjesseincubation is a path to core20:26
vishyi know20:27
devcamcar_make it an upstream problem?20:27
vishyso we are saying that no other api could ever be in core?20:27
heckjvishy: I think we're asserting an API can become part of core if it applies for and gains acceptance through the incubation process.20:27
devcamcar_if not core then upstream packaging issue, if core then it's included20:27
anotherjessevishy: requirements change, but under the current situation I think that would be ideal20:27
ttxWe should have official projects developed within openstack that are not part of the core product.20:27
heckjdevcamcar_: I think you mean downstream, yes? (i.e. ubuntu, fedora, etc)20:28
mtaylorttx: ++20:28
devcamcar_heckj: yes20:28
mtaylorttx: we should propose a formal definition of that at some point20:28
ttxso that we can extend our ecosystem of projects without diluting the values of our core product20:28
ttxmtaylor: rather soon than late, I think20:28
vishyttx: what does an official project mean in that case?20:28
anotherjesseif you belive that most systems will be cloud enabled, and we hope that openstack is a major part of that, then the surface area of a complete cloud solution is huge20:28
anotherjessewe shouldn't try to own everything20:29
anotherjessewe should focus on being a great "kernel" for the cloud20:29
ttxvishy: developed withing our infrastructure ?20:29
heckjanotherjesse: +120:29
mtayloranotherjesse: ++20:29
anotherjessetrying to own every layer and impose our processes on it will limit inovation20:29
notmynameanotherjesse: +120:29
mtaylorwe already use many non-us components too ... mysql, rabbit, etc20:29
anotherjessehaving resources available (like mtaylor's stackforge) that help developers / projects out is great20:29
vishyttx: ok I'm not sure what the benefit is though.  Why would a third party project go through the overhead of being 'official'? What do they get out of it?20:29
ttxvishy: some amount of openstack branding ?20:30
ttxif you have openstack core, openstack official and ecosystem...20:30
ttxFor example, as of today, openstack-common is an official project.20:30
anotherjesseowning the ecosystem could limit the ecosystem20:30
ttxit's not core. It's like... used to build core20:31
notmynameanotherjesse: s/could/would/20:31
ttxbut it's still very much officially openstack20:31
devcamcar_core^220:31
vishyttx: ok, so the current proposal is third party apis are not allowed in core, they are welcome in the ecosystem, and at some point there will be a process to become official?20:31
anotherjessesupporting external projects that live outside openstaack but work with openstack would be my proferrence.20:31
anotherjessethat might mean test suites, api work, ...20:31
devcamcar_vishy: we better plan how to plan for that process though20:31
devcamcar_otherwise we are just deferring the issue20:32
anotherjessebecause in the end the people selling / distributing openstack will go through and make decsisions about what their users get (what is possible / what is default)20:32
ttxvishy: they should be developed as a plug-in or a proxy, so that they can be either a separate plug-in, an official plug-in (tested with core), or a core plugin (shipped with core)20:32
vishydevcamcar_: i think we should also mandate an effort by the core projects to make 3rd party apis as easy as possible.20:32
anotherjessevishy: again - I don't see advantages to making them core20:32
ttxvishy: +120:33
vishyanotherjesse: there is no core in the above proposal20:33
*** heckj has quit IRC20:33
notmynamean API "becoming official" would be up to the PTLs. look at how the project is being used and make the best choice for the project (?)20:33
anotherjessevishy: sorry, I meant making them official20:33
*** heckj has joined #openstack-meeting20:33
vishyanotherjesse: there is no advantage for us, but it is good for the ecosystem20:33
*** joesavak has joined #openstack-meeting20:33
heckjdamn, bad network day for me20:33
ttxanotherjesse: if they don't see an advantage, they will stay non-official20:33
ttxFor example, I wouldn't gate on something non-official20:34
anotherjessettx: what advantage for openstack20:34
ttxso Tempest will be an official project (not core=20:34
ttx)20:34
anotherjessenot that I don't think they should exist20:34
anotherjesseerr, not that I think they shouldn't exist20:34
ttxanotherjesse: gives us some amount of control.20:34
anotherjessettx: we don't want it.  owning our official APIs are enough work20:34
anotherjesseand being a cloud platform - instead of a cloud product - means we need to give control to people to write stuff on top of openstack20:35
mtayloryeah - and other people, such as canonical, who have vested interests in other apis can own those for their purposes20:35
ttxanotherjesse: think devstack being used as a gate mechanism. Making it official forces devstack to play by our rules... and lets us influence it so that we can keep using it as a gate20:35
vishyanotherjesse, ttx: perhaps that is exactly the definitition of official.  We feel it is an important enough use case to do some gating on it20:35
mtaylorvishy: ++20:35
heckjvishy: I can stand by that definition of official20:35
anotherjessettx: and if devstack guys didn't want to play by those rules DVCS has easy ways of *OPENSTACK* adding process without limiting the external project20:35
ttxI hate gating on something we don't control.20:36
ttxanotherjesse: sure.20:36
mtaylordvcs solves all the worlds problems...20:36
*** jsavak has quit IRC20:36
vishyanotherjesse: but that is just adding a dependency20:36
ttxPersonally I see our copre infrastructure as an official project too. Though we don'ty formally gate on it... it's THE GATE.20:37
anotherjessevishy: exactly20:37
ttxcore*20:37
vishyanotherjesse: which is different from actively working on the code20:37
vishyanotherjesse: and keeping it up to date20:37
anotherjesseopenstack will want to expose a stable interface to build things upon20:37
anotherjesseif we break upstream projects like a http proxy api - then will probably are breaking LOTS of other people building custom integrations20:37
anotherjessebut that doesn't mean we have to mark something as official20:38
anotherjesseI want to know if we are breaking for users or use-cases20:38
anotherjessebut that doesn't imply that those users/use-cases code needs to be official20:38
anotherjessewe are an API20:38
anotherjessewe need to support the users of the API regardless of "official"-ness20:38
mtaylorbut we can support them by testing the api... we don't have to test all of the users of the api, yeah?20:39
anotherjesseand if we start blessing the high level projects on top of openstack we will end up being even more bureaucratic20:39
vishyanotherjesse: from a community perspective I think there is a lot of perceived value to having some kind of official openstack support.20:39
anotherjessemtaylor: exactly - that is what we can focus on to help these guys20:39
vishyanotherjesse: i don't know how you can avoid it. So either we do it via technical requirements or we punt let marketing people decide what to do with it20:40
anotherjessevishy: I'm saying you are looking at it backwards20:40
mtaylormemcached has a great tool called memcapable that you can run against your api thing to ensure that your non-memcached implementation works20:40
ttxvishy: yes, maybe "official" is not the best term to describe that state.20:40
anotherjessewe should have APIs that 3rd parties can say they work with and have tests suites that show that they have integration20:40
sorenmtaylor: A memcached that just doesn't cache anything?20:41
mtaylorif we're testing the api with something, and we can hand that something to people consuming the api that they can use to verify their side of things, then we're taking care of those consumers, right?20:41
mtaylorsoren: yup20:41
ttxanotherjesse: so you would prefer 3rd party APIs being completely separate ?20:41
sorenmtaylor: I'm not sure what the equivalent would be here?20:41
vishyanotherjesse: that still makes no sense, they run the test suite themselves and tell us it works20:41
anotherjessevishy: yes20:41
vishyanotherjesse: and we say, awesome, use our logo?20:41
anotherjessevishy: we say "here are the branding guidelines" - if you are compatable with openstack 2.0 api, then you say that20:42
vishyanotherjesse: that still fits perfectly in what i was proposing, just that we have some way to specify officialness20:42
anotherjessejust like software boxes show mac  / windows logos on the side of the box ...20:43
ttxvishy: did you raise the thread on this on the ML ? I haven't seen it, but I'm a bit behind on ML processing20:43
vishywe can say: must pass these tests20:43
vishyttx: no i did not20:43
anotherjessevishy: we can say that "this logo means you pass the tests" - but we don't run the tests20:43
anotherjessethey do20:43
vishyanotherjesse: that's fine20:43
anotherjesseand if they lie then users will be pissed - at both parties probably20:43
anotherjesse;)20:44
vishyanotherjesse: that is a hard sales pitch when the tests don't even exist though20:44
vishyanotherjesse: who's going to write them?20:44
mtaylorwon't tempest wind up being an API compat test?20:44
ttxvishy: I think some emails would go a long way to crystalize the different options before we can confront them20:44
mtaylorif it's testing everything black box via the APIs?20:44
ttxvishy: we seem to still struggle with the breadth of the topic :)20:45
vishymtaylor: that doesn't give 3rd party apis or plugins any pth forward.20:45
mtaylorvishy: hrm. k. fair20:45
devcamcar_mtaylor: I don't think that's a stated goal of tempest20:45
anotherjessevishy: if we don't write them (as in all of openstack) then how is integrating them directly into the project any better20:45
anotherjessewe end up with a larger project with more brittle integrations20:45
vishyanotherjesse: I don't want to integrate them into the project20:46
anotherjessevishy: I don't want to be the gatekeeper of the labeling of "works with openstack"20:46
vishyanotherjesse: I want to be able to tell the authors of these that there is a specific process by which they can become "part of openstack".20:46
anotherjesseI want people to compete for adoption rather than wanting to be blessed20:46
vishybecause otherwise there is too much perceived value in core20:47
vishyand so they will keep pushing to be in core20:47
ttxvishy: +120:47
*** mattray has joined #openstack-meeting20:47
ttxPart of the "official" concept is to distract people from bwatning "core or nothing"20:47
ttxwanting*20:47
*** heckj_ has joined #openstack-meeting20:47
anotherjessevishy: my point is being part of openstack needs to be bigger than just being in core …  I can be part of linux by writing a software project that distros include20:47
anotherjesseI don't have to get the kernel's blessing to write a game for linux20:48
anotherjesseor for distros to include it20:48
*** heckj has quit IRC20:48
*** heckj_ is now known as heckj20:48
*** rkukura has joined #openstack-meeting20:48
vishyanotherjesse: I understand your point, but they don't20:48
ttxanotherjesse: in that case we are talking external APIs. Which is like proposing a new executable format for the kernel.20:48
anotherjessevishy: k - so if we agree that we should be going for an ecosystem that is market driven, then lets work towards enabling that20:48
ttxanotherjesse: not like adding a new game.20:49
anotherjessettx: not true, since it is a compatability layer.  for performance reasons you might want to be in the kernel but there is no reason to not implement it in userland20:49
*** joesavak has quit IRC20:49
sorenanotherjesse: It may or may not be a compatibility layer.20:49
sorenanotherjesse: That's the point, isn't it?20:50
ttxsoren: +120:50
vishyanotherjesse: you can do a new filesystem in userland as well20:50
sorenanotherjesse: It's not necessarily just a proxy. Just like the EC2 API implementation in Nova now.20:50
vishyanotherjesse: but there are valid reasons for proposing it into the kernel20:50
anotherjessesoren: we are proposing that the way it is in  nova right now is wrong20:50
anotherjessethat you can do it that way but we aren't mature enough to do both http API and internal api with stability of interfaces20:51
devcamcar_that ec2 API needs to be a proxy to openstack API20:51
devcamcar_correct?20:51
vishydevcamcar_: undetermined20:51
devcamcar_what tests do you have to pass?20:51
vishydevcamcar_: either a proxy or communicating through defined rpc api20:51
ttxagain, EC2 is a historical corner case, let's not turn this into a EC2 API question20:52
vishyttx: I don't know if we can consider it that while it still in the code base20:52
ttxthe question is: what do we do for the "other" cloud standard APIs20:52
sorenanotherjesse: I know that's what being discussed, but the point remains that it doesn't have to be the proxy model. Not eveyone thinks the proxy model is super awesome.20:52
devcamcar_ttx: yep, not trying to, but it's best example we have atm20:52
sorenanotherjesse: Present company included.20:52
sorenttx: Do you think we might keep the EC2 API beucase it's been grandfathered in, but have other policies for new API's that come along?20:53
ttxsoren: the alternative is a clean/versioned internal API coupled with a plug-in system, I think20:53
anotherjessesoren: we could go with the linux codebase model where everything is in core - including 3rd party stuff20:53
devcamcar_soren: my question is how do you measure compatibility for a non proxy api?20:53
anotherjessesoren: but our gerrit process makes it cumbersome already20:53
sorendevcamcar_: Compatiblity with what? (and why do I care?)20:54
anotherjessesoren: for instance in the volume code we have drivers that 3rd parties maintain - and we basically have to blind accept them as they come through20:54
ttxsoren: yes20:54
mtayloranotherjesse: for sake of argument, that can be fixed (and remind me to chat with you about some ideas we had)20:54
sorenttx: Ok.20:54
ttxsoren: but the decision we take here would definitely influence where the EC2 API could go in the future.20:55
devcamcar_soren: exactly my point. what are we even trying to measure here?20:55
sorenanotherjesse: I'm not sure where you're going?20:55
sorendevcamcar_: Are we trying to measure something?20:55
soren:)20:55
anotherjessesoren: if there are snippets of code which could live on their own, they should20:55
anotherjessesince our process sucks for those20:55
sorenWe could make the OpenStack API external, too.20:55
*** heckj_ has joined #openstack-meeting20:55
anotherjessesoren: that was our original proposal a year ago but we lost that battle20:56
heckj_I'm having the worst damn day with networking20:56
devcamcar_we have 4 mins20:56
devcamcar_anything we can vote on thats tangible? :)20:56
heckj_[tempchair]: we have 4 minutes left. I propose that we synthesize this conversation, post on the mailing list, and discuss further there. Then reconvene next week here to formally decide20:56
anotherjessedevcamcar_: no20:56
*** gabrielhurley has joined #openstack-meeting20:56
ttxheckj: you should endmeeting as soon as you recover "heckj"20:56
anotherjessewe should enable optional components to thrive with their own coding process, release process and marketing demand process …  or figure out how to fix our processes to work with those20:57
anotherjesseright now our processes don't work well for subgroups20:57
mtayloranotherjesse: or both20:57
*** heckj_ has left #openstack-meeting20:57
*** heckj_ has joined #openstack-meeting20:57
heckj_.20:57
*** heckj_ has quit IRC20:57
anotherjesseand adding more "blessings" where people either land-rush or agreements with project seems less than ideal20:57
anotherjessewhich is what the process has been so far20:58
*** heckj has quit IRC20:58
*** heckj_ has joined #openstack-meeting20:58
ttxheckj: you should endmeeting20:58
sorenheckj_: "heckj" just left. You can /nick heckj20:58
ttxwhile you can20:58
*** heckj_ is now known as heckj20:58
heckjfinally!20:58
sorenOh, look! It's heckj !20:58
heckj#endmeeting20:58
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"20:58
sorenHi, heckj!20:58
openstackMeeting ended Tue May  1 20:58:45 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:58
vishyanotherjesse: i think plugins vs separate projects need to be considered separately20:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-01-20.14.html20:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-01-20.14.txt20:58
*** jerdfelt has joined #openstack-meeting20:58
heckjbefore the freakin' wifi dies again20:58
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-01-20.14.log.html20:58
ttxyay20:58
heckjmtaylor: WOOT! It worked ^^20:59
vishyanotherjesse: for example api extensions20:59
anotherjessevishy: which suck right now20:59
sorenheckj: It'll pass. </pessimism>20:59
anotherjessevishy: people think that extensions imply official approval20:59
vishyanotherjesse: no argument here, but there needs to be a way for plugins/extensions to become official20:59
vishyexternal projects like LBaaS etc. I agree should not be officialized21:00
ttxvishy: so you start a thread on this ? Hopefully that wil let us advance the discussion enough to come to decision next meeting21:00
vishyok21:00
anotherjesseor don't define official - let openstack define "compatbile" and let the market define "desirable"21:00
*** davlaps has joined #openstack-meeting21:00
notmynameanotherjesse: +121:00
ttxanotherjesse: we'll need "official" for things like openstack-common21:00
heckjttx: sounds like you have a proposal to write on what it means to be official21:01
ttxwhich are not core but are very much openstack21:01
vishyttx: i think that is a separate discussion as well21:01
* mtaylor too21:01
mtaylorhrm. that was vague of me21:01
ttxyes, I need to work on that21:01
anotherjesseheh21:01
*** SumitNaiksatam has joined #openstack-meeting21:01
vishya 3rd party api is not really equivalent to devstack or tempest or openstack-ci21:01
devcamcar_haw21:01
mtaylorvishy: ++21:01
ttxbcwaldon, danwent; still around ?21:01
danwentyup21:01
bcwaldonmaaaaaybe21:01
ttx#startmeeting21:02
openstackMeeting started Tue May  1 21:02:03 2012 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:02
ttxWelcome everyone to our weekly Project/release meeting21:02
ttxToday's agenda: http://wiki.openstack.org/Meetings/ProjectMeeting21:02
ttxShould be a quick one. We'll have a look at the current state of the Folsom plans.21:02
*** dolphm has joined #openstack-meeting21:02
ttx#topic Keystone status21:02
*** openstack changes topic to "Keystone status"21:02
ttxLet's start with heckj while the wifi works21:02
ttxmaybe21:03
heckjKeystone meeting this morning nailed down most of the blueprints21:03
ttx#link https://blueprints.launchpad.net/keystone/folsom21:03
heckjWe have a few undeteremined for who's going to do them, but most are assigned out at this point21:03
ttxservice-endpoint-location is marked "obsolete", should we unset the series goal ?21:03
ttxor is it still very much a goal ?21:03
heckjunset - I'll get it21:03
ttxAlso I don't really get what draft-v3-blueprint is about. A blueprint about drafting a blueprint ?21:04
heckjit's for drafting the next rev API21:04
*** ewindisch has quit IRC21:04
heckjjust typoed the name21:04
vishyheckj: you can change it21:04
dolphmdraft-v3-api?21:04
ttxheckj: so this will be a non-code blueprint, right ?21:05
dolphmvishy: the url is a permalink though, i think21:05
heckjvishy: would love to - haven't figured out how21:05
vishydolphm: nope just fixed it for you21:05
heckjthe text in the blueprint is correct21:05
dolphmhttps://blueprints.launchpad.net/keystone/+spec/draft-v3-api21:05
dolphmmagic!21:05
ttxawesome21:05
heckjthank you!21:05
devcamcar_ooo21:05
* cloudfly reads furiously21:06
vishyheckj, dolphm : ffr it is the 'Set the URL for this specification' link under the summary21:06
ttxheckj: so this will be a non-code blueprint, right ?21:06
* vishy knows way too much about blueprints :(21:06
heckjttx: correct. API document opened for feedback - much like what jaypipes/bcwaldon have done for Glance21:06
ttxheckj: ok21:06
ttxDo you expect more blueprints to be targeted to folsom-1, or is the map pretty much complete ?21:07
heckjfor F1, we're complete - I expect some churn and change in F2/F3 though21:07
heckjvery dependent on the V3 API core BP21:08
ttxsure, that's ok21:08
ttxheckj: anything else ?21:08
heckjnope21:08
ttxQuestions about Keystone ?21:08
ttx#topic Swift status21:08
*** openstack changes topic to "Swift status"21:08
ttxnotmyname: o/21:08
notmynameo/21:08
ttxnotmyname: Do you expect any major new feature in your next release ?21:08
notmynameyes. object versioning has been added since essex21:09
ttx(something that would warrant a blueprint ?)21:09
ttxnotmyname: could you create a blueprint retrospectively ?21:09
notmynameya, I can do that21:09
ttxShould the next Swift release be 1.4.10, 1.5...21:09
ttxOr do we need to discuss a bit more how we want to actually do it ?21:10
notmynameI think it will probably 1.521:10
ttx1.5.0 probably, then21:10
notmynamebut I don't have strong feeling either way21:10
ttxme neither... at least 1.5.0 makes the minor version number mean something (series mapping)21:11
ttxAny vague idea on the date, so that I start planning ?21:12
notmynameI'll add the blueprints for other things that have happened as well21:12
notmynameno, I don't have a date yet. I can work on that this week21:12
ttxdoesn't have to be a precise date. More like an indication :)21:13
ttxnotmyname: Anything else ?21:13
notmynamenope21:13
ttxQuestions on Swift ?21:13
ttxnotmyname: I'll create the 1.5.0 milestone so that you can target your blueprints against it21:13
notmynameok21:13
*** dprince has quit IRC21:14
ttx#topic Glance status21:14
*** openstack changes topic to "Glance status"21:14
ttxbcwaldon: yo21:14
bcwaldoneyyyy21:14
ttx#link https://blueprints.launchpad.net/glance/folsom21:14
bcwaldonyeah...21:14
bcwaldonI'm looking for feedback on a couple of emails I sent to the list, one about 'Glance Architecture' and one on 'Blueprints!'.21:14
ttxbcwaldon: glance-get-cmd is marked obsolete, should we unset the series goal for it ?21:14
bcwaldonif I marked it Obsolete, then yes21:14
ttxon it21:15
ttxyou should start targeting some of them to folsom-1 when they have someone signed up to do it21:15
bcwaldonYep, definitely will21:15
ttxWould separate-client be a folsom-1 target ?21:15
bcwaldonI've got a couple that are superblueprints that wont be targeted for a while21:15
bcwaldonttx: definitely21:16
bcwaldon(had to look up when f1 was)21:16
ttxok, please set the folsom-1 targets before the end of the week21:16
*** devcamcar_ has quit IRC21:16
bcwaldondon't you boss me around21:16
ttxso that we can start tracking progress towards the milestone21:16
bcwaldonbut I will21:16
ttxbcwaldon: "no target" is a valid answer :P21:17
bcwaldonSounds good. I'm looking for assignees for several of those blueprints21:17
bcwaldonSo if anybody has been poking me about how to help with Glance inFolsom, go read my email 'Blueprints!'21:17
ttxbcwaldon: Anything else you wanted to mention ?21:17
bcwaldonttx: nope, I'm trying to release my thoughts directly to the ML so I don't forget anything around meeting time21:18
bcwaldonso that's it for me :)21:18
ttxworks for me :)21:18
ttxQuestions on Glance ?21:18
ttx#topic Quantum status21:18
*** openstack changes topic to "Quantum status"21:18
ttxdanwent: hey21:18
danwenthttps://launchpad.net/quantum/+milestone/folsom-121:18
danwenthey21:19
ttxhttps://blueprints.launchpad.net/quantum/folsom is empty because you didn't set the series goal to Folsom on the blueprints21:19
ttxSetting the series goal lets you compile a list of "Folsom" blueprints which is generally more useful than the list of all blueprints, so I recommend doing it21:19
danwentah, sorry, i've just been targeting things to milestones21:19
danwentOk, will do that.21:19
ttxdanwent: not a big deal, gives you those nice "Folsom" views21:19
danwentso far, I've flushed out folsom-1 and folsom-2 milestones21:19
ttxfor some reason LP doesn't automatically build that21:19
danwentwhich is where we're targeting to get must of our "must haves" for Folsom release21:20
ttxI see 9 blueprints were targeted to folsom-1...21:20
ttx#link https://launchpad.net/quantum/+milestone/folsom-121:20
ttxYou probably should set them to "Approved" and prioritize all of them if you're OK with them.21:20
danwentyup, many of them are fairly small, but two are very large (new API work to merge melange, and authz work)21:20
danwentok, I was waiting on designs on some of them before approving.21:21
ttxI tend to check status on things that you set Essential/High21:21
danwentwill make sure that we get designs and approval for next week.21:21
ttxso lowering prio is a good way to get rid of me21:21
* oubiwann makes a note of that...21:21
danwentok, i expect only two high/essential blueprints left after this week.21:22
danwenttwo other ones will be done21:22
ttxoubiwann: priority is an indication of how important the blueprint is for release. So it's not totally a joke :)21:22
ttxdanwent: Anything else ?21:23
danwentnope21:23
ttxQuestions on Quantum ?21:23
ttx#topic Nova status21:23
*** openstack changes topic to "Nova status"21:23
ttxvishy: hey21:23
vishyhi21:23
ttx#link https://blueprints.launchpad.net/nova/folsom21:23
vishyso I've been doing massive blueprint triaging21:23
ttxLooks quite good. You're getting used to that game21:23
vishyhad 180 blueprints21:23
vishyi think i'm only about halfway done21:24
* oubiwann chokes21:24
vishy(actually 188)21:24
*** anderstj has joined #openstack-meeting21:24
vishyso I've targetted all the ones i am familiar with, but there are still a few that I have no idea about21:24
*** anderstj has quit IRC21:24
ttxoubiwann: vishy tries to beat me a blueprint-handling LP karma.21:24
ttxat*21:24
oubiwannhehehe21:24
*** anderstj has joined #openstack-meeting21:24
vishyttx: i'm considering declaring blueprint bankruptcy21:24
ttxYou should set the priority for all the undefined ones...21:25
ttxat least those who have a clear assignee that signed up to do the work21:25
vishybasically saying, if you own a blueprint and it isn't targetted for folsom, let me know because i'm going to delete all of the others in 2 weeks21:25
ttxec2-id-compatibilty is targeted to folsom-1 and has no assignee ?21:25
vishyttx: does that seem reasonable21:25
vishyttx: there are a bunch with no assignee21:25
*** johnpostlethwait has joined #openstack-meeting21:25
vishyttx: I din't man to target a milestone though21:26
vishy* mean21:26
ttxvishy: by "deleting" you mean obsoleting ?21:26
vishyttx: yes21:26
ttxvishy: oh, hellyes21:26
vishythere are just a whole bunch of random blueprints that are good ideas but have no one to work on them21:26
vishyand a bunch that are just old and I have no idea about21:27
vishyttx: I haven't prioritized the ones in there yet so a lot are still undefined21:27
*** Gordonz has quit IRC21:27
heckjvishy: burn them all to the ground and start again :-) Worked for me21:27
vishyttx: i was going to do a prioritization after I got them all targetted to folsom21:27
ttxvishy: sounds good. Try to prioritize the folsom-1 by next week21:27
vishyok i will do one more pass through all of them, then I will send out an email notifying about pending deletion21:28
ttxthe rest is not that urgent21:28
ttxvishy: Anything else ?21:28
vishynope21:29
* vishy sharpens his email pen21:29
cloudflyit's possible some of the existing side projects satisfy blue prints21:29
vishycloudfly: ?21:29
cloudflyadmin-cli vs unified-cli for instance21:29
vishycloudfly: possibly, I've been attempting to obsolete those21:30
vishycloudfly: if you notice any that you feel should be obsoleted, feel free to let me know21:30
vishycloudfly: I can use help21:30
cloudflywill do21:30
*** troytoman is now known as troytoman-away21:30
vishyactually that is true for anyone, if anyone notices blueprints that should be removed, let me know :)21:31
ttxOther questions on Nova ?21:31
*** atiwari has quit IRC21:31
*** littleidea_ has joined #openstack-meeting21:31
ttx#topic Horizon status21:31
*** openstack changes topic to "Horizon status"21:32
ttxdevcamcar: o/21:32
devcamcaro/21:32
ttx#link https://blueprints.launchpad.net/horizon/folsom21:32
ttxLooks good...21:32
devcamcarmost of whats there is only what we've targeted for folsom-121:32
ttxdevcamcar: there are two blueprints targeted to folsom-1 that don't have series goal = Folsom:21:32
devcamcarstill have a lot of blueprints to add from the summit which hopefully i can get to this week21:32
devcamcaroops, which?21:33
ttxhttps://blueprints.launchpad.net/horizon/+spec/scaffolding21:33
devcamcari'll fix21:33
ttxhttps://blueprints.launchpad.net/horizon/+spec/transition-to-lesscss21:33
ttxI was about to set them but thought you might want to confirm21:33
*** Haneef has quit IRC21:33
ttx(series targeting is limited to drivers, while milestone-targeting is open to everyone, so people may add stuff that you don't agree with21:33
devcamcarhm, they both say proposed for folsom21:34
devcamcaroh i see21:34
devcamcarnm21:34
devcamcarfixed :)21:34
ttxdevcamcar: soon you'll become a Jedi master21:34
devcamcarbut yes, F1 is looking good for us21:34
devcamcarttx: hah21:34
devcamcarF2 and on are mostly undefined right now21:34
devcamcari also have a list of tickets we'll be back porting to stable/essex21:35
gabrielhurleydevcamcar: maybe we won't be adding features until the last second this release ;-)21:35
*** pengyong has quit IRC21:35
devcamcarhttps://bugs.launchpad.net/horizon/+bugs?field.tag=essex-backport-potential21:35
*** littleidea has quit IRC21:35
*** littleidea_ is now known as littleidea21:35
devcamcarmostly trivial fixes21:35
ttxdevcamcar: you can use series targeting there too21:35
devcamcarok21:36
ttx"Target to series" and select "Essex"21:36
ttxthen it shows on https://bugs.launchpad.net/horizon/essex21:36
devcamcarahh perfect21:36
ttxand we can track completion21:36
devcamcari'll update those now as well21:36
* ttx still needs to fix the bugstatus-updating gerrit hook so that it understands the series, but otherwise it's pretty functional21:36
devcamcaryep, i had marked a few as fix released by mistake21:37
ttxfor some reason I thought that the weeks after the design summit would be pretty calm for me21:37
ttxdevcamcar: Anything else ?21:37
devcamcarttx: that is all!21:37
ttxQuestions for Horizon ?21:37
ttx#topic Other Team reports21:38
*** openstack changes topic to "Other Team reports"21:38
ttxannegentle, jaypipes, mtaylor: ?21:38
ttxOr any other team lead with a status report ?21:38
annegentleme!21:38
ttxhey, you made it :)21:38
annegentleWorking on a branch that switches all links to /essex for the docs.21:39
annegentleyup just!21:39
annegentleso I can release docs.openstack.org/essex today and open doc comments on all those pages21:39
annegentlealso going to eliminate the /bexar and /cactus "sites" by doing 301 redirects to /trunk21:39
ttxok21:39
annegentlethen I'll get cracking on a blueprint or two.21:40
ttxannegentle: we should open a "folsom" series for openstack-manuals21:40
ttxannegentle: so that you can target your blueprints to the series, at least21:41
annegentlethat would be great.21:41
ttxwilldo that for you21:41
annegentlealso you may have seen on the mailing list a post for an intern, needs to be a full time student and it is the Austin location of Rackspace. Approximately May to August.21:41
ttxsaw that. Great opportunity :)21:42
ttxannegentle: anything else ?21:42
annegentlealso the docs site now has all nova.conf flags listed at http://docs.openstack.org/trunk/openstack-compute/admin/content/compute-options-reference.html and another writer is working on a list of all swift flags21:42
annegentleand _that_ is all for this week.21:43
* oubiwann high-fives annegentle21:43
ttx#topic Open discussion21:43
*** openstack changes topic to "Open discussion"21:43
ttxAnything else, anyone ?21:43
jog0are we still planning on trying a shorter folsom release cycle?21:44
ttxI'll be at UDS in Oakland next week, maybe speaking21:44
ttxjog0: the release cycle will be 6 months21:45
jog0so folsom-1 will not have an associated 2 week code freeze?21:45
*** ryanpetrello has quit IRC21:45
ttxjog0: we /might/ consider late Folsom milestones as full releases, but it's pretty unlikely21:45
ttxno it won't21:45
jog0ttx: thanks21:46
ttxfolsom-1 will be cut on the Tuesday and delivered on the Thursday.21:46
ttxMay 22-2421:46
ttxok then, if nobody has anything, we'll close early21:47
ttx#endmeeting21:47
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"21:47
openstackMeeting ended Tue May  1 21:47:43 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-01-21.02.html21:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-01-21.02.txt21:47
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-01-21.02.log.html21:47
*** gabrielhurley has left #openstack-meeting21:47
ttxhave a good week!21:47
oubiwannttx: you too!21:48
*** jerdfelt has left #openstack-meeting21:48
*** oubiwann has quit IRC21:49
*** dendro-afk is now known as dendrobates21:51
*** salv-orlando has joined #openstack-meeting21:52
*** markmcclain has quit IRC21:52
salv-orlandoknock knock?22:00
termiewho's there?22:00
s0mikhey salv22:00
danwentnetstack's there!22:01
danwent#startmeeting22:01
openstackMeeting started Tue May  1 22:01:14 2012 UTC.  The chair is danwent. Information about MeetBot at http://wiki.debian.org/MeetBot.22:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:01
*** russellb has left #openstack-meeting22:01
danwent#link agenda: http://wiki.openstack.org/Network/Meetings22:01
GheRivero_hi people22:01
danwenthi GheRivero !22:01
rkukurahi22:01
danwentwelcome to the quantum scrum :)22:02
SumitNaiksatamHi All!22:02
danwentin terms of reviews outstanding, we have: https://review.openstack.org/#/q/status:open+project:openstack/quantum,n,z22:02
danwentand https://review.openstack.org/#/q/status:open+project:openstack/python-quantumclient,n,z22:02
garykhi guys22:02
danwentin particular, two reviews.  First22:03
danwentmnewby: https://review.openstack.org/#/c/6545/22:03
danwentand a similar patch on the client side: https://review.openstack.org/#/c/6549/22:03
danwentthese are very valuable style clean-up.22:03
danwentgiven how many pieces of the code it touches, I'd like to get these merged ASAP, otherwise we'll have a conflict mess22:03
danwentsalv-orlando: any chance you can reapprove the main patch (thanks for the review!)?22:04
danwentthe client side patch is smaller, and we need folks to take a crack at that as well.22:04
salv-orlandosure22:04
danwentthx… i don't think there have been any significant changes since you reviewed last22:04
danwentlater in the meeting we'll talk a bit more about enforcing style guidelines in reviews22:04
*** ayoung has quit IRC22:05
danwentother big review is from garyk : https://review.openstack.org/#/c/6744/22:05
danwentI think this is good to go, though there's an interesting question about introducing new mandatory fields in config files.  this will break any existing deploys, including devstack environments.22:05
garyki think that this should be considered for essex stable?22:05
danwentgaryk: I think that is reasonable.22:06
danwentbut in that case, I'd definitely want to have some default values for the new config params you suggested.22:06
garykwe could set a default value if the field is missing. it would ensure uptime22:06
danwentif we're going to backport, seems like a must for me.22:06
*** shwetaap has joined #openstack-meeting22:06
danwentany other opinions on this?22:06
garykdanwent: i agree.22:06
rkukuradefaults make sense to me22:07
GheRivero_agree22:07
danwentok, sounds good.22:07
salv-orlandogaryk proposal seems reasonable to me22:07
danwentonly other review is: https://review.openstack.org/#/c/6606/22:07
danwentmnewby: you here?22:07
garykgreat - i'll make the change22:07
GheRivero_since quantum is not core in essex,  garyk should be no problem to backport22:07
rkukuraany ordering issue between Gary's and Maru's patches?22:08
danwentrkukura: yes22:08
rkukuraGetting Gary's in 1st would make backport easier22:08
danwentI suspect there will be conflicts.  Given that mnewby's patch is huge, and garyk's needs to be resubmitted again for a change anyway, I would suggest we put garyk's on top22:08
danwenthaha :)22:08
danwentgood point, I hadn't thought about the backport22:09
salv-orlandorkukura: backport would consist of cherrypicking commit onto essex-stable, wouldn't it?22:09
salv-orlandorkukura: and hence agree with you :)22:09
rkukuraif they touch alot of the same code22:09
danwentsalv-orlando: yes, but mnewby's change won't be in essex-stable, so if garyk's change was based on it, that would be trickier22:09
salv-orlandoindeed. I thought about it while I was writing :)22:09
salv-orlandoand luckily I refrained just in time from approving Maru's patch.22:10
danwent:)22:10
salv-orlandoSo just a +2 for now. The approve will come after Gary's patch goes in.22:10
danwentok, yeah, let's have garyk's patch go in first.22:10
danwentsalv-orlando and I can quickly re-approve a rebased version of mnewby's changeset22:10
salv-orlandocool22:11
mnewbyI'll likely have to do more than a rebase, but that's fine.22:11
danwentmnewby: thx22:11
rkukuramnewby: I thought you already got garyk to perfect his style:-S22:12
danwent#todo danwent talk to aaron lee about responding to review: https://review.openstack.org/#/c/6606/22:12
salv-orlandorkukura: that's a good idea actually22:12
danwentok, that should be good for reviews22:12
danwentNext up, talking about Folsom-122:12
mnewbyrkukura: Hard to be pedantic about style if the rest of the code doesn't match up.22:12
jkoelkeraarron is no longer working on openstack fulltime22:13
jkoelkerjust fyi22:13
jkoelkerso if someone wants to take that patch and update it would be best22:13
danwentjkoelker: good to know.  so should we assume that this patch is abandoned?22:13
danwentok.22:13
danwentlooks worth saving, anyone want to volunteer?22:13
GheRivero_me?22:14
danwentmight suck to rebase after mnewby's chang-set though :)22:14
danwentGheRivero: sold!22:14
*** dolphm has quit IRC22:14
GheRivero_cool22:14
danwentGheRivero: thanks.22:14
danwentOk, now on to F-1.  Three weeks away from release already.22:15
danwenthttps://launchpad.net/quantum/+milestone/folsom-122:15
danwentI took most issues from the summit and assigned them to F-1 or F-2 if I felt like I understood them and who was working on them.22:15
danwentfeel free to fill in gaps.22:15
danwentThe biggest thing we need to focus on in F-1 is getting the Melange stuff merged in.  A bunch of other stuff depends on that.22:16
danwentjkoelker: anything to add as the driver for that issue?22:16
jkoelkerwe're working on figuring it out as we speak22:16
jkoelkeri'll update the blueprint as soon as the arm wrestling is over22:17
jkoelkerto determine how wer're going to attack it22:17
danwentOk, would be good to have something widely visible by next week.22:17
rkukura+122:17
danwentthere may be layers of arm-wrestling :)22:17
jkoelkeryea we want to have a plan of action by tomorrow22:17
danwentok, and any idea who from troy's team is driving the authn/authz stuff?  I pinged him, but haven't heard back.22:18
tr3buchet\(o.o)/22:19
_cerberus_We're going to get together in the morning to get everything worked out, and hopefully come out of it with a plan for the API et al22:19
danwenti know heckj was interested in helping as well22:19
_cerberus_danwent: re: auth, looking at Kevin Mitchell for that22:19
_cerberus_troy and I need to chat a bit more about it, but that's the plan22:19
danwent_cerberus_: ok, thanks for the info.  Those are the top two priority issues I'm tracking for F-1… so you'll definitely get sick of me bugging you for updates :)22:19
heckjo/ willing to help22:19
danwentok, thanks heckj !22:20
salv-orlandoI can offer my help on authn/authz but cannot be full-time at the moment.22:21
salv-orlandojust consider me probably for menial tasks :)22:21
danwentsalv-orlando: that would be great, especially since you did a lot of the initial authn work for quantum.22:21
tr3buchetsalv-orlando: we'll point kevin at you!22:21
danwentIn other F-1 news, I'm working on getting multi-node quantum devstack up.  Should be able to propose end of day today, as in my testing, everything seems to work.22:22
danwentMost of the rest of the F-1 tasks are around the open source agents, fixing issues or laying the groundwork for improvements that will be coming in F-222:22
danwentoops, except I missed security groups.  davlaps is working on that.22:23
*** ywu has joined #openstack-meeting22:23
davlapsyup :)22:23
danwentSo feel free to target additional things at F-122:23
danwentbut remember that it is 3 weeks out :)22:23
danwenthttps://launchpad.net/quantum/+milestone/folsom-222:23
danwenta couple items here are probably big enough that we need to be working on them during the F-1 timeframe.  particular the nova paraity work for DHCP (carlp) and (L3 forwarding + NAT).  Both are needed so we can remove nova-network (tr3buchet)22:24
danwentI also have items slotted for reworking the client lib + doing the horizon integration.22:25
danwentour goal from the summit is the have all of the "base" items needed to make the argument for quantum being the default done by F-222:25
tr3buchetdanwent: i plan on doing some work with the nova network quantum api as well soon22:25
danwentrkukura: are you going to make a BP for "provider networks"?22:25
rkukuraI did today22:25
rkukuraAlso did one on scalable agent comms22:26
danwenttr3buchet: great.  I know you've done a lot of that work already, but I figured to put it in F-2 as it would have to wait until the merged API is finalized.22:26
tr3buchetdanwent: that's fine, i'm working closely with koelker enough to keep it up to date anyway22:26
danwentrkukura: great.  can you target them for the folsom release and a particular milestone?22:26
danwentand set me as the approver.22:26
rkukuraOK22:27
danwenttr3buchet: ok, great22:27
*** gyee has quit IRC22:27
danwentis carlp missing again?22:27
*** edygarcia has quit IRC22:27
danwenthe's always leaving me hanging :P22:27
danwent#todo: get carlp to send an update on dhcp plans22:28
danwentOk, anything else to discuss on F-1 or F-2 before moving on to some community questions?22:28
danwentOk, first topic is "enforcing style guidelines"22:28
danwent#info mnewby's patch highlights that we're being a bit lax on enforcing pep-8 style guidelines (http://www.python.org/dev/peps/pep-0008/)22:29
danwentthe automated pep8 checker doesn't warn about a handful of things that are still good style to follow.22:30
danwenti'd encourage all core devs to take a look at the patch and see what things were missed.  we may even compile a "commonly missed style issues" writeup.22:30
danwentbut now that we're core, we need to get better at enforcing this.22:30
danwentgoing through the review, I even realized a few things about our style guidelines that I didn't know :)22:31
danwentany questions/comments?22:31
danwentOk, next topic is about tempest integration with Quantum.22:31
danwentA recent review was proposed to add quantum tests for tempest: https://review.openstack.org/#/c/4896/322:31
danwentWe're looking for someone to help take a lead on this.22:32
*** onfun has joined #openstack-meeting22:32
danwentmnewby and I will continue to drive work on this review, but hopefuly someone else will step up as well.22:33
danwentNew topic:  commit gating22:33
mnewbyI'm going to work with Darryl to explore generative testing.22:33
mnewbyThis will tie into client improvements, too.22:33
tr3buchetgenerative testing?22:34
mnewbyMy pet name for functional tests driven by machine-readable api specification.22:34
mnewbyIt's probably in error - data-driven is more accurate.22:34
tr3buchetsounds like magic!22:35
*** mugu has joined #openstack-meeting22:35
danwentmnewby: that would be really cool.22:35
danwenttr3buchet: but if its magic that makes our software better, that's great!22:35
danwentback to the topic of gating22:36
mnewbyIt should allow automation of the mechanical types of testing.  More exploratory testing will still be required, but hopefully we'll have more effort to apply towards it.22:36
tr3buchetಠ_ಠ22:36
danwenti'm going to reach out to mtaylor and jeblair to get quantum and python-quantumclient gating on unit tests, then gating on excercise.sh tests22:36
danwentif anyone feels passionately about this and wants to help drive, let me kno22:37
danwentw22:37
danwentok, open discussion22:37
danwentany other topics?22:37
shwetaapdanwent: Going back to reviews .. Could you and davlaps review https://review.openstack.org/#/c/6246/ - its regarding Linuxbridge plugin iinstall support using devstack. Dean Troyer wanted a few others to approve it since he could not test it on his end. Its been there for a while. I will re-open it.22:38
davlapsno problem.22:38
shwetaapThanks Dave!22:39
danwentshwetaap: sure.22:39
danwentok, last call?22:39
shwetaapcool thanks22:39
*** kpepple_ has joined #openstack-meeting22:41
*** mattray has quit IRC22:46
*** martines has quit IRC22:50
*** notmyname has quit IRC22:50
*** cloudfly has quit IRC22:50
*** _cerberus_ has quit IRC22:50
*** mugu has quit IRC22:50
*** openstack has joined #openstack-meeting22:55
*** ChanServ sets mode: +o openstack22:58
*** deshantm has joined #openstack-meeting22:59
*** kiffer84 has joined #openstack-meeting23:00
*** glenc has joined #openstack-meeting23:00
*** ryanpetrello has joined #openstack-meeting23:00
*** sleepson- has joined #openstack-meeting23:00
*** chmouel_ has joined #openstack-meeting23:00
*** chuck_ has joined #openstack-meeting23:00
*** anderstj has joined #openstack-meeting23:00
*** shwetaap has joined #openstack-meeting23:00
*** littleidea has joined #openstack-meeting23:00
*** rkukura has joined #openstack-meeting23:00
*** danwent has joined #openstack-meeting23:00
*** justinsb has joined #openstack-meeting23:00
*** lloydde_ has joined #openstack-meeting23:00
*** reed has joined #openstack-meeting23:00
*** sandywalsh has joined #openstack-meeting23:00
*** novas0x2a|laptop has joined #openstack-meeting23:00
*** jdurgin has joined #openstack-meeting23:00
*** mnewby has joined #openstack-meeting23:00
*** garyk has joined #openstack-meeting23:00
*** jgriffith has joined #openstack-meeting23:00
*** Amw3000 has joined #openstack-meeting23:00
*** blamar has joined #openstack-meeting23:00
*** jacky has joined #openstack-meeting23:00
*** jaypipes-afk has joined #openstack-meeting23:00
*** Adri2000 has joined #openstack-meeting23:00
*** jog0 has joined #openstack-meeting23:00
*** jakedahn has joined #openstack-meeting23:00
*** cp16net has joined #openstack-meeting23:00
*** zykes-_ has joined #openstack-meeting23:00
*** jkoelker has joined #openstack-meeting23:00
*** Daviey has joined #openstack-meeting23:00
*** fattarsi has joined #openstack-meeting23:00
*** nikhil__ has joined #openstack-meeting23:00
*** mikal has joined #openstack-meeting23:00
*** clarkb has joined #openstack-meeting23:00
*** sdague has joined #openstack-meeting23:00
*** med_ has joined #openstack-meeting23:00
*** xtoddx has joined #openstack-meeting23:00
*** _0x44 has joined #openstack-meeting23:00
*** anticw has joined #openstack-meeting23:00
*** sleepsonzzz has joined #openstack-meeting23:00
*** yamahata_ has joined #openstack-meeting23:00
*** comstud has joined #openstack-meeting23:00
*** Madkiss has joined #openstack-meeting23:00
*** edleafe has joined #openstack-meeting23:00
*** jamespage has joined #openstack-meeting23:00
*** termie has joined #openstack-meeting23:00
*** LinuxJedi has joined #openstack-meeting23:00
*** tr3buchet has joined #openstack-meeting23:00
*** pknouff has joined #openstack-meeting23:00
*** ttrifonov has joined #openstack-meeting23:00
*** troytoman-away has joined #openstack-meeting23:00
*** Kiall has joined #openstack-meeting23:00
*** carlp has joined #openstack-meeting23:00
*** no`x has joined #openstack-meeting23:00
*** hazmat has joined #openstack-meeting23:00
*** anotherjesse has joined #openstack-meeting23:00
*** jkoelker has quit IRC23:01
*** s0mik has joined #openstack-meeting23:01
*** GheRivero has joined #openstack-meeting23:01
*** DuncanT has joined #openstack-meeting23:01
*** dendrobates has joined #openstack-meeting23:01
*** ohnoimdead has joined #openstack-meeting23:01
*** dtroyer_zzz has joined #openstack-meeting23:01
*** mtaylor has joined #openstack-meeting23:01
*** kiffer84 is now known as Guest3419623:01
*** mugu has joined #openstack-meeting23:01
*** martines has joined #openstack-meeting23:01
*** notmyname has joined #openstack-meeting23:01
*** cloudfly has joined #openstack-meeting23:01
*** _cerberus_ has joined #openstack-meeting23:01
*** phantomcircuit has joined #openstack-meeting23:01
*** annegentle has joined #openstack-meeting23:01
*** antonym has joined #openstack-meeting23:01
*** dragondm has joined #openstack-meeting23:01
*** jbarratt has joined #openstack-meeting23:01
*** cburgess has joined #openstack-meeting23:01
*** phantomcircuit has quit IRC23:02
*** jkoelker has joined #openstack-meeting23:02
*** blamar has quit IRC23:04
danwent#endmeeting23:06
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"23:06
openstackMeeting ended Tue May  1 23:06:08 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:06
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-01-22.01.html23:06
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-01-22.01.txt23:06
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-01-22.01.log.html23:06
clarkbo_O so it decided to eventually be happy?23:08
*** littleidea has quit IRC23:08
s0mikapparently took a couple of tries but that made MeetBot happy23:11
*** davlaps has quit IRC23:12
*** phantomcircuit_ has joined #openstack-meeting23:14
*** jdurgin has quit IRC23:14
*** galstrom has joined #openstack-meeting23:15
*** mugu has quit IRC23:16
*** mugu has joined #openstack-meeting23:16
*** lloydde_ has quit IRC23:17
*** oubiwann has joined #openstack-meeting23:19
*** rkukura has quit IRC23:19
*** dtroyer_zzz is now known as dtroyer23:21
*** somik has joined #openstack-meeting23:24
*** mtaylor1 has joined #openstack-meeting23:25
*** dtroyer- has joined #openstack-meeting23:26
*** littleidea has joined #openstack-meeting23:26
*** ohnoimde1d has joined #openstack-meeting23:27
*** ewindisch has joined #openstack-meeting23:27
*** anotherjesse is now known as anotherjesse_zz23:29
*** shwetaap has quit IRC23:30
*** dendroba` has joined #openstack-meeting23:30
*** shwetaap has joined #openstack-meeting23:31
*** sandywalsh has quit IRC23:31
*** s0mik has quit IRC23:32
*** GheRivero has quit IRC23:32
*** DuncanT has quit IRC23:32
*** dendrobates has quit IRC23:32
*** ohnoimdead has quit IRC23:32
*** dtroyer has quit IRC23:32
*** mtaylor has quit IRC23:32
*** somik is now known as s0mik23:32
*** dtroyer- is now known as dtroyer23:32
*** DuncanT has joined #openstack-meeting23:34
*** zykes- has joined #openstack-meeting23:37
*** GheRivero has joined #openstack-meeting23:39
*** ewindisch has quit IRC23:41
*** lloydde has joined #openstack-meeting23:42
*** sdague_ has joined #openstack-meeting23:42
*** zykes-_ has quit IRC23:42
*** glenc has quit IRC23:42
*** glenc_ has joined #openstack-meeting23:42
*** Madkiss has quit IRC23:43
*** Madkiss_ has joined #openstack-meeting23:43
*** Madkiss_ is now known as Madkiss23:43
*** jog0_ has joined #openstack-meeting23:44
*** troytoma` has joined #openstack-meeting23:45
*** lloydde has quit IRC23:47
*** gakott has joined #openstack-meeting23:49
*** mnewby_ has joined #openstack-meeting23:50
*** ewindisch has joined #openstack-meeting23:50
*** jog0 has quit IRC23:50
*** sdague has quit IRC23:50
*** troytoman-away has quit IRC23:50
*** anotherjesse_zz has quit IRC23:50
*** no`x has quit IRC23:50
*** reed has quit IRC23:51
*** garyk has quit IRC23:51
*** Adri2000 has quit IRC23:51
*** Kiall has quit IRC23:51
*** jog0_ is now known as jog023:51
*** reed has joined #openstack-meeting23:51
*** anotherjesse_zz has joined #openstack-meeting23:51
*** anotherjesse_zz is now known as anotherjesse23:51
*** no`x has joined #openstack-meeting23:51
*** Kiall has joined #openstack-meeting23:54
*** mnewby has quit IRC23:54
*** lloydde has joined #openstack-meeting23:54
*** mnewby_ has quit IRC23:55
*** blamar has joined #openstack-meeting23:57
*** jgriffith has quit IRC23:57
*** mtaylor1 is now known as mtaylor23:57
*** galstrom has quit IRC23:59
*** lloydde has quit IRC23:59

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