Tuesday, 2012-08-14

*** ryanpetrello has joined #openstack-meeting00:01
*** ryanpetrello has quit IRC00:03
*** jaypipes has joined #openstack-meeting00:05
*** ncode has quit IRC00:20
*** sandywalsh has joined #openstack-meeting00:20
*** Mandell has quit IRC00:22
*** runlevel1 has joined #openstack-meeting00:23
*** runlevel1 has quit IRC00:32
*** SumitNaiksatam has quit IRC00:32
*** ayoung has quit IRC00:34
*** ryanpetrello has joined #openstack-meeting00:40
*** hggdh has quit IRC00:40
*** kiffer84 has quit IRC00:43
*** hggdh has joined #openstack-meeting00:45
*** jdurgin has quit IRC00:56
*** oubiwann has quit IRC01:02
*** dwcramer has joined #openstack-meeting01:07
*** charles_ has joined #openstack-meeting01:08
*** johnpostlethwait has quit IRC01:08
*** vladimir3p has quit IRC01:08
*** lloydde has quit IRC01:08
*** charles__ has joined #openstack-meeting01:11
*** charles_ has left #openstack-meeting01:11
*** adjohn has quit IRC01:13
*** Gordonz has quit IRC01:15
*** matiu_ has joined #openstack-meeting01:18
*** ryanpetrello has quit IRC01:24
*** matiu_ has quit IRC01:28
*** littleidea has quit IRC01:29
*** charles__ has quit IRC01:41
*** markmcclain has joined #openstack-meeting01:41
*** littleidea has joined #openstack-meeting01:43
*** johnpur has quit IRC01:48
*** Mandell has joined #openstack-meeting01:54
*** johnpur has joined #openstack-meeting02:16
*** anniec has quit IRC02:17
*** danwent has quit IRC02:17
*** johnpur has left #openstack-meeting02:21
*** ryanpetrello has joined #openstack-meeting02:45
*** rkukura has quit IRC02:47
*** rkukura has joined #openstack-meeting02:48
*** ncode has joined #openstack-meeting02:55
*** maoy has quit IRC03:04
*** nati_ueno has joined #openstack-meeting03:14
*** rohitk has joined #openstack-meeting03:15
*** rohitk has quit IRC03:28
*** rohitk has joined #openstack-meeting03:28
*** danwent has joined #openstack-meeting03:28
*** sacharya has joined #openstack-meeting03:45
*** sdake has quit IRC03:46
*** littleidea has quit IRC04:06
*** matiu has quit IRC04:06
*** chmouel has quit IRC04:06
*** dendro-afk has quit IRC04:06
*** nati_uen_ has joined #openstack-meeting04:09
*** nati_uen_ has left #openstack-meeting04:09
*** nati_ueno has quit IRC04:12
*** rohitk has quit IRC04:17
*** sacharya has quit IRC04:18
*** timello has quit IRC04:23
*** sdake has joined #openstack-meeting04:32
*** ncode has quit IRC04:35
*** markmcclain has quit IRC04:38
*** littleidea has joined #openstack-meeting04:59
*** matiu has joined #openstack-meeting04:59
*** chmouel has joined #openstack-meeting04:59
*** dendro-afk has joined #openstack-meeting04:59
*** littleidea_ has joined #openstack-meeting05:17
*** littleidea has quit IRC05:19
*** matiu has quit IRC05:19
*** chmouel has quit IRC05:19
*** dendro-afk has quit IRC05:19
*** littleidea_ is now known as littleidea05:19
*** timello has joined #openstack-meeting05:23
*** jdurgin has joined #openstack-meeting05:30
*** nati has joined #openstack-meeting05:38
*** nati has joined #openstack-meeting05:39
*** nati is now known as nati_ueno05:40
*** nati_ueno has joined #openstack-meeting05:40
*** nati_ueno_2 has joined #openstack-meeting05:48
*** kpepple has quit IRC05:48
*** kpepple has joined #openstack-meeting05:48
*** nati_ueno has quit IRC05:50
*** nati_ueno_2 has quit IRC05:51
*** nati_ueno has joined #openstack-meeting05:52
*** littleidea has quit IRC05:52
*** s0mik has joined #openstack-meeting05:54
*** zhuadl has quit IRC05:55
*** zhuadl has joined #openstack-meeting05:57
*** zhongyue has joined #openstack-meeting05:58
*** shang has quit IRC06:03
*** shang has joined #openstack-meeting06:07
*** dwcramer has quit IRC06:13
*** EmilienM has joined #openstack-meeting06:14
*** nati_ueno has quit IRC06:16
*** dwcramer has joined #openstack-meeting06:17
*** s0mik has quit IRC06:17
*** eglynn__ has joined #openstack-meeting06:23
*** ryanpetrello has quit IRC06:29
*** dwcramer has quit IRC06:30
*** matiu has joined #openstack-meeting06:33
*** chmouel has joined #openstack-meeting06:33
*** dendro-afk has joined #openstack-meeting06:33
*** dwcramer has joined #openstack-meeting06:36
*** dwcramer has quit IRC06:50
*** dwcramer has joined #openstack-meeting07:00
*** ttrifonov is now known as ttrifonov_zZzz07:10
*** dwcramer has quit IRC07:15
*** dwcramer has joined #openstack-meeting07:23
*** ttrifonov_zZzz is now known as ttrifonov07:38
*** zhongyue has quit IRC07:40
*** ttrifonov is now known as ttrifonov_zZzz07:53
*** blamar has quit IRC07:54
*** ttrifonov_zZzz is now known as ttrifonov07:59
*** darraghb has joined #openstack-meeting08:08
*** derekh has joined #openstack-meeting08:09
*** reed has joined #openstack-meeting09:04
*** reed has quit IRC09:12
*** gongys has quit IRC09:13
*** dwcramer has quit IRC09:54
*** dwcramer has joined #openstack-meeting09:58
*** dwcramer has quit IRC10:03
*** garyk has quit IRC10:04
*** dwcramer has joined #openstack-meeting10:08
*** danwent has quit IRC10:15
*** dwcramer has quit IRC10:16
*** dwcramer has joined #openstack-meeting10:26
*** garyk has joined #openstack-meeting10:35
*** dwcramer has quit IRC10:35
*** dwcramer has joined #openstack-meeting10:41
*** anniec has joined #openstack-meeting10:43
*** anniec_ has joined #openstack-meeting10:46
*** anniec has quit IRC10:49
*** anniec_ is now known as anniec10:49
*** fergal has joined #openstack-meeting11:01
*** carlp has quit IRC11:18
*** martines has quit IRC11:18
*** yamahata has quit IRC11:18
*** yamahata has joined #openstack-meeting11:23
*** carlp has joined #openstack-meeting11:24
*** martines has joined #openstack-meeting11:24
*** rkukura has quit IRC11:43
*** rkukura has joined #openstack-meeting11:43
*** rkukura has quit IRC11:44
*** nijaba has quit IRC11:57
*** gongys has joined #openstack-meeting12:21
*** nijaba has joined #openstack-meeting12:22
*** nijaba has quit IRC12:28
*** nijaba has joined #openstack-meeting12:32
*** nijaba has quit IRC12:32
*** nijaba has joined #openstack-meeting12:32
*** dwcramer has quit IRC12:34
*** AlanClark has joined #openstack-meeting12:50
*** gongys has quit IRC12:56
*** AlanClark has quit IRC12:58
*** AlanClark has joined #openstack-meeting12:58
*** dprince has joined #openstack-meeting13:09
*** joesavak has joined #openstack-meeting13:11
*** markmcclain has joined #openstack-meeting13:19
*** tongli has joined #openstack-meeting13:21
*** markmcclain has quit IRC13:22
*** markmcclain has joined #openstack-meeting13:23
*** ryanpetrello has joined #openstack-meeting13:28
*** ayoung has joined #openstack-meeting13:35
*** mattray has joined #openstack-meeting13:43
*** dwcramer has joined #openstack-meeting13:47
*** mnewby has joined #openstack-meeting13:49
*** maoy has joined #openstack-meeting14:01
*** markmcclain has quit IRC14:03
*** markmcclain has joined #openstack-meeting14:04
*** ncode has joined #openstack-meeting14:04
*** blamar has joined #openstack-meeting14:07
*** blamar has quit IRC14:10
*** mnewby has quit IRC14:12
*** blamar has joined #openstack-meeting14:12
*** ayoung has quit IRC14:17
*** primeministerp has joined #openstack-meeting14:28
*** Mandell has quit IRC14:34
*** sandywalsh has joined #openstack-meeting14:40
primeministerpmorning everyone Hyper-v discussion in 10 minutes14:50
*** zhuadl has quit IRC14:53
*** heckj has joined #openstack-meeting14:54
*** pnavarro has joined #openstack-meeting14:54
*** matwood has joined #openstack-meeting14:59
openstackMeeting started Tue Aug 14 15:00:02 2012 UTC.  The chair is primeministerp. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
primeministerpHi all welcome to the weekly Hyper-V meeting15:00
*** Gordonz has joined #openstack-meeting15:00
primeministerpI sent out the agenda for discussion15:00
primeministerpto start we'll discuss the submission15:00
primeministerp#topic Hyper-V code submission15:00
*** openstack changes topic to "Hyper-V code submission"15:00
*** dwcramer has quit IRC15:01
primeministerpalexpilotti: submitted the code yesterday15:01
primeministerpas of last night we have successfully passed throught he jenkins and smokestack gates with a +115:01
primeministerpsome comments have be made regarding some additional formating15:01
primeministerpand we are in the process of the cleaning that up and resubmitting15:01
primeministerpalexpilotti: do you want to raise the point on one of the comments15:02
primeministerptr3buchet: alexpilotti or are you planning to reply to the comments you had questions on directly?15:02
primeministerpalexpilotti: that was for you15:03
primeministerptr3buchet: sorry about that15:03
* primeministerp waits15:04
*** rafaduran has quit IRC15:07
primeministerplet's move on until alexpilotti is back15:07
primeministerpalexpilotti: so based on those comments the only thing to fix is the indents in the volume.py?15:08
primeministerpalexpilotti: I've asked pedro to take a look at the indents15:09
pnavarroprimeministerp: I'm on it15:09
primeministerppnavarro: i guess alexpilotti may have already done it15:10
primeministerphe's skyping me while correcting it15:10
*** dolphm has joined #openstack-meeting15:10
alexpilottiprimeministerp: pnavarro sotrry guys I was answering those comments15:11
primeministerper great15:11
primeministerpmtaylor: any chance for some +1 love?15:11
primeministerpvishy: +1 for hyper-v?15:11
alexpilottimtaylor: they ask to get rid of get_connection in driver.py15:12
alexpilottimtaylor: we kept it for compatibility w the essex code base. Do we have to remove it?15:12
primeministerpvishy: ^^15:12
primeministerpalexpilotti: if we can't get a response in this meeting, send an email to the list asking15:13
primeministerpok I'll move on15:13
primeministerp#topic hyper-v ci15:14
*** openstack changes topic to "hyper-v ci"15:14
primeministerpso the hyper-v ci has some issues, suffered a hw failure yesterday15:14
primeministerpWe'll be setting up to start the base unit tests on hyper-v to trigger from zuul15:14
primeministerpand start building from that15:15
primeministerpalso we'll shooting for everything to be in place hopefully in the next 2 weeks15:15
alexpilottiI removed get_connection from our code base, I'll waut for more comments to commit, as it is not affecting at all the code base15:15
primeministerpalexpilotti: so it was completely unneeded?15:16
primeministerpeven for essex compat?15:16
alexpilottiprimeministerp: for essex it is15:16
primeministerphopefully we can get some comments15:17
mtayloralexpilotti: hey15:17
primeministerpmtaylor: hey now15:17
mtaylorso, is essex compat needed?15:17
alexpilottimtaylor: well, we can keep a separate driver.py15:18
mtaylorI mean, this isn't going to get merged back into stable/essex...15:18
alexpilottimtaylor: for sure, it's just for our internal tests15:18
mtaylorah, I suppose you could - but why not just steer people towards folsom for hyperv support?15:18
alexpilottimtaylor: but since it was a 2 lines innocuous method, I just left it there15:19
primeministerpwell i guess that's a discussion we could have15:19
primeministerpshould be able to get backported to essex15:19
primeministerpor do we not want to care15:19
*** Gordonz has quit IRC15:19
alexpilottimtaylor: anyway, I just removed it, will send it w the next review15:19
primeministerpwe can leave the essex integration sort of where it is15:19
*** Gordonz has joined #openstack-meeting15:20
mtaylorcool cool15:20
primeministerpfor hyper-v specifically we were always targeting folsom as the reintegration point15:20
primeministerpalexpilotti: do we want to vote15:20
mtayloryeah - so, backported to essex...15:20
primeministerpmtaylor: what's your take?15:20
mtaylorwould be adding a feature to stable/essex15:20
mtaylorand I can say it just flat wont' happen15:20
primeministerpthat's an easy answer to accept15:21
primeministerpalexpilotti: remove it and let's move on15:21
primeministerpmtaylor: how's about some +1 love then once we address the comments ;)15:21
mtaylorprimeministerp: I'll do my best15:22
primeministerpmtaylor: all i can ask15:22
primeministerpmtaylor: every bit is appreciated15:22
primeministerpmoving on then15:22
primeministerp#topic puppet/hyper-v/openstack15:22
*** openstack changes topic to "puppet/hyper-v/openstack"15:22
primeministerpso I've got the beginings of a puppet manifest for hyper-v/openstack15:23
primeministerpI've spoke with our friends at puppetlabs15:23
*** matwood has quit IRC15:23
*** markmcclain has quit IRC15:23
primeministerpthey've been extremely helpful in some overall direction15:23
primeministerpas well as put me in touch with some others doing puppet on windows.15:23
*** jaypipes has quit IRC15:24
*** hggdh has quit IRC15:24
primeministerpI was hoping someone from CERN was available15:24
primeministerpas maybe we could tap them for some more testing and assistance on the puppet manifest15:24
primeministerpI'll make note to reach out to Jose and see if there's interest in assisting15:24
primeministerpif that's anything else that needs to be addressed?15:25
primeministerppnavarro: alexpilotti?15:25
alexpilottiprimeministerp: just waiting for somebody to comment15:25
primeministerpalexpilotti: not sure if we're going to get it15:26
alexpilottiprimeministerp: on the code15:26
primeministerplet's ask15:26
*** hggdh has joined #openstack-meeting15:26
primeministerpanyone any comments on the Hyper-V code that we can address now?15:26
*** littleidea has joined #openstack-meeting15:27
primeministerpthis is definately the forum for any concerns to be addressed15:27
alexpilottimtaylor: how does it work with the comments? if the gerrit sum is > 0 we are simply in?15:27
alexpilottiI left a comment on #Openstack-dev if anybody wants to discuss it here15:28
primeministerpwe'll wait a few more before i close the meeting15:29
*** jaypipes has joined #openstack-meeting15:29
primeministerpjaypipes: jay!15:29
primeministerpjaypipes: mind answering a quick question about the gerrit cycle15:29
jaypipesprimeministerp: sure thing15:29
primeministerpjaypipes: if we are >0 does that mean we will offically be in15:29
primeministerpor does some other magic have to happen15:30
primeministerpis there a minimum number we have to hit15:30
*** dwcramer has joined #openstack-meeting15:30
jaypipesprimeministerp: you need to get 2 +2s from core reviewers and complete the Jenkins gate successfully15:30
primeministerpjaypipes: thank you15:30
primeministerpso time to start sending gifts to core reviewers15:31
primeministerpjust kidding15:31
pnavarroI can propose an spanish jambon...15:31
primeministerppnavarro: that won't make out of my kitchen15:31
primeministerpif it's what i think it is15:31
primeministerpalexpilotti: is that good enough?15:32
primeministerpalexpilotti: of an answer?15:32
alexpilottiprimeministerp: I got the same answer on #Openstack-infra15:33
primeministerpo perfect15:33
primeministerpok then15:33
primeministerpif no one has anything else to add, i'll call the meeting15:33
alexpilottiprimeministerp, jaypipes: given that the deadline is tonite, do we need two core reviewers doing it today?15:33
*** danwent has joined #openstack-meeting15:33
alexpilottiprimeministerp, jaypipes is there a list of core reviewers?15:33
primeministerpalexpilotti: ^15:34
jaypipesalexpilotti: yes, ASAP.15:35
*** lloydde has joined #openstack-meeting15:35
alexpilottiprimeministerp, jaypipes how can we get who are the reviewers today?15:36
alexpilottiprimeministerp: jaypipes that list arrives to Aug 1st15:36
jaypipesalexpilotti: all of nova core is on today. :)15:36
primeministerpjaypipes: awesome15:36
jaypipesalexpilotti: it's crunch time.15:36
primeministerpthanks jay15:37
alexpilottijaypipes: so, who can we ping for that?15:37
primeministerpalexpilotti: i believe what he means is if we submit it someone will have to review it15:37
alexpilottijaypipes: is Tiago Mello a core reviewer?15:37
primeministerpjaypipes: please clearify if i'm wrong15:37
vishyalexpilotti: the get_connection compatibility is just for people that need backwords compatibility15:37
vishy* drivers that need15:38
primeministerpvishy: thanks for joining15:38
vishysince hyper-v wasn't aound in essex I don't know that it matters15:38
alexpilottivishy: that's why we left it there. We just voted to remove it anyway15:38
vishyoh, cool15:38
jaypipesalexpilotti: vishy, bcwaldon, blamar, markwash, Johannes, _0x44, jkoelker, jk0, maoy, mikal, soren, termie15:38
alexpilottivishy: tx :-)15:38
primeministerpalexpilotti: so are were clear on what needs to be done then?15:39
alexpilottivishy: is there something we can do to hep for the review?15:39
*** matiu_ has joined #openstack-meeting15:39
*** matiu_ has joined #openstack-meeting15:39
*** dendro-afk is now known as dendrobates15:39
primeministerpvishy: other than addressing the comments asap15:39
jaypipesalexpilotti: answer comments and questions quickly and keep on reviewers to do the reviews... that's about it.15:39
vishyalexpilotti: doubtful, there are just a million really big reviews that dropped right at the end15:39
pnavarrovishy: you know pizzas, sodas, massages...15:40
alexpilottivishy: sorry for the silly qestion: does it mean that we will reviewed in case in the forthcoming days, or that we could not make it for Folsom?15:40
*** markmcclain has joined #openstack-meeting15:41
*** hggdh has quit IRC15:41
vishyalexpilotti: we will decide whether to give it an FFE if it doesn't make it today15:41
primeministerpvishy: and FFE is exactly what?15:41
*** danwent has quit IRC15:41
primeministerpFeature Freeze Exemption?15:41
vishyor maybe it is Exemption :p15:42
*** Hitesh has joined #openstack-meeting15:42
primeministerpvishy: hehe15:43
Hiteshprimeministerp: Hi Peter15:43
Hiteshpnavarro: Hi Pedro15:43
primeministerphowdy hitesh15:43
alexpilottiHitesh: hi!15:43
Hiteshprimeministerp: Sorry for being late15:43
Hiteshalexpilotti: Hi Alessandro15:44
alexpilottijaypipes: until what time do we have to commit updates to the review?15:44
primeministerpalexpilotti: ok then, i think we know what we need to do15:44
alexpilottijaypipes: midnight PDT?15:44
jaypipesalexpilotti: I think it might be up to vishy15:45
Hiteshprimeministerp: once the discussion done, please let me know to do iteams :)15:46
primeministerpHitesh: test the new code15:46
alexpilottivishy: until what time do we have to commit updates to the review? Midnight Pacific time?15:46
Hiteshprimeministerp: Ok :)15:46
*** dwcramer has quit IRC15:46
primeministerpHitesh: you can also assist w/ puppet manifests for hyperv if you want15:47
Hiteshpnavarro: currently we are not developing any feautre right?15:47
Hiteshprimeministerp: ok :)15:47
alexpilottivishy: sorry, reformulating: until what time can we commit updates to the review? Midnight Pacific time?15:47
primeministerpHitesh: I suggest reading throught the meeting notes once we're done so you can catch up15:47
Hiteshprimeministerp: Sure15:47
Hiteshprimeministerp: will do15:47
*** rnirmal has joined #openstack-meeting15:48
*** nati_ueno has joined #openstack-meeting15:48
primeministerpHitesh: then take questions to the usual channel15:48
primeministerpif that's it15:49
primeministerpi know there's still the open question to vish alexpilotti15:49
primeministerphowever let's followup outside of this channel15:50
*** matwood has joined #openstack-meeting15:51
primeministerpok closing the meeting folks thanks for the comments, please take additinal comments to #openstack-hyper-v15:52
*** 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"15:52
openstackMeeting ended Tue Aug 14 15:52:35 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-14-15.00.html15:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-14-15.00.txt15:52
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-14-15.00.log.html15:52
*** cp16net is now known as cp16net|away15:52
*** AndrewWeiss has joined #openstack-meeting15:56
*** reed has joined #openstack-meeting15:57
vishyalexpilotti: keep doing updates as long as people request them :)15:58
primeministerpvishy: perfect15:58
primeministerpvishy: thanks15:58
alexpilottivishy: tx!15:58
*** hggdh has joined #openstack-meeting16:00
*** sdake has quit IRC16:01
*** sdake has joined #openstack-meeting16:01
*** ayoung has joined #openstack-meeting16:05
*** s0mik has joined #openstack-meeting16:09
*** Mandell has joined #openstack-meeting16:10
*** cp16net|away is now known as cp16net16:13
*** oubiwann has joined #openstack-meeting16:17
*** oubiwann has quit IRC16:17
*** oubiwann has joined #openstack-meeting16:17
*** nati_ueno has quit IRC16:22
*** nati_ueno has joined #openstack-meeting16:25
*** anniec has quit IRC16:28
*** jdurgin has quit IRC16:29
*** nati_ueno has quit IRC16:30
*** johnpur has joined #openstack-meeting16:30
*** AndrewWeiss has quit IRC16:32
*** joesavak has quit IRC16:42
*** mnewby has joined #openstack-meeting16:42
*** dprince has quit IRC16:53
*** derekh has quit IRC16:54
*** AndrewWeiss has joined #openstack-meeting17:02
*** zul has quit IRC17:03
*** Hitesh has quit IRC17:05
*** zul has joined #openstack-meeting17:05
*** AndrewWeiss has quit IRC17:12
*** dolphm has quit IRC17:13
*** sandywalsh_ has joined #openstack-meeting17:13
*** darraghb has quit IRC17:13
*** sandywalsh has quit IRC17:14
*** bcwaldon has joined #openstack-meeting17:14
*** lostsoul has quit IRC17:20
*** jjm3 has quit IRC17:20
*** anniec has joined #openstack-meeting17:23
*** anniec_ has joined #openstack-meeting17:23
*** dprince has joined #openstack-meeting17:24
*** anniec has quit IRC17:27
*** anniec_ is now known as anniec17:27
*** lloydde_ has joined #openstack-meeting17:34
*** jdurgin has joined #openstack-meeting17:34
*** lloydde has quit IRC17:37
*** rohitk has joined #openstack-meeting17:40
*** garyk has quit IRC17:49
*** marek_ has joined #openstack-meeting17:55
openstackMeeting started Tue Aug 14 18:00:30 2012 UTC.  The chair is heckj. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
heckj#topic agenda at http://wiki.openstack.org/Meetings/KeystoneMeeting18:01
*** openstack changes topic to "agenda at http://wiki.openstack.org/Meetings/KeystoneMeeting"18:01
heckjWe're closing in on the feature freeze end of this week18:01
heckjThere's a few reviews up that need some lovin'18:02
heckjdolphm, ayoung - if you can take a few minutes over the next two days and review all the open keystone reviews18:02
heckjdolphm has a V3 API initial cut up for review18:02
heckjlooking pretty good.18:03
heckjI think we're going to want to continue to move that forward while we keep master relatively locked down with feature requests - any recommendations on how to accomplish this?18:03
ayoungwill do18:03
ayoungif he can get an excpetion on policy, can I get one on token revocations?18:04
*** harlowja has joined #openstack-meeting18:04
heckjayoung: I was trying to avoid the exceptions and thinking about doing something with feature branches - not sure what mtaylor has as a possibility there18:04
heckjayoung: however18:05
heckjayoung: i think the token recovation addition is worthwhile to get added in during the freeze if we get it in soon18:05
*** dolphm has joined #openstack-meeting18:05
ayoungheckj, we are close, but I would rather get it right, than rush to get it in under the deadline, and then do a slew of bug fixes18:05
mnewbyayoung: seconded.18:05
dolphmayoung: pki revocation?18:05
ayoungmnewby is helping me out, and we've got PKI revocation scared....18:05
heckjayoung: totally with you - just do'nt want to add it one week prior to RC cut if we can avoid it18:06
ayoungheckj, we can have it ready for review in the next couple of days, I think18:06
mnewbyheckj: I concur18:06
heckjsounds good18:06
ayoungheckj, should we go through and triage the open requests?18:06
heckjayoung: do you have a question about one? (not sure what to triage there…)18:08
ayoungI'll take a look offline18:08
heckj#topic Grizzly Design Summit18:09
*** openstack changes topic to "Grizzly Design Summit"18:09
heckj#link http://etherpad.openstack.org/GrizzlyKeystoneSessions18:09
heckjWe have some suggestions for topics in Grizzly design summit18:09
heckjTTX is getting set up with general scheduling - keystone meetings will be mostly on monday, some tuesday18:10
heckjLast summit I set (almost) all the sessions - this time through I'm going to open it up to y'all to suggest and I'll help schedule coordinate the results18:11
heckjOther than what's the etherpad today - are there any burning topics folks want to bring up at the summit?18:11
ayoungHow well understood is Keystone by the community, and how  attended do you think our sessions will be based on last time?18:11
heckjI think it's fairly poorly understood actually - many folks have deployment questions about it and "can I use it too…" assuming there are more backends than there are18:12
heckjLast summit, there were a few very vocal folks - but while there was significant attendance, there was little in the way of diverse feedback18:12
ayoungshould we have an intro to Keystone session for the rest of the people there?18:12
heckjayoung: would be a very good idea18:13
ayoungI gave a presentation to the Boston user group.  My slides are here:18:13
heckjayoung: we're screwed a bit by the scheduling - most of the general "intro to" workshops are concurrently scheduled with our first day18:14
heckj#link http://adam.younglogic.com/presentations/KeystoneFolsom/18:14
ayoungWe can use that as the starting point.  It is probably a good thing for us all to start on the same sheet of music WRT Keystone anyway18:14
mnewbyI haven't thought it out too much, but I would like to see some changes to keystone internals to make integration with non-sql backends less painful.18:14
heckjayoung: nice - I'll steal some of that if it's OK with you18:14
dolphmheckj: ayoung: folsom summit attendance was about double, on average, vs essex attendance, for keystone sessions (not sure how that compares to the size increase of the overall conference?)18:14
ayoungheckj, I can send you a link to the original Open offic presentation18:14
heckjmnewby: sounds like an excellent brainstorming session18:14
mnewbyheckj: I would agree.18:15
dolphmmnewby: please share! i'm making some such changes18:15
heckjdolphm: I think it matched the overall the growth18:15
mnewbydolphm: Share here?  Or discuss offlin?18:15
ayoungmnewby, ^^18:16
heckjmnewby: if you've got some early thoughts, feel free to start some email threads too18:16
heckj(or here too)18:16
dolphmmnewby: up to you -- i just want to know what's on your mind18:16
ayoungdolphm, I suspect it is the case where there is some centralize auth server for the organization that is read only WRT openstack, but you need to keep group info local...hybrid LDAP SQL  for example18:17
ayoungusers come out of LDAP,  projects and roles are local.  Users are read only.  Authentication uses LDAP.18:17
heckjayoung: that's coming out as a very common use case18:17
mnewbyBriefly, Keystone exposes a driver model for identity to aid in extensibility, but the way the driver is used is really only useful for an sql or memory-backed service.18:17
dolphmayoung: so, a more granular breakdown of catalog | identity | tokens | policy18:17
ayoungdolphm, probably more like the ability to split identity18:18
ayoungmaybe authZ vs authN18:18
mnewbyI'd like to see a cleaner separation between z and n.18:18
mnewbyThey are really separate contexts, and mixing them makes it difficult to ensure quality code.18:19
dolphmpolicy is theoretically Z, and identity is theoretically N -- what do you want to move? roles?18:19
dolphmin v3: identity = domains, projects, users, credentials & roles18:20
ayoungdolphm, probably users18:20
dolphmayoung: out of identity?18:20
ayoungdolphm, I think more the ability to delegate it from identity.18:21
ayoungeither it is going to be in the same DB as the rest or18:21
heckjayoung: let's do this carefully - if at all. I think we need some hybrid backends here, but it's not clear how we should make that possible18:21
ayoungit is going to be read only from remote18:21
ayoungheckj, hence the session to brainstorm18:21
ayoungwe don't need to solve it now.18:21
*** dwcramer has joined #openstack-meeting18:22
heckjIn particular, I want to see what we can do to allow roles and/or projects to come from groupings in read-only source (active directory LDAP) - right now it's just a freaking Identity backend, but it's all together reasonably18:22
heckjcool - yeah18:22
ayoungActually, that was what I had in minde with the AD integration.  Maybe we should merge that session.18:22
heckjayoung: yeah - I'd like to come into that session with some concrete work in hand to inform the discussion18:23
heckj(that's my plan, anyway)18:23
ayoungrelated but different:  once the policy mechanism is in place, will we need to provide som precanned policies to support common cases?18:23
dolphmayoung: policies for not-keystone?18:24
ayoungdolphm, yes18:25
heckjayoung: That was what I'd asked liemn to help pull together, but he's disappeared this past few weeks18:25
dolphmayoung: i mean, other projects are already publishing precanned policy.json's18:25
ayoungliemn is off of Openstack, I thought.18:25
dolphmheckj: ^^18:25
heckjayoung, dolphm : I wanted to pull them all together and get at least a basic suggested deployment documented18:25
heckjdolphm: yeah - got that note18:25
ayoungdolphm, how about a session which is an over view of the policy mechanism, to include the current state at the start of grizzly development, and what is going to be expected in working with the other projects?18:26
primeministerpheckj: that's what i'm talking about18:26
dolphmheckj: i don't think we should document much more than how to setup a policy for a service -- it's up to the service to provide the actual policy blob18:26
mnewbydolphm: agreed18:27
dolphmheckj: i don't want our docs to get into how-to-deploy-openstack, even though we're at the core of it18:27
ayoungdolphm, yes...but, I think we also need to be prepared to answer other people's policies questions. It would be good if we were all on the same page.  Train-the-trainer?18:27
primeministerpheckj: ayoung: please feel free to include me on any AD dicussions18:27
heckjdolphm, mnewby fair enough - but I think openstack as a global project *needs* that information, and some suggestions on how to solve some of those common issues will be coming from us18:27
dolphmheckj: can we just point to a higher level doc at openstack.org?18:28
heckjprimeministerp: so far, they18:28
dolphmheckj: maybe a specific section18:28
ayoungprimeministerp, this is Summit planning.  So we plan on kidnapping you there and duct taping you to a seat to answer the windows specific stuff.  Or provide an alternate that we can kidnap18:28
dolphmof something18:28
dolphmwhich we can write :P18:28
mnewbyheckj, dolphm: An RFC for how to do policy, without getting into specifics?18:28
heckjprimeministerp: they've been happening (or not - all quiet) in openstack-operators mailing list, and discussions here in IRC18:28
heckjmnewby: I want to coordinate with someone doing genearl openstack docs (or just do it myself) to get that information genearlly available18:29
mnewbyheckj: +118:29
heckjI don't want it to be "keystone docs" , but "how to use Keystone in Openstack" docs18:29
primeministerpheckj: well feel free to tap me as a resource18:29
primeministerpif i can help i will18:29
heckjprimeministerp: will do, thank you18:29
mnewbyheckj: I think that's a good approach.  That way service-specific issues can be documented but don't necessarily have to take keystone resources to do it.18:30
ayoungso it sounds like we need to have two types of sessions,  those for the rest of the openstack community, and then planning sessions for us18:30
ayoungWe also probably need to identify where it would be useful to have keystone developers listening in on other sessions.18:31
ayoung"Intel Prep of the Battlefield" if you forgive the Army term18:31
dolphmayoung: that would be awesome18:32
heckjayoung: +118:32
heckjIn the past, I've found that I had to do that in the week prior to the summit, because there wasn't general visibiltiy into potential sessions18:32
heckjI'll send an email to ttx and see what we can coordinate to make that easier to find out this time18:33
ayoungyeah, I am guessing that it is going to be last minute.18:33
primeministerpheckj: may I ask a question?  How formal is the discussion around AD?18:33
dolphmayoung: it'd be nice to have all session planner people throw some keywords into their session descriptions a list of "other relevant projects" or whatever18:33
heckj#topic open discussion18:33
*** openstack changes topic to "open discussion"18:33
dolphmSo, even though its a Quantum session, it's about authz, so "relevant projects: Keystone"18:33
ayoungprimeministerp, I was at first planning a break out session of it,  but it looks like it makes sense to link in to a discussion about how to split identity out into readonly and writable segments18:33
primeministerpheckj: did you mention any of it to any msft people you may have met at meetups in seatle?18:33
heckjprimeministerp: not terribly formal at this point - some questions in the past, notes from folks who've been implementing "Identity" backend/drivers18:33
primeministerpheckj: simple because it's part of the discussion here18:34
primeministerpas work they are looking to do for Grizzley18:34
dolphmayoung: i guess i'm lost on the need to split by read only / write required ... if you don't want write operations... don't implement them? and 501's get raised appropriately18:34
heckjprimeministerp: with the local (seattle) meetups, only that there was some work going on there, but nothing specific got drawn out or brought up18:34
ayoungdolphm, nah, I mean the LDAP stuff I was talking about aboce18:35
primeministerpheckj: I believe you met yigal18:35
heckjprimeministerp: could easily have - I don't always remember everyone I meet there I'm afraid :-)18:35
primeministerpheckj: we can discuss more off meeting if interested, but I think it would be worth while to sync up18:36
heckjprimeministerp: sure, happy to18:36
primeministerpheckj: and make sure my mgmt is planning on duplicating existing efforts18:36
heckjprimeministerp: I've been hesitant to drive any discussion until I have some time (or resources) to implement, but if folks are struggling to do that work, I want to make it happen and help there18:36
primeministerpheckj: well i have ad implemented and am a bit off from giving people access "today" but can easily arrange access to infrastructure18:37
primeministerpheckj: to speed efforts18:37
heckj(I'd planned for us to do that work this past release team, but didn't get the time to make it happen)18:38
primeministerpanyway thx for the time18:38
ayoungI wonder if we can get the folks that did that Federation proof-of-concept to present18:40
ayoungI'd like to understand it a little better.18:40
heckjayoung: who did that?18:41
ayoung"David Chadwick" <d.w.chadwick@kent.ac.uk>18:42
ayoungSubject: Federated Access to Keystone18:42
heckjayoung: let's definitely see if we can get him to talk about it!18:42
ayoungI think what they have done is removed tokens, and used SAML for all services.18:43
heckjayoung: did they make their own auth_… middleware for other openstack services?18:44
ayoungThere are four docs in drop box18:44
heckjayoung: link?18:44
ayoungheckj, damned if I know,  I am not signing up for a drop box account just tored their docs!18:44
ayoung1 sec18:44
heckjyeah - they definitely did their own middleware18:45
ayoungah..loks like I can read them now18:45
heckjspecs mostly, description of operation18:46
ayoungI think it is their own middleware...and that leaves the question of how they do  service catalog support18:46
*** kindaopsdevy has joined #openstack-meeting18:46
heckjyeah - I presume they're embedding it somewhere, but lord knows where18:46
heckjayoung: I'm mostly interested in their driving use cases that resulted in this implementation18:47
ayoungheckj, so we can have that integrated in to the Federation session18:47
heckjayoung: yeah18:48
ayoungOne thing I am surprised we have not been bugged about is providing a store for user preferences from the WebUI.18:50
heckjayoung: so far they (horizon folks) have been stashing them into session cookies and keeping it pretty light18:52
ayoungOK...well, if they don't ask, we won't offer18:52
heckjwe've got enough to pull off with credentials :-)18:52
heckjAnyone have other topics? I need to kick out into other meetings...18:53
*** s0mik has quit IRC18:53
mnewbynothing from me.18:54
ayoungI need to get back to PKI revocation...and so does mnewby18:54
dolphmheckj: quick api consistency Q: the two attributes Credential.data and Policy.policy should have the same attribute name, i'm thinking, and the spec is unclear whether Credential.data is actually supposed to be serialized or not?18:54
*** s0mik has joined #openstack-meeting18:55
heckjdolphm: I wasn't entirely sure what credentials needed there - so fundamentally, I don't know18:55
dolphmheckj: as i recall, the description describes Credential.data as a serialized blob, but it's just a deeper json tree in the example18:55
ayoungBTW, on the V3 API,  should we make it explicit that the client needs to send the "Content-Type:application/json" header18:56
heckjdolphm: I think the only hard example we really have are the EC2 credentials, and a desire to host SSH keys for logging into instances18:56
heckjayoung: what's your preference?18:57
dolphmheckj: i think they should both just be serialized blobs then18:57
heckjdolphm: kk18:57
heckjI need to skip out guys - be online later...18:58
*** 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:58
ayoungheckj, I think so...I need to research what the HTML/HTTP spec says about it, but I doubt JSON by default is the intention18:58
dolphmheckj: /salute18:58
openstackMeeting ended Tue Aug 14 18:58:11 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-14-18.00.html18:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-14-18.00.txt18:58
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-14-18.00.log.html18:58
heckjayoung: thanks18:58
*** Shrews has joined #openstack-meeting18:58
*** markmcclain has quit IRC18:59
*** markmcclain has joined #openstack-meeting19:00
clarkbmtaylor: still stuck with other things?19:00
*** vladimir3p has joined #openstack-meeting19:01
*** heckj has quit IRC19:02
mtaylorclarkb: yes19:03
clarkbjeblair LinuxJedi shall we meet? anyone else?19:04
jeblairi'm not sure we can meet without mtaylor19:05
jeblairi asked someone to show up today specifically so that mtaylor could address his concerns19:05
jeblairit's unfortunate he can't attend.19:05
jeblairmy work is also blocked waiting on mtaylor, so that's not useful either.19:06
*** ohnoimdead has joined #openstack-meeting19:06
mtaylorok. I'm here19:07
jeblairglad to hear it19:07
harlowjahey, this is the CI meeting rightttt??19:08
openstackMeeting started Tue Aug 14 19:08:12 2012 UTC.  The chair is mtaylor. Information about MeetBot at http://wiki.debian.org/MeetBot.19:08
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:08
mtaylorwhat's up folks?19:08
harlowjaso, only thing i have to bring up is possibly, https://bugs.launchpad.net/openstack-ci/+bug/103596619:08
uvirtbotLaunchpad bug 1035966 in openstack-ci "Move 'anvil' to stackforge" [Undecided,New]19:08
harlowjai'm fixing it up/cleaning it up for folsom and might be useful to show up in stackforge instead of y! organization19:09
* mtaylor look at bug...19:09
harlowjak, anvil is similar to devstack for those that are wondering19:10
harlowjabut i've tried to add features that devstack doesn't have and tried to refactor it (in python) with other goodies as well19:10
mtaylorah. hrm.19:10
harlowjaexample outputs are attached to that bug...19:10
harlowjabut its a useful tool, so thats why i think it belongs on stackforge, being that the forge site seems like the right place?19:11
mtayloryeah - so, are there any concerns?19:12
harlowjanot from me (i'd wait on moving it for say another week though as i finish up some fixes in it)19:12
harlowjaidk about the devstack guys but devstack seems like it should also be on stackforge, idk19:12
harlowja*i won't push that, but seems to make sense19:12
mtaylorseems to make general sense to me19:14
mtaylormy main concern would be in what testing for it would look like19:14
*** novas0x2a|laptop has joined #openstack-meeting19:15
harlowjaya, unit level stuff would make sense, the capabiltiiy to do more than that could be added on (setting up openstack components on diffferent distros...), but that might not be useful since thats approaching integration tests (but idk)19:15
mtaylorexactly, and that winds up starting to be a larger engineering effort19:16
mtaylorI'd like to keep it to unittesty stuff, because that's all stuff you can manage pretty easily by just putting in patches to the puppet repo19:16
harlowjathats fine with me19:16
mtaylorkk. then I don't see any difference between this and heat from a suitability perspective19:17
jeblairmtaylor: is there documentation on how a project joins stackforge?  and what is expected, as far as self-managing and ci?19:17
harlowjaya, that'd be useful also, cause i wasn't really sure :)19:17
mtaylorjeblair: there is not. so far it's all been one off requests19:17
mtaylorjeblair: and I believe the expectation is that the project should be mostly self-suffient19:18
mtayloriirc, the fine folks at heat added all of their job-builder and zuul config themselves19:18
jeblairmtaylor: ok.  i thought there used to be docs, but i couldn't find them.19:18
* LinuxJedi thought I wrote them too, I guess I thought about writing them and it didn't happen19:18
* mtaylor could be wrong about the docs19:19
*** johnpur has quit IRC19:19
harlowjamight be useful to have more docs, i could see alot of 'tools' or similar wanted to get on that site19:19
harlowjasince it seems to be the centeral openstack useful tools 'place'19:19
jeblairit's not linked19:19
harlowjaright, i just wonder if its useful to have a what could showup on stackforge list, but idk19:21
harlowja' similar to that of the main OpenStack project but for use with projects that are not under the main OpenStack umbrella.' is pretty vague ;)19:21
jeblairharlowja: so how to create the jenkins jobs is not very well documented at the moment, you may have to do some digging.  it's all in the openstack-ci-puppet repo.19:22
jeblairharlowja: one of us will have to do the initial import into gerrit, but you should be able to self-manage the jenkins bits after that.19:22
harlowjacool beans19:22
*** marek_ has quit IRC19:22
mtaylorjeblair: any other concerns from your end?19:23
jeblairi think that covers it19:24
mtaylorcool cool. then harlowja we'll sync up with you on getting you imported and stuff19:25
harlowjathx guys!19:25
*** mrmartin has joined #openstack-meeting19:25
mtaylorjeblair: you mentioned being blocked on me ...19:26
jeblairi have made no progress on backups, other than to find out that hpcloud requires custom novaclient in order to use their block storage19:26
mtaylorawesome. so, apparently that's a diablo v. folsom issue19:27
jeblairi don't feel that's appropriate for a project level activity like this -- they're not even available without an hpcloud account.19:27
mtaylorin that novaclient apparently has ceased supporting diablo or something19:27
jeblairmtaylor: the bug indicated it was related to keystone.19:27
mtaylorI agree - I do not think that we should use a modified novaclient19:27
mtaylorjeblair: yeah, apparently something changed between now and then and novaclient doesn't support the old way at all?19:29
jeblairmtaylor: that's vague19:29
mtaylorapparently block storage is also having data corruption issues at the moment19:30
mtaylorso it might not be terrible that we can't get it19:30
jeblaireffectively, we have no viable option for off-site backup (let's define that as at least not the same cloud provider as our main servers)19:30
mtaylorjeblair: what about copies to multiple backup hosts, even if it's on ephemeral drives?19:31
mtaylorjeblair: like, backup to rax and hp az{1,2} - and it would take a 4-way failure to take us all the way to dead19:31
jeblairmtaylor: well, i'm unaware of a site-level raid system -- each time hpcloud loses a node, we would need to copy the data back from another host19:32
jeblair(i don't think that's feasible -- no one here is actually interested in backups, so anything that relies on anyone doing anything by hand isn't going to work)19:34
jeblairmtaylor: so do you expect the situation with hpcloud to change, or do we just need to write it off completely?19:35
mtaylorjeblair: I do not expect the situation with hpcloud to change any time in the near future19:36
mtaylorso if the lack of block storage access means that our current plan is unworkable, then I think we will need to come up with a new plan19:36
mtaylorwhich is quite sad19:36
jeblairit is.  hpcloud foils every attempt of ours to use it.19:36
LinuxJedimaybe we should get physical kit from somewhere for this?19:37
jeblairyeah, that may be a good idea.19:37
jeblairmtaylor: got anything laying around?19:38
mtaylorjeblair: hrm19:39
* LinuxJedi has a beat-up old Pentium 4 laptop in the loft. Probably more reliable19:39
jeblairother options: ask other partners if they have something appropriate, or punt until the foundation is formed19:39
jeblair(presumably the foundation will have an interest in this, and a budget to procure commercial solutions if necessary)19:39
jeblairokay, well, if anyone has ideas, let us know.  :)19:40
LinuxJediwe all work for companies with data centres with lots of kit.  Surely we can punt for a half-rack or something19:40
mtaylorit's not just kit19:41
mtaylorbare metal needs to be managed19:41
LinuxJeditrue :/19:41
jeblairtrue, a backup server with a degraded raid array is no fun19:41
*** tgall_foo has joined #openstack-meeting19:41
* mtaylor will ask around19:41
* jeblair anticipates mtaylor getting the response "why not use hpcloud?"19:41
LinuxJedilol! :)19:42
creihtmtaylor: you should store backups in swift datastores :)19:42
jeblaircreiht: we considered that -- however, that means having read-write credentials to the data store on the hosts being backed up...19:42
jeblaircreiht: we'd like our backups to be append-only19:42
jeblaircreiht: if you know of a swift provider that supports an append-only configuration, i'm all ears.  :)19:43
creihtahh heh19:43
jeblairso how about some good news?  swift is part of the devstack gate now19:44
jeblairi set up bitrot jobs in jenkins: https://jenkins.openstack.org/view/Bitrot/19:44
jeblair(i'll email the ML about that after the new ones have their first run)19:44
mtaylorjeblair: woohoo!19:45
jeblairi'd like to get someone/group set up to receive email alerts when those fail.  maybe QA team, maybe core devs, maybe PTLs, maybe stable-maint...19:45
mtaylorjeblair: ++19:45
mtaylorttx: around? thoughts on above? ^^ jaypipes  ?19:45
jeblair(if not, i'll bring it up on the ML)19:46
jeblairso in dog-fooding cherry-pick mode, i realized that having gerrit-git-prep do merges while the repo is cherry-picking is problematic19:46
mtaylorjeblair: oh, heh19:47
jeblairif you approve a series of changes, once the first one is cherry-picked, the subsequent ones can't merge because they conflict19:47
jeblair(because an older version of the cherry-picked patch is in their ancestry)19:47
*** danwent has joined #openstack-meeting19:47
mtaylorjeblair: I noticed that19:47
mtaylorjeblair: when doing puppet this weekend, but didn't make the causation connection19:48
jeblairso, rather than adding complexity to gerrit-git-prep for that, i started moving that complexity into zuul19:48
*** rohitk has quit IRC19:48
mtaylorjeblair: saw that come through - looking at it now19:48
jeblairthat's a change so that zuul starts managing copies of git repos, and whenever it wants a change tested, it merges/cherry-picks as appropriate whatever changes it wants tested19:48
jeblairso the end result is that zuul passes a single ref to jenkins, and jenkins checks that out and tests it19:49
jeblairthit should make zuul much easier for other people to use, as they (and we!) can (eventually) get rid of the gerrit-git-prep script19:49
*** Gordonz has quit IRC19:49
jeblairmtaylor has a patch submitted to the jenkins git module to fix one problem we'd have with doing that right away19:50
jeblairbut we should be able to get to that point, and pretty soon.19:50
jeblairso an open question is where should zuul's git repos be served from -- currently zuul is running on jenkins.o.o, which means they would have to be served from there (via apache, presumably)19:50
mtaylorjeblair: I was just about to ask about that19:51
jeblairwe could move zuul to the gerrit server, but they'd still need to be separate from the replica repos, because zuul needs a working tree, and gerrit requires replicas be bare19:51
jeblair(presumably, we could do the work in zuul, and then push the results to the replica repos)19:52
jaypipesmtaylor: reading back.19:52
jeblairor we could put zuul on its own server.19:52
*** johnpostlethwait has joined #openstack-meeting19:53
jeblairanyway, it's not too important.  we'll find some place.19:53
jeblaironce we switch gerrit-git-prep to using the new method, i also plan on renaming all the GERRIT_ env variables, so there will be a bit of an overhaul for all the jenkins jobs that reference them.19:54
jeblairafter the switch, i'd like to burn in cherry-pick mode some more before we examine changing the projects.19:54
*** johnpur has joined #openstack-meeting19:55
mtaylorI agree with that - cherry-pick so far has been mildly weird19:55
mtaylorbut that's probably largely the merge thing19:55
jeblairyeah, i think so.  but good to be sure.19:55
*** cp16net is now known as cp16net|away19:56
*** cp16net|away is now known as cp16net19:56
mtaylorand with that - I think we're at about time19:57
ttxmtaylor: stable-maint sounds good to me19:58
ttxfor bitrot jobs19:59
ttxsince they apply to stable/*19:59
*** markmc has joined #openstack-meeting19:59
jeblairttx: cool, i'll make that a strawman suggestion when i post to the ml20:00
ttxjeblair: could be some group that people opt in20:00
ttxI mean, if people are into that...20:00
*** heckj has joined #openstack-meeting20:00
* med_ thinks there's an endmeeting that needs to occur.20:01
*** dolphm has quit IRC20:01
*** jdurgin has quit IRC20:02
med_mtaylor, ^?20:02
*** 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:02
openstackMeeting ended Tue Aug 14 20:02:31 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-14-19.08.html20:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-14-19.08.txt20:02
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-14-19.08.log.html20:02
*** jdurgin has joined #openstack-meeting20:02
*** harlowja has left #openstack-meeting20:04
*** mrmartin has quit IRC20:04
*** dolphm has joined #openstack-meeting20:05
*** wabat_away is now known as wabat20:15
*** danh has joined #openstack-meeting20:19
*** danh has quit IRC20:25
*** Shrews has left #openstack-meeting20:40
*** h3k1 has joined #openstack-meeting20:41
*** matiu has quit IRC20:45
*** sandywalsh_ has quit IRC20:46
*** andrewbogott has joined #openstack-meeting20:50
*** danh has joined #openstack-meeting20:55
*** belliott has joined #openstack-meeting20:55
*** pnavarro has quit IRC20:58
*** renuka_ has joined #openstack-meeting20:59
*** gabrielhurley has joined #openstack-meeting21:00
ttxheckj, notmyname, bcwaldon, jgriffith, vishy, devcamcar/gabrielhurley, danwent: around ?21:01
gabrielhurleyttx: I believe I'm your devcamcar again...21:01
bcwaldonttx: hhey21:01
notmynamettx: here21:01
ttxLong meeting ahead, so we'll start now21:02
openstackMeeting started Tue Aug 14 21:02:08 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
ttxAgenda @ http://wiki.openstack.org/Meetings/ProjectMeeting21:02
*** mcohen has joined #openstack-meeting21:02
ttx#info Folsom-3 should be cut at the end of the day, so we'll look into remaining targets and defer/consider exceptions where appropriate21:02
ttx#topic Actions from previous meeting21:02
*** openstack changes topic to "Actions from previous meeting"21:02
ttx* comstud to create a Cells blueprint so that we can track it21:02
ttxvishy: Can't find one yet. I guess this is Grizzly material now ?21:02
*** markmcclain has quit IRC21:03
*** rkukura has joined #openstack-meeting21:03
vishyttx: yes appears so21:04
ttx#topic Keystone status21:04
*** openstack changes topic to "Keystone status"21:04
ttxheckj: o/21:04
ttx#link https://launchpad.net/keystone/+milestone/folsom-321:04
ttxNot much apparent progress since last week...21:04
ttxdocument-deployment-suggestions-policy being doc-only can be postponed to RC1...21:04
ttxheckj: https://blueprints.launchpad.net/keystone/+spec/pki : Defer/Will be merged today/Exception requested ?21:05
*** salv-orlando has joined #openstack-meeting21:05
heckjexception requested21:05
ttxheckj: ETA for that ?21:05
heckjbased on feedback from the community, we really want to add in revocation support for the tokens - aiming to have it in within 1 week21:05
ttxheckj: how self-contained is this feature ?21:05
*** mcohen_ has joined #openstack-meeting21:05
ttxso it doesn't impact "regular use" of keystone ?21:06
heckjnope - not even defaults. It's all for new use of PKI - default is the older token mechanisms21:06
ttxheckj: i'm fine with it, especially if it's the only one in Keystone21:06
*** mcohen_ has quit IRC21:06
ttx* https://blueprints.launchpad.net/keystone/+spec/ocf-support : Couldn't find code proposed... Deferred ?21:06
heckjttx: change was abandoned - so deferring it21:07
ttxheckj: Is that all the features that got in F3 ? Or is there anything we should retroactively create ?21:07
ttx#info FFe for pki blueprint, if it gets merged in one week max21:07
heckjThat's really it21:08
ttxFrom the Folsom blueprints, I'll also defer iana-register-port to Grizzly.21:08
ttxheckj: Looking at F3-targeted bugs now, I see two bugs targeted... Are those really F3 publication blockers, or should they be removed from list ?21:08
heckjttx: they denied us - so will be relooking at that blueprint entirely21:08
*** mcohen has quit IRC21:08
*** markmcclain has joined #openstack-meeting21:08
ttx(or pushed back to RC1 milestone)21:09
heckjttx: not blockers for the release21:09
heckjcan be easily kicked back to RC1 milestone - it's also out of the path for normal operation21:09
ttxok, great21:09
ttxheckj: anything else ?21:09
heckjI need to follow up with mtaylor and jeblair, but we might experiment with a feature branch to continue work on the V3 API while we continue to stabilize keystone for grizzly release21:10
ttxyou mean Folsom :)21:10
ttxsounds like a cool experiment21:10
ttxQuestions about Keystone ?21:10
heckjyeah - sorry, Folsom21:10
dolphmheckj: good idea21:10
ttx#topic Swift status21:11
*** openstack changes topic to "Swift status"21:11
ttxnotmyname: hey21:11
ttxGreat write-up to the list with recent features, thanks.21:11
ttxI created 1.6.1 milestone for you, no date yet. Let me know when you have an ETA.21:11
notmynamethanks. it's a great group of contributors21:11
notmynameok. I have an FYI though21:12
ttxI can use that21:12
notmynamebased on a patch merged yesterday, and depending on what happens before the next release, there is a very good chance we may call the next one 2.021:12
notmynamethe patch updated the on-disk format of the ring (a great fix from swifterdarrell) but it may require the version updated to communicate that21:13
bcwaldonnotmyname: curious what the reason is21:13
*** file has joined #openstack-meeting21:13
notmynameI'll probably send an email to the openstack-dev list about it21:13
ttxnotmyname: sounds like a good plan21:14
bcwaldonha, looked up and hit enter, ill shh now21:14
ttxnotmyname: anything else ?21:14
*** dolphm has quit IRC21:14
notmynamenope. swift meetup on Aug 30 if you are in the bay area21:14
ttx#action notmyname to send an email to openstack-dev with 2.0 plans21:14
ttxQuestions on Swift ?21:14
ttx#topic Glance status21:15
*** openstack changes topic to "Glance status"21:15
ttxbcwaldon: o/21:15
ttx#link https://launchpad.net/glance/+milestone/folsom-321:15
ttxOnly one left:21:15
ttx* https://blueprints.launchpad.net/glance/+spec/glance-deprecate-client : Looks like we should wait for this one, should be merged today ?21:15
*** dprince has quit IRC21:15
ttxor do you need slightly more time ?21:16
bcwaldonif anyone can offer their opinion on https://review.openstack.org/#/c/11359/, we can get that bp in today21:16
bcwaldonttx: the code is there, just need to get it reviewed/merged21:16
ttxbcwaldon: ok, lets wait21:16
ttx#help Priority glance review at https://review.openstack.org/#/c/11359/21:17
bcwaldonhopefully somebody watching this meeting has a few minutes21:17
ttxIs that all the features that got in F3 ? Or is there anything we should retroactively create ?21:17
bcwaldonthat would be it, afaik21:17
ttxLooking at F3-targeted bugs now, I see two bugs targeted...21:17
ttxAre they F3 blockers, or more like RC1 targets now ?21:17
ttxbcwaldon: Anything else ?21:17
*** markvoelker has quit IRC21:18
bcwaldonI wanted to mention something about the v2.0 Images API spec21:18
ttxgo ahead21:18
bcwaldonAs Folsom-3 is our feature freeze, this is the point where we say "What's in the code is v2.0"21:18
bcwaldonand I'm working on getting a nice markdown-formatted api spec for people to refer to21:18
heckjbcwaldon: nice!21:19
ttxQuestions on Glance ?21:19
ttx#topic Quantum status21:20
*** openstack changes topic to "Quantum status"21:20
ttxdanwent: around ?21:20
ttx#link https://launchpad.net/quantum/+milestone/folsom-321:20
ttxPretty long list of stuff under review here :)21:20
danwentstill clearing out some bugs21:20
danwentso the way to think of it as there are 3 high priority things we're tracking21:20
danwentand anything medium or below "gets in if it gets in"21:20
danwentthe provider net stuff is 90% in, we just keep lobbing off sub-commits21:21
danwentOVS support is all that is left21:21
ttxAll the "needs review" here are expected to hit today ? Or do you need slightly more time ?21:21
danwentI wouldn't mind more time for our 3 branches that are high priority and above21:22
danwentbut any of the lower stuff should either be merged tonight, or move on, in my opinion21:22
danwentto help people focus on key items and testing.21:22
ttxhmm, we'll see with Nova if it makes sense to delay F3 one more day to include a bit more stuff21:23
ttxI won't ask if there was anything implemented that isn't already part of this list :)21:23
danwentttx: otherwise, the three big high priority branches can get merged21:23
danwentwe'd just lop off smaller bugs to fix any remaining issues.21:23
ttxLooking at https://launchpad.net/quantum/+milestone/folsom-rc1 you targeted quite a few blueprints there21:23
ttxtaht's in addition to the 3 you already mentioned, right21:24
danwentack.  two of those are testing infrastructure21:24
danwentand two are in review already21:24
ttx(but unlikely to hit today or tomorrow ?)21:24
danwentif we have an extra day, the ones in review may hit.  I just haven't been super involved in the reviews, so I can't say for sure.21:25
ttxwhich ones are testing infra ?21:25
danwent"agent for test"21:25
danwent"v2 quantum versions of devstack exercise scripts"21:25
danwentbasically, those are one item, but they are going into separate repos, so two BPs.21:25
ttxI'm fine with those hitting early in RC121:26
danwentthe L3 CLI stuff is in review, but needs unit tests written21:26
ttxespecially the devstack one which probably doesn't land in Quantum anyway21:26
danwentmulti-host and rootwrap are the more concerning ones.21:26
ttxWhat about https://blueprints.launchpad.net/quantum/+spec/ovs-security-filtering ?21:26
ttxif it's really not started, sounds like grizzly to me21:26
danwentthis would likely be a very small vif driver21:27
danwentif its about 200 lines of code, it won't go in :)21:27
ttxwhat about https://blueprints.launchpad.net/quantum/+spec/metadata-overlapping-networks ?21:27
danwentyeah, carlp mentioned that last week.21:27
danwentthis is one of those "oh shit.." issues, as nova's metadata API assumes clients have unique ips.21:28
ttxhmm, could almost be considered a gap bug rather than a blueprint21:28
ttxThose all kinda make sense, but added all together it makes me fear for Quantum stability21:28
danwentyeah.  we tend to create BPs for everything.21:28
ttxin times when we need some stasis21:29
* ttx should reassign the last one since he is no longer working on it21:29
danwentagreed.  as I mentioned, these aren't all for sure things we're looking for, more just things we're considering21:29
danwenti'll do a write-up on this and get your thoughts.21:29
danwentas I mentioned, rootwrap and multi-host seem the most possible to disrupt21:30
ttxdanwent: sure, I'll look into them into more detail and talk to you21:30
danwentk, thanks21:30
ttx#action danwent/ttx to discuss how to reduce the nmber of FFe in Quantum21:30
ttxFrom the untargeted Folsom blueprints, should we just defer:21:30
danwentv2 spec is going to be done, but its not code, just using an item to track it.21:31
danwentall others are going to be deferred.21:31
ttxOn the bugs list, you should only keep F3 blockers21:31
danwentyup, i'm half way to cleaning it out21:31
ttx(those we'll need to fix and backport to milestone-proposed before Thursday)21:31
ttxIdeally all of those should have someone assigned to fix21:31
ttxOtherwise it doesn't look like it's going to happen21:32
ttxYou can push back the others to Folsom-RC1.21:32
ttxdanwent: Anything else ?21:32
danwentnope, back to hacking and reviewing :)21:32
ttxdanwent: stay around, we migth discuss a one-day delay once we get to Nova21:32
*** ttrifonov is now known as ttrifonov_zZzz21:32
*** EmilienM has quit IRC21:32
ttxQuestions on Quantum ?21:32
danwentok.  do me a favor and ping my irc handle?21:32
danwenti'll be rebasing :)(21:33
ttx#topic Cinder status21:33
*** openstack changes topic to "Cinder status"21:33
ttxjgriffith: around ?21:33
ttx#link https://launchpad.net/cinder/+milestone/folsom-321:33
ttxThis list grew quite a lot since last week :)21:33
jgriffithYes, that it did21:33
ttxAre all those reviews going to land today ?21:34
jgriffithMost are close, minor fixes here and there21:34
ttxin other words, can we defer anythign that doesn't make it by the end of the day ? Or would you appreciate just a few more hours ?21:34
jgriffithDepends on when the end of your today is :)21:35
jgriffithA few more hours would be great21:35
ttxjgriffith: it's actually the beginning of my tomorrow.21:35
ttxalso known as midnight Hawai time21:35
jgriffithI think everything that's in review now should be closed out by COB mountain time today21:35
ttxhttps://blueprints.launchpad.net/cinder/+spec/cinder-notifications -> deferred ?21:36
jgriffithyes, that's the *one* that won't go probably21:36
jgriffithyes, deferred21:36
ttxnetapp-volume-driver-cmode and create-volume-from-image got reviews merged, are they completed ?21:36
ttxok, willfix21:37
ttxIn the untargeted folsom list, I see:21:37
ttx* https://blueprints.launchpad.net/cinder/+spec/implement-availability-zones21:37
ttxshould I mark this one deferred too ?21:37
jgriffithThat made it I believe...21:37
* jgriffith checking...21:37
jgriffithYes, that made it21:38
ttxlinked stuff says "Partially implement blueprint implement-availability-zones"21:38
ttxso I was kinda wondering21:38
ttxWe can clarify that off-meeting21:39
ttxOnly one bug targeted to F3, that's bug 102331121:39
jgriffithk.. the second part was cinderclient which is going through now21:39
uvirtbotLaunchpad bug 1023311 in cinder "Quotas management is broken" [High,Triaged] https://launchpad.net/bugs/102331121:39
ttxIs it really a F3 blocker, which will get fixed in master and backported to milestone-proposed before Thursday ?21:39
ttxOr should we just retarget it to RC1 to make sure it's fixed before release time ?21:39
jgriffithI've about got it, but honestly won't get back to it in time21:39
ttxWill add implement-availability-zones to F3 targets21:40
ttxjgriffith: Anything else ?21:40
jgriffithNope, just trying to push the pypi of cinderclient21:40
jgriffiththat's it21:40
ttxQuestions on Cinder ?21:40
annegentlejgriffith: moving to docs after f3?21:41
gabrielhurleyttx, jgriffith, mtaylor: can we get cinderclient pushed to PyPI? The entry for the package exists but no distributions were ever uploaded. It's non-existence is blocking the last Horizon blueprint (code's done, it just depends on a package that doesn't exist...).21:41
jgriffithannegentle: Yes21:41
annegentlejgriffith: great, thanks. I think the original "doc plan" we outlined on IRC still works.21:41
jgriffithgabrielhurley: Working on it now, you should see it soon21:41
gabrielhurleyjgriffith: thanks21:41
ttx#topic Nova status21:42
*** openstack changes topic to "Nova status"21:42
ttxvishy: hey21:42
comstudjust in time21:42
ttxhmm, maybe we'll do horizon first21:44
ttx#topic Horizon status21:44
*** openstack changes topic to "Horizon status"21:44
ttx#topic Nova status21:44
*** openstack changes topic to "Nova status"21:44
ttx#link https://launchpad.net/nova/+milestone/folsom-321:44
ttxvishy: this list is a mess :)21:44
vishyyes it is21:45
ttxok, lets iterate through it...21:45
ttx* https://blueprints.launchpad.net/nova/+spec/general-host-aggregates : Implemented, right ?21:45
ttx* https://blueprints.launchpad.net/nova/+spec/task-management21:45
vishyremaining work of converting availability zones will have to be in grizzly21:45
vishymaoy: comments on that ^^ are we complete for now? remaining stuff done in bugs?21:45
ttx* https://blueprints.launchpad.net/nova/+spec/config-drive-v221:46
maoyvishy: it's a bit complicated. :)21:46
vishymaoy: so do we defer it to grizzly then?21:47
maoyvishy: I'd revise the bp for folsom only and get a new one for grizzly21:47
maoyvishy: there is a race condition that should be fixed in f-421:47
vishymaoy: ok can you revise it to what was done and mark it implemented?21:47
ttxmaoy: unfortunately tere is no f4 :)21:47
vishymaoy: yes that can be reported as a bug21:48
maoyttx: oops. my bad21:48
vishymaoy: and fixed for rc121:48
maoyvishy: yes i'll update it21:48
vishymaoy: thanks21:48
ttx* https://blueprints.launchpad.net/nova/+spec/novaplugins21:48
ttxlooks like defer to me21:49
vishyi still haven't heard from andrew whether it is done21:49
vishyhe got stuff merged21:49
vishybut i don't know if it is complete21:49
ttxright, but no more code in21:49
ttxin all cases21:49
ttx* https://blueprints.launchpad.net/nova/+spec/deprecate-createserverext21:49
vishyttx: so i'm not exactly sure how we should deprecate an extension21:50
vishyso i guess that one is kind of blocked?21:50
vishyi mean we can warn when it is loaded i guess21:50
ttxyeah I would add a DeprecationWarning21:50
vishyright now createserverext is exactly the same as /servers/21:50
vishyso maybe we should just leave it and kill that blueprint21:50
ttxkill kill21:51
ttx* https://blueprints.launchpad.net/nova/+spec/xenapi-live-block-migration21:51
markmcyeah, probably best - not like it's much maintenance overhead21:51
vishythat should make it21:51
ttxvishy: today ?21:51
vishyi think so21:51
ttxI won't go over all the Low stuff...21:51
*** danh has left #openstack-meeting21:51
ttxcan we apply the "what gets in is in, the rest is Grizzly" rule ?21:52
vishyttx: i have a list of potential stuff to keep an eye on for ffe21:52
vishyttx: http://etherpad.openstack.org/nova-ffe21:52
vishyand I would also like a special ffe to put everything that goes into cinder into nova-volumes21:52
vishywe can drop it as one big chunk21:53
ttxvishy: would one extra day of review significantly help in getting more in F3 and less in FFe ?21:53
annegentlewhat is the ruling there? cinder v nova-volume?21:53
vishyprobably, there is a number of close stuff21:53
ttxI've been pondering delaying F3 by one day since there is so much stuff "almost there"21:53
vishyttx: i buy that21:54
ttxWould be good to apply some priority treatment though... Concentrate on stuff that is more important first21:54
ttxdanwent: would you buy that too ?21:54
danwentas long as its a targeted extension, only at high priority stuff, then yes.21:55
vishymy rationale on the dump from cinder -> volume is: there was uproar about removing nova-volume so we need to keep it and put in security fixes21:55
* ttx kinda prefers to wait one day and get less FFes, so that stuff gets tested in F3 rather than randomly after21:55
vishya) cinder is the one being gated on so we should keep the code the same21:55
danwentthough i'm not sure how to enforce that, other than to actually branch, and just say that its OK to cherry-pick a select set of features over as well as bugs.21:55
*** ayoung has quit IRC21:55
vishyb) security backports will be way easier if the code is in sync at folsom release21:55
vishyttx: do you buy that?21:56
ttxvishy: yes, from security pov21:56
ttxrussellb: opinion ?21:56
* russellb reads scrollback..21:57
ttx#info F3 cut for Quantum/Nova delayed by one day to let a few extra prioritized reviews in, in an effort to limit the number of FFe21:57
ttx#info other projects may opt in21:57
russellbyes, does seem like a good idea to keep the code in sync, backports would def be easier21:57
russellbneed to look closely at any compatibility/upgrade issues from the big dump though ....21:58
danwentttx:  is it just the branch cut that is delayed, or also the final release?21:58
danwent(of folsom-3)21:58
ttxalso F3 milestone publication, yes21:58
ttxwould be done on Friday (god, I hate that)21:58
ttxvishy: Can I mark Deferred everything from https://blueprints.launchpad.net/nova/folsom that is not F3-targeted ?21:58
vishyttx: yes21:59
ttxOn the bugs side, there are 6 bugs targeted to F3...21:59
ttxCould we refine that list to include only real F3 blockers ?21:59
ttxLike "ZOMG I can't start an instance anymore"21:59
russellbpretty sure that qpid one is fixed, *changes it*22:00
*** tgall_foo has quit IRC22:00
ttxvishy: Anything else ?22:00
primeministerpttx: may speak for a sec22:01
vishyi would suggest people doing reviews prioritize these: http://etherpad.openstack.org/nova-ffe22:01
ttx#help Nova Review prio to http://etherpad.openstack.org/nova-ffe22:01
comstudi just approved xenapi live migration22:01
ttxprimeministerp: sure22:01
primeministerpwould like to open up https://review.openstack.org/#/c/1127622:01
primeministerpfor reprioritization22:01
primeministerpfor review if possible22:02
primeministerpto a higher priority22:02
med_3rd on vishy's list22:02
ttxprimeministerp: it's on vishy's prio list I just linked22:02
* primeministerp needs to refresh22:02
primeministerpttx: thx22:03
med_(row 12)22:03
russellbit's a good candidate for an exception if we don't get it in by the freeze22:03
ttxbut let's be honest... there is a risk that it won't get in... it was proposed very late22:03
russellbbut yes, that too22:03
russellbit's a lot of code to review..22:03
primeministerpttx: I understand22:03
*** jcooley has joined #openstack-meeting22:03
ttxFrankly I was amazed by the number of last-minute reviews22:03
ttxnot just yours22:03
vishyttx: it was kind of amazing actually :(22:03
ttxIt's so much easier to get your code in at any other moment of the 6-month-long cycle22:03
russellbyeah we kinda got slammed in the last week or two22:03
ttxQuestions on Nova ?22:04
primeministerphowever quite honestly it would be a major milestone and help our community from a single source of code perspective22:04
* ttx tries not to overrun too much22:04
primeministerpgive us the ability to file bugs properly22:04
*** renuka_ has quit IRC22:04
russellb'tis on the exception candidate list22:04
ttx#topic Horizon status22:04
*** openstack changes topic to "Horizon status"22:04
ttxgabrielhurley: thanks for your patience22:05
gabrielhurleyo hai22:05
ttx#link https://launchpad.net/horizon/+milestone/folsom-322:05
gabrielhurleyI'm so much happier with this milestone than I was last week22:05
ttxswitch-to-cinder-client got done ?22:05
gabrielhurleyit's merging right this second22:05
ttx* https://blueprints.launchpad.net/horizon/+spec/translation-documentation -- sounds like this is doc and can be pushed back to RC1 in case of need22:06
ttxYou have an enormous list of F3-targeted bugs, I suspect most of them are not F3 publication blockers...22:06
gabrielhurleyall the wishlist stuff can be flat out deferred22:06
ttxShould I push back to RC1 anything that is not FixCommitted when I cut the branch ?22:06
*** ewindisch has joined #openstack-meeting22:06
gabrielhurleyof the remaining 8 there are no blockers, and most of them will be fixed today22:06
ttxit might be end of day tomorrow, so you have a bit more time22:06
gabrielhurleyeven better22:07
ttxgabrielhurley: Anything else you wanted to mention ?22:07
ohnoimdeadwoo hoo extra day!22:07
gabrielhurleynope. just a thanks to everyone for helping tear through the end of the F3 milestone :-)22:07
ttxQuestions for Horizon ?22:08
ttxohnoimdead: yay, thank me for another sleepless night22:08
ttx#topic Other Team reports22:08
*** openstack changes topic to "Other Team reports"22:08
ttxAny other team lead with a (quick) status report ?22:08
ttxgo for it22:10
*** rnirmal has quit IRC22:10
annegentleactually no, looking at the clock :)22:10
annegentleI'll put it in an email22:10
ttx#topic Open discussion22:10
*** openstack changes topic to "Open discussion"22:10
ttxAnything else, anyone ?22:10
*** anniec has quit IRC22:10
*** littleidea has quit IRC22:11
*** 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:11
openstackMeeting ended Tue Aug 14 22:11:25 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:11
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-14-21.02.html22:11
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-14-21.02.txt22:11
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-14-21.02.log.html22:11
ttxThaanks everyone, sending F3 delay email to list now22:11
*** markmc has quit IRC22:12
*** littleidea has joined #openstack-meeting22:12
*** gabrielhurley1 has joined #openstack-meeting22:15
*** ryanpetr_ has joined #openstack-meeting22:16
*** gabrielhurley1 has quit IRC22:17
*** kindaopsdevy has quit IRC22:18
*** gabrielhurley has quit IRC22:18
*** ryanpetrello has quit IRC22:18
*** benner has quit IRC22:18
*** benner has joined #openstack-meeting22:18
*** eglynn__ has quit IRC22:19
*** markmcclain has quit IRC22:19
*** anniec has joined #openstack-meeting22:20
*** dwcramer has quit IRC22:24
*** kindaopsdevy has joined #openstack-meeting22:27
*** adjohn has joined #openstack-meeting22:30
*** maoy has quit IRC22:35
*** nati_ueno_2 has joined #openstack-meeting22:36
*** lloydde_ has quit IRC22:37
*** ryanpetrello has joined #openstack-meeting22:43
*** mattray has quit IRC22:45
*** ryanpetr_ has quit IRC22:46
*** heckj has quit IRC22:54
*** h3k1 has quit IRC23:03
*** h3k1 has joined #openstack-meeting23:06
*** anniec_ has joined #openstack-meeting23:06
*** ryanpetrello has quit IRC23:07
*** h3k1 has left #openstack-meeting23:08
*** anniec has quit IRC23:08
*** anniec_ is now known as anniec23:08
*** nati_uen_ has joined #openstack-meeting23:09
*** nati_ueno_2 has quit IRC23:12
*** jakedahn_zz is now known as jakedahn23:23
*** ncode has quit IRC23:28
*** jdurgin has quit IRC23:30
*** Dr_Who has joined #openstack-meeting23:46
*** kindaopsdevy has quit IRC23:47
*** ohnoimdead has quit IRC23:48
*** tgall_foo has joined #openstack-meeting23:48
*** jakedahn is now known as jakedahn_zz23:52
*** littleidea has quit IRC23:54
*** littleidea has joined #openstack-meeting23:56

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