Tuesday, 2012-05-29

*** bencherian has quit IRC00:02
*** bencherian has joined #openstack-meeting00:03
*** Ravikumar_hp has joined #openstack-meeting00:18
*** ovidwu has quit IRC00:19
*** ryanpetrello has joined #openstack-meeting00:30
*** fattarsi has quit IRC01:18
*** bencherian has quit IRC01:20
*** ywu has joined #openstack-meeting01:20
*** deshantm has joined #openstack-meeting01:22
*** ryanpetrello has quit IRC01:50
*** ryanpetrello has joined #openstack-meeting02:01
*** Mandell_ has joined #openstack-meeting02:10
*** Mandell has quit IRC02:10
*** deshantm_ has joined #openstack-meeting02:14
*** deshantm has quit IRC02:17
*** _ozstacker_ has quit IRC02:21
*** ozstacker has joined #openstack-meeting02:21
*** deshantm_ has quit IRC02:31
*** ryanpetrello has quit IRC02:33
*** bencherian has joined #openstack-meeting02:42
*** sdake has joined #openstack-meeting02:49
*** sandywalsh_ has quit IRC02:50
*** sdake has quit IRC03:03
*** sdake has joined #openstack-meeting03:04
*** matwood has quit IRC03:06
*** garyk has quit IRC03:10
*** ywu has quit IRC03:11
*** dwcramer has quit IRC03:18
*** dwcramer has joined #openstack-meeting03:30
*** sdake has quit IRC03:38
*** edygarcia has quit IRC03:54
*** dwcramer has quit IRC04:03
*** garyk has joined #openstack-meeting04:03
*** nati_ueno has joined #openstack-meeting04:19
*** littleidea has quit IRC04:41
*** zul has quit IRC04:58
*** zul has joined #openstack-meeting04:59
*** nati_uen_ has joined #openstack-meeting05:42
*** nati_ueno has quit IRC05:43
*** nati_ueno has joined #openstack-meeting05:52
*** nati_uen_ has quit IRC05:52
*** Ravikumar_hp has quit IRC05:58
*** GheRivero has joined #openstack-meeting06:01
*** nati_ueno has quit IRC06:32
*** vishy has quit IRC06:32
*** vish1 has joined #openstack-meeting06:32
*** devcamcar has quit IRC06:33
*** tightwork has quit IRC06:33
*** jakedahn_zz has quit IRC06:33
*** dtroyer has quit IRC06:33
*** dtroyer has joined #openstack-meeting06:34
*** devcamcar has joined #openstack-meeting06:34
*** jakedahn_zz has joined #openstack-meeting06:34
*** ttrifonov_zZzz is now known as ttrifonov06:36
*** bencherian has quit IRC06:37
*** tightwork has joined #openstack-meeting06:37
*** mikal has quit IRC06:45
*** mikal has joined #openstack-meeting06:47
*** Razique has joined #openstack-meeting07:02
*** sdague_ has joined #openstack-meeting07:07
*** dragondm has quit IRC07:09
*** _cerberus_ has quit IRC07:09
*** _cerberus_ has joined #openstack-meeting07:09
*** dragondm has joined #openstack-meeting07:09
*** gholt_ has joined #openstack-meeting07:09
*** mtaylor has quit IRC07:09
*** mtaylor has joined #openstack-meeting07:10
*** dendroba` has joined #openstack-meeting07:10
*** gholt has quit IRC07:11
*** Daviey has quit IRC07:11
*** sdague has quit IRC07:11
*** ttrifonov has quit IRC07:11
*** dendrobates has quit IRC07:11
*** gholt_ is now known as gholt07:11
*** ttrifonov_ has joined #openstack-meeting07:11
*** Daviey has joined #openstack-meeting07:19
*** ttrifonov_ is now known as ttrifonov07:37
*** Mandell_ has quit IRC08:03
*** derekh has joined #openstack-meeting08:09
*** semyazz has joined #openstack-meeting08:21
*** semyazz has left #openstack-meeting08:21
*** semyazz has joined #openstack-meeting08:39
*** semyazz has left #openstack-meeting08:39
*** _ozstacker_ has joined #openstack-meeting09:23
*** _ozstacker_ has quit IRC09:23
*** ozstacker has quit IRC09:24
*** semyazz has joined #openstack-meeting09:24
*** semyazz has left #openstack-meeting09:29
*** sdake has joined #openstack-meeting09:42
*** milner has quit IRC10:45
*** milner has joined #openstack-meeting10:57
*** sdague_ has quit IRC11:20
*** markvoelker has joined #openstack-meeting11:37
*** semyazz has joined #openstack-meeting11:46
*** nati_ueno has joined #openstack-meeting11:50
*** dwcramer has joined #openstack-meeting11:53
*** semyazz has left #openstack-meeting11:57
*** nati_ueno has quit IRC12:00
*** sdague has joined #openstack-meeting12:03
*** primeministerp has joined #openstack-meeting12:18
*** dprince has joined #openstack-meeting12:23
*** sandywalsh has joined #openstack-meeting12:45
*** troytoman-away is now known as troytoman12:53
*** martines has joined #openstack-meeting12:54
*** AlanClark has joined #openstack-meeting12:58
*** dendroba` is now known as dendro-afk13:07
*** dolphm has joined #openstack-meeting13:07
*** mattray has joined #openstack-meeting13:07
*** mattray has quit IRC13:10
*** ttrifonov has quit IRC13:10
*** tightwork has quit IRC13:10
*** davidkranz has quit IRC13:10
*** dabo has quit IRC13:10
*** ttx has quit IRC13:12
*** ttx has joined #openstack-meeting13:12
*** ttx has joined #openstack-meeting13:12
*** dolphm has quit IRC13:15
*** ayoung has joined #openstack-meeting13:16
*** mattray has joined #openstack-meeting13:16
*** ttrifonov has joined #openstack-meeting13:16
*** tightwork has joined #openstack-meeting13:16
*** davidkranz has joined #openstack-meeting13:16
*** dabo has joined #openstack-meeting13:16
*** tightwork has quit IRC13:16
*** ayoung has quit IRC13:16
*** ayoung has joined #openstack-meeting13:16
*** tightwork_ has joined #openstack-meeting13:17
*** randomubuntuguy has quit IRC13:18
*** ryanpetrello has joined #openstack-meeting13:23
*** rash has joined #openstack-meeting13:33
*** dwcramer has quit IRC13:34
*** primeministerp has quit IRC13:40
*** edygarcia has joined #openstack-meeting13:41
*** GheRivero_ has joined #openstack-meeting13:42
*** Ravikumar_hp has joined #openstack-meeting13:51
*** littleidea has joined #openstack-meeting13:54
*** littleidea has quit IRC13:58
*** anderstj has joined #openstack-meeting14:00
*** jgriffith_zz is now known as jgriffith14:01
*** anderstj has quit IRC14:02
*** dolphm has joined #openstack-meeting14:07
*** nikhil_ has joined #openstack-meeting14:16
*** nikhil_ is now known as Guest1133414:16
*** dwcramer has joined #openstack-meeting14:20
*** dolphm has quit IRC14:22
*** dolphm has joined #openstack-meeting14:22
*** dwcramer has quit IRC14:28
*** dwcramer has joined #openstack-meeting14:28
*** Ravikumar_hp has quit IRC14:30
*** dtroyer is now known as dtroyer_zzz14:32
*** Mandell has joined #openstack-meeting14:32
*** mdomsch has joined #openstack-meeting14:34
*** littleidea has joined #openstack-meeting14:35
*** littleidea has quit IRC14:36
*** dwcramer has quit IRC14:36
*** littleidea has joined #openstack-meeting14:36
*** edygarcia has quit IRC14:39
*** edygarcia has joined #openstack-meeting14:39
*** oubiwann has joined #openstack-meeting14:41
*** blamar has joined #openstack-meeting14:42
*** mikal has quit IRC14:48
*** dwcramer has joined #openstack-meeting14:49
*** mikal has joined #openstack-meeting14:49
*** rafaduran has quit IRC14:56
*** jog0 has joined #openstack-meeting14:58
*** jaypipes has joined #openstack-meeting14:58
*** matwood has joined #openstack-meeting15:01
*** jog0 has quit IRC15:07
*** Ravikumar_hp has joined #openstack-meeting15:08
*** dwcramer has quit IRC15:16
*** dwcramer has joined #openstack-meeting15:17
*** Mandell has quit IRC15:21
*** Razique has quit IRC15:27
*** heckj has joined #openstack-meeting15:40
*** dwcramer has quit IRC15:43
*** littleidea_ has joined #openstack-meeting15:53
*** liemmn has quit IRC15:55
*** jog0 has joined #openstack-meeting15:56
*** littleidea has quit IRC15:56
*** littleidea_ is now known as littleidea15:56
*** Ravikumar_hp has quit IRC16:00
*** dwcramer has joined #openstack-meeting16:04
*** joearnold has joined #openstack-meeting16:05
*** dtroyer_zzz is now known as dtroyer16:15
*** joearnold has quit IRC16:16
*** darraghb has joined #openstack-meeting16:17
*** dhellmann has joined #openstack-meeting16:26
*** joearnold has joined #openstack-meeting16:32
*** edygarcia has quit IRC16:42
*** jdurgin has joined #openstack-meeting16:42
*** Mandell has joined #openstack-meeting16:44
*** anderstj has joined #openstack-meeting16:45
*** garyk has quit IRC16:45
*** Ravikumar_hp has joined #openstack-meeting16:56
*** jdurgin has quit IRC16:57
*** jdurgin has joined #openstack-meeting16:58
*** edygarcia has joined #openstack-meeting16:59
*** Ravikumar_hp has quit IRC17:01
*** Ravikumar_hp has joined #openstack-meeting17:01
*** derekh has quit IRC17:07
*** Ravikumar_hp has quit IRC17:07
*** garyk has joined #openstack-meeting17:09
*** joearnold has quit IRC17:11
*** aswadrangnekar has joined #openstack-meeting17:14
*** joearnold has joined #openstack-meeting17:14
*** Ravikumar_hp has joined #openstack-meeting17:15
*** jakedahn_zz is now known as jakedahn17:20
*** bencherian has joined #openstack-meeting17:23
*** nati_ueno has joined #openstack-meeting17:27
*** jakedahn is now known as jakedahn_zz17:29
*** Mandell has quit IRC17:30
*** Mandell has joined #openstack-meeting17:30
*** jakedahn_zz is now known as jakedahn17:31
*** darraghb has quit IRC17:35
*** GheRivero_ has quit IRC17:37
*** troytoman is now known as troytoman-away17:38
*** joearnold has quit IRC17:43
*** liemmn has joined #openstack-meeting17:45
*** edygarcia_ has joined #openstack-meeting17:45
*** Ravikumar_hp has quit IRC17:46
*** rafaduran has joined #openstack-meeting17:46
*** edygarcia has quit IRC17:46
*** edygarcia_ is now known as edygarcia17:46
*** liemmn has quit IRC17:46
*** aswadrangnekar has quit IRC17:48
*** ohnoimdead has quit IRC17:49
*** ohnoimdead has joined #openstack-meeting17:49
*** anderstj_ has joined #openstack-meeting17:50
*** anderstj has quit IRC17:52
*** joearnold has joined #openstack-meeting17:52
*** edygarcia_ has joined #openstack-meeting17:53
*** edygarcia has quit IRC17:56
*** edygarcia_ is now known as edygarcia17:56
*** edygarcia_ has joined #openstack-meeting17:57
*** adjohn has joined #openstack-meeting18:01
*** devananda has joined #openstack-meeting18:01
heckjfolks here for keystone meeting?18:01
*** edygarcia has quit IRC18:02
openstackMeeting started Tue May 29 18:02:12 2012 UTC.  The chair is heckj. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
heckjOla all18:02
heckj#topic status and progress...18:02
*** openstack changes topic to "status and progress..."18:02
heckjmilestone 1 is cut and available18:02
heckjso we're into milestone 218:02
*** edygarcia_ has quit IRC18:03
heckj#link https://launchpad.net/keystone/+milestone/folsom-218:03
*** liemmn has joined #openstack-meeting18:03
heckjLots of blueprints this next milestone18:03
*** dolphm_ has joined #openstack-meeting18:03
ayoungI was hoping to use Apache HTTPD and make it a non issue.18:03
rafaduranhi all18:03
ayoungLet me check on the status of Eventlet upstream IPv6 support.18:04
heckjayoung: sounds good18:04
heckjtoken_id work is under review now18:04
heckjV3 API is in review, and needs another draft. I have a significant amount of feedback to pull together this week.18:05
heckjIs joesavak around?18:05
*** edygarcia has joined #openstack-meeting18:05
heckjdolphm (guilty by association here) - any idea what joesavak specifically wanted with https://blueprints.launchpad.net/keystone/+spec/rbac-keystone? (I updated the whiteboard with what I think it needs, but wasn't sure)18:07
dolphm_He reviewed my proposal, and gave it a thumbs up18:08
dolphm_Some of his feedback was already included in what I posted tithe draft API18:08
*** edygarcia_ has joined #openstack-meeting18:08
heckjdolphm_: do we need a separate blueprint for what he wants there?18:08
*** joearnold has joined #openstack-meeting18:09
dolphm_Something specific you're referring to?18:09
*** edygarcia__ has joined #openstack-meeting18:09
heckjdolphm_: just trying to figure out what he wanted with the blueprint and how to track it's "progress".18:09
heckjeverett toewes about?18:10
dolphm_He likes actions/capabilities, doesn't need rules for rax18:10
heckjdolphm_: I guess my question really is should we be tracking a blueprint for that specific work against the v3 api?18:10
*** joearnold has quit IRC18:11
dolphm_I'd roll it into the RBAC-keystone bp, but it's up to you18:11
*** edygarcia has quit IRC18:12
*** jakedahn is now known as jakedahn_zz18:12
*** edygarcia_ has quit IRC18:13
heckjI'll hunt down chmouel and everett related to the last two blueprints in folsom-2 to find out how they're doing and what help might be needed. Everett is a new contributor, so i'm expecting he'll need some18:13
heckj#topic open discussion18:13
*** openstack changes topic to "open discussion"18:13
heckjWe've got a pile of reviews outstanding. I'm working through a number today18:14
heckjhaven't checked bug and questions this week yet either, so I"ll be trying to hit that today as well18:14
heckjAny open questions?18:15
liemmno/  Thanks for all the love for https://review.openstack.org/#/c/7706/...  How do we trigger SmokeStack for patch set#3?18:16
ayoungthe ... messes up the hyperlink18:16
liemmnWhat ...?18:17
heckjliemmn: not entirely sure… mtaylor or dprince might have a good idea18:17
dolphmneed someone with smokestack admin access to retrigger last i asked18:17
liemmnokie dokie18:17
ayoungwho are the core reviewers?  Why does this patch require so many reviewers to get in?  We have 3 community members plus core....18:18
heckjayoung: all reviews take 2 core reviewers18:19
dolphmi'm happy to +2 if there's community consensus there18:19
heckjcore members are https://launchpad.net/~keystone-core/+members18:19
ayoungdolphm, are you core?18:19
dolphmayoung: yes18:19
ayoungyeah, and this code is basically adding in functionality that didn't make the KSL redo18:20
*** edygarcia__ has quit IRC18:20
*** dolphm_ has quit IRC18:20
*** edygarcia has joined #openstack-meeting18:20
ayoungAs far as other topics:  I have a working proof of concept of the PKI signed tokens18:21
ayoung#link https://github.com/admiyo/keystone/tree/signed-tokens18:21
heckjayoung: nice!18:21
*** lcheng has joined #openstack-meeting18:22
ayoungOne thing I noticed is that the service.py authenticate method is kindof overflowing its scope.  I think this should move mostly into a middleware component18:22
ayoungit does more than authenticate, really,  as it also generates the data for the token,  then calls the token API18:22
dolphmwhat would you move to middleware?18:23
dolphmit is a token api call18:23
ayoung this one might include a refactoring where user-id authentication is one middleware component, and the token generation and persistance a different one18:23
*** mnaser_ has quit IRC18:23
ayoungI have to grok the architecture a little bit better18:24
dolphmif you can simplify, please do!18:24
ayoungdolphm, there are 3 stages as I see it.  1 is authenticate.  2  Is generate token,  and that needs to call the SSL binary (in my first impl)  3 is persist to DB/KVS whatever18:25
ayoungI'd like to be able to say:  add in these two authentication mechanisms:  basic-auth,  certiificate,  and if you use those,  you then get aswsigned a token18:25
ayounghowever,  if you come in with a token,  you can do new things.18:26
ayoungBut you need to use a non-token based auth in order to get assigned a token,  or tokens never really time out...18:26
dolphmbasic-auth == http basic auth?18:27
ayoungdolphm, yes18:27
ayoungdolphm, as well as client certificate auth, which is part of the PkI blueprint.18:27
dolphmmakes sense to me18:27
ayoungdolphm, the idea is, I think, that the authentication mechanism sets REMOTE_USER,  which is the WSGI way of saying the container has done auth for us.18:28
ayoungSo the definition of authenticated is that REMOTE_USER is set,  and then we can build a token for users that need it18:29
ayoungIt should also allow us to interop with Apache HTTPD a little more cleanly18:29
*** novas0x2a|laptop has joined #openstack-meeting18:29
ayoungheckj, I'd like to backpeddal on https://bugs.launchpad.net/keystone/+bug/99613918:31
ayoung"Change default token backend from KVS to SQL "18:32
* heckj looks18:32
uvirtbotLaunchpad bug 996139 in keystone "Change default token backend from KVS to SQL" [Undecided,In progress]18:32
ayoungI think that change only makes sense if we default to HTTPD18:32
ayoungI think that for Eventlet,  I'd prefer to keep the Tokens in memory.  Especially in light of the PKI Signing18:32
dolphmwhat's the impact from pki?18:32
ayoungsince we won't have to go back to Keystone to authenticate tokens,  "losing" them on reboot is no longer a real concern18:33
heckjayoung: I'm OK with that. You're welcome to mark the bug as invalid to kill it.18:33
ayoungI like memory vs  SQL  for security reasons18:33
ayoungIE,  you can't get access to everyone's token via A SQL query18:34
ayoungheckj, OK.  Will do18:34
*** jakedahn_zz is now known as jakedahn18:34
dolphmdo pki tokens need to be persisted at all, then? or just logged a bit18:34
rafaduranayoung: if many tokens are saved in memory, can be an issue?18:35
*** troytoman-away is now known as troytoman18:35
ayoungrafaduran, possibly18:35
ayoungthe new tokens are going to be larger.  Probably about 700 Bytes or so,  ve 64 currently18:36
ayoungrafaduran, so maybe the right answer is to not persist them at all18:36
ayoungI could see an argument that for Signed tokens,  just append the new tokens to an audit log18:37
rafaduranayoung: yes, I think so18:37
rafaduranayoung: if you are not going back to ask for them not saving them seems the way to go18:38
*** _adjohn has joined #openstack-meeting18:39
ayoungrafaduran, let me think about that for a bit.   There is some discussion vis-a-vis revocation I want to deal with first18:39
ayoungrevocation might require persistance18:39
*** mnaser has joined #openstack-meeting18:40
dolphmayoung: pki tokens still have an identifier, i assume?18:40
dolphmayoung: persist only that, and remember its state?18:40
ayoungdolphm, well,  for the first approximation, it is the whole token18:40
dolphma hash of the entrie token then?18:41
dolphmsha1 or whatever18:41
ayoungdolphm, I thought there was a separate Blueprint for splitting Token ID from secret portion18:41
ayoungHashing would be fine...just not certain yet it is required18:41
dolphmayoung: that was just a thought, i didn't make a bp18:41
*** adjohn has quit IRC18:42
*** _adjohn is now known as adjohn18:42
ayoungIf a token has a life span of 8 hours, are we really going to need revocation?18:42
dolphmayoung: 8 hours is an eternity ;)18:42
ayoungI tend to doubt it, as it makes the system much more complex, and Kerberos works with 8 hour service tickets for 20+ years now18:43
ayoungdolphm, the only reason to make them that long is if tokens need to be used in batch jobs or something18:43
ayoungfor most uses,  20 minutes would likely be fine18:44
dolphmpersonally, i think "need" is relative, so i'm just playing devil's advocate18:44
ayoungThe devil can hire his own advocates.  He has the payroll for it18:44
*** reed has joined #openstack-meeting18:44
dolphmas long as the token lifespan is configurable18:44
ayoungdolphm, that is my thinking18:44
*** Gordonz has joined #openstack-meeting18:46
rafaduranayoung: I don't know a lot of encryption so probably is a bad idea, but you could get automatic revocation if the encryption includes a variable part that changes/cycle afet expriation time18:47
ayoungrafaduran, if it is after expiration time,  you have to go and get a new certificate.18:48
ayounglets call them tokens, actually18:48
ayoungso the signed token has a expiry in it18:48
ayoungand the auth_token middleware will check that18:49
ayoungif the token has timed out,  the user will not be authenticated18:49
ayoungthe usually deal is that they then go back to keystone and get a new token18:49
rafaduranayoung: I think that would work fine18:50
ayoungWe can provide a grace period if the token was used to auth against, say, Nova, and then is needed a while later to talk to, say Quantum.18:50
ayoungand b "talk to"  I mean that nova sends the token along as part of a quantum request....18:51
mtaylorheckj: aroo?18:54
heckjmtaylor: ola18:54
heckjy'all good with ending the meeting?18:55
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"18:56
openstackMeeting ended Tue May 29 18:55:59 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-29-18.02.html18:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-29-18.02.txt18:56
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-29-18.02.log.html18:56
*** Shrews has joined #openstack-meeting18:56
heckjmtaylor: all yours18:57
mtaylorheckj: thanks!18:58
*** pcrews has joined #openstack-meeting18:59
mtaylorwho wants to talk about CI?19:01
openstackMeeting started Tue May 29 19:01:28 2012 UTC.  The chair is mtaylor. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
* LinuxJedi appears to be the only one :)19:02
mtaylorLinuxJedi: we'll give folks a few to straggle in19:02
clarkbI am here19:02
* clarkb read mtaylor's "aroo" in Nixon from futurama's voice19:02
LinuxJedihehe :)19:03
mtaylorLinuxJedi: how about you tell us whatcha been doing?19:03
LinuxJedimtaylor: sure19:03
LinuxJediso, lots of little things this week19:04
LinuxJediStackforge now has a Gerritbot running on #stackforge-dev (after requests from heat)19:04
LinuxJediJenkins Jobs has lots of minor updates and on more Openstack projects (I'm sure mtaylor will speak about that).  I have done documentation updates and blogged about it19:05
LinuxJediWe had an issue with pep8 where some new rules in a new release broke lots of projects during a release.  A slight modification to tox.ini worked around it for now19:05
LinuxJediAll Stackforge jobs now run on the new Jenkins jobs filler too19:06
LinuxJediStackforge's disk filled again due to my error, shouldn't happen again.19:06
LinuxJediAnd the openstack-ci-puppet tree is now tested with pyflakes19:06
*** GheRivero_ has joined #openstack-meeting19:07
LinuxJediand about a billion little things.19:07
LinuxJediany questions?19:07
mtaylorit's been a week :)19:07
clarkbdo we expect openstack to honor pep8 1.1 at some point? I suppose we don't really worry about it too much?19:07
LinuxJediclarkb: yes19:08
LinuxJediI don't have more of an answer than that though19:08
mtaylorseveral of the projects have fixed themselves alread19:08
notmynameLinuxJedi: is the gerrit hook fixed from this weekend? what was up with that?19:08
mtaylorthe underlying build bug is that the pep8 version specified in tools/test-requires is not the thing pulling in the pep8 for the test...19:08
notmynamemtaylor: swift is 1.1 compliant now :-)19:08
mtaylorso there was a version mismatch19:08
LinuxJedinotmyname: ah, yes, so...19:09
mtaylorwe're working on a better solution for that systemically19:09
mtaylorunfortunately, there is a setuptools/pip disconnect which is really frustrating19:09
LinuxJedigerrit trigger broke over the weekend.  It appears to be due to a stuck thread in Jenkins.  A restart fixed it19:09
LinuxJedibut we are working on making such things less likely19:09
mtaylorin the future, jeblair's work should obviate that problem moving forward19:09
mtaylorwhat LinuxJedi said19:09
LinuxJedijust one of the billion things I fixed this week ;)19:10
mtayloras a follow up from me on one of LinuxJedi's things ... all of the openstack projects are on jenkins job filler now19:10
*** Gordonz has quit IRC19:11
*** jog0 has quit IRC19:11
mtaylorso things like coverage or docs jobs that break at this point are things we should treat as bugs in the project to be fixed there19:11
*** joearnold has joined #openstack-meeting19:11
mtaylorwhich means I think we should be able to annoy people on failures in non check-* or gate-* jobs19:11
LinuxJediblog post at http://www.linuxjedi.co.uk/2012/05/openstacks-jenkins-job-filler.html by the way for people who want to learn more about it19:12
mtaylorcool. thanks LinuxJedi19:12
mtaylorclarkb: how's life in your world?19:12
jeblair#link http://www.linuxjedi.co.uk/2012/05/openstacks-jenkins-job-filler.html19:12
annegentlewill this jenkins job filter fix the sphinx doc builds (autodoc python modules problems)?19:12
annegentleP.S. nice job on the docs at http://ci.openstack.org/jenkins_jobs.html19:13
mtaylorannegentle: no, but we will be building all of the docs jobs the same now, so there's one less variable to track down19:13
clarkbSo late Friday I thought my gerrit patches were all ready and good to go when I realized that I had been working off of master which is old.19:13
LinuxJediannegentle: thx :)19:13
* mtaylor apologizes to clarkb for that19:13
clarkbI spend the majority of my time last week getting those going19:14
clarkbafter some quick cherry picking this morning I think those patches are good to go again19:14
clarkb(they have been reapplied to the openstack/2.4 branch)19:14
clarkbI lucked out with that as I don't think Shrews had an easy time reapplying the commits to the newer branch19:15
clarkbI think that is it for me. No exciting fires were put out19:15
mtaylorcool. thanks!19:16
mtaylor(speaking of, I kinda broke the gerrit gating jobs this weekend, which I have suitably chastised for - hopefully they're better now)19:16
LinuxJedibetween me and mtaylor we broke all jobs for a very short time on Sunday, but no jobs were run in this time :)19:17
LinuxJediapart from Stackforge but I don't think anyone noticed19:17
mtaylorjeblair: anything on the make-things-parallel front?19:17
clarkblooks like jenkins just +1ed my most recent push to gerrit so I think it is working again19:18
jeblairgerrit-git-prep now supports testing dependent changes19:18
jeblairso you can tell it "merge change A, B, then C and test"19:19
jeblairwhich is a pre-requisite for speculative execution of jenkins gating tests19:19
notmyname(oh, and thanks LinuxJedi for helping me merge things during a holiday weekend)19:19
LinuxJedinotmyname: wasn't a holiday here in the UK ;)19:20
notmynameLinuxJedi: it was still Sunday pm central time. very late for you either way :-)19:20
mtaylorclarkb: w00t!19:20
jeblairthat's in now, but not being used; when we switch to the new parallelized gating system, we'll start using that.19:20
jeblairthat's it.19:20
mtaylorjeblair: I'm excited by that19:21
mtaylorShrews: you wanna punch me in the kidney about work in progress?19:21
Shrewsmtaylor: emphatically yes19:21
*** mnaser has quit IRC19:21
* LinuxJedi thinks Shrews doesn't want the Java mug I bought for him :/19:22
Shrewsplumbing appears to have changed rather significantly in 2.4, so i need to re-do a lot of that. but at least this time i know where to look for things19:22
Shrewsso yay19:22
mtaylorthat's good19:22
mtaylor(for folks following at home, same problem as clarkb -- I forgot to tell clarkb and Shrews about how we're tracking gerrit upstream...)19:23
LinuxJediso ignore the random bullet holes in mtaylor's torso19:23
mtaylorI guess from me, other than breaking things - I've been working on getting jclouds unittest builders running19:24
mtaylorwhich would be easy - except for the setup time it takes to launch and configure a build slave19:24
mtaylorI was going DEEP trying to get it sorted, but it seems I may have left a zero off of the timeout - so I'm re-testing :)19:25
*** sdake is now known as sdake_pto19:26
mtaylorso hopefully that'll be done this week ... as will proper support for maven jobs from jenkins job filler19:26
mtayloranybody else got anything?19:26
LinuxJedimtaylor: do you want me or you to do maven stuff?19:26
clarkbmtaylor: you mentioned that some of our changes to gerrit in 2.3 would not be applied to 2.419:27
mtaylorLinuxJedi: I'll poke at it ... the current maven job thing was my doing :)19:28
mtaylorLinuxJedi: unless you get bored :)19:28
clarkband do we have a plan for upgrading gerrit to 2.4?19:28
LinuxJedimtaylor: I have a few things I was planning to do first, if you haven't started by Thursday I can take over19:28
mtaylorclarkb: yeah - I was working on upstreaming the require-short-subject patch19:29
mtaylorand it looks like there's a better way to do it coming up19:29
mtaylorso I'm just going to wait on that (also, nobody's actually using it)19:30
mtaylorok. I think that does it19:35
mtaylorthanks everybody!19:35
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"19:36
openstackMeeting ended Tue May 29 19:36:01 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:36
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-29-19.01.html19:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-29-19.01.txt19:36
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-29-19.01.log.html19:36
LinuxJedimtaylor: can we change the default topic on this channel?19:36
mtaylorLinuxJedi: PLEASE19:36
* LinuxJedi adds to todo to get the bot user to do that :)19:36
*** dprince has quit IRC19:37
*** Shrews has left #openstack-meeting19:39
*** adjohn has quit IRC19:41
*** rkukura has joined #openstack-meeting19:43
*** lcheng has quit IRC19:47
*** pimpministerp has joined #openstack-meeting19:48
*** pimpministerp has quit IRC19:50
*** dwcramer has quit IRC20:03
*** ewindisch has joined #openstack-meeting20:04
*** rkukura has left #openstack-meeting20:05
*** rkukura has joined #openstack-meeting20:08
*** s0mik has joined #openstack-meeting20:18
*** ijw has joined #openstack-meeting20:20
*** pcrews has left #openstack-meeting20:22
*** mnaser has joined #openstack-meeting20:22
*** ayoung has quit IRC20:23
*** adjohn has joined #openstack-meeting20:24
*** ttrifonov is now known as ttrifonov_zZzz20:35
*** jakedahn is now known as jakedahn_zz20:41
*** dwcramer has joined #openstack-meeting20:42
*** bcwaldon has joined #openstack-meeting20:43
*** ayoung has joined #openstack-meeting20:47
*** MarkAtwood has joined #openstack-meeting20:48
*** rash has quit IRC20:48
*** danwent has joined #openstack-meeting20:52
*** gabrielhurley has joined #openstack-meeting20:55
*** salv-orlando has joined #openstack-meeting20:56
*** markvoelker has quit IRC20:56
*** jakedahn_zz is now known as jakedahn20:56
bcwaldonI mena Cloyster?21:00
ttxheckj, vishy, devcamcar, danwent: around ?21:00
heckjohnoimdead is standing in for devcamcar21:01
ttxvishy is still in vacation apparently, so we'll just pile up actions on him.21:01
openstackMeeting started Tue May 29 21:01:53 2012 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
ttxToday's usual agenda: http://wiki.openstack.org/Meetings/ProjectMeeting21:02
ttx#topic Actions from previous meeting21:02
*** openstack changes topic to "Actions from previous meeting"21:02
ttxpushing back to next week:21:02
ttx#action vishy to adjust 'undefined' folsom bp priorities21:02
*** johnpostlethwait has joined #openstack-meeting21:02
ttx#topic Keystone status21:02
*** openstack changes topic to "Keystone status"21:02
bcwaldonhis priorities are elsewhere at the moment21:02
ttxheckj: o/21:03
ttx#link https://launchpad.net/keystone/+milestone/folsom-221:03
ttxheckj: Is status accurate for those ? i.e. mostly not started ?21:03
heckjttx: correct. I'm hunting a few folks to see where they are, haven't received any detail back, so leaveing them in not-started for now. Will push out if they're not going to be able to engage shortly.21:03
ttxheckj: how is the feedback on v3 APi going so far ?21:04
heckjttx: may collapse a BP or two besed on feedback21:04
heckjAPI feedback has been excellent - another draft will be forthcoming in the next few days with any luck. Still waiting for some feedback because folks on vacation right now21:04
ttxStil on track to deliver the implementation of the API in F2 ?21:05
*** johnpostlethwait has quit IRC21:05
*** matwood_ has joined #openstack-meeting21:06
*** johnpostlethwait has joined #openstack-meeting21:06
heckjttx: That's looking iffy, but we're going to try. Given the draft feedback and round-up process, it may slip into F321:06
ttx"stop-ids-in-uris" was in F1 and deferred, do you have news on progress on that ?21:06
ttxhaven't seen code proposed yet21:07
heckjcode is under review, just not linked. Moment and I'll get that link21:07
ttx#info implement-v3-core-api may slip to F3 due to  draft feedback and round-up process21:07
ttxIn other news, your Folsom plan at https://blueprints.launchpad.net/keystone/folsom looks good and realistic21:07
ttxheckj: anything else ?21:08
heckj#link https://review.openstack.org/#/c/7010/ <-- stop-id work21:08
heckjnope. Questions?21:08
*** markwash_ has joined #openstack-meeting21:08
ttxDo you / keystone plan to participate to the Bugtriage day on June 7th ?21:08
*** matwood has quit IRC21:09
heckjttx: yep. We've been trying to keep up on that triage a bit more aggressively, so we're a touch ahead, but a run through would be good regardless21:09
ttxOther questions about Keystone ?21:09
*** MarkAtwood has quit IRC21:10
*** matwood_ has quit IRC21:10
ttx#topic Swift status21:10
*** openstack changes topic to "Swift status"21:10
ttxnotmyname: yo21:10
ttx#link https://launchpad.net/swift/+milestone/1.5.021:10
notmyname#link https://github.com/openstack/swift/blob/576be4d77efc57b7ee20f0207845349de9960b1b/CHANGELOG21:11
ttx#info Swift 1.5.0 milestone-proposed branch was cut today, waiting for the final go-ahead sometimes Thursday.21:11
notmynameswift 1.5.0 is getting ready for release21:11
ttxnotmyname: I filed bug 1005801 as potentially release-critical21:11
uvirtbotLaunchpad bug 1005801 in swift "[1.5.0] Missing test/sample.conf in generated tarballs" [High,Confirmed] https://launchpad.net/bugs/100580121:11
ttxWe should either fix it (in master and in milestone-proposed) or un-1.5.0-target it21:11
*** rustlebee has joined #openstack-meeting21:11
ttxno idea of the exact impact, so if you could have a look21:11
notmynameok, I'll look in to that when we're done here21:11
notmynamethere are a few things that should be mentioned about the 1.5.0 release21:12
ttxif you confirm it, I can push fix tomorrow morning if nobody beats me to it today21:12
*** SumitNaiksatam has joined #openstack-meeting21:12
notmynamethe first 3 points on the CHANGELOG I linked above will require config changes for deployers21:12
*** ncode has joined #openstack-meeting21:13
notmynameI'm working on an email to be sent to the mailing list at the time of official release to talk about all the changes in this release21:13
ttxnotmyname: we should probably highlight that directly in the release email announcement. I'll let you write it ?21:14
notmynameya, I'll definitely highlight it21:14
ttxIn other news, could you confirm that 1.5.1 will be the first version that will no longer have the swift python client lib shipped within swift ?21:14
notmynamethat's the plan, and I think there is a very good chance that it will happen21:15
ttxhorizon: might affect you ^21:15
ttxnotmyname: Anything else ?21:15
ttx#info 1.5.1 should be the first version that will no longer have the swift python client lib shipped within swift21:16
ttxQuestions on Swift ?21:16
ttx#info 1.5.0 will require config changes for deployers21:16
ttx#topic Glance status21:17
*** openstack changes topic to "Glance status"21:17
ttxbcwaldon: o/21:17
ttx#link https://launchpad.net/glance/+milestone/folsom-221:17
ttxGot a few questions for you21:17
ttxapi-v2-images-sorting has no assignee ?21:18
ttxso you're looking for someone to do the work ? Or you know who will ?21:18
bcwaldonI'll do it if nobody volunteers21:19
ttxI suppose its status is "not started", then.21:19
bcwaldonthere's no rush at this point21:19
*** randomubuntuguy has joined #openstack-meeting21:19
ttxapi-v2-images-filtering, swift-tenant-specific-storage: unknown status, I suspect they are "not started" as well ?21:19
*** PotHix has joined #openstack-meeting21:19
bcwaldonyep, all not started21:19
bcwaldonI'm leaving things undefined until they have asignees21:19
bcwaldonthen I'm relying on the asignee to track their progress21:19
* ttx unfixes21:20
*** salv-orlando_ has joined #openstack-meeting21:20
bcwaldonit doesn't really matter either way :)21:20
ttxapi-v2-user-properties looks implemented to me ?21:20
*** salv-orlando has quit IRC21:21
ttxor is there more to it ?21:21
bcwaldonttx: I'll have to sync up with markwash_ on that, there will be another patch coming21:21
bcwaldonwe have enough to ship the feature, but more will get done21:21
ttxLooking now at the general Folsom plan at https://blueprints.launchpad.net/glance/folsom21:21
ttxAren't separate-client and glance-client-parity already implemented in folsom-1 ?21:21
bcwaldonno sir21:22
ttxwith the python-glanceclient split ?21:22
bcwaldonseparate-client isnt done till we have parity vfor v1 and a full v2 implementation21:22
bcwaldonat that point we can drop the old client from openstack/glance21:22
ttxoh, it's still in. I see.21:22
bcwaldonyeah, we created the new client21:22
bcwaldonneed to rally on that now21:23
ttxbcwaldon: Anything else you wanted to mention ?21:23
ttxDoes Glance participate to the Bugtriage day on June 7th ?21:23
bcwaldonthere aren't many bugs to triage, but I'll take all contributions21:23
ttxsounds good21:24
ttxQuestions on Glance ?21:24
markwash_bcwaldon: is v2 pagination different than v2 sorting?21:24
markwash_blueprint wise?21:24
bcwaldonas is filtering21:24
markwash_gotcha, I guess I was thinking we can't do the last links for pagination sensibly without sorting21:25
markwash_maybe that is a dependency21:25
bcwaldonok, there may be an order we need to document then21:25
markwash_anyway, nikhil and I will probably have energy to devote to the sorting part as well21:25
bcwaldonlets hook up offline21:25
*** nati_ueno has quit IRC21:25
gabrielhurley+1 to supporting all that in the API :-)21:25
ttx#topic Quantum status21:25
*** openstack changes topic to "Quantum status"21:25
bcwaldon+1 to your +1, sir21:26
ttxdanwent: hey21:26
ttx#link https://launchpad.net/quantum/+milestone/folsom-221:26
ttxI have a few questions:21:26
ttxLooks like v2-api-melange-integration is in the critical path, what's the status on this ?21:26
*** dwcramer has quit IRC21:26
ttxit's blocking a lot of other stuff21:26
danwentyes, its our key blocker right now.  talked to jkoelker this morning about it.  they are fully focused on it.21:26
ttxdo they have an ETA for it ?21:27
danwentwe're going to try and get some docs published on the API to unblock some of the other folks21:27
danwentthere's several days of work until its fully tested and can be proposed is my guess.21:27
danwentthey have it in a side branch that people have access to it though21:28
danwentso early integration is possible.21:28
ttxyes, some parallelization (through doc or looking into the branch) can't hurt21:28
ttxuse-common-cfg: could you confirm it's a Folsom goal ? Do you have an assignee for it ?21:29
danwentagreed.  I think everyone else who is blocked should at least be able to write-up their designs based on the API doc, so that's the goal.21:29
danwentI thought I updated that one this morning… one sec21:29
ttxoh, you have one now21:29
*** nati_ueno has joined #openstack-meeting21:29
danwenthaha.. that wasn't even a last minute refresh :P21:29
* ttx confirms it for Folsom21:29
ttxovs-api-v2-support: Folsom goal ?21:30
ttxfixed now21:30
ttxOK then, looking at the general Folsom plan at: https://blueprints.launchpad.net/quantum/folsom21:30
ttxYou have nothing targeted to folsom-3... is that because you want all goals complete by F2 ?21:30
ttxand use F3 for anything that gets deferred ?21:31
danwentthat is the goal.  f-2 is packed though, so the more realistic way to think about it is that F-3 will be overflow21:31
ttxok, that works21:31
danwentbut the good news is that we have people working on all of the important stuff in F-221:31
danwentthough odds are it won't all land in F-221:31
ttx#info Goal is to target all features to F2 and use F3 for overflow21:31
ttxdanwent: Anything else ?21:32
danwentother than mounds of code to be written?   nope :)21:32
ttxCan you confirm Quantum will participate to the Bugtriage day on June 7th ?21:32
ttxOther questions on Quantum ?21:32
*** edgarmagana has joined #openstack-meeting21:33
*** GheRivero_ has quit IRC21:33
ttx#topic Nova status21:33
*** openstack changes topic to "Nova status"21:33
ttxSo we don't have Vish, still on a beach somewhere sipping Mojitos21:33
ttxSo I'll monologue all the questions I have, that will make an interesting read for him when he comes back21:34
ttx#link https://launchpad.net/nova/+milestone/folsom-221:34
ttxthat said, if you know the answer, feel free to answer :)21:34
*** ozstacker has joined #openstack-meeting21:35
ttxgeneral-host-aggregates (joe gordon): not started ?21:35
ttxtrusted-messaging (russellb) and ec2-id-compatibilty (sina): unknown status, should i assume not started ?21:36
rustlebeetrusted-messaging is eric w21:36
rustlebeeno-db-messaging is me ... not started21:36
rustlebeei think trusted messaging is started, though21:36
rustlebeecan't speak much to progress, but started at least21:36
ttxquota-refactor (klmitch) : fully implemented, or more to come ?21:36
*** dolphm has quit IRC21:37
ttxLooking at the general Folsom plan now: https://blueprints.launchpad.net/nova/folsom21:37
*** nati_ueno has quit IRC21:37
ttxStill a few "High" priorities that are not targeted to any milestone...21:37
ttxso if you are the assignee and know when it should land, just update it:21:37
ttxhttps://blueprints.launchpad.net/nova/+spec/config-drive-v2 (unsassigned)21:38
ttxhttps://blueprints.launchpad.net/nova/+spec/delete-in-any-state (sina)21:38
*** semyazz has joined #openstack-meeting21:38
ttxhttps://blueprints.launchpad.net/nova/+spec/user-configurable-rbac (sleepsonthefloor)21:38
ttxewindisch: news on trusted-messaging ? Is work started there ?21:38
ttxjgriffith: around ?21:38
ttxjgriffith: how is Cinder going today ?21:39
ttxA bit more than a month to reach feature parity, still on track ?21:39
jgriffithGoing pretty good... Yes, I think we should hit that21:39
*** dprince has joined #openstack-meeting21:39
jgriffithCurrently the cinderclient is working well against nova21:39
ttxjgriffith: What's left to do ?21:39
jgriffithcinder itslef is 'working' but...21:39
*** semyazz has left #openstack-meeting21:40
jgriffithStill some problems getting devstack configured to point to the right comps21:40
*** markvoelker has joined #openstack-meeting21:40
jgriffithBig steps still to be done... Finish all of the seperation out of nova21:40
jgriffithcreate the client in cinder for nova to talkt o21:40
ttxjgriffith: so IIUC the important blueprints are:21:40
jgriffithThe attach piece is going to be tricky but I believe vishy has something in mind there21:41
ttxor is there more ?21:41
jgriffithThis generalizes all of it pretty well21:41
ttxok, will keep an eye on them21:41
ttxjgriffith: anything else you wanted to mention ?21:42
jgriffithNope, just plugging away.  Should have vishy and anotherjesse back later this week :)21:42
ttxAny Cinder question ?21:42
ttx#topic Horizon status21:43
*** openstack changes topic to "Horizon status"21:43
ttxohnoimdead: hey!21:43
ttx#link https://launchpad.net/horizon/+milestone/folsom-221:43
*** Guest11334 has quit IRC21:43
ttxohnoimdead: status looks good to me21:43
ttxAbout switch-to-cinder-client, there is a bit of a race condition here...21:43
ttx...as the cinder-client itself will be released at folsom-221:43
ttxI guess we'll have to do a pre-release somewhere ?21:44
ohnoimdeadyeah, that doesn't sound unreasonable21:44
ttxwe might get our act together and fix the client versioning/releases by then21:44
ohnoimdeadthat would be swell. ;)21:44
ttxanything you wanted to mention on folsom-2 progress ?21:45
ohnoimdeadfyi we also added https://blueprints.launchpad.net/horizon/+spec/readd-quantum-support and https://blueprints.launchpad.net/horizon/+spec/quantum-workflow-integration for re-introducing the quantum ui21:45
ohnoimdeadi want to not mention node.js21:45
gabrielhurleyohnoimdead: then why did you mention it?21:45
ohnoimdeadgabrielhurley: mention what?21:46
*** davidkranz has quit IRC21:46
*** adjohn has quit IRC21:46
gabrielhurleyohnoimdead: exactly.21:46
ttxthose two blueprints you mentioned... I suspect they will be added to folsom goal and targeted to some milestone in the near future ?21:46
ohnoimdeadyes, i was going to let devin target them21:47
ttxLooking at the Folsom general plan at: https://blueprints.launchpad.net/horizon/folsom21:47
*** bencherian has quit IRC21:47
ttxohnoimdead: There are 5 "High" priority blueprints in there that are not targeted yet21:47
*** ayoung has quit IRC21:47
ttxI suppose they will end up targeted to folsom-3 ?21:47
*** adjohn has joined #openstack-meeting21:48
*** adjohn has quit IRC21:48
ttx(unless shit happens ?)21:48
gabrielhurleythe asset-compression bluprint is actually in code review right now...21:48
ohnoimdeadyeah. at least one of those is actually done and just not updated :/21:48
ttxI kinda like it that way, rather than than the other way around.21:48
ttxi'll let you fix it :)21:49
gabrielhurleywe'll take a look at 'em and clean 'em up21:49
ttxohnoimdead: Anything else you wanted to not mention ?21:49
ohnoimdeadand bug devin to target them21:49
ohnoimdeadi mean, no thank you21:49
ttxohnoimdead: Horizon bugs are pretty well triaged, do you plan to participate to the Bugtriage day on June 7th anyway ?21:49
*** davidkranz has joined #openstack-meeting21:50
ohnoimdeadmight participate for a bit21:50
ttxCool. Other questions for Horizon ?21:50
ttx#topic Other Team reports21:51
*** openstack changes topic to "Other Team reports"21:51
ttxjaypipes, mtaylor: ?21:51
ttxoubiwann: ?21:51
oubiwannttx: nothing from me21:51
ttxAny other team lead with a status report ?21:51
*** gongys has joined #openstack-meeting21:52
ttx#topic Open discussion21:52
*** openstack changes topic to "Open discussion"21:52
ttxDoes anyone want to organize a realworld event on that June 7 bugtriage day ?21:52
med_jgriffith, I can set something up in Fort Collins if you want to come up....21:53
med_not sure there's any cinder triaging to do though.21:54
ttxheh, probably not yet21:54
jgriffithmed_: Sounds good to me21:55
ttxanyway, if you want to, just edit http://wiki.openstack.org/BugDays/20120607BugTriage to mention it21:55
jgriffithmed_: Actually there may be... if local folks are familiar with the client project_id settings etc21:55
jgriffithmed_: ttx thanks!21:55
ttxAnything else ? Anyone ?21:56
* med_ will look into it and contact jgriffith later.21:56
ttxok then21:56
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"21:57
openstackMeeting ended Tue May 29 21:56:59 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-29-21.01.html21:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-29-21.01.txt21:57
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-29-21.01.log.html21:57
*** jgriffith is now known as jgriffith_away21:57
*** ryanpetrello has quit IRC21:57
ttxdanwent: Vish should be back tomorrow to confirm your meeting time change21:57
danwentttx: k, thanks!21:57
*** MarkAtwood has joined #openstack-meeting21:58
*** matwood has joined #openstack-meeting21:59
danwenthi folks!22:00
*** gabrielhurley1 has joined #openstack-meeting22:01
mesteryYo yo yo!22:01
edgarmaganahi everybody!22:01
openstackMeeting started Tue May 29 22:01:32 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
SumitNaiksatamHi All!22:01
danwent#link agenda: http://wiki.openstack.org/Network/Meetings22:01
danwentSo, F-2 starts today: https://launchpad.net/quantum/+milestone/folsom-222:02
*** arosen1 has joined #openstack-meeting22:02
danwentwe have a bit of a bottleneck around items that require API v2.0 for F-222:02
*** gabrielhurley1 has quit IRC22:03
danwentjkoelker and team continue to make progress on the branch https://github.com/jkoelker/quantum/commits/melange22:03
danwentbut I think we're still at least a few days out from a potential merge.22:03
danwentjkoelker: around to give a more informed estimate?22:04
danwent_cerberus_ ?22:04
danwentSo to prevent other people from blocking, we're going to work on the detailed API docs22:04
*** gabrielhurley has quit IRC22:04
danwentgongys: you're probably waiting on the v2 stuff I assume?22:05
danwentfor https://blueprints.launchpad.net/quantum/+spec/new-cli?22:05
gongysI am waiting.22:05
danwentI think the api stuff is in good enough shape that you can get started.  I will work with you to help you understand the API.22:05
*** dprince has quit IRC22:05
*** davidkranz has quit IRC22:05
danwentmy guess is that having a client-lib and CLI will be important to have first, as others will need the clientlib to build on.22:06
*** heckj has quit IRC22:06
danwentI'm going to work with jkoelker and get at least the most common API flows documented later today/tomorrow.22:06
danwentthe etherpad is just too messy to make sense of anymore :)22:06
*** rustlebee has left #openstack-meeting22:07
danwentthe other two BPs that I think we must get done in F-2 are: https://blueprints.launchpad.net/quantum/+spec/improved-nova-quantum-integration22:07
danwentand https://blueprints.launchpad.net/quantum/+spec/quantum-dhcp (carlp + team)22:07
danwentif you're on one of those 4 BPs, I'll be hounding your for updates :)22:08
danwentThere's lots of other important stuff for F-2, but those have the most dependencies and complexity I believe.22:09
danwentIs anything major missing from the F-2 list of BPs?  If so, we should bring it up ASAP, as the release is probably overfull already.22:09
danwentI will comment that it would be great to have a few more core devs by the time F-2 is ending, as the reviewing load will be significant given everything that is targeted.22:10
PotHixdanwent: we'll work with carlp on the dhcp, just waiting for melange merge22:10
danwentPotHix: great.  have you already sent him email?  Since there wasn't a concrete design presented on this at the summit, this blueprint is the one that concerns me most for F-222:11
PotHixdanwent: yes, but the response was to wait the melange API22:11
PotHixso we can decide what to do22:12
jkoelkerdanwent: sorry was working on the tests22:12
danwentok.  once we send out basic docs on the v2 api, we can hopefully put together a design.22:12
danwentPotHix: would like to have a sketch by next monday, so i'll try to get you the API docs tomorrow.22:12
*** anderstj_ has quit IRC22:12
danwentjkoelker: no worries, probably a better use of your time.22:12
danwentjkoelker: was just looking for a general thought on when you might propose that API code.22:13
*** davidkranz has joined #openstack-meeting22:13
*** salv-orlando_ has quit IRC22:13
jkoelkerhrm, the biggest thing that still needs to be figured out is the ip allocation bits22:13
PotHixdanwent: cool! Include carlp on the discussion too22:13
jkoelkerbut if peeps don't care about working plugin and just want the APIRouter, then i can do that tomorrow ;)22:13
danwentjkoelker: yeah, doing that in a clever way is a bit tricky.22:14
danwentprobably good to have SOMETHING for IP allocation, though it could be something simple that we later improve on.22:14
jkoelkercuz the plugin api is done22:14
danwentwhat is the status of tests?  perhaps that's some place we could pull some more people in on.22:14
danwentif anyone can volunteer22:14
jkoelkeri got everything except for ports working22:14
danwentok, great.22:15
danwentso it sounds like we're pretty close.  I'm guessing a couple days and maybe propose by end of week?22:15
jkoelkerfiltering and other methods are all untested22:15
jkoelkerhave yet to run coverage on it to see what needs to be filled in22:15
danwentwhat do you mean by "other methods"22:15
*** davidkranz has quit IRC22:15
jkoelkerall the query string stuff22:15
jkoelkerlike show, filter, and verbose22:16
danwentah, ok.22:16
jkoelkertotally punted on those22:16
danwentI'd be fine merging those in separately, if you think that's best.22:16
jkoelkerjust got basic crud tested22:16
danwentup to you22:16
jkoelkeri'm good for whatever22:16
danwentI'd rather get the merge at least started soon.22:17
danwentthat way people can review + get up to speed on the new API at the same time.22:17
SumitNaiksatam+1 for phased approach22:17
gongysand we will be able to help test22:17
jkoelkeryea i ahve the github issues to break up the merge22:18
*** salv-orlando has joined #openstack-meeting22:18
jkoelkerthe biggest question is do ya'll want the v2 api in without the SamplePlugin working?22:18
*** AlanClark has quit IRC22:18
jkoelkerif so i can do that like tommorrow22:18
jkoelkerotherwise its going to be a while22:18
jkoelkersince we're finding bugs with the implementation when we are writing the tests ;)22:18
jkoelkerso its a bit of a chicken and the egg22:19
salv-orlandojkoelker: which plugin do unit tests for API v2 use?22:19
danwentsalv-orlando: we created a basic DB/sample plugin22:19
* cdub is surprised SamplePlugin isn't done as part of v2 for testing22:19
jkoelkeronly the V2 sample plugin22:19
jkoelkerno other plugin is compatible wiht the V2 plugin api22:19
danwentcdub: I believe it is...22:19
jkoelkercdub it is22:19
jkoelkerthat is the question22:20
jkoelkerdo you want to wait on the v2 spec for the sample plugin22:20
jkoelkeror do you want it now22:20
danwentjkoelker: I tend to think we should wait for the unit tests to be running to merge22:20
jkoelkerwell i can fake out a plugin really easy22:20
danwentsince the only think you can to with the routers alone is look at the code, and we already have access to the branch.22:20
danwentah, you mean write a really simple sample plugin?22:21
danwentis that what you mean by "fake out a plugin"?22:21
jkoelkerno i mean use mock to return the exact data22:21
*** reed has quit IRC22:22
danwentah, for unit tests only you mean.  I suspect this gets back to the "these unit tests aren't unit tests" comment :P22:22
jkoelkeryea cuz that's the thing22:22
jkoelkerthe v2 api is just a wrapper around getattr22:22
jkoelkerit really doesn't do much22:23
danwentI think there would be value in that, if for no other reason than phasing the merge.22:23
jkoelkerso if we want tests on just it, then that's easy22:23
jkoelkerwell here's the thing22:23
jkoelkeri'd rather do one or the other22:23
jkoelkerbecause no one will use the sample plugin22:23
danwentisn't this what we talked about on the github issue?  That the sample plugin would really be the dbbase_plugin, which others could subclass to implement their plugins?22:24
jkoelkeryea, but then its totally not my problem ;)22:25
jkoelkerthat's the plugin implementor's problem22:25
*** troytoman is now known as troytoman-away22:25
danwentI think that's the right long-term direction in that it makes our unit tests more like real unit tests.22:26
danwentand separates the testing of the api layer from the testing of the plugin beneath it.22:26
jkoelkersweet, any objections?22:26
danwentI'm fine with it.22:27
jkoelkerrock on I'll run with that22:27
danwentwhat is to become of the DB-base code then?22:27
jkoelkerit will still be there22:27
danwentDB-plugin-base?  target for a separate merge with separate unit tests?22:27
jkoelkeri think whoever uses the ovs-plugin might be able to use it as a base22:28
*** davidkranz has joined #openstack-meeting22:28
danwentjkoelker: yeah.  I think its worth keeping as a separate class, so that multiple plugins can use it, but I'm ok with it being a separate merge.  We'll have to create some new unit testing infrastructure around it though.22:29
danwentbut as I said, i think that's a better long term direction.22:29
jkoelkeri'll work on that tomorrow22:29
danwentok, sounds good.22:29
jkoelkerand see if i can get someone to pull out the authn stuff and submit that22:30
jkoelkeras well as the db models22:30
danwentjkoelker: db models would be separate merge from db-plugin?22:30
jkoelkercould be22:30
danwenti would see them as coupled, but don't feel too strongly.22:31
jkoelkersome of the cleanup in the db/api is badly needed anyway22:31
jkoelkerand using declarative_base properly22:31
danwentok, sounds good.22:31
danwentok, so back onto the agenda :)22:32
danwentI think we're done with F-2 discussion, so I'll move on to community topics22:32
danwent#topic community topics22:32
*** openstack changes topic to "community topics"22:32
danwent#info we are planning on moving team meetings to monday 2100 UTC starting next week.22:32
danwentwe are planning on using this same channel, but I need to confirm with Vish that the meeting scheduled in that slot no longer actually meets.22:33
danwentvish is on vacation, but will be back soon, so look for a confirmation on the netstack list later this week.22:33
danwent#info quantum is participating in the "bug triage day" june 7th:  http://wiki.openstack.org/BugDays/20120607BugTriage and http://wiki.openstack.org/BugTriage22:34
*** mdomsch has quit IRC22:34
danwent#topic open discussion22:34
*** openstack changes topic to "open discussion"22:34
gongysabout authn(z) on server side, who is on that?22:34
danwentor did jkoelker and I put everyone to sleep :)22:35
danwentgongys: that is kevin mitchell from Rackspace22:35
danwentjkoelker: do you know his handle?22:35
SumitNaiksatamdanwent: is there a "work-in-progress" branch for https://blueprints.launchpad.net/quantum/+spec/quantum-l3-fwd-nat?22:35
danwentSumitNaiksatam: not yet… I'm working on it though22:36
jkoelkerits usually Vek, but he doesn't look like he's on22:36
*** blamar has quit IRC22:36
danwentjkoelker: there's a branch with some of the authz stuff right, right?22:36
jkoelkerthere is22:37
jkoelkerit was just updated this morning22:37
jkoelkerlet me get the link22:37
danwentthis one? https://github.com/jkoelker/quantum/commits/melange-authz22:37
*** rafaduran has quit IRC22:37
*** davidkranz has quit IRC22:37
*** maoy has joined #openstack-meeting22:37
gongysIt is will be in f-2?22:37
gongysWill it be in f-2?22:38
jkoelkerits stacked ontop of the v2 api branch22:38
garykhttps://blueprints.launchpad.net/quantum/+spec/use-common-cfg - added support for linux bridge and ovs. do we want for the quantum service?22:38
jkoelkerI have yet to go through it and see what it all does,22:38
danwentgongys: it is targeted for f-2 and actively being worked on, so I suspect it will land in f-222:38
jkoelkergongys I think that is the hope22:38
danwentgaryk: yes please :P22:38
jkoelkergaryk: yes please22:39
jkoelkerthe quantum/common/config is killing me22:39
garykjoin the club22:39
jkoelkerits a party!22:39
jkoelkeri almost added cfg support for the v2 api22:40
jkoelkerbut then realized the hozer of only the v2 using it22:40
danwentok, great.  any other open discussion?22:40
cdubgaryk: did you see markmc's recent update on that topic?22:40
*** dwcramer has joined #openstack-meeting22:40
gongysnova will call new quantum api v2.0 in f-2?22:40
garykcdub: yes22:40
cdubgaryk: cool22:40
danwentgongys: yes, that is tr3buchet's work.22:41
garykis there anyway of nova knowing which plugin is being used?22:42
danwenthe's had most of it done for a while, waiting on the v2.0 api to finalize before completing it, I believe.  this is the patch I mentioned in the email today, as it will mean you do not need nova-network when using quantum.22:42
gongysF-2 will be a big change then.22:42
danwentgaryk: I would argue that nova shouldn't know.  perhaps it would want to know what type of vif-plugging is supported, but not necessarily what plugin.22:42
danwentgongys: yup :)22:42
danwentwe're trying to get disruptive things in early in the cycle.22:43
*** jgriffith_away is now known as jgriffith22:43
danwentgaryk: what is your use case?22:43
garykdanwent: the ovs keeps attachment id's but gw name.22:43
tr3buchetdanwent: that's exactly right. no sense having to update it over and over22:43
danwentgaryk: let's chat about this after mtg?22:44
gongysDan: I think  vif-plugging is plugin term on the nova side.22:44
danwentor tomorrow if you're tired22:44
garykdanwent: great22:44
danwentok, any other issues we need to discuss, or can we let most people go?22:44
danwentok, thanks folks.  keep hacking, see you next week :)22:45
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"22:45
openstackMeeting ended Tue May 29 22:45:07 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-29-22.01.html22:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-29-22.01.txt22:45
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-29-22.01.log.html22:45
med_tx danwent22:45
danwentbye salv-orlando !22:45
s0miktake care folks!22:45
markvoelker'night all22:45
danwentby folks22:45
garykdanwent: you have a few minutes to go over the essex stable?22:45
*** markvoelker has quit IRC22:45
*** mattray has quit IRC22:46
danwentgaryk: sure.  but i first want to make sure I understand your question about nova + plugins22:46
garykshould we take it to openstack-dev or do it here?22:46
*** edgarmagana has quit IRC22:47
* salv-orlando lurkes in the background 22:47
danwentgaryk: up to you, as I know its late for you.22:47
garykdanwent: i can give it a bash.22:48
garykdanwent: ovs stores the attachement id. it does not store the gw id. this too can be stored. i sent a mail last week. i'll try and did it up22:49
*** WilliamHerry has joined #openstack-meeting22:49
danwentah, yeah.  let me check the code quickly to get back up to speed.22:50
danwentgaryk: yes.  right now nova does not general a true attachment-id for gateway interfaces, it just uses the device name.22:52
danwentthis is the code in nova-network, right?22:52
*** sdake_pto is now known as sdake22:52
garykdanwent: http://fpaste.org/NNYE/22:52
garykdanwent: correct22:53
danwentyes, I remember the issue now22:53
*** davidkranz has joined #openstack-meeting22:53
danwentyes, using the full UUID is a more proper solution.22:54
garykcan we context switch to the essex stable?22:55
danwentthat said, this code will be being moved to quantum in F-222:55
danwentor early F-322:55
garykok, great22:55
danwentso probably best to make the change then.22:55
danwent(this vif-plugging code will probably end up in quantum/agent/linux as a library22:55
danwentok, sure stable/essex22:56
danwentyour list looked good.  one of the changes only applied to folsom though.22:56
danwentone sec22:56
uvirtbotLaunchpad bug 1000887 in quantum "Nova/Quantum Integration broken due to typo in serializer" [Critical,Fix released]22:56
danwenti think this fixes something that was only broken in Folsom22:56
*** dtroyer is now known as dtroyer_zzz22:57
danwentbut there's actually another QuantumManager fix that we do need to backport22:57
garyki am a bit confused about the git commands i need to use. if you have an example on how you check out the version then i can start to get it up and running22:57
danwentk, will send you an email with the right git command22:58
garykgreat thanks! i am going to crash now22:58
*** anderstj has joined #openstack-meeting22:59
danwenthehe, ok.  will send you email soon.  night23:00
*** jkoelker has left #openstack-meeting23:00
garykthanks - i'll be in the office in a few hours :)23:00
*** SumitNaiksatam has quit IRC23:01
*** jkoelker has joined #openstack-meeting23:01
*** dolphm has joined #openstack-meeting23:05
*** randomubuntuguy has quit IRC23:13
*** ecarlin has joined #openstack-meeting23:27
*** sdake is now known as sdake_pto23:28
*** matwood has quit IRC23:31
*** MarkAtwood has quit IRC23:36
*** matwood has joined #openstack-meeting23:36
*** MarkAtwood has joined #openstack-meeting23:36
*** edygarcia has quit IRC23:37
*** matwood has quit IRC23:38
*** matwood has joined #openstack-meeting23:42
*** dolphm has quit IRC23:44
*** dtroyer_zzz is now known as dtroyer23:47
*** WilliamHerry has quit IRC23:49
*** joearnold has quit IRC23:58

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