Tuesday, 2012-08-07

*** matiu has joined #openstack-meeting00:00
*** matiu has quit IRC00:00
*** matiu has joined #openstack-meeting00:00
*** sdake_ has quit IRC00:11
*** maoy has joined #openstack-meeting00:13
*** kindaopsdevy has quit IRC00:18
*** kindaopsdevy has joined #openstack-meeting00:18
*** danwent has joined #openstack-meeting00:18
*** sdake has joined #openstack-meeting00:29
*** Gordonz has joined #openstack-meeting00:33
*** johnpur has left #openstack-meeting00:35
*** ncode has quit IRC00:39
*** gyee has quit IRC00:45
*** matwood has quit IRC00:49
*** novas0x2a|laptop has quit IRC00:56
*** sdake has quit IRC00:57
*** sdake has joined #openstack-meeting01:00
*** kindaopsdevy has quit IRC01:00
*** Gordonz has quit IRC01:03
*** matiu has quit IRC01:04
*** jdurgin has quit IRC01:05
*** ncode has joined #openstack-meeting01:08
*** markmcclain has joined #openstack-meeting01:09
*** oubiwann1 has quit IRC01:16
*** zhuadl has quit IRC01:25
*** danwent has quit IRC01:34
*** bencherian has quit IRC01:38
*** adjohn has quit IRC01:39
*** jakedahn_zz is now known as jakedahn01:40
*** PotHix has quit IRC01:40
*** johnpostlethwait has joined #openstack-meeting01:53
*** matwood has joined #openstack-meeting01:58
*** edgarmagana has quit IRC02:06
*** johnpostlethwait has quit IRC02:06
*** sdake has quit IRC02:18
*** zhuadl has joined #openstack-meeting02:24
*** yoshiotu has quit IRC02:25
*** danwent has joined #openstack-meeting02:29
*** ayoung has quit IRC02:33
*** rkukura has quit IRC02:35
*** rkukura has joined #openstack-meeting02:36
*** kindaopsdevy has joined #openstack-meeting02:36
*** s0mik has joined #openstack-meeting02:41
*** Mandell has joined #openstack-meeting02:43
*** tongli has joined #openstack-meeting02:44
*** sdake has joined #openstack-meeting02:45
*** dolphm has joined #openstack-meeting02:47
*** dolphm has quit IRC02:53
*** nati_ueno has left #openstack-meeting02:54
*** nati_ueno has quit IRC02:54
*** bencherian has joined #openstack-meeting02:57
*** tongli has quit IRC03:03
*** kindaopsdevy has quit IRC03:03
*** ncode has quit IRC03:08
*** lloydde has joined #openstack-meeting03:10
*** Mandell has quit IRC03:10
*** alrs has quit IRC03:11
*** ryanpetrello has quit IRC03:12
*** lloydde has quit IRC03:13
*** ryanpetrello has joined #openstack-meeting03:13
*** dolphm has joined #openstack-meeting03:18
*** s0mik has quit IRC03:25
*** s0mik has joined #openstack-meeting03:27
*** s0mik has quit IRC03:28
*** Mandell has joined #openstack-meeting03:30
*** dolphm has quit IRC03:34
*** adjohn has joined #openstack-meeting03:45
*** koolhead17 has joined #openstack-meeting03:55
*** adjohn has quit IRC03:58
*** zhuadl has quit IRC04:06
*** dolphm has joined #openstack-meeting04:17
*** ryanpetrello has quit IRC04:22
*** koolhead17 has quit IRC04:26
*** Mandell has quit IRC04:34
*** markmcclain has quit IRC04:39
*** zhuadl has joined #openstack-meeting04:48
*** dolphm has quit IRC05:03
*** maoy has quit IRC05:09
*** Mandell has joined #openstack-meeting05:15
*** jog0 has quit IRC05:15
*** garyk has joined #openstack-meeting05:23
*** shang has quit IRC05:53
*** shang has joined #openstack-meeting05:54
*** rafaduran has joined #openstack-meeting06:02
*** adjohn has joined #openstack-meeting06:22
*** littleidea has quit IRC06:35
*** Mandell has quit IRC06:45
*** EmilienM has joined #openstack-meeting07:03
*** jamespage has joined #openstack-meeting07:06
*** johnpostlethwait has joined #openstack-meeting07:31
*** oubiwann has quit IRC07:43
*** huats has quit IRC07:43
*** cp16net has quit IRC07:43
*** davidkranz has quit IRC07:43
*** nikhil has quit IRC07:43
*** DuncanT has quit IRC07:43
*** rturk has quit IRC07:43
*** Blake_Yeager has quit IRC07:43
*** tr3buchet has quit IRC07:43
*** xtoddx has quit IRC07:43
*** bencherian has quit IRC07:47
*** bencherian has joined #openstack-meeting07:48
*** bencherian has quit IRC07:52
*** johnpostlethwait has quit IRC07:57
*** adjohn has quit IRC08:02
*** darraghb has joined #openstack-meeting08:05
*** derekh has joined #openstack-meeting08:08
*** oubiwann has joined #openstack-meeting08:11
*** huats has joined #openstack-meeting08:11
*** cp16net has joined #openstack-meeting08:11
*** davidkranz has joined #openstack-meeting08:11
*** nikhil has joined #openstack-meeting08:11
*** DuncanT has joined #openstack-meeting08:11
*** rturk has joined #openstack-meeting08:11
*** Blake_Yeager has joined #openstack-meeting08:11
*** tr3buchet has joined #openstack-meeting08:11
*** xtoddx has joined #openstack-meeting08:11
*** SumitNaiksatam has quit IRC08:19
*** jjm3 has quit IRC08:19
*** reed has joined #openstack-meeting08:42
*** matwood has quit IRC09:02
*** shang_ has joined #openstack-meeting09:12
*** jakedahn is now known as jakedahn_zz09:12
*** shang has quit IRC09:15
*** goldfish has joined #openstack-meeting09:53
*** danwent has quit IRC09:58
*** zhuadl has quit IRC10:22
*** maoy has joined #openstack-meeting11:16
*** hggdh has quit IRC11:38
*** hggdh has joined #openstack-meeting11:39
*** kiffer84 has quit IRC11:46
*** milner has joined #openstack-meeting11:48
*** markvoelker has joined #openstack-meeting11:53
*** dwcramer has quit IRC12:02
*** dprince has joined #openstack-meeting12:08
*** littleidea has joined #openstack-meeting12:20
*** littleidea has quit IRC12:22
*** jrd-redhat has quit IRC12:25
*** rkukura has quit IRC12:40
*** huats has quit IRC12:44
*** maoy has quit IRC12:50
*** troytoman-away is now known as troytoman12:56
*** markmcclain has joined #openstack-meeting13:09
*** jaypipes has joined #openstack-meeting13:09
*** sandywalsh has joined #openstack-meeting13:10
*** dwcramer has joined #openstack-meeting13:11
*** DuncanT has quit IRC13:13
*** DuncanT has joined #openstack-meeting13:13
*** jrd-redhat has joined #openstack-meeting13:14
*** sandywalsh has quit IRC13:15
*** tongli has joined #openstack-meeting13:19
*** dolphm has joined #openstack-meeting13:19
*** dwcramer has quit IRC13:23
*** ayoung has joined #openstack-meeting13:30
*** zhuadl has joined #openstack-meeting13:32
*** markmcclain has quit IRC13:33
*** mattray has joined #openstack-meeting13:44
*** dwcramer has joined #openstack-meeting13:45
*** ncode has joined #openstack-meeting13:46
*** dendro-afk is now known as dendrobates13:46
*** primeministerp has joined #openstack-meeting13:49
*** sandywalsh has joined #openstack-meeting13:55
*** ecarlin has joined #openstack-meeting14:02
*** markmcclain has joined #openstack-meeting14:09
*** Mandell has joined #openstack-meeting14:11
*** lloydde has joined #openstack-meeting14:20
*** matiu has joined #openstack-meeting14:20
*** matiu has quit IRC14:24
*** maoy has joined #openstack-meeting14:25
*** Mandell has quit IRC14:33
*** cp16net is now known as cp16net|away14:34
*** cp16net|away is now known as cp16net14:34
*** mattray has quit IRC14:39
*** matwood has joined #openstack-meeting14:41
*** zhuadl has quit IRC14:42
*** danwent has joined #openstack-meeting14:44
*** troytoman is now known as troytoman-away14:45
*** _0x44 has quit IRC14:47
*** andrewbogott_afk is now known as andrewbogott14:50
*** _0x44 has joined #openstack-meeting14:50
primeministerphyper-v meeting will start in 9 minutes14:52
*** rkukura has joined #openstack-meeting14:53
*** Gordonz has joined #openstack-meeting14:55
openstackMeeting started Tue Aug  7 15:00:43 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
primeministerp#topic Openstack Compute for Hyper-V15:00
*** openstack changes topic to "Openstack Compute for Hyper-V"15:01
primeministerpmorning everyone15:01
primeministerpwe'll start the meeting today by discussing the current status of the integration work for folsom15:01
*** sdake has quit IRC15:02
*** sdake has joined #openstack-meeting15:02
primeministerpalessandro isn't on the channel yet15:02
*** alexpilotti has joined #openstack-meeting15:03
primeministerpalexpilotti: there you are15:03
alexpilottihi everybody15:03
primeministerpalexpilotti: is pedro going to join?15:03
alexpilottiI guess so!15:03
primeministerpalexpilotti: thx15:03
primeministerpalexpilotti: actually I wanted to have dan bode on the channel as well15:04
alexpilottiprimeministerp: pedro says that he's going to be a bit late due to corporate policies w IRC firewalling15:04
primeministerpalexpilotti: ok15:04
alexpilottiprimeministerp: do u know of any HTTP based client?15:04
primeministerpalexpilotti: actually i did15:05
primeministerpone sec15:05
*** bencherian has joined #openstack-meeting15:05
*** ociuhandu has joined #openstack-meeting15:06
primeministerpociuhandu: morning15:06
ociuhandumorning all15:06
primeministerpguess we'll wait a couple for pedro as well15:06
alexpilottiprimeministerp: great news live migration ported to Folsom :-)15:06
alexpilottiprimeministerp: finished now15:06
primeministerpalexpilotti: awesome!15:06
primeministerpalexpilotti: ok15:07
primeministerpwhile we have some folks on15:07
*** pnavarro has joined #openstack-meeting15:07
primeministerppnavarro: pedro!15:07
pnavarrohi all !15:07
alexpilottiprimeministerp: we have to verify / port volumeops only, for the rest all the features have been ported15:07
primeministerpwish jordan was here15:07
pnavarrosorry for the delay15:07
primeministerppinged him but no love15:07
primeministerpok let's finally begin15:07
primeministerp#topic Statuc of Folsom integration15:07
*** openstack changes topic to "Statuc of Folsom integration"15:07
primeministerp#topic Status of Folsom integration15:07
*** openstack changes topic to "Status of Folsom integration"15:07
primeministerpSo there's been a lot of activity from alexpilotti recently15:08
primeministerpalexpilotti: stop me if i'm incorrect15:08
alexpilottiand from pnavarro !15:08
primeministerpand from pnavarro !15:08
*** mattray has joined #openstack-meeting15:08
primeministerpso the current status of hyper-v is as follows15:09
primeministerpthe code has been refactored15:09
primeministerpthe moc driver is complete15:09
primeministerpthe following functions have been ported to folsom15:09
*** lloydde has quit IRC15:09
alexpilottiprimeministerp: snapshot15:10
primeministerpsnapshot as well15:10
alexpilottiactually all of them, we have to test only volumes15:10
primeministerpo execelent15:10
primeministerppnavarro: have you tested it at all?15:10
alexpilottipnavarro: do you think you could have time to test the volume stuff on Folsom?15:10
primeministerppnavarro: I will setup a folsom env today15:11
primeministerpit's on my list15:11
alexpilottitest as in "verify"15:11
primeministerpalexpilotti: I should be able to verify15:11
primeministerpalexpilotti: can you get me a pip freeze?15:11
pnavarrothat'd be nice, if I have a setup to tested it as fast as possible15:11
primeministerppnavarro: if you have devstack vm15:11
primeministerpyou can have a vhd for your iscsi volume15:11
primeministerpi have small one i use just to verify15:12
primeministerphowever that was essex15:12
alexpilottipnavarro: you can keep all your existing environment, you only need a devstack controller15:12
pnavarrook, that'd be easy then15:12
primeministerpso volume is the last key piece to verify15:12
*** cp16net is now known as cp16net|away15:12
primeministerpalexpilotti: do we have any other bugs that aren't currently addressed?15:12
alexpilottiprimeministerp: no, we are set15:13
primeministerpalexpilotti: and what's the status on the unit tests?15:13
alexpilottiprimeministerp: it's the next (and last step) that I can start now15:13
primeministerpalexpilotti: perfect15:13
alexpilottiprimeministerp: I was actually discussing w Pedro about some technical stuff15:14
primeministerpalexpilotti: perfect15:14
primeministerplet's discuss then15:14
alexpilottione funny thing. I don't see vmware tests in Folsom15:14
primeministerpmaybe they'll be pulled from the project as well15:14
alexpilotticoming to the techical things, unit tests require some fake classes to emulate dependencies15:14
alexpilottiwe call them stubs, fakes or mocks15:15
primeministerpvishy: any response to the lack of vmware tests in Folsom?15:15
alexpilottidepending on how complex tthey are15:15
primeministerpalexpilotti: ok15:15
alexpilottiso what I don't get is how they inject those fakes in teh xen tests for example15:16
primeministerpalexpilotti: so that will be the formal naming convention?15:16
primeministerphow are they currently doing it in kvm?15:16
alexpilottiprimeministerp: for what?15:16
primeministerpunit tests15:16
primeministerpinjecting fakes15:17
alexpilottiprimeministerp: false alarm. I just found the vmware tests15:17
primeministerpalexpilotti: perfect15:17
primeministerpvishy: nevermind they've been found15:17
alexpilottiwho knows in what directory I looked 10' ago!15:17
primeministerpalexpilotti: hehe15:18
primeministerpso you are set there now/15:18
*** pnavarro_ has joined #openstack-meeting15:18
*** littleidea has joined #openstack-meeting15:18
primeministerppnavarro_: pedro's back15:18
primeministerpalexpilotti: let's continue then15:18
*** pnavarro has quit IRC15:18
primeministerpalexpilotti: is there enough info  there to help you?15:18
pnavarro_my connection is not very stable15:18
primeministerppnavarro_: i see15:19
*** cp16net|away is now known as cp16net15:19
alexpilottiwo from what I see, they just set up the entire connection against the real hypervisor!15:19
*** markvoelker has quit IRC15:19
alexpilottior, I just miss something15:19
alexpilottithat's why I'm going to shoot a nosetest against them right now and see :-)15:20
primeministerpalexpilotti: hehe15:20
primeministerpalexpilotti: perfect15:20
alexpilottiin Essex I had the issue that tests were based on a custom runner.py15:20
alexpilottiwhich had a dependency on Unix15:20
pnavarro_you are shooting your tests from Windows them?15:21
*** rnirmal has joined #openstack-meeting15:21
alexpilottiI mean, if they are completely mocked, it's just plain python code15:21
pnavarro_that's true15:21
alexpilottiif not, I'll get a storm of errors :-)15:21
primeministerpshould we move on to the next topic?15:22
primeministerpalexpilotti: keep me on the threads15:22
*** pnavarro has joined #openstack-meeting15:23
*** markvoelker has joined #openstack-meeting15:23
primeministerpok then, moving on15:23
primeministerp#topic Status of the Hyper-V ci15:23
*** openstack changes topic to "Status of the Hyper-V ci"15:23
primeministerpso lots have happend in a week15:23
*** danwent has quit IRC15:24
primeministerpI have secured a dedicated network connection and firewall resources15:24
primeministerpthose are now active15:24
primeministerpzuul has been setup and configured however is currently not actively ruunning15:24
alexpilottiERROR: Failure: ImportError (No module named lxml)15:24
primeministerpalexpilotti: sounds like another dep issue15:25
alexpilottiyep, that's it15:25
primeministerpso continuing15:25
alexpilottithe implicit question was: do you guys remember where to get a binary lxml?15:26
primeministerpthe hyper-v jenkins keys have been supplied to mtaylor and I have succesfully tested the zuul connectivity15:26
*** pnavarro_ has quit IRC15:26
primeministerpalexpilotti: no15:26
primeministerpalexpilotti: what's it asking for specifically15:26
alexpilottipip install lxml15:27
primeministerpp and configured however is currently not actively ruunning15:27
alexpilottijust waiting for the result15:27
primeministerpi see the egg for 2.215:27
alexpilottiit tries to compile it and it fails15:27
primeministerpon what15:28
alexpilottiI remembered correctly that we need a precompiled Win32 copy15:28
pnavarroeven 2.3: http://pypi.python.org/pypi/lxml/2.3/15:28
alexpilottifound it15:29
*** markmcclain has quit IRC15:29
primeministerpon w/ ci discussion15:29
primeministerpI have made the decision to put the hyper-v chef on hold to focus on puppet for the ci infrastructure to keep in line with core project15:30
alexpilottiERROR: Failure: ImportError (No module named crypt)15:31
pnavarrothat makes sense15:31
primeministerpanyone have any issues with that15:31
primeministerpon the puppet note, i have discussed with dan bode of puppet labs15:32
primeministerpwe will hopefully engaging cern to assist in the effort15:32
primeministerpi was hoping jose would be on the meeting today, hopefully he sees the minutes15:32
*** shang_ has quit IRC15:34
primeministerpadditionally the current ci controller infrastructure will be moved to devstack with my goal of using the same ci setup as core for the hyper-v15:34
primeministerppnavarro: alexpilotti any objections?15:34
pnavarroprimeministerp: it's ok for me15:34
primeministerpok perfect15:35
alexpilottifrom primeministerp bootstrap: http://stackoverflow.com/questions/6158125/is-there-an-m2crypto-installer-for-windows-7-64-bit15:35
alexpilottiops: http://chandlerproject.org/pub/Projects/MeTooCrypto/M2Crypto-0.21.1.win32-py2.7.msi15:35
*** hggdh has quit IRC15:35
primeministerpalexpilotti: i'll need your pip freeze so i create a new bootstrap15:35
primeministerpalexpilotti: also I've created a openstack-puppet-hyper-v public repo15:35
primeministerpalexpilotti: i'm going to start putting things like that there15:36
primeministerpi believe15:36
primeministerp#link https://github.com/ppouliot/openstack-puppet-hyper-v.git15:36
primeministerpthat will be the starting point15:37
primeministerppnavarro: alexpilotti anything else to add15:37
primeministerpkeep me on the dialog between you to15:37
primeministerppnavarro: i'll email you as soon as i'm able to test volume15:37
primeministerpalexpilotti: keep plugging on the unit tests15:38
*** dolphm has quit IRC15:38
primeministerplast topic15:38
*** ecarlin has quit IRC15:38
primeministerp#topic folsom submission15:38
*** openstack changes topic to "folsom submission"15:38
primeministerpalexpilotti: what's a good estimate for the push of the code upstream?15:38
alexpilottiprimeministerp: pnavarro got disconnected15:38
*** pnavarro_ has joined #openstack-meeting15:38
primeministerpalexpilotti: ok15:38
alexpilottipnavarro: he asks: what about docs integration on Folsom15:38
primeministerppnavarro_: back w/ us15:39
primeministerpdo docs15:39
pnavarro_yes, primeministerp we should do doockbookize15:39
primeministerpwe need to do docks15:39
primeministerppnavarro_: ok15:39
primeministerppnavarro_: do you know how to do that or where to begin?15:39
*** hggdh has joined #openstack-meeting15:39
primeministerppnavarro_: i'm new to it15:39
pnavarro_there are the official integration docs from openstack15:40
primeministerppnavarro_: do you have link15:40
annegentleOxygen is an XML editor where the company supports work on open source projects, so we can get you a license.15:40
* primeministerp adds to his reading list15:40
annegentle#link http://wiki.openstack.org/Documentation/HowTo15:40
primeministerpannegentle: perfect!15:40
pnavarro_thanks annegentle !15:40
pnavarro_Oxygen is really cool, I've used it in the past15:40
annegentlewe never did delete the hyper v chapter, so it's still in the openstack-manuals GitHub repo. You can update that with the latest and then do an xi:include to put it in the Compute Admin manual15:40
annegentlepnavarro_: good, I find it really comfortable for authoring15:41
*** pnavarro has quit IRC15:41
primeministerpannegentle: on that note15:41
primeministerpannegentle: what about restoring the hyper-v column on the wiki15:41
alexpilottiouch: crypt is Unix only15:41
primeministerpannegentle: is it possible to get some help w/ that15:41
annegentleprimeministerp: on the first page? it's sort of too detailed for the first page15:41
*** troytoman-away is now known as troytoman15:41
annegentleprimeministerp: or do you mean the hypervisor page?15:42
primeministerpannegentle: the supported hypervisors matrix15:42
annegentleprimeministerp: got it. you should be able to go to a previous edit of it and pick up the changes?15:42
primeministerpstill learning, just don't want to break it15:42
annegentleprimeministerp: yeah try the GUI editor for the table15:43
annegentleprimeministerp: but yes it's touchy15:43
primeministerpannegentle: perfect, ok to ping you if I have issues?15:43
pnavarro_annegentle: who to address to have the oxygen license?15:44
*** heckj has joined #openstack-meeting15:45
primeministerppnavarro_: i figure docs will be a big part of our f4 push15:45
pnavarro_ok, after F3 then15:45
primeministerpannegentle: if you could get us that info re: the oxygen license, that would be great, feel free to email to directly to me and I can share w/ the team.  ppouliot@microsoft.com15:46
primeministerppnavarro_: we need to get what we have in first15:46
primeministerpalexpilotti: pnavarro_ ok on that note then, i'm going to end it15:46
primeministerpanything else to add before i do?15:46
primeministerpalexpilotti: pnavarro_ ?15:46
pnavarro_nothing to add...15:47
primeministerpok great work guys15:47
primeministerpi appreciate all the effort15:47
primeministerpon that note15:47
*** 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:47
openstackMeeting ended Tue Aug  7 15:47:31 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-07-15.00.html15:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-07-15.00.txt15:47
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-07-15.00.log.html15:47
*** shang has joined #openstack-meeting15:52
*** pnavarro_ has quit IRC15:52
*** kindaopsdevy has joined #openstack-meeting15:55
*** Mandell has joined #openstack-meeting15:56
*** patelna has joined #openstack-meeting15:57
*** shang has quit IRC15:59
*** rafaduran has quit IRC15:59
*** kindaopsdevy_ has joined #openstack-meeting16:00
*** milner_ has joined #openstack-meeting16:01
*** kindaopsdevy has quit IRC16:03
*** kindaopsdevy_ is now known as kindaopsdevy16:03
*** milner has quit IRC16:03
*** maoy has quit IRC16:07
*** mnewby has joined #openstack-meeting16:11
*** mnewby has joined #openstack-meeting16:12
*** s0mik has joined #openstack-meeting16:13
*** markmcclain has joined #openstack-meeting16:14
*** milner_ has quit IRC16:14
*** lloydde has joined #openstack-meeting16:16
alexpilottinew bug: https://bugs.launchpad.net/nova/+bug/103404316:16
uvirtbotLaunchpad bug 1034043 in nova "nova/virt/disk/api.py imports crypt, doesn't work on Windows " [Undecided,New]16:16
*** ecarlin has joined #openstack-meeting16:22
*** kindaopsdevy has quit IRC16:22
*** kindaopsdevy has joined #openstack-meeting16:22
*** heckj has quit IRC16:29
*** heckj has joined #openstack-meeting16:30
*** milner_ has joined #openstack-meeting16:31
*** ecarlin has quit IRC16:34
*** ecarlin has joined #openstack-meeting16:34
*** markmcclain has quit IRC16:36
*** bencherian has quit IRC16:38
*** gyee has joined #openstack-meeting16:42
*** markmcclain has joined #openstack-meeting16:43
*** dwcramer has quit IRC16:43
*** markmcclain has quit IRC16:44
*** markmcclain has joined #openstack-meeting16:45
*** markmcclain has quit IRC16:46
*** markmcclain has joined #openstack-meeting16:47
*** adjohn has joined #openstack-meeting16:52
*** bencherian has joined #openstack-meeting16:54
*** rafaduran has joined #openstack-meeting16:56
*** derekh has quit IRC16:56
*** maoy has joined #openstack-meeting16:59
*** Gordonz has quit IRC17:00
*** Gordonz has joined #openstack-meeting17:00
*** maoy has quit IRC17:00
*** garyk has quit IRC17:06
*** PotHix has joined #openstack-meeting17:08
*** johnpur has joined #openstack-meeting17:16
*** bencherian has left #openstack-meeting17:21
*** dendrobates is now known as dendro-afk17:24
*** darraghb has quit IRC17:28
*** cp16net is now known as cp16net|away17:29
*** anniec has joined #openstack-meeting17:31
*** ecarlin has quit IRC17:33
*** ociuhandu has quit IRC17:35
*** ecarlin has joined #openstack-meeting17:36
*** jakedahn_zz is now known as jakedahn17:37
*** dolphm has joined #openstack-meeting17:41
*** jdurgin has joined #openstack-meeting17:42
*** alrs has joined #openstack-meeting17:45
*** dwcramer has joined #openstack-meeting17:47
*** alrs_ has joined #openstack-meeting17:49
*** matwood has quit IRC17:54
*** matwood has joined #openstack-meeting17:55
*** dendro-afk is now known as dendrobates17:55
ayoung\m/ ^v^ \m/17:55
*** alexpilotti has quit IRC17:56
*** alexpilotti has joined #openstack-meeting17:57
*** alexpilotti has quit IRC17:58
*** maoy has joined #openstack-meeting17:59
*** sandywalsh has quit IRC17:59
ayoungheckj, gyee shall we dance?17:59
openstackMeeting started Tue Aug  7 18:00:05 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
heckjola all18:00
ayoung\m/ ^v^ \m/18:00
*** maoy has quit IRC18:00
ayoungGotta be a better way to do horns than that....18:00
heckjayoung: did you want to reset to last week's agenda and continue?18:01
ayoungYes please18:01
ayoungIf I can jumpright in to the PKI stuff, I'll truy top keep it moving18:01
heckj#topic PKI stuff18:02
*** openstack changes topic to "PKI stuff"18:02
heckjayoung: take it away18:02
ayoung"Reissue of tokens "18:02
ayoungTHe ides here is that tokens are not necessarily 0 cost to create18:02
ayoungso the question is does it make sense to return an old token if requested18:02
ayoungit used to bwe done, before the time out was bound to the token18:03
ayoungso, in order to implement, we would need a new concept:  reissue window18:03
ayoungsomething like this18:03
ayoungtokens last 24 hours18:03
ayoungif I ask for a new one,  and I have an active one that is less than, say, 1 hour old, reissue it18:03
heckjayoung: this makes me a little squirmy18:04
ayoungmy concern is that without this concept,  we will start generating DDOS levels of tokens on a busy system18:04
dolphmif reissue_window == 0, would new tokens always be created on POST?18:04
ayoungdolphm, yes18:04
dolphmand if reissue_window == 24 hours, existing tokens will always be returned, if any18:04
heckjI'm not disagreeing that it's costly to make a token, but I think we're generally better off creating new tokens as a standard18:04
heckjI'd prefer to not re-issue tokens18:05
ayoungdolphm, yes,18:05
*** tim_ has joined #openstack-meeting18:05
ayoungheckj, we can make it a configuration option, with NO_REISSUE the default policy18:05
heckjI was talking with some security professionals that reviewed the keystone codebase, and they called out the direct token usage as being somewhat fundamentally flawed18:05
*** marek_ has joined #openstack-meeting18:05
ayoungbut we build in the mechanism to alleviate the pressure if it turns out to be necessary18:05
heckjayoung: yeah - I've got that, but it seems like a poor idea in genera18:06
ayoungheckj, if the clients tended to cache the tokens, I would agree with you18:06
gyeewhat's the use case for token reissue? job automation?18:06
dolphmayoung: instead of "NO_REISSUE", just set the default reissue window to be 018:06
ayoungin the past we haven't seen the problem because we weren't too strict on the time outs.  so doing a request for a no-tenant token would not generate a new DB line18:07
*** lcheng has joined #openstack-meeting18:07
ayoungdolphm, yeah, I was just naming the policy,  but that is what I am saying18:07
ayoungheckj, also,  with putting the whole token text in the database, the DB is going to get larger quicker18:07
ayoungand that was what this concept grew out of:  right now, the PKI tokens are recorded en-toto18:08
ayoungone discussion was whether this was necessary.18:08
dolphmyeah -- was there another use case for storing the entire token in keystone, other than to re-issue them?18:09
ayoungthe only reason I could see is if you ever needed to re-read the token data.  So if there is no re-issue,  we can remove the token body from the db table18:09
ayoungdolphm, only for parity with the previous system.   If no reissue, I think we can safely remove it18:09
gyeeif you are going to reissue the old token, why not just store the hash?18:10
ayoungAnd, if no reissue, we *should* remove it.18:10
*** Mandell has quit IRC18:10
ayounggyee, agreed:  we can store just the hash18:10
gyeethe request will contain the old token data anyway right?18:10
dolphmi vote to only store a token hash + enable/disable state (for revocation), and skip re-issuing tokens altogether18:10
ayoungif we reissue the token,. we need to have the body identical18:10
*** Mandell has joined #openstack-meeting18:10
*** andrewbogott is now known as andrewbogott_afk18:10
ayoungheckj, is ^^ your opinion as well?18:11
heckjayoung: yeah, I'd prefer dolph's suggestion18:11
heckjjust want to keep enough to allow revocation18:11
ayoung#action ayoung to remove token body from the database table.  tokens will not be reissued.18:12
* heckj nods18:12
ayoungOK...next line item:  use of keyring:18:12
heckjsaw some notes on the list re: this, but don't know what "keyring" is...18:13
ayoungI think, if we can, we should  cache the tokens on the client side18:13
ayoungheckj, it is a python library that maintains a credentials cache\18:13
ayoungthey are going to use it in the unified cli to store the password18:13
ayoungI'd like to store any tokens received in there as well18:14
dolphmpurely a client-side issue, correct?18:14
*** devananda has joined #openstack-meeting18:14
ayoungIt will allow the sharing of tokens.  If we are not going to reissue, this is the best way to keep load off the keystone server18:14
heckjayoung: so what's the issue - seems perfectly reasonable for the unifiedCLI work (BTW: who's doing that work?)18:15
heckjayoung: define "sharing of tokens"?18:15
ayoungheckj, they are doing it for passwords.  I am proposing extending it to tokens18:15
dolphmheckj: dtroyer18:15
ayoungheckj, most CLI calls do a POST /tokens  before calling glance, nova, etc18:15
ayoungthis will obviate that call if the token is fresh enough18:16
ayoungsince each call into the CLI is a separate process, you need to store the token somewhere to reuse it.  Keysring is a safe way to do that.18:16
ayoungI think it is this: http://pypi.python.org/pypi/keyring/18:17
ayoungKind of like ssh agent18:18
*** jog0 has joined #openstack-meeting18:18
ayoungdoes this sound like a good approach?  I think it is18:18
ayoungIf so, I'll write up the blueprint18:18
gyeeswift team is implement auth plugin for their client right?18:18
gyeekeyring will be a plug-in then?18:18
ayounggyee, yes, and will not be a hard requirement, I think18:19
dolphmayoung: bp for keystoneclient?18:19
ayoungdolphm, probably for keystoneclient and common18:19
gyeeyeah, should be in common18:20
*** johnpur has quit IRC18:20
ayoungI'll let you guys hedge for now if you want time to think about it.  I just wanted to get it above the noise threshold18:20
heckjseems perfectly reasonable to me18:20
ayoung?action ayoung to write up blueprints for using keyring for client side token caching18:21
ayoungthat OK18:21
heckjdoes dtroyer have a launchpad or something that we can add that to, or should we keep it in keystone?18:21
*** johnpur has joined #openstack-meeting18:21
heckj(er, keystonelclient project)18:21
ayoungheckj, I can find out18:22
heckjI'm good with it either way - just think we should keep this close to unifiedCLI work if we can18:22
*** primeministerp has quit IRC18:22
uvirtbotLaunchpad bug 1030440 in python-openstackclient "keyring support for openstack client" [Undecided,New]18:22
ayoung#action ayoung to write up blueprints for using keyring for client side token caching as part of python-openstackclient18:23
marek_Are you assuming that all clients will have to store the tokens somewhere since heystone server only stores the hash? what is returned when the user asks for the token with the same credentials? Are you going to issue  a new one or regenerate the old one.18:23
ayoungmarek_, they get a new one, since it will have a new timeout value18:23
dolphmdoes the keyring api let us delete cached tokens once they expire?18:24
ayoungmarek_, a comparison other is Kerberos.18:24
ayoungSo in this case, the Kerberos credentials cache is the analogue of using keyring18:24
marek_How many active tokens can a user hold?18:24
ayoungdolphm, NO idea...but if it does not, we can delete any old tokens when we get a new one18:25
dolphmhttp://pypi.python.org/pypi/keyring/#api-interface is this what we're talking about?18:25
ayoungmarek_, potentially multiple...one per tenant would be the expected case18:25
ayoungdolphm, I *think* so18:25
dolphmayoung: pip-requires for the proposed page references 'keyring'18:25
dolphmproposed patch*18:26
ayoungdolphm, right...18:26
ayoungdolphm, so keysring is just a front to a handful of different stores18:26
ayoungGnomeKeyring, KDEWallet18:26
ayoungideally it would handle openssh and Mozilla NSS dbs...18:26
ayoungbut I digress18:26
*** anniec_ has joined #openstack-meeting18:27
*** anniec has quit IRC18:27
*** anniec_ is now known as anniec18:27
ayoungbut there is no dedicated process.  SO any work has to be done on the process that access the keyring18:27
ayoungI'd like top move on18:28
ayoungenable: token_format = PKI | uuid18:28
ayoungdecideing when to swith over18:29
dolphmin keystone.conf?18:29
ayoungdolphm, let me restate18:29
dolphmor is this a poll lol18:29
ayoungcriteria for switching from UUID to PKI as the default18:29
ayoungthat is what I meant to have in the agenda.  The config option is already decided18:30
ayoungso, I think a *must have* feature is revocation18:30
ayoungare there are any other criteria we need to meet before we flip the default to PKI tokens?18:30
dolphmtiming with release milestones?18:31
ayoungI think it is clear that we will leave the ability to do UUID tokens in as part of keystone18:31
dolphm> grizzly day 0?18:31
ayoungdolphm, I'd hoped to have it in Folsom18:31
ayoungis that even possible now?18:31
dolphmas a default?18:31
dolphmi'd say we need to ship uuid as default for folsom, but i'd like to switch asap after18:32
ayoungOK.  I think I am OK with that18:32
ayounglet me rephrase the question, then18:32
ayoungassumign that we need a fully functional PKI token as an alternative auth mechnism in Folsom, what else does it need?18:33
dolphmrevocation -- what was the conclusion on the mailing list? GET /tokens/revoked, and let clients cache the result?18:34
ayoungdolphm, basciially, yes18:34
dolphmdoes support for that (middleware included) need to land in folsom?18:34
gyeeif you are going to implement revocation, what benefits does PKI token have? :)18:34
ayoungdolphm, yes, I think it does18:34
ayounggyee, it will still be a lot less chatty than UUID tokens18:35
*** Shrews has joined #openstack-meeting18:35
ayoungyou are talking one RPC request per timeout period as opposed to multiple RPCS per request18:35
dolphmgyee: revoked token list could be checked & cached every minute, for example, instead of GET /tokens/{token_id} per token, several times a second18:35
gyeenot sure about that18:35
ayoungplus..I think that revocation should be optional.  I suspect that most people would want it.  But with revocation, you could have tokens for a long period of time (weeks) and have a short revocation cache window (hours) if you wanted18:36
heckjgyee: what you expectging otherwise there18:36
*** sandywalsh has joined #openstack-meeting18:36
gyeeif they want revocation, use UUID tokens18:37
heckjayoung: i like the optional revocation setup18:37
gyeethere's a reason why OCSP failed :)18:37
ayoungheckj, I'll make sure that is noted in the blueprint18:37
gyeecomplexity versus benefits18:37
dolphmi imagine GET /tokens/revoked will be a very small request with (generally) an empty response... way better than a giant PKI GET request, with a giant pki response18:37
rafaduranand what about an RPC call to do revokation explicit?18:39
ayoungdolphm, yes, that is what I foresee as well:  a signed document if there is anything, an empty document otherwise.  Document will be nothing more that [HASH1,HASH2]18:39
ayoungrafaduran, you mean to revoke a token?  There are ways of doing that now.18:39
ayoungrafaduran, at a minimum, I know that all tokens for a user account get revoked when the account is deactivated18:40
ayounglet me see if we havea deliberate revoke_token API...I can add that, too if needs be18:40
ayoungBTW< tokens also get revoked on password change18:40
ayoungOK.  15 minutes left.  I can surrender the floor18:41
ayoung#action  UUID tokens will be default for Folsom18:41
heckjayoung: revokation of uuid tokens has been invoking a delete /token/UUID18:41
ayoung#action PKI tokens will ship in Folsom with revocation.18:41
dolphmayoung: DELETE /tokens/{token_id} is part of the api18:41
*** cp16net|away is now known as cp16net18:42
ayoungI figured as much...just realized I hadn't looked directly.  I reviewed the changes for the password/account revocation cases, so I knew we already had some ways...18:42
*** cp16net is now known as cp16net|away18:42
*** cp16net|away is now known as cp16net18:42
ayoungheckj, floor is yours18:43
heckjuh, hi?18:44
*** jakedahn is now known as jakedahn_zz18:44
heckjas usual, highly distracted18:44
dolphmHI, HECKJ!18:44
* heckj needs more coffee18:44
heckjOkay - other topics18:44
*** kindaopsdevy has quit IRC18:45
gyeewhat's the feature cut off date for folsom?18:45
heckj#topic API changes18:45
*** openstack changes topic to "API changes"18:45
heckjgyee: Aug 16th or so18:45
ayoungheckj, the reason I put "API Changes " on the agenda was to trigger a review of the changes done thus far18:45
*** maoy has joined #openstack-meeting18:45
heckjOkay - how about summit topics18:45
heckj#topic blah blah open discussion18:46
*** openstack changes topic to "blah blah open discussion"18:46
ayoungheckj, one sec18:46
ayoungthe question of API stability was a big topic on the main list18:46
ayoungwe've made some changes to the API, specifically to the return codes18:46
dolphmv3 stability?18:46
heckjayoung: yeah18:46
ayoungno v218:46
dolphmwhat return codes? i must have missed this18:46
*** kindaopsdevy has joined #openstack-meeting18:46
ayoungso the question is, if someone coded against v2 for essex, is it going to break against v2 in folsom?18:47
*** sandywalsh_ has joined #openstack-meeting18:47
heckjSomewhere in there (I'm missing the reviews), we approved some changes that were subtle tweaks to the V2 api return codes18:47
ayoungdolphm, 403 vs 402 type stuff is what I've noticed18:47
*** sandywalsh has quit IRC18:47
ayoungheckj, right, so the question is:  is this OK, is it a big deal,  who are we going to annoy...?18:47
heckjIn general, I'm very much in favor of the "keep the API static" - there's almost no means of versioning like a 2.1 in a meaningful way18:47
ayoungI guess that is more than one question18:47
dolphmi thought 403 vs 402 was all straightened out -- i think we changed it and reverted it18:47
heckjwe did - but it's worth bringing up18:48
ayoungdolphm, if that is the case, great18:48
*** markmcclain1 has joined #openstack-meeting18:48
*** markmcclain1 has quit IRC18:49
gyee402 or 420? :)18:49
gyeejust kidding18:49
*** markmcclain1 has joined #openstack-meeting18:49
ayounggyee, we aren't writing a twitter client here...18:49
heckjUnless anyone disagrees, I'd like to assert that we'll generally abide by the API stability policy that the crew on the ML defined out18:49
*** garyk has joined #openstack-meeting18:49
ayoungheckj, I think that is a given18:50
ayoungmy question was, have we done so thus far?18:50
ayoungItsounds like we have at least made a best effort to do so18:50
dolphmheckj: link?18:50
*** markmcclain has quit IRC18:50
heckjayoung: we've been pretty darned good18:51
heckjdolphm: link in a sec...18:51
dolphmfor meeting officiallity18:51
*** kindaopsdevy has quit IRC18:51
heckj#link http://wiki.openstack.org/APIChangeGuidelines18:51
heckjIt's a pretty good set of general guidelines (FWIW)18:51
ayoungOK to table the summit topics to next week?18:52
heckjyep - we're running out of time. I'll update the wiki agenda with the notes, and I think we're good.18:52
ayoungOh..one other thing,  gyee and I talked, and it looks like Domains will have to wait until Grizzly18:52
ayoungno big surprise there18:52
heckjdarnit. I understand, but darnit18:52
*** markmcclain1 has quit IRC18:52
ayoungbut It does mean we can do all the work in /v3/18:53
*** markmcclain has joined #openstack-meeting18:53
heckjI haven't had the time to knock in much code this past release.. working to get that better18:53
dolphmspeaking of v3... https://review.openstack.org/#/c/974418:53
dolphmi added /v3 to keystone.conf, and laid down some new routers and whatnot18:54
heckjdolphm: nice18:54
heckjI'll do some lookin'18:55
dolphmalso some v3 testing infrastructure which runs against wsgi directly, since we don't have keystoneclient support yet (chicken and egg)18:55
gyeedolphm, is the RBAC stuff ready for action?18:55
heckjdolphm: I'd like to get the keystoneclient stuff in first (not that it's happened)18:55
heckjdolphm: for the primary reason of setting up the tests and then filling in the implementation18:56
dolphmgyee: you review it and tell me :)18:56
dolphmheckj: is there a keystoneclient bug for v3 work?18:57
dolphmor bp18:57
heckjdolphm: yep18:57
ayoungwe still working with https://docs.google.com/document/d/1VP-bTBbwsn6q-rDzuS9CEKb2ubE1VjbWRFd4BkkjoOY/edit?pli=118:58
dolphmayoung: i am, so i hope so :)18:58
ayoungCan we move this over to wiki soon?18:59
ayoungI'll volunteer18:59
*** adam_g has joined #openstack-meeting18:59
dolphmayoung: the draft itself?18:59
heckjayoung: OK by me, but recall we're keeping it "open" to learn from implementation18:59
heckjneed to wrap this up so mtaylor doesn't smack me around19:00
*** 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"19:00
openstackMeeting ended Tue Aug  7 19:00:06 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-07-18.00.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-07-18.00.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-07-18.00.log.html19:00
* mtaylor smaks heckj around on principle19:00
* dolphm ¡runs!19:00
* ayoung sneaks in an ties mtaylors shoolaces together, then sneaks off19:01
* mtaylor trips and skins his knee, then cries19:01
mtaylorand with that19:01
openstackMeeting started Tue Aug  7 19:01:24 2012 UTC.  The chair is mtaylor. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
mtaylorCI anybody?19:01
mtaylorjeblair: you wanna talk about anything?19:01
*** reed has quit IRC19:02
jeblairmtaylor: i'd like to talk about current problems and what we're going to do about them.19:02
mtaylor#topic current problems19:02
*** openstack changes topic to "current problems"19:02
mtaylorjeblair: you have the floor19:02
jeblairmtaylor: have you had a chance to look into why a git remote update taks 6 minutes?19:02
*** reed has joined #openstack-meeting19:03
mtaylorjeblair: no, I have not. I keep getting pulled on to phone calls19:03
mtaylorjeblair: is it only between rax hosts? or does that need investigation too?19:03
jeblairso i'm very worried about that.19:04
*** novas0x2a|laptop has joined #openstack-meeting19:04
jeblairi have only performed minimal investigation.  it seems to be most pronounced on an oneiric rs host talking to review.openstack.org.  it seems less of a problem from a precise host.  and it doesn't seem to be much of a problem from my home connection.19:04
jeblairthat's all the data i hive.19:04
jeblairreview.o.o is averaging 2.24 Mb outbound traffic.  I forget what the link is, but i don't think it's hitting the limit.19:06
mtayloroneiric is running an older version of git than precise - but not by much, so it _should_ support efficent http protocol19:06
jeblairi'd really love it if someone could look into that, because it's eating up 6 minutes of run time for every unit test, and more than _20_ minutes on devstack runs.19:07
jeblairi think it's a critical issue.19:07
mtaylor1.7.5.4 vs.
mtayloryeah. I will work on that this afternoon. LinuxJedi any chance you have any brain-space to help?19:07
jeblairthe ideas i've brainstormed are slow links between certain sets of hosts within rackspace19:07
LinuxJediprobably, yes19:08
jeblairor perhaps even oversubscribed io19:08
* LinuxJedi wonders if we can simulate the traffic19:08
jeblairwhich traffic?19:09
*** ecarlin_ has joined #openstack-meeting19:09
LinuxJedigit http19:09
*** ecarlin has quit IRC19:10
*** ecarlin_ is now known as ecarlin19:10
jeblair"git remote update" ?19:10
*** johnpostlethwait has joined #openstack-meeting19:10
mtaylorjeblair: btw - do we need to do remote update?19:10
LinuxJedisure, but I meant with something we can get some real data from19:10
mtaylorjeblair: since we're later doing fetch on specific refspec?19:10
*** marek_ has quit IRC19:10
jeblairyes, so that we can "git checkout master"19:10
jeblairLinuxJedi: i'm trying to follow, but i'm puzzled.  what's not real about that?19:11
jeblairLinuxJedi: i'm trying to understand what thing you want to simulate?19:11
LinuxJedijeblair: nevermind we can just use packet analysers to get everything I was thinking of19:12
jeblairnext critical issue:19:13
jeblairi filed this bug: https://bugs.launchpad.net/openstack-ci/+bug/103403219:13
uvirtbotLaunchpad bug 1034032 in openstack-ci "make static html versions of jenkins reports for archiving" [Critical,Triaged]19:13
jeblairwe really need to stop using the junit post-build option in jenkins19:13
jeblairthat's step on in that bug -- to generate junit output some other way19:14
jeblairthen we can stick the job information, including the unit test report, on a static webserver19:14
jeblairi think this is the next biggest scalability hurdle for us -- it's significantly slowing down zuul and jenkins19:15
jeblairand it's the biggest cause of deadlocks that we have to manually clear out19:15
clarkbcan we disable that plugin while we work on a fix?19:16
jeblairso i'd really like to see some progress on that.19:16
jeblairclarkb: unfortunately, we did a lot of work to make the unit test output usable via the junit module...19:16
mtaylorclarkb: doesn't nose have an html output mechanism?19:16
*** nati_uen_ has joined #openstack-meeting19:16
jeblairmtaylor: no it does not.19:16
jeblairmtaylor: if we disabled the junit build step, do you believe the results would be usable to developers, as things currently stand?19:17
jeblair(my understanding is that you did some work to get all of the log output, etc, in the xunit report)19:17
mtaylorjeblair: I did - but that was really just getting the results to be picked up by nose19:18
mtaylorjeblair: if we turned off xml output, we'd get standard nose error reports to stdout at the end of the run19:18
clarkbit isn't the output that is failing though right? it is the junit plugin waiting for the output?19:19
jeblairmtaylor: so you think that output would be useful, without the organization provided by junit?19:20
mtaylorjeblair: it wouldn't be as pretty, but all of the information should be there19:20
mtayloroh, wait19:20
*** tim_ has quit IRC19:21
mtaylorso - they'd get this:19:21
*** ryanpetrello has joined #openstack-meeting19:21
mtaylorso you can see the traceback at the end19:21
mtayloras well as captured logging19:22
mtaylorit's ugly, but it's here19:22
jeblairnot yet i can't, i'm waiting for jenkins.19:22
jeblairmtaylor: why isn't that job processed by junit?19:23
clarkbjeblair: it is but the option to also retain stdout results is checked19:23
mtaylorwhat clarkb said19:23
jeblairwhy does that build not have a test report?19:23
mtayloroh, you're right19:24
mtaylorwe do this: export NOSE_WITH_XUNIT=119:24
jeblairthe option to "also retain stdout" is an option in jenkins junit processing that causes jenkins to keep the output recorded in the xml file19:24
jeblairyes, that job _wrote_ an xml file19:25
jeblairbut jenkins did not read it.19:25
jeblairclarkb: the "retain stdout" option doesn't have any effect on what is printed to stdout by nose, or what's recorded in the xml file.19:25
mtaylorgood question19:25
jeblairmtaylor: so what i'm getting at is, is there logging that's going into the xml file that we're not seeing?19:26
mtaylorjeblair: there should be no _additional_ logging into xml19:26
jeblairmtaylor: i thought there was a whole "run_tests.log" thing and you got most of the output to go via the nose log capture plugin.19:26
jeblairi don't see any logs from that failed test19:26
mtaylorthat is the output at the end19:27
jeblairoh wait19:27
jeblairthere is _one_ log line19:27
mtayloryeah. there just wasn't much log output during that test run19:27
jeblairokay, sorry i missed that.19:27
jeblairi just saw the exception.  was expecting more logs.19:27
*** dwcramer has quit IRC19:28
jeblairokay, so i guess we can disable junit in jenkins as clarkb suggested.  do we have agreement on that?19:28
mtayloryes. works for me19:28
clarkbworks for me too19:28
mtaylorand then we can work on getting nose output into html pages that can be copied to a static web server19:29
mtayloronce we do that, I assume zuul will be able to report back the right link for people to look at?19:29
jeblairokay.  i will submit a change to disable junit19:29
jeblairyep. that's all described in the bug19:29
jeblair(the rest of the bug still stands -- this is just the first step)19:29
jeblair#action jeblair disable junit processing in jenkins jobs19:30
jeblair(is that the right action syntax?)19:30
jeblairnext critical item: https://bugs.launchpad.net/openstack-ci/+bug/101062119:31
uvirtbotLaunchpad bug 1010621 in openstack-ci "important servers should have backups" [Critical,In progress]19:31
jeblairmtaylor: have you heard back about the hpcloud volume service?19:31
*** ecarlin has quit IRC19:31
clarkbjeblair: yes I think that is correct19:32
mtaylorjeblair: no19:32
mtaylorjeblair: pinging again19:32
jeblairmtaylor: are they being unresponsive?  cause I'd really like to get this going, but i don't think we have an effective backup until we _at least_ have one in another account from the one where all our important servers are...19:33
*** AlanClark has joined #openstack-meeting19:34
jeblairi mean, should we come up with a different backup strategy?19:34
*** ecarlin has joined #openstack-meeting19:35
*** dwcramer has joined #openstack-meeting19:35
mtaylorjeblair: they report it as enabled on tenant id 1581384766078319:36
jeblairmtaylor: no idea what tenant that is.19:36
mtaylorI know. super helpful, right?19:36
*** alexpilotti has joined #openstack-meeting19:37
jeblairokay, that's supposed to be the stackforge tenant.  i'll try again.19:37
jeblair#action jeblair to see if volume service works in hpcloud for backups19:38
jeblairso those are all the critical issues i know of that we can do something about at the moment...19:38
jeblairi'd really like to see work going into addressing those, and maybe dealing with some of the bug backlog.19:39
*** ecarlin has quit IRC19:39
* mtaylor agrees19:39
mtaylorI'll work with LinuxJedi on trying to figure out the git slowdown19:40
jeblairi'm filing a bug about that one right now19:40
mtaylorclarkb: can you take figuring out how to get a nice html report from nose?19:40
mtaylorjeblair: artifact copy itself is a blocking operation, yeah?19:40
mtaylorjeblair: do we need to solve that for html report transfer?19:40
clarkbmtaylor: we could just add another 'execute shell' at the end of the builds if we need to19:41
clarkbthere is the option to always run a piece of code even if a test fails I think19:41
jeblairjust as an scp operation, without listing them as artifacts, like the docs jobs.19:41
clarkbthat should work19:42
jeblairi think that's worth investigating first -- i don't think it has the jenkins locking problems that artifacts have19:42
jeblairand it's cleaner than running a shell19:42
jeblairbut another challenge is how to get the console output..19:42
clarkband we already have jenkins_job builders for it19:42
clarkbjeblair: more tee?19:42
mtaylorlet's do one thing at a time - let's get test output fixed19:43
jeblairclarkb: that's an idea.  output with timestamps would be even more awesome though.  :)19:43
mtaylorthen we can figure out console output19:43
uvirtbotLaunchpad bug 1034130 in openstack-ci "find out why git operations from oneiric hosts are slow" [Critical,Triaged]19:43
*** heckj has quit IRC19:44
jeblair#action clarkb get a nice html report from nose19:44
jeblair#mtaylor,LinuxJedi find out why git operations from oneiric hosts are slow19:44
clarkbyou forgot the #action19:45
jeblair#action mtaylor,LinuxJedi find out why git operations from oneiric hosts are slow19:45
LinuxJedimtaylor is an action :)19:45
jeblairi think that covers critical operational stuff.19:45
* clarkb jumps in really quick so that he doesn't forget. if people could take a look at https://review.openstack.org/#/c/10784/ that would be awesome19:46
clarkbthat is a draft to deal with one of the things assigned to me last week19:46
*** tongli has quit IRC19:47
*** andrewbogott_afk is now known as andrewbogott19:47
*** ecarlin has joined #openstack-meeting19:47
mtaylorclarkb: I shall look at that19:49
mtaylorclarkb: perhaps un-draft it so I don't forget?19:49
mtaylor#topic open floor19:50
*** openstack changes topic to "open floor"19:50
mtayloranybody got anything else?19:50
clarkbgerritbot is ready for its first release as soon as zuul can handle it19:50
*** anotherjesse_zz is now known as anotherjesse19:50
jeblairgo for it19:50
clarkbI don't think I have the proper permissions19:51
clarkbI can't even +2 gerritbot19:51
devanandadevstack merged my openvz support patch, so it would be great if devstack-gate did the same soon19:51
jeblairclarkb: apparently you need to join openstack-ci-core19:51
clarkbjeblair: ok19:52
*** rkukura has quit IRC19:52
jeblair(and we probably need to give that group perms to tag)19:52
mtaylorclarkb: http://pypi.python.org/pypi/HTMLTestRunner19:52
mtaylordevananda: ++19:52
jeblairmtaylor: why don't you review it?  i gave it a +2.  ;)19:53
clarkbmtaylor: nice. BSD too19:53
mtaylorjeblair: maybe I will19:53
jeblairlovely.  i mean, other than the colors.  but i think that's exactly what we want.19:53
mtaylorI have no idea if that's suitable, but it might be a start at leats19:54
jeblairthat at least is what i was imagining the end product looked like.19:54
jeblairs/looked/should look/19:54
*** sandywalsh_ has quit IRC19:55
*** thingee has joined #openstack-meeting19:55
*** jk0 has joined #openstack-meeting19:56
mtaylorokie. that's all I've got for this week19:57
mtaylorthanks all19:57
*** 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"19:57
openstackMeeting ended Tue Aug  7 19:57:10 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-07-19.01.html19:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-07-19.01.txt19:57
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-07-19.01.log.html19:57
*** dendrobates is now known as dendro-afk19:59
*** danwent has joined #openstack-meeting20:00
ttxThat's 6, including danwent. Need at least 2 more20:01
anotherjessevishy should be here - he is across the table from me20:01
*** ecarlin has quit IRC20:02
*** markmc has joined #openstack-meeting20:02
ttxdevcamca-, notmyname ?20:03
ttxpvo ?20:03
ttxyay, 820:04
openstackMeeting started Tue Aug  7 20:04:21 2012 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:04
*** ewanmellor has joined #openstack-meeting20:04
ttxOnly one thing, should be quick20:04
ttxBasically, should we bend our rules and consider openstack-common has a full-right PTL20:05
ttxThe only difference with a generic team lead is the TC reserved seat20:05
* jaypipes ready to vote.20:05
ttxand a few other goodies, like a track at the design summit :)20:05
danwentttx: what are other library projects that we'd have to make a similar decision for?20:05
*** devcamca- is now known as devcamcar20:06
vishysdague: here was old review: https://review.openstack.org/#/c/10770/20:06
ttxdanwent: the others are all client libs20:06
*** ecarlin has joined #openstack-meeting20:06
danwentttx: k, thanks.20:06
*** kindaopsdevy has joined #openstack-meeting20:06
ttxdanwent: so those are obviously the case where we'd link them to the existing ptl20:06
*** kindaopsdevy has quit IRC20:06
*** devcamcar is now known as devcamca-20:06
*** heckj has joined #openstack-meeting20:06
ttxbut for future ones, we would decide when the library project is first accepted20:06
*** kindaopsdevy has joined #openstack-meeting20:06
ttxeveryone ready to vote ?20:06
*** kindaopsdevy_ has joined #openstack-meeting20:06
*** devcamca- is now known as devcamcar20:07
ttx#startvote get openstack-common a proper PTL? Yes, No, Abstain20:07
openstackBegin voting on: get openstack-common a proper PTL? Valid vote options are Yes, No, Abstain.20:07
openstackVote using '#vote OPTION'. Only your last vote counts.20:07
anotherjesse#vote yes20:07
ttx(see the link for the precise meaning of each option)20:07
vishy#vote yes20:07
danwent#vote yes20:07
jaypipes#vote yes20:07
heckj#vote yes20:07
jk0#vote yes20:07
johnpur#vote yes20:07
pvo#vote yes20:07
ttx#vote yes20:07
devcamcar#vote yes20:08
*** joshuamckenty has joined #openstack-meeting20:08
ttx30 more seconds20:08
*** Shrews has left #openstack-meeting20:08
anotherjesseuntil meeting over?20:08
ttxuntil vote over20:09
heckjanotherjesse: ++20:09
ttx(and meeting) :)20:09
openstackVoted on "get openstack-common a proper PTL?" Results are20:09
openstackYes (10): anotherjesse, johnpur, vishy, heckj, jaypipes, jk0, ttx, danwent, devcamcar, pvo20:09
markmcwow, that was easy - thanks all20:09
ttxSo we'll vote on openstack-common PTL at the end of the month20:09
ttxmarkmc is interim lead20:09
johnpursounds good20:10
anotherjessetoo late to change my vote then … (joking)20:10
devcamcarcongrats markmc ;)20:10
anotherjessegreat work markmc20:10
markmcthanks guys20:10
* markmc better get the finger out and do a release :)20:10
danwentoh wait, nobody told me markmc was going to be running it...20:10
danwentj/k :)20:10
ttxok, meeting oover, unless someone else has something ?20:10
anotherjessegoogling "better get the finger out"20:10
devcamcarfastest meeting ev-ar20:10
devcamcaranotherjesse: that won't end wel20:11
anotherjessebetter than googling my name with safe search turned off...20:11
anotherjessebtw, don't do that if you are at work...20:11
*** alrs_ has quit IRC20:11
markmcdevcamcar, "A way to tell a slacker to hurry up." :)20:11
devcamcaro rly?20:11
devcamcarmarkmc: thanks :)20:11
ttxNow that was easy and fast.20: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"20:11
openstackMeeting ended Tue Aug  7 20:11:46 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:11
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-07-20.04.html20:11
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-07-20.04.txt20:11
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-07-20.04.log.html20:11
ttxrelease/status meeting in 48min20:12
ttxthanks everyone!20:12
*** alrs has quit IRC20:12
*** jk0 has left #openstack-meeting20:14
*** alrs has joined #openstack-meeting20:14
*** reed has quit IRC20:14
*** anotherjesse is now known as anotherjesse_zz20:14
*** ecarlin has quit IRC20:16
*** ecarlin has joined #openstack-meeting20:16
*** ecarlin_ has joined #openstack-meeting20:17
*** ecarlin__ has joined #openstack-meeting20:18
*** alrs_ has joined #openstack-meeting20:20
*** ecarlin has quit IRC20:20
*** ecarlin__ is now known as ecarlin20:20
*** ecarlin_ has quit IRC20:22
*** ewanmellor has quit IRC20:24
notmyname /here20:32
johnpurhey John!20:33
johnpurwe had a 12 minute meeting today20:33
notmynameI didn't see an #endmeeting20:33
heckjwas at 1:11pm20:37
heckjnotmyname: logs at http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-07-20.04.html20:38
notmynameI'm been having a lot of lag on freenode the last few days20:38
notmynameheckj: thanks20:38
*** dwcramer has quit IRC20:42
*** ryanpetrello has left #openstack-meeting20:42
*** jrd-redhat has quit IRC20:45
*** jakedahn_zz is now known as jakedahn20:46
*** jaypipes has quit IRC20:46
*** dwcramer has joined #openstack-meeting20:55
*** markmc has quit IRC20:55
*** gabrielhurley has joined #openstack-meeting20:57
*** ecarlin has quit IRC20:57
*** markvoelker has quit IRC20:57
gabrielhurleyttx: unless devcamcar decides to tell me to shut up I'll be speaking for horizon again today21:00
ttxgabrielhurley: ack21:00
ttxmarkmc, heckj, notmyname, jgriffith, vishy, danwent: around ?21:01
ttxI know bcwaldon will be in in 12 min21:01
*** markwash has joined #openstack-meeting21:01
*** lzyeval has joined #openstack-meeting21:02
ttxhmm we have enough to start, I guess21:03
openstackMeeting started Tue Aug  7 21:03:16 2012 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:03
markwashbcwaldon is on his way21:03
ttxAgenda @ http://wiki.openstack.org/Meetings/ProjectMeeting21:03
ttx#info One week left to propose, review and merge the last Folsom features!21:03
ttxdo we have markmc for a 2012.1.2 update ?21:03
*** ecarlin has joined #openstack-meeting21:04
ttxotherwise we'll push that at the end21:04
*** maoy has quit IRC21:04
heckjhe's not online at the moment...21:04
ttx#topic Keystone status21:04
*** openstack changes topic to "Keystone status"21:04
ttxheckj: then you're in21:04
*** markmc has joined #openstack-meeting21:04
*** joshuamckenty has quit IRC21:04
* heckj waves21:04
ttxmarkmc: keystone in, you're next21:04
ttx#link https://launchpad.net/keystone/+milestone/folsom-321:04
ttxHow is https://blueprints.launchpad.net/keystone/+spec/pki going ?21:05
heckjquite well21:05
markmcttx, sorry, had network issues21:05
heckjgood feedback from the community on revocation needs around the initial implement, getting nailed down in blueprint right now21:05
*** ecarlin has quit IRC21:05
ttxok good21:05
heckjwe're not holding PKI back for it, but accelerating getting revocation ready to roll21:05
ttxAbout document-deployment-suggestions-policy, it's doc-only, right ? So we can postpone it to RC1 if not completed in the week ?21:05
heckjuncertain if we'll make the feature freeze deadline, but giving it a shot21:06
heckjttx: it's doc only21:06
ttxQuick look at untargeted blueprints on the series plan at:21:06
*** ecarlin has joined #openstack-meeting21:06
ttx#link https://blueprints.launchpad.net/keystone/folsom21:06
ttxheckj: agree that prompt-for-password is actually a python-keystoneclient blueprint ?21:06
heckjttx: yes21:06
ttxwil redirect21:06
ttxheckj: about https://blueprints.launchpad.net/keystone/+spec/iana-register-port ... I suspect it's still blocked at IANA ?21:06
*** bcwaldon has joined #openstack-meeting21:07
heckjyes, they haven't responded. Not likely to happen at this point, so we'll be staying where we are :-/21:07
ttxShould we defer to grizzly ? target to F3 and pray ?21:07
heckjgrizzly is what I'm thinking21:07
ttxFinal question: what's the status of APIv3 one week away from featurefreeze ?21:08
heckjsome initial stabs at implementation up for review (thank you dolph!), not as much as we'd hoped.21:08
*** joshuamckenty has joined #openstack-meeting21:08
ttxheckj: is it worth pushing anything in, then ?21:08
ttxheckj: the grizzly branch should be open in a few weeks, once we nail RC1...21:09
heckjI don't believe so - everyone's strapped for time, but not a lot of progress on much other than PKI right now21:09
ttxheckj: agreed, looks like a Grizzly thing now21:09
ttxheckj: anything else ?21:10
heckjnot from me21:10
ttxQuestions about Keystone ?21:10
ttx#topic 2012.1.2 stable release21:10
*** openstack changes topic to "2012.1.2 stable release"21:10
ttxmarkmc: the plan is still to have Keystone/Nova 2012.1.2 on Thursday ?21:10
markmcso, the nova security fix we were waiting for has landed21:10
markmcand we've had ~10 more nova fixes and a couple of keystone fixes21:11
ttxso we have candidates up for testing, or are we waiting for anything more ?21:11
markmcthere's one nova fix that I'm worried might be a regression, looking at that21:11
markmcthe big change is that we've had ~10 fixes backported by bcwaldon for glance21:11
bcwaldonaw yeah21:11
markmcmost haven't landed yet21:11
markmcit'd be nice to do 2012.1.2 with at least some of them21:12
*** Ravikumar_hp has joined #openstack-meeting21:12
markmcbut thinking we should get the important ones landed today21:12
bcwaldonmarkmc: we can make those land this afternoon21:12
*** markmcclain has quit IRC21:12
markmcand send out a call for testing for nova, glance and keystone21:12
markmcand then release friday21:12
markmcgiving another day for testing glance21:12
markmcpushing out another week would conflict with folsom-321:12
ttxmarkmc: ok, so we should see clearer tomorrow, and call for testing candidates then21:12
markmcttx, yep, hoping to send out the call for testing tonight21:13
Ravikumar_hpwhat level of testing ? is it unit tests by develoepr?21:13
ttx#info 2012.1.2 may be pushed back to Friday to include Glance21:13
ttxRavikumar_hp: it's mostly a question of looking at proposed deliveries for things that would not get caught by our rigorous testing21:13
ttxlike fucked up tarballs.21:14
ttxmarkmc: anything else ?21:14
mtaylorttx: I promise, no fucked up tarballs this time21:14
patelnayayaya ...21:14
dolphmayoung: i'm honestly not sure how the client should call :5000/v2.0/tenants without initializing it as Client(token='asdf', endpoint='http://keystone:5000/v2.0')21:15
markmcttx, nope21:15
ttx#topic Swift status21:15
*** openstack changes topic to "Swift status"21:15
*** nati_uen_ has quit IRC21:15
ttxnotmyname: hey21:15
ttxYou just released 1.6.0, so I don't have so many questions for you :)21:15
ttxnotmyname: should I create a tentative 1.6.1 milestone to target new things against ?21:16
ttx(like for 1.5.1 we can always rename it if you change your mind wrt numbering)21:16
notmynameyes. 1.6.1 for now21:16
ttx#action ttx to create 1.6.1 milestone for Swift if nobody beats him to it21:16
ttxnotmyname: anything you wanted to mention ?21:16
notmynameya, I have one question for you21:16
notmynameI think we have time for about one more release for folsom21:17
notmynamewhen is that scheduled?21:17
ttxnotmyname: definitely. Final is scheduled for Sep 2221:17
*** nati_uen_ has joined #openstack-meeting21:17
ttxI expect to have RC1 for the other projects around Sep 621:17
notmynameok, thanks. that's what I was wonderign21:18
ttxSo I'd say you can plan one between Sep 1-1321:18
ttxErr, release is Sep 2721:18
ttxSep 22 was Diablo. Good ol days21:19
ttxQuestions on Swift ?21:19
ttx#topic Glance status21:20
*** openstack changes topic to "Glance status"21:20
ttxbcwaldon: o/21:20
ttx#link https://launchpad.net/glance/+milestone/folsom-321:20
bcwaldonttx: hey hey21:20
ttxLooking good, let's see in more details:21:20
ttx* https://blueprints.launchpad.net/glance/+spec/api-v2-store-access21:20
ttxWhat's the status here ? ETA for code being proposed ?21:21
bcwaldonttx: today/tomorrow21:21
ttxOk... Is this the last step before we can mark the api-2 super-blueprint completed ?21:21
ttx* https://blueprints.launchpad.net/glance/+spec/glance-deprecate-client21:21
ttxIs this one just a question of finding the 5min to do it, or is it blocked on something else ? (like glance-client-parity ?21:21
bcwaldonthat will be done today/tomorrow by me if nobody jumps at it21:22
bcwaldonits a 5-min thing21:22
ttxok, then I think we look good here21:22
*** markmcclain has joined #openstack-meeting21:22
ttxOn python-glanceclient side, is there anything blocking the core stuff ?21:22
*** ecarlin has quit IRC21:22
bcwaldonits in great shape21:22
bcwaldonit does have some outstanding ssl-related reviews21:22
bcwaldonthat could use some love21:22
ttxbcwaldon: Anything else ?21:23
bcwaldonI wanted to mention that I'm thinking through images api versioning21:23
bcwaldon(surprise surprise)21:24
bcwaldonand I will be sending out an email with my thoughts21:24
ttxsuspense is now killing me21:24
vishyttx: mind if i jump ahead in the queue, may be losing internet soon.21:24
ttxvishy: ok, you're next21:24
ttxQuestions on Glance ?21:24
ttx#topic Nova status21:25
*** openstack changes topic to "Nova status"21:25
ttx#link https://launchpad.net/nova/+milestone/folsom-321:25
ttxvishy: Let's see progress on essential stuff:21:25
ttx* https://blueprints.launchpad.net/nova/+spec/general-host-aggregates (jog0)21:25
*** notmyname has quit IRC21:25
ttxThis one looks in danger because of lack of review activity ?21:25
*** notmyname has joined #openstack-meeting21:25
*** salv-orlando has joined #openstack-meeting21:25
vishyttx: yes, although I think it is ready, just needs a +221:26
jog0ttx: I got a few reviews today, but still need more reviews21:26
vishythe last patch in the series might not make it21:26
*** sandywalsh has joined #openstack-meeting21:26
ttx#help nova-core needed to review general-host-aggregates proposed changes21:26
vishyjog0, ttx: but I think we can mark it complete without it21:26
jog0vishy: I agree21:27
ttxvishy, jog0: sure, maybe create a separate blueprint or bug to track the remaining work21:27
vishyttx: cool21:27
ttx* https://blueprints.launchpad.net/nova/+spec/integrate-python-glanceclient21:27
ttxIs this one complete ? Or more code is needed ?21:27
jog0ttx: +121:27
bcwaldonI'm blocked on testing that guy21:27
bcwaldonso frustrating21:27
ttxblocked on testing ? How can we unblock you ?21:28
bcwaldonnot use glance client three different ways in nova21:28
bcwaldonits all on me21:28
* vishy slaps bcwaldon21:28
ttxbcwaldon: should still be in in time for F3 ?21:28
bcwaldonI dont want openstack folsom to use legacy glance client21:29
*** andrewbogott is now known as andrewbogott_afk21:29
bcwaldonwouldnt be the end of the world, but t'would be better21:29
ttxhmm right. We would probably have to grant an exception for that21:29
ttxbut would definitely prefer if it got in in time21:30
ttxOthers may just already be complete:21:30
ttx* https://blueprints.launchpad.net/nova/+spec/extract-nova-volumes (remaining work is covered in Cinder blueprint ?)21:30
vishyjgriffith: progress on migration?21:30
ttx(or is there anything left to do on Nova's code side ?)21:30
jgriffithvishy: ttx: pretty much there21:30
jgriffithdb and persistent targets added to cinder-manage21:30
vishyjgriffith: do you have changes to nova-manage? or is it separate?21:30
jgriffithvishy: I made them all in cinder-manage21:31
vishygreat we can mark that implemented then21:31
annegentlejgriffith: how's progress on docs?21:31
jgriffithWriting a script now to do the service switch over etc and doing some tests21:31
ttxvishy: will do21:31
jgriffithannegentle: believe it or not, I am working on it :)21:31
ttx* https://blueprints.launchpad.net/nova/+spec/xenstore-metadata looks complete too21:31
annegentlejgriffith: I do :)21:31
ttxas do https://blueprints.launchpad.net/nova/+spec/per-user-quotas and https://blueprints.launchpad.net/nova/+spec/update-flavor-key-value21:32
vishyyes and the plugin one21:32
ttxAll 4 ?21:32
ttxnovaplugins ?21:33
ttxvishy: still with us ?21:33
vishyjust marking them21:34
ttxheh, just checking.21:34
vishyandrewbogott_afk: ping?21:34
vishylooks like he is afk, I'm not sure if he had more to do on that one21:34
ttxvishy: you can update them off-meeting21:34
vishymarked the other three implemented21:34
ttxA couple more questions...21:34
*** sandywalsh has quit IRC21:34
ttx* https://blueprints.launchpad.net/nova/+spec/disable-server-extensions : priority ?21:34
vishyi consider it essential for release21:35
*** notmyname has quit IRC21:35
vishybut the later ones can be done as bugs21:35
ttxvishy: mark it High and we'll do bugs21:35
ttx* https://blueprints.launchpad.net/nova/+spec/volume-usage-metering : was that started ? ISTR seeing it discussed somewhere21:35
vishyttx: marked it, any that miss we will do as bugs21:35
vishyttx: yes it was discussed, but i think the plan was to do it in cinder instead21:36
vishyhaven't seen any props21:36
jgriffithYes, that's correct21:36
ttxin Cinder in Folsom ?21:36
ttxor some Grizzly thing ?21:36
jgriffithttx: yes Folsom21:36
ttxok will redirect21:36
jgriffithttx: But I haven't heard anyhting about it for a while now21:36
*** notmyname has joined #openstack-meeting21:36
ttx#info In general, if anyone already knows a given feature won't make it, please mark its blueprint "Deferred"21:37
ttxthere are more than one in that case21:37
ttxIt will help others focus on stuff that is more likely to land.21:37
ttxvishy: Anything else ?21:37
vishynope, we will have another meeting on thursday21:37
vishymostly just need help with reviews21:37
vishyactually yes21:38
*** joshuamckenty has quit IRC21:38
vishyneed lots of help with reviews:21:38
vishyis a big one that would be nice to get in21:38
vishy+ the cells code21:38
ttx#help need help with reviews, including https://review.openstack.org/1072621:38
markmcyeah, was going to mention cells21:39
ttxvishy: you really want Cells in in Folsom rather than early Grizzly ?21:39
markmcwould be good to have a bp to track it every week21:39
annegentle#help need documentation on cells21:39
*** rnirmal has quit IRC21:39
ttx#action comstud to create a Cells blueprint so that we can track it21:39
vishyttx: early grizzly is probably fine for cells, although experimental support in would be nice for the third parties that are waiting on it21:40
vishylike mercado-libre21:40
ttxvishy: it's sufficiently separate ?21:40
ttxfrom the core code ?21:40
vishythey may be able to work off of trunk though so isn't super crazy21:40
markmcvishy, if only we had a way of marking things as experimental :)21:40
vishyttx: yes, both cells and bare metal don't really touch core21:40
russellband even if it's marked experiemental, people are going to want backports21:41
vishymarkmc: yes we do! release notes!21:41
markmcheh, who reads docs21:41
ttxi do.21:41
* markmc hides from annegentle :)21:41
russellbso not sure what experimental does other than set expectations ... doesn't reduce maintenance load21:41
* ttx lies well21:41
* annegentle finds markmc 21:41
* jgriffith ducks so annegentle can reach markmc 21:41
vishyrussellb, markmc: point taken, do you feel the same about the bare metal stuff?21:41
russellbi don't think something should go in as experiemental, if it's not ready, it's just not ready21:42
markmcvishy, haven't looked yet, but it does seem late21:42
markmcvishy, new drivers are slightly different, though - e.g. doesn't add API21:42
ttxrussellb: +1 -- bracnhes can be used to track experimental stuff21:42
russellbbaremetal stuff does have some docs on the wiki, so that was cool, i don't know about the code state yet21:42
vishymarkmc: we have the unfortunate result of having a tremendous amount of work being done by multiple companies21:42
vishymarkmc: who are trying to do their best to get into folsom21:42
*** ecarlin has joined #openstack-meeting21:42
vishylets discuss it at the nova meeting/mailing list21:43
ttxLooks like a good topic for the Nova meeting21:43
markmcsure, sounds good21:43
ttxAs long as there is no blueprint for it, it doesn't exist from my perspective21:43
russellbi don't think we should decide based on that it seems late, judge it by the quality of the code21:43
ttxand late blueprint I do despise.21:43
russellbbut i don't think we should cut slack if there isn't enough time for legitimate feedback to be addressed21:43
vishyttx: ok I'm done, you can move on!21:43
ttxOther questions on Nova ?21:43
ttx#topic Quantum status21:44
*** openstack changes topic to "Quantum status"21:44
ttxdanwent: yo21:44
ttx#link https://launchpad.net/quantum/+milestone/folsom-321:44
danwentbtw, refresh if you haven't in the past half hour21:44
ttxProgress looks generally good, but I think it's time to land and complete stuff21:44
danwentyeah, today was our deadline for all 'features' being pushed to review.openstack.org21:44
danwentsome of the stuff is not truly complete though, they are WIP branches21:44
ttxAh, that explains it21:44
ttxOK, essential stuff review...21:45
ttx* https://blueprints.launchpad.net/quantum/+spec/provider-networks21:45
ttxProposal is in, missing review: https://review.openstack.org/#/c/10938/21:45
ttxIt's the last part, right ?21:45
ttx* https://blueprints.launchpad.net/quantum/+spec/quantum-v2-public-networks21:45
ttxStill blocked in review at https://review.openstack.org/#/c/9845/21:45
ttxThis is also the last part ?21:45
danwentchecking the reviews, it looks like we're getting some input from people who weren't around when the original discussion happened on the ML :(21:46
danwentso I think we're going to simplify the code a bit to avoid the objection, and then merge it.21:46
ttxyay, ignore them :)21:46
ttx* https://blueprints.launchpad.net/quantum/+spec/quantum-l3-fwd-nat21:46
ttx"Needs code review"... Where is the review ?21:46
danwentI just pushed that today.  definitely still needs polish, testing, and style cleanup21:47
ttxIs it the only part needed ?21:47
danwentI think jenkins missed it21:47
danwentyes, all code is there, just not in great shape21:47
ttxLink it here and I'll add it21:47
ttxOK. In other news was wondering if https://blueprints.launchpad.net/quantum/+spec/quantum-notifications was actually completed ?21:47
danwenti'll add it, as I want to add the cli link too21:47
*** Gordonz has quit IRC21:47
danwentyes, it was merged a few days ago, but not updated on LP21:48
ttxok, will do21:48
ttxThere are a number of folsom-3 targets that are not in the plan:21:48
ttxcisco-nxos-enables-multiple-ports, metadata-overlapping-networks, metaplugin21:48
ttxShould I just add them with Low prio ?21:48
danwenti actually updated their priority abou 20 mins ago21:48
*** rafaduran has quit IRC21:49
danwentall med + low21:49
*** s0mik has quit IRC21:49
ttxdanwent: did you set their series goal as well ?21:49
ttx=Folsom ?21:49
ttxFinally, looking at untargeted blueprints in https://blueprints.launchpad.net/quantum/folsom :21:49
danwent(at least on two of them… i'll re-run ttx.py later to be sure)21:49
ttxhttps://blueprints.launchpad.net/quantum/+spec/add-basic-quantum-system-tests looks like it should be a Tempest blueprint rather than a Quantum one ?21:49
*** s0mik has joined #openstack-meeting21:50
danwentyes, probably, though I think that BP is basically dead (no one has worked in it in months)21:50
ttxwill redirect21:50
ttxWhat about https://blueprints.launchpad.net/quantum/+spec/quantum-security-groups and https://blueprints.launchpad.net/quantum/+spec/quantum-client-security-groups ?21:50
*** s0mik has quit IRC21:50
ttxcan I remove them from the Folsom series goal ?21:51
*** s0mik has joined #openstack-meeting21:51
danwentWe're going to work on them very soon after F-3, but we just can't get them in for Folsom.  We have a lot of testing + bug fixing to do as it is.21:51
ttxdanwent: ok... Anything else ?21:51
danwentnot that I can think of...21:51
danwentjust going to need to organize the core devs to focus on the top priority reviews21:51
ttxyes, lots of review backlog now21:52
danwentand then test test test21:52
ttxQuestions on Quantum ?21:52
* ttx pauses21:52
annegentleI just wanted to check on the doc plan of record - you're updating wiki pages and Diane's bringing it into "official" docs?21:52
danwentannegentle: that's what we're doing for the API spec.  salv-orlando is leading that.21:52
danwentfor admin docs, I was planning on doing doc-book directly21:53
annegentleok, and what's the plan for admin?21:53
danwentwhile pulling in chunks of text from others21:53
annegentleheh I can't type  fast enough!21:53
ttxOther questions ?21:53
danwenti'll be the point-of-contact for admin docs21:53
annegentleok sounds good. Any WADL for the API so we could put it on api.openstack.org?21:53
annegentleI can contact salv-orlando offline with the WADL Q.21:53
danwenti don't think we have it at this point.21:53
danwentyeah, that would be great.21:54
salv-orlandoI don't believe we'll have a wadl for next week21:54
ttxok then21:54
ttx#topic Cinder status21:54
*** openstack changes topic to "Cinder status"21:54
ttxjgriffith: howdy!21:54
ttx#link https://launchpad.net/cinder/+milestone/folsom-321:54
ttxWe already touched it during the Nova part21:54
ttx* https://blueprints.launchpad.net/cinder/+spec/migrate-nova-volumes-to-cinder21:54
ttxHow is this doing ? You told me yesterday it was almost done ?21:54
jgriffithI think we're ready to close that21:54
*** ayoung has quit IRC21:54
annegentlesalv-orlando: I just got a WADL for object storage last week so it's not time-sensitive other than missing out on being on api.openstack.org :)21:55
ttxjgriffith: as in.. propose code ?21:55
ttxor have it merged ?21:55
*** kindaopsdevy has quit IRC21:55
*** s0mik has quit IRC21:55
jgriffithYeah, I should push the review today21:55
ttxok, set to "Needs code review" status when done21:55
jgriffithThe patch will only be db and targets21:55
jgriffithEverything else is so dependent I'm doing an example script21:56
ttxjgriffith: Anything else on your mind ?21:56
jgriffithie switching the service21:56
*** kindaopsdevy_ has quit IRC21:56
jgriffithLots of things up in the air21:56
jgriffithmulti back-ends and boot from volumes21:56
ttxThat's how the last week before FeatureFreeze should look21:56
ttxQuestions on Cinder ?21:56
ttx#topic Horizon status21:57
*** openstack changes topic to "Horizon status"21:57
ttxgabrielhurley: o/21:57
gabrielhurleyttx: hello sir21:57
ttx#link https://launchpad.net/horizon/+milestone/folsom-321:57
ttxStill feeling confident about those 4 incomplete "High" blueprints ? What's the ETA for code proposal on them ?21:57
gabrielhurleyas soon as I get through this quantum stuff they're next on deck21:57
gabrielhurleywell, two of them *are* the quantum stuff21:58
*** dwcramer has quit IRC21:58
ttxso code should be pushed for review in the next two days for those ?21:58
gabrielhurleyI'd say end of the week is reasonable21:58
ttxLooking at https://blueprints.launchpad.net/horizon/folsom ...21:59
ttxCan we assume that anything not targeted to folsom-3 (i.e. identity-backend-type, syspanel-tests and tenant-deletion) should be deferred to Grizzly ?21:59
ttxok, will clean up21:59
ttxgabrielhurley: Anything else you wanted to mention ?21:59
gabrielhurleymore eyes on the quantum code review would be awesome21:59
ttx#action ttx to create grizzly series for Horizon and defer non-targeted Folsom bps21:59
gabrielhurleyalso, help getting the devstack/quantum docs up-to-date21:59
gabrielhurleyit's making reviewing/testing that code difficult22:00
gabrielhurleythat's about it22:00
ttxQuestions for Horizon ?22:00
*** kiffer84 has joined #openstack-meeting22:00
ttx#topic Other Team reports22:01
*** openstack changes topic to "Other Team reports"22:01
ttxAny other team lead with a status report ?22:01
annegentleI'll be quick22:01
ttxannegentle: go for it22:01
annegentleReminder to please use DocImpact in your commit messages. And don't be surprised if I just amend  your message with DocImpact added.22:01
annegentlethat's all22:02
*** ecarlin has quit IRC22:02
ttxquick indeed22:02
ttx#info remember to please use DocImpact in your commit messages. And don't be surprised if I just amend  your message with DocImpact added.22:02
ttx#topic Open discussion22:02
*** openstack changes topic to "Open discussion"22:02
ttxAnything else, anyone ?22:02
ttxwell the,22:03
*** openstack changes topic to "OpenStack meeting channel. See http://wiki.openstack.org/Meetings for schedule and http://eavesdrop.openstack.org/meetings/openstack-meeting/ for meeting logs"22:03
openstackMeeting ended Tue Aug  7 22:03:03 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-07-21.03.html22:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-07-21.03.txt22:03
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-07-21.03.log.html22:03
ttxThanks everyone!22:03
*** gabrielhurley has left #openstack-meeting22:03
*** lzyeval has quit IRC22:03
*** ecarlin has joined #openstack-meeting22:05
*** dolphm has quit IRC22:07
*** kindaopsdevy has joined #openstack-meeting22:08
*** markmcclain has quit IRC22:09
*** dendro-afk is now known as dendrobates22:10
*** littleidea has quit IRC22:13
*** s0mik has joined #openstack-meeting22:13
*** kindaopsdevy_ has joined #openstack-meeting22:15
*** gyee has quit IRC22:15
*** andrewbogott_afk is now known as andrewbogott22:17
*** kindaopsdevy has quit IRC22:18
*** kindaopsdevy_ is now known as kindaopsdevy22:18
*** kindaopsdevy has quit IRC22:19
*** kindaopsdevy has joined #openstack-meeting22:19
*** s0mik has quit IRC22:20
*** s0mik has joined #openstack-meeting22:23
*** troytoman is now known as troytoman-away22:35
*** s0mik has quit IRC22:42
*** AlanClark has quit IRC22:44
*** matwood has quit IRC22:49
*** mattray has quit IRC22:52
*** mikal has quit IRC23:02
*** mikal has joined #openstack-meeting23:04
*** lloydde has quit IRC23:05
*** mikal has quit IRC23:09
*** mikal has joined #openstack-meeting23:10
*** ncode has quit IRC23:12
*** mnewby has quit IRC23:23
*** mnewby has joined #openstack-meeting23:24
*** dendrobates is now known as dendro-afk23:25
*** mnewby has quit IRC23:25
*** patelna has quit IRC23:28
*** dwcramer has joined #openstack-meeting23:30
*** littleidea has joined #openstack-meeting23:33
*** ecarlin has quit IRC23:35
*** andrewbogott is now known as andrewbogott_afk23:41
*** andrewbogott_afk is now known as andrewbogott23:44
*** mnewby has joined #openstack-meeting23:45
*** Ravikumar_hp has quit IRC23:46
*** thingee is now known as thingee_zz23:47
*** dprince has quit IRC23:57

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