Tuesday, 2012-01-24

*** adjohn has joined #openstack-meeting00:01
*** adjohn has quit IRC00:05
*** ravi has quit IRC00:10
*** adjohn has joined #openstack-meeting00:11
*** patelna has quit IRC00:16
*** rnirmal has quit IRC00:19
*** sleepsonthefloo has quit IRC00:23
*** dprince has joined #openstack-meeting00:38
*** debo-os has joined #openstack-meeting00:44
*** dolphm has joined #openstack-meeting00:47
*** dprince has quit IRC00:48
*** carlp has quit IRC00:53
*** debo-os has quit IRC01:05
*** ravi has joined #openstack-meeting01:08
*** sleepsonthefloo has joined #openstack-meeting01:08
*** sandywalsh has quit IRC01:10
*** dendrobates is now known as dendro-afk01:12
*** dolphm has quit IRC01:13
*** dendro-afk is now known as dendrobates01:14
*** ttx has joined #openstack-meeting01:27
*** ttx has joined #openstack-meeting01:27
*** lloydde has quit IRC01:33
*** _adjohn has joined #openstack-meeting01:34
*** adjohn has quit IRC01:35
*** _adjohn is now known as adjohn01:35
*** zns has quit IRC01:36
*** jakedahn has quit IRC01:46
*** jakedahn has joined #openstack-meeting01:46
*** adjohn has quit IRC01:56
*** zns has joined #openstack-meeting02:08
*** glenc has joined #openstack-meeting02:10
*** zns has quit IRC02:18
*** jog0 has left #openstack-meeting02:21
*** bencherian has quit IRC02:23
*** gyee has quit IRC02:43
*** jdurgin has quit IRC02:48
*** jakedahn_ has joined #openstack-meeting02:58
*** zns has joined #openstack-meeting02:58
*** jakedahn has quit IRC03:02
*** jakedahn_ is now known as jakedahn03:02
*** novas0x2a|laptop has quit IRC03:28
*** dwalleck_nova has joined #openstack-meeting03:41
*** oubiwann has quit IRC03:45
*** lloydde has joined #openstack-meeting04:04
*** carlp has joined #openstack-meeting04:11
*** ayoung has quit IRC04:13
*** deshantm__ has quit IRC04:18
*** bencherian has joined #openstack-meeting04:20
*** dendrobates is now known as dendro-afk04:21
*** dendro-afk is now known as dendrobates04:23
*** deshantm__ has joined #openstack-meeting04:32
*** dwalleck_nova has quit IRC05:01
*** ewindisch has quit IRC05:01
*** deshantm__ has quit IRC05:19
*** ewindisch has joined #openstack-meeting05:35
*** lloydde has quit IRC05:43
*** mikal has quit IRC05:46
*** mikal has joined #openstack-meeting05:50
*** mikal has quit IRC05:54
*** mikal has joined #openstack-meeting05:58
*** GheRivero_ has joined #openstack-meeting06:01
*** bencherian has quit IRC06:21
*** zigo has joined #openstack-meeting06:33
*** GheRivero_ has quit IRC06:35
*** GheRivero is now known as Gherivero07:03
*** Gherivero is now known as Rivero07:03
*** zigo has quit IRC07:05
*** novas0x2a|laptop has joined #openstack-meeting07:51
*** sleepsonthefloo has quit IRC08:13
*** sleepsonthefloor has joined #openstack-meeting08:19
*** carlp has quit IRC08:19
*** jakedahn has quit IRC08:19
*** westmaas has quit IRC08:19
*** medberry has quit IRC08:19
*** sleepson- has quit IRC08:19
*** westmaas has joined #openstack-meeting08:21
*** carlp has joined #openstack-meeting08:21
*** medberry has joined #openstack-meeting08:22
*** medberry has joined #openstack-meeting08:22
*** novas0x2a|laptop has quit IRC08:23
*** novas0x2a|laptop has joined #openstack-meeting08:31
*** novas0x2a|laptop has quit IRC08:37
*** novas0x2a|laptop has joined #openstack-meeting08:39
*** darraghb has joined #openstack-meeting09:50
*** zigo has joined #openstack-meeting09:50
*** derekh has joined #openstack-meeting10:12
*** novas0x2a|laptop has quit IRC10:30
*** novas0x2a|laptop has joined #openstack-meeting11:40
*** markvoelker has joined #openstack-meeting11:57
*** novas0x2a|laptop has quit IRC12:43
*** dprince has joined #openstack-meeting13:06
*** glenc_ has joined #openstack-meeting13:15
*** glenc has quit IRC13:17
*** bencherian has joined #openstack-meeting13:37
*** AlanClark has joined #openstack-meeting13:59
*** mattray has joined #openstack-meeting14:00
*** Rivero has quit IRC14:01
*** GheRivero has joined #openstack-meeting14:01
*** hggdh has quit IRC14:24
*** hggdh has joined #openstack-meeting14:28
*** dendrobates is now known as dendro-afk14:32
*** bencherian has quit IRC14:36
*** dendro-afk is now known as dendrobates14:50
*** glenc_ is now known as glenc15:10
*** shang has joined #openstack-meeting15:10
*** reed has joined #openstack-meeting15:14
*** Gordonz has joined #openstack-meeting15:15
*** mikal has quit IRC15:15
*** shang has quit IRC15:19
*** mikal has joined #openstack-meeting15:21
*** dendrobates is now known as dendro-afk15:23
*** dendro-afk is now known as dendrobates15:23
*** GheRivero_ has joined #openstack-meeting15:24
*** ayoung has joined #openstack-meeting15:33
*** bmcconne has quit IRC15:44
*** GheRivero_ has quit IRC15:47
*** mikal has quit IRC15:48
*** MrHeat has joined #openstack-meeting15:55
*** MrHeat has left #openstack-meeting15:55
*** dolphm has joined #openstack-meeting15:57
*** rnirmal has joined #openstack-meeting16:00
*** AlanClark has quit IRC16:04
*** AlanClark has joined #openstack-meeting16:06
*** reed has quit IRC16:19
*** dendrobates is now known as dendro-afk16:37
*** mattray1 has joined #openstack-meeting16:43
*** mattray has quit IRC16:44
*** ayoung has quit IRC16:45
*** ayoung has joined #openstack-meeting16:45
*** dolphm has quit IRC16:51
*** dolphm has joined #openstack-meeting16:52
*** lloydde has joined #openstack-meeting16:53
*** mattray1 is now known as mattray16:55
*** mattray has joined #openstack-meeting16:55
*** bmcconne has joined #openstack-meeting17:11
*** dendro-afk is now known as dendrobates17:20
*** derekh has quit IRC17:20
*** patelna has joined #openstack-meeting17:21
*** davlap has joined #openstack-meeting17:45
*** sleepsonthefloo has joined #openstack-meeting17:46
*** sleepsonthefloo has quit IRC17:46
*** sleepsonthefloo_ has joined #openstack-meeting17:53
*** sleepsonthefloo_ has quit IRC17:53
*** sleepsonthefloo_ has joined #openstack-meeting17:53
*** sleepsonthefloo_ has quit IRC17:53
*** LinuxJedi has joined #openstack-meeting17:53
*** sleepsonthefloo_ has joined #openstack-meeting17:54
*** sleepsonthefloo_ has quit IRC17:55
*** sleepsonthefloo has joined #openstack-meeting17:55
*** martine has joined #openstack-meeting17:56
ayoungAnyone here for Keystone?18:00
ayoungzns, Keystone?18:02
znsayoung: yes.18:03
zns#startmeeting Keystone Team Meeting18:03
openstackMeeting started Tue Jan 24 18:03:54 2012 UTC.  The chair is zns. Information about MeetBot at http://wiki.debian.org/MeetBot.18:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.18:03
*** openstack changes topic to " (Meeting topic: Keystone Team Meeting)"18:03
znsHi there! Anyone else here for Keystone?18:04
znsQuick Update on status: https://launchpad.net/keystone/+milestone/essex-318:05
znsWe're tracking well to completing these items today. We'll be ready to bask under the sunlight of ttx's microscope in a few hours.18:06
*** jog0 has joined #openstack-meeting18:06
znsAnything you had on your mind, specifically, ayoung? Looks like you're the only one here...18:06
ayoungzns, what is the relationship between the Essex release and the Eventlet upstream?18:06
ayoungThere is a patch for IPv6 which I'm looking at,  but that doesn't seem to have generated much interest other than me.\18:07
ayoungIf it goes in,  it fixes: https://bugs.launchpad.net/bugs/85688718:07
uvirtbotLaunchpad bug 856887 in keystone "Keystone cannot listen on IPv6" [Medium,In progress]18:07
znsIPv6 support is listed as a bug. I think we can add it without breaking or altering existing functionality or configs. So I would vote for including it in Essex as long as it lands before E5 (my vote/guess).18:08
*** digitaldreams77 has joined #openstack-meeting18:08
ayoungI'm guessing that even if it got checked in right now,  there is still a delay  in closing it.  Is it gated on getting an updated Eventlet in Ubuntu, or is just having it upstream sufficient?18:08
znsBy 'lands' I mean in a released version of eventlt. Other alternatives would be code we can include in OpenStack projects that patches eventlet.18:08
*** adjohn has joined #openstack-meeting18:09
*** digitaldreams77 has left #openstack-meeting18:09
ayoungcan we ship a customer version of eventlet?18:09
znsI don't know. I wouldn't want to hold back other distros if Ubuntu was the only one not supporting it.18:10
znsThat sounds like a packaging question. Maybe ask ttx later? Or the team in openstack-dev?18:10
*** novas0x2a|laptop has joined #openstack-meeting18:11
znsDo you think it is something that can be patched at runtime or is it deep in the eventlet code?18:11
*** _adjohn has joined #openstack-meeting18:11
ayoungzns, it is already monkey patched once.  It would make more sense to ship a patched eventlet,  and let the monkey patching happen as per normal18:12
znsAnything else? Anyone else?18:12
ayoungzns, I took a quick look at alternative auth methods18:13
znsif not, I think we can go back to getting E3 done!18:13
znsalternatives like? oauth? basic?18:13
ayoungAgain,  this is an eventlet issue:  I am not sure exactly what it supports,  but I think it is safe to say the Negotiate and Client certs are not supported18:13
*** adjohn has quit IRC18:13
*** _adjohn is now known as adjohn18:13
ayoungBasic auth is (I am fairly sure) supported by Eventlet18:13
ayoungand there is one ticket...18:14
znsSame applies to httplib… would be nice if we could plug in our protocol.18:14
uvirtbotLaunchpad bug 773804 in keystone "Feature: basic auth" [Wishlist,New]18:14
ayoungI am not on the hook for anyting other than the IPv6...was wondering what else is high enough priority that I should be looking at it.18:15
ayoungthis is the only one that has no one assigned https://bugs.launchpad.net/keystone/+bug/84306618:15
uvirtbotLaunchpad bug 843066 in keystone "Unable to auth against nova with keystone enabled novaclient ..." [High,Fix committed]18:15
*** andrewsben has joined #openstack-meeting18:15
ayoungthat is high priority18:16
ayoungthere are 3 other of medium or lower:18:16
znsFrom my perspective RBAC is big, but that's probably a big conversation to have in Folsom. Until then, I think we'll all be focusing on stability. So getting bugs closed, improving logging, adding diagnostics, etc...18:16
uvirtbotLaunchpad bug 885750 in keystone "Support CRUD calls for ec2credentials as per contract." [Medium,Confirmed]18:17
uvirtbotLaunchpad bug 919397 in keystone "Tests in MiddlewareTestCase not being executed" [Medium,Confirmed]18:17
ayoungthose are moth medium.18:17
ayoungUndecided:  https://bugs.launchpad.net/bugs/90452618:17
uvirtbotLaunchpad bug 904526 in keystone "ec2tokens passes AWS Access Key ID twice" [Undecided,Confirmed]18:17
znsIf you can get some of that done before ttx cuts the release that would SUPER. I think anotherjesse put in some code to keystoneclient for that.18:17
ayoungzns the nova ticket?18:18
*** gyee has joined #openstack-meeting18:18
znsI think it was here: https://review.openstack.org/#change,308918:19
ayoungzns, also  can you confirm the IPv6 fix?  I suspect that more voices speaking up the better, and faster into upstream18:20
*** novas0x2a|laptop has quit IRC18:20
*** novas0x2a|laptop has joined #openstack-meeting18:20
ayoungThe patch was posted to the Eventlet DL, I can forward if needs be.18:20
ayoungBut the repo is https://bitbucket.org/flub/eventlet-ipv6/18:20
znsayoung: sure, I have the link. Will do later this week.18:21
*** jdurgin has joined #openstack-meeting18:21
znsAnother thing we need to do is make sure ec2 calls also follow the correct spec:18:21
zns  "auth": {18:21
zns    "OS-KSEC2:ec2Credentials": {18:21
zns      "username": "test_user",18:21
zns      "secret": "aaaaa",18:21
zns      "signature": "bbb"18:21
zns    },18:21
zns    "tenantId": "77654"18:21
zns  }18:21
znsI think there are different clients making different calls.18:21
ayoungzns does that fall under 885750?18:21
ayoungIf so,  I can take that one18:22
znsNot quite. I think it is spread about. There are three or four ec2 bugs.18:23
*** oubiwann has joined #openstack-meeting18:24
ayoungWHat is the scope of 885750?  It is't clear from the report18:24
zns843058, 869778, 904526, ...18:24
gyeeyou guys see any performance issues with ec2 signature validation? two round trips to the backend18:25
ayounghttps://bugs.launchpad.net/keystone/+bug/843058  says "fix commited"18:25
uvirtbotLaunchpad bug 843058 in keystone "EC2 compatibility middleware" [High,Fix committed]18:25
zns885750's scope was to implement the REST APIs to allow the management of EC2 credentials; and as part of that write a client to test (preferable python-keystoneclient)18:25
ayoungzns, I can take https://bugs.launchpad.net/keystone/+bug/86977818:26
uvirtbotLaunchpad bug 869778 in keystone "2 bugs in ec2_token.py" [Undecided,New]18:26
znsCool. Akira also just posted some S3 code which I merged in last night. I'm about to submit another fix to EC2 so the server listens for the right contract as I posted above.18:27
ayoungzns do you think that fixes 869778  or is just something I should be aware of?18:28
znsJust to be aware of it. He copied the EC2 code to make the S3 code, so he may have included code that works in S3 that you can reference. Just FYI18:29
ayoungzns, OK  I'll grab that ticket.  Any others?18:30
zns904526 would be great.18:31
ayoungOK.  I'll see what I can do.18:31
znsayoung: thanks18:33
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"18:33
openstackMeeting ended Tue Jan 24 18:33:44 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:33
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-24-18.03.html18:33
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-24-18.03.txt18:33
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-24-18.03.log.html18:33
*** zns has quit IRC18:34
*** zns has joined #openstack-meeting18:34
*** gyee has quit IRC18:36
*** martine has quit IRC18:39
*** gyee has joined #openstack-meeting18:43
*** martine has joined #openstack-meeting18:47
*** ohnoimdead has joined #openstack-meeting18:48
*** darraghb has quit IRC18:49
*** Gordonz has quit IRC18:57
*** adjohn has quit IRC18:57
*** adjohn has joined #openstack-meeting18:57
*** LinuxJedi_cell has joined #openstack-meeting18:57
mtaylorhey LinuxJedi_cell18:57
*** Gordonz has joined #openstack-meeting18:57
LinuxJedi_cellHey mtaylor. Swimming running late18:58
mtaylorLinuxJedi_cell: no worries.18:58
*** jakedahn has joined #openstack-meeting18:58
LinuxJedi_cellmtaylor: if you scroll up -infra you should see the topic me and ttx proposed18:59
mtaylorLinuxJedi_cell: yes. I have read it18:59
LinuxJedi_cellmtaylor: cool :)19:00
openstackMeeting started Tue Jan 24 19:02:15 2012 UTC.  The chair is mtaylor. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.19:02
mtaylor#topic OpenStack CI Meeting19:02
*** openstack changes topic to "OpenStack CI Meeting"19:02
mtaylorhey all - what's up?19:02
LinuxJedi_cellThe sky19:02
mtaylorit's good that the sky is up19:03
LinuxJedi_cellTrue :)19:03
mtaylorso - LinuxJedi_cell and ttx were chatting earlier and had a couple of questions about gerrit review voting19:03
*** jakedahn has quit IRC19:04
*** jakedahn has joined #openstack-meeting19:04
mtaylora) can a -2 vote be overridden19:04
mtaylorb) why do we need a +2 vote in addition to the approval vote19:05
mtaylorthe answer to a) is really easy ... "no"19:06
LinuxJedi_cellWell, more why can't it for a)19:06
mtaylora -2 is a hard blocker vote which is essentially saying "over my dead body will this go in, you will have to convince me first"19:06
LinuxJedi_cellLol! OK :)19:07
mtaylorwhich is a thing that has been requested in the past (and then we got lucky because it already worked that way019:07
_0x44mtaylor: +2 is needed to distinguish -core from +1 reviewers...19:07
mtaylor-2 is the only vote which persists across new patches19:07
mtaylorand _0x44 is correct about purpose of +2 votes19:07
mtayloralso, if a core reviewer is adding the second review and hitting approve, having them go ahead and add the +2 just makes it clear who the people who voted +2 were later on19:08
mtaylorLinuxJedi_cell: does that help?19:09
LinuxJedi_cellVery much so, thanks19:09
mtaylorof course - they did bring up the issue of a core reviewer voting -2 and going awol, but hopefully we won't have awol core devs too much19:09
mtaylor#topic expiration of old reviews19:10
*** openstack changes topic to "expiration of old reviews"19:10
mtaylorfor those who weren't paying attention first thing this morning, the expire-stale-reviews work that LinuxJedi_cell did went live last night19:10
mtaylorso now code reviews that are old and crusty will get marked abandoned.19:11
mtaylorif a dev really does want it around, they can always go to it and click "unabandon"19:11
*** martines has quit IRC19:11
*** martines has joined #openstack-meeting19:12
mtaylorthe rules are currently that any patch that has no activity in 2 weeks is marked abandoned, and any patch with a negative review and no activity for 1 week is marked abandoned19:12
mtaylorobviously, as this goes on, if those seem either too lax or to strict, they can be adjusted19:12
*** joesavak has joined #openstack-meeting19:12
mtaylor#topic narcissism, or report from LCA19:13
*** openstack changes topic to "narcissism, or report from LCA"19:13
mtaylorjeblair and I went and spoke at Linux Conf Australia last week about the OpenStack gerrit and jenkins setup19:14
mtaylorthe talk went really well, if you can't go to sleep one night and want to be bored, it is on youtube19:14
*** LinuxJedi_cell has quit IRC19:14
mtaylorbut as a result we learned that there are several folks who are implementing our system for their dev environments, either by following our code, or in one case we're talking about making sure that our puppet modules are done in a way that they can consume them directly19:15
mtaylorso that's great- more people poking around at things is always great19:15
mtaylor#topic tox, bundles and multi-version support19:16
*** openstack changes topic to "tox, bundles and multi-version support"19:16
mtayloralso, we've got jobs in jenkins that do a proof of concept of using tox to drive virtualenv building and testing - and that use pip bundles as the package caching method rather than trying to do relocatable virtualenvs19:17
mtaylor(turns out that virtualenvs just aren't properly relocatable - and really the --relocatable option for virtualenv is an outright lie)19:18
mtaylorthe pip bundle part of that is a replacement for the current process we do of making a clean virtualenv, tarring it up and then untarring it at the start of jobs19:18
mtaylorwhich we do to avoid pulling network resources during test runs (gives us quicker speed and also less false negatives)19:19
mtaylortox replaces install_venv.py and with_venv.sh with a tox.ini file, and then handles the creation of the virtualenvs. out of the box it allows us to do multiple python versions (right now doing 2.6 and 2.7)19:20
mtaylorthe plan is to get a few more infrastructure pieces done this week (a set of new builders) so that we can start proposing migrating projects over ... most of them work right now19:21
mtaylornova not so much for reasons I still don't understand19:21
mtaylor#topic open discussion19:21
*** openstack changes topic to "open discussion"19:21
mtayloranything else from anybody?19:21
* LinuxJedi home now19:21
mtaylorhey adam_g19:21
mtaylorhey LinuxJedi19:21
adam_gso, we've got our 12 node CI rig up and running, building packaging and trigger jobs based on upstream commits19:22
notmynameI've got a couple of things19:22
notmyname(but I may have forgotten one)19:22
adam_gat UDS, we discussed possibly hooking this into the upstream jenkins infrastructure, to trigger jobs on our systems and collect upstream, is that right mtalor?19:22
*** GheRivero_ has joined #openstack-meeting19:23
mtayloradam_g: yes. I would love to do that19:23
mtayloradam_g: simplest way from my end would be to get a jenkins slave that runs the driver jobs, and then get your jobs moved/copied in to our jenkins (And give  you access to edit them)19:24
adam_gmtaylor: has this happened yet with any other downstream parties, or is this the first? im curiosu to know when/waht would be triggering jobs, and what information you'd be interested in getting back. our setup is more complex than the devstack-driven single node tests, so i dont want to flood you with garbase19:24
mtaylorI don't know if that meets your needs19:24
mtayloradam_g: we've started the process with a few other downstreams, none of them have actually started running tests though :(19:24
notmynamemtaylor: when not logged in to review.openstack.org, there are nice little copy widgets. they aren't there when I am logged in (minor bug perhaps)19:25
adam_gcurrently we're running a subset of the devstack tests, but hope to have tempest hitting the cluster as well for every deployment soon19:25
mtaylornotmyname: there is a preferences setting for copy widgets ... one sec19:25
Kiallnotmyname: thats a preference for your gerrit account19:25
notmynameah. interesting. thanks19:25
Kiall"Use Flash Clipboard Widget"19:25
mtaylorhttps://review.openstack.org/#settings,preferences  <-- and then what Kiall said19:26
*** oleg__ has joined #openstack-meeting19:26
notmynamemtaylor: and the other thing is the status of the discussion on removing the default text for the votes (eg a -1 could/should only put in the comment "-1")19:26
mtayloradam_g: we'd start off triggering jobs post-merge I think19:26
mtayloradam_g: and we'd be interested in getting back _everything_ (verbose logs are great, because that way devs can diagnose)19:26
adam_gmtaylor: we currently trigger a full deployment/test run on post-merge to nova. but build new packages for commits to almost everything else19:27
adam_gmtaylor: i suppose you and i can sync up sometime outside of meeting to get the ball rolling on this19:27
mtayloradam_g: totally! let's just say that I'm quite excited to get that working!19:28
mtaylornotmyname: physically it's easy to change the text - it's a db table19:28
notmynamemtaylor: if it can be done per project, can we get it changed for swift?19:29
mtaylornotmyname: practically, the text needs to be something, because the -1/+1 doesn't get put into the set of comments, so you can't see vote history any way other than the comment text in the review comment history19:29
notmynamemake the text "-1" or "+1" or whatever19:29
* LinuxJedi is sure there is a bug open for the default message somewhere...19:30
annegentleI have 2 Qs - 1) if I use git review on Lion am I going to run into trouble? See https://bugs.launchpad.net/git-review/+bug/900317.19:30
uvirtbotLaunchpad bug 900317 in git-review "Upgrade doesn't seem to work on MacOSX 10.7.2 Lion" [High,Triaged]19:30
mtaylorit _could_ be changed to be the string "-1" of course - but it's global to all of gerrit, so you'd need to get some consensus across everyone19:30
mtaylorannegentle: gah. I keep meaning to try to find a Lion system to track that bug down ...19:31
notmynamemtaylor: no worries if it's a global thing. if it were per project, it's something I'd want changed. not sure if it's really worth the effort to get it changed globally19:31
mtayloranybody here on OSX Lion?19:31
notmyname(but only for editors, etc. dev target is a VPS)19:31
uvirtbotLaunchpad bug 914431 in openstack-ci "remove automatic comment text from reviews" [Low,Triaged]19:31
LinuxJedithat is the one I am thinking19:32
mtaylorgreat! are you using git-review and/or is it working for you?19:32
mtaylorLinuxJedi: yes. that's the one19:32
annegentlemtaylor: ok I'm just hoping it's not going to affect my work19:32
mtaylorannegentle: I am also hoping that!19:32
LinuxJediannegentle: if you run into any problems feel free to ask for help19:33
mtaylorannegentle: although that error looks like some sort of system issue with pip and not anything specifically git-review related19:33
mtaylorannegentle: LinuxJedi can solve all problems19:33
annegentlemtaylor: and my next question is a basic one - can I get some help patching an already submitted patch? I'm embarrassed I don't know how to already :)19:33
notmynamemtaylor: yes. git-review is working fine for me. I'm using a local (ie current) version of git, and I had to change one of my config settings for ui color (but I don't think that's related to git-review19:33
LinuxJedilol! :)19:33
mtaylorannegentle: yes - be happy to19:33
annegentlemtaylor: yay thanks I'll PM you and not take up meeting time :)19:34
mtaylorannegentle: ok. simple story is "git review -d 2354 # where 2354 is the gerrit review id ; # edit patch ; git commit -a --amend ; git review"19:34
mtaylorannegentle: but grab me and we'll walk through it19:34
mtaylornotmyname: hopefully color thing not related to git review - we did get a patch a while back to make it work properly if git was configured for color output19:35
mtayloroh! while I'm bugging notmyname about things ...19:36
notmynamemtaylor: ya, I had color.ui = True and the newer version of git needed color.ui = always. git-review was fine (I know, I looked at the source)19:36
mtaylorwe're currently doing virtualenv-based testing for everyone except for swift19:36
notmynamedo we still have some hard coded python paths?19:37
mtaylorthe new approach to which is using tox (as I babbled about before)19:37
notmynameI was in here late and did catch all your babbling ;-)19:37
mtaylornotmyname: what? you're not always paying attention to me? weird...19:37
notmynameoh it's in the scoll buffer somewhere...19:38
mtaylornotmyname: main thing is that I'd like to add a tox.ini file to the swift tree (I don't have one written yet) to allow us to use it to do multi-python-version testing and venv-based testing without copying gobs of code into your tree19:38
notmynameah. you know my feelings on having meta stuff in the code (like vcs stuff, review stuff, now testing env stuff)19:39
mtaylornotmyname: that's why I wanted to touch base with you about tha19:40
*** lloydde has quit IRC19:40
notmynameI'm not familiar with tox, so if it's something that offers benefit outside of our specific testing environment, then I'll be more for it19:41
notmyname(the tox.ini)19:41
mtaylornotmyname: it's a tool that knows how to drive nose and friends and to do it in various per-version virtualenvs19:42
mtaylornotmyname: might be easier to look at example ... python-quantumclient is set up to use tox19:42
notmynameok, let me look in to it and then ping me later about it19:43
mtaylornotmyname: awesome. thanks19:43
mtaylornotmyname: also, when you do look in to it, there are currently more stanzas in the quantumclient tox.ini than I really want to be in there19:43
mtaylornotmyname: I'm working on a fix to upstream to allow me to fix that/collapse them19:44
mtaylorok. I think that's it for me... anything else?19:44
notmynamemtaylor: status of your vcsversion stuff?19:44
mtaylornotmyname: languishing - got a slammed the last couple of weeks - but I have nice plane flight tomorrow, which is normally where I get all of my hacking on that done :)19:45
mtaylornotmyname: I did get some good feedback from ttx though19:45
mtaylorso I'm going to try to work through all of that19:45
notmynameI'm still looking forward to it19:45
mtaylorme too!19:45
LinuxJedinotmyname: mtaylor is in the land of management now, so we will zap all his usual dev time ;)19:46
mtaylornotmyname: yes. blame LinuxJedi's Home Based Worker Application Form Approvals19:48
LinuxJedioh wow that stuff is so much fun :)19:48
LinuxJedimtaylor: you could always fill in the "emigrate to USA" forms instead19:49
LinuxJedianyway, getting off-topic for the meeting :)19:49
*** _adjohn has joined #openstack-meeting19:49
mtayloralright! I'm calling it19:49
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"19:49
openstackMeeting ended Tue Jan 24 19:49:41 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-24-19.02.html19:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-24-19.02.txt19:49
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-24-19.02.log.html19:49
*** adjohn has quit IRC19:51
*** _adjohn is now known as adjohn19:51
*** dolphm has quit IRC19:56
*** ewanmellor has joined #openstack-meeting19:56
znsNo new agenda. So assuming no PPB meeting today. Right?20:02
*** patelna has quit IRC20:02
ewanmellorLooks that way20:02
ttxmeeting not confirmed one day ago > no meeting.20:06
*** ravi has joined #openstack-meeting20:11
*** bcwaldon has joined #openstack-meeting20:17
*** adjohn has quit IRC20:19
*** adjohn has joined #openstack-meeting20:19
*** hggdh has quit IRC20:21
*** hggdh has joined #openstack-meeting20:23
*** martine_ has joined #openstack-meeting20:24
*** ewanmellor has quit IRC20:26
*** russellb has joined #openstack-meeting20:30
*** xtoddx- is now known as xtoddx20:34
*** mikal has joined #openstack-meeting20:48
*** edconzel_ has joined #openstack-meeting20:49
*** armandomi has joined #openstack-meeting20:49
*** wwkeyboard has joined #openstack-meeting20:50
*** bhall has joined #openstack-meeting20:50
*** yehudasa has joined #openstack-meeting20:51
*** Vek has joined #openstack-meeting20:54
*** sarob has joined #openstack-meeting20:57
wwkeyboardYou're both early20:59
Vekwwkeyboard: so're you.21:00
Vekand it's by seconds, so...21:00
* dragondm waves21:00
ttxjaypipes, vishy, devcamcar: around ?21:00
*** danwent has joined #openstack-meeting21:00
Vekzns: btw, was just thinking about x-realm Keystone; if you're curious, drop by my desk after the meeting if you can21:00
ayoungVek, no fair,  I'm curious too.21:00
znsVek: WFH today, but would love to hear more.21:01
Vekayoung: don't worry, I haven't fully committed to the concept yet anyway, and once I do, you'll see it too :)21:01
ttxok, let's get started, devcamcar should join soon21:01
*** rkukura has joined #openstack-meeting21:01
openstackMeeting started Tue Jan 24 21:01:41 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
Vekzns: OK, feel free to drop by any time.  I have the concept laid out as a graphic right now.21:01
ttx#topic Actions from previous meeting21:02
*** openstack changes topic to "Actions from previous meeting"21:02
ttx* anotherjesse to sync up with zns on keystone-client blueprint status21:02
ttxzns: did you get some updated status on that ?21:02
znsttx: erm… no, sorry.21:02
ttxvishy: if anotherjesse is near you, could you ask him to join us on irc ?21:03
vishyttx: he is at castle21:03
vishy(in meetings)21:03
*** lzyeval has joined #openstack-meeting21:03
znsttx: I know there has been some work on keystone-client, and I contributed some, but not sure what status I would put on it...21:04
ttxyes, I'm not sure what's the completion criteria on this one21:04
ttxlet's go over the rest of keystone status*21:04
ttx#topic Keystone status21:04
*** openstack changes topic to "Keystone status"21:04
ttx#link https://launchpad.net/keystone/+milestone/essex-321:04
znsttx: when does the gavel hit the gavel-thingy? When are we out of time for E3?21:04
*** heckj has joined #openstack-meeting21:05
ttxideally end of day today, so that I cut the branches tomorrow european morning21:05
ttxthere are 3 open blueprints left:21:05
znstx: ok21:05
ttx* https://blueprints.launchpad.net/keystone/+spec/keystone-client (anotherjesse)21:05
*** mcohen has joined #openstack-meeting21:05
ttx* https://blueprints.launchpad.net/keystone/+spec/keystone-logging (heckj)21:05
*** liemmn has joined #openstack-meeting21:05
ttx* https://blueprints.launchpad.net/keystone/+spec/keystone-documentation (heckj)21:05
ttxzns, heckj: status on the last two ?21:05
*** lloydde has joined #openstack-meeting21:05
znsKeystone status is good. I think we're closing off our last loose ends. The main items are ones assigned outside our team, but if we don't get them done tonight we slip to E4.21:06
*** andrewbogott has joined #openstack-meeting21:06
ttxzns: ok, so I can cut the milestone branch tomorrow with what's in today.21:06
znsAll the above three have enough progress on them to close them for E3. We can re-open new ones for E4 if there is more work. Except maybe keystone-client because it is well defined in a spec...21:06
heckjzns: closing up the doc one now - it's where we needed it to be now21:06
znsttx: yes. We feel good with where we are today. We're cleaning up mainly until you cut.21:07
ttxzns: you have 7 targeted bugs -- which ones are actually blocking E3 ?21:07
znsttx: none.21:07
znsttx: all the bugs we feel we HAD to get done are fix committed already21:07
*** anotherjesse has joined #openstack-meeting21:07
ttxso I will untarget the ones that are left tomorrow21:07
*** lxu has joined #openstack-meeting21:08
ttxanotherjesse: yo21:08
*** somik has joined #openstack-meeting21:08
*** dprince has quit IRC21:08
anotherjessettx: i'm in texas to meet with folks about keystone21:08
ttxanotherjesse: status on https://blueprints.launchpad.net/keystone/+spec/keystone-client ?21:08
anotherjessettx: that mostly works!21:08
ttxanotherjesse: can we consider the bp completed ?21:08
anotherjessettx: I think we have user/role/tenant/ec2 cli21:08
anotherjessettx: we are working on tests as well21:08
heckjanotherjesse: should we drop this back to E4, or wrap it up today?21:09
ttxanotherjesse: here is my suggestion... lets' consider this one completed, and you can file extra blueprints for any work that needs to be done by E421:09
anotherjessettx: I think it is done - I just haven't verified that EVERY function is there21:10
anotherjesseso I think closing it will be good and anythign we didn't hit is a bug21:10
ttxanotherjesse: deal. Updating21:10
jakedahnttx: keystone client cli landed here: https://review.openstack.org/#change,3174 - does basic crud items21:10
ttxzns: Looks good now. Anything else ?21:11
znsNot right now! Thanks21:11
ttxQuestions for Keystone ?21:11
znsFYI: ayoung has been working on evebntlet IPv6 for us, but that applies to all OpenStack. Something to consider for Essex...21:12
*** mperez has joined #openstack-meeting21:12
ttx#topic Swift status21:13
*** openstack changes topic to "Swift status"21:13
ttxnotmyname: o/21:13
ttxnotmyname: Signs of 1.4.6 ?21:13
notmynameyes, probably in about 3 weeks21:14
*** ewanmellor has joined #openstack-meeting21:14
ttxnotmyname: should we set a tentative date, even if that may be modified ?21:15
ttxor just keep it open-ended ?21:15
notmynameI think we could tentatively set feb 13.21:15
*** liemmn_ has joined #openstack-meeting21:15
ttxI'll be skiing on that week, but I can find other people to replace me21:15
ttxthat could be an interesting exercise.21:15
notmynameheh. I'll be travelling too21:16
notmynamethe 10th then?21:16
ttx#action ttx to set Swift 1.4.6 tentative date to Feb 13.21:16
*** liemmn has quit IRC21:16
ttxnotmyname: release on the 10th means... freezing for your QA a bit earlier. Would that work ?21:17
notmynameI'd expect to have our QA sign off by friday the 10th either way. it's just a matter of coordinating our different time zones (end of day here is awfully late for you)21:17
*** salv-orlando_ has joined #openstack-meeting21:18
ttxLet's put a tentative date on the 10th, and see what we can do to hit that. Worst case scenario someone else will release it early the next week21:18
notmynameok, sounds good to me21:18
ttx#action ttx to set Swift 1.4.6 tentative date to Feb 10 (!)21:18
ttxnotmyname: Anything else ?21:19
notmynameI'm almost done with object versions21:19
notmynameI hope to have that in 1.4.6 (we'll see how code review goes)21:19
ttxQuestions on Swift ?21:19
notmynamenothing else code related. just marketing stuff (conferences and meetups and stuff)21:19
notmynameoh. the feb 2 bug fix day21:20
* jaypipes will be in Austin21:20
notmynameswift will be "officially unofficially" participating in the feb 2 bug squash day21:20
ttxI'll be i nBrussels21:20
annegentlethere will be tacos21:20
jaypipesnotmyname: I like that :) officially unofficially21:21
ttxnotmyname: great.21:21
*** cthiel_ has joined #openstack-meeting21:21
notmynamein other words, we'll be around online (and we've already had one company ask to participate for swift), but we won't be actively promoting our own bug squash day at this time21:21
notmynameI'm doing what I can to make sure that we have a rapid turn around on reviews on feb 221:21
ttxnotmyname: no specific objective for the bug squashing day on your side ?21:21
notmynameby core devs21:21
notmynamewell, less bugs is better ;-)21:22
ttx#topic Glance status21:22
*** openstack changes topic to "Glance status"21:22
ttxjaypipes: yo21:22
ttx#link https://launchpad.net/glance/+milestone/essex-321:22
ttxIs interim-glance-authz-service complete ? Or more to come ?21:22
ttx(convenience link: https://blueprints.launchpad.net/glance/+spec/interim-glance-authz-service)21:22
jaypipesneeded documentation. currently in review: https://review.openstack.org/337021:23
*** liemmn__ has joined #openstack-meeting21:23
jaypipesttx: that is the ONLY outstanding E3 item. other than that, we're ready to ship.21:23
bcwaldonand that *will* be in today21:23
ttx5 targeted bugs -- none actually blocking E3 ?21:23
Vekttx: refresh?  I only see 2 bugs21:24
Vek(all others fix-committed)21:24
jaypipesttx: you always fail to remember to refresh :P21:24
ttxtwo incomplete bugs... what should I do with them ?21:24
* ttx makes mental note not to fall into that refresh trap ever again21:24
*** liemmn__ has quit IRC21:25
jaypipesttx: meh... feel free to push to E4 for both. not a big deal..21:25
ttxok, will do if they are not fixed tonight.21:25
ttxjaypipes: Anything else ?21:25
jaypipesttx: no, they won't be.21:25
jaypipesttx: feel free to move.21:25
ttxso I move them21:25
jaypipesttx: nope, no other news from me.21:25
ttxQuestions on Glance ?21:25
ttx#topic Nova status21:26
*** openstack changes topic to "Nova status"21:26
ttxvishy: hey21:26
*** liemmn_ has quit IRC21:26
ttx#link https://launchpad.net/nova/+milestone/essex-321:26
vishywe're looking very good21:26
ttxLet's review incomplete stuff:21:26
vishya few branches are being reviewed today21:27
ttxAlmost there:21:27
ttx* https://blueprints.launchpad.net/nova/+spec/x509-cert-crud (vishy)21:27
ttx* https://blueprints.launchpad.net/nova/+spec/apache-qpid-rpc (russellb)21:27
ttxCould make it in:21:27
*** _adjohn has joined #openstack-meeting21:27
ttx* https://blueprints.launchpad.net/nova/+spec/host-aggregates (armando)21:27
ttx* https://blueprints.launchpad.net/nova/+spec/separate-nova-adminapi (bcwaldon)21:27
ttx* https://blueprints.launchpad.net/nova/+spec/scaling-zones (comstud)21:27
ttx* https://blueprints.launchpad.net/nova/+spec/public-and-private-dns (andrew)21:28
bcwaldonttx: marked separate-nova-adminapi complete21:28
russellbapache-qpid-rpc is done and reviewed, should be in shortly21:28
vishyhttps://blueprints.launchpad.net/nova/+spec/separate-nova-adminapi  and https://blueprints.launchpad.net/nova/+spec/public-and-private-dns  are done21:28
ttxbcwaldon: cool.21:28
vishyand marked21:28
*** troytoman-away is now known as troytoman21:28
ttxhost-aggregates and scaling-zones might fall a bit short21:28
vishyscaling-zones is not going to make it21:28
vishyhost-aggregates might21:28
vishythe others should make it21:29
ttxand the remaining 7 clearly won't make it. Are you considering any for E4 ?21:29
armandomifor host-aggregates, we got a bunch of reviews in the queue21:29
ewanmellorCitrix has four host-aggregates reviews on Gerrit right now.  Would appreciate some reviews!21:29
ttxvishy: which ones ?21:29
ewindischI'm still working on the 0mq stuff. Passes unit tests, doesn't pass smoketests yet... the patch would only create a new driver and service, it wouldn't touch any existing code and wouldn't be enabled by default.21:29
ewanmellorOh, hey Armando ;-)21:29
vishyarmandomi: I'm trying to get some reviewers21:29
vishythere are 3 branches needed21:29
armandomiwe are nearly there, we still have some bits missing21:29
*** adjohn has quit IRC21:29
*** _adjohn is now known as adjohn21:29
bcwaldonvishy: I'll review shortly21:29
armandomibut it'd be great if we could get at least the OSAPI extensions in21:29
armandomiso that the rest could be filed as bug fixes21:30
vishyI'm considering ff exceptions for zeromq and solidfire driver21:30
pvoewanmellor: we're lining up to review.21:30
*** mcohen has left #openstack-meeting21:30
ewanmellorpvo: Thanks21:30
vishyas neither one needs to touch core code21:30
ttxvishy: any signs that those will be worked on ?21:30
armandomithere is also bug #921087 that makes sense for host aggregates21:31
uvirtbotLaunchpad bug 921087 in nova "i18n-key and local-storage hard-coded in xenapi" [Undecided,Confirmed] https://launchpad.net/bugs/92108721:31
vishyso volume type scheduler going to defer21:31
ttxvishy: which one is solidfire ?21:31
vishyalso think an ffe for kvm-resize is useful21:31
armandomiI have got a fix, file it later, tomorrow morning at latest21:31
ewanmellorWe also have a review outstanding for https://blueprints.launchpad.net/nova/+spec/xenapi-provider-firewall.  That's ready to go in if it can get reviewed in time.21:31
vishyit just implements an unimplemented feature in libvirt driver21:31
ttxvishy: no bp for that one yet, right ?21:32
vishyewanmellor: review link?  it isn't connected to the bp21:32
ewindischttx: I'm committed to having the zeromq working and making good progress.21:32
vishyttx: which the kvm-resize?21:32
bcwaldonvishy: is there a formal process for requesting feature-freeze exceptions?21:32
ewanmellorvishy: https://review.openstack.org/#change,320721:32
vishyadded to review list21:32
ttxvishy: yes21:33
vishyttx: I think there is one21:33
ewanmellor(Isn't Gerrit supposed to add those links automatically?  The blueprint name is in the title)21:33
vishyttx: maybe it didn't get targetted21:33
ttxvishy: ideally you would mark "Deferred" the ones that go to F and target to E4 the ones that get a FFe21:33
vishyewanmellor: it needs to be in the form "blueprint xxxx"21:33
vishyas opposed to bp/xxxx21:33
ewanmellorvishy: Oh, bummer.21:34
ttxvishy: so, unless you send me an IRC message or email, I'll cut milestone-proposed with what's in tonight21:34
vishyssl is fine in e421:35
*** dabo has quit IRC21:35
*** spectorclan has quit IRC21:35
ttxvishy: does that work for you ?21:35
vishyas well as testing cleanup21:35
vishyttx: yes21:35
vishyso i will move those21:35
ttxOn the bugs side, 5 targeted bugs...21:35
ttxBug 917397 needs some review love at https://review.openstack.org/#change,324521:35
uvirtbotLaunchpad bug 917397 in nova "Quantum Manager configuration sanity checks" [Medium,In progress] https://launchpad.net/bugs/91739721:35
ttxThose two that may already be solved:21:35
vishyusnure about openvz and illumos21:35
ttx* https://bugs.launchpad.net/nova/+bug/885265 (bhall)21:35
uvirtbotLaunchpad bug 885265 in nova "quantum 420 error leaves instance in BUILD state" [Medium,In progress]21:35
ttx* https://bugs.launchpad.net/nova/+bug/917457 (sleepsonthefloor)21:35
uvirtbotLaunchpad bug 917457 in nova "Openstackx broken since nova api refactor" [High,Confirmed]21:35
vishyi think we might just wait on those until f opens21:35
ttxvishy: agreed21:36
*** ewindisch_ has joined #openstack-meeting21:36
ttxAnything left to do on those two bugs ^^ ?21:36
bhallttx: we moved 885265 out21:36
ttxit's a bit unclear from their status21:36
bhallanyone else is welcome to grab it but I don't think we have time for it for this release21:36
ttxbhall: out of... E3 ?21:36
bhallttx: yup21:36
*** mjfork has joined #openstack-meeting21:37
ttxok, moving on nova side as well, then21:37
Vekany word on how quick quantum will be refactored to nuke those non-standard responses?21:37
bhallthank you21:37
ttxwhat about bug 917457 ? Anything left to do on nova's side for this one ?21:37
uvirtbotLaunchpad bug 917457 in nova "Openstackx broken since nova api refactor" [High,Confirmed] https://launchpad.net/bugs/91745721:37
danwentVek: in review21:37
danwentbut will be only for API v1.121:37
Vekdanwent: cool :)21:37
*** dabo has joined #openstack-meeting21:37
Vekgot it.21:37
danwentsince we don't want to change error codes and surprise clients21:37
* Vek nods21:38
vishyttx: we are in process of removing openstackx21:38
vishyi wil check status21:38
ttxvishy: is this bug blocking E3 ?21:38
*** spectorclan has joined #openstack-meeting21:38
ttxFinally, those last two don't have an assignee -- should we try to get them in as well:21:39
ttx* https://bugs.launchpad.net/bugs/91441821:39
ttx* https://bugs.launchpad.net/nova/+bug/91785121:39
uvirtbotLaunchpad bug 914418 in nova "Nova notifications now seem to be using the default rabbit exchange " [High,Confirmed]21:39
uvirtbotLaunchpad bug 917851 in nova "replace m2crypto with shelling to openssl" [Wishlist,Confirmed]21:39
*** mcohen has joined #openstack-meeting21:40
dragondmI've looked a bit into lp91441821:40
ttxI think the M2Cryptoectomy can wait for post-E321:40
vishyttx: I don't think so21:41
vishym2crypto can be e421:41
vishythe first one i haven't seen before21:41
russellbdragondm: is it still broken?  looks right to me ...21:41
ttxvishy: ok, let's keep those last two in E3 scope for the moment21:42
dragondmI'm currently doing a workaround for a related system for the default exchange bug, so I haven't looked at the novaissue in a day or 221:42
ttxAnything missing from that list that should be blocking E3 ?21:42
ttxdragondm: can we assign you to this bug for the time being ?21:42
dragondmya sure.21:42
ttxdragondm: thx, keep us posted.21:43
ttxvishy: Anything else ?21:43
ttxvishy: if you have other E3-critical bugs, be sure to add them to the E3 list21:43
vishyttx: nope.21:43
ttxQuestions on Nova ?21:44
vishygood luck reviewing everyone21:44
oleg__can I hope to target this to e-4: https://blueprints.launchpad.net/nova/+spec/nexenta-volume-driver ?21:44
oleg__we have diablo version code, it is 2 week effort to update it for essex21:44
vishyoleg__: I will consider Feature Freeze exceptions for drivers that don't touch the core code21:44
ttxvishy: we could require a ML thread for every FFe request... so that we can have a public discussion on whether the benefit outweighs the risk21:45
vishybut it needs to get in early in e421:45
oleg__vishy: good to hear21:45
vishyor else you will have to ship it separately until F21:45
oleg__what we have to do21:45
ttxdevcamcar: around now ?21:45
vishyttx: sounds good21:45
oleg__to make it into e4 ?21:45
ttx#topic Horizon status21:45
*** openstack changes topic to "Horizon status"21:45
vishyoleg__: please make a request to the mailing list so it can be discussed in public21:45
*** novas0x2a|lapto1 has joined #openstack-meeting21:45
ttx#link https://launchpad.net/horizon/+milestone/essex-321:46
oleg__fine, thank you21:46
ttxOnly one blueprint missing:21:46
ttxhttps://blueprints.launchpad.net/horizon/+spec/novaclient-migration (sleepsonthefloor)21:46
ttxdevcamcar: What's the status on this one ?21:46
devcamcaryea - and that is very very close to being done (jf not already)21:46
devcamcarthat will land today21:46
ttxok, so it should be done today.21:46
*** anotherjesse has quit IRC21:46
*** novas0x2a|laptop has quit IRC21:47
ttxand we should be ready to cut.21:47
ttxYou also have 8 targeted bugs...21:47
ttxAre they all blocking E3 ?21:47
devcamcaryep! we are looking good21:47
devcamcarthere is only one critical bug at this time21:47
devcamcarthat should land today as well21:47
devcamcarwe have may to back port from trunk to milestone-proposed a few over the next few days21:47
devcamcarer, well, tomorrow :)21:47
ttxdevcamcar: ideally after today you should refine the list so that it only contains candidates for milestone-proposed backporting21:47
devcamcarwill do21:48
devcamcari expect most of these to land today or tomorro21:48
ttx(the idea being to use that as a dashboard of work left to do before E3 delivery)à21:48
ttxdevcamcar: Anything else ?21:48
devcamcarthat is all21:48
ttxQuestions for Horizon ?21:49
ttx#topic Incubated projects and other Team reports21:49
*** openstack changes topic to "Incubated projects and other Team reports"21:49
ttxdanwent, troytoman: yo21:49
danwenthello :)21:49
ttxA quick reminder of how milestone-proposed works...21:49
ttxEarly tomorrow I'll cut a milestone-proposed branch off master21:50
ttxThat branch can still get urgent milestone-blocking bugfixes, but no more features or gratuitous changes21:50
troytomansounds good21:50
ttxYou have to push bugfixes to the master branch first, and propose a backport of the fix to milestone-proposed21:50
ttxSo, let's have a look at Quantum first21:50
*** jlm^ has joined #openstack-meeting21:50
ttxdanwent: Is the status accurate ?21:50
danwentbit of a log-jam in reviewing21:50
danwentone or more of the features won't make it21:51
ttxCan I cut the milestone-proposed branch in 10 hours with what will be in there ?21:51
* mtaylor is causing problems for quantum21:51
danwentwe're trying to get the repo split.  that should be done21:51
Vekjust do to the need for reviews?21:51
ttxdanwent: good.21:51
danwentvek: an general stability21:51
ttxdanwent: anything else ?21:51
danwentan -> and21:51
ttxOK, Melange now...21:51
troytomanwe've gotten the client separated out21:52
troytomanprimarily focused on vetting integration with nova/quantum21:52
troytomani think we're good for the milestone release21:52
ttxtroytoman: so that one can be marked completed ?21:52
ttx*or both ?21:52
troytomani believe so21:52
troytomani'll double check that the reviews finished21:52
ttx"improve scalability" is rather open-ended :)21:53
troytomansorry, will clarify that but it will push out to e4.21:53
ttxtroytoman: ok, will cut branch with what's in tomorrow, unless you tell me otherwise21:53
troytomani decided it was too disruptive to push in this window21:53
troytomansounds good.21:53
ttxok, so client split -> done, scalability -> e4 ?21:53
troytomanttx: yes. i'll update launchpad on scalability21:54
ttxwill mark client split done21:54
ttxtroytoman: other remarks ?21:54
troytomanttx: no21:54
*** edgarmagana has joined #openstack-meeting21:54
ttxAny other team lead with a status report ?21:55
*** _adjohn has joined #openstack-meeting21:55
ttxmtaylor: ^ ?21:55
mtaylorttx: ?21:55
annegentleThe ginormous install guide is here: https://review.openstack.org/#change,330121:55
mtaylorttx: code review auto-expiration went live last night21:56
annegentleAlso making headway on the API reference site.21:56
mtaylorttx: hoping to get some tox-based unittest stuff rolled out this week21:56
Vekmtaylor: so I noticed :)21:56
mtaylorttx: python-quantumclient currently is using tox - so we've got a test case/example project21:56
*** adjohn has quit IRC21:57
*** _adjohn is now known as adjohn21:57
mtayloralso, LinuxJedi is going to solve all of our remaining problems this weekj21:57
ttxmtaylor: python-quantumclient ? Do you have a tarball job for that ?21:57
* ttx didn't plan to release quantumclient as part of E3421:58
Vekthat would be quite a release cycle, if we were going all the way to E3421:58
LinuxJedilol! :)21:59
ttx#topic Open discussion21:59
*** openstack changes topic to "Open discussion"21:59
danwentI think mtaylor is coding it up right now so he can say yes :)21:59
ttxAnything else, anyone ?21:59
ttxdanwent: a bit late to include it in my process... We can make a quantumclient tarball release for E4 -- would that work ?22:00
mtaylorttx: working on the split - it'll be like keystoneclient/novaclient - part of quantum project22:00
danwentmtaylor, ttx, let's chat after meeting22:00
mtaylordanwent: ++22:00
zule3 is friday isnt it?22:00
ttxdanwent: if I'm still around :)22:00
ttxzul: e3 is thursday.22:01
ttxRule #4 of release management is don't release on a Friday.22:01
danwentttx, i meant right now, but you can close main meeting first22:01
Vekhehe :)22:01
ttxdanwent: sure22:01
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"22:01
openstackMeeting ended Tue Jan 24 22:01:49 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-24-21.01.html22:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-24-21.01.txt22:01
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-24-21.01.log.html22:01
*** lzyeval has quit IRC22:02
*** armandomi has quit IRC22:02
openstackMeeting started Tue Jan 24 22:02:01 2012 UTC.  The chair is danwent. Information about MeetBot at http://wiki.debian.org/MeetBot.22:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.22:02
*** Vek has left #openstack-meeting22:02
danwentok, netstack meeting'22:02
davlaphi folks!22:02
edgarmaganaHi Folks!22:02
danwentagenda: http://wiki.openstack.org/Network/Meetings22:02
somikhi folks!22:02
ttxdanwent: make that your first item :)22:02
danwentfirst topic is talking with ttx + monty22:02
mestery_'sup guys!22:02
danwentttx: already one… see agenda :)22:02
*** debo-os has joined #openstack-meeting22:02
*** zns has quit IRC22:02
*** russellb has left #openstack-meeting22:02
ttxdanwent: damn, you're fast22:02
cdubheh, convenient22:02
danwentOk, problem is that there is no automated tarball job for python-quantumclient22:03
danwentso its hard to release it for E-3?22:03
ttxdanwent: it's also that I didn't plan to have quantumclient /melangeclient done for E3, tbh22:03
danwentI really wanted to get it into E-3, so we could make sure distro packagers had time to adjust22:03
ttxdanwent: ok, let's see what we can do22:03
*** joesavak has quit IRC22:04
ttxmtaylor: what's the status ? repo is up ?22:04
danwentttx: ok.  don't want to cause more work for you.  is this just a matter of mtaylor writing a script?22:04
danwentttx: yes, repo is up22:04
*** dolphm has joined #openstack-meeting22:04
ttxmtaylor: I'd need the repo set up, and tarball jobs for master and milestone-proposed... today22:04
danwentoops, just kidding22:04
danwentcode is at: https://github.com/openstack/python-quantumclient22:04
mtaylorand it's in gerrit, etc22:04
danwentbut ttx, you're talking about a different repo?22:04
ttxif not, we can do an out-of-band quantumclient/E3 thing22:05
ttxdanwent: no, that one22:05
danwentok, i'll stop talking :)22:05
*** SumitNaiksatam has joined #openstack-meeting22:05
mtaylorttx: I think we should be able to get tarball job up asap - quantumclient is using the same version setting code as quantum and others22:05
mtaylorttx: I didn't set one up already because I wasn't sure if we should yet22:06
ttxmtaylor: if the tarball job is up, I'll pick up quantumclient as part of the E3 regular process22:06
ttxstarting tomorrow morning22:06
danwentmtaylor, can you give you the TODO?22:06
ttxif not, we can upload a tarball for E3 out of band22:06
danwentor rather, can I give you the TODO :)22:06
ttxso that packagers are happy to play22:06
danwent(too many late nights recently)22:07
danwentthanks ttx22:07
ttxdanwent: would that work for you ?22:07
danwentappreciate it22:07
ttxok, deal.22:07
*** mperez has quit IRC22:07
danwent#TODO #mtaylor try to setup a tarball job for python-quantumclient22:07
*** zigo has quit IRC22:08
danwentI'll just assume mtaylor is off working on it already :)22:08
danwentthanks mtaylor22:08
* mtaylor is eating a sandwich, but yeah22:08
danwenthere are the open reviews.22:09
danwentwith respect to python-quantumclient, we still need to approve the change-set to split out the client code.22:09
danwentsalv, I believe you had some input on how exceptions are handled?22:09
* mtaylor is working on that one22:09
mtaylornot the exceptions - waiting for salv feedback on exception22:10
salv-orlando_feedback is on the review page22:10
danwentright now, we get away with not duplicating, because server depends on client, but its a bit odd that some server-only exceptions are included in the client.22:10
danwentso can I take that as saying you're fine with the exceptions as is, for now?22:11
salv-orlando_I think we can easily keep this odd thing and proceed with the split, as long as we file a bug for tidying up exceptions22:11
salv-orlando_well, not really as it is on the changeset, as it is going to be deleted from the server package...22:11
salv-orlando_are we creating a repository for quantum.common as well?22:12
danwentok, sounds good.  such a large change makes me nervous, so i'd lke to get it in ASAP.  I think there's a fair amount of testing that still needs to be done around packaging with the split.22:12
danwentI think mtaylors approach was to take things that might go in a "common" and put them in "client".22:12
danwentas the server depends on "client", and thus pulls the "common" code in.22:13
danwentis that right mtaylor?22:13
*** andrewsben has quit IRC22:13
danwentapparently he's still eating his sandwich :)22:13
salv-orlando_In that case we will probably need exceptions to stay in the server repository, too. Otherwise Quantum API would be unable to raise faults, I'm afraid.22:13
danwentno, it works correctly, i believe22:14
danwentthe exceptions code is available to the server, because the server depends on the client.22:14
salv-orlando_ah... that's the bit I was missing :)22:14
*** ryu_ishimoto_ has joined #openstack-meeting22:14
danwentyeah… took me a while as well :)22:14
salv-orlando_In that case we should be all right22:15
danwentOk, I still think we need to do a fair amount of testing + reviewing with this patch.22:15
cduband do we expect client -> common to happen before E4?22:15
danwentcdub: I don't think we'll create a common22:15
cdubor F+22:15
cdubdanwent: ever?22:15
danwentwe may rework the exception code a bit so that there is no longer any "common"22:15
danwentwhich would probably be less confusing22:16
danwentcdub: that is my guess.  long-term, both packages should be able to depend on something like openstack-common.22:16
danwentI don't think nova + novaclient have a shared library22:16
cdubdanwent: right, ultimately we'd like to be able to install server and client separately (not on same box)22:16
mtaylordanwent: yes. sorry - multi-tasking kills me22:16
danwentor most of the other openstack projects.22:16
danwentcdub: you can do that already22:16
danwentyou can install and run client with independently22:17
danwentno need for server.22:17
danwentits just that when you install the server, you have to install the client as well.22:17
cdubwith server needing excpetion code provided by client?22:17
danwentwhich you probably want for testing as well.22:17
salv-orlando_mtaylor: danwent clarified that actually quantum-server will depend on quantum-client. I was afraid the exceptions module was not anymore available to the server. In this case, we can go ahead with the merge.22:17
danwentThat's the part we'd like to clean up, but its more of a style thing that a correctness thing.22:17
*** bcwaldon has left #openstack-meeting22:18
danwentsalv-orlando: OK, there are other things that need to be fixed in the patchset, but we will note that you have withdrawn your concern about the exceptions.22:18
mtaylorsalv-orlando_: ok. cool.22:18
danwentcdub: can you explain your concern in more detail?  or comment on the review?22:18
mtayloryes - need to sort the namespace pacakge issue22:18
mtaylorwhich means we need to land a patch in horizon, right?22:19
danwentdave, can you comments?22:19
davlapmtaylor: so there's a pip requires we need to add to horizon22:19
davlapand also need to make a mod to devstack.sh22:19
davlapsorry.. stack.sh22:19
danwentdavlap: is horizon change required, or just suggested?22:20
mtaylordavlap: cool. also, you were pointing to my old emonty repo and not the openstack repo22:20
davlapstack.sh was creating fake quantum/client module in its tree which was imported before the client..22:20
danwentwasn't clear on that22:20
davlapwe need horizon change to capture the dep for installation of horizon22:20
davlapok.. great.. i'll take a look at the new one..22:20
danwentdavlap: ok.  its the right change anyway.22:20
cdubdanwent: sure, i'll comment in review, shouldn't effect merge ;)22:20
mtaylorshould we poke heckj or someone about the horizon thing?22:21
danwentmtaylor: i already pinged devmancar and you in an email.22:21
mtayloroh hey! there it is22:21
danwentlooping in heckj would be good22:21
heckjI'm here and officially loopy22:21
mtaylorheckj: we have a quantum.client package now, so we want horizon to use it22:21
*** novas0x2a|lapto1 has quit IRC22:22
mtaylorheckj: -e git+https://review.openstack.org/p/openstack/python-quantumclient#egg=python-quantumclient-dev22:22
*** cthiel_ has left #openstack-meeting22:22
heckjsounds good - pretty much a straight up deps change I think. Is it pushed to pypi now? (i.e. easy to get) or do we have to wrangle a git based PIP install for it?22:22
heckjgit, eh?22:22
heckjdan - same API setup, or are there code changes to use this that will be needed as well?22:23
danwentheckj: should just be a dependency issue22:24
danwentthere is stuff broken with horizon + quantum, but that's another discussion (for another day, but hopefully soon!)22:24
danwentthis dep change should get us to status quo22:24
debo-osdanwent: :)22:24
debo-osI guess you meant creating networks etc22:25
danwentdebo-os: yeah, and integration with IPAM.22:25
danwentessentially what we talked about at Essex summit22:25
danwentok, heckj, does that sound reasonablee?22:26
heckjdanwent: quite. I was just getting the latest code to make that change right now, see that it worked OK.22:26
danwentok, thanks.  definitely ping us if you see problems.  we will test it all with devstack as well once it is in.22:26
danwentok, so my final question with the repo split stuff is whether people have been testing generating packages from the repos.22:27
*** GheRivero_ has quit IRC22:27
mtaylordanwent: _hopefully_ zul and friends will start building us offical debs of these bad boys, right zul?22:27
zulof what?22:28
danwentmtaylor: yes, but some people build packages themselves with the setup scripts, so I want to make sure everything's happy before we drop E-322:28
*** ewanmellor has quit IRC22:28
danwentjust want to make sure we're safe before we approve :)22:29
danwentzul: quantum and python-quantumclient22:29
heckjdanwent: I've seen some packages generated from the managedIT guys too22:29
zuldanwent: quantum is already packaged in ubuntu/debian python-quantumclient not so much22:29
* heckj is currently stealing zul's hard work there22:29
mtaylorzul: it's just a split of the client libs from the quantum core22:30
zulheckj: meh :)22:30
mtaylorzul: you can blame me for that one22:30
*** novas0x2a|laptop has joined #openstack-meeting22:30
heckjhow very…. articulate!22:31
danwentOk…. so are we good talking about the client repo split?22:31
danwentanything else to bring up?  This is a pretty big change, so we'll need everyone to pitch in on testing.22:31
danwentthanks for your help mtaylor, heckj, zul22:32
danwentOk, next up:  API patches22:32
ohnoimdeaddanwent: any idea on when the horizon + quantum discussion can happen? :)22:32
mtaylorthanks everybody!22:32
danwentohnoimdead: definitely want to chat22:32
danwentperhaps late this week?22:32
ohnoimdeadcool cuz we'd like to get that stuff working again22:32
danwentonce we get E-3 under controller22:32
danwentsweet, I would too :)22:33
danwentohnoimdead: please ping netstack list.22:33
ohnoimdeaddoing now22:33
danwentOk, salv-orlando?22:33
danwentprobably asleep from coding all night22:34
salv-orlando_not yet22:34
salv-orlando_a possibly final changeset for api-error-codes has been pushed22:34
danwentok, so its pretty late and we have the repo split… minimizing other churn at this point is good.22:35
danwentthe filters seem like the most important other thing, as we want nova to start using the filters in E-4, if possible.22:35
danwenterror-codes is about good to go though, right?22:35
salv-orlando_I'm happy with deferring pagination.22:35
salv-orlando_error-codes is good to go. Feedback has been addressed.22:36
salv-orlando_For api-filters it seems that we managed to agree on the plugin behaviour.22:36
danwentok, so let's try to get people to review error codes.22:36
danwentshould be a quick re-review22:36
salv-orlando_Summarizing: a plugin might or might not implement the filters. For the filters it does not implement, the API layer would perform the filtering.22:36
salv-orlando_This keeps the code in the API layer pretty simple and gives client a consistent experience.22:37
danwentfilters is more complex.  Do we have two core reveiwers on that yet (I think it was just Aaron and I, last I checked)22:37
salv-orlando_Yes, just the two of you. A contribution from somebody knowledgeable with the UCS plugin would be greast.22:37
edgarmaganadan: I take it22:38
danwentthis is mostly already reviewed, so it shouldn't be too bad.22:38
salv-orlando_edgarmagana: thanks!22:38
SumitNaiksatamyeah, I am looking at it too22:38
edgarmaganaI already reviewed but I was not sure about the plugin implementing or not the filters22:38
salv-orlando_cool. So I will be able to address previous feedback in the next hour or so.22:39
danwentah, sorry, missed that edgar22:39
danwentsalv: hope you can stay up that late… we're all running on fumes :)22:39
danwentok, and so we'll defer the pagination?  I think that's a good call.22:39
salv-orlando_I have plenty of coffee22:39
salv-orlando_and in case I should run out there's a supermarket open 24/7 near my home22:40
danwentok, so we also have reviews for linux-bridge plugin and ryu controller plugin.22:40
danwentryu we've already decided to bump.  i personally think its pretty late to squeeze in linux-bridge given all the churn.22:40
danwentsumit: is there a problem with just doing this first thing in e-4?22:41
debo-osfolks,  for the new plugins: it would be good to try with devstack22:41
*** ewindisch has quit IRC22:41
*** ewindisch_ is now known as ewindisch22:41
danwentdebo-os: yes, we'll definitely want to do full system testing for new plugins.22:41
debo-osdanwent: cool22:42
danwent(ideally with your new system test framework :)22:42
SumitNaiksatamyeah, I am fine22:42
SumitNaiksatamwe have one review from edgar22:42
edgarmaganadan: I have an end-to-end testbed with devstack and the linux-bridge code, It is working very well so far!22:42
danwentOk.  but it will be important that we don't let this go to late in E-422:42
SumitNaiksatamneed one more for the linux bridge22:42
cdubi think risk is low22:42
debo-osedgar: did you get it automated in devstack.sh22:43
cdubfor linux-bridge e3, since it's a plug in22:43
debo-osI can do the 2nd one22:43
danwentSumit: yeah, with a big chunk of new code, we definitely want to review it carefully.22:43
edgarmaganadebo: no, i had to do some manual confguration22:43
danwentis there a big deal if we just do it next week?22:43
danwentwe're really overloaded already with code to review + test22:43
debo-osedgar: by devstack we meant push button ... spec linuxbridge in the localrc and voila22:44
danwentI'd much rather have those cycles go to making sure e-3 is not busted22:44
cdubprobably not, considering we'll probably going to spend more time w/ packaging anyway22:44
edgarmaganadebo: we need to modify the script and i am not working on that22:44
rkukuralinux-bridge would allow end-to-end testing of packages on fedora 16, which doesn't have OVS yet22:44
danwentcdub: that would be my preference.  we've already had a couple late nights22:44
edgarmaganadebo: I just wanted to have a full functional end-to-end testbed with two or more cloud computes22:45
cdubyeah, it's a balance between testable (no ovs in fedora) and testable (busted)22:45
danwentrkukura: definitely can get this in E-422:45
danwentis e-3 important in particular?22:45
debo-osedgar: understand ... but we would want to get it automated soon22:46
debo-osthats why danwent mentioned the test framework22:46
cdubrkukura: when's fedora OS testday?  before E4?22:46
danwentdebo-os: you want to get this working in devstack, then testing it should be easy.22:46
*** dolphm has quit IRC22:46
debo-osdanwent: +!22:47
cdubrkukura: oh, not until march822:47
danwentOk, so next week is reasonable?22:47
rkukuracould update packages to git snapshot after E322:47
danwentOk, that way salv and I can review as well.  which I would prefer.  we're both out of cycles for e-322:48
*** hggdh has quit IRC22:48
* cdub will give it proper review as well, and could use the extra time too22:49
danwentdebo, we could make testing this be part of the bug-squashing system test day as well22:49
danwentthat is Feb 2nd.  would be cool if we coudl do some testing on RHEL22:49
danwentok, sounds good.22:50
*** Gordonz has quit IRC22:50
danwentwanted to talk about system test more general, but debo-os said he has to bail (meeting is running long)22:50
debo-osdanwent: sure22:51
danwent#TODO: #debo-os will update system test BP with info about his tempest work.22:51
danwentreminder: we are hosting bug-squashing day @ Nicira on Feb 2nd.22:51
danwentwill send out an invite with details after the release madness, but expect afternoon and early evening.22:51
danwentemphasis will be on code quality + system test.  Debo will hopefully be giving an overview of using devstack with quantum, and using tempest to create interesting test environments.22:52
edgarmaganafree pizza?22:52
danwentyou bet :)22:52
*** hggdh has joined #openstack-meeting22:52
edgarmaganaand beers?22:52
danwentmaybe even free beer22:52
danwentok, any open discussion?22:53
debo-osdanwent: +1 for beer and devstack+quantum test env22:53
danwentbefore we end this marathon meeting and get back to testing + reviewing22:53
danwentOk, thanks folks.  Please keep an eye on the netstack list in case critical bugs pop-up.22:54
carlpdanwent: you know there is an OpenStack meetup in SF that day as well?22:54
danwentcarlp: yes22:54
carlpdanwent: OK, just checking :)22:54
danwentenough people voiced a desire for closer location22:54
danwentyou know us bay area folks are so environmentally friends (or lazy)22:55
carlpFair enough22:55
danwentok, later folks!22:55
salv-orlando_or the US-101 is alway so packed with traffic...22:55
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"22:55
salv-orlando_hasta la vista!22:55
openstackMeeting ended Tue Jan 24 22:55:24 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-24-22.02.html22:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-24-22.02.txt22:55
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-24-22.02.log.html22:55
danwentare you going to be on IRC while coding tonight?22:55
danwentI might need to bounce something quickly off of your for your patch22:56
salv-orlando_my IRC window will be open22:56
*** ryu_ishimoto_ has quit IRC22:57
*** lloydde has quit IRC22:57
salv-orlando_I'll be up for the next 3-4 hours22:57
mtaylordanwent: quick ?22:57
mtaylordanwent: curerntly the quantum setup.py lists install_requires ... in general, we've been moving to a model/thought that servers will probably never be installed from pip so don't need those (but _clients_ certainly will, so they're really important there)22:58
mtaylordanwent: do you have any strong objections to me removing those bits in the split patch as well?22:58
*** debo-os has quit IRC22:59
*** markvoelker has quit IRC22:59
*** jlm^ has left #openstack-meeting23:00
danwentmtaylor: i know a fair number of people build their own packages, so I'm fairly hesistent to doing this right before a release.23:01
*** _adjohn has joined #openstack-meeting23:01
mtaylordanwent: ok.23:01
danwenthow about doing it once E-3 is out, so people have some time to react if it breaks?23:01
danwentthere's a couple people I should check with first, at the last23:02
danwentlast -> least23:02
mtaylordanwent: works for me - biggest concern I want to address is that install_requires needs to reference python-quantumclient now23:02
mtaylorbut we don't have a pypi package for it yet23:02
mtaylorI was thinking a workaround for now would be to release a 0.1 python-quantumclient package to pypi by hand23:02
mtaylorof the state of the current client tree - that way quantum install_requires will work ... and moving forward we can solve it for real23:03
danwentcould we instead just direct people to install python-quantuclient from egg manually first?23:03
*** adjohn has quit IRC23:03
*** _adjohn is now known as adjohn23:03
heckjI have the pull request up in review time now for the python-quantumclient in horizon: https://review.openstack.org/337523:03
mtayloryes. I would love that23:03
danwentmtaylor: was that comment to me or heckj?23:03
heckjdanwent - you, I think23:03
*** ayoung has quit IRC23:04
*** sleepsonthefloo has quit IRC23:04
*** sleepsonthefloo has joined #openstack-meeting23:05
*** mattray has quit IRC23:06
danwentheckj: thanks for taking care of that so quickly.23:06
*** rnirmal has quit IRC23:07
heckjyou made it easy with a drop-in replacement!23:08
*** ewindisch_ has joined #openstack-meeting23:08
*** hggdh has quit IRC23:09
*** dendrobates is now known as dendro-afk23:11
*** martine has quit IRC23:12
*** hggdh has joined #openstack-meeting23:13
*** pvo has left #openstack-meeting23:13
*** pvo has joined #openstack-meeting23:13
danwentheckj: noticed the additional of python-gflags.  is that needed by python-quantumclient?23:13
danwentif so, I would have expected that to be in its pip-requires23:14
heckjyeah - it appears so23:14
heckjthe tests don't pass when I make that switch until I add in python-gflags23:14
danwenthuh, weird, as it is in pip-requires for python-quantumclient23:16
danwenti guess it doesn't hurt to have it there as well, just odd23:16
mtaylorit shoudl be in python-quantumclient's install_requires23:18
mtaylorheckj, danwent: ^^23:19
mtaylorpip-requires is not processed by installation by other things23:19
danwentah, you were installing, not running from source.  yeah, makes sense.  I still don't totally get a lof of this packaging stuff :)23:20
danwentso that is something we should fix?23:20
mtaylordanwent: we should make a patch that removes things from python-quantumclient's pip-requires that are not needed by python-quantumclient - and in the same patch probably _add_ the things in the top section of the pip-requires to the requires [] in setup.py23:20
danwentmtaylor: yes, was just about to contact you about that...23:21
danwentmtaylor: i can take a shot at this.23:22
mtaylordanwent: awesome.23:22
*** rkukura has quit IRC23:23
*** wwkeyboard has left #openstack-meeting23:25
*** SumitNaiksatam has quit IRC23:31
*** danwent has quit IRC23:46
*** bhall has quit IRC23:46
*** ravi has quit IRC23:47
*** adjohn has quit IRC23:47
*** adjohn has joined #openstack-meeting23:47
*** mcohen has left #openstack-meeting23:48
*** lxu has quit IRC23:53
salv-orlando_mtaylor, danwent: quick question for you -> I see we are adding tissue to pip-requires and removing with-tissue from setup.cfg. I don't know anything about packaging, is that normal?23:59

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