Tuesday, 2011-12-06

*** novas0x2a|laptop has joined #openstack-meeting00:07
*** sleepsonthefloo has quit IRC00:24
*** gyee has quit IRC00:28
*** anotherjesse has quit IRC00:45
*** novas0x2a|laptop has quit IRC00:57
*** dolphm has quit IRC01:03
*** lloydde has quit IRC01:04
*** dragondm has quit IRC01:13
*** reed_ has joined #openstack-meeting01:14
*** bengrue has quit IRC01:15
*** danwent has joined #openstack-meeting01:15
*** reed has quit IRC01:16
*** dolphm has joined #openstack-meeting01:21
*** bencherian has quit IRC01:24
*** reed_ has quit IRC01:34
*** dolphm has quit IRC01:37
*** shang has joined #openstack-meeting01:41
*** anotherjesse has joined #openstack-meeting01:49
*** yamahata has quit IRC01:57
*** novas0x2a|laptop has joined #openstack-meeting01:58
*** anotherjesse has quit IRC02:03
*** adjohn has joined #openstack-meeting02:06
*** _adjohn has joined #openstack-meeting02:08
*** adjohn has quit IRC02:09
*** _adjohn is now known as adjohn02:09
*** _adjohn has joined #openstack-meeting02:26
*** adjohn has quit IRC02:26
*** _adjohn is now known as adjohn02:26
*** nati2 has quit IRC02:45
*** nati2 has joined #openstack-meeting02:45
*** adjohn has quit IRC02:49
*** jdurgin has quit IRC03:00
*** adjohn has joined #openstack-meeting03:10
*** danwent has quit IRC03:31
*** reed_ has joined #openstack-meeting03:34
*** reed_ has quit IRC03:35
*** deshantm has joined #openstack-meeting03:39
*** adjohn has quit IRC03:45
*** novas0x2a|laptop has quit IRC03:51
*** nati2_ has joined #openstack-meeting03:53
*** nati2 has quit IRC03:54
*** nati2_ has quit IRC04:10
*** nati2 has joined #openstack-meeting04:10
*** novas0x2a|laptop has joined #openstack-meeting04:12
*** sleepsonthefloo has joined #openstack-meeting04:32
*** adjohn has joined #openstack-meeting04:42
*** anotherjesse has joined #openstack-meeting04:58
*** anotherjesse has quit IRC04:59
*** nati2 has quit IRC05:00
*** nati2 has joined #openstack-meeting05:00
*** danwent has joined #openstack-meeting05:28
*** nati2 has quit IRC05:29
*** nati2_ has joined #openstack-meeting05:29
*** novas0x2a|laptop has quit IRC05:29
*** novas0x2a|laptop has joined #openstack-meeting05:30
*** novas0x2a|laptop has quit IRC05:48
*** novas0x2a|laptop has joined #openstack-meeting05:49
*** novas0x2a|laptop has quit IRC06:10
*** novas0x2a|laptop has joined #openstack-meeting06:11
*** deshantm has quit IRC06:31
*** novas0x2a|laptop has quit IRC06:42
*** novas0x2a|laptop has joined #openstack-meeting06:43
*** adjohn has quit IRC06:45
*** adjohn has joined #openstack-meeting06:46
*** jakedahn has joined #openstack-meeting06:57
*** jog0 has joined #openstack-meeting06:57
*** jog0 has left #openstack-meeting06:57
*** nati2_ has quit IRC07:14
*** danwent has quit IRC07:14
*** novas0x2a|laptop has quit IRC07:54
*** novas0x2a|laptop has joined #openstack-meeting07:56
*** bencherian has joined #openstack-meeting08:04
*** novas0x2a|laptop has quit IRC08:09
*** novas0x2a|laptop has joined #openstack-meeting08:09
*** novas0x2a|laptop has quit IRC08:09
*** novas0x2a|laptop has joined #openstack-meeting08:12
*** adiantum has joined #openstack-meeting08:14
*** shang has quit IRC08:32
*** novas0x2a|laptop has quit IRC08:45
*** bencherian has quit IRC08:46
*** novas0x2a|laptop has joined #openstack-meeting08:49
*** shang has joined #openstack-meeting08:50
*** adiantum has quit IRC08:50
*** adiantum has joined #openstack-meeting08:51
*** adjohn has quit IRC08:51
*** adjohn has joined #openstack-meeting08:56
*** beekhof has quit IRC08:57
*** beekhof_ has quit IRC08:58
*** beekhof has joined #openstack-meeting09:06
*** adjohn has quit IRC09:06
*** beekhof_ has joined #openstack-meeting09:08
*** novas0x2a|laptop has quit IRC09:25
*** novas0x2a|laptop has joined #openstack-meeting09:27
*** novas0x2a|laptop has quit IRC09:32
*** adiantum_ has joined #openstack-meeting09:39
*** adiantum has quit IRC09:43
*** adiantum_ has quit IRC10:18
*** adiantum_ has joined #openstack-meeting11:39
*** mattray has joined #openstack-meeting13:55
*** deshantm has joined #openstack-meeting13:56
*** lloydde has joined #openstack-meeting14:02
*** markvoelker has joined #openstack-meeting14:26
*** dprince has joined #openstack-meeting14:28
*** blamar has quit IRC14:40
*** blamar has joined #openstack-meeting14:43
*** hggdh has quit IRC14:47
*** danwent has joined #openstack-meeting14:47
*** hggdh has joined #openstack-meeting14:52
*** lloydde has quit IRC15:01
*** deshantm has quit IRC15:02
Davieyzul: ?15:04
zuldamn it15:04
zulanyone around for the nova-ec2-api team meeting?15:04
zulsince i have nothing on the agenda today15:05
zulDaviey: do you have anything?15:05
zulif not..15:06
openstackMeeting started Tue Dec  6 15:06:08 2011 UTC.  The chair is zul. Information about MeetBot at http://wiki.debian.org/MeetBot.15:06
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.15:06
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"15:06
openstackMeeting ended Tue Dec  6 15:06:12 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:06
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-06-15.06.html15:06
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-06-15.06.txt15:06
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-06-15.06.log.html15:06
*** AlanClark has joined #openstack-meeting15:06
zuli thought so15:07
Davieyzul: don't forget to distribute the logs.15:08
*** deshantm has joined #openstack-meeting15:10
ttxzul: I had one thing !15:23
zulwhich was?15:23
ttxzul: couldn't get uec-publish-tarball to upload an image in a recent test (E1)15:23
ttxzul: I abandoned the idea and did a glance add directly15:24
zulttx: you might want to smoser15:24
ttxzul: that may be something you might want to doublecheck15:24
zulttx: k15:24
smoserttx, well, uec-publish-tarball isalmost certainly not what you wanted anyway15:24
smoseras you dont want to add tarballs anymore, but rather the .img files.15:24
smoserbut asside from that...15:25
smoseryes, ew want that fixed if it is broken.15:25
ttxsmoser: I was trying to follow my howto from maverick days :) Boy, that was wrong15:25
smoserand i'm under the impression that it is.15:25
smoserttx, it will still work.15:25
smoserjust wont reboot into new kernels.15:25
smoserthe .img files allow kernel updates15:25
smoseras they have grub installed.15:25
ttxyes, I used the .img in my glance add call :)15:26
*** sleepsonthefloo has quit IRC15:29
*** jog0 has joined #openstack-meeting15:30
*** jog0 has left #openstack-meeting15:39
*** martines has joined #openstack-meeting15:42
*** rnirmal has joined #openstack-meeting15:45
*** bencherian has joined #openstack-meeting15:47
*** dolphm has joined #openstack-meeting15:52
*** beekhof has quit IRC15:55
*** beekhof_ has quit IRC15:55
*** jaypipes has joined #openstack-meeting15:58
*** deshantm has quit IRC15:58
*** deshantm has joined #openstack-meeting15:58
*** dragondm has joined #openstack-meeting15:59
*** adjohn has joined #openstack-meeting16:00
*** beekhof has joined #openstack-meeting16:03
*** beekhof_ has joined #openstack-meeting16:05
*** dolphm_ has joined #openstack-meeting16:07
*** adiantum_ has quit IRC16:08
*** dolphm has quit IRC16:09
*** danwent has quit IRC16:15
*** novas0x2a|laptop has joined #openstack-meeting16:23
*** jaypipes has quit IRC16:45
*** jaypipes has joined #openstack-meeting16:47
*** bencherian_ has joined #openstack-meeting16:48
*** bencherian has quit IRC16:51
*** bencherian_ is now known as bencherian16:51
*** novas0x2a|laptop has quit IRC16:54
*** mestery has quit IRC16:54
*** mattray has quit IRC16:57
*** mattray has joined #openstack-meeting16:58
*** bencherian has quit IRC17:03
*** nati2 has joined #openstack-meeting17:06
*** oubiwann has joined #openstack-meeting17:07
*** vladimir3p has joined #openstack-meeting17:09
*** sleepsonthefloo has joined #openstack-meeting17:10
*** lloydde has joined #openstack-meeting17:13
*** danwent has joined #openstack-meeting17:14
*** dwcramer has joined #openstack-meeting17:23
*** joesavak has joined #openstack-meeting17:23
*** jog0 has joined #openstack-meeting17:24
*** jog0 has quit IRC17:29
*** bencherian has joined #openstack-meeting17:30
*** jog0 has joined #openstack-meeting17:30
*** reed has joined #openstack-meeting17:32
*** davelap has joined #openstack-meeting17:35
*** bencherian has quit IRC17:35
*** danwent has quit IRC17:40
*** danwent has joined #openstack-meeting17:46
*** mestery has joined #openstack-meeting17:49
*** sleepsonthefloo has quit IRC17:54
*** sleepsonthefloo has joined #openstack-meeting17:54
*** zns has joined #openstack-meeting17:56
joesavakhi all - who is here for the keystone meeting? It starts in 2 minutes17:58
joesavakmight be a short one.17:59
joesavakwine delivered, btw17:59
joesavakMy wife says thanks17:59
znsCool! Merriness.18:00
joesavak#startmeeting Keystone Team Meeting18:00
openstackMeeting started Tue Dec  6 18:00:41 2011 UTC.  The chair is joesavak. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.18:00
*** openstack changes topic to " (Meeting topic: Keystone Team Meeting)"18:00
joesavak#link http://wiki.openstack.org/Meetings/KeystoneMeeting#preview18:00
joesavakagenda above18:01
joesavakAnyone else besides me & zns here for keystone meeting?18:01
joesavakFor the record, I'll report the status updates I know18:02
joesavak#topic status and progress18:02
*** openstack changes topic to "status and progress (Meeting topic: Keystone Team Meeting)"18:02
joesavak#link https://blueprints.launchpad.net/keystone/+spec/portable-identifiers18:03
znsPortable Identifiers targetted for E2: https://blueprints.launchpad.net/keystone/+spec/portable-identifiers18:03
joesavakportable identifiers moving along nicely. Dolph is working on it and still on track for e218:03
*** bcwaldon has joined #openstack-meeting18:03
*** bencherian has joined #openstack-meeting18:04
znsA series of refactors were pushed in today. Those will probably continue as we stabilize and clean up the code.18:04
joesavakany status on #link: https://blueprints.launchpad.net/keystone/+spec/endpoint-identifiers18:04
joesavakalso tagged as a e2?18:04
joesavakprobably should be pushed as portable IDs will cover users and tenants initially18:05
znsUpdated to E3 and added dependency on portable-identifiers.18:07
joesavakanyone from HP here to provide status on e-2 keystone bps?18:07
*** adjohn has quit IRC18:07
joesavaki'll bring it up in the community meeting later today18:08
joesavak#topic open-discussion18:08
*** openstack changes topic to "open-discussion (Meeting topic: Keystone Team Meeting)"18:08
joesavakany questions, issues, comments?18:09
znsCan you attend the team meeting on my behalf? I have a conflict...18:09
joesavakwill do18:09
joesavakok - closing meeting and i'll publish the minutes18:09
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"18:10
openstackMeeting ended Tue Dec  6 18:10:15 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:10
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-06-18.00.html18:10
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-06-18.00.txt18:10
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-06-18.00.log.html18:10
znsthank you. later...18:10
*** gyee has joined #openstack-meeting18:11
*** zns has quit IRC18:11
*** novas0x2a|laptop has joined #openstack-meeting18:12
*** deshantm has quit IRC18:22
*** dolphm_ has quit IRC18:23
*** CDY has joined #openstack-meeting18:26
*** danwent has quit IRC18:26
*** heckj has joined #openstack-meeting18:28
*** danwent has joined #openstack-meeting18:30
*** smoser has quit IRC18:31
*** jdurgin has joined #openstack-meeting18:33
*** bengrue has joined #openstack-meeting18:33
*** deshantm has joined #openstack-meeting18:35
*** reed has quit IRC18:36
*** sleepsonthefloo has quit IRC18:36
*** reed_ has joined #openstack-meeting18:36
*** davelap has quit IRC18:37
*** sleepsonthefloo has joined #openstack-meeting18:37
*** anotherjesse has joined #openstack-meeting18:37
*** reed_ has quit IRC18:40
*** KyleM1 has joined #openstack-meeting18:49
*** ArseneRei has joined #openstack-meeting18:56
mtaylorwhat's up party people?19:00
anotherjesseparty people in the house!19:01
openstackMeeting started Tue Dec  6 19:01:51 2011 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.19:01
mtaylorok. so, I've got a list of things to share with folks - but I think jeblair and ttx had something we were chatting about earlier that they said was a good CI meeting topic...19:04
mtaylorI suppose we can come to that later. for now19:05
lloyddefor the new guy here (me!) the wiki overview on the CI team is?19:05
mtaylorlloydde: hi! and we should probably have one of those19:05
anotherjesselloydde: there is ci.openstack.org for some of the information19:05
lloyddethnx anotherjesse!19:06
mtaylorlloydde: the CI team essentially runs jenkins, gerrit and the rest of the dev infrastructure19:06
mtaylorlloydde: so the folks who are only noticed when things are annoying :)19:06
mtaylor#topic CI todo list19:06
*** openstack changes topic to "CI todo list"19:06
ArseneReilloydde: May or may not be helpful. http://wiki.openstack.org/GerritJenkinsGithub19:07
mtaylorI keep mentioning our todo list, and I keep promising to make blueprints and bugs out of it19:07
mtaylorI still haven't gotten that done yet, so I just pastebinned the todo list so I could share it at the moment19:07
mtaylor#link http://paste.ubuntu.com/761935/19:07
mtaylor#action mtaylor turn the todo list into proper blueprints by 12/1219:08
mtaylorthere are essentiall three sections to the list - the first section is the general pile of random stuff that needs done at some point19:09
*** jk0 has joined #openstack-meeting19:09
mtaylorthe second section, which is marked Jim, are mainly tasks focued on the integration testing19:10
mtaylorand the third section are plugins and bugfixes on the docket for jenkins itself19:10
mtaylorwhich I'm working on hiring someone to do (but which had no current resource assigned to them)19:10
anotherjessesome of them go in openstack-common instead of openstack-ci right?19:10
anotherjesseclient split for instance19:11
mtaylorthat's mainly listed in the CI todo list because the way some of the jenkins jobs are structured is either waiting on that or needs to be changed once it's done19:11
mtaylorglance client being a good example of that - pip-requires glance is much uglier than the future pip-requires -e git:python-glanceclient19:12
anotherjessemtaylor: I'll help writeup the cli separation19:13
mtayloranotherjesse: awesome19:13
anotherjessesince I can't help with the ci stuff as much19:13
mtayloranotherjesse: I was chatting with a guy at hp who (similar to you) has his own jenkins up and doing tasks ... and we were talking about getting someone to write a jenkins plugin that would allow us to sensibly check the jenkins configs in to git and actually, you know, version control them19:14
mtaylorI think that would be killer helpful in getting more of us better able to work together on that aspect of things19:15
anotherjessemtaylor: currently devstack has a build_jenkins.sh that builds a 2 devstack based jenkins jobs on oneiric19:15
*** wwkeyboard has joined #openstack-meeting19:15
mtayloranotherjesse: that uses the jenkins api, yeah? we've got an outstanding bug in jenkins which prevents us from using that on the public jenkins19:16
mtayloranotherjesse: but I'm working on getting that filed with kohsuke so that it'll be fixed19:17
*** novas0x2a|laptop has quit IRC19:17
*** novas0x2a|laptop has joined #openstack-meeting19:18
mtayloralso - I want to convince ppb of something, but this might be a good place for an initial discussion19:18
mtaylorwhich is that gerrit has built in support for ensuring that devs have signed the CLA19:18
mtaylorseems to me with all of our automated things, having reviewers required to go look at a wiki page to see if the person submitting the patch has signed the CLA is a failure point19:19
*** jmckenty has joined #openstack-meeting19:19
mtaylorwhen all of the machinery is there to remove the need for reviewers to care about it19:19
mtayloranybody have any good reasons in their head why we _shouldn't_ do that?19:19
mtaylor#agreed gerrit should handle/enforce CLA signing so devs don't have to19:21
mtaylorthat was easy19:21
anotherjesseI thought we were doing that ...19:21
anotherjesseso I agree that we should19:21
mtayloryeah - the "check the wiki" step is pretty fail19:22
mtaylor#topic translations import19:22
*** openstack changes topic to "translations import"19:22
mtaylorwe set up the jobs yesterday to handle the translations import from the launchpad translations into a git commit19:22
mtaylorthere are two different ways to handle the final step:19:23
mtaylorone is to have jenkins submit the translations to gerrit for review as a normal change19:23
mtaylor(I lied, there are three ways)19:23
mtaylorthe second is to give jenkins the permissions to allow it to push the translations changes directly19:23
mtaylorthe third is to have it submit a change and then write a server-side hook for gerrit which will notice a translations change and automatically merge it19:24
mtaylorthe third way seems the nicest, because it means we don't have to give all of the jenkins jobs push access to trunk19:24
mtaylorbut it will mean a couple of extraneous emails on each translations import19:24
mtaylorany thoughts/opinions?19:25
jeblairthe second is the simplest of course19:26
mtaylorjaypipes: you here yet? I'm vamping a little bit because I want you in the next topic I want to talk about19:26
jeblairbut it grants jenkins a lot of permissions19:26
ArseneReiI'm exactly sure what the translations are, but the third seems best, despite extraneous e-mails.19:26
ArseneReiI'm not*19:26
jeblairyep, the only downsides to 3 are extra emails for watchers of projects, and a little extra complexity.19:27
ArseneReiRight, but I don't see a good reason to put that work in the hands of Jenkins, other than the simplicity.19:28
mtaylorArseneRei: translations of text strings into other languages - we use the launchpad translations feature to have people do the translating work itself, and it provides files with the translated text19:28
jeblairwe feel we don't need further code review of these changes (which option 1 would provide) because they are reviewed inside of launchpad19:29
ArseneReimtaylor: Ah, okay. Thanks. Then yes, #3. Jenkins shouldn't be involved on that level, in my opinion.19:29
ArseneReiYeah, that's sounds reasonable to me.19:29
mtaylorArseneRei: well, jenkins will still be involved somewhat, as it will be the one fetching the translations from launchpad and making a git commit from them ... but i do believe that having the acceptance of that commit codified inside of gerrit is a nicer place for it19:30
ArseneReimtaylor: Sure, but that's why I said at that level. :)19:30
mtaylor#agreed have jenkins propose a translations change to gerrit and then have a gerrit hook that notices a translation change from jenkins that only contains changes to po/ and automatically accepts it19:31
jaypipesmtaylor: here now.19:32
mtaylorare we keeping translations in consistent places across projects? I think they're in the po/ subdir everywhere that we use them, yeah?19:32
mtaylorjaypipes: excellent19:32
mtaylor#topic Integration testing and gating19:32
*** openstack changes topic to "Integration testing and gating"19:32
*** smoser has joined #openstack-meeting19:32
*** hub_cap has joined #openstack-meeting19:33
mtaylorso, jeblair is about to send out an email with a longer-form version of this, but I wanted to loop folks here in to both status and thinking19:33
mtaylorwe've got devstack-based integration testing working from jenkins, which is great19:33
mtayloramongst the features it has are spinning up fresh clean cloud servers for each tests, running devstack in them, and then on failures putting the machine to the side and installing the ssh key of the dev who broke it so that they can debug the problem19:34
jeblairmtaylor: do we have have authorization to do that yet?19:35
jaypipesmtaylor: excellent. what are you using for integration tests, though? because I have yet to be able to run tempest properly...19:35
*** rohitk has joined #openstack-meeting19:35
mtaylorno. we do not have authorization to hand the vms to devs yet19:35
jeblairso that feature will be disabled until we do.  :(19:35
heckjmtaylor: in same boat - haven't got tempest all sorted yet myself19:35
mtaylorbut we've asked and hopefuly should have an answer soon19:36
anotherjessemtaylor: eventually it would be nice to have a flow to inject others keys19:36
mtaylorjeblair: we're still running exercise.sh at the moment, yeah?19:36
mtayloranotherjesse: ++19:36
anotherjessesince the person who can fix might not be the person who runs19:36
jeblairyes, exercise.sh19:36
mtayloranotherjesse: good feature request19:36
* mtaylor adds to list19:36
jeblaircan we elaborate on that?19:36
jeblairas it stands, it adds the keys of the dev who proposed the change19:37
jeblairand of course, that person can add whoever else's key he or she wants19:37
jaypipesheckj: I'm *almost* there, though... been fixing a lot of bugs as I go along.19:37
jeblairhow would people like to change that?19:37
anotherjessejeblair: maybe anyone in core can inject a key?19:37
* jaypipes can't get exercise.sh to succeed... fails all tests :( https://bugs.launchpad.net/devstack/+bug/89884319:38
uvirtbotLaunchpad bug 898843 in devstack "exercise.sh fails all three exercises" [Undecided,New]19:38
anotherjessecurrently trunk is broken btw19:38
mtayloryou know - what might be interesting (and might have to wait until we're running on something with glance) ... would be a button or something to say "hey, I'd also like a copy of that machine over here"19:39
anotherjesseabout 7 hours ago - so having this in place would be muy bueno19:39
mtaylorso that brings us to the next point ... which is gating trunk with this19:40
anotherjessejaypipes: if you have time we can help figure out the fix for that later19:40
anotherjessein #dev19:40
jaypipesanotherjesse: coolio :)19:40
jaypipesanotherjesse: cheers19:40
jaypipesanotherjesse: prolly something silly.. just don't know enough to diagnose19:40
*** jkoelker_ is now known as jkoelker19:41
mtaylorgating trunk on the integration tests, it currently stands, may just about kill most of the devs, because of the potential complexity of submitting coordinated changes19:41
mtaylorso we have a couple of thoughts on dealing with that19:41
*** adam_g has joined #openstack-meeting19:42
mtaylorthe first step - and the easiest (it'll get us at least _something_) - is to turn on integration tests post merge and then have those actually send notification somewhere that people will notice it19:42
anotherjessemtaylor: the coordinated changes is the complexity :(19:42
anotherjessemtaylor: ya - knowing when it breaks is half the battle19:42
jeblairalso, there are a number of technical issues that need to be a lot more solid before we gate trunk on such a complicated test.  currently devstack and the launch scripts are highly suceptible to network and transient errors, that needs to be a lot more solid so we don't have false negatives19:42
mtaylorthis may be a combination of IRC messages and emails to the QA team, but ensuring actual information is there is at least a start19:42
mtayloryes. also what jeblair said - there are some external depends that we don't have control over such as PyPI and github19:43
jeblair(gating stable on those will help us flush those stability problems out)19:43
ArseneReiWhat is gating? Is it freezing a merge until some set of tests pass?19:43
heckjI've been seeing a huge number of intermittent errors with PyPi over the past few days -I'd be very loate to gate trunk on it.19:44
mtaylorArseneRei: yes. we currently do not allow code to hit trunk unless it passes unittests19:44
mtaylorheckj: yeah - same with github19:44
ArseneReimtaylor: Thanks.19:44
mtaylorheckj: so we need to solve those19:44
mtayloradditional things we can do to improve on the trunk situation include:19:44
mtayloradding a feature similar to what dprince did to run tests on code before it's approved/reviewed, but without jenkins voting on the change, so that reviewers can assess the failures19:45
mtaylorand then developing tooling around submitting coordinated changes that would potentially ease the burden of needing to change nova and devstack at the same time19:45
_0x44mtaylor: There was a verbal vote at the essex summit to gate on an integration test that was supported by vish for nova.19:45
jeblairthat's on the list under "- Pre-review testing" which is chronologically after "- New Gerrit Trigger Plugin" because that's a dependency19:45
bengrue"gating trunk on the integration tests, it currently stands, may just about kill most of the devs, because of the potential complexity of submitting coordinated changes"19:45
mtaylor(there are client-side tools we'd need, as well as a change to gerrit or the gerrit trigger plugin to make that work)19:45
_0x44mtaylor: I'm not sure why this needs to come up again.19:46
_0x44mtaylor: If there's a single integration test, gate on it.19:46
mtaylor_0x44: yes. we're talking about the actual implementation of it, not whether or not we agree it should be done19:46
dprincemtaylor: we are currently running everything pre-commit to trunk:19:46
_0x44mtaylor: It's already been done by Ozone...19:46
mtaylor_0x44: it's that the integation tests depend on multiple things, not just nova, and the coordination of those things become tricky19:46
dprinceI know there is a bit of disagreement on the use of SmokeStack. But its what I've got.19:47
_0x44mtaylor: If you don't gate it won't be less tricky.19:48
_0x44mtaylor: It will just force that trickiness onto the user/downstream distributor19:48
ArseneReimtaylor: On the dprince and intermittent issue, it can be modified perhaps with voting when knowing if the intermittent issues are absent.19:48
mtaylor_0x44: I think what we're talking about is a phased implementation19:49
dprinceAlso. I aim to update that report so that installer (ubuntu) or config management changes (chef) that team titan makes those changes ahead of time.19:49
dprincereviewday and smokestack essentially are trying to visualize the "fullstack".19:49
_0x44mtaylor: I don't think that's the right way to do it.19:49
mtaylor_0x44: based on concerns from vish, actually, on the process of submitting changes sensibly19:49
mtaylor_0x44: and the concern about a high level of false negatives at the moment that have nothing to do with the devs code19:50
_0x44mtaylor: The phased implementation that was chosen at essex was to gate on a single integration test.19:50
mtaylorbut instead on the flakiness of github and pypi19:50
mtaylor_0x44: which is what we have at the moment for stable/diablo19:51
_0x44mtaylor: Fix those as they come up, don't try to prematurely decide what false-negatives will happen and throw out the value of integration testing because you want to fix occassional false negatives.19:51
mtaylor_0x44: we're not prematurely deciding19:51
mtaylorwe've been running this for weeks and looking at the actual problems19:51
jeblairthose failures are all false negatives19:52
jeblairand that job can't even run right now because of a problem with the cloud provider we're using19:52
jeblairi don't think it's fair to stop all forward progress on the project until we can handle problems like that19:52
_0x44jeblair: There are only five false negatives there.19:53
mtaylorso what we're saying is, we need to sort those out, but in the mean time we'd like to at least run this stuff post-merge so that we're not waiting for nirvana before getting feedback19:53
jeblairand there are only 30 tests there, that's a 16% false negative rate19:53
jeblairit is also worth noting that at this point, i don't believe any integration test can involve less than nova, glance, and keystone19:55
mtaylorand devstack19:55
mtaylorand python-novaclient19:55
_0x44jeblair: That's the point of an integration test...19:55
jeblairso this test (will) actually gate(s) all of nova, glance, keystone, devstack, python-novaclient, and openstack-ci (which has the scripts that launch the test)19:55
jeblair_0x44: i know, i mean only to give an indication of what's meant by "coordinated change"19:56
*** dolphm has joined #openstack-meeting19:57
jeblair(oh, and tempest, the test framework itself, once that's ready)19:57
mtaylorjeblair: I wonder, since dprince is already doing pre-review testing on his systems ... any reason to not have reviewday register code review votes on gerrit? at least for coordinated information purposes19:58
_0x44jeblair: Only fixes that depend on new features in a specific project need to have coordinated changes. Otherwise you test against the last known good.19:58
mtaylorI mean, anybody can register a non-binding review on something19:58
mtaylor_0x44: yes. it turns out that's what we're doing19:58
jmckentymtaylor: that seems like a really good idea19:58
jmckentyre: having reviewday post reviews to gerritt19:58
*** zns has joined #openstack-meeting19:59
jeblairmtaylor: i don't believe anything should be prohibiting that19:59
mtaylordprince: ^^^19:59
mtaylordprince: any interest on your side in doing that? or any way I can help you do that?19:59
_0x44mtaylor: If you're already doing that, then the fact that patches need to land in a specific order in order for tests to pass isn't really a concern for CI. It's a concern for the upstream projects.20:00
mtaylor_0x44: yes. I think the larger concern is coordinating changes between devstack and project config changes. landing patches in API/feature order is less problematic20:00
jeblairif strict ordering is the approach projects would like to take, then that certainly makes it easier to implement on the CI side20:00
jeblairbut vishy seemed concerned with that approach the last time we spoke20:01
_0x44mtaylor: That still isn't a CI problem, that's a project management/PTL problem.20:01
jeblairmtaylor: i'm not sure how devstack in special in that regard20:01
jmckentysorry to interrupt, but are we going to use this channel for PPB?20:01
jmckentyit's noon20:01
jmckentyer... GMT somethingorother20:01
mtaylorit is time to wrap up20:01
_0x44Anyway, I'll stfu now.20:01
mtaylorlet me just say...20:01
jeblairmtaylor: during a development cycle, how nova and devstack interact isn't that different than nova and glance20:01
jeblairas far as how you would coordinate those changes20:02
*** dwcramer has quit IRC20:02
znshere. PPB?20:02
mtaylor_0x44: well, it's not about stfu - I think we might have missed each other on scope of what I'm talking about here ...20:02
jmckentyzns, just waiting for the channel20:02
_0x44mtaylor: I was meaning for the ppb20:02
*** markmc has joined #openstack-meeting20:02
vishyjmckenty: is the ppb happening?20:02
mtaylor_0x44: heh20:02
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"20:02
dprincesorry guys. Got interrupted.20:02
openstackMeeting ended Tue Dec  6 20:02:54 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-06-19.01.html20:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-06-19.01.txt20:02
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-06-19.01.log.html20:02
jmckentyvishy - my proposed topics bounced from the openstack-poc mailing list again20:03
mtaylordprince: read the scrollback - you have a mushy-request for wonderfulness20:03
* jmckenty hates all the launchpad mailing lists20:03
dprinceI'm up for posting the test results to gerrit. Absolutely.20:03
mtaylordprince: great. I think that'll be killer helpful20:03
jmckentyvishy: do you want to chair? We have no jonathan today20:03
mtayloro/ btw - although I suppose that's obvious20:03
vishywell i was hoping we weren't going to have it20:03
jmckentyk  - just wanted to discuss how cloudaudit should get proposed20:04
vishylets see if enough people show up20:04
jmckentyas a separate project vs. as an integration effort to existing projects20:04
jmckentyI prefer the latter, but there's no framework for incubation in that case20:04
vishyis that a ppb decision?20:04
znsjmckenty: where can I find out more about cloudaudit?20:04
anotherjessejmckenty: one of the factors behind incubation was adoption I thought20:04
vishyI mean you can propose it in to the projects individually20:04
notmyname(from what I saw at the summit) I'd think it would integration into each project20:05
_0x44zns: cloudaudit.org and https://github.com/piston/openstack-cloudaudit20:05
jmckentyanotherjesse: right, but integration is blocking adoption20:05
vishyI think the ppb mandating that all projects must merge it is a horrible idea20:05
notmynamevishy: agreed20:05
jmckentyalso, it's possible that the cloudaudit evidence gathering components could help with debug and CI20:05
jmckentyvis-a-vis the system API stuff we were talking about previously20:05
anotherjessejmckenty: isn't there a blueprint somewhere too?20:05
jmckentyyeah, hold on...20:06
vishyjmckenty: are you suggesting a copy of all of the cloudaudit files individually into each project?20:06
jmckentyeach project needs an evidence gatherer20:06
*** reed has joined #openstack-meeting20:06
jmckentythe cloudaudit API endpoint runs separately,20:06
znsjmckenty: thanks20:07
jmckentybut needs to be able to report on evidence related to each upstream component20:07
vishyso propose the api reporting code as incubated20:07
jmckentyjust trying to avoid project proliferation20:07
vishyand propose evidence gatherers into each project20:07
jmckentyright, but it'll fail incubation until we have evidence gatherers20:07
jmckentyb/c we can't meet adoption requirements20:07
vishyor don't incubate it at all and manage it separately if you prefer20:07
anotherjessejmckenty: incubation = a label20:07
anotherjessepeople can use a project before incubation20:08
vishyyou can manage it separately + propose gatherers20:08
jmckentyyeah, I realize. We proposed the blueprint for openstack-common20:08
vishythen incubate it later20:08
* mtaylor is a fan of bringing things in to the folks sooner rather than later, fwiw20:08
mtaylorbut that may just be me20:08
mtaylorthings in to the fold20:08
jmckentyb/c (hopefully) the evidence gatherers would get built to a common model20:08
mtaylornot the folkss20:08
jaypipesvishy: PPB mandating that all projects should merge *what*?20:08
anotherjessehttps://blueprints.launchpad.net/openstack-common/+spec/cloud-audit-api <- would be nice to have a more detailed blueprint (whiteboard or wiki)20:08
jmckentyI'll get some generated docs out of the code20:09
vishyjaypipes: cloudaudit support20:09
jmckentyor more detailed on the evidence gatherers?20:09
jaypipesvishy: still not sure what you mean by "merge it"...20:09
vishyjaypipes: evidence gatherers20:09
vishyso are we having an official ppb meeting?20:10
vishybecause someone should start it if so20:10
openstackMeeting started Tue Dec  6 20:10:27 2011 UTC.  The chair is jmckenty. Information about MeetBot at http://wiki.debian.org/MeetBot.20:10
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.20:10
jmckenty#topic cloud-audit background20:10
*** openstack changes topic to "cloud-audit background"20:10
anotherjessejmckenty: I guess I see evidence gathers similar to monitoring plugins - which aren't normally kept in the core project ...20:10
jaypipesanotherjesse: agreed.20:10
znsjmckenty: Could the gatherers be created in an openstack-common type library (which seems always to be on the verge of getting started - maybe this could move it along)? Or how deep is the introspection you need?20:11
jmckentyI also agree they should be built as plugins, but I was hoping to have them somewhat symmetrical across projects20:11
jmckentyzns - exactly what I'm hoping for20:11
vishycommon config looks like it might kick off openstack-common20:11
jmckentye.g., that cloudaudit's requirements are a good use-case for openstack-common20:11
jaypipes_0x44: FYI, typo in https://github.com/piston/openstack-cloudaudit/blob/master/cloudaudit/evidence_engine/idle_session_lock.py ( grep for eivdence)20:12
zns+10 to common config. How can I help, get some, …?20:12
mtaylorvishy: common config and also melange, which depends on openstack-common20:12
_0x44jaypipes: Grazie...20:12
anotherjessezns: keystone middleware should be there -but this is getting off the topic20:12
vishyzns: have you been following the ML?20:13
vishythere is a proposal in20:13
znsanotherjesse: no disagreement from me.20:13
vishyjmckenty: is there anything specific you need from the ppb?20:13
znsvishy: obviously behind...20:13
anotherjessejmckenty: it seems like before proposing to the pbb it would be good to bring it to the ML?20:13
jmckentywe're not proposing20:14
znsvishy: I'll trawl through the emails and catch up...20:14
jmckentythis is pre-proposal, just checking with the PPB on status of openstack-common20:14
jmckentyand whether it's going to be in Essex20:14
*** dwcramer has joined #openstack-meeting20:14
vishyjmckenty: well it isn't exactly an official project20:15
vishyjmckenty: but it looks like projects will be depending on it20:15
ttxvishy: it's a rather specific case, we might need to fast-track it.20:16
vishyI don't know if we have a process for this.  It is kind of like an external library20:16
anotherjessejmckenty: afaik there are several code "projects" (the common config, perhaps keystone middleware, perhaps a base for openstack cli tools - that novaclient, keystoneclient, … can use) - and then a place for blueprints about the project as a whole20:16
*** dprince has quit IRC20:16
jmckentyso as a specific point,20:16
jmckentythe root_wrapper stuff ttx has been working on for nova20:17
ttxvishy: imho openstack-common is more an expression of commonality between projects.20:17
jmckentyis a key requirement (or something equiv) for evidence gatherers20:17
ttxvishy: not a new project per-se20:17
vishyttx: good so we don't need to vote it in20:17
mtaylorttx: yes, but it's still a project with a lifecycle and will need reviewers and a core team20:17
jmckentyand hopefully would move into openstack-common20:17
vishywe just need to make it work.20:17
ttxmtaylor: sure, I'm just finding excuses for fast-tracking it.20:17
* mtaylor doesn't think we need to vote it in - but we may have to deal later with issues - I think we're fine for right now20:18
vishycore could initilaly be all core members?20:18
jmckentyttx and vishy - are you happy to make openstack-common a dependency for nova, and move root_wrapper into it?20:18
mtaylorat the moment, I've got the poc members and anotherjesse in the openstack-common-core team20:18
vishyand common config20:18
*** GheRivero_ has joined #openstack-meeting20:18
mtaylorwell, I've invited openstack-poc, the invitation hasn't yet been accepted20:19
ttxjmckenty: the reason why it's done in Nova is that the other projects don't really need privilege escalation20:19
jmckentygreat - that will unblock us on cloudaudit20:19
jmckentyttx - they will for cloudaudit plugins, though20:19
jmckentythat's my point20:19
mtaylorwas also going to add markmc and jvoelker, since they've been doing the most hacking on the project so far20:19
ttxjmckenty: in which case, yes, it would make a good candidate for openstack-common.20:19
*** troytoman-away is now known as troytoman20:20
jmckentyI'm happy - any other topics?20:20
jmckentyI would ask for a foundation update, but we've got no Jonathan20:20
jmckentyI could give a FITS update - which is that it's hung on foundation updates20:20
mtaylorjmckenty: I'd like to check in with folks on the CLA stuff I mentioned in the CI meeting20:20
jmckenty#topic Management of CLA20:21
mtaylorso - in case you weren't in the CI meeting ...20:21
*** openstack changes topic to "Management of CLA"20:21
jmckentyI overhead it20:21
jmckentyproposed that gerritt manages CLA, right?20:21
mtaylorgerrit has a facility for managing CLA signing and not allowing proposals from people who haven't signed it20:22
jmckentyThat only addresses individual contributor CLA and not organizational CLA20:22
mtaylorthis seems nicer than asking reviewers to check a wiki page20:22
jmckenty+1 notionally, would like to see how we manage org. CLA as well20:22
zns* wonders if he should have been checking a wiki page before accepting reviews! *20:22
vishyis there a discussion necessary?20:23
anotherjessezns: ya - I had thought it was done for us - but that is it is just the mailmap that was checked20:23
vishysounds like our tools just fell behind20:23
jmckentymtaylor - can we do this without requiring anyone to resign their CLA?20:23
mtaylorjmckenty: I believe so20:23
mtaylorjmckenty: I think we can pre-seed the database20:23
mtaylorjmckenty: although I want to double-check that before I 100% commit to being able to do it20:23
notmynamedoes this need to be something we decide on as a PPB or just something that needs to be done?20:24
jmckentyI think changes to how CLA is managed is a PPB issue20:24
jmckentybut only if it's a substantive change20:24
mtaylorI think it might be a ppb decision, since it affects how we'd be telling folks to contribute20:24
jmckentyand this seems like simple tools issues20:24
anotherjessego for it +120:24
mtaylorok. well, I mean, we can certainly do a POC, show some folks and then move forward20:24
jmckenty#vote CLA will be managed by Gerritt20:25
anotherjesseship it20:25
ttxI think currently it's not managed at all. +120:25
jmckentyI think we've got quorum and that seems like enough votes...20:25
jmckenty#agreed CLA to be managed by Gerritt20:25
ttx(tarmac used to check the list up, I'm pretty sure the current Ci doesn't)20:25
mtaylorawesome. thanks guys.20:26
jmckentyAny other topics?20:26
* jmckenty loves finishing meetings early20:26
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"20:26
openstackMeeting ended Tue Dec  6 20:26:35 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:26
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-06-20.10.html20:26
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-06-20.10.txt20:26
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-06-20.10.log.html20:26
ttxlunch at 10pm ?20:27
mtaylorttx: yes. eat lunch now. silly europeans eating at different times from the rest of us.20:27
*** johnpur has joined #openstack-meeting20:30
*** heckj has quit IRC20:34
*** heckj has joined #openstack-meeting20:34
*** ArseneRei has left #openstack-meeting20:35
*** somik has joined #openstack-meeting20:38
*** davelap has joined #openstack-meeting20:38
*** dolphm has quit IRC20:44
*** jwalcik has joined #openstack-meeting20:47
*** johnpur has quit IRC20:49
*** dolphm has joined #openstack-meeting20:50
*** Vek has joined #openstack-meeting20:51
*** bencherian has quit IRC20:51
*** bencherian has joined #openstack-meeting20:51
*** deshantm has quit IRC20:58
*** Ravikumar_hp has joined #openstack-meeting21:00
glencI'm here21:00
* Vek yawns21:00
ttxzns, notmyname, jaypipes, vishy, devcamcar: around ?21:00
joesavakfor zns21:01
anotherjessevishy & notmyname are here - just geting back21:01
*** reed has quit IRC21:01
openstackMeeting started Tue Dec  6 21:01:42 2011 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
*** mikeyp has joined #openstack-meeting21:01
ttxWelcome everyone to our weekly general meeting...21:01
ttxNothing special on today's agenda: http://wiki.openstack.org/Meetings/TeamMeeting21:02
*** zns has quit IRC21:02
ttx#topic Actions from previous meeting21:02
*** openstack changes topic to "Actions from previous meeting"21:02
ttx* ttx and vishy to discuss how to solve Nova's team structure21:02
ttxSo we've discussed that... vishy has a few changes coming up, I think21:02
ttxvishy: care to share your plans ?21:02
*** zns has joined #openstack-meeting21:02
comstudsolve implies there's a problem.  did I miss the problem?21:02
comstudi guess i did..i missed last meeting21:03
*** dwcramer has quit IRC21:03
*** tcampbell has joined #openstack-meeting21:03
vishysorry: stepped away for a sec21:03
vishyI will be drafting an email to explain it21:03
vishywe're going to deprecate a few teams and move them to a wanted list21:03
ttxvishy: ok, don't want to spoil your effects :)21:03
vishyand probably change the ml structure21:04
lloyddeI just figured out the o/21:04
ttxvishy: and have a weekly Nova-specific meeting ?21:04
vishyso I guess the result is email on the way!21:04
vishyyes, team lead meeting once a week21:04
vishyhave to determine where on the schedule that fits21:04
ttxk, thx!21:04
ttx* ttx to check the need for MP jenkins jobs on novaclient21:05
ttxSo those are still needed, bug 899056 tracks that21:05
uvirtbotLaunchpad bug 899056 in openstack-ci "python-novaclient needs milestone-proposed Jenkins jobs" [High,Confirmed] https://launchpad.net/bugs/89905621:05
ttx* ttx or vishy to start a discussion on release PPA21:05
*** scottsanchez has joined #openstack-meeting21:05
ttxI started a thread on the ML, here is a summary:21:05
ttxIf you don't agree, I encourage you to voice your opinion there :)21:05
*** sgrebnov has joined #openstack-meeting21:05
ttxLet's move on to project status...21:06
ttx#topic Keystone status21:06
*** openstack changes topic to "Keystone status"21:06
ttxjoesavak: o/21:06
joesavak#link https://blueprints.launchpad.net/keystone/+spec/portable-identifiers21:06
ttx#link https://launchpad.net/keystone/+milestone/essex-221:06
joesavakportable ids is looking good for e-2. Good progress21:06
ttxOne week left to merge those E2 features, are all the others still on track ?21:07
joesavakI've seen some reviews by HP - but not sure if they close out their BPs21:07
ttxjoesavak: in particular service-endpoint-location, which is marked Not Started...21:07
ttxjoesavak: should keystone-documentation and keystone-swift-acls be considered completed ?21:08
joesavaknot sure on those. ping heckj21:08
joesavakping hp21:08
heckjthe docbook stuff hasn't been finished - I've made no progress there recently21:09
znsttx, joesavak: the reviews from HP don't address the blueprints.21:09
heckjdon't know the swift-acls though21:09
*** mjfork has joined #openstack-meeting21:10
ttxheckj: is the doc thing an "always in progress" thing ? In which case I'd rather have it out of the plan21:10
ttxI mean, we don't have a "Bugfixing" blueprint either.21:10
heckjttx: it was a specific effort to bring the documentation to date to enable an install. It's horrifically lacking at this point21:10
*** mcohen has joined #openstack-meeting21:10
*** tcampbell has quit IRC21:10
ttxheckj: ok, if there is a way to complete it, I'm fine with it21:11
ttxheckj: so wit hthat description, it's not complete yet, is it going to be ok by next week ?21:11
lloyddeupdate the title to "Document Keystone Install"?21:11
*** deshantm has joined #openstack-meeting21:11
ttxlloydde: good idea21:11
heckjttx: I'm not likely to be able to get it done by E2 deadline21:12
*** sgrebnov has quit IRC21:12
ttxok, pushing back to E3 then.21:12
* heckj nods21:12
ttxjoesavak: Anything else ?21:12
joesavaknot from me...21:13
ttx#action joesavak/zns to sync with HP for updated status on their blueprints21:13
joesavaki'll ping them now21:13
ttxQuestions for Keystone ?21:13
ttxjoesavak: just update the status based on the result21:13
joesavakwill do21:14
ttx#topic Swift status21:14
*** openstack changes topic to "Swift status"21:14
ttxnotmyname: o/21:14
*** deshantm has quit IRC21:14
ttxWhat news ?21:14
notmynameI don't think I have any21:14
notmynamemeetup tomorrow night in sunnyvale21:15
notmynamethat's it21:15
mtaylornotmyname: how's the go rewrite going?21:15
notmynamemtaylor: I'm still working on the erlang/go interpreter ;-)21:15
ttxOther questions on Swift ?21:15
ttxnotmyname: not likely to have 1.4.5 before the end of the year ?21:16
* ttx is planning vacations.21:16
notmynamettx: unlikely21:16
ttx#topic Glance status21:17
*** openstack changes topic to "Glance status"21:17
ttxjaypipes: yo21:17
jaypipesttx: oy21:17
ttx#link https://launchpad.net/glance/+milestone/essex-221:17
*** heckj has left #openstack-meeting21:17
ttxjaypipes: Looks like you have a new target: multi-process-server21:17
*** heckj has joined #openstack-meeting21:17
ttxIs that one still on track for the December 13 deadline ?21:17
jaypipesttx: I'll push that one to E3. Stuart McLaren is working on that at HP.21:18
jaypipesttx: for the other bugs, a lot of them are packaging-related. I'll work with monty on getting some status updates on those.21:18
ttxjaypipes: ok21:18
*** dwcramer has joined #openstack-meeting21:18
ttxjaypipes: you're getting ready for a very busy E3.21:19
jaypipesttx: yeah I know...21:19
*** ohnoimdead has joined #openstack-meeting21:19
ttxjaypipes: pushed21:19
ttx#action jaypipes to get status updates from mtaylor on Glance packaging issues21:20
ttxjaypipes: Anything else ?21:20
jaypipesttx: nope. expect the 2.0 API 3rd draft by end of today...21:20
jaypipesttx: that is the main blocker for a lot of E3 blueprints, BTW,.21:20
ttxjaypipes: is everything going as you want on that front ?21:21
*** somik_ has joined #openstack-meeting21:21
jaypipesttx: on the 2.0 API proposal front?21:21
ttx#info expect the 2.0 API 3rd draft by end of today21:21
jaypipesttx: yes, got great feedback so far. just putting the final touches on it based on some Ozone team feedback.21:21
ttxQuestions on Glance ?21:22
*** edconzel has joined #openstack-meeting21:22
ttx#topic Nova status21:22
*** openstack changes topic to "Nova status"21:22
ttxvishy: yo21:22
ttx#link https://launchpad.net/nova/+milestone/essex-221:22
ttxLooks generally good, though lots of stuff is blocked in review21:23
ttxvishy, tr3buchet: I see two new targets: compute-network-info and network-info-model21:23
ttxDo those warrant two separate blueprints ?21:23
vishyI'm a little concerned about the first essential blueprint21:23
*** tech__ has joined #openstack-meeting21:23
ttxvishy: yes, me too21:23
*** somik has quit IRC21:23
*** mcohen_ has joined #openstack-meeting21:23
ttxGaurav did not update his proposed change since Nov 15.21:23
vishyhaven't seen any updates for a while21:24
* ttx looks behind him as apparently vishy is copying his notes21:24
vishyso I wonder if someone else should take it over and fix the testing issues21:24
ttxvishy: +121:24
ttx(giving appropriate credit where due)21:25
*** mcohen has quit IRC21:25
*** mcohen_ is now known as mcohen21:25
ttxvishy: question is... who ?21:25
*** CDY has quit IRC21:25
*** CDY has joined #openstack-meeting21:25
vishyok, I can't think of anyone else who can take it offhand21:25
vishyI might have to grab that one myself21:25
vishyI will also contact david-perez and see if he can get the other one up to date?21:26
vishybranch point is next tuesday?21:26
ttx#action vishy to find a victim or complete by himself nova-volume-snapshot-backup-api21:26
ttxand yes21:26
vishyi think that tr3buchet's network ones are on track21:26
ttx#action vishy to sync with david-perez on finishing up nova-vm-state-management21:27
ttxsure, was just wondering if that warranted two blueprints, and if yes, one is missing priority.21:27
ttxShould quantum-nat-parity be considered completed ? (bhall)21:27
*** thingee has joined #openstack-meeting21:27
*** dolphm_ has joined #openstack-meeting21:28
ttxwestmaas: are you seeing the end of internal-uuids ?21:28
danwentttx: yes, my understanding is that it is in.21:28
ttxdanwent: ok, marking completed21:28
ttxoh, someone already did.21:28
danwentbhall said he was going to :)21:28
ttx"Brad Hall 2 hours ago"21:28
vishyyes i think everything else is on track21:28
ttxLooking at the reviews situation... A few hours ago we had 55 nova/master reviews opened21:29
ttxI'd like to consider an abandon policy for stale reviews. Something like:21:29
ttxAbandon all changes with a -2 that were not updated in the last x days21:29
ttxAbandon all changes with a -1 that were not updated in the last y days21:29
ttxx=7 and y=14 would bring down the number of reviews to a more manageable 2221:30
ttxWould that work ?21:30
*** dolphm has quit IRC21:30
* Vek won't typically look at a -1 or -2 review, waiting for the OP to upload a fresh one...21:30
wwkeyboardAnd anything older than those numbers will need to be rebased anyways21:31
vishyttx: I definitely think -2 is fine21:31
vishyfor 7 days21:31
vishyI suppose they can resubmit right?21:31
vishycan we get it to automatically do that?21:31
ttxnothing should prevent them to.21:31
Vekvishy: I wonder if they might have to generate a new change-id?21:32
*** davidk has joined #openstack-meeting21:32
ttxvishy: I'll ask mtaylor/jeblair21:32
vishymtaylor, jeblair? ^^21:32
bhallVek: yes, they would I believe21:32
*** davidk is now known as Guest3521921:32
vishythat is kind of annoying, if that is the case then we might want to make the -1 a little longer21:32
*** patelna has joined #openstack-meeting21:32
ttxvishy: I guess multiple -1s could be considered as well21:32
mtayloryou do not have to regen a change id for abandonded changes21:33
mtaylorthey can be un-abandoned21:33
bhallah, good to know21:33
mtayloralso, we have a todo list item for a work-in-progress state, so this would just be a workaround until then21:33
ttxvishy: ideally the tool can autoabandon, but having a policy that nova-core can apply in the mean time also helps.21:33
Vekttx: +1; a -2 or 2 or more -1s seems like a good call for that.  I'd still have 7 days for -2 and, say, 14 for -1s21:34
vishycan we force abandon changes?21:34
vishyI can't find a button for it21:34
ttxvishy: I thought you core dudes could... but maybe not.21:34
ttxmaybe it's just a question of filtering default views21:35
ttxreviewday could do that.21:35
ttxvishy: Anything else ?21:35
ttx#action ttx to discuss options for getting a sane list of reviews with CI guys21:36
ttxNova subteam leads: anything you wanted to add ?21:36
ttxEveryone: Questions on Nova ?21:36
ttx#topic Horizon status21:37
*** openstack changes topic to "Horizon status"21:37
ttxdevcamcar: o/21:37
ttx#link https://launchpad.net/horizon/+milestone/essex-221:37
ttxOne week left, you look a bit behind schedule, especially Tres Henry (with 3 non-started things on his plate)21:38
devcamcartwo of the three are going to have to be punted to essex-321:38
ttxdevcamcar: do you already know which ?21:38
devcamcaryes, i'm actually updating them now21:38
devcamcarthose two are being punted21:39
ttxok, the rest is on track to get merged in before EOD next Tuesday ?21:39
devcamcarshould be21:39
ttxyou have a huge list of essex-2-targeted bugs21:39
devcamcarwe may have to punt a few of the ux changes to essex-321:40
devcamcarmost of those are small fixes and a ton of those are getting fixed every day21:40
ttxworks for me :)21:40
devcamcaryea, we are actually making a ton of progress21:40
*** rohitk has quit IRC21:40
devcamcarnew modal system is done: http://c213515.r15.cf1.rackcdn.com/29e0c2820346b6b68edc8067044e2ac5.png21:40
devcamcarimproved side nav: http://c213515.r15.cf1.rackcdn.com/4b3d78edecca73daded75202a1750ee4.png21:41
ttxdevcamcar: about the ux changes, either push the blueprint completion to E3, or split it in two (if the two subsets makke sense separated)21:41
*** rohitk has joined #openstack-meeting21:41
devcamcarttx: i will push the blueprint to e3. i think that makes more sense21:41
ttxdevcamcar: Anything else ?21:41
devcamcarwe also added tenant management when using keystone in db only mode: http://c213515.r15.cf1.rackcdn.com/6226b6a06b8489c59dcd402b41986cee.png21:42
devcamcarttx: that's about it21:42
tr3buchetvishy: ttx: sorry i had stepped out. those 2 blueprints are on track.21:42
ttxtr3buchet: thx21:42
ttxQuestions for Horizon ?21:42
ttx#topic Incubated projects and other Team reports21:43
*** openstack changes topic to "Incubated projects and other Team reports"21:43
ttxdanwent, troytoman: o/21:43
ttxEverything going well in Quantum/Melange world ?21:43
danwenton quantum.  our e-2 nova blueprints are done.  two bugs that we'd like to get in for e-2.21:43
danwentI didn't seem to be able to target bugs to a release though… is that something you or vish have to do?21:44
ttxdanwent: no, you should be able to do that for Quantum21:44
danwentttx: sorry, i'm talking about nova21:44
ttxdanwent: yes, we can do it, just paste bug numbers21:44
ttxso two bugs in nova ?21:45
danwent https://bugs.launchpad.net/nova/+bug/89976721:45
uvirtbotLaunchpad bug 885265 in quantum "quantum 420 error leaves instance in BUILD state" [High,New]21:45
uvirtbotLaunchpad bug 899767 in quantum "live_migration does not perform vif unplugging " [High,In progress]21:45
danwentin quantum itself:  https://bugs.launchpad.net/quantum/+milestone/essex-221:45
danwenthave a lot of code to review… and some bugs to squash21:45
ttxdo you have someone working on the first one on nova side ?21:45
Vekwhat the heck is a 420?21:46
ttx(is Brad Hall working on the nova side of the fix as well ?)à21:46
danwenthttp error code… don't get any ideas Vek :P21:46
danwentttx: yes, I will assign bhall to the nova side as well. sorry21:46
ttxdanwent: i'm on it21:46
danwentonly other point to bring up was a discuss I read about on Rob H's blog about dependencies on Quantum by other openstack projects21:47
ttxdanwent: you'll use a milestone-proposed branch for E2 ?21:47
danwentttx: yes21:47
Vek"Policy not Fulfilled"?21:47
ttxdanwent: ok, let me know if you've questions on that.21:47
danwentwe now have the github permissions21:47
danwentVek: ask salvatore.. he defined our error codes.  I thought you were hinting at another meaning of that number21:48
* ttx gets curious21:48
*** salv has joined #openstack-meeting21:48
danwentanyway, back to the dependenices question.  I'd like to figure out a way that quantum can be a "soft dependency" for things like horizon + nova while it is incubation.21:48
danwentttx: i'm sure google can help21:48
ttxdanwent: it does !21:49
danwentso if anyone has thoughts on the dependency issues, please contact me, or the netstack list as a whole.  that's all from me.21:49
*** zul has quit IRC21:49
troytomanwrt Melange, we have moved the repo into Github/gerrit thanks to jeblair21:49
troytomanspent time this week working on documentation that is now in the repo21:49
Vekthe only documentation I can find for 420 so far also documents 418--"I'm a Teapot" :)21:49
Vekanyway, I digress...21:50
ttxtroytoman: nothing blocking you ?21:50
troytomanwe still have to resolve an issue wound whether to use an openstack common repo or pull that code into Melange21:50
troytomanwe have a work around so it is not a blocker right now21:50
mtaylortroytoman: I believe we've made progress in agreeing to make openstack-common a real thing21:50
danwentvek: http://docs.openstack.org/incubation/openstack-network/developer/quantum-api-1.0/content/Faults.html21:51
mtaylortroytoman: and you can, of course, add a tag or a commit hash to the pip-requires line ... so I think we're making good progress there21:51
danwentprops to salvatore for some great docs :)21:51
troytomanmtaylor: looks like it. so we'll hope that plays out21:51
troytomantrying to see if we'll be ready to do an E-2 release or wait for E-321:51
troytomanotherwise, we're moving forward21:52
ttxtroytoman: for the first one feel free to do an out of band release/tag, no need to sync on the same date21:52
ttxAny other team lead with a status report ?21:52
wwkeyboarddanwent: those non-standard error codes have already caused bugs in nova, I can't imagine what they are going to do for our consumers.21:52
*** primeministerp has joined #openstack-meeting21:53
*** AlanClark has quit IRC21:53
troytomanttx: sounds good21:53
ttxtroytoman: I mean, if you're ready one day after the E2 date, go for it and tag it E2 :)21:53
ttxdon't wait 6 weeks.21:53
Vekyeah, "Policy not Fulfilled" != "NetworkNotFound"21:53
danwentwwkeyboard: I definitely understand.  I'll chat with Salvatore about this for the next rev of the API.21:53
ttxCI / doc / stable / packagers ?21:54
wwkeyboarddanwent: thank you! let me know what I can do to help21:54
ttxmtaylor: if you have anythin to announce, go for it21:54
mtaylorstuff rocks21:55
ttxOtherwise I'll switch to open discussion.21:55
ttx#topic Open discussion21:55
*** openstack changes topic to "Open discussion"21:55
ttxIf you are around Brussels in February, please submit talks to the FOSDEM "Open Source Virtualization and Cloud" devroom21:55
ttxWe want OpenStack to be all over it21:55
ttx#info please submit talks to the FOSDEM "Open Source Virtualization and Cloud" devroom21:56
ttx#link https://lists.fosdem.org/pipermail/fosdem/2011-November/001354.html21:56
ttxAnything else, anyone ?21:56
ttxI guess not.21:58
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"21:58
openstackMeeting ended Tue Dec  6 21:58:12 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-06-21.01.html21:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-06-21.01.txt21:58
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-06-21.01.log.html21:58
*** jk0 has left #openstack-meeting21:58
ttxThanks everyone !21:58
*** jwalcik has left #openstack-meeting21:58
*** mikeyp has left #openstack-meeting21:58
*** Vek has left #openstack-meeting21:58
*** nati2 has quit IRC21:59
*** mcohen_ has joined #openstack-meeting21:59
*** mcohen has quit IRC21:59
*** mcohen_ is now known as mcohen21:59
danwenthello netstackers!22:00
bhallhey :)22:00
*** mcohen has quit IRC22:00
*** AlanClark has joined #openstack-meeting22:00
openstackMeeting started Tue Dec  6 22:00:55 2011 UTC.  The chair is danwent. Information about MeetBot at http://wiki.debian.org/MeetBot.22:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.22:00
danwent#link  Agenda: http://wiki.openstack.org/Network/Meetings22:01
*** markmc has left #openstack-meeting22:01
danwent#status melange status22:01
danwent#topic melange status22:01
*** openstack changes topic to "melange status"22:01
danwentman, did it again :)22:01
danwentI need to stop typing exactly what I'm thinking22:01
troytomanhave the code in github/gettit now22:02
troytomanspent this week working on docs and notifications22:02
danwentis gettit like gerrit but doesn't suck?22:02
*** edconzel has quit IRC22:02
troytomanunfortunately it still sucks. just more tolerant of typos22:02
troytomanwe're hoping to cut an initial release as close to E-2 as possible.22:03
danwentbtw, on the docs.  are you planning any kind of an "admin guide" (per Anne Gentel's email?)22:03
danwentwow, sweet.  that's a great turn-around time.22:03
troytomanI would say I intend to do one. but don't have it planned :-)22:03
troytomani think most of the basic functionality we view as necessary is now there.22:04
danwentfair enough.  when you do, definitely get a oxygen license from Anne… makes creating docbook much easier22:04
troytomanotherwise, we would love to get more feedback and involvement if anyone is interested.22:04
danwentgreat, and to confirm, the right place for people to ask questions is on launchpad: https://answers.launchpad.net/melange22:04
*** thingee has left #openstack-meeting22:05
*** mcohen has joined #openstack-meeting22:05
*** SumitNaiksatam has joined #openstack-meeting22:05
troytomanyes. already had our first question asked and answered.22:05
danwentanything else on melange?  any questions?22:05
*** shwetaap has joined #openstack-meeting22:06
danwent#topic quantum status22:06
*** openstack changes topic to "quantum status"22:06
danwentOk, a lot of get done for essex-2, which branches in a week.22:06
*** edgarmagana has joined #openstack-meeting22:06
danwentParticularly, we have a lot of reviews to take care of.  Salv's framework review just needs ying and I to do a quick re-review.22:06
danwentbut there's also the operational status code, which just arrived for review22:07
danwent#link: please focus on reviews for e-2: https://review.openstack.org/#q,status:open+project:openstack/quantum,n,z22:07
danwentas well as a host of other smaller reviews for bugs we need squashed.22:07
danwentany reviews folks feel a need to call out in partcular?22:08
salvapi-framework-essex is still out for review...22:08
bhalla few of the ones in the list you just pointed to are small22:08
danwentsalv: yup.  I will re-review, and hopefully ying can as well.  Your changes since last review were pretty small right?  I remember only minor nits on the code.22:09
*** debo-os has joined #openstack-meeting22:09
salvThe diff between the last two changsets is less than 20 lines22:09
danwentsalv:  thanks for sending out email on operational status.  Anything else to add on that feature.  To confirm, we're pushing API filters to e-3, so no need to review.22:10
salvconfirming filters for e-3. Discussion to be started on mailing list this week.22:10
danwentgreat, thanks.22:10
salvOperational status is not yet explicitly supported in CLI.22:10
danwentI see carlp lurking, not sure if he's around22:11
salvBut that's another story...22:11
danwentsalv: yes, agreed with that point on the email.22:11
*** joesavak has quit IRC22:11
danwentOk, on the jenkins setup, I haven't heard back from carlp and the bug was stuck in "unknown", so I'm bumping that item and my bug blocked on it to e-3, thought I'd REALLY love to get jenkins up and running soon.22:12
danwent#TODO  #danwent contact #carlp about jenkins integration for quantum22:12
danwentbhall, nova-parity for L3, NAT, and metadata server are in nova now, correct?22:12
bhallall in22:13
danwentI will be bugging you about documenting that as well :)22:13
danwentin the admin guide22:13
*** mencken has joined #openstack-meeting22:13
bhallok, no prob22:13
danwentIs edgar here?22:14
edgarmaganaI am here!22:14
danwentHi, can you give an update on your blueprint?  status is still 'started' and branching date is one week out.  if its a big patch, may be hard to review in time.22:14
edgarmaganai have the code almost ready22:15
edgarmaganakeep testing some functionality, this is not conflicting with any other module, so it should be an easy review22:15
danwentok, great.22:15
danwentbest to have tests included as well, if possible.22:15
*** primeministerp has quit IRC22:16
edgarmaganaof course, wait for the check in between today and tomorrow22:16
danwentand finally, there are a LOT of open bugs for e-2.  this is a good thing, as it means people are really using (and breaking quantum)22:16
danwenthopefully a lot of them are already in review, but if there's a bug assigned to you, please update it indicating that you are still targeting for e-2, or move it to e-3 if you won't make it.22:17
danwentAny critical issues anyone needs to call out?22:17
danwentOk, that should be it for e-2.  There are a couple other issues in the agenda for quantum22:18
danwentfirst, as discussed last week with mtaylor, we need to figure out our strategy for whether we are going to split quantum into multiple repos.22:18
*** dwcramer has quit IRC22:19
salvbefore deciding on a strategy let's decide whether we want to split the repos or not! :)22:19
mtaylordanwent: re that: we've got openstack.common going now - so perhaps quantum.common can live there?22:20
danwentwe can have the detailed discussion on the ML, but the high-level options seem to be (1) keep as is, all one repo (2) split into two repos, client and server, but potentially duplicate the little bits of shared code and (3) split into three repos, client, server, and common22:20
salvSplitting in which way exactly? client and server components?22:20
danwentmtaylor: I was thinking something very similar myself, if we decide to go with #222:20
danwentsalv: up for discussion22:20
danwent#TODO: #danwent, start ML thread for splitting repos, include #mtaylor as well22:21
bhallmy vote is for #2  (client and "the rest")22:21
mtaylor#2 with some elements in openstack.common would be the thing that matches the other projects more closely22:21
danwentif anyone else wants to comment now, go ahead, otherwise i'll forward this content to start a thead on the ML22:21
danwenton an unrelated topic, there was some confusion in a blog post that I wanted to clarify.  Quantum applied for incubation status just prior to the Essex development period, so Quantum will not be "core" for the main Essex release.22:22
bhalldo you have a link to the blog post?22:23
danwentwe can (and I think should) apply to be core for the F-series.22:23
danwentRob was nice enough to correct this already.22:23
*** anotherjesse has quit IRC22:24
*** netstack has joined #openstack-meeting22:25
danwentand lastly, I just started a thead on the ML to discuss whether we should consider shifting to more standardized HTTP error code for our API.  wwkeyboard mentioned this during the nova meeting.22:25
*** dolphm_ has quit IRC22:25
danwentOk, any other discussion for Quantum, or open discussion?22:25
salvThanks for sending email on the ML for error codes.22:25
salvThis was one of my dilemmas during the implementation of API 1.022:25
danwentsalv: I wasn't sure of the original motivation, so I guessed.  If I was wrong, please correct me.22:25
salvmotivation is more than correct, but it is also true that people don't want to mess with codes they don't understand. Anyway, I'm more than happy to tackle this issue,22:26
danwentsalv:  great.  and wwkeyboard said he might pitch in as well.22:27
salvThat would be great22:27
wwkeyboarddanwent: salv, I'm brewing an response email with some suggestions,22:27
danwentOk, so please review, review, review this week, and don't forget to participate in the ML discussions.22:28
wwkeyboardI'd like to continue the discussion, but I don't have answers for all of those status codes22:28
danwentAlso, I should point out that somik sent an email out for review on a simple Authz proposal22:28
salvwwkeyboard: thanks!22:28
danwentand that debo-os is planning on sending one out soon on nova-parity-vpn work.22:28
danwentk, have a good week folks!22:28
*** anotherjesse has joined #openstack-meeting22:28
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"22:29
openstackMeeting ended Tue Dec  6 22:29:00 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-06-22.00.html22:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-06-22.00.txt22:29
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-06-22.00.log.html22:29
*** anotherjesse has quit IRC22:29
*** KyleM1 has left #openstack-meeting22:29
salvthanks, have a good one!22:29
*** GheRivero_ has quit IRC22:29
*** netstack has quit IRC22:30
*** anotherjesse has joined #openstack-meeting22:31
*** jog0 has left #openstack-meeting22:32
*** hub_cap has quit IRC22:34
*** danwent has quit IRC22:37
*** heckj has quit IRC22:40
*** edgarmagana has quit IRC22:45
*** shwetaap has left #openstack-meeting22:47
*** bcwaldon has quit IRC22:50
*** nati2 has joined #openstack-meeting22:55
*** bcwaldon has joined #openstack-meeting23:02
*** mcohen has quit IRC23:03
*** bcwaldon has quit IRC23:06
*** tcampbell has joined #openstack-meeting23:08
*** davelap has quit IRC23:12
*** Ravikumar_hp has quit IRC23:12
*** dwcramer has joined #openstack-meeting23:13
*** tcampbell has quit IRC23:16
*** anotherjesse has quit IRC23:22
*** anotherjesse has joined #openstack-meeting23:23
*** anotherjesse has quit IRC23:27
*** patelna has quit IRC23:36
*** dwcramer has quit IRC23:37
*** KyleM1 has joined #openstack-meeting23:38
*** KyleM1 has left #openstack-meeting23:38
*** hub_cap has joined #openstack-meeting23:43
*** hub_cap has quit IRC23:43
*** GheRivero_ has joined #openstack-meeting23:44
*** Guest35219 has quit IRC23:47
*** mattray has quit IRC23:49
*** troytoman is now known as troytoman-away23:50
*** GheRivero_ has quit IRC23:51
*** zns has quit IRC23:51
*** mcohen has joined #openstack-meeting23:52
*** anotherjesse has joined #openstack-meeting23:54
*** tech__ has quit IRC23:58

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