Tuesday, 2012-01-17

*** GheRivero has quit IRC00:05
*** GheRivero has joined #openstack-meeting00:06
*** GheRivero has quit IRC00:07
*** GheRivero has joined #openstack-meeting00:08
*** GheRivero has quit IRC00:10
*** vladimir3p has joined #openstack-meeting00:10
*** GheRivero has joined #openstack-meeting00:11
*** zul has quit IRC00:16
*** zul has joined #openstack-meeting00:17
*** GheRivero has quit IRC00:19
*** GheRivero has joined #openstack-meeting00:19
*** Gordonz has joined #openstack-meeting00:33
*** jog0 has joined #openstack-meeting00:47
*** jog0 has left #openstack-meeting00:48
*** Gordonz has quit IRC00:51
*** Gordonz has joined #openstack-meeting00:52
*** GheRivero has quit IRC00:58
*** GheRivero has joined #openstack-meeting00:58
*** reed has quit IRC01:02
*** mdomsch has quit IRC01:17
*** ayoung has quit IRC01:18
*** GheRivero has quit IRC01:19
*** GheRivero has joined #openstack-meeting01:19
*** GheRivero has quit IRC01:27
*** GheRivero has joined #openstack-meeting01:27
*** adjohn has quit IRC01:38
*** adjohn has joined #openstack-meeting01:39
*** GheRivero has quit IRC01:39
*** GheRivero has joined #openstack-meeting01:39
*** GheRivero has quit IRC01:42
*** GheRivero has joined #openstack-meeting01:42
*** adjohn has quit IRC01:43
*** GheRivero has quit IRC01:49
*** GheRivero has joined #openstack-meeting01:49
*** novas0x2a|laptop has quit IRC01:57
*** vladimir3p has quit IRC01:59
*** GheRivero has quit IRC01:59
*** GheRivero has joined #openstack-meeting01:59
*** dragondm has quit IRC02:00
*** GheRivero has quit IRC02:10
*** GheRivero has joined #openstack-meeting02:10
*** GheRivero has quit IRC02:43
*** GheRivero has joined #openstack-meeting02:43
*** bengrue has quit IRC02:55
*** troytoman is now known as troytoman-away03:06
*** danwent has quit IRC03:12
*** deshantm has quit IRC03:37
*** deshantm has joined #openstack-meeting03:49
*** adjohn has joined #openstack-meeting03:54
*** reed has joined #openstack-meeting03:54
*** dendrobates is now known as dendro-afk03:58
*** dendro-afk is now known as dendrobates04:00
*** AlanClark has quit IRC04:01
*** reed has quit IRC04:10
*** deshantm has quit IRC04:16
*** adjohn has quit IRC04:23
*** dendrobates is now known as dendro-afk04:42
*** dendro-afk is now known as dendrobates04:44
*** danwent has joined #openstack-meeting04:57
*** adjohn has joined #openstack-meeting05:01
*** GheRivero has quit IRC05:40
*** GheRivero has joined #openstack-meeting05:40
*** Gordonz has quit IRC06:02
*** GheRivero has quit IRC06:31
*** GheRivero has joined #openstack-meeting06:31
*** jog0 has joined #openstack-meeting06:52
*** adjohn has quit IRC06:53
*** sleepsonthefloo has quit IRC06:58
*** jog0 has quit IRC06:58
*** GheRivero has quit IRC07:07
*** adjohn has joined #openstack-meeting07:12
*** adjohn has quit IRC07:12
*** zul has quit IRC08:14
*** GheRivero has joined #openstack-meeting08:18
*** GheRivero has quit IRC08:21
*** GheRivero has joined #openstack-meeting08:21
*** GheRivero has quit IRC08:31
*** GheRivero has joined #openstack-meeting08:31
*** zigo has joined #openstack-meeting08:37
*** GheRivero has quit IRC08:38
*** GheRivero has joined #openstack-meeting08:38
*** bencherian has quit IRC08:40
*** GheRivero has quit IRC08:40
*** GheRivero has joined #openstack-meeting08:40
*** GheRivero has quit IRC08:54
*** GheRivero has joined #openstack-meeting08:54
*** danwent has quit IRC08:58
*** derekh has joined #openstack-meeting09:13
*** LinuxJedi has quit IRC09:22
*** GheRivero has quit IRC09:22
*** GheRivero has joined #openstack-meeting09:22
*** LinuxJedi has joined #openstack-meeting09:25
*** GheRivero has quit IRC09:36
*** GheRivero has joined #openstack-meeting09:36
*** GheRivero has quit IRC09:37
*** GheRivero has joined #openstack-meeting09:37
*** GheRivero has quit IRC09:44
*** GheRivero has joined #openstack-meeting09:44
*** GheRivero has quit IRC09:54
*** GheRivero has joined #openstack-meeting09:54
*** GheRivero has quit IRC09:55
*** GheRivero has joined #openstack-meeting09:55
*** GheRivero has quit IRC09:56
*** GheRivero has joined #openstack-meeting09:56
*** GheRivero has quit IRC09:57
*** GheRivero has joined #openstack-meeting09:57
*** shang has joined #openstack-meeting09:59
*** GheRivero has quit IRC10:02
*** GheRivero has joined #openstack-meeting10:02
*** darraghb has joined #openstack-meeting10:08
*** GheRivero has quit IRC10:08
*** GheRivero has joined #openstack-meeting10:08
*** GheRivero has quit IRC10:16
*** GheRivero has joined #openstack-meeting10:16
*** GheRivero has quit IRC10:45
*** GheRivero has joined #openstack-meeting10:45
*** GheRivero has quit IRC10:47
*** GheRivero has joined #openstack-meeting10:47
*** GheRivero has quit IRC11:42
*** GheRivero has joined #openstack-meeting11:42
*** zul has joined #openstack-meeting12:17
*** GheRivero has quit IRC12:21
*** GheRivero has joined #openstack-meeting12:21
*** GheRivero has quit IRC12:28
*** GheRivero has joined #openstack-meeting12:28
*** markvoelker has joined #openstack-meeting12:29
*** GheRivero has quit IRC12:41
*** GheRivero has joined #openstack-meeting12:41
*** GheRivero has quit IRC12:43
*** GheRivero has joined #openstack-meeting12:43
*** GheRivero has quit IRC12:54
*** GheRivero has joined #openstack-meeting12:54
*** GheRivero has quit IRC13:19
*** GheRivero has joined #openstack-meeting13:19
*** GheRivero has quit IRC13:20
*** GheRivero has joined #openstack-meeting13:20
*** GheRivero has quit IRC13:24
*** GheRivero has joined #openstack-meeting13:24
*** GheRivero has quit IRC13:25
*** GheRivero has joined #openstack-meeting13:25
*** GheRivero has quit IRC13:29
*** GheRivero has joined #openstack-meeting13:29
*** GheRivero has quit IRC13:30
*** GheRivero has joined #openstack-meeting13:30
*** GheRivero has quit IRC13:38
*** GheRivero has joined #openstack-meeting13:38
*** GheRivero has quit IRC13:40
*** GheRivero has joined #openstack-meeting13:40
*** GheRivero has quit IRC13:41
*** GheRivero has joined #openstack-meeting13:41
*** GheRivero has quit IRC13:43
*** GheRivero has joined #openstack-meeting13:43
*** GheRivero has quit IRC13:44
*** GheRivero has joined #openstack-meeting13:44
*** GheRivero has quit IRC13:48
*** GheRivero has joined #openstack-meeting13:48
*** dprince has joined #openstack-meeting13:49
*** GheRivero has quit IRC13:59
*** GheRivero has joined #openstack-meeting13:59
*** AlanClark has joined #openstack-meeting14:01
*** GheRivero has quit IRC14:01
*** GheRivero has joined #openstack-meeting14:01
*** GheRivero has quit IRC14:06
*** GheRivero has joined #openstack-meeting14:06
*** GheRivero has quit IRC14:11
*** GheRivero has joined #openstack-meeting14:11
*** GheRivero has quit IRC14:17
*** GheRivero has joined #openstack-meeting14:17
*** GheRivero has quit IRC14:20
*** GheRivero has joined #openstack-meeting14:20
*** mestery has joined #openstack-meeting14:21
*** GheRivero has quit IRC14:22
*** GheRivero has joined #openstack-meeting14:22
*** GheRivero has quit IRC14:34
*** GheRivero has joined #openstack-meeting14:34
*** GheRivero has quit IRC14:39
*** GheRivero has joined #openstack-meeting14:39
*** GheRivero has quit IRC14:40
*** GheRivero has joined #openstack-meeting14:40
*** GheRivero has quit IRC14:41
*** GheRivero has joined #openstack-meeting14:41
*** GheRivero has quit IRC14:42
*** GheRivero has joined #openstack-meeting14:42
*** GheRivero has quit IRC14:46
*** GheRivero has joined #openstack-meeting14:46
*** GheRivero has quit IRC14:48
*** GheRivero has joined #openstack-meeting14:48
*** mattray has joined #openstack-meeting14:50
*** GheRivero has quit IRC14:52
*** GheRivero has joined #openstack-meeting14:52
*** zigo has quit IRC14:58
*** GheRivero has quit IRC15:06
*** GheRivero has joined #openstack-meeting15:06
*** GheRivero has quit IRC15:09
*** GheRivero has joined #openstack-meeting15:09
*** hggdh has quit IRC15:09
*** hggdh has joined #openstack-meeting15:16
*** GheRivero has quit IRC15:30
*** GheRivero has joined #openstack-meeting15:30
*** GheRivero has quit IRC15:35
*** GheRivero has joined #openstack-meeting15:35
*** GheRivero has quit IRC15:36
*** GheRivero has joined #openstack-meeting15:36
*** deshantm has joined #openstack-meeting15:41
*** ayoung has joined #openstack-meeting15:45
*** reed has joined #openstack-meeting15:48
*** rnirmal has joined #openstack-meeting15:54
*** GheRivero has quit IRC16:02
*** GheRivero has joined #openstack-meeting16:02
*** danwent has joined #openstack-meeting16:04
*** dendrobates is now known as dendro-afk16:05
*** GheRivero has quit IRC16:06
*** GheRivero has joined #openstack-meeting16:06
*** dendro-afk is now known as dendrobates16:07
*** GheRivero has quit IRC16:10
*** GheRivero has joined #openstack-meeting16:10
*** GheRivero has quit IRC16:13
*** GheRivero has joined #openstack-meeting16:13
*** hggdh has quit IRC16:14
*** Gordonz has joined #openstack-meeting16:24
*** jsavak has joined #openstack-meeting16:27
*** GheRivero has quit IRC16:27
*** GheRivero has joined #openstack-meeting16:27
*** dendrobates is now known as dendro-afk16:28
*** GheRivero has quit IRC16:31
*** GheRivero has joined #openstack-meeting16:31
*** dragondm has joined #openstack-meeting16:35
*** hggdh has joined #openstack-meeting16:35
*** GheRivero has quit IRC16:35
*** GheRivero has joined #openstack-meeting16:35
*** GheRivero has quit IRC16:41
*** GheRivero has joined #openstack-meeting16:41
*** GheRivero has quit IRC16:44
*** GheRivero has joined #openstack-meeting16:44
*** bencherian has joined #openstack-meeting16:45
*** mdomsch has joined #openstack-meeting16:46
*** GheRivero has quit IRC17:13
*** GheRivero has joined #openstack-meeting17:13
*** sleepsonthefloo has joined #openstack-meeting17:15
*** GheRivero has quit IRC17:21
*** GheRivero has joined #openstack-meeting17:21
*** GheRivero has quit IRC17:22
*** GheRivero has joined #openstack-meeting17:22
*** GheRivero has quit IRC17:23
*** GheRivero has joined #openstack-meeting17:23
*** GheRivero has quit IRC17:25
*** GheRivero has joined #openstack-meeting17:25
*** GheRivero has quit IRC17:26
*** GheRivero has joined #openstack-meeting17:26
*** zigo has joined #openstack-meeting17:27
*** GheRivero has quit IRC17:29
*** GheRivero has joined #openstack-meeting17:29
*** GheRivero has quit IRC17:30
*** GheRivero has joined #openstack-meeting17:30
*** GheRivero has quit IRC17:32
*** GheRivero has joined #openstack-meeting17:32
*** GheRivero has quit IRC17:39
*** GheRivero has joined #openstack-meeting17:39
*** GheRivero has quit IRC17:41
*** GheRivero has joined #openstack-meeting17:41
*** derekh has quit IRC17:42
*** sleepsonthefloo has quit IRC17:42
*** sleepsonthefloo has joined #openstack-meeting17:42
*** jdurgin has joined #openstack-meeting17:43
*** openstack` has joined #openstack-meeting17:48
-zelazny.freenode.net- [freenode-info] channel flooding and no channel staff around to help? Please check with freenode support: http://freenode.net/faq.shtml#gettinghelp17:48
*** openstack has quit IRC17:48
*** openstack` is now known as openstack17:49
*** ChanServ sets mode: +o openstack17:49
*** mtaylor has quit IRC17:49
*** mtaylor has joined #openstack-meeting17:49
*** mtaylor has joined #openstack-meeting17:49
*** openstack has joined #openstack-meeting17:57
*** ChanServ sets mode: +o openstack17:57
*** gyee has joined #openstack-meeting17:59
*** zns has joined #openstack-meeting17:59
jsavak#startmeeting Keystone Weekly Status18:00
openstackMeeting started Tue Jan 17 18:00:13 2012 UTC.  The chair is jsavak. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.18:00
*** openstack changes topic to " (Meeting topic: Keystone Weekly Status)"18:00
jsavak#link Agenda: http://wiki.openstack.org/Meetings/KeystoneMeeting18:00
*** GheRivero has quit IRC18:00
*** GheRivero has joined #openstack-meeting18:00
jsavak#link Essex-3 status: https://launchpad.net/keystone/+milestone/essex-318:01
jsavakWho is here for the Keystone weekly meeting?18:01
gyeeme18:01
*** GheRivero has quit IRC18:01
jsavakHi gyee!18:01
gyeethe service endpoint location blueprint will not make E318:01
*** GheRivero has joined #openstack-meeting18:01
gyeeI am actively working on the keystone domains blueprint18:01
znso/18:02
jsavakOk - i think we untagged that a while back18:02
*** openstack` has joined #openstack-meeting18:06
*** openstack has quit IRC18:06
jsavakgyee - ok. We have another meeting before e-3 freeze so may be I'll leave it as it is for now18:07
*** openstack` is now known as openstack18:07
*** ChanServ sets mode: +o openstack18:07
jsavaknext week if it seems that domains is close to making the 1/26 date, we can target it as e-318:07
*** GheRivero has quit IRC18:07
jsavaksound ok?18:07
*** GheRivero has joined #openstack-meeting18:07
gyeesure18:07
jsavak#note Keystone domains is being worked on by gyee and may be ready for E3. Status check next week to determine if E3 is a realistic milestone for it18:08
*** GheRivero has quit IRC18:08
*** GheRivero has joined #openstack-meeting18:08
gyeecan we do the domains feature in phases, as long as it doesn't impact backward compatibility?18:09
gyeethe scope is pretty big as far as I can tell18:09
*** GheRivero has quit IRC18:09
jsavakYes - since it's an extension maybe just having a minimially viable scope would be a good first step18:09
*** GheRivero has joined #openstack-meeting18:09
gyeesounds good, I'll put together a proposal, thanks18:10
jsavakno problem18:10
jsavakAny other comments or issues for Keystone?18:10
jsavakOverall E3 is looking good and we don't see any blockers18:11
jsavakThanks gyee for the status update18:11
gyeeno problem18:12
jsavak#endmeeting18:12
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"18:12
openstackMeeting ended Tue Jan 17 18:12:10 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:12
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-17-18.00.html18:12
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-17-18.00.txt18:12
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-17-18.00.log.html18:12
znsjsavak: thanks for running the meeting!18:13
jsavakzns - no problem18:13
*** GheRivero has quit IRC18:13
*** GheRivero has joined #openstack-meeting18:13
*** GheRivero has quit IRC18:18
*** GheRivero has joined #openstack-meeting18:18
*** GheRivero has quit IRC18:21
*** GheRivero has joined #openstack-meeting18:21
*** johnpur has joined #openstack-meeting18:23
*** GheRivero has quit IRC18:26
*** GheRivero has joined #openstack-meeting18:26
*** carlp has joined #openstack-meeting18:28
*** GheRivero has quit IRC18:31
*** GheRivero has joined #openstack-meeting18:31
*** GheRivero has quit IRC18:33
*** GheRivero has joined #openstack-meeting18:33
*** jakedahn has joined #openstack-meeting18:34
*** GheRivero has quit IRC18:34
*** GheRivero has joined #openstack-meeting18:34
*** GheRivero has quit IRC18:35
*** GheRivero has joined #openstack-meeting18:35
*** darraghb has quit IRC18:37
*** GheRivero has quit IRC18:37
*** novas0x2a|laptop has joined #openstack-meeting18:37
*** GheRivero has joined #openstack-meeting18:37
*** GheRivero has quit IRC18:39
*** GheRivero has joined #openstack-meeting18:39
*** GheRivero has quit IRC18:41
*** GheRivero has joined #openstack-meeting18:41
*** GheRivero has quit IRC18:43
*** GheRivero has joined #openstack-meeting18:43
*** GheRivero has quit IRC18:44
*** GheRivero has joined #openstack-meeting18:44
*** GheRivero has quit IRC18:47
*** GheRivero has joined #openstack-meeting18:47
*** jsavak has quit IRC18:49
*** GheRivero has quit IRC18:50
*** GheRivero has joined #openstack-meeting18:50
*** GheRivero has quit IRC18:51
*** GheRivero has joined #openstack-meeting18:51
*** GheRivero has quit IRC18:52
*** GheRivero has joined #openstack-meeting18:52
*** bengrue has joined #openstack-meeting18:53
*** oubiwann has joined #openstack-meeting18:54
*** dendro-afk is now known as dendrobates18:59
*** GheRivero has quit IRC19:03
*** GheRivero has joined #openstack-meeting19:03
*** GheRivero has quit IRC19:06
*** GheRivero has joined #openstack-meeting19:06
*** GheRivero has quit IRC19:13
*** GheRivero has joined #openstack-meeting19:13
*** ewindisch has joined #openstack-meeting19:16
*** heckj has joined #openstack-meeting19:19
*** GheRivero has quit IRC19:20
*** GheRivero has joined #openstack-meeting19:20
*** GheRivero has quit IRC19:27
*** GheRivero has joined #openstack-meeting19:27
*** oubiwann1 has joined #openstack-meeting19:33
*** oubiwann has quit IRC19:36
*** jk0 has joined #openstack-meeting19:45
*** joshuamckenty has joined #openstack-meeting19:46
*** mdomsch has quit IRC19:49
*** GheRivero has quit IRC19:49
*** GheRivero has joined #openstack-meeting19:49
*** jbryce has joined #openstack-meeting19:57
*** GheRivero has quit IRC19:57
*** GheRivero has joined #openstack-meeting19:57
*** anotherjesse has joined #openstack-meeting19:58
*** GheRivero has quit IRC19:58
*** GheRivero has joined #openstack-meeting19:58
notmynamehi19:59
ttxo/19:59
jk0hi19:59
*** GheRivero has quit IRC19:59
jbrycehello19:59
*** GheRivero has joined #openstack-meeting19:59
jbryce#startmeeting20:00
openstackMeeting started Tue Jan 17 20:00:12 2012 UTC.  The chair is jbryce. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.20:00
*** ewanmellor has joined #openstack-meeting20:00
jbrycewho all is here?20:00
ewanmellorReady and willing20:00
* jk0 20:00
* ttx 20:00
jbryceewanmellor: but are you able?20:00
mtayloro/20:01
ewanmellorLess able than I was when I was younger.  I have to settle for "willing" these days.20:01
*** dendrobates is now known as dendro-afk20:01
jbryceewanmellor: ha20:01
johnpuro/20:01
anotherjesseo/20:02
*** GheRivero has quit IRC20:02
jbrycejoshuamckenty, anotherjesse, vishy, pvo, zns: here?20:02
anotherjesseand vishy is here20:02
*** GheRivero has joined #openstack-meeting20:02
jbryceagenda: http://wiki.openstack.org/Governance/PPB20:02
*** bencherian has quit IRC20:03
jbrycefirst couple of items were requested by josh, so maybe we skip to m2crypto and give him time to arrive20:03
jbryce#topic M2Crypto options20:03
*** openstack changes topic to "M2Crypto options"20:03
jbrycemtaylor: want to lead this one?20:03
mtaylortotally20:04
joshuamckentyhey, sorry I was late20:04
znszns here20:04
anotherjesseour use is pretty small at the moment20:04
*** GheRivero has quit IRC20:04
anotherjessewe could just shell out to openssh ....20:04
joshuamckentygah20:04
*** GheRivero has joined #openstack-meeting20:04
joshuamckentywe USED to do that, and replaced it with m220:04
mtaylorm2 seems to be a pretty good lib - other than the abandoned part, yeah?20:05
joshuamckentyI like the idea of reviving m2crypto if it's paid for by HP20:05
johnpur:)20:05
mtayloryeah - I certainly don't mind doing the work on it (or making someone else do the work)20:06
anotherjesseit is only used for the EC2 x509 cert stuff - we originally wrote it shelling to openssh20:06
joshuamckentyit's used in cloudpipe as well, IIRC20:06
*** GheRivero has quit IRC20:06
anotherjesseswitching back to not using m2crypto should be pretty easy20:06
joshuamckentybut I don't think anyone uses cloudpipe anymore20:06
ttxis there another better-maintained Python lib to do that ?20:06
*** GheRivero has joined #openstack-meeting20:06
anotherjessejoshuamckenty: xtoddx- has been rewriting in openstack20:06
joshuamckentyyeah, I saw the bastion-host notes20:07
ewanmellorYou all mean openssl, no?  For x509 processing?20:07
mtaylorthere was also the thought of moving people away from pycryto so that we used m2 in all the places we use pycrypto too20:07
ttxewanmellor: yes20:07
joshuamckentyone dependency is better than two20:07
mtaylorPaul McMillan was suggesting that he thought that would be a good idea a little while ago20:07
ttxewanmellor: (if they don't, that's what they should mean)20:07
joshuamckentyis m2crypto > pycrypto ?20:08
mtaylorthat's what paul was asserting20:08
anotherjesseother than x509 it is used in ./nova/virt/xenapi/vmops.py20:08
anotherjesseeverwhere else already does shells out to openssh20:08
joshuamckentyopenssl20:08
anotherjessevishy doesn't want m2crypto either20:09
anotherjessewe both prefer removing it as a dependency if we have this issue20:09
joshuamckentyis that because of packaging bugs?20:10
anotherjessem2crypto has always been a pain20:10
anotherjessethe value we get out of it so small20:10
joshuamckentyesp. for mac dev environments :)20:10
*** GheRivero has quit IRC20:10
_0x44One thing... nova has paramiko as a requirement and paramiko depends on pycrypto...20:10
mtaylorwell, packaging bugs/bugs in setup.py are the thing that brought it to mind - but we have no way to fix upstream bugs of any sort at the moment20:10
*** GheRivero has joined #openstack-meeting20:10
joshuamckentywell, if it's a nova dependency only, it seems like a PTL call20:11
ttxShelling out to openssl would be ugly if we didn't shell out in lots of places already20:11
mtaylorit's less work from my end to just stop using it - and yeah, that's totally a vish call20:11
joshuamckentyI prefer libraries to shelling out in general, but it's a loosely held opinion20:11
ttxjoshuamckenty: I agree with that, when a valid lib exists.20:12
anotherjessehttps://github.com/openstack/nova/blob/master/nova/crypto.py#L124 <- in the same file we already use it20:12
mtaylorso shall I just file a bug requesting m2crypto removal from nova?20:12
jk0+120:12
*** GheRivero has quit IRC20:12
joshuamckentyanotherjesse: if you git blame that, is it mine?20:12
mtaylor(that's so much less work on my part)20:12
*** GheRivero has joined #openstack-meeting20:12
ttxmtaylor: sounds more reasonable than aopting M2Crypto under openstack core infra20:13
ttxadopting*20:13
mtaylorgreat!20:13
joshuamckentymtaylor: +020:13
notmyname-1 to that20:13
LinuxJedimtaylor: happy to take that one once you file it20:13
joshuamckentynotmyname: you'd rather fix the library?20:13
notmyname(adopting m2crypto into openstack)20:13
joshuamckentyoh, right20:13
johnpurok by me to removal20:13
*** GheRivero has quit IRC20:13
joshuamckentynotmyname: we're voting the reverse - gut m2crypto use20:13
ewanmellorDoesn't anyone fancy taking it over, outside of OpenStack infrastructure?  Just maintain it like any other open-source project?20:13
mtaylorthanks LinuxJedi20:13
*** GheRivero has joined #openstack-meeting20:13
joshuamckentyewanmellor: I'll propose that to CloudPassage20:13
notmynamejoshuamckenty: it's a nova-only thing so its use is, as you said, a ptl issue20:14
joshuamckentyit's kind of outside our focus, really20:14
notmynameindeed20:14
johnpurjust so Monty has a clear directive from Vish, or whatever20:14
jbrycesounds like there's no real interest in taking it over so it just falls back to the project to decide about taking it out20:14
mtayloryup. as long as we decide that we don't want to take it under our wing, the rest I can take up with vish. thanks!20:14
joshuamckentyNext topic?20:15
jbryce#topic ppb role in foundation20:15
*** openstack changes topic to "ppb role in foundation"20:15
joshuamckentyRight20:15
jbrycejoshuamckenty: did you have anything specific in mind on this one?20:15
joshuamckentyThere were some comments on the foundation list about whether we should be reviewing / juggling the governance structure prior to foundation formation20:15
*** GheRivero_ has joined #openstack-meeting20:16
joshuamckentyI know the issue of jbryce, anotherjesse, johnpur and myself having appointed seats has come up repeatedly20:16
ttxjoshuamckenty: opening more seats to election ?20:16
ttx(or all ?)20:16
*** GheRivero has quit IRC20:16
joshuamckentyPersonally, I don't see this as something that needs to get changed prior to the foundation setup, but I should probably excuse myself from the vote :)20:16
*** GheRivero has joined #openstack-meeting20:16
jbrycehonestly, i'd rather focus on figuring out what changes we want in the foundation and move as quickly as we can on that than trying to push changes to existing--lightly used anyway--structure20:16
zns+120:17
mtaylor+120:17
ttxjoshuamckenty: unfortunately the PPB doesn't own its own governance, so we can't vote to change that20:17
joshuamckentywell, I would respect a PPB vote to have me give up my seat20:17
joshuamckentyso in that sense, we do20:17
anotherjessettx: we can't vote to appoint ourselves dictators for life :(20:17
johnpurjbryce: is the foundation thinking far enough along to have this discussion?20:17
joshuamckentyThe PPB is currently the closest thing to what the foundation board is likely to look like20:18
johnpurat some poiont we will need a transition plan20:18
ttxjbryce: I think opening all seats would be a step forward towards a full meritocracy though -- and we don't have an idea of when the foundation will be set up, yet20:18
*** GheRivero has quit IRC20:18
joshuamckentyso I'm curious if we feel any specific responsibilities towards foundation-establishment20:18
joshuamckentyas a group, I mean20:18
*** sparkycollier has joined #openstack-meeting20:18
*** GheRivero has joined #openstack-meeting20:18
joshuamckentyI'm personally fairly involved with it20:18
joshuamckentybut not in the PPB context20:19
jbrycettx: that's based on the assumption that voting is automatically a better result which you yourself told me you don't fully agree with at the last conference20:19
anotherjessenot sure that PTLs would want to be on the governance board of the foundataion…  speaking not as one20:19
*** wwkeyboard has joined #openstack-meeting20:19
jbrycejohnpur: we've said that there will be a technical body in the foundation similar to the ppb20:19
*** GheRivero has quit IRC20:19
joshuamckentyttx: I'm also not convinced that a full meritocracy is either ideal or likely for the foundation20:19
ttxjbryce: you can't blame RAX for getting people elecrted, but you can blame Rackspace for having the power to appoint20:19
*** GheRivero has joined #openstack-meeting20:19
joshuamckentysince the community itself is largely (exclusively) a business ecosystem20:19
znsWe talked about the governance of the foundation being separate from the technical governance. So PTLs would probably be more keen on technical governance, IMO.20:20
joshuamckentyzns: good point20:20
johnpurzns: agree20:20
ttxjoshuamckenty: the solution would be to have a board of directors that is separate from the technical meritocracy20:20
*** GheRivero has quit IRC20:20
jbrycei think it makes sense to have a discussion about what the technical governance body should look like in our opinion, but that will also be a discussion that the broader community will have input on as well20:20
mtaylorwhat jbryce just said is my only important concern ... I want to make sure there is a technical meritocracy body to take questions like the m2crypto question to. I certainly don't mind there also being a business-focused board as well20:20
*** GheRivero has joined #openstack-meeting20:20
joshuamckentymtaylor: +120:20
joshuamckentyso my only concern is getting a better balance in the technical board20:21
ttxthe problem being, the current PPB kinda has the double role20:21
joshuamckentyI think the PTL mechanism isn't that useful for a set of projects at different lifecycle points20:21
*** GheRivero has quit IRC20:21
notmynamejoshuamckenty: balance in what way?20:21
ttxjoshuamckenty: we could have quotas from a given company ?20:21
joshuamckentynova is 80% of the active development, no?20:21
joshuamckentyno, I meant across projects20:21
jbrycettx: i'd be happy to blame rax if i felt damaging decisions were coming from that power. can you point to specifics that have damaged the community or the developers?20:21
*** GheRivero has joined #openstack-meeting20:21
ttxjoshuamckenty: i.e. they can't own more than 49% of the seats ?20:21
joshuamckentyI'm worried about company quotas on the board, not so much on technology20:22
ttxjbryce: people that are afraid of this power look at the future more than at the past20:22
*** GheRivero has quit IRC20:22
*** GheRivero has joined #openstack-meeting20:22
notmynamejoshuamckenty: do you think that means that nova needs more or less representation on a tech board?20:23
joshuamckentynotmyname: I sort of feel like nova needs proportional representation - e.g., more.20:23
joshuamckentyto account for nova-volumes and nova-network20:23
ttxjoshuamckenty: you can have one seat reserved by project (kinda PTL) + the rest elected from the global community of dev20:23
jbrycejoshuamckenty: that tends to leave the smaller projects underrepresented who have a different perspective and need sometimes20:24
joshuamckentybut again, the projects aren't equal in size, community interest, or lifecycle20:24
ttxAnyway, we are discussing foundation structure now20:24
joshuamckentyno20:24
joshuamckentywe're discussing the role that the PPB should have in establishing it20:24
joshuamckentyif any20:24
znsjoshuamckenty: what does a better balance on the technical board get you? What problem are you trying to solve? Does Nova have a problem they are facing because of underrepresentation?20:24
jbrycethe other question is does every ptl get a seat forever? what if we end up with a dozen projects, does the technical body grow infinitely?20:24
notmynamejoshuamckenty: is nova getting forced into decisions now that it wouldn't if it had more representation?20:24
joshuamckentyyes to both20:24
znsjoshuamckenty: elaborate?20:25
joshuamckentynova has the bulk of the work from any openstack-wide technical decisions20:25
jbryceyes to both of my comments or ziad's? = )20:25
joshuamckentyyes to zns and notmyname20:25
*** GheRivero has quit IRC20:25
joshuamckentymultithreading20:25
*** GheRivero has joined #openstack-meeting20:25
ttxjbryce: I think I would rather have project representatives present at the meetings, but with no voting power if they weren't elected20:25
anotherjessejoshuamckenty: vishy and I think the rest of the projects have been pretty supportive of project wide issues20:26
anotherjessejoshuamckenty: can you give examples?20:26
joshuamckentypaste20:26
znsWhat about multithreading? * not arguing, just missing info *20:26
ttxand have true elections over the whole corpus of openstack developers, no per-project seat20:26
*** GheRivero has quit IRC20:26
jbrycezns: i think he was just referring to multiple conversations threads20:26
joshuamckentyyeah, sorry20:26
joshuamckentyI am multithreading20:26
*** GheRivero has joined #openstack-meeting20:26
znsah. Got it.20:26
jbrycettx: so elected voting members and PTLs are ex-officio?20:27
joshuamckentyAnyway, technical board composition I think we can solve going forward. Is that something the PPB wants to put a proposal forward on?20:27
ttxif they didn't get elected, PTLs should be present, but not have voting powers20:27
joshuamckentyE.g., do we think that's a role we play in foundation discussions?20:27
ttxjoshuamckenty: as a group ?20:28
joshuamckentyyes20:28
jbrycejoshuamckenty: i think it would be very relevant for us to talk about this specifically20:28
ttxif we agreed on something, we... could20:28
ttxbut we also can as individual members20:28
*** GheRivero has quit IRC20:28
jbrycewe've probably all seen plenty of the problems and areas for improvement20:28
joshuamckentySo I see three key topics the PPB could weigh in on...20:28
joshuamckenty1. Technical board composition, representation, etc.20:28
*** GheRivero has joined #openstack-meeting20:28
joshuamckenty2. OpenStack as implementation and not standards20:29
joshuamckenty3. OpenStack as IaaS20:29
joshuamckentythe third is, e.g., clarifying the openstack mission statement20:29
*** GheRivero has quit IRC20:29
ttxjoshuamckenty: it seems simpler to weigh in the general foundation discussion as individuals with influence20:29
ttxrather than try to come up with some lazy consensus among all PPB members20:29
joshuamckentywell, the first might be good to have a PPB lazy consensus20:29
*** GheRivero has joined #openstack-meeting20:29
joshuamckentysince it would represent the current-best-effort20:30
joshuamckentyDo we feel we own responsibility for a transition plan? Jointly with whomever/whatever the foundation is?20:30
ttxjoshuamckenty: so we would discuss that on our mailing-list rather than on the foundation ml ?20:30
joshuamckentyOr cc both of them < ttx20:31
*** GheRivero has quit IRC20:31
*** hggdh has quit IRC20:31
joshuamckentyIs everyone on the PPB also on the foundaotion mailing list?20:31
ttxjoshuamckenty: I'll be happy to weigh in on any discussion about tech board composition, on whatever ML20:31
notmynameonce the foundation is in the later stages (ie we have a pretty good idea of what it will look like), IMO we have the responsibility to be a part of a smooth transition20:31
*** GheRivero has joined #openstack-meeting20:31
notmynamejoshuamckenty: I'm not on the foundation list20:31
joshuamckentyI would feel uncomfortable drawing conclusions about PPB dynamics without knowing that everyone else was involved20:31
ttxI already did start a discussion on that on the foundation ML, but almost nobody picked it up20:32
znsjoshuamckenty: I'm not on the foundation ml. Not looking to be either unless I am called upon...20:32
*** GheRivero has quit IRC20:32
jbrycei think these topics are important to have in the broader discussions, but i would appreciate thoughts based on the last year of this PPB experiment from all of you who i'm sure have opinions20:32
jbryce= )20:32
*** GheRivero has joined #openstack-meeting20:32
jbryceand i read the messages to the both lists so wherever it happens is fine with me20:33
joshuamckentyFor context, can we get some numbers from stefano about contributor's / committers to each project?20:33
notmynamezns: +120:33
*** hggdh has joined #openstack-meeting20:33
*** GheRivero has quit IRC20:33
jk0we need to make sure those numbers are accurate :)20:33
*** GheRivero has joined #openstack-meeting20:33
joshuamckentyAlright, if I start a rant about tech board composition with ttx, I'll make sure it's cc'd to both foundation ML and PPB ML20:33
mtaylorjoshuamckenty: I also want to take soren's participation numbers from a few months ago and expand them into a few regular reports20:34
ttx"I'll be ranting with you"20:34
mtaylorsince we can get some really accurate numbers about committers from gerrit pretty easily20:34
*** GheRivero has quit IRC20:34
joshuamckentyAnyone else feel we have foundation responsibilities? Either in definition, in transition, or ongoing?20:34
jbrycewhat if we start with a reasonable proposal before we go straight to a rant20:34
joshuamckentyAs a group, not as individuals.20:34
*** GheRivero has joined #openstack-meeting20:34
jbryceit sounds like there's some pretty common ground20:34
joshuamckentyjbryce: I'm down with that20:34
jbrycejoshuamckenty: i think transition definitely...we've got some projects in incubation20:35
joshuamckentyI'd like to see us decouple (a little bit) the "openstack core" definition with PPB membership / PTL status20:35
jbrycebut my guess is that since 10 of 14 seats are currently elected, the make up will be fairly similar20:35
mtaylorjoshuamckenty ++20:35
joshuamckentylike what ttx is suggesting vis-a-vis ex-officio for PTLs that haven't been elected yet,20:36
joshuamckentybut also allowing PPB participation for really LARGE incubated projects20:36
*** GheRivero has quit IRC20:36
*** GheRivero has joined #openstack-meeting20:36
mtaylorand not getting swamped as we collect things like client libraries and the like20:36
znsjoshuamckenty: define LARGE. Lines of code or importance? … slippery20:37
joshuamckentyagreed20:37
notmynamejoshuamckenty: in other words, be decent grown-ups and talk to each other?20:37
ttxI'd rather have more area-specific technical leads and less PPB members20:37
joshuamckentyWell, just thinking about nova-volumes again20:38
joshuamckentyWanting to make sure it's got solid tech board representation even BEFORE it gets carved off from nova20:38
joshuamckentysince API definition, etc. is all happening inside nova, but will end up being a point of cross-project integration20:39
znsSounds like Large would probably be defined by the PPB. And since they're voting on incubation, there caveat for LARGE is unnecessary…20:39
*** GheRivero has quit IRC20:39
jbrycewe've got 20 minutes left and i'd love to get to the last agenda item20:39
znsi.e. vot in or out. Size doesn't matter ( in this case )20:39
*** GheRivero has joined #openstack-meeting20:39
znsvote20:39
joshuamckentyLet's do it20:39
jbrycecan we make starting a mailing thread the action of this?20:40
joshuamckentyzns: I just want them decouipled20:40
jbryce#topic Essex release check20:40
*** openstack changes topic to "Essex release check"20:40
joshuamckentyyeah20:40
znsjoshuamckenty: not against that. For a later discussion....20:40
joshuamckentyAm I the only one who's worried?20:40
*** GheRivero has quit IRC20:40
ttxworried by ?20:40
joshuamckentyOf course, I'm ALWAYS worried20:40
*** GheRivero has joined #openstack-meeting20:40
joshuamckentystate of essex20:40
joshuamckentyLack of good CI coverage at this date20:41
joshuamckentythe usual20:41
znsNo, you're not the only one.20:41
joshuamckentyHaving the entire tree broken in 2.6 just prior to E320:41
joshuamckentyWe *can't* ship a broken Essex20:41
*** GheRivero has quit IRC20:41
* ttx puts his release manager hat on20:41
joshuamckentySo if we're going to slip the date,20:41
notmynamethat really happened? how? isn't that why we have gates?20:41
joshuamckentyI think we should do it now.20:41
*** GheRivero has joined #openstack-meeting20:41
joshuamckentyMessaging will be much worse if we're closer to the release date.20:41
ttxjoshuamckenty: how is slipping the date helping in the areas you outlined ?20:42
zns-1 on slipping the date. +1 on focusing on hitting it.20:42
mtaylorjaypipes: (or anyone) is tempest ready to be turned on in the integration test gating yet?20:42
ttxWith Nova/Glance/keystone using Essex-3 as their feature freeze, we already have 10 weeks of stabilization planned20:42
jaypipesmtaylor: no.20:42
ttxCompared to 4 weeks for Diablo, and 3 weeks for Cactus20:42
mtaylorok20:42
*** GheRivero has quit IRC20:42
ttxSo the challenge will be to get most developers focused on bugfixing for 10 weeks20:42
joshuamckentyright20:42
ttxSlipping the date doesn't help when nobody is working on bugfixing20:42
joshuamckentywe've got global hack day20:42
joshuamckentyand bug crush day20:42
*** GheRivero has joined #openstack-meeting20:42
ttxOn previous releases I could count the number of developers working on that on one hand20:42
joshuamckentywe're trying to use meetups to build some shared momentum around bug fixing20:42
ttxSo I'd really like people/companies complaining about Essex potential lack of stability to put their foot where their mouth is and get developers on deck working on existing known bugs20:43
anotherjessejoshuamckenty: are you concerned about E3 not being "feature complete"20:43
ttxI'd like core reviewers to get anal-rententive20:43
*** GheRivero has quit IRC20:43
jaypipesttx: ++20:43
anotherjesseis there stuff your team is still working on?20:43
joshuamckentyanotherjesse: no, just not stable.20:43
*** GheRivero has joined #openstack-meeting20:43
jaypipesjoshuamckenty: what is piston doing about stability?20:43
joshuamckentyYeah, but we're shipping on Diablo anyway, so that doesn't worry me.20:43
ttxThat's all we need.20:44
joshuamckentyjaypipes: Organizing bug fixing sprints. You coming on the 2nd?20:44
jaypipesjoshuamckenty: yup. already booked tix.20:44
anotherjesse3 months before release seems early to call it20:44
*** GheRivero has quit IRC20:44
joshuamckentyAny later will be too late20:44
joshuamckentythere will be too much market pressure to hit the date20:44
ttxanotherjesse: slipping the date is not really an option20:44
*** GheRivero has joined #openstack-meeting20:44
jaypipesjoshuamckenty: but that doesn't mean bugs get fixed. we need a better prioritization of bugs and less focus on Diablo.20:44
joshuamckentySlipping the date is always an optino20:45
ttxWe have a design summit lined up, and promises to distributions20:45
notmynamecan there be a later date (say 1 month from now) where everything is reevaluated and a decision to push back is made then?20:45
joshuamckentyI'd like to propose a vote to fire the release manager who doesn't believe we can slip the date20:45
jaypipesjoshuamckenty: disagree. slipping the date just means we aren't doing time-based releases..20:45
ttxa later date will NOT help in anything. We'll just ship later, in the same state20:45
*** GheRivero has quit IRC20:45
ttxThe challange is to get developers working on bugfixes.20:45
ttxNot just their bugs20:45
*** GheRivero has joined #openstack-meeting20:45
jaypipesttx: and functional test writing.20:45
ttxKnown bugs20:45
anotherjessettx: ++20:45
mtaylorttx: ++20:46
ttxjaypipes: and functional test writing.20:46
jbryceso how can we rally on that front?20:46
ttxrallying doesn't help. Mettups don't help20:46
jaypipesjbryce: getting help from devs at RAX and Piston on Tempest test writing would be a good start...20:46
*** GheRivero has quit IRC20:46
jbryceadmitting defeat helps?20:46
ttxForcing your developers to work on it helps20:46
*** GheRivero has joined #openstack-meeting20:46
joshuamckentyjaypipes: wait - it's Tempest now?20:46
joshuamckentyWhat happened to Kong?20:46
joshuamckentyAnd SmokeStack?20:47
ttxFor Diablo we had 4 weeks, but only 5 people actually tried to address known bugs20:47
znsPart of the problem is we're pushing to get features in by E3 given we're freezing features after E3. So stability has been pushed back to beyond E3. That does not bode well for E3 being stable...20:47
anotherjessejbryce: imho the fact that the folks working on feature changes are all targeting E3 as feature complete and focusing on stability after Jan 26 means we are20:47
jaypipesjoshuamckenty: different things.20:47
joshuamckentyAnd... what was Soren's thing?20:47
ewindischjaypipes: companies shipping this code do need to continue working on and fixing Diablo. Piston and Cloudscaling both. That doesn't distract too much from fixing bugs in Essex, imho.20:47
anotherjessejoshuamckenty: tempest has be the ci project for a few months now20:47
anotherjesseci.openstack.org20:47
ttxI'd like to have a sizeable portion of our 200+ committers working on bugfixes. Not 520:47
*** GheRivero has quit IRC20:47
vishyzns: agreed, but no one is trying to ship off of e320:47
mtaylorjoshuamckenty: tempest is the name of openstack-integration-test project, it sucked in code from kong early on20:47
ttxand that WON'T happen unless they get the word from their management20:47
anotherjesseerr - http://qa.openstack.org/20:47
jaypipesewindisch: those companies should be helping to write test cases (in Tempest) and firing those tests against their Diablo targets.20:47
*** GheRivero has joined #openstack-meeting20:47
ttxthe PTLs have done their share, featurefreezing at E3 is VERY early20:47
znsjoshuamckenty implied he wants to "ship" E3...20:47
anotherjessehttp://qa.openstack.org/integration.html is the details20:47
*** jwalcik has joined #openstack-meeting20:48
ewindischCloudscaling has some people working on bug fixes and we're increasing that effort. We also have the zeromq-rpc blueprint ready to move toward inclusion, which is a new driver, but the code doesn't change or break anything that is already in trunk, so it is low-risk.20:48
vishyttx: i know that our team is rallying around testing / perf testing / bugfixing / administration cleanup20:48
joshuamckentyzns: I didn't imply that that I know of20:48
ttxvishy: goos. We'll see how that translates into targeted bugs getting picked up20:48
*** GheRivero has quit IRC20:48
ttxgood*20:48
*** clayg has joined #openstack-meeting20:48
jbrycettx: that sounds like rallying the companies to put their money where their mouth is...20:48
*** GheRivero has joined #openstack-meeting20:48
jaypipesvishy: your team, yes. I20:48
mtayloralso - as soon as we have even smaller chunks of usable tests laying around, let us know and we can add them to the integration testing being done20:49
jbrycewhich i'm willing to go work on20:49
ttxjbryce: yes. Give a break to their devs and tell them to go and fix known issues instead of doing... whatever they do20:49
jaypipes'm hoping Gigi's team can add some heft to Tempest20:49
ttxjoshuamckenty: and I'd agree that the time ie NOW20:49
*** GheRivero has quit IRC20:49
ttxis*20:49
jk0ttx: it's not always that easy20:49
ttxjk0: explain20:49
*** GheRivero has joined #openstack-meeting20:49
znsjoshuamckenty: my bad. I misread your "we can't ship a borken Essex". That I agree with. So, does that mean we can live with an unstable E3 to get features in and then stabilize by Essex release?20:50
notmynamettx: we can't control what companies set as the priorities for their devs20:50
*** jog0 has joined #openstack-meeting20:50
jk0if a team is in the middle of trying to ship features, it can be hard to break away and focus only on bugs (that might not even apply)20:50
*** GheRivero has quit IRC20:50
*** bcwaldon has joined #openstack-meeting20:50
jaypipeszns: for Glance, I'm going to push back hard on any features after E3.20:50
joshuamckenty"We", being the OpenStack community, can't afford to have Essex as broken as Diablo was20:50
joshuamckentyit will be the end of OpenStacl20:50
notmynamejoshuamckenty: +120:50
jaypipesjoshuamckenty: ++20:50
mtaylor++20:50
*** GheRivero has joined #openstack-meeting20:50
johnpur+120:50
ttxnotmyname: indeed. But we can spread the word that it will be their fault (again) if it's not rock-solid20:50
jaypipesjoshuamckenty: and "broken" == "not integrated properly"20:51
joshuamckentycorrect20:51
joshuamckentyalso not release-noted20:51
jaypipesjoshuamckenty: release-noted?20:51
*** GheRivero has quit IRC20:51
ttx"We", being the OpenStack community, should spend our resources getting integration tests written, then20:51
joshuamckentySo can we get a PPB vote, just so I'm clear on the consensus?20:51
*** GheRivero has joined #openstack-meeting20:51
joshuamckentyOpenStack should never slip a release date:20:51
jaypipesjoshuamckenty: vote on what precisely?20:51
anotherjessewhat is the vote on?20:52
joshuamckentyThat OpenStack is a time-based release, no matter the quality20:52
ttxI would slip the release date if I thought it would help in quality. It's usually a few more days at the end.20:52
*** GheRivero has quit IRC20:52
joshuamckentyIt puts a very clear message on openstack's priorities20:52
jaypipesno it doesn't.20:52
*** GheRivero has joined #openstack-meeting20:52
*** russellb has joined #openstack-meeting20:52
znsThose are not the only two options. You can have time and qualirty if you're flexible on scope.20:53
jaypipesyep20:53
joshuamckentynot as a community effort you can't20:53
jaypipesit's all about whether you push back properly.20:53
jaypipesyes you can...20:53
*** GheRivero has quit IRC20:53
joshuamckentyin a company, you can redirect resources from features, to quality20:53
jaypipesyes you most certainly can.'20:53
*** GheRivero has joined #openstack-meeting20:53
anotherjesseyou can not accept patches that aren't improving quality20:53
znsjoshuamckenty: sounds like your opinion, but not necessarily fact or shared...20:53
joshuamckentyin a community, you need a lever against business investment20:53
ttxjoshuamckenty: then you should get the word out there to all those openstack companies you see at your meetups20:54
mtayloranotherjesse: ++20:54
ttxjoshuamckenty: all we can do is say "no more features past next week"20:54
*** GheRivero has quit IRC20:54
ttxand ask core reviewers to not let pass any crap20:54
*** GheRivero has joined #openstack-meeting20:54
jaypipesright.20:55
johnpurttx: agree 100%20:55
zns+120:55
ttxin the end, if nobody works on bugs, adding months to the release won't change a single thing.20:55
anotherjessettx:  / joshuamckenty - and that is exactly what we said at the summit20:55
anotherjesseand all the PTLs agreecd20:55
jaypipesanotherjesse: ++20:55
ttxI think we are having a reasonable state of breakage at feature freeze. Now we need to REALLY switch to bugfixing.20:56
ttxand not just continue to work on features on our end20:56
jbryceso...what are we arguing about right now exactly? it sounds like we have a plan that we think we yield better results if we are sticklers for what gets in and we need companies to commit to quality for the remaining milestones20:56
ttxjbryce: that's the message we need to get out20:56
*** GheRivero has quit IRC20:56
*** GheRivero has joined #openstack-meeting20:56
*** Vek has joined #openstack-meeting20:57
*** mikeyp_ has joined #openstack-meeting20:57
jbrycein terms of what we can do, do all reviewers know what they should be using as new guidelines?20:57
jbrycettx: we'll work on getting that message out20:57
joshuamckentyfair enough. I have a 1pm, gotta run. Good to know what we're working with.20:57
jbrycei just happen to be meeting with managers at several companies next week. this will definitely be on my list of topics20:57
ttxjbryce: a lot of companies said they would invest in strategic contributions, and yet jaypipes has been struggling to get people writing integration tests20:57
*** joshuamckenty has quit IRC20:57
*** glenc has quit IRC20:58
jaypipesjbryce: we need a strong and united PTL voice to the mailing list to say that after E3, the focus is entirely on stabilizing and bug fixing.20:58
*** rkukura has joined #openstack-meeting20:58
ttxand Cish and I have been struggling to get people assigned to known and targeted bugs20:58
mtaylorand for folks doing work on test suites ... get me things I can run consistently and repeatably ... the more tests we can run, the more we can check that quality20:58
ttxVish*20:58
jbryceand we can review progress in a month20:58
*** glenc has joined #openstack-meeting20:58
jaypipesmtaylor: that is the goal.20:58
ewindischIt is pretty short notice to say that for E3. I suppose it is fine if it isn't a hard-fast rule, or if there is a leniency for new code.20:58
mtaylorjaypipes: I know it. :) -- just re-iterating20:58
jbryceewindisch: i believe this is the plan for after e320:59
jbryceok20:59
jbrycewe're up against our time limit20:59
znsGood meeting. It's been a while! Thanks, all.20:59
jbrycethanks everybody. i thought we actually covered some good stuff today20:59
*** GheRivero has quit IRC20:59
ttxand with that.. next meeting is precisely on getting a better handle on release status20:59
mtaylor++20:59
*** cmagina has left #openstack-meeting20:59
jbryce#endmeeting20:59
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"20:59
openstackMeeting ended Tue Jan 17 20:59:47 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-17-20.00.html20:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-17-20.00.txt20:59
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-17-20.00.log.html20:59
*** GheRivero has joined #openstack-meeting20:59
jaypipesewindisch: this is actually something discussed at length at the last summit (stopping feature dev at E321:00
ttxzns, notmyname, vishy, devcamcar: still around ?21:00
notmynamehere21:00
vishyo/21:00
*** GheRivero has quit IRC21:00
zns* present *21:00
*** GheRivero has joined #openstack-meeting21:00
*** jdg has joined #openstack-meeting21:01
*** GheRivero has quit IRC21:01
ttx#startmeeting21:01
openstackMeeting started Tue Jan 17 21:01:34 2012 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.21:01
ttxToday's agenda: http://wiki.openstack.org/Meetings/ProjectMeeting21:01
*** GheRivero has joined #openstack-meeting21:01
ttx#topic Actions from previous meeting21:02
*** openstack changes topic to "Actions from previous meeting"21:02
ttx* gyee to talk to zns about service-endpoint-location milestone targeting21:02
*** GheRivero has quit IRC21:02
*** GheRivero has joined #openstack-meeting21:02
ttxzns, gyee: ?21:03
znsI have to search back on the outcome of that. I asked and got acknowledgement, but not sure about the status. I'd lean towards saying it won't make it in E3.21:03
ttxnor in Essex ?21:03
*** anotherjesse1 has joined #openstack-meeting21:03
znsIf it won't be in E3, then it won't be in Essex. Refer to last meeting :-)21:04
ttxthat was a loaded question :)21:04
ttx* vishy to ping HP on openstack-api-ssl status21:04
*** GheRivero has quit IRC21:04
vishydone21:04
znsjsavak and I have talked about starting an F branch for all new features. WHat's your take on that?21:04
*** GheRivero has joined #openstack-meeting21:04
vishyresult was undetermined21:04
jaypipeshehe21:04
vishythey said that they are under a lot of time pressure but they would try to update it this week21:05
ttxzns: an official F branch sounds like a good way for developers not to work on bugfixes.21:05
jaypipesvishy: please feel free to use me to get answers on that. happy to help.21:05
*** GheRivero has quit IRC21:05
vishyit is just supporting SSL for endpoints, so I actually think that one is ok post e-3 if need be21:05
znsttx: maybe we open an F branch after E4? E5?21:05
*** GheRivero has joined #openstack-meeting21:05
vishyI'm still hoping they get it fixed though21:05
ttxafter E4 yes.21:05
znsttx: deal21:06
ttx#topic Keystone status21:06
*** openstack changes topic to "Keystone status"21:06
*** Tushar has joined #openstack-meeting21:06
ttx#link https://launchpad.net/keystone/+milestone/essex-321:06
vishyjaypipes: ok, I will include you in communication in the future21:06
ttxzns: Is the status on this page accurate ?21:06
znsyes21:06
*** GheRivero has quit IRC21:06
jaypipesvishy: cheers21:06
ttxWhat's the status on:21:06
*** jbryce has quit IRC21:06
ttx* https://blueprints.launchpad.net/keystone/+spec/keystone-client (anotherjesse)21:06
*** GheRivero has joined #openstack-meeting21:06
mtaylorttx, zns: re: opening f branch21:06
ttx(on time for next week ?21:06
mtaylorttx, zns: we should talk, possibly offline, about that21:07
znsttx: that's the one my team is most concerned about since we have not put resources on it. Need input from anotherjesse.21:07
*** GheRivero has quit IRC21:07
*** anotherjesse has quit IRC21:07
ttxmtaylor: sure21:07
ttx* https://blueprints.launchpad.net/keystone/+spec/keystone-configuration (dabo)21:07
*** GheRivero has joined #openstack-meeting21:07
znsThat one is almost ready for merge. SHould be ready.21:08
ttx* https://blueprints.launchpad.net/keystone/+spec/keystone-logging (jheck)21:08
*** GheRivero has quit IRC21:08
ttxheckj, rather21:08
*** GheRivero has joined #openstack-meeting21:08
heckjttx: huh?21:09
znsI've put some work into that. keystone-configuration includes improvements to it. Not sure about status from jheck, but I think we've made enough progress through other blueprints to call it good.21:09
mtaylorttx, zns: (you guys move too fast ...) python-keystoneclient is in all the systems and producing tarballs and whatnot now, in case that's helpful for keystone-client status21:09
*** bmullan_ has joined #openstack-meeting21:09
ttxzns: if any of those 3 miss next week, are you considering an exception for them, or will it be F ?21:09
ttxheckj: status on keystone-logging ?21:10
znsmtaylor: I'm not sure it is being used by all projects, though (maybe only horizon?). Keystone middleware, for example, doesn't use it yet.21:10
ttxanotherjesse1: status on keystone-client blueprint ?21:10
*** GheRivero has quit IRC21:10
mtaylorzns: gotcha21:10
*** GheRivero has joined #openstack-meeting21:10
mtaylorwell, fwiw, it's hooked in to all the things needed for other projects to start depending on it in pip-requires and whatnot21:11
heckjttx: good progress, should be able to wrap up shortly21:11
ttxheckj: cool, thx21:11
znsttx: I'm not considering any exceptions as of now. If anything, I've considered getting the feature in asap and stabilizing after E3, but I hear resistance to E3 being less unstable.21:11
heckjttx: expecting that to be resolved fully by E4 - hoping to close by E321:11
*** GheRivero has quit IRC21:11
ttx#info In other news, we should have a python-keystoneclient tarball deliverable in Keystone E321:11
*** GheRivero has joined #openstack-meeting21:11
ttx#action anotherjesse to sync up with zns on keystone-client blueprint status21:12
ttxzns: Anything else ?21:12
znsnope21:12
*** bhall has joined #openstack-meeting21:12
ttxQuestions for Keystone ?21:12
znstx21:12
*** GheRivero has quit IRC21:12
* jaypipes still thinks the keystone client should be called keystone-cops21:12
*** bhall has quit IRC21:12
*** bhall has joined #openstack-meeting21:12
jk0jaypipes: +121:12
znslol!21:12
*** GheRivero has joined #openstack-meeting21:12
* mtaylor starts the gerrit renaming process...21:12
ttx#topic Swift status21:13
*** openstack changes topic to "Swift status"21:13
ttxnotmyname: o/21:13
notmynamehi21:13
dragondm+121:13
anotherjesse1ttx: the library stuff is done for the client - the CLI is being worked on as we speak - about 1day of work21:13
*** GheRivero has quit IRC21:13
notmynamenot much to report this week. working on new features and bug fixes. I expect the next release to be fairly soon21:13
ttxanotherjesse1: thx21:13
notmynameto include for posting and some bug fixes21:13
*** GheRivero has joined #openstack-meeting21:13
notmynames/for/form/21:13
ttxnotmyname: will it include object versioning ?21:14
*** maoy has joined #openstack-meeting21:14
*** jbryce has joined #openstack-meeting21:14
notmynameprobably not yet.21:14
ttxnotmyname: so 1.4.6 it will be ?21:14
notmynameversioning is probably still a few weeks out21:14
*** GheRivero has quit IRC21:14
notmynameya. the next release is 1.4.621:14
ttxnotmyname: let me know as soon as you have a target date21:14
*** GheRivero has joined #openstack-meeting21:14
notmynamewill do21:14
ttxnotmyname: Anything else ?21:14
notmynamenot unless there are questions21:15
ttxQuestions on Swift ?21:15
*** ohnoimdead has joined #openstack-meeting21:15
jaypipesI did, but now I can't remember... doh.21:15
*** joesavak has joined #openstack-meeting21:15
jaypipesoh, that was it..21:15
* ttx waits21:16
notmynameask away21:16
jaypipesnotmyname: someone on #openstack this morning was asking about whether Swift has a stable/diablo-type branch that backported fixes are going to?21:16
*** GheRivero has quit IRC21:16
*** GheRivero has joined #openstack-meeting21:16
notmynamejaypipes: only major security issues (of which there have been none)21:16
notmynameit hasn't happened, so it hasn't been done21:17
jaypipesnotmyname: ah, gotcha.21:17
ttx#topic Glance status21:17
*** openstack changes topic to "Glance status"21:17
ttx#link https://launchpad.net/glance/+milestone/essex-321:17
*** GheRivero has quit IRC21:17
jaypipesnotmyname: but in the case there is, y'all will create a stable/1.4.x or whatever branch?21:17
*** GheRivero has joined #openstack-meeting21:17
notmynamejaypipes: I'm sure we'll figure something out21:17
jaypipesnotmyname: ok.21:18
ttxjaypipes: a few questions on status...21:18
jaypipesnotmyname: just wanted to make sure I give correct information to people that were asking about it.21:18
notmynamethanks21:18
*** GheRivero has quit IRC21:18
ttx* https://blueprints.launchpad.net/glance/+spec/refactor-internal-api (jaypipes)21:18
jaypipesttx: refresh your page. ;)21:18
ttxjaypipes: ah!21:18
*** GheRivero has joined #openstack-meeting21:18
ttxjaypipes: it's gone!21:19
jaypipesttx: all blueprints and bugs on the E3 status page are in proper order. The only remaining blueprint is one that bcwaldon is working on (adding policy support to Glance, same as Nova)21:19
*** GheRivero has quit IRC21:19
bcwaldonjaypipes: will be MP'd today21:19
ttxbcwaldon: so on track for completion ?21:19
*** GheRivero has joined #openstack-meeting21:19
bcwaldonyep21:19
jaypipesttx: we're in code review on the Swift-style multiprocess/multigreenthreadpool servers, but that should be good to go by E321:20
jaypipesttx: and the remaining unassigned bugs will be assigned by EOD tomorrow21:20
*** GheRivero has quit IRC21:20
*** GheRivero has joined #openstack-meeting21:20
ttxas a sidenote, Essex was a good success in containing the number of new features. Now if we can convert that into buggfixing frenzy...21:20
jaypipesttx: a couple of the Low priority bugs may get pushed out to E4 or so, but the 1 High and 4 Mediums should be done by E321:21
ttxjaypipes: OK21:21
*** GheRivero has quit IRC21:21
ttxjaypipes: Anything else ?21:21
jaypipesttx: I've been kind of splitting my time recently between Glance and Tempest (about 40/60%), so sorry about the lag in status updates on Glance.21:21
*** GheRivero has joined #openstack-meeting21:21
*** mcohen has joined #openstack-meeting21:21
ttxyou prefer to bust me with last minute updates21:22
mtaylorjaypipes: just commented on the glance config devstack bug ... does applying the nova fix seem workable to you?21:22
jaypipesttx: :)21:22
jaypipesmtaylor: will take offline21:22
ttxOther questions on Glance ?21:22
*** GheRivero has quit IRC21:22
*** GheRivero has joined #openstack-meeting21:22
ttx#topic Nova status21:23
*** GheRivero has quit IRC21:23
*** openstack changes topic to "Nova status"21:23
ttxvishy: o/21:23
vishyhi21:23
ttx#link https://launchpad.net/nova/+milestone/essex-321:23
ttxLooks like we'll have a few high-prio misses:21:23
*** GheRivero has joined #openstack-meeting21:23
ttx* https://blueprints.launchpad.net/nova/+spec/separate-nova-adminapi (bcwaldon)21:23
ttx(unless it's unblocked ?)21:24
vishyit is unblocked21:24
bcwaldonttx: unblocked this morning, we've got a clear path forward21:24
bcwaldonttx: it will land this week21:24
*** GheRivero has quit IRC21:24
vishywe're going to do it by adding policy checks to the extensions21:24
ttxmarking good progress21:24
*** GheRivero has joined #openstack-meeting21:24
ttx* https://blueprints.launchpad.net/nova/+spec/volume-type-scheduler (vladimir3p)21:25
ttxvishy: we'll miss this one, right ?21:25
*** GheRivero has quit IRC21:25
ttxWhat is plan B for this one ? E4 or F ?21:25
*** GheRivero has joined #openstack-meeting21:25
vishyyes that one will be missed21:25
vishyi guess vladimir is too busy21:26
vishyI think we will have to do without it21:26
ttxso F it is ?21:26
vishylooks like F to me21:26
vishyI'm fiddling with scheduler stuff this week for a couple other blueprints21:26
*** GheRivero has quit IRC21:26
ttxok, we'll defer next week if nothing landed21:26
vishyso I will try and see if it can be done externally21:26
*** GheRivero has joined #openstack-meeting21:26
ttxAlso going slowly and in jeopardy (medium-prio):21:26
vishyI think there is a way to do it with an external scheduler21:26
ttx* https://blueprints.launchpad.net/nova/+spec/openstack-api-ssl (HP)21:27
ttx* https://blueprints.launchpad.net/nova/+spec/scaling-zones (comstud)21:27
ttxunless someone has good news.21:27
vishya) is in jeopardy, I'm not sure if they will get to it but I think that is e4 no problem21:27
vishyb) comstud assures me it will be complete21:27
*** GheRivero has quit IRC21:27
vishythe majority of the work is in a patch under review21:27
vishywhich is not linked properly21:27
*** GheRivero has joined #openstack-meeting21:27
ttxok. All in all it sounds like a fair feature freeze waiting for us next week.21:28
ttxvishy: we'll try to find a way to get popular bugs some attention, starting next week and throughout E421:28
vishyyes21:29
vishyI think the bugsquash day will be a good time to kick that off21:29
ttxI want people to know where they can help and make a difference21:29
jog0any plans to fix up the numerous HACKING violations?21:29
ttxthe bugsquash day will definitely help in getting legacy stuff out of the way21:29
*** GheRivero has quit IRC21:29
Vekjog0: wasn't someone working on a tool to help us find them?21:29
*** GheRivero has joined #openstack-meeting21:29
ttxvishy: would be also good to push nova-core to get a bit more anal retentive as we make progress towards Essex21:30
Vekthat would probably be the first step toward fixing those up...21:30
jog0Vek: Yes I am, but I can use some help fixing the problems21:30
ewindischThe ZeroMQ blueprint is actually making considerable progress and should be ready for E3.  I've been emailing Duncan on it, but he hasn't been responding for nearly a month - Duncan owns the blueprint, officially.21:30
vishyyessir21:30
vishyewindisch: if you can get a proposal in we will look at it21:30
ttxewindisch: the deadline is Tuesday next week21:30
vishybut I'm not sure it is a huge deal, you could easily ship the driver separately if need be21:30
ttxvishy: Anything else ?21:31
ewindischvishy, true, but I'd like to get it included if possible.21:31
russellbsame with the qpid equivalent :-)21:31
*** GheRivero has quit IRC21:31
vishyewindisch: sure21:31
russellbbut i think that one is close21:31
*** GheRivero has joined #openstack-meeting21:31
ttxNova subteam leads: anything on your side ?21:32
ttxQuestions on Nova ?21:33
ttx#topic Horizon status21:33
*** openstack changes topic to "Horizon status"21:33
*** GheRivero has quit IRC21:33
ttxdevcamcar: around ?21:33
ohnoimdead<- filling in for devcamcar (currently stuck in his car on snowy seattle roads)21:33
*** GheRivero has joined #openstack-meeting21:33
ttxohnoimdead: welcome :)21:34
ohnoimdead:D21:34
ttx#link https://launchpad.net/horizon/+milestone/essex-321:34
ttxSo... ext-roles was deferred. Looks like you're preparing yourself for a busy E4 :)21:34
ttxPrioritization will be key.21:34
*** GheRivero has quit IRC21:34
ohnoimdeadyeah. we punted a few things to e4. still a nasty bunch of bugs for e3 too.21:34
*** ewanmellor has quit IRC21:34
*** GheRivero has joined #openstack-meeting21:34
ttxohnoimdead: from what I'm seeing you have a good handle on them21:34
ttxohnoimdead: so I have no question. Anything you wanetd to mention ?21:35
ohnoimdeadnope21:35
ttxQuestions for Horizon ?21:35
ohnoimdead(not that i can think of anyway)21:35
*** joesavak has quit IRC21:36
ttx#topic Incubated projects and other Team reports21:36
*** GheRivero has quit IRC21:36
*** openstack changes topic to "Incubated projects and other Team reports"21:36
ttxdanwent: o/21:36
danwenthello21:36
danwenthttps://launchpad.net/quantum/+milestone/essex-321:36
ttxtroytoman is stuck in some training21:36
danwentwe're a bit behind21:36
*** GheRivero has joined #openstack-meeting21:36
wwkeyboard721:36
danwentthough a lot of the code for review just landed.21:37
danwentin terms of nova code, I think the floating IP stuff should make it (enable floating IPs for quantum manager)21:37
danwentthe VPN stuff may not (debo has been fighting with devstack today)21:37
*** GheRivero has quit IRC21:37
ttxdanwent: looks like a busy week ahead21:37
danwentsigh....21:37
danwentindeed21:37
*** GheRivero has joined #openstack-meeting21:37
danwentwe'll bump one or two things out21:37
ttxdanwent: we shall branch milestone-proposed at the end of Tuesday (i.e. Wednesday morning European time)21:38
ttxdanwent: would that work for you ?21:38
danwentyup.  thanks again for getting quantum into the standard release processing21:38
*** GheRivero has quit IRC21:38
ttxQuantum and Melange now have working -tarball jobs21:38
danwenti think all issues monty + james have had are working now21:38
danwentyup21:38
ttxso everything should be ready for getting E3 released under release team management21:38
*** GheRivero has joined #openstack-meeting21:38
danwentwe're also going to push to get something whipped up with tempest… that's all for quantum.21:39
ttxAny other team lead with a status report ? annegentle (docs), mtaylor (CI), jaypipes (QA) ?21:39
annegentle0/21:39
ttxannegentle: floor is yours21:39
*** GheRivero has quit IRC21:39
annegentleor is it o/ ? anyway21:39
mtaylorttx: o/ after anne21:39
annegentleI sent the note to the mailing list about a "diablo stable" install doc21:39
vishydepends if you are a cyclops...21:39
*** GheRivero has joined #openstack-meeting21:39
jaypipesttx: I'll be sending out a status report on Tempest tomorrow.21:40
annegentlesounds like the community is on board with that approach for now21:40
annegentlebut I'm happy to entertain other ideas21:40
*** GheRivero has quit IRC21:40
*** GheRivero has joined #openstack-meeting21:40
ttxannegentle: that doc points to cloudbuilders packages ?21:41
annegentlewe're also making progress on building an API reference site (though we're tracking down api.openstack.org, if you registered it please let me know)21:41
*** salv-orlando has joined #openstack-meeting21:41
*** lloydde has joined #openstack-meeting21:41
annegentlettx: it points to Cloud Builders packages and ones from Managed IT (Kiall)21:41
ttxannegentle: any reason why we don't use Oneiric official Ubuntu ones ?21:41
russellbstable/diablo is also packaged in Fedora21:41
annegentlettx: the OpenStack Starter Guide does (point to Ubuntu official). This is an additional installation guide that gets Keystone and Dashboard on Ubuntu.21:42
ttxannegentle: ok21:42
*** GheRivero has quit IRC21:42
annegentlerussellb: this guide is built so that additional distros instructions can be added easily.21:42
ttxannegentle: anything else ?*21:42
*** GheRivero has joined #openstack-meeting21:42
annegentleIt's really a starting point to build from - a first step in separating install from admin also, which will take more work.21:43
russellbannegentle: cool.  we don't have dashboard packaged yet.  we'll look at helping with the docs though.21:43
annegentleThat's all from the land of docs.21:43
ttxmtaylor: go ahead21:43
annegentlerussellb: much appreciated!21:43
mtaylorI'm planning on having multi-python testing rolled out next week- we've had several issues with this recently.21:43
ttxmtaylor: I'd like to have tarball/repo diff jobs as well, we keep getting hit by surpises in that area21:43
mtaylorbut that'll be a dev-visible change21:43
mtaylorttx: funny story...21:43
mtaylorttx: the new hotness for doing the multi-version testing gets you that as well21:44
mtayloras it makes an sdist and then installs _that_ into the virtualenv, and then does the testing21:44
ttxmtaylor: I need to see that with my own eyes21:44
Vekheh.21:44
*** GheRivero has quit IRC21:44
dragondmre mult-python testing: ...and there was much rejoicing.21:44
mtaylorso we actually start testing the tarball, rather than the repo21:44
Vek+121:44
*** novas0x2a|laptop has quit IRC21:44
sorenmtaylor: Sadly, many things missing from tarball won't cause test failures.21:44
ttxmtaylor: you'll still miss the "missing binaries" issues, I guess21:44
*** GheRivero has joined #openstack-meeting21:44
sorenmtaylor: like that ^21:44
ttxI'm pretty sure tests pass if bin/nova-api-ec2 is missing for example.21:45
mtaylorsoren, ttx: those should be filed as missing test cases or something21:45
sorenmtaylor: But yes, many things will be caught by that.21:45
mtaylorit's a start at least :)21:45
ttxok21:45
*** debo-os has joined #openstack-meeting21:45
ttxmtaylor: anything else ?21:45
mtaylorbut yes - I agree with both of you21:45
sorenmtaylor: Not everything will have test cases like that.21:46
*** dprince has quit IRC21:46
mtaylornope, that's it - I just wanted to bring that up because it'll be a slight change that people will notice21:46
ttxFrom release management land, markmc has worked on 2011.3.1 tarballs for Nova and Glance21:46
sorenmtaylor: We have no unit tests for the existence of docs, for instance.21:46
ttx#help Would be good to get those 2011.3.1 candidates out for a date21:46
*** davlap has joined #openstack-meeting21:46
Vekthe one downside of the multipython testing will probably be that the unit tests will take twice as long to run once a mp is approved...21:47
mtaylorsoren: ++21:47
mtaylorVek: not necessarily - we can parallelize that21:47
ttxand without further ado...21:47
*** GheRivero has quit IRC21:47
ttx#topic Open discussion21:47
*** openstack changes topic to "Open discussion"21:47
Vekgood :)21:47
ttx#info So the winner is... Folsom21:47
*** GheRivero has joined #openstack-meeting21:47
danwentyes!21:48
ttxby an overwhelming 50 votes, Freedom was second with 35 votes, Fortuna had 3321:48
ttxIn related news, the F design summit location and date was announced:21:48
ttx#info F design summit: April 16-18, San Francisco, CA21:48
ttx#link http://www.openstack.org/conference/san-francisco-2012/21:48
ttxIt will be followed by an OpenStack Conference, same place, April 19-20.21:49
ttxAnything else, anyone ?21:49
ttxBug squashing day is still on Groundhog day, Feb 221:49
annegentleBug Squash day links:21:49
annegentle#link San Fran http://www.meetup.com/openstack/events/48362422/21:49
annegentle#link Austin http://www.meetup.com/OpenStack-Austin/events/48406252/21:50
ttxIs anyone interested in tracking stats for the bug squashing day ?21:50
ttxI think reed will be on a plane that day21:50
*** somik has joined #openstack-meeting21:50
*** GheRivero has quit IRC21:50
*** johnpur has quit IRC21:50
*** GheRivero has joined #openstack-meeting21:50
annegentlettx: with an already exiting tool or one to be made soon?21:51
ttxannegentle: probably with custom made tools.21:52
ttxannegentle: Ubuntu used things like http://people.canonical.com/~brian/complete-graphs/nautilus/plots/nautilus-1day-triaging.png21:52
ttxto track progress during the day21:52
ttxI guess I could ask brian for his magic scripts21:52
ttx#help Anyone interested in coordinating the Bug Squashing day should contact annegentle or ttx21:53
ttxand if nobody has anything else...21:54
ttx#endmeeting21:54
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"21:54
*** GheRivero has quit IRC21:54
openstackMeeting ended Tue Jan 17 21:54:33 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-17-21.01.html21:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-17-21.01.txt21:54
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-17-21.01.log.html21:54
*** GheRivero has joined #openstack-meeting21:54
*** Vek has left #openstack-meeting21:54
*** Tushar has quit IRC21:55
*** bmullan_ has quit IRC21:56
*** mikeyp_ has quit IRC21:56
*** Vell has joined #openstack-meeting21:57
*** edgarmagana has joined #openstack-meeting21:58
*** glenc has quit IRC21:59
danwento/ netstack22:00
*** zigo has quit IRC22:00
*** glenc has joined #openstack-meeting22:00
markvoelkero/22:00
*** russellb has left #openstack-meeting22:00
danwent#startmeeting22:00
openstackMeeting started Tue Jan 17 22:00:48 2012 UTC.  The chair is danwent. Information about MeetBot at http://wiki.debian.org/MeetBot.22:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.22:00
danwenthow've you been mark?22:00
salv-orlandoHello!22:00
markvoelkerdanwent: doing good thanks!22:01
somikhi folks!22:01
danwent#info agenda for today's meeting: http://wiki.openstack.org/Network/Meetings22:01
edgarmaganaciao22:01
*** GheRivero has quit IRC22:01
danwent#topic General Topics22:01
mesteryHi everyone!22:01
*** openstack changes topic to "General Topics"22:01
danwent#info F-series release will be 'folsom'22:01
*** GheRivero has joined #openstack-meeting22:01
danwent#info Folsom design summit: April 16-18, San Francisco, CA (http://www.openstack.org/conference/san-francisco-2012/)22:02
GheRivero_night evryone22:02
danwentsign-up is not yet open, but remember to block out the dates on your schedule.22:02
*** GheRivero has quit IRC22:02
*** jlm^ has joined #openstack-meeting22:02
danwent#topic Quantum Status22:02
*** openstack changes topic to "Quantum Status"22:02
*** GheRivero has joined #openstack-meeting22:02
danwent#info next tuesday is quantum feature freeze for E-3: https://launchpad.net/quantum/+milestone/essex-322:03
*** GheRivero has quit IRC22:03
*** SumitNaiksatam has joined #openstack-meeting22:03
*** GheRivero_ is now known as GheRivero22:03
salv-orlandodanwent: feature freeze or branch point for E-3?22:03
*** vlan-os has joined #openstack-meeting22:03
danwentwe still have a LOT of issues not yet in review.  want to those things on gerrit by thursday/friday at the latest, if they are non-trivial reviews.22:03
danwentsalv-orlando: meant the same thing.. yeah, only referring to E-3 here.22:04
salv-orlandok, cool22:04
danwentwe can pull bug fixes into E-3 branch if really needed, but definitely not features (and preferrably, no minor bugs)22:04
danwentThanks to all those who did reviews in the past week, our existing set of reviews is large, but doable, I think22:05
danwent#info: current reviews: https://review.openstack.org/#q,status:open+project:openstack/quantum,n,z22:05
danwentI wanted to highlight a couple of larger patches that we should start reviewing soon, as they may take some iteration.22:05
danwentfirst, mtaylor will soon be pushing a review for removing the client code from the main repo.22:06
danwentthis obviously has the potential to be disruptive, so lots of review TLC is in order.22:06
danwentAlso, Salv's API work has two large reivews:  API filters and API error codes (seem ML for discussion)22:07
*** jk0 has left #openstack-meeting22:07
danwentsalv: wanted to get your thoughts on: Bug #80308622:07
uvirtbotLaunchpad bug 803086 in quantum "plugins.ini should be collapsed into quantum.conf to prevent configuration"sprawl"" [Medium,In progress] https://launchpad.net/bugs/80308622:07
*** jbryce has quit IRC22:07
danwentseems like there is a lot of review feedback, I was trying to understand the current status22:07
danwentsalv-orlando?22:08
salv-orlandoI'm here22:08
danwentthoughts on Bug #80308622:09
uvirtbotLaunchpad bug 803086 in quantum "plugins.ini should be collapsed into quantum.conf to prevent configuration"sprawl"" [Medium,In progress] https://launchpad.net/bugs/80308622:09
salv-orlandoI read your comment - last time I checked I was pretty sure the "old" behaviour (plugins.ini) still worked. Will have another crack22:09
salv-orlandoright today22:09
salv-orlandoLast time I checked was on Jan 1022:09
danwentOk, let me re-run my tests as well.  might have been on an old version or something.22:09
danwentOk, anyone from the Ryu controller team here today?22:09
danwentI will respond on the ML in more detail, but my gut feeling is that this code should actually be a separate plugin, as it seems like primary overlap in functionality is just around the SQLalchemy DB model.22:10
salv-orlando+122:11
danwentI'd like to create a base "sqlalchemy_plugin_base" class to make it easier for plugins to share DB code.22:11
danwent#todo #danwent ML reply to Ryu controller team22:11
danwentOk, any other large reviews out there (or coming soon) that I missed?22:11
*** jbryce has joined #openstack-meeting22:12
danwentunfortunately, our core reveiwers will again be pretty swamped this release, so we need all cover devs to pitch in22:12
salv-orlandoI have a patch22:12
*** jbryce has quit IRC22:12
salv-orlandowhich is going to be pushed soon which is around 200-300 hundred lines. It is for response pagination.22:12
salv-orlandocan't remember the bug id right now, sorry.22:12
danwentOk, that's been targeted for E-3 for a while, right?22:12
salv-orlandoYeah. Code is basically ready, but i still need to sort out XML serialization for the link to the next page.22:13
danwentcool.  just wanted to confirm it wasn't something brand new.  sounds good.22:13
SumitNaiksatamdan: I am planning to submit the linux bridge plugin for review22:13
salv-orlandowill either push tomorrow or defer22:13
salv-orlandoodds are 4/11 to push tomorrow 3/1 to defer22:13
*** adam_g has quit IRC22:14
danwentYeah, any big patches should be in by thursday.22:14
danwentSumit:  ok, just make sure we get it in early, and be sure to help out with others reviews as a thank you :)22:14
SumitNaiksatamdan: sure, edgar is my proxy :-)22:15
edgarmagana:-)22:15
danwentindeed, but we need all the help we can get reviewing.22:15
SumitNaiksatamdan: yeah, kidding :-)22:15
danwentgood good :)22:15
danwentok, is debo here?22:15
danwenti injected a VPN item into the agenda last minute22:16
debo-osyeah22:16
danwentOk, cloudpipe thoughts?22:16
debo-osThx a lot for the feedback22:16
debo-osI think I summarized the feedback and the action items for cloudpipe on the ML22:17
debo-oswe will aim to do a no frills version for E22:17
debo-osassuming that a lot of will change with the real VPN service in F22:17
danwentdebo-os:  I think that makes sense.22:17
danwentmy main concern is whether we can get anything into Nova during E-4…. they will be in a pretty hard feature freeze based on concerns over stabalization22:18
danwentI would say that if you don't think you can do something in the next few days, and have a shot for E-3, we should ping vish to get his thoughts on this.22:19
debo-osI will try to make it to E3 but lets ping Vish anyway22:19
danwentwould help to have it well scoped what changes you would be making to nova, as I think they will be pretty targeted.22:19
danwentok, good idea.22:19
debo-osI think I have the changes scoped out for Nova and I had run them past Soren and Vish22:19
danwentOk, anything else in terms of e-3?22:19
danwentOk, one topic I wanted to bring up with Nova + Quantum Integration testing22:20
danwentwe get a fair amount of breakage in QuantumManager due to nova changes, and presumably the fact that the unit tests + smoke tests run before nova commits don't test QuantumManager well.22:21
danwentjaypipes sent out a cool preso on Tempest, if you haven't seen it yet: https://docs.google.com/a/nicira.com/presentation/d/1M3XhAco_0u7NZQn3Gz53z9VOHHrkQBzEs5gt43ZvhOc/edit#slide=id.p22:21
debo-oson that note ... Dan, would it make sense to focus on devstack stability w. Quantum + Nova22:21
debo-osultimately a naive user would use something like devstack22:22
bhalldanwent: do you have another link?22:22
danwentI think we've made good progress on Nova-parity with Essex, but not very much progess with system test.22:22
danwentbhall: that one not working?22:22
jaypipesbhall: http://joinfu.com/slides22:22
bhalljaypipes: thanks22:22
jaypipesnp22:23
danwentwhoops, yeah, not public22:23
danwentdebo-os: yes… devstack stability is a start22:23
danwentand things like tempest build on devstack22:23
danwentI'd really like to see us making more progress on this front.  I'm going to start poking on it in my "free" time, but I'd really love if someone decided to take some more ownership here.22:24
danwentI'm pretty swamped with a lot of project management stuff22:24
danwentand haven't had as much time to code as I would like.22:24
danwent#info On a related note, we have our bug-squashing day on Feb 2nd.22:25
*** lennox has joined #openstack-meeting22:25
GheRiverois that test integration for essex or folsom release?22:25
danwentI think we need to get the infrastructure in place ASAP.  I'd love to see work done in E-4, but if not, then it will need to happen in F22:26
danwenthttp://wiki.openstack.org/BugSquashingDay/2012020222:26
*** heckj has quit IRC22:26
bhalldanwent: I agree.. we definitely need it22:26
*** lennox has quit IRC22:26
*** Vell has quit IRC22:26
danwentsince we were thinking of focusing on code quality + coverage for bug squashing, one thing we could do was help people setup devstack + tempest and write integration tests.22:27
debo-osI can do devstack and tempest setup22:27
danwentThere is a local meetup in SF, which might serve as a central location (sorry salv!) or we could meet in the southbay.22:27
debo-osand maybe some tests too22:27
debo-ossouthbay :)22:27
danwentdebo-os: that would be awesome.22:27
salv-orlandomy thoughts will be with you :)22:28
salv-orlandoanyway, what are your targets for the bug squashing day... what will be considered as a success?22:28
danwentdebo-os:  Ok, I will sync up with you directly on this.  Perhaps Nicira or Cisco could play host for an in person meetup.  I will send an email to the list to see if there are enough people who would like to meet up in person for the bug squashing day to make organizing an event worth it.22:28
*** pballand has joined #openstack-meeting22:28
*** bcwaldon has left #openstack-meeting22:29
danwentsalv-orlando:  my goal was to get a functioning system test environment up and running, with multiple people knowledgeable enough to add tests.22:29
debo-osdanwent: awesome ...22:29
danwentcarlp says he has infrastructure to run these tests automatically on each commit, which is ultimately what we want.22:29
danwentGreat, thanks for volunteering debo.22:30
danwent#todo #debo-os and #danwent sync up on tempest + system testing22:30
danwentI think this stuff is realy important for the success of the project.22:30
danwentOK, one last topic to bring-up.22:30
danwentSince we are getting close to the main essex release, we want to make sure that distros that package quantum have correct packaging, and are aware of recent changes to our packaging (e.g., splitting client repo out).22:31
danwentthere are a few listed here: http://wiki.openstack.org/QuantumPackages22:31
cdubdanwent: if that's a question, fedora is aware22:32
danwentI'll also be contacting folks at Stackops, etc.22:32
danwentcdub: great, will assume you have that taken care of.22:32
cdubyup, rkukura will holler if things break22:32
danwentif there are other distros that any of you think should package quantum, but don't, let's add them to the page and reach out to them.22:32
*** deshantm_ has joined #openstack-meeting22:33
danwentOk, any other topics to bring up on Quantum? or open discussion?22:33
GheRiveroi'm taking care of debian packages and also stackosp22:33
danwentawesome, thanks GehRivero.  Does stackops package quantum already, or will it be new with the final Essex release?22:33
danwentGeh -> Ghe22:33
bhalldanwent: did you and monty chat about how plugins are going to work with the repo split?22:34
GheRiveroit's a work in progress22:34
danwentbased on his reply, I think his comment about plugins wasn't related to the repo split22:34
danwentGheRivero: thx22:34
anotherjesse1danwent: love the work you guys are doing for devstack integration22:34
bhalloh ok22:34
anotherjesse1thanks :)22:34
danwentanotherjesse1:  thanks!  was just thinking the same thing about all the cool stuff you folks have been doing with devstack!22:35
danwentmakes a devs life so much easier22:35
danwentOk, last call, any questions/comments?22:35
cdubany folks going to FOSDEM?22:35
danwentnot I… wish I could22:36
anotherjesse1danwent: we do multi-node devstack by setting ENABLED_SERVICES=n-cpu,n-net,n-api (and MYSQL_HOST, RABBIT_HOST, GLANCE_HOSTPORT) - is it possible to do multi-node quantum?22:36
anotherjesse1perhaps an email?22:36
*** deshantm has quit IRC22:36
*** deshantm_ is now known as deshantm22:36
danwentanotherjesse1:  yes, quantum can do multi-node22:37
danwentwas planning on looking at how to do multi-node in devstack.  please send email with thoughts.22:37
bhallanotherjesse1: I have it working on our end.. I have some changes to propose around that fairly soon22:37
danwentlast i checked it was "coming soon" on the webpage, or is it already supported?22:37
danwentah, got it22:37
danwentyeah, multi-node will be very important to us using devstack for serious system test.22:38
danwentthanks folks.  please remember to focus on reviews this week, and if you have non-trivial patches, to get them done by thursday.22:38
danwent#endmeeting22:38
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"22:38
openstackMeeting ended Tue Jan 17 22:38:51 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:38
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-17-22.00.html22:38
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-17-22.00.txt22:38
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-17-22.00.log.html22:38
*** jlm^ has left #openstack-meeting22:39
*** markvoelker has quit IRC22:39
danwenthave a good afternoon/night folks!22:39
salv-orlandobye!!!22:39
wwkeyboardthanks for the information22:39
*** rkukura has quit IRC22:40
somikhave a good one everybody!22:40
*** maoy has quit IRC22:41
*** sparkycollier has quit IRC22:41
*** GheRivero has quit IRC22:41
*** Gordonz has quit IRC22:44
*** adam_g has joined #openstack-meeting22:45
*** novas0x2a|laptop has joined #openstack-meeting22:46
*** jaypipes is now known as jaypipes-afk22:47
*** mcohen has left #openstack-meeting22:47
*** debo-os has quit IRC22:50
*** jdg has quit IRC22:53
*** jdg has joined #openstack-meeting22:55
*** jwalcik has quit IRC23:05
*** jdg has quit IRC23:13
anotherjesse1danwent: I'll prioritize documentation23:20
danwentanotherjesse1:  cool, thanks23:21
*** debo-os has joined #openstack-meeting23:43
*** edgarmagana has quit IRC23:46
*** mattray has quit IRC23:47
*** rnirmal has quit IRC23:55

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