Tuesday, 2012-07-03

*** anniec has joined #openstack-meeting00:07
*** anniec_ has joined #openstack-meeting00:10
*** nati_ueno has joined #openstack-meeting00:11
*** salv-orlando has left #openstack-meeting00:11
*** anniec has quit IRC00:14
*** anniec_ is now known as anniec00:14
*** somik has joined #openstack-meeting00:22
*** s0mik has quit IRC00:22
*** somik is now known as s0mik00:22
*** reed_ has quit IRC00:29
*** edgarmagana has quit IRC00:31
*** joearnold has quit IRC00:36
*** dtroyer is now known as dtroyer_zzz00:38
*** ryanpetr_ has joined #openstack-meeting00:43
*** ryanpetrello has quit IRC00:46
*** anderstj has joined #openstack-meeting00:47
*** s0mik has quit IRC00:51
*** cp16net is now known as cp16net|away00:53
*** ryanpetr_ has quit IRC01:00
*** Gordonz has joined #openstack-meeting01:04
*** johnpostlethwait has quit IRC01:09
*** nati_ueno has quit IRC01:10
*** nati_ueno has joined #openstack-meeting01:11
*** nati_uen_ has joined #openstack-meeting01:12
*** cp16net|away is now known as cp16net01:13
*** nati_ueno has quit IRC01:15
*** nati_uen_ has quit IRC01:16
*** nati_ueno has joined #openstack-meeting01:17
*** reed_ has joined #openstack-meeting01:18
*** ryanpetrello has joined #openstack-meeting01:19
*** nati_ueno has quit IRC01:21
*** PotHix has quit IRC01:29
*** ryanpetrello has quit IRC01:32
*** anniec has quit IRC01:34
*** rnirmal has quit IRC01:35
*** mnaser has quit IRC01:42
*** adjohn has quit IRC01:47
*** jdurgin has quit IRC01:56
*** ryanpetrello has joined #openstack-meeting02:01
*** novas0x2a|laptop has quit IRC02:20
*** danwent has quit IRC02:23
*** reed_ has quit IRC02:25
*** ayoung has quit IRC02:27
*** ryanpetrello has quit IRC02:28
*** dwcramer has quit IRC02:28
*** adjohn has joined #openstack-meeting02:31
*** ryanpetrello has joined #openstack-meeting02:32
*** ryanpetrello has quit IRC02:33
*** mnaser has joined #openstack-meeting02:42
*** rnirmal has joined #openstack-meeting02:46
*** littleidea has quit IRC03:00
*** adjohn has quit IRC03:05
*** Gordonz has quit IRC03:05
*** zhhuabj has joined #openstack-meeting03:06
*** anniec has joined #openstack-meeting03:08
*** anniec_ has joined #openstack-meeting03:10
*** Gordonz has joined #openstack-meeting03:11
*** anniec has quit IRC03:13
*** anniec_ is now known as anniec03:13
*** Gordonz has quit IRC03:23
*** kindaopsdevy has joined #openstack-meeting03:23
*** adjohn has joined #openstack-meeting03:40
*** adjohn has quit IRC03:41
*** littleidea has joined #openstack-meeting03:43
*** anniec has quit IRC03:54
*** mnaser has quit IRC03:55
*** kindaopsdevy has quit IRC03:56
*** anniec has joined #openstack-meeting04:00
*** matiu has quit IRC04:44
*** adjohn has joined #openstack-meeting04:45
*** novas0x2a|laptop has joined #openstack-meeting04:47
*** markmcclain has quit IRC04:55
*** adjohn has quit IRC04:57
*** anniec has quit IRC04:59
*** matiu has joined #openstack-meeting05:01
*** garyk has quit IRC05:02
*** danwent has joined #openstack-meeting05:05
*** carlp has joined #openstack-meeting05:41
*** carlp has quit IRC05:45
*** littleidea has quit IRC05:47
*** garyk has joined #openstack-meeting05:49
*** carlp has joined #openstack-meeting05:51
*** rnirmal_ has joined #openstack-meeting05:52
*** rnirmal_ has quit IRC05:52
*** rnirmal has quit IRC05:54
*** carlp has quit IRC05:59
*** rohitk has joined #openstack-meeting06:12
*** carlp has joined #openstack-meeting06:16
*** carlp has quit IRC06:21
*** anderstj has quit IRC06:31
*** dwcramer has joined #openstack-meeting06:42
*** carlp has joined #openstack-meeting06:54
*** carlp has quit IRC06:59
*** sdake has quit IRC07:15
*** sdake has joined #openstack-meeting07:18
*** ijw has joined #openstack-meeting07:49
*** ijw has quit IRC07:51
*** ijw has joined #openstack-meeting07:52
*** ttrifonov_zZzz is now known as ttrifonov08:27
*** ijw has quit IRC08:28
*** ijw has joined #openstack-meeting08:28
*** ijw1 has joined #openstack-meeting08:30
*** ijw has quit IRC08:33
*** darraghb has joined #openstack-meeting08:40
*** carlp has joined #openstack-meeting08:42
*** carlp has quit IRC09:10
*** ijw1 has quit IRC09:17
*** carlp has joined #openstack-meeting09:17
*** ijw has joined #openstack-meeting09:17
*** carlp has quit IRC09:21
*** rkukura has quit IRC09:33
*** Mandell has quit IRC09:33
*** carlp has joined #openstack-meeting09:39
*** gongys has quit IRC09:42
*** carlp has quit IRC09:43
*** zhhuabj has quit IRC09:59
*** ijw has quit IRC10:46
*** ijw has joined #openstack-meeting10:47
*** carlp has joined #openstack-meeting11:01
*** carlp has quit IRC11:05
*** rkukura has joined #openstack-meeting11:18
*** glenc_ has quit IRC11:19
*** glenc has joined #openstack-meeting11:20
*** milner has joined #openstack-meeting11:27
*** ncode has joined #openstack-meeting11:53
*** ncode has joined #openstack-meeting11:53
*** mnaser has joined #openstack-meeting11:59
*** markvoelker has joined #openstack-meeting12:05
*** ijw has quit IRC12:08
*** carlp has joined #openstack-meeting12:21
*** troytoman-away is now known as troytoman12:21
*** carlp has quit IRC12:25
*** mnaser has quit IRC12:27
*** anniec has joined #openstack-meeting12:27
*** anniec_ has joined #openstack-meeting12:27
*** hggdh has quit IRC12:30
*** anniec has quit IRC12:31
*** anniec_ is now known as anniec12:31
*** markmcclain has joined #openstack-meeting12:40
*** hggdh has joined #openstack-meeting12:40
*** markmcclain has quit IRC12:45
*** oubiwann has quit IRC12:50
*** dhellmann_ has joined #openstack-meeting12:52
*** dhellmann_ has quit IRC12:52
*** dhellmann has quit IRC12:55
*** salv-orlando has joined #openstack-meeting13:03
*** mnaser has joined #openstack-meeting13:10
*** martines has joined #openstack-meeting13:12
*** lzyeval has joined #openstack-meeting13:19
*** mnaser has quit IRC13:19
*** ayoung has joined #openstack-meeting13:19
*** mnaser has joined #openstack-meeting13:20
*** dprince has joined #openstack-meeting13:32
*** dwcramer has quit IRC13:33
*** markmcclain has joined #openstack-meeting13:38
*** oubiwann has joined #openstack-meeting13:41
*** garyk has quit IRC13:43
*** mnaser has quit IRC13:45
*** littleidea has joined #openstack-meeting13:47
*** dwcramer has joined #openstack-meeting13:47
*** mnaser has joined #openstack-meeting13:47
*** mestery has joined #openstack-meeting13:48
*** littleidea has quit IRC13:50
*** mestery has quit IRC13:52
*** ryanpetrello has joined #openstack-meeting13:54
*** oubiwann has quit IRC13:58
*** troytoman is now known as troytoman-away14:09
*** Mandell has joined #openstack-meeting14:11
*** anderstj has joined #openstack-meeting14:15
*** sandywalsh has joined #openstack-meeting14:19
*** Mandell has quit IRC14:22
*** littleidea has joined #openstack-meeting14:26
*** troytoman-away is now known as troytoman14:29
*** dendrobates is now known as dendro-afk14:30
*** dendro-afk is now known as dendrobates14:31
*** dendrobates has joined #openstack-meeting14:31
*** mnaser has quit IRC14:31
*** mnaser has joined #openstack-meeting14:33
*** oubiwann has joined #openstack-meeting14:33
*** dhellmann has joined #openstack-meeting14:33
*** novas0x2a|laptop has quit IRC14:33
*** littleidea has quit IRC14:40
*** salv-orlando has quit IRC14:40
*** salv-orlando has joined #openstack-meeting14:41
*** Gordonz has joined #openstack-meeting14:41
*** dhellmann has quit IRC14:46
*** ryanpetr_ has joined #openstack-meeting14:46
*** dhellmann has joined #openstack-meeting14:46
*** ryanpetrello has quit IRC14:46
*** mestery has joined #openstack-meeting14:50
*** jgriffith has joined #openstack-meeting14:50
*** Gordonz has quit IRC14:53
*** Gordonz has joined #openstack-meeting14:54
*** matwood has joined #openstack-meeting14:57
*** danwent has quit IRC14:57
*** mnewby has joined #openstack-meeting15:03
*** rnirmal has joined #openstack-meeting15:05
*** anderstj has quit IRC15:07
*** lzyeval has quit IRC15:08
*** cp16net is now known as cp16net|away15:12
*** dwcramer has quit IRC15:14
*** zigo has joined #openstack-meeting15:15
*** dprince has quit IRC15:18
*** dhellmann has quit IRC15:23
*** ryanpetr_ has quit IRC15:24
*** oubiwann has quit IRC15:25
*** markmcclain has quit IRC15:25
*** dwcramer has joined #openstack-meeting15:26
*** danwent has joined #openstack-meeting15:27
*** mestery_ has joined #openstack-meeting15:32
*** mestery has quit IRC15:33
*** s0mik has joined #openstack-meeting15:33
*** mestery_ has quit IRC15:38
*** mnaser has quit IRC15:39
*** mnaser has joined #openstack-meeting15:41
*** sandywalsh_ has joined #openstack-meeting15:45
*** sandywalsh has quit IRC15:46
*** ozstacker has quit IRC15:49
*** dprince has joined #openstack-meeting15:55
*** uvirtbot has quit IRC15:59
*** uvirtbot has joined #openstack-meeting16:01
*** mnaser has quit IRC16:05
*** joearnold has joined #openstack-meeting16:14
*** heckj has joined #openstack-meeting16:16
*** ryanpetrello has joined #openstack-meeting16:17
*** markmcclain has joined #openstack-meeting16:17
*** kindaopsdevy has joined #openstack-meeting16:18
*** rohitk has quit IRC16:18
*** oubiwann has joined #openstack-meeting16:19
*** dhellmann has joined #openstack-meeting16:20
*** garyk has joined #openstack-meeting16:20
*** littleidea has joined #openstack-meeting16:33
*** anderstj has joined #openstack-meeting16:36
*** ozstacker has joined #openstack-meeting16:41
*** mnewby has quit IRC16:44
*** Mandell has joined #openstack-meeting16:46
*** zigo has quit IRC16:57
*** anniec has quit IRC17:04
*** zigo has joined #openstack-meeting17:09
*** PotHix has joined #openstack-meeting17:10
*** lloydde has joined #openstack-meeting17:12
*** nati_ueno has joined #openstack-meeting17:14
*** nati_uen_ has joined #openstack-meeting17:16
*** torgomatic has joined #openstack-meeting17:17
*** nati_ueno has quit IRC17:19
*** sandywalsh_ has quit IRC17:20
*** jdurgin has joined #openstack-meeting17:25
*** sandywalsh has joined #openstack-meeting17:29
*** darraghb has quit IRC17:38
*** danwent_ has joined #openstack-meeting17:39
*** dwcramer has quit IRC17:40
*** danwent has quit IRC17:42
*** danwent_ is now known as danwent17:42
*** kindaopsdevy_ has joined #openstack-meeting17:43
*** mnewby has joined #openstack-meeting17:45
*** nati_ueno has joined #openstack-meeting17:45
*** kindaopsdevy has quit IRC17:46
*** kindaopsdevy_ is now known as kindaopsdevy17:46
*** nati_uen_ has quit IRC17:46
*** anniec has joined #openstack-meeting17:47
*** jakedahn_zz is now known as jakedahn17:48
*** sacharya has joined #openstack-meeting17:55
*** adjohn has joined #openstack-meeting17:55
*** dwcramer has joined #openstack-meeting17:56
*** dolphm has joined #openstack-meeting17:56
*** atiwari has joined #openstack-meeting17:58
*** jrouault has joined #openstack-meeting17:59
dolphmo/18:00
heckjfolks around for the keystone meeting?18:00
heckjo/18:00
*** rafaduran has joined #openstack-meeting18:00
heckjLooks like it's just you and me this time :-)18:01
*** tw__ has joined #openstack-meeting18:01
heckj#startmeeting18:01
openstackMeeting started Tue Jul  3 18:01:24 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
heckjHow's things?18:01
*** nati_uen_ has joined #openstack-meeting18:01
*** kevin-lewis-9 has joined #openstack-meeting18:01
heckj#topic folsom-2 milestone18:01
*** openstack changes topic to "folsom-2 milestone"18:01
heckj#link https://launchpad.net/keystone/+milestone/folsom-218:02
heckjdolphm: you and I have a few reviews outstanding - otherwise we're in good shape for the F2 release milestone18:02
liemmno/18:03
dolphmheckj: i'll take another pass this afternoon18:03
*** dwalleck has joined #openstack-meeting18:03
heckjayoung: around?18:03
dolphmis jenkins having a bad day again? :-/18:04
*** nati_ueno has quit IRC18:04
*** kevin-lewis-9 has quit IRC18:05
heckjoh, probably18:05
*** sleepsonzzz is now known as sleepsonthefloor18:05
*** Haneef has joined #openstack-meeting18:05
*** kevin-lewis-9 has joined #openstack-meeting18:05
heckjReviews that need someone other than Dolph or I looking at this for the F2 release: https://review.openstack.org/#/c/8909/, https://review.openstack.org/#/c/9182/18:05
heckjboth for F2 milestone18:05
heckj#link https://review.openstack.org/#/c/9182/18:06
heckj#link https://review.openstack.org/#/c/8909/18:06
heckj#topic hot issues18:06
*** openstack changes topic to "hot issues"18:06
*** tongli has joined #openstack-meeting18:07
heckjAny new issues? Hot topics?18:07
liemmnHeckj, when is the v3 API "frozen"?18:07
ayoung\)/18:07
ayoungfinally got the SSL Cert generation into Keystone18:08
heckjliemmn: I'm going through the existing feedback now - going to take one more cut at it, and then it'll be solid enough to start development against18:08
heckjI'd hoped to do that this past weekend, but ended up sleeping through most of it18:08
liemmnsounds good :)18:08
heckjayoung: yeah!!!18:08
ayoungheckj, do we have a summary sheet of the changes?18:08
dolphmready for implementation != frozen, correct?18:08
ayoungI have to present on it, and am lazy18:08
heckjliemmn: I do expect to leave the spec "open" per bcwaldon's suggestion to allow us to revise as we run into implementation issues18:09
heckjayoung: #link https://launchpad.net/keystone/+milestone/folsom-218:09
dolphmheckj: is that what glance did?18:09
heckjdolphm: yeah18:09
*** tim_chan has joined #openstack-meeting18:09
heckjdolphm: Brian said it made a huge difference for their work as they sussed out deeper issues18:09
dolphmheckj: i can imagine :)18:09
ayoungshould I add in https://bugs.launchpad.net/keystone/+bug/994860  ?18:10
uvirtbotLaunchpad bug 994860 in keystone "Keystone middleware auth_token assumes top level URL when making http connection" [Medium,In progress]18:10
liemmnayoung, there were some feedback on making PKI optional... That is still in the plan right?18:10
ayoungliemmn, I don't want it optional.18:10
ayoungI'd rather have it out there, have everyone beat on it18:10
ayoungand if it is a real problem,  we roll back18:10
jrouaultbut some implementers will not use PKI18:11
ayoungthere are 2 parts to it:   token generation and token validation18:11
ayoungthe old style validation *can* be done with the new tokens18:11
heckjayoung: I think it's only pending unit tests18:11
ayoungbut vice versa is not18:11
ayoungheckj, my ticket?  Yes,  I will get unit tests.  I meant should I add that bug to the API blueprint?18:11
ayoungjrouault, why would they not use PKI?18:12
heckjayoung: not worried too much about it either way -18:12
dolphmheckj: ayoung: can we "demote," for example, the token validation call to an official extension, if it's not necessary for PKI and PKI is core?18:12
ayoungdolphm, I don't think that is wise18:13
liemmnayoung, so...  if someone is using non PKI and going through to Keystone backend to do a validation (and have no cert), how would that work with PKI enforced?18:13
jrouaultayoung: because they have implementations running today that dont require it18:13
heckjdolphm, ayoung: I don't want to demote anything at this point18:13
ayoungI think PKI will give us many new features.  Probably most important is Federation18:13
ayoungliemmn, token is generated using PKI.  That means that it can be validated with the signing cert.  But it can also be validated the old way:  by asking Keystone directly.18:14
ayoungI am going to post another patch shortly that is just the token generation18:14
ayoungthe vaolidation will be a separate patch18:14
liemmnCool, as long as we can still have an option to ask Keystone to validate the token, should the signed cert is not there, I think that should be ok18:15
ayoungdolphm, the thing is,  token validation without calling to keystone is pretty much the reason for having PKI in the first place.  Otherwise,  we've just implemented a slightly more expensive token generation scheme18:15
*** tim_chan has quit IRC18:15
ayoungliemmn, signed cert is fetched on demand18:16
jrouaultwhich is why it should be optional whether the token is signed18:16
liemmnI mean, if a token is not signed, then we have the option to ask Keystone to validate the token as before...18:16
ayoungOne thing that is currently missing, and I am tempted to try and add before submitting the token generation is the ID of the Keystone server18:16
rafaduranayoung: PKI  will be part of just v3 API or it will land into master before it?18:16
dolphmayoung: that's why i don't like it remaining in the "core" api18:17
ayoungrafaduran, it makes no changes to the API and will land before it18:17
heckjrafaduran: he's aiming to have it in prior to V3 api - in progress now18:17
dolphmayoung: it's just bloat if it's not recommended18:17
dolphmgranted, it should be kept around18:17
ayoungdolphm, this is based on the lessons learned in other IdM systems.  Probably most notably is Kerberos.  THe biggest difference between V4 and V5 is the way that service tickets are validated,  which is what this is echoing18:18
jrouaultanother reason to support the current token scheme in conjunction to the PKI scheme is to support token revocations18:19
*** tchan_ has joined #openstack-meeting18:19
ayoungIt should have a significant impact in decreasing the amount of network traffic18:19
jrouaultnot arguing that... just asking that is be optional18:20
jrouaultyou configure if you want PKI or not18:20
heckjwe do need it to work side-by-side with the legacy mechanisms and not break the legacy mechanisms18:20
heckj#topic keystone-core18:21
*** openstack changes topic to "keystone-core"18:21
heckjSwitching topics - sounds like that one's tapped out18:21
heckjI'm proud to announce the addition of ayoung to keystone-core18:21
dolphmawesome18:21
dolphmayoung: grats18:21
heckjI'll send a note out to the list shortly with the same18:22
ayoungthanks18:22
heckjayoung: awesome work, thank you - and here's more to do18:22
heckj:-)18:22
heckj#topic open discussion18:23
*** openstack changes topic to "open discussion"18:23
*** rnirmal has quit IRC18:23
ayoungum...one last thing on the PKI tokens...I was planning on changing the behavior of auth_token middleware,  but I could also privde a different middleware  for it....I could do something like check the length of the token,  and if it is short, assume it is a hashed (current style) token,  but if it is longer than some threshold, assume it is PKI signed.  Question then is do we want to make people 1) default to phone home and  enable18:24
ayoung signing validation or 2)  default to PKI validation and explicelty enable phone home?18:24
ayoungMy thought is that we should push the new functionality to ensure that people test it and report issues18:24
ayoungwe can provide the fall back...so you would have to explicitly set the middleware on, say glance18:25
ayoungI'd hoped to avoid doing anything along those lines....18:25
*** anniec has quit IRC18:25
*** anniec has joined #openstack-meeting18:26
jrouaultso you will then support unsigned tokens?18:26
dolphmayoung: shouldn't you try to decrypt in middleware, and if that fails, try phoning home if phoning home is enabled?18:26
ayoungjrouault, only under duress :)18:26
dolphmayoung: otherwise immediately fail?18:26
heckjayoung: extending the current auth_token middleware should be fine as long as it doesn't get too complex in there. kind of a judgement call though.18:26
dolphmayoung: fail = reject authentication18:26
liemmnayoung, you could leave the auth_token as is to provide the default behavior, and create a new filter before auth_token to handle PKI tokens.  If the tokens are not PKI, then let them fall to the auth_token for legacy support.18:27
jrouault+118:27
ayoungliemmn, but that makes a configuration nightmare18:27
liemmnjust another filter in the WSGI pipeline...18:27
*** zigo has quit IRC18:27
ayoungliemmn, I object to the word "just"18:27
heckjmeans we have to change a bunch of client pipelines18:27
dolphmliemmn: that doesn't sound like it will work at all -- auth_token will filter out incoming authentication claims as-is18:28
ayoungit means that we have to change devstack,  plus any tool like puppet or chef...18:28
ayounghuman sacrifice,  dogs and cats. living together18:28
heckjheh18:28
dolphmliemmn: and always attempt token validation18:28
ayoungmasss hysteria18:28
ayoungHere's a thought.  Let me get the token generation code through review and into the repo,  and let people beat on it for a while.18:29
liemmnwell.. the alternative is to have auth_token do it all... that's fine too, but IMHO, I am just trying to do separation of concerns... did not think about deployment18:29
ayoungMeanwhile,  we can go through the auth_token code with a fine tooth comb,  deal with corner cases etc18:29
heckjayoung: that sounds like a good take on it18:30
jrouaulti would like to conclude on whether PKI usage will be optional...18:30
ayoungI'd like to make it default18:30
ayoungbut provide an override to turn it off?18:30
dolphmjrouault: are you asking about the api or keystone's implementation?18:30
jrouaultyes, I would like to turn it off and use the v2.0 mechanism18:31
heckjjrouault: We will support that18:31
dolphmi'd vote for optional in API, and required (or at least on by default) in keystone18:31
jrouaultdoph: my understanding is ayoung wanted to force all tokens to be signed... I don't want to do that if I am using the v2 mechansim18:31
jrouaultof validation18:31
jrouaultit is unnecessary overhead18:31
*** novas0x2a|laptop has joined #openstack-meeting18:32
dolphmjrouault: still not sure if you're referring to the v2 api or v2 implementation?18:32
ayoungjrouault, out of curiousty, why?  I mean, I understand the revokation issue,  but beyond that,  what issue do you see with PKI?18:32
*** ryanpetrello has quit IRC18:32
*** zigo has joined #openstack-meeting18:32
*** kindaopsdevy_ has joined #openstack-meeting18:32
jrouaultif I request a token from Keystone configured for no PKI, i should get a token back that is not signed18:32
ayoungjrouault, are you worried about doing a rolling upgrade?18:33
dolphmjrouault: as a service consumer, does it matter?18:33
*** Haneef has quit IRC18:33
jrouaultno, we have use cases where a signed token will just cause us greif18:33
dolphmjrouault: example?18:34
ayoungjrouault, the token is opaque.  To the end user, the only difference will be the length18:34
ayoungand they should not really even care about that18:35
jrouaultand that will cause problems for other services we have18:35
dolphmjrouault: example?18:35
*** ryanpetrello has joined #openstack-meeting18:35
*** kindaopsdevy has quit IRC18:35
*** kindaopsdevy_ is now known as kindaopsdevy18:35
heckjjrouault: can you expand on the "grief" and what causes it?18:37
dolphmjrouault: i'm not sure how we're supposed to address issues that you're not sharing or justifying18:37
jrouault1. we have other services that consume tokens that have problems with the length18:38
ayoungOK...I'll put in a disalbe override,  but leave enabled the default.  Will that  suit everyone?18:38
*** dwalleck_ has joined #openstack-meeting18:38
jrouaultyes18:38
ayoungjrouault, so you specifically need the shorter length?18:39
dolphmjrouault: what kind of length is problematic? what lead you to assume a specific length?18:39
*** dwalleck_ has quit IRC18:39
dolphmjrouault: is there a maximum token length documented somewhere that we need to correct?18:40
*** ijw has joined #openstack-meeting18:40
*** ijw has quit IRC18:40
*** ijw has joined #openstack-meeting18:40
jrouault2.  we also have some keystone like token generators that are used for testing... those would all need to change to support signing... but that is not so much a concern for the community18:40
ayoungjrouault, I can help you build some replacements.18:41
*** dwalleck_ has joined #openstack-meeting18:41
heckjjrouault: I'm most interested in the length issue and what you're hitting there - do you have a max length?18:41
jrouaultheckj: i do have the exact length but can get that to you18:42
jrouaults/don't/do18:42
*** dwalleck has quit IRC18:42
heckjjrouault: thanks - would like to know that ASAP, as there's a bunch of other potential impacts there18:43
ayoungOK...I'm thinking that is insufficient reason to hold up the PKI side of things.  THe token length could change for many reasons  without PKI.  I am not really willing to disable the server side just for a specific test harness18:43
jrouaultmaking it optional is holding things up?18:44
heckjayoung: don't hold up the PKI effort - carry it forward, let's just make sure we can disable it as an option, but not as the default settings18:44
ayoungheckj, disabling it is not trivial on the Keystone side.18:45
ayoungSo it will hold it up.  Plus,  if both forms of tokens ate allowed, they should be minimally tested18:45
heckjayoung: gotcha. Let's see what we can suss out to enable both or either at the same time18:46
ayoungOK...I'll post the current code to my github page here shortly18:46
heckjsounds good18:46
rafaduranayoung: Can I change topic now?18:48
heckj#action jrouault to provide a max key length18:48
heckjrafaduran: yep -18:49
ayoungrafaduran, yes, please do so18:49
rafaduranI've working on the rate limit middleware, I still need some work on it, but It would be nice get some feedback on corner cases, defaults ...18:49
rafaduranI think it would be nice take some time for next meeting18:49
*** zigo has quit IRC18:49
heckjrafaduran: I'll schedule it up as a specific topic for next meeting18:49
rafaduranheckj: Ok, thanks18:49
*** Shrews has joined #openstack-meeting18:50
heckjcool - any other topics for today?18:51
heckjOkay - gotta present in 5 minutes, so I'll close this up for today.18:53
heckj#endmeeting18:53
*** openstack changes topic to "OpenStack meeting channel. See http://wiki.openstack.org/Meetings for schedule and http://eavesdrop.openstack.org/meetings/openstack-meeting/ for meeting logs"18:53
openstackMeeting ended Tue Jul  3 18:53:32 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-03-18.01.html18:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-03-18.01.txt18:53
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-03-18.01.log.html18:53
*** kevin-lewis-9 has quit IRC18:53
*** jrouault has quit IRC18:54
*** Mandell has quit IRC18:55
*** Mandell has joined #openstack-meeting18:56
*** atiwari has quit IRC19:00
*** devananda has joined #openstack-meeting19:00
mtaylorola!19:01
mtaylor#startmeeting19:01
openstackMeeting started Tue Jul  3 19:01:38 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
clarkbohai19:01
mtayloranybody around want to talk about so you think you can dance?19:02
mtayloroh19:02
mtaylorI mean19:02
mtayloropenstack CI stuff?19:02
jeblairo/19:02
*** rkukura has quit IRC19:02
mtaylorneat19:03
*** tchan_ has quit IRC19:03
mtaylorso - jeblair I believe wanted to talk about jenkinsy failure and retrigger stuff, yeah19:03
jeblairyep.19:03
jeblairmy main concern is global dependency list and how that relates to getting the pypi mirror stable19:04
jeblairi see there's a mailing list thread, which unfortunately has some confusion associated with it.19:04
*** Daviey has quit IRC19:04
jeblairi certainly haven't seen a viable suggestion other than your initial one.19:04
jeblairwould it be productive to talk about that here (perhaps summoning some people), or should we leave that on the ML for now?19:05
mtaylorno. and I intend, for the record, to ignore all of the irrelvant things that have been said so far19:05
mtaylorthe ML thread is supposed to be informative, and then to ask an opinion on the name "openstack-requires"19:05
mtaylorthe one counter suggestion I've heard is "openstack-packaging" - which I don't REALLY like19:05
jeblairyeah, i don't see a justification far that.  i might say openstack-requirements but it's close enough.19:06
mtayloralthough I do think we could certainly put in a dpkg-selections file and an rpm list so that devstack could consume the current state of depends19:06
jeblair(or openstack-dependencies)19:06
jeblairindeed.19:06
mtaylorI have to think too much to type dependencies19:06
jeblairheh19:06
clarkbthat is what tab keys are for19:07
clarkbor ^N19:07
jeblairso do you have an estimate for when we might be fully utilizing that (and can use only our pypi mirror)?19:07
jeblair(and are there things other ppl can do to help it along?)19:08
mtaylorthere's a couple of stages19:08
mtaylorI could post the new repo today (and just assume that when markmc gets back from vacation that he'll be unhappy with whatever the name is ;) )19:08
mtaylorbut then we have to start actually aligning the projects19:08
mtaylorI don't see that happening realistically until F319:08
clarkband alignment is what will actually make this useful towards stability?19:09
*** kindaopsdevy has quit IRC19:09
mtaylorit will ... because once we're aligned once, then all of the packages will have come from that list19:10
mtaylorso future divergence (like the list moving forward but nova not tagging along immediately)19:10
mtaylorwill still have all of the prior versions in the mirror (since we don't reap)19:10
mtaylorACTUALLY - I'm lying19:10
*** kindaopsdevy has joined #openstack-meeting19:10
jeblairbut in all cases, devstack is going to test with exactly one version of each thing.19:10
mtaylorwe don't need convergence. we have the complete set of packages _today_19:10
*** kindaopsdevy has quit IRC19:10
mtaylorall we need is for the repo to exist and the _policy_ to be that all new package versions must hit it first19:11
*** kindaopsdevy has joined #openstack-meeting19:11
*** nati_uen_ has quit IRC19:11
jeblairyeah, we don't actually need changes to each project to get this merged.19:12
*** nati_ueno has joined #openstack-meeting19:12
mtaylorcorrect19:12
mtaylorwe just need the repo, and to add its lists to our pypi mirror creation - and then we need to trigger a pypi mirror run on changes from the repo19:12
jeblairthen perhaps we should go ahead and do that much, because it will make our mirror much more useful.19:13
*** dwalleck_ has quit IRC19:13
jeblairand then get devstack using the packages, and then get the copy-into-projects thing going.19:14
*** dwalleck has joined #openstack-meeting19:14
jeblairyou think we can get the first step done within a week or two?19:14
mtaylorI do think so19:14
*** Daviey has joined #openstack-meeting19:15
*** dwalleck has quit IRC19:15
jeblairokay.  so my second item was to explore an alternate plan in case we couldn't do that in a reasonable amount of time...19:15
mtaylorI think if we can get vishy and bcwaldon and heckj and notmyname and danwent and devcamcar on board with at least attempting it19:15
jeblair(something like build the mirror from the individual projects and use it exclusively except in the case of testing a change to the -requirements)19:15
jeblairbut perhaps we don't need to talk about the alternate plan if the main one looks viable.19:16
mtaylorright. well - also, I should take this moment to point out that we were seeing a MUCH higher failure rate than normal because the mirror script had been silently failing for the last month19:16
*** jmckenty has joined #openstack-meeting19:16
jeblairindeed, and thanks for fixing that!19:17
mtaylorwell... remind me next time _not_ to put 2>/dev/null in scripts that get run by cron :)19:17
jeblairso point #3 i had was how to be more resilient to gerrit errors19:18
jeblairi believe clarkb's exponential backoff script is in place now19:18
jeblairand things seem to still work, so that's great.  that should help us avoid failing when a simple retry of the git command would succeed.19:18
clarkbit is. I have been checking console output for jobs semi randomly to see if any of them have had to fetch more than once, but I haven't seen that happen19:18
jeblairit might be useful to have that script log when it has to back off19:19
*** bcwaldon has joined #openstack-meeting19:19
*** dolphm has quit IRC19:19
jeblairperhaps it could syslog, and we could check up on it periodically19:19
jeblairclarkb: what do you think?19:19
clarkbsounds good. I will add that19:19
jeblair(and maybe someday we'll have a syslog server)19:19
jeblaircool, then we'll be able to track whether the incidences of transient gerrit failures are increasing or decreasing.19:20
clarkbyou have also increased the http timeout from 5ms to 5s19:20
jeblairand of course, after our badgering, spearce found a bug in gerrit19:20
jeblairyes, that one19:20
jeblairthere was a tuning parameter which i would have changed had the default not already been a 5 minute timeout19:21
*** Mandell has quit IRC19:21
mtaylorI think that'll help19:21
jeblairthe bug was that it was interpreted as a 5 millisecond timeout, so that was pretty much useless.19:21
*** Mandell has joined #openstack-meeting19:21
jeblairit's definitely a parameter that's right in the middle of where we thought the problem might be, so yeah, pretty optimistic.19:21
mtayloralso, I've got some apache rewrite rules up for review that I need to test that would allow all of our anon-http fetching to be done by normal git and apache - with packs themselves served out as static files by apache with no cgi anything in the way19:22
clarkbyou also restarted all the things after the leap second bug which I am sure didn't hurt19:22
mtaylorso I'm hoping that helps too19:22
jeblairmtaylor: yep.  that system is basically idle, plenty of room for apache to do what it does best.19:23
jeblairokay so #4 is how to handle retriggers, because no matter how awesome everything else is, something is going to break, or someone is going to impreve the system.19:23
jeblairand we need a not-ridiculous way for people to retrigger check and gate jobs.19:23
*** novas0x2a|laptop has quit IRC19:24
jeblairso we've had two ideas about that19:24
clarkbmy idea which is a bit of a hack (but less so than pushing new patchsets) is to leave a comment with some string in it that zuul will interpret as meaning retrigger the jobs19:24
jeblairand an earlier idea i had was to have a link in jenkins (maybe in the build description) that would retrigger the change in question.19:25
jeblairmy idea is not easily or elegantly implemented in zuul.19:25
jeblairclarkb's idea is.19:25
jeblairthe only downside i see to clark's is that, by design, anyone would be able to say "reapprove" and launch the approve jobs, even before a change has been approved.  but that's really okay since gerrit won't merge them without the approved vote anyway.19:26
mtaylorI'd say...19:27
*** dendrobates is now known as dendro-afk19:27
mtaylorwe don't really need re-approve, since anyone with approval bit in gerrit can already re-approve19:27
jeblairalso, in magical pony world, i'd really like to have a button in gerrit, and clark's solution is more compatible with that possible future expansion.19:27
mtaylorretrigger, on the other hand, meets a current missing need19:27
jeblairwell, before, anyone could retrigger an approval job19:27
jeblairi think probably patchset authors want to be able to reapprove their own patches, since they're watching out for them, without bugging core reviewers19:28
mtaylorgood point19:28
mtaylorok. I'm fine with it19:28
jeblairit's easy to do one, the other, or both with clarkb's change anyway, it's all just configuration.19:29
mtayloragree19:29
* mtaylor is in favor of clark's change19:29
* jeblair agrees19:29
mtaylorand a long-term task to add a button to gerrit19:29
jeblairso that just leaves 'what should the magic words be?'19:29
*** zigo has joined #openstack-meeting19:29
clarkbhttps://review.openstack.org/#/c/9195/ adds this functionality to zuul19:29
*** ijw has quit IRC19:29
jeblairi'm not sure just 'retrigger' is a good idea, i mean, it might trigger jobs due to casual code reviews.19:29
mtaylorI'd say that a comment left that is the text "retrigger" and only that text19:30
jeblairah ok.19:30
*** Mandell_ has joined #openstack-meeting19:30
mtaylorso: ^\s*retrigger\s*$19:30
*** jmckenty has quit IRC19:30
jeblairand retrigger itself is vague (retrigger what?)19:30
*** lloydde_ has joined #openstack-meeting19:30
*** lloydde has quit IRC19:30
mtaylorrebuild?19:31
jeblairperhaps it should be recheck/reapprove19:31
mtaylorrecheck19:31
clarkbthe verbs I used when testing were reverfiy and recheck19:31
mtayloryeah19:31
*** Mandell has quit IRC19:31
clarkb*reverify19:31
jeblairand we need distinct values for the two kinds of jobs19:31
clarkbrecheck and reapprove sound good to me19:31
mtaylorrecheck for pre-approval, reverify for post-approval19:31
mtaylor?19:31
*** mestery has joined #openstack-meeting19:31
*** littleidea has quit IRC19:31
*** mestery has quit IRC19:32
jeblairslight preferene for recheck/reverify19:32
mtaylordamn naming19:32
mtayloryeah. me too19:32
jeblair(since jenkins isn't actually approving)19:32
clarkbworks for me19:32
*** mestery has joined #openstack-meeting19:32
mtaylorcool. sold19:32
*** tw__ has quit IRC19:32
jeblairokay, i think that's all the decision making i needed today.  :)19:33
mtayloranybody in channel who isn't the three of us have an opinion? you have exactly one minute19:33
jeblair(and i even told the ml we'd talk about this at the meeting today)19:34
mtaylorcool. ok. done19:36
mtaylor#topic bragging19:37
*** openstack changes topic to "bragging"19:37
mtaylorclient libs are auto-uploading to PyPI now19:37
mtaylor#topic open discussion19:37
*** openstack changes topic to "open discussion"19:37
mtayloranything else?19:37
jeblairthe devstack-gate job output is _much_ cleaner now19:37
LinuxJedioh, I have something19:38
clarkbI do too once LinuxJedi is done19:38
jeblairjaypipes: any chance you're around?19:38
LinuxJediGerrit is now using my row color theme patch19:38
mtayloryay!19:38
LinuxJediand that has been pushed for review upstream19:38
LinuxJedialong with the other theme patch19:38
clarkb(and JavaMelody)19:38
mtayloroh - and the monitoring patch is live - although if you didn't know that already, you probably don't have access to see it19:38
mtaylorjaypipes: yeah - how's that tempest stuff coming along?19:38
* mtaylor doesn't konw if that's what jeblair was pinging jaypipes about19:39
LinuxJediif you don't have access to see it, it is the pot of gold at the end of the rainbow you have all been looking for19:39
mtaylorSO ... clarkb19:39
jeblairyep.  we are so ready to run tempest on gates, but i don't think tempest is yet.19:39
devanandachiming in randomly here, my openvz kernel scripts can now handle in-place kernel upgrades19:40
mtaylorI _think_ there is some way to get melody to splat out its information in a form that collectd or icinga can pick up19:40
*** dwcramer has quit IRC19:40
mtaylordevananda: w00t!19:40
mtayloroh, I spoke with primeministerp earlier today and he's working on getting the hyper-v lab back up and going - so we might have more contrib testing from there19:40
jeblairwho is primeministerp?19:41
mtaylorand Shrews may or may not be getting closer to or futher away from nova openvz support, fwiw19:41
jeblairnotmyname: are you here or on the road?19:41
clarkbmtaylor: it has pdf exports :) its "enterprise"19:41
mtaylorjeblair: can't think of real name - boston guy from suse/novell who worked with microsoft on interop19:41
Shrewsmtaylor: yeah, well, there's been a wrench thrown in that we should discuss19:41
mtaylorShrews: does the wrench involve buying me liquor?19:42
*** novas0x2a|laptop has joined #openstack-meeting19:42
jeblairah, i remember him.19:42
Shrewsmtaylor: no. devananda gave me some news that the RS patch may be forthcoming soon19:42
mtayloro really?19:43
mtaylorgreat. well, do you feel you've learned things?19:43
devanandashort version, it may arrive on github thursday, or it may not19:43
joearnoldjeblair: notmyname is on the road.19:43
mtayloron github?19:43
Shrewsgithub?19:43
mtaylorwhy would it arrive on github?19:43
jeblairjoearnold: thanks.  bad day for getting updates from other people.  :)19:43
mtaylorjoearnold: unacceptable!19:44
joearnold:)19:44
devanandaright. i don't know why.19:44
mtaylorjoearnold: notmyname is always to be available19:44
clarkbI wanted to bring up cgroups and ulimits for jenkins slaves19:44
mtaylordevananda: well, I suppose it's something :)19:44
mtaylorclarkb: yes!19:44
jeblairthe change to add swift to the devstack gate worked without any particular drama, so it'd be nice to work on a plan to get that merged.19:44
LinuxJediclarkb: excellent!19:44
mtaylor#topic cgroups and ulimits19:44
*** openstack changes topic to "cgroups and ulimits"19:44
joearnoldmtaylor: true enough. He's on his way to flagstaff, az19:44
clarkbthe ulimits modules was merged and is straightforward to use19:45
clarkbI think we are fairly safe limiting the jenkins user to some reasonable process limit using that module19:45
*** jmckenty has joined #openstack-meeting19:45
clarkbtwo questions though. what is a reasonably safe process limit? and how does the jenkins user login is it through su?19:46
jeblairclarkb: via ssh actually19:46
clarkbawesome. ssh login has security limits applied by default on ubuntu19:46
*** jk0 has joined #openstack-meeting19:46
jeblairjenkins master ssh's into the slave host, runs a java process, and that process runs jobs.19:47
clarkbbut not for su19:47
jeblairon the devstack nodes, that _job_ would su to another user (stack) who might also su to root to run devstack..19:47
*** novas0x2a|laptop has quit IRC19:47
jeblairbut since that happens on single use slaves with job timeouts, it's not such a priority.19:47
clarkbso other than determining what a sane number for a process limit is the ulimit stuff is not very scary19:48
clarkbcgroups on the other hand have the potential to be great fun19:48
LinuxJediclarkb: 640kbytes should be enough for anyone!19:48
jeblairso we should probably monitor process count during, say, a nova unit test run.19:48
clarkbthe current cgroup change https://review.openstack.org/#/c/9074/ adds support for memory limits for the jenkins user on jenkins slaves but does not apply them in site.pp19:49
clarkbjeblair: good idea19:49
*** dendro-afk is now known as dendrobates19:49
jeblairclarkb: how do you think we should apply the cgroups change?19:49
jeblaircarefully or recklessly?  :)19:50
clarkbthe cgroup configuration sets a soft memory limit of 512MB of memory for the jenkins user. This comes into play if there is any memory contention on the box19:50
*** dprince has quit IRC19:50
*** nikhil has quit IRC19:50
clarkbso jenkins would be limited to 512MB if something else was making the machine unhappy.19:50
clarkbit also applies a hard limit of 75% of the physical memory on the machine19:50
clarkbthe hard limit is more dangerous, because by default OOM killer will be invoked to clean up jenkins' processes if it doesn't free memory when asked nicely19:51
clarkbwe can disable OOM killer which will cause memory overruns to force processes to sleep when they need more memory19:52
clarkbor we can completely redo the numbers. I think not setting a hard limit and only setting a soft limit to 75% of physical memory would be safer19:52
clarkbjeblair: I was thinking carefully would be best :)19:53
jeblairso what happens if the soft limit is reached?19:53
clarkbmaybe add a node definition for a specific jenkins_slave (more specific than the current glob) and see how that host does19:53
*** thingee has joined #openstack-meeting19:53
*** sleepsonthefloor is now known as sleepsonzzz19:53
jeblairclarkb: that's a good idea.  then we can easily disable that node if it causes problems.19:53
clarkbjeblair: soft limit only applies if there is memory contention on the host. In that case it acts like a hard limit19:53
*** nikhil has joined #openstack-meeting19:54
LinuxJediclarkb: contention including swap?19:55
*** novas0x2a|laptop has joined #openstack-meeting19:55
clarkbLinuxJedi: I think so19:55
LinuxJediI know HP Cloud only applies to devstack but we give those like 100GB of swap due to the way the disks are configured19:55
clarkbhttp://www.mjmwired.net/kernel/Documentation/cgroups/memory.txt kernel documentation doesn't quite spell out all of the details19:56
* LinuxJedi really doesn't want to be using 100GB of swap on anything ;)19:56
clarkbin that case we can set hard limits that are larger than 75% of physical memory19:57
clarkbmaybe physical memory * 219:57
LinuxJedijeblair: what do you think?19:57
jeblairwell, i don't want to be swapping at all really.  :)19:57
jeblairperhaps a hard limit of 90%?19:58
clarkbjeblair: ok19:58
LinuxJedisounds good to me19:58
jeblairat 5G, that leaves 400M for the rest of the system, which seems reasonable.19:58
jeblair4G, that is.19:58
clarkbI will update the change after lunch with what that looks like19:58
LinuxJediwe can always tweak it if it causes pain19:58
LinuxJedibut I feel safe with that19:58
*** jaypipes has quit IRC19:58
mtaylor++19:59
jeblairok.  and let's do clark's idea of applying it to just one jenkins slave19:59
clarkbsounds good19:59
*** jbryce has joined #openstack-meeting19:59
jeblair1 sec and i'll pick one.19:59
* LinuxJedi watches jeblair use the scientific method of closing eyes and pointing to a random machine on the screen20:00
jeblairprecise820:00
jeblairLinuxJedi: close -- gate-nova-python27 runs there a lot.  :)20:01
ttxhrm hrm.20:01
devcamcaro/20:01
ttxjeblair: time to call that meeting to an end :)20:01
jeblairmtaylor: time to call that meeting to an end :)20:01
mtaylorkk20:01
mtaylor#stopmeeting20:01
jbrycemtaylor: !20:01
mtaylorthanks guys!20:01
mtaylor#endmeeting20:01
*** openstack changes topic to "OpenStack meeting channel. See http://wiki.openstack.org/Meetings for schedule and http://eavesdrop.openstack.org/meetings/openstack-meeting/ for meeting logs"20:01
openstackMeeting ended Tue Jul  3 20:01:56 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-03-19.01.html20:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-03-19.01.txt20:02
LinuxJedilol :)20:02
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-03-19.01.log.html20:02
mtaylorjbryce: how ya doing?20:02
jbrycemtaylor: great, you?20:02
*** Shrews has left #openstack-meeting20:02
jbryce#startmeeting20:02
openstackMeeting started Tue Jul  3 20:02:17 2012 UTC.  The chair is jbryce. Information about MeetBot at http://wiki.debian.org/MeetBot.20:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:02
jbrycewho all is present?20:02
bcwaldonhere20:02
mtaylorjbryce: awesome as always :)20:02
jk0o/20:02
ttx\o20:02
devcamcaro/20:02
*** sleepsonzzz is now known as sleepsonthefloor20:02
heckjo/20:02
*** devananda has left #openstack-meeting20:03
danwento/20:03
ttxthat makes 620:03
ttx720:03
jbryceand 720:03
jbrycegreat20:03
jbrycelet's start with bcwaldon's topic20:03
jbryce#topic Code for interfacing with proprietary systems20:03
*** openstack changes topic to "Code for interfacing with proprietary systems"20:03
jbrycebcwaldon: want to lead this one?20:03
bcwaldonmatiu: and we already have a concept of sure20:03
bcwaldonbah20:03
bcwaldonyes20:03
bcwaldonstrike that from the record!20:04
ttx<REDACTED>20:04
* jbryce strikes20:04
bcwaldonthank you, ttx20:04
bcwaldonand jbryce20:04
bcwaldonassuming everyone didn't read the email I sent, the tl;dr here is 'do we accept code designed to interface with non-open source or paid-only systems'?20:05
jeblairbcwaldon: what's the subject of the email you sent?20:05
bcwaldonjeblair: it was in response to jbryce's 'Tomorrow's meeting' sent to openstack-poc20:05
ttxjeblair: https://lists.launchpad.net/openstack-poc/msg00552.html20:05
*** rafaduran has quit IRC20:05
heckjttx: thanks20:06
jeblairbcwaldon: ah, mere mortals are unable to subscribe to that list.20:06
bcwaldonjeblair: yes, I see that now20:06
bcwaldonjeblair: thankfully ttx has your back20:06
Davieyit doesn't seem bad, providing there is protection to ensure that openstack is only a decent platform with paid-for software (ie, open core).. But also.. the tests need to be finite.. nbody can be blamed if they break that support, if the tests pass..20:06
ttxbcwaldon: you mean, accept in core, right ?20:06
bcwaldonyes20:06
bcwaldonthe cost of supporting this code weighed against the benefit seems too high20:07
jbrycedoes glance do this already? with s3 for instance?20:07
pvoo/20:07
ttxbcwaldon: my 2c is that we should only accept code in core that we can test20:07
danwentbcwaldon: we certainly do in quantum.   we have code that hits nicira solutions, cisco, and will be accepting code that hits NEC in F-320:07
bcwaldonfor example, if I want to make a sweeping change to all of our glance store drivers, I need to test that I didn't break that20:07
bcwaldonttx: yes, thats what I'm getting at20:07
danwentour approach is that all unit tests should be able to pass even without the proprietary system being there.20:08
bcwaldonjbryce: there are open-source implementations of the s3 api20:08
danwent(using a mock)20:08
bcwaldonjbryce: so its kind of a special case20:08
ttxdanwent: but is that code core ? Or a plugin ?20:08
danwentttx:  its a plugin, but its in the main repo...20:08
danwentmaybe i'm confused by what you mean by "core"20:08
bcwaldonour functional tests are a bit weak in glance right now as we depend on a functional system (amazon s3, rackspace cloud files) to be able to run them20:08
bcwaldondanwent: into the openstack/glance repo20:08
danwentok, yes, that's the same defintion I was using.  Our plugins are in openstack/quantum20:09
danwentas would be nova code that hits vmware or hyper-v, I suspect20:09
ttxdanwent: main repo, so your case would be in bcwaldon's scope20:09
jbrycewhat is the alternative for where this code would live?20:09
ttxjbryce: in a separate plugin project20:10
bcwaldonjbryce: hosted by the other side of the equation20:10
heckjseperate repo, I suppose20:10
bcwaldonjbryce: or in a different openstack repo20:10
*** thingee_zz has joined #openstack-meeting20:10
ttxthe Hyper-V story shows that what we cannot test ends up breaking20:10
ttxbut...20:10
bcwaldonI don't think anybody wants to argue that this code can't exist, it's really just who should own it and be expected to support it20:10
ttxI'm not sure the line in the sand is about "interface to proprietary"20:10
jbryceso separate and the user/distro is responsible for grabbing and integrating20:10
bcwaldonjbryce: thats one idea20:11
ttxIMHO it's more about being given ways to test it20:11
danwentbcwaldon: agreed.  for third-party code like this to be allowed to be in core, we require that a core dev signs up to maintain it.20:11
jbrycettx: agree20:11
*** thingee has quit IRC20:11
danwent(otherwise its kept out of trunk)20:11
bcwaldondanwent: I don't see how that would necessarily work in practice20:11
bcwaldondanwent: if a different member needs to make a change to that bit of code, how can he move forward?20:11
heckjbcwaldon: My own take would be to allow it, but keep it in a contrib/ (or equiv) directory, and support it to the point that it's tests drive it (through mocks, fakes, or whatever).20:11
ttxso if we are given "stuff" that allows us to gate on tests that interface with a proprietary platform AND a commitment to maintain that code... not sure we should refuse it becuase it interfaces with "something you have to pay for"20:12
heckjbcwaldon: you might end up needing to yank it in the future if it bitrots through ignoring, but I'd personally lean towards inclusion.20:12
danwentbcwaldon: anyone can change the code… the point is that someone is responsible for answering questions about the code, figuring out why a test broke if its unclear, etc.20:12
bcwaldoneven if we aren't given tests, we just have to make sure it's isolated20:12
bcwaldondanwent: ok, then we're back to the added cost to development20:12
ttxI suspect on one end of the spectrum you have Hyper6V, on the other end you have Nicira's plugin20:12
danwentbcwaldon: not sure I follow, but according to ttx, it may not be relevant, so i'll stay quite :)20:13
danwentquiet20:13
bcwaldondanwent: please speak up! I'm not trying to shut anyone down here :)20:13
bcwaldonso it doesn't sound like we have a single answer to the question here20:14
bcwaldonI think I can move forward20:14
danwentbcwaldon: no worries20:14
bcwaldonso let's move on if nobody else has anything20:14
jbrycei think testability is a good delineator. also committed parties for maintaining. any additional features whether it's proprietary or not are going to have some added cost to the development20:15
jbryceok20:15
bcwaldonjbryce: yes, all things I'm going to take into account20:15
*** dendrobates is now known as dendro-afk20:15
ttxbcwaldon: my gut feeling is that stuff that cannot be freely tested by anyone should be out of core. If we are given ways for anyone on the community to test their code against a proprietary platform, that would still count as "freely testable" in my book20:15
danwentjbryce: +120:15
bcwaldonttx: my gut feeling as well20:15
bcwaldonttx: good explanation of 'freely testable'20:15
jbryceyes...i like that definition too20:15
jbryceok. moving on?20:16
bcwaldon+120:16
jbryce#topic PPB to Technical Committee transition20:16
*** openstack changes topic to "PPB to Technical Committee transition"20:16
ttxbcwaldon: i.e. I would not consider an outside test platform that nobody has access to to count as "freely testable"20:16
danwent+120:16
ttxyou actually want random devs to be able to test that their code doesn't break yours20:16
ttxanyway, new topic20:17
jbryceso i think there are 3 main things to discuss20:17
jbrycefirst...if things proceed on schedule, the foundation would be operational in september. which will also coincide with our next regularly scheduled election for PTLs, etc20:17
jbrycei propose that any time before the fall 2012 election that the TC needs to exist, the current PPB serves20:18
*** nati_uen_ has joined #openstack-meeting20:18
jbryceit will probably be a matter of weeks that we're talking about and would be simpler than trying to run another ad hoc election for that time period20:18
ttxsounds fair, we don't really have an alternative solution anyway :)20:18
*** jaypipes has joined #openstack-meeting20:18
bcwaldonjbryce: +120:18
heckj+120:18
jbryceok. that's what we'll write in20:19
Davieyttx: No, an openstack developer should have to touch non-free software unless they want to.  The unit tests must be enough IMO, and those that care about it - fix up issues.20:19
jbrycesecond and related to that20:19
Davieyoh, i'm too slow.20:19
ttxDaviey: you live 5 min in the past. Must be painful sometimes20:19
jbrycejaypipes and ttx were both elected to a 1-year term this spring20:19
jbrycei would propose that their terms continue until the spring 2013 election20:20
ttxjbryce: I'd say that depends on the election mechanism. If it is staggered, that would probably be appropriate20:20
*** nati_ueno has quit IRC20:21
ttxespecially if we renew the elected seats 2 by 2 or 2.5 by 2.520:21
Davieyttx: it's the leap second throwing me off.. (sorry for the noise)20:21
ttx(PTLs+5 option)20:21
jbrycewell i think for any of the generally elected seats (whether that is all the TC or a subset) we should have staggered 1-year terms elected in our regular 6-month cycle20:21
ttxjbryce: I'm ok with it, but I probably shouldn't have voice on that ;)20:22
jbrycehaha20:22
jbrycedoes anyone object?20:22
jbryceok20:23
jbrycethe final item is the big one...20:23
*** hggdh has quit IRC20:23
jbryce9 generally elected or PTLs + 5 generally elected20:23
jbrycei've gone back and forth on this several times. i think either can work and they both have pros and cons20:24
jbrycein talking to non-PPB members and the emails on the list from non-PPB members, there does seem to be more buy-in to not automatically giving seats to PTLs20:24
devcamcarjbryce: i'm all in favor of simplicity and removing the need for additional bodies/committees20:25
*** MarkAtwood has joined #openstack-meeting20:25
devcamcarso i favor PTLs + 520:25
ttxjbryce: I think it depends on whether the TC has oversight on the projects or not20:25
jbrycebut i know that several of the PTLs feel very strongly that it would disconnect the projects from the TC20:25
*** hggdh has joined #openstack-meeting20:25
ttxjbryce: if it does, then I'd agree that the PTLs need to be there, so PTLs+520:25
*** ijw has joined #openstack-meeting20:26
ttxIf the PTLs still have final full control and can ignore TC... then 9 elected sounds better20:26
heckjif the TC doesn't have oversight on the projects, what is it's purpose?20:26
*** ijw has quit IRC20:26
*** ijw has joined #openstack-meeting20:26
ttxheckj: defines what openstack is and is not. But can't tell a given PTL he is wrong20:26
ttxheckj: I agree with you that it should have that oversight20:27
ttxheckj: but so far, in the PPB setting, it never did20:27
ttxso that's a change. I'm all for it. And I'm ready to accept PTLs+5 if its clear that the TC has oversight20:27
jbrycettx: besides the swift release cycle, i would say that there are plenty of things the ppb has laid out that the projects have had to follow20:28
danwentI think PTL+5 is the best why to insure good communication of TC decisions to the different projects, though I admitly don't have a strategy around what happens as we get more and more core projects.  If we think TC decisions are all that relevant for each ongoing project though, this may not matter.20:28
jbrycenot all of which have always been popular20:28
ttxjbryce: example ?20:28
danwentsorry, missing a NOT in my last sentence :)20:28
jbrycenew review system20:28
jbrycegithub for code, launchpad for blueprints/bugs20:28
danwentjbryce: if those are representative of TC decisions, then I think PTLs should be involved.20:29
danwentif TC is more about letting a new project join, etc. then maybe they don't need to be involved.20:29
jbryceand even with the release cycle, swift has had a release for inclusion in every openstack "release" and we didn't mandate that milestone all had to be coordinated20:29
ttxjbryce: I know we stopped from pushing for specific things precisely because the projects kept final call. Up to the point where we had to threaten to remove the "openstack" label from a given project20:30
ttxjbryce: but that's history. Looking ahead, I'd like to put that in the TC charter20:30
ttxand if everyone agrees with that, I'm fine with PTLs+520:30
*** sleepsonthefloor is now known as sleepsonzzz20:31
ttx(I still think it will suck as we add more core projects, but life is full of trade-offs :)20:31
jbryceok20:31
jbrycedo we have anyone else on the side of 9 generally elected seats?20:31
ttxjaypipes: ^ ?20:31
jbryceok20:32
jbrycewell let's edit the proposal to put these decisions in there as final20:32
jbrycei think the only other thing is the election staggering20:32
devcamcarif TC is only about which projects join, then its scope is too limited to really be effective20:33
jbryceif we go with PTL + 5, i'd rather just elect 2 general seats in the spring and 3 in the fall like we've been doing instead of having a .5 month term20:33
jbryce.5 year term20:33
*** nati_ueno has joined #openstack-meeting20:33
jbryce.5 month term wouldn't be very long...20:33
jbrycei'd volunteer for that one. = )20:33
devcamcarlulz20:34
ttxjbryce: we also mentioned that we could have a rep from the user committee20:34
devcamcarjbryce: sounds reasonable though20:34
ttxso that would make 2+220:34
jbrycejbryce: i think we're just going to have a provision for the user committee to be able to add agenda items that the TC chair will need to recognize (can't just ignore indefinitely)20:35
jbryceso we would just run our fall 2012 election with 3 seats for 1-year generally elected terms and jaypipes and ttx would continue to serve until the spring 2013 election20:35
heckj(hands of blue)20:35
jbrycefirefly!20:36
*** nati_uen_ has quit IRC20:36
ttxjbryce: sounds simpler than my "3rd guy gets 6month" hack20:36
jbryceok20:36
jbrycedone20:36
ttxthough it hurts my sese of symmetry20:36
ttxsense*20:36
jbryceyou guys are all really into this discussion, i can tell20:36
*** ijw1 has joined #openstack-meeting20:37
jbrycei think that's it then20:37
heckjjbryce: I guess you just need to get to something more contentious...20:37
jbrycewe'll get these docs all updated20:37
ttxheckj: any suggestion ?20:37
ttxjbryce: I can draft the last version based on that20:37
heckjttx: not today - saving it up for blowing stuff up tomorrow20:38
jbrycettx: awesome20:38
ttxhaha20:38
jbryce#topic open discussion20:38
*** openstack changes topic to "open discussion"20:38
*** ijw1 has quit IRC20:38
jbryceanyone have anything else?20:38
bcwaldonnegatory20:38
heckjgood here20:38
danwentnope20:38
*** ijw1 has joined #openstack-meeting20:38
ttxI have20:38
*** zigo has quit IRC20:38
jbrycejust under the wire...i was about to stopmeeting20:38
ttxjbryce: at the bottom of http://wiki.openstack.org/Governance/Foundation/TechnicalCommittee20:38
ttxAmendment section20:39
*** ijw has quit IRC20:39
ttxshould amendments to the TC charter be approved by the BoD ?20:39
jbryceoops...missed that one20:39
*** dhellmann has quit IRC20:40
ttx(Also there is a bit of choice in the election system, let me know if anyone has string opinions for/against STV/Schulze)20:41
bcwaldonttx: makes sense to me20:41
jbrycettx: this is not something that the bylaws currently requires20:41
jbrycei can give you the wording from the latest draft (which i'm hoping to get on the wiki tonight)20:42
*** s0mik has quit IRC20:42
jbryce"Except as expressly provided in these Bylaws, the Technical Committee shall determine its process and procedures, provided that such process and procedures must be published in a manner that they are readily accessible to all Members of the Foundation."20:42
ttxjbryce: I guess it depends if the BoD will have to power to dissolve the TC ot not20:42
jbrycettx: they do not20:42
ttxjbryce: I see you've been busy :)20:42
jbrycettx: oui20:43
* ttx puts his collection of trade-offs back in the closet20:43
devcamcarttx: i'd say the tc charter should be approved by BoD, but the BoD charter should also be approved by the TC20:43
devcamcarmutually assured destruction :)20:43
ttxdevcamcar: looks like it will rather be mutually assured ignorance20:43
*** zigo has joined #openstack-meeting20:44
ttxjbryce: if that language stands in the bylaws, obviously amendments do not require BoD approval20:44
*** sleepsonzzz is now known as sleepsonthefloor20:44
jbryceultimately, the membership as a whole (including individual members) could change the bylaws and change the technical committee however they want, but a bylaws amendment is not a board only decision20:45
jbrycebylaws amendments in this area are a pretty high bar to cross20:45
ttxjbryce: oh, I see. BoD can't dissolve TC... but it can dissolve the bylaws tat created the TC in the first place.20:45
jbrycettx: no...the bod on their own cannot do that20:46
jbryceit requires a special type of vote20:46
ttxworks for me20:46
jbryceit requires an affirmative vote of the individual members20:46
ttxok, will remove that "option" at the end20:46
jbryceto change the tc portions of the bylaws specifically20:47
jbrycettx: one final question20:47
jbrycedoes it look like cinder is going to hit their f2 milestone requirements to be core in folsom?20:47
ttxjbryce: all lights are green20:48
jbrycegreat20:48
jbryceanything else from anyone?20:48
jbrycethanks guys!20:48
jbryce#endmeeting20:48
*** openstack changes topic to "OpenStack meeting channel. See http://wiki.openstack.org/Meetings for schedule and http://eavesdrop.openstack.org/meetings/openstack-meeting/ for meeting logs"20:49
openstackMeeting ended Tue Jul  3 20:48:59 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-03-20.02.html20:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-03-20.02.txt20:49
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-03-20.02.log.html20:49
bcwaldonjbryce: thank you, sir20:49
heckjgrazie20:49
ttx10min recess20:49
*** kindaopsdevy has joined #openstack-meeting20:52
*** anniec has quit IRC20:54
*** sandywalsh has quit IRC20:55
*** jk0 has left #openstack-meeting20:56
danwentmarkmcclain:  even though we aren't integrated with devstack, can you add a few lines here about how to run the dhcp-agent manually? http://wiki.openstack.org/RunningQuantumV2Api20:57
markmcclainyes20:57
danwentthx20:57
ttxo/21:00
*** gabrielhurley has joined #openstack-meeting21:00
danwento/21:00
ttxheckj, bcwaldon, vishy, devcamcar: back ?21:00
*** adjohn has quit IRC21:00
devcamcaro/21:00
bcwaldonttx: yep21:01
*** tongli has quit IRC21:01
heckjo/21:01
ttxbcwaldon: is Vish in your line of fire ?21:02
lloydde_he's in mine21:02
vishyo/21:02
ttx#startmeeting21:02
openstackMeeting started Tue Jul  3 21:02:26 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
ttxawesome21:02
ttxAgenda @ http://wiki.openstack.org/Meetings/ProjectMeeting21:02
ttx#info F2 will be cut at the end of the day.21:02
ttx#info In this meeting we'll review what's left to do, defer stuff that won't make it, get the PTL sign-off and refine the F2-targeted bug lists.21:02
*** nati_ueno has quit IRC21:03
*** anniec has joined #openstack-meeting21:03
*** adjohn has joined #openstack-meeting21:03
*** ecarlin has joined #openstack-meeting21:03
*** matiu_ has joined #openstack-meeting21:03
*** matiu_ has quit IRC21:03
*** matiu_ has joined #openstack-meeting21:03
ttx#topic Actions from previous meeting21:03
*** openstack changes topic to "Actions from previous meeting"21:03
ttx* vishy to comment on Nova bug triaging thread so that we can start doing sth about it21:03
*** ecarlin has quit IRC21:03
ttxWas DONE, nova-bugs team is now open so anyone can help with http://wiki.openstack.org/BugTriage21:03
ttx* ttx to look into organizing a bug squashing day like we did for Essex21:03
ttxThis was DONE as well. Proposed date is Thursday next week, July 12th:21:04
ttx#link http://wiki.openstack.org/BugDays/20120712BugSquashing21:04
*** ecarlin has joined #openstack-meeting21:04
ttxIf you want to organize a real-life event, you can add it to the wiki page21:04
*** adjohn has quit IRC21:04
*** s0mik has joined #openstack-meeting21:04
ttx#topic Keystone status21:05
*** nati_ueno has joined #openstack-meeting21:05
*** openstack changes topic to "Keystone status"21:05
ttxheckj: o/21:05
ttx#link https://launchpad.net/keystone/+milestone/folsom-221:05
*** nati_uen_ has joined #openstack-meeting21:05
ttxAll targets are implemented, so I suppose we are OK to cut the milestone-proposed branch in ~10 hours ?21:05
heckjttx: yep21:05
ttxLooking at the F2-targeted bugs... there are 3 of them.21:05
ttxAt this point we need to refine that list so that it only contains "milestone publication blockers":21:06
heckjwe're getting some bugfixes in - they've just been approved by our newest core member and are flowing through the system now21:06
*** matiu has quit IRC21:06
ttx(which we'll fix and backport to milestone-proposed)21:06
ttx* https://bugs.launchpad.net/keystone/+bug/101949821:06
uvirtbotLaunchpad bug 1019498 in keystone "update keystone to pep8 1.3 " [Wishlist,In progress]21:06
ttxI think this one is nice-to-have, but not blocking... I'm fine with it landing today, but I don't think it should be considered a blocker ?21:07
heckjif it doesn't flow through the approval perfectly, I'll pull it. It's literally in-progress in the gates now21:07
ttx* https://bugs.launchpad.net/keystone/+bug/101617121:07
uvirtbotLaunchpad bug 1016171 in keystone "Keystone API is forcing Content-Transfer: chunked on responses" [Wishlist,In progress]21:07
heckjIf any of these don't make it in by 5pm PST tonight, I'll pull em21:07
ttxOK21:07
heckj(3 more hours)21:07
*** kindaopsdevy has left #openstack-meeting21:08
ttxthen anything you taregt to F2 will mean that we cannot publish the milestone until the fix is in.21:08
ttxheckj: Is there any other bug that should be fixed before we finally publish Keystone F2 ?21:08
ttxWas wondering about https://bugs.launchpad.net/keystone/+bug/102010921:09
uvirtbotLaunchpad bug 1020109 in keystone "User role deletion is broken" [High,Fix committed]21:09
*** nati_ueno has quit IRC21:09
ttxooo. Fixed21:09
heckj:-)21:09
heckjDo you have a script that lines up all the fix-committed, or do I need to do that manually?21:09
ttxwell then, you have all the correct answers, I'm forced to let you go21:09
ttxheckj: I have a script that turns FixCommitted into FixReleased + milestone21:10
heckjperfect21:10
ttxthat I run as part of the MP cut process (tomorrow morning)21:10
ttxWednesday morning bugmail spam21:10
ttxheckj: anything else ?21:10
heckjnot from me - I'm good21:10
ttxQuestions about Keystone ?21:11
ttx#topic Swift status21:11
*** openstack changes topic to "Swift status"21:11
ttxnotmyname is traveling this week, asked me to paste a bit of update21:11
ttx#link https://twitter.com/notmyname/status/21994171192798003221:11
*** dwcramer has joined #openstack-meeting21:11
ttx"although I haven't updated LP yet, everything is on track for the 1.5.1 release in 2 weeks AFAIK."21:11
ttxSo let's move to another F2-affected project, unless someone has questions on Swift ?21:12
*** adjohn has joined #openstack-meeting21:12
ttx#topic Glance status21:13
*** openstack changes topic to "Glance status"21:13
ttxbcwaldon: o/21:13
bcwaldonttx: hello21:13
ttx#link https://launchpad.net/glance/+milestone/folsom-221:13
bcwaldonttx: pretty, eh?21:13
ttxWas a bit scary this afternoon, but now looks like you're all set!21:14
bcwaldonttx: I wouldn't say it was 'scary'...21:14
bcwaldonttx: it needed some grooming21:14
bcwaldonttx: and that's all done now :)21:14
* ttx thinks bcwaldon will need more than grooming to complete all his F3 targets21:15
* vishy resists the urge to change the blueprints out from under ttx21:15
ttxvishy: try me21:15
* bcwaldon also enjoys speaking the third person21:15
bcwaldoncrap!21:15
ttxAnyone has a bug that we shouldn't publish F2 with ?21:15
ttx(Glance F2, I mean)21:15
*** markvoelker has quit IRC21:16
ttxbcwaldon: Anything else on your mind ?21:16
bcwaldonttx: well, I've been feeling like I need to get some coffee21:16
*** markmcclain has quit IRC21:16
bcwaldonttx: other than that, no21:16
ttxcoffee good21:16
ttxRaise your hand if you've a question on Glance...21:16
ttx(when I prepared this meeting earlier today, it looked a lot more busy)21:17
heckjbcwaldon: coffee ++21:17
ttx#topic Quantum status21:17
*** openstack changes topic to "Quantum status"21:17
ttxdanwent: yo21:17
danwenthi21:17
*** mestery has quit IRC21:17
ttx#link https://launchpad.net/quantum/+milestone/folsom-221:17
ttxOn the blueprints side, 2 targets left:21:17
danwentbtw, you'll want to refresh for status on a couple bugs that i updated 15 mins ago21:17
danwentyes, dhcp is our key focus21:18
ttx* https://blueprints.launchpad.net/quantum/+spec/quantum-dhcp21:18
danwentwe're very close on that.21:18
ttxPending on https://review.openstack.org/#/c/9064/ ?21:18
danwentyes.  -1s are style issues right now.  needs final testing though.21:18
ttx* https://blueprints.launchpad.net/quantum/+spec/provider-networks21:18
danwenti'm confident this will get in.21:18
danwent(comment was about dhcp)21:18
*** adjohn has quit IRC21:18
ttxLooks like this one is still a bit far away. The change up for review only partially implements it. Defer ?21:18
*** matiu_ is now known as matiu21:19
danwentthe provider-networks stuff will almost certainly not make it.21:19
danwentunless we decide to backport to milestone proposed21:19
danwenthe will have a review tonight, but I don't think its critical to push.21:19
ttxdanwent: I'd prefer not to backport feature code21:19
danwentttx: yes, that's my feel as well.  I'm fine bumping it right now if you prefer.21:19
danwentyou're pulling branches in 3 hours?21:20
ttxAre you OK with me cutting the F2 branch in ~10 hours with what will be in there ? Or is quantum-dhcp a must-have-in-F221:20
ttx~10hours, I need some sleep21:20
danwentwe'll have it in less than 10 hours21:20
ttxdanwent: sure, but in case I wake up and it isn't ? I hear Ci sometimes fails21:20
danwentshould have it pushed in a few, as author is on east coast21:20
danwenthehe.  please hold if its not in.  its important, and i'll my best to make sure it is in, CI be damned.21:21
ttxOK21:21
danwentbut I will email you to let you know if we somehow can't get CI working.21:21
* ttx refreshes bug list21:21
ttx5 bugs on the F2 target list21:22
danwentall in progress bugs are in review.21:22
ttx* https://bugs.launchpad.net/bugs/101946221:22
uvirtbotLaunchpad bug 1019462 in quantum "devstack support for quantum DHCP" [High,Confirmed]21:22
danwenttwo of the 5 issues are devstack, which isn't something that makes the tarball21:22
ttxisn't that a devstack bug ?21:22
danwentyes, but for sanity I track it in quantum (ducks)21:22
ttxdanwent: we should find a way for you to track outside bugs that doesn't involve creating fake bugs :)21:23
danwenti would love that21:23
danwentwe should probably also just defer #101989921:23
ttx#action ttx to see how danwent could track bugs outside quantum without creating noise21:24
danwenti need to track changes to nova, devstack, horizon as well as quantum21:24
ttxdanwent: at the EOD can you refine that list so that it only contains stuff you intend to backport and that you don't want to release F2 without ?21:24
danwentno easy to to do that sanely on launchpad without "shadow" bugs21:24
salv-orlandobug 1019899 is 5 minutes from push21:25
uvirtbotLaunchpad bug 1019899 in quantum "add support for requested_networks extension to Nova/Quantum v2 code" [High,Confirmed] https://launchpad.net/bugs/101989921:25
danwentsalv-orlando: ah, still up :)21:25
ttxdanwent: you can search for tags at openstack superproject level21:25
ttxdanwent: we'll talk about that another day :)21:25
danwentttx: ok, will explore that.21:25
ttxdanwent: at the EOD can you refine that list so that it only contains stuff you intend to backport and that you don't want to release F2 without ?21:25
danwentsalv-orlando: please propose soon, as we'll need to find nova core devs for that one (ducks again..)21:26
danwentttx: yes, will have bug lists pruned.21:26
danwentall of that stuff will move if the reviews done clear today21:26
danwentdon't21:26
ttxdanwent: Awesome. Anything else ?21:26
danwentone thing21:26
danwentso with v2 quantum there are a lot of changes in how you invoke quantum that will be the result of F-2 and F-3 work.21:27
*** ryanpetrello has quit IRC21:27
danwentwe've had a lot of trouble getting eyeballs on quantum-related reviews for devstack21:27
danwentso we're trying to work with devstack leads on how we can get some quantum team members core reviewers status for devstack to help with the load21:27
ttxdanwent: right, that sounds like the good way to solve that21:28
danwentthis is also important for devstack gating21:28
danwentwe've had reviews for that hanging for weeks21:28
ttxdanwent: ok, keep us posted on the outcome21:28
danwentI'll loop you into the existing email thread.21:29
danwentthat's all from me21:29
ttxQuestions on Quantum ?21:29
ttx#topic Nova status21:29
*** openstack changes topic to "Nova status"21:29
ttxvishy: hey21:29
ttx#link https://launchpad.net/nova/+milestone/folsom-221:30
* ttx refreshes21:30
vishyhi21:30
*** mnewby has quit IRC21:30
vishyi didn't break it :)21:30
ttx7 targets left, looks like massive defer-to-F3 is in order :) let's review them...21:30
ttx* https://blueprints.launchpad.net/nova/+spec/finish-uuid-conversion21:30
ttxStatus a bit unclear on that one ?21:30
vishyttx: turns out there is a bit more, so lets defer it21:30
vishybcwaldon: this is done, right? https://blueprints.launchpad.net/nova/+spec/integrate-python-glanceclient21:31
bcwaldonvishy: no21:31
ttxbcwaldon: what's left to do ?21:31
bcwaldonvishy: I did all the work to be able to do that21:31
bcwaldonactually do it21:31
ttxbcwaldon: how much time does actually doing it take ?21:31
ttxis that compatible with F2 ?21:32
bcwaldonttx: more than I would have for f221:32
ttxack21:32
bcwaldonbar21:32
ttxbcwaldon: what about https://blueprints.launchpad.net/nova/+spec/remove-deprecated-auth ?21:32
bcwaldonttx: I've been totally ignoring that one21:32
bcwaldonttx: f321:32
ttx(finish-uuid-conversion pushed to F3)21:32
vishybcwaldon: wth, its not like you have anything else to work on21:32
vishy:o21:33
bcwaldonvishy: I know :(21:33
*** PotHix has quit IRC21:33
ttx* https://blueprints.launchpad.net/nova/+spec/quantum-nova-network-api21:33
ttxPending on https://review.openstack.org/#/c/8916/ ?21:33
ttxwhich was merged..21:33
ttxso complete ?21:34
vishyyup21:34
ttx* https://blueprints.launchpad.net/nova/+spec/nova-image-cache-management-221:34
ttxremove-deprecated-auth, integrate-python-glanceclient -> F321:34
vishydefer21:35
*** zigo has quit IRC21:35
vishythat one got stuck in review21:35
*** jbryce has quit IRC21:35
vishyi think mikal switched to uuid stuff and will get back to it later21:35
ttxdeferred21:35
ttx* https://blueprints.launchpad.net/nova/+spec/instance-type-extra-specs-extension21:35
*** PotHix has joined #openstack-meeting21:35
ttxReview @ https://review.openstack.org/#/c/8089/21:35
ttxLooks almost there, would be good to push it in today21:36
ttxthough the last comment by jog0 makes me wonder a bit21:36
*** mnewby has joined #openstack-meeting21:36
ttxvishy: ?21:37
vishyttx: i think it is ok. We are moving from capabilities specified21:37
vishyin flags to host aggregates21:37
vishyhis patch is just adding more filtering based on capabilities21:37
ttxOK, so good to have,n but won't block F2 MP cut if not in in 10hours21:38
ttxlast one: https://blueprints.launchpad.net/nova/+spec/per-user-quotas21:38
*** zigo has joined #openstack-meeting21:38
ttxReview @ https://review.openstack.org/#/c/8388/21:38
ttxAlso looks almost there, would be good to push it in today21:38
vishyttx: i will approve that one21:39
vishyI was almost finished with the review21:39
ttxOK. I had a question about https://blueprints.launchpad.net/nova/+spec/multi-process-api-service (which is marked "Implemented")21:39
ttxLooks like https://review.openstack.org/#/c/8228/ is part of it though ?21:39
ttxso should it be considered still in progress ? and how likely is this to end in F2 ?21:40
vishyttx: no that should be abandoned21:41
vishyjerdfelt rewrote that patch and it merged21:41
ttxgood stuff21:42
ttxOn the bugs side, no F2 targets. Anything that we should definitely fix before we cut F2 ?21:42
ttxI noted bug 1018721, maybe21:42
uvirtbotLaunchpad bug 1018721 in nova "Launching with source groups under load produces lazy load error" [High,Triaged] https://launchpad.net/bugs/101872121:42
ttxthough if its a corner case it doesn't matter that much21:42
vishyttx: it isn't a corner case and it is really nasty in essex as well. I just don't have a real fix, just the workaround21:43
*** anniec_ has joined #openstack-meeting21:43
vishyttx: should i prop the workaround? I would really like to know what is causing it, because I expect it will come back in another form eventually21:43
ttxvishy: would be good to avoid the condition using the workaround... and open another bug to make sure we don't lose track of the more permanent fix21:44
vishyttx: yeah, although the repro case will be hard :)21:45
ttx(maybe targeting it to F3 so that it stay on scope)21:45
ttxso yes, I'd prop it for f221:45
ttxshould I target that bug ?21:45
vishyyes21:46
ttxanything else that looks really bad and we shouldn't have on the milestone ? Apart from the two CVEs that were pushed today ? ;)21:46
*** anniec has quit IRC21:47
*** anniec_ is now known as anniec21:47
ttxvishy: Anything else ?21:47
ttxvishy: i'll cut F2 with what's in master tomorrow morning, and defer the last two BPs in case they didn't make it21:48
vishyyes21:48
vishyI need reviews on host_aggregates patch too21:48
ttxthat's for F3, right ?21:48
ttxQuestions on Nova ?21:49
gabrielhurleyttx, vishy: question: while we're in the nova-volume/cinder transitional period when there are bugs about volumes (api, attachment, etc.) should those bugs be targeted against nova, cinder, or both on Launchpad?21:49
ttxgabrielhurley: single bug, two tasks21:49
gabrielhurleyttx: so add each project on the same bug report21:49
ttxgabrielhurley: that's how I would do it yes21:49
gabrielhurleyk21:49
vishygabrielhurley: probably both21:50
ttxvishy: the host_aggregates patch is for F3, right ?21:50
vishyttx: final is for f3, i was hoping to get part 1 if f221:50
vishybut i guess it isn't super-urgent21:50
ttxvishy: ok21:50
ttx#help reviews wanted on host_aggregates patch21:51
ttx#topic Horizon status21:51
*** openstack changes topic to "Horizon status"21:51
ttxdevcamcar: hey21:51
ttx#link https://launchpad.net/horizon/+milestone/folsom-221:51
gabrielhurleyttx: be sure to refresh the page... ;-)21:51
ttx1 target left :)21:51
ttx* https://blueprints.launchpad.net/horizon/+spec/nova-volume-optional21:51
ttxLooks like it's "almost there" with https://review.openstack.org/#/c/9038/ ?21:51
gabrielhurleyttx: devcamcar will reappear here, I'm sure, but yes. just needs a second +221:52
gabrielhurleyno controversy21:52
ttxgabrielhurley, devcamcar: in the unlikely case that it's not merged at the end of the day..; should I block or cut F2 MP without it ?21:53
gabrielhurleyttx: cut without it. it was moved up from F3 'cuz it was done.21:53
ttxok, thx21:53
ttxLooking at the F2-targeted bugs... 4 left21:53
ttxdevcamcar, gabrielhurley: Should they all be considered final F2 publication blockers ?21:54
*** ijw1 has quit IRC21:54
gabrielhurleyttx: I'm just gonna keep talking until someone tells me to shut up... my two will be merged today but aren't blockers. as for the other two:21:54
gabrielhurleybug 982590 isn't a blocker but I don't know who has the power to fix it21:54
uvirtbotLaunchpad bug 982590 in horizon "Repo description on github talks about old name django-openstack" [Low,Confirmed] https://launchpad.net/bugs/98259021:54
gabrielhurleyand it'd be nice to get that fixed.21:54
ttxhmm, probably openstack-ci21:55
gabrielhurley‏‎bug 101608521:55
uvirtbotLaunchpad bug 1016085 in horizon "Directories not included during install" [High,Confirmed] https://launchpad.net/bugs/101608521:55
gabrielhurleythat one is probably a blocker21:55
gabrielhurleyit had an assignee until recently21:55
ttxthis one looks like something we would backport the fix for21:55
gabrielhurleythey abandoned it21:55
ttxagreed21:55
gabrielhurleyso it needs to be fixed. I'll probably have to do it today21:55
gabrielhurley:-/21:55
*** mnaser has joined #openstack-meeting21:55
ttxgabrielhurley: you still have tomorrow, we can backport the fix until early Thursday21:56
ttxdevcamcar, gabrielhurley: Anything else you wanted to mention ?21:56
gabrielhurleyit mostly only affects the downstram packagers, but it needs resolution, for sure. I'll see what I can do.21:56
gabrielhurleyttx: that's it for me...21:56
ttxQuestions for Horizon ?21:56
ttx#topic Other Team reports21:56
*** openstack changes topic to "Other Team reports"21:56
devcamcarand i'm back! perfect timing :)21:56
ttxannegentle, jaypipes, mtaylor: ?21:57
devcamcarthanks gabriel21:57
ttxdevcamcar: heh21:57
ttxdevcamcar: anythign you wanted to add ?21:57
ttxdevcamcar: just in time for the best topic of the meeting21:57
jgriffithttx: can Cinder be "other team"21:57
devcamcarlooks like you guys have it under control21:57
ttxjgriffith: certainly :)21:57
jgriffithttx: We'll hit F2 with what was planned after today I believe21:58
jgriffith6 or 7 folks here at Piston today working on Cinder21:58
ttxjgriffith: unless you tell me otherwise i'll cut F2 branch from master in ~9 hours21:58
jgriffithttx: That works21:58
ttxjgriffith: anything else ?21:59
jgriffithNope21:59
ttx#topic Open discussion21:59
*** openstack changes topic to "Open discussion"21:59
ttxTime has come for us to choose the name of the "G" release !21:59
devcamcarhizzah!21:59
ttxYou should all be able to cast your vote at:21:59
ttx#link https://launchpad.net/~openstack/+poll/g-release-naming21:59
ttxPoll will close at 21:30 UTC Tuesday next week22:00
ttxI cleaned up the options according to the rules of play at http://wiki.openstack.org/ReleaseNaming22:00
devcamcargerber? really? :x22:00
ttxheh22:00
heckjoooh! Now I like that one!22:00
ttxStill pretty good names in there, like Gazelle, Glenn or Guadalupe22:00
devcamcarbaby cloud22:00
ttx"gerber" means "to throw up" in French.22:00
devcamcarlol22:00
ttx#action ttx to formally announce the poll on ML/twitter etc.22:00
devcamcarits a brand of baby food over this way22:00
ttxthere must be a story behind that22:01
*** Gordonz has quit IRC22:01
devcamcari'd love to hear it22:01
*** ayoung has quit IRC22:01
bcwaldonttx: Grizzly is Grizzly Flats, right?22:01
ttxbcwaldon: Grizzly is no longer an option22:01
bcwaldonno!22:01
bcwaldonthat's it22:01
bcwaldonI'm quitting22:01
ttxwe only accept single words22:01
ttxthat's the rules !22:01
* devcamcar turns over a table22:02
* ttx hides22:02
*** mnaser has quit IRC22:02
ttxI guess that means the meeting is over ?22:02
bcwaldon+122:02
ttxAwesome.22:03
ttx#endmeeting22:03
*** openstack changes topic to "OpenStack meeting channel. See http://wiki.openstack.org/Meetings for schedule and http://eavesdrop.openstack.org/meetings/openstack-meeting/ for meeting logs"22:03
openstackMeeting ended Tue Jul  3 22:03:02 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-03-21.02.html22:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-03-21.02.txt22:03
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-03-21.02.log.html22:03
*** sleepsonthefloor is now known as sleepsonzzz22:03
*** mnaser has joined #openstack-meeting22:03
* ttx can't wait for bcwaldon "G stands for Grizzly" grassroots movement to change the historic naming rules22:04
bcwaldonttx: I'm on it22:04
bcwaldonttx: you told me last week it was an option!22:04
ttxbcwaldon: I was fooled too22:04
bcwaldonttx: let's be fools together22:04
bcwaldonGrizzly blows the other names out of the water22:04
danwent+122:05
ttxbut but but22:05
bcwaldonttx: the people have spoken!22:05
heckjbcwaldon: +122:06
bcwaldonttx: GRIZZLY or gazelle22:06
*** thingee_zz has quit IRC22:06
ttxwe always only considered single words that make up a city or county name ! you mean you mean22:06
gabrielhurleybcwaldon: +122:06
ttxwe would /change the rules/ ?22:06
bcwaldonFEEL MY WRATH22:06
bcwaldonttx: I have seen no such rules22:06
bcwaldonttx: and don't you start linking me to things22:06
gabrielhurleybcwaldon: http://wiki.openstack.org/ReleaseNaming22:07
gabrielhurley;-)22:07
ttxhmmm22:07
* gabrielhurley is not ttx22:07
bcwaldongabrielhurley: a wiki...interesting22:07
gabrielhurleybcwaldon: agreed22:07
bcwaldongabrielhurley: it's editable!22:07
gabrielhurley+!22:07
*** sandywalsh has joined #openstack-meeting22:07
gabrielhurleyhmmm... "+!"... not what i was going for, but I like it22:08
ttxhmmm I tried to add the option but it looks like I can't :)22:08
bcwaldonttx: Grizzly still fits the criteria22:08
ttxthere is no place called "Grizzly" in california !22:08
bcwaldonttx: can't...or won't22:08
bcwaldonttx: It's short for Grizzly Flats22:08
ttxbcwaldon: and I can't even stop the poll I launched22:08
bcwaldonttx: it's out of control!22:08
ttxLP is now sentient22:08
bcwaldonttx: however, there is a Waldon, CA22:09
devcamcarits aware22:09
devcamcarbcwaldon: for w release22:09
bcwaldonif I can get a promise now that we will use Waldon, CA, I'll back off of Grizzly22:09
devcamcargot my vote!22:09
ttxObviously W stands for Waldon22:09
ttxI don't even see the point in voting22:10
bcwaldonttx: https://plus.google.com/112755545647106347658/about?gl=us&hl=en22:10
bcwaldonttx: roller coasters count!22:10
*** oubiwann has quit IRC22:10
ttxerr22:10
*** gabrielhurley has quit IRC22:11
bcwaldonI am disappoint22:11
salv-orlandobcwaldon: I have a much more legitimate claim to the "O" release, then....22:12
ttxbcwaldon: so it looks like there is no way back. Though I'd be happy to delegate the organization of the next poll to you22:12
bcwaldonsalv-orlando: if it's in florida, you've got my vote22:12
*** s0mik has quit IRC22:12
bcwaldonttx: let's not go crazy, now22:12
ttxI'll take full responsibility for G not being named Grizzly.22:12
bcwaldonttx: we can let this one happen, then go to a bonus round where its the winner vs Grizzly22:12
danwentall G names on that list are boring.  i'm still pro GrizzlyFlat22:12
ttxbcwaldon: hmm, tempting22:13
bcwaldonyeah, California is pretty disappointing for G's22:13
bcwaldonttx: or just send out an email and short circuit the whole process22:13
bcwaldonttx: just say 'does anyone really want it not to be grizzly?'22:13
ttxbcwaldon: OK, so how about you send22:13
bcwaldonttx: done22:14
bcwaldonttx: shortly22:14
danwentlet's make t-shirts.  they can say: I'm pro-gizzly22:14
danwentgrizzly22:14
bcwaldonttx: I'll follow-up your email announcing the poll22:14
ttxbcwaldon: an email saying you want to amend the rules of the contest so that "Grizzly" becomes an option22:14
bcwaldonttx: just add in a clause about bears22:14
ttxand we run a second-round vote between the first contest winner and Grizzly22:14
bcwaldonor characteristics of lumberjacks22:14
bcwaldonttx: ok, I'll send something after you announce the thing22:15
ttxok, I guess I should send that email now, so that you can followup22:15
*** dwcramer has quit IRC22:17
*** adjohn has joined #openstack-meeting22:17
ttxbcwaldon: sent, should be up whenever the LP ML digests it22:21
ttxhttps://lists.launchpad.net/openstack/msg14123.html22:21
ttxbcwaldon: If Grizzly wins, I want a "G stands for Grizzly" T-shirt22:22
*** dhellmann has joined #openstack-meeting22:27
*** dwcramer has joined #openstack-meeting22:31
*** zigo has quit IRC22:31
*** ryanpetrello has joined #openstack-meeting22:37
*** cp16net|away is now known as cp16net22:43
*** ryanpetrello has quit IRC22:47
*** s0mik has joined #openstack-meeting22:51
*** nati_uen_ has quit IRC22:52
*** lloydde_ has quit IRC23:03
* mtaylor votes for grizzle23:13
mtaylorgrizzly23:13
mtaylornot drizzle23:13
mtaylorgrizzle23:13
mtaylorgoddamit23:13
* mtaylor votes for nothing - he apparently can't type worth a two-penny shit23:13
*** joearnold has quit IRC23:14
*** markmcclain has joined #openstack-meeting23:18
*** s0mik has quit IRC23:19
clarkbI think mtaylor is trying to say that he would like grizzle to be an option23:20
*** ryanpetrello has joined #openstack-meeting23:22
mtaylorclarkb: I clearly should work on a release of a project called grizzle shortly after having worked on a database called drizzle23:22
mtaylorclarkb: because then doing an openstack install on top of drizzle would be - well, let's just say it wouldn't not be ridiculous23:22
*** ryanpetrello has quit IRC23:22
*** sandywalsh has quit IRC23:25
*** mnaser has quit IRC23:27
*** kindaopsdevy has joined #openstack-meeting23:33
*** kindaopsdevy has quit IRC23:37
*** ryanpetrello has joined #openstack-meeting23:40
*** salv-orlando has quit IRC23:43
*** anderstj has quit IRC23:44
*** ecarlin has quit IRC23:49
*** littleidea has joined #openstack-meeting23:49

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