Tuesday, 2011-07-05

*** adjohn has joined #openstack-meeting01:11
*** msinhore has joined #openstack-meeting01:26
*** msinhore has quit IRC01:41
*** msinhore has joined #openstack-meeting02:14
*** msinhore1 has joined #openstack-meeting10:01
*** msinhore has quit IRC10:02
*** adjohn has quit IRC10:06
*** adjohn has joined #openstack-meeting11:09
*** adjohn has quit IRC11:09
*** adjohn has joined #openstack-meeting11:10
*** _adjohn has joined #openstack-meeting11:10
*** adjohn has quit IRC11:10
*** _adjohn is now known as adjohn11:10
*** _adjohn has joined #openstack-meeting11:11
*** adjohn has quit IRC11:11
*** _adjohn is now known as adjohn11:11
*** _adjohn has joined #openstack-meeting11:12
*** adjohn has quit IRC11:12
*** _adjohn is now known as adjohn11:12
*** _adjohn has joined #openstack-meeting11:13
*** adjohn has quit IRC11:13
*** _adjohn is now known as adjohn11:13
*** _adjohn has joined #openstack-meeting11:13
*** adjohn has quit IRC11:13
*** _adjohn is now known as adjohn11:13
*** msinhore1 has quit IRC11:14
*** adjohn has quit IRC11:14
*** adjohn has joined #openstack-meeting11:14
*** adjohn has quit IRC11:14
*** adjohn has joined #openstack-meeting11:15
*** adjohn has quit IRC11:15
*** _adjohn has joined #openstack-meeting11:15
*** adjohn has joined #openstack-meeting11:16
*** _adjohn has quit IRC11:16
*** _adjohn has joined #openstack-meeting11:17
*** adjohn has quit IRC11:17
*** _adjohn is now known as adjohn11:17
*** adjohn has quit IRC11:17
*** adjohn has joined #openstack-meeting11:17
*** adjohn has quit IRC11:18
*** adjohn has joined #openstack-meeting11:18
*** adjohn has quit IRC11:19
*** adjohn has joined #openstack-meeting11:19
*** _adjohn has joined #openstack-meeting11:20
*** adjohn has quit IRC11:20
*** _adjohn is now known as adjohn11:20
*** adjohn has quit IRC11:20
*** adjohn has joined #openstack-meeting11:20
*** adjohn has quit IRC11:21
*** adjohn has joined #openstack-meeting11:51
*** adjohn has quit IRC11:52
*** adjohn has joined #openstack-meeting11:52
*** adjohn has quit IRC11:52
*** adjohn has joined #openstack-meeting11:53
*** adjohn has joined #openstack-meeting11:53
*** adjohn has quit IRC11:54
*** adjohn has joined #openstack-meeting11:54
*** adjohn has quit IRC11:55
*** adjohn has joined #openstack-meeting11:55
*** adjohn has quit IRC11:55
*** adjohn has joined #openstack-meeting11:55
*** adjohn has quit IRC11:56
*** adjohn has joined #openstack-meeting11:56
*** _adjohn has joined #openstack-meeting11:57
*** adjohn has quit IRC11:57
*** _adjohn is now known as adjohn11:57
*** _adjohn has joined #openstack-meeting11:58
*** adjohn has quit IRC11:58
*** _adjohn is now known as adjohn11:58
*** adjohn has joined #openstack-meeting11:58
*** _adjohn has joined #openstack-meeting11:59
*** adjohn has quit IRC11:59
*** _adjohn is now known as adjohn11:59
*** _adjohn has joined #openstack-meeting12:00
*** adjohn has quit IRC12:00
*** _adjohn is now known as adjohn12:00
*** _adjohn has joined #openstack-meeting12:00
*** adjohn has quit IRC12:00
*** _adjohn is now known as adjohn12:00
*** adjohn has quit IRC12:01
*** adjohn has joined #openstack-meeting12:01
*** adjohn has quit IRC12:01
*** adjohn has joined #openstack-meeting12:02
*** adjohn has quit IRC12:02
*** adjohn has joined #openstack-meeting12:33
*** adjohn has quit IRC12:33
*** _adjohn has joined #openstack-meeting12:34
*** adjohn has joined #openstack-meeting12:34
*** adjohn has joined #openstack-meeting12:35
*** Binbin has joined #openstack-meeting12:35
*** adjohn has quit IRC12:35
*** adjohn has joined #openstack-meeting12:36
*** adjohn has quit IRC12:36
*** _adjohn has joined #openstack-meeting12:36
*** adjohn has joined #openstack-meeting12:37
*** adjohn has joined #openstack-meeting12:38
*** adjohn has quit IRC12:38
*** adjohn has joined #openstack-meeting12:38
*** adjohn has joined #openstack-meeting12:39
*** _adjohn has joined #openstack-meeting12:40
*** adjohn has quit IRC12:40
*** _adjohn is now known as adjohn12:40
*** _adjohn has joined #openstack-meeting12:40
*** adjohn has quit IRC12:40
*** _adjohn is now known as adjohn12:40
*** adjohn has joined #openstack-meeting12:41
*** adjohn has joined #openstack-meeting12:42
*** adjohn has joined #openstack-meeting12:42
*** _adjohn has joined #openstack-meeting12:43
*** adjohn has quit IRC12:43
*** _adjohn is now known as adjohn12:43
*** _adjohn has joined #openstack-meeting12:44
*** adjohn has quit IRC12:44
*** _adjohn is now known as adjohn12:44
*** _adjohn has joined #openstack-meeting12:44
*** adjohn has quit IRC12:44
*** _adjohn is now known as adjohn12:44
*** _adjohn has joined #openstack-meeting12:45
*** adjohn has quit IRC12:45
*** _adjohn is now known as adjohn12:45
*** _adjohn has joined #openstack-meeting12:46
*** adjohn has quit IRC12:46
*** _adjohn is now known as adjohn12:46
*** _adjohn has joined #openstack-meeting12:46
*** adjohn has quit IRC12:46
*** _adjohn is now known as adjohn12:46
*** adjohn has quit IRC12:47
*** adjohn has joined #openstack-meeting12:47
*** adjohn has joined #openstack-meeting12:48
*** adjohn has joined #openstack-meeting12:48
*** adjohn has joined #openstack-meeting12:49
*** _adjohn has joined #openstack-meeting12:50
*** adjohn has quit IRC12:50
*** _adjohn is now known as adjohn12:50
*** adjohn has quit IRC12:50
*** adjohn has joined #openstack-meeting12:50
*** adjohn has quit IRC12:51
*** adjohn has joined #openstack-meeting12:51
*** _adjohn has joined #openstack-meeting12:52
*** adjohn has quit IRC12:52
*** _adjohn is now known as adjohn12:52
*** adjohn has quit IRC12:53
*** adjohn has joined #openstack-meeting12:53
*** adjohn has joined #openstack-meeting12:53
*** _adjohn has joined #openstack-meeting12:54
*** adjohn has quit IRC12:54
*** _adjohn is now known as adjohn12:54
*** adjohn has joined #openstack-meeting12:55
*** adjohn has joined #openstack-meeting12:55
*** _adjohn has joined #openstack-meeting12:56
*** adjohn has quit IRC12:56
*** _adjohn is now known as adjohn12:56
*** adjohn has joined #openstack-meeting12:57
*** adjohn has joined #openstack-meeting12:57
*** adjohn has quit IRC12:58
*** msinhore has joined #openstack-meeting13:09
*** dprince has joined #openstack-meeting13:38
*** jkoelker has joined #openstack-meeting14:03
*** adjohn has joined #openstack-meeting14:07
*** adjohn has quit IRC14:17
*** vladimir3p has joined #openstack-meeting14:22
*** creiht has joined #openstack-meeting14:39
*** dprince has quit IRC14:46
*** heckj has joined #openstack-meeting14:59
*** mdomsch has joined #openstack-meeting15:15
*** Binbin has quit IRC15:25
*** ohnoimdead has joined #openstack-meeting17:07
*** reidrac has joined #openstack-meeting17:18
*** med_out is now known as medberry17:30
*** nati has joined #openstack-meeting17:54
*** nati has quit IRC18:01
*** nati has joined #openstack-meeting18:01
*** mrmartin has joined #openstack-meeting18:06
*** shwetaap has joined #openstack-meeting18:08
*** Shubhangi has joined #openstack-meeting18:09
*** dprince has joined #openstack-meeting18:21
*** Shubhangi has quit IRC18:27
*** jakedahn has joined #openstack-meeting18:51
*** shwetaap has quit IRC19:03
*** shwetaap has joined #openstack-meeting19:03
natiCI Meeting?19:03
*** sai has joined #openstack-meeting19:04
*** Shubhangi has joined #openstack-meeting19:04
*** nati has left #openstack-meeting19:08
*** nati has joined #openstack-meeting19:08
saihi19:09
sorenmtaylor: ping?19:09
*** spectorclan_ has joined #openstack-meeting19:09
mtaylorsoren: pong19:10
mtayloroh! hey - it's meeting time :)19:10
mtaylor(darned timezones)19:10
sorenThere's supposed to be a...19:10
ttxit's your meeting dude :19:10
sorenright.19:10
sorenthat19:10
soren :)19:10
mtaylorsorry - I got distracted talking to ttx. I blame him19:10
termiezingaling19:10
nati:D19:10
mtaylor#startmeeting19:10
openstackMeeting started Tue Jul  5 19:10:55 2011 UTC.  The chair is mtaylor. Information about MeetBot at http://wiki.debian.org/MeetBot.19:10
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.19:10
mtaylor#topic CI Meeting19:11
*** openstack changes topic to "CI Meeting"19:11
*** dendrobates is now known as dendro-afk19:11
mtaylorhey everybody - I'm assuming we've got some folks in here and stuff?19:11
mtaylorhi nati19:11
dprinceyo19:12
mtaylorhey dprince19:12
natihi mtaylor19:12
spectorclan_just watching from the background19:12
mtaylorexcellent19:12
mtaylorso - first things first - let's check in on stuff from last time19:12
mtaylor#topic Actions from last meeting19:12
*** openstack changes topic to "Actions from last meeting"19:12
mtaylordprince: you got the openstack_vpc job added and running. so, w00t!19:13
*** markvoelker has joined #openstack-meeting19:13
dprincemtaylor: Yep. I think we can mark that completed.19:13
mtayloragree!19:13
mtaylorcan we add a new action for getting the tests run through nosexunit and returning the xml?19:14
dprincemtaylor: So like we talked late last week I had to add a sleep to the job to get around this issue: https://bugs.launchpad.net/nova/+bug/80431719:14
uvirtbotLaunchpad bug 804317 in nova "FixedIpNotFoundForInstance: Instance 1 has zero fixed ips." [Undecided,Incomplete]19:14
mtayloryes. do we have anybody on the nova side of things working on a real fix for that?19:14
dprinceEssentially after the multi_nic merge nova-network has to run a periodic task at least once before the network is set.19:15
dprinceI'll take it.19:15
mtaylorsweet19:15
dprinceOr at least I'll argue for it.19:15
mtaylorttx marked it as incomplete... ttx, do you hate us?19:15
dprinceAnd yes. Lets have another task for the nosexunit stuff.19:15
ttxI do. Let me check that.19:15
mtaylor#action dprince Have smoketests return xunit file via nosexunit19:15
dprinceYeah. I saw he marked it incomplete. I can refile in a more cleanly worded ticket perhaps?19:16
mtaylor#action dprince fight with ttx over fixing bug 80431719:16
uvirtbotLaunchpad bug 804317 in nova "FixedIpNotFoundForInstance: Instance 1 has zero fixed ips." [Undecided,Incomplete] https://launchpad.net/bugs/80431719:16
ttxdprince: marked it incomplete because tr3buchet seemed to consider it was normal behavior19:16
ttxso it didn't seem everyone agreed it was something to be fixed :)19:17
dprinceSure. I'll vet the idea a bit more.19:17
dprinceMy options are sleep. Or edit the DB manually.19:17
mtaylorttx: well - in _some_ manner we need to be able to smoketest things without adding in a "sleep 1" call :)19:17
dprinceI'd prefer to do this via a nova-manage command.19:17
ttxThough your comment #2 makes sense.19:17
ttxrigth. I can confirm/wishlist it19:18
dprinceAdditionally I think some end users will want a preset option as well.19:18
ttxdoing so right now. /me hates incomplete bugs anyway.19:18
mtayloryay!19:18
mtaylordprince: look at that - one of your actions for next week is done already!19:18
mtaylor:)19:18
dprinceYep. progress already.19:18
ttxalso note that the bug triaging game is a game that everybody is allowed to play. It's not just me.19:18
ttxI'm doing it because almost nobody else does, boohoohoo19:18
mtaylorso - next on the list is mtaylor jenkins job for the PXE boot goodness19:19
dprincettx: we just value your oppinion.19:19
natiThank you for your work! :ttx19:19
* ttx pads himself in the back19:19
* dprince and by oppinion I really mean opinion19:19
mtaylorI had a meeting at rackspace last week with the folks from rcb in san fran (including termie, since he's in the meeting here)19:20
*** dendro-afk is now known as dendrobates19:20
mtaylorand it came out that it makes _way_ more sense to have them set up the bare metal deploy infrastructure that we'll just trigger from our jenkins (otherwise we were duplicating efforts)19:20
naticool19:21
mtaylorso this is still outstanding, but we have a whole new approach to it ... termie, are you a point person for that?19:21
termiemtaylor: oui19:21
mtaylortermie: sweet - mind if I mark you down with an action of getting that spun up for this week?19:22
termiesure19:22
mtaylor#action termie finish work on bare-metal testing deployment19:22
*** dabo has joined #openstack-meeting19:22
mtaylorsweet. if we don't watch out - we're going to have progress around this joint19:22
sorenIt'll pass.19:23
*** johnpur has joined #openstack-meeting19:23
* soren <- optimist19:23
mtaylorI'll burn through the next ones real quick19:23
mtaylormtaylor fork griddynamics/openstack-rhel into openstack/openstack-rhel - done19:23
mtaylortalk with Novel/MSFT Interop guys about an OBS build profile run from our jenkins - not done - kept playing phone tag with peter (mostly my fault or the fault of our offsite meeting)19:23
mtaylor#action mtaylor connect with Peter from Novel/MSFT lap about OBS builds19:24
mtaylor#action mtaylor connect with Peter from Novel/MSFT lap about hyperV testing19:24
mtaylormtaylor coordinate with Mihai from rPath to get him what he needs for getting the rPath builder up and going19:24
mtaylorI spoke with mihai and we had a plan for this - but then last week everything changed with the machines we're using and the approach we're looking at across the board for testing different deployment options19:25
mtaylorso I need to re-discuss with hium19:25
mtaylor#action talk to Mihai about new options for rPath testing19:25
mtaylorand I did none of the rest of the pinging - so I'll need to do that this week ... but will probably loop in termie as well so that we can make a good plan for what that might look like19:26
mtaylor#action mtaylor ping ewanmellor about testing esx and vsphere19:26
mtaylor#action mtaylor ping community at large about lxc testing19:26
mtaylor#action mtaylor ping reddwarf team about openvx/lxc testing19:26
mtayloralright - so that was fun19:26
mtaylor#topic Update on status of bare metal testing changes from last week19:27
*** openstack changes topic to "Update on status of bare metal testing changes from last week"19:27
mtaylorso - the only other thing I've got on this weeks agenda before open discussion was just to do an update on last week's conversations so that interested folks can be looped in19:27
mtaylorbefore last week, the idea was that I had a chunk of machines and was working on the deployment of openstack on them for automated testing19:28
mtaylorturns out - my lovely colleagues in san francisco are not only working on the same thing, it's what they do and they already have it working19:28
mtaylortherefore, in the interest of sanity, we decided it made the most sense to hand the machines over to them and have them do their deployment thing and hand me a jenkins slave ...19:29
dprincemtaylor: how many machines is it?19:29
mtaylorwhich, incidentally, is the exact same approach that we would take with novell/msft and the hyperv lab - so I think we have a consistent approach to how we handle hardware setups people want tested19:30
mtaylordprince: 10 machines at the moment - we're working on requisitioning a different set of machines though (also, hopefully 10 machines)19:30
nati consistent approach+19:30
westmaasmtaylor: sorry I came in a little late, but whats the config on this set of 10 machines?19:31
westmaaswhich hypervisor, in particular, I mean/19:31
mtaylorwestmaas: right now it's just 10 boxes ... termie - any thoughts on hypervisor you guys are going to attack first?19:31
mtaylorwestmaas: (actually, I eventually would love to get both a xenserver and a kvm hypervisor test up and going with our machines ... but I'll defer to termie there on what's sensible, if we know yet)19:32
termiewe always start with kvm19:32
termiexenserver requires the knowledge and love of somebody else19:33
dprinceTermie: I've got a good start on some XenServer Cookbooks if you want to see them.19:33
dprincetermie: Wnat are you using for config mgmt?19:33
mtaylormight it make sense to loop in with someone from rax cloud servers and get them to provide a set of machines + jenkins slave for xenserver deployments?19:33
mtayloror dprince perhaps :)19:34
termiemtaylor: probably, that just isn't my focus at the moment19:34
mtaylortermie: agree19:34
termiedprince: we're using both chef and puppet at current19:34
dprincemtaylor: I'm up for the task. Not sure I'm in a position to volunteer my time. Feel free to assign it to me and I'll get back to you.19:34
* mtaylor is sort of thinking that the stakeholders who want a particular thing tested should make sure that we get an environment on which we can run tests19:35
termiedprince: we generally prefer chef, but we had some customer reqs that ended up putting puppet back onto our plates19:35
dprincemtaylor: very interested in seeing it done.19:35
mtaylordprince: cool - I'll put you down for it and then see if we can find internal rax motivation for ensuring you have the resources you need19:35
dprincetermie: I was wondering why you guys started getting cranking on the Puppet. Thanks. Good to see both.19:35
mtaylor#action dprince investigate getting a xenserver-based bare-metal deploy up and going for CI purposes19:36
mtaylor#action mtaylor bug people in management to get dprince resources19:36
mtayloractually, speaking of that action19:36
dprincetermie: In case you are interested... https://github.com/dprince/openstack_cookbooks/tree/master/cookbooks/xenserver19:37
*** vladimir3p_ has joined #openstack-meeting19:37
dprincetermie: There is more work to be done there but it is a good start.19:37
termiecoolio19:37
mtayloranything else on that topic? or I'll open things up for general discussion19:38
natiso which puppet recipes we use?19:38
natifor baremetal setup19:38
dprincenati: you might check out the cloud builders puppet scripts: https://github.com/cloudbuilders/openstack-puppet19:39
dprincenati: I haven't tried them myself but they seem to be the furthest along.19:39
*** vladimir3p has quit IRC19:39
natiThank: dprince19:39
natiI got another one. https://github.com/puppetlabs/puppetlabs-openstack19:40
mtaylornati: yes, I believe that is what is being used right now - there was discussion about getting that work integrated in with the stuff from the guys at puppetlabs eventually19:40
mtaylornati: sorry - I mean, I believe https://github.com/cloudbuilders/openstack-puppet  is the one being used, and there is an eventual todo for someone to get that integrated with https://github.com/puppetlabs/puppetlabs-openstack19:40
natiI got it19:40
mtaylorsweet19:41
natiso this branch may be a official puppet recipes?19:41
mtaylor#topic Open Discussion19:41
*** openstack changes topic to "Open Discussion"19:41
mtaylornati: perhaps not 100% related to CI itself, but since it's testing related... there is a guy at Dell wanting to do work on increasing test coverage and coordinating work on writing new tests ... I told him he should definitely talk with you about that19:43
mtaylornati: I believe dprince is also talking with him19:44
dprincemtaylor: Is that Dean? We are talking to him on Thursday right?19:44
mtaylordprince: yes. that's him19:44
natiYes, I agree with you19:45
natiPersonally speaking, there are several dep tools, and I think we need a offial dep tool ..19:45
naticool19:45
mtaylornati: can you define dep tool for me in this context?19:45
mtaylor#action mtaylor and dprince will discuss testing with Dean from Dell19:46
natiautomated openstack deploy tool19:46
mtaylorah - well, that's some of the stuff termie and folks are working on19:46
naticool19:46
termieaye, working on that right this moment, actually19:47
natiis there some docs of your work? :termie19:47
termienati: nope19:48
termienati: i am making the tool19:48
naticobbler + puppet?19:48
natior cobbler + chef?19:48
*** stevezd has joined #openstack-meeting19:49
termiedunno yet, still digging through the existing stuff19:49
termiewe've previously done pxe + preseed + chef19:49
mtaylorvishy had also mentioned something about looking at orchestra+puppet, but don't know if that will make sense or be helpful19:49
termieit isn't going to be helpful today19:49
termiemaybe next week once we have the basics moving19:49
natiI got it, thank you for your information19:50
mtaylortermie: speaking of - did you get my email with the wrap up of what I had moving on that box? I can't remember if I copied you on it or not19:50
termiemtaylor: i don't think so19:50
mtaylortermie: k. I'll go find and send it your way in case any of it is useful at all19:51
termiegeneral fyi, a bunch of work went into parts of these over the last week but it is all jumbled at the moment19:51
termiewhich is why i don't have a lot of specific info19:51
termiedigging it out of the people who were working on it19:51
mtaylorsweet19:52
mtaylork. sent19:53
mtayloralright ... anybody got anything else CI related they want to talk about?19:53
mtaylorok. in that case - I'm going to say that we're done - and early even!19:55
mtaylor#endmeeting19:55
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"19:55
openstackMeeting ended Tue Jul  5 19:55:19 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-07-05-19.10.html19:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-07-05-19.10.txt19:55
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-07-05-19.10.log.html19:55
*** zns has joined #openstack-meeting19:55
*** nati has quit IRC19:57
*** nati has joined #openstack-meeting19:58
*** jbryce has joined #openstack-meeting20:00
notmynamejbryce: do we have a meeting today or not?20:01
*** reidrac has left #openstack-meeting20:02
jbrycenotmyname: not this week20:02
*** Shubhangi has quit IRC20:05
*** ohnoimdead_ has joined #openstack-meeting20:08
*** dprince has quit IRC20:09
*** ohnoimdead has quit IRC20:11
*** ohnoimdead_ is now known as ohnoimdead20:11
*** zns has left #openstack-meeting20:11
*** ohnoimdead has quit IRC20:12
*** nati has quit IRC20:13
*** jbryce has quit IRC20:19
*** jbryce has joined #openstack-meeting20:19
*** sai has left #openstack-meeting20:22
*** dendrobates is now known as dendro-afk20:25
*** mdomsch has quit IRC20:27
*** nati has joined #openstack-meeting20:27
*** Mandell has joined #openstack-meeting20:29
*** danwent has joined #openstack-meeting20:33
*** nati has quit IRC20:37
*** nati has joined #openstack-meeting20:37
*** joearnold has joined #openstack-meeting20:38
*** ohnoimdead has joined #openstack-meeting20:44
*** ohnoimdead has quit IRC20:44
*** ohnoimdead has joined #openstack-meeting20:44
*** alandman has joined #openstack-meeting20:46
*** troytoman-away is now known as troytoman20:49
*** Vek has joined #openstack-meeting20:50
*** cynb has joined #openstack-meeting20:50
*** jk0 has joined #openstack-meeting20:50
*** jaypipes has joined #openstack-meeting20:52
*** bidt has joined #openstack-meeting20:53
*** carlp has quit IRC20:53
*** bidt has quit IRC20:54
*** User518 has joined #openstack-meeting20:56
*** Tushar has joined #openstack-meeting20:56
*** mattt has joined #openstack-meeting20:57
*** johan_-_ has joined #openstack-meeting20:57
*** bcwaldon has joined #openstack-meeting20:59
*** rdc has joined #openstack-meeting20:59
ttxo/20:59
* Vek waves back21:00
markvoelkero/21:00
dabo \021:00
cynbhola21:00
soreno/21:00
ttxnotmyname, vishy, jaypipes: ?21:00
notmynameyar21:00
jaypipesttx: o/21:01
ttxI know vishy is not very far away, so let's start.21:02
vishyo/21:02
jaypipeswe at 4pm EDT now? .. hmm. have to update my calendar.21:02
ttxdidn't think he was that close, though :)21:02
ttx#startmeeting21:02
openstackMeeting started Tue Jul  5 21:02:26 2011 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.21:02
vishyit is 5 EDT right now....21:02
ttxMeeting is at 21 UTC21:02
ttxI don't even want to know about this EDT thing21:03
ttxToday's agenda is at:21:03
ttx#link http://wiki.openstack.org/Meetings/TeamMeeting21:03
*** comstud has joined #openstack-meeting21:03
ttx#topic diablo-2 postmortem21:03
*** openstack changes topic to "diablo-2 postmortem"21:03
jaypipesvishy: doh! still had my time set to San Antonio! :(21:03
*** Shubhangi has joined #openstack-meeting21:03
ttxtravel fail21:03
*** littleidea has joined #openstack-meeting21:03
ttxLast week we released diablo-2, and for the first time there were fixes committed to the milestone-proposed branch21:03
ttxThe branches proposed for merging into milestone-proposed were reviewed by core teams, which caused confusion (since the branch was already reviewed for its trunk inclusion)21:04
ttxSo we decided that the milestone-proposed merge should be reviewed by another team21:04
ttxand only accepted if (1) it made it to trunk first and (2) it was considered milestone-critical21:04
ttx(so the core teams still control the quality of what gets in)21:04
ttxThe team in charge of that is openstack-release (me, soren + PTLs), so the core teams should not be bothered by double reviews again21:05
ttxAny question or comment on how we handled diablo-2, or how we can improve the process ?21:05
*** ryu_ishimoto has joined #openstack-meeting21:05
jaypipesnope, the solution works for me...21:05
ttxthe process is mostly automated now, we need to cover the remaining gaps21:06
ttxsoren: btw, I worked on a script to do the LP "release" thing.21:06
ttxso nothing should be manual anymore21:06
*** salv-orlando has joined #openstack-meeting21:06
ttx#topic Swift status21:07
*** openstack changes topic to "Swift status"21:07
ttxnotmyname: howdy21:07
notmynamehowdy21:07
ttxnotmyname: So at this point we are still planning on 1.4.2 release on July 20th ?21:07
notmynameperhaps. we're in the middle of discussions with you about making it more closely align with the other projects in version number and release date. there is no resolution yet, though21:07
notmynamebut either way, the date will be july 20-2921:08
ttxok21:08
ttxPlan at https://launchpad.net/swift/+milestone/1.4.2 looks in very good shape.21:08
ttxnotmyname: Other announcements or comments ?21:08
*** carlp has joined #openstack-meeting21:08
notmynameI don't think so.21:08
ttxQuestions on Swift ?21:09
*** spectorclan_ has quit IRC21:09
*** somik has joined #openstack-meeting21:09
ttx#topic Glance status21:09
*** openstack changes topic to "Glance status"21:09
ttxjaypipes: Hi!21:09
ttxLooking at: https://launchpad.net/glance/+milestone/diablo-321:09
ttxThat plan looks a bit optimistic, and D4 is pretty empty... Anything that should already be pushed back ?21:10
*** spectorclan_ has joined #openstack-meeting21:10
ttxjaypipes: ?21:11
* Vek guesses the jet lag is getting to jaypipes...21:11
comstudhe fell back into san antonio time.21:11
jaypipesttx: sorry... here now21:11
ttxcomstud: lol21:11
*** ameade has joined #openstack-meeting21:12
*** edconzel has joined #openstack-meeting21:12
*** renuka has joined #openstack-meeting21:12
jaypipesttx: keystone integration work is lagging a bit... I'll know by EOD tomorrow who/what team can pick up the slack on that. I will email you an update.21:12
ttxnobody is assigned to https://blueprints.launchpad.net/glance/+spec/glance-notifications, so it looks like a good D4 defer ?21:13
ttxunless someone picks it up ?21:13
jaypipesttx: yes, please do.21:13
ttxack21:13
jaypipesttx: now that the Nova notification stuff is done, should be fairly simple to emulate21:13
comstudjay: my team was trying to figure out if we were ready to do keystone/glance integration.. it's possible we could pick something up next sprint21:14
comstud(july 18th)21:14
ttxjaypipes: I'll wait for your update21:14
jaypipescomstud: yeah, I'll email you and gabe to chat about it.21:14
ttxjaypipes: Other announcements, comments ?21:14
jaypipesttx: no.21:14
ttxQuestions for the Glance PTL ?21:15
ttx#topic Nova status21:15
*** openstack changes topic to "Nova status"21:15
ttxvishy: yo!21:15
ttxLooking at: https://launchpad.net/nova/+milestone/diablo-321:15
ttxvishy: So the plan is ambitious, and I'm in the process of confirming with all assignees that they still think they can deliver21:16
ttxEveryone, let us know of anything in there that should be abandoned, or pushed back to D421:16
ttxWe already did a pass to adapt21:16
ttxWe should expect a lot of branch merges for this milestone, so the sooner we review, the better !21:17
ttxWith that in mind, would be good to give review time to:21:17
ttxhttps://code.launchpad.net/~nttdata/nova/block-migration/+merge/6466221:17
comstudRackspace Shared IP groups might be changing per something I heard earlier today21:17
comstudso that might be something that slips21:17
ttxanyone feeling like they know that area enough to review that ? It only got one (syntactic) review in 20 days.21:17
ttxcomstud: yes, I still need to sync with Ozone21:17
ttxcomstud: thanks for the headsup21:18
comstudttx: you'll probably want to sync with ed conzel from rackspace product21:18
comstud(i saw him join in here)21:18
*** Mandell has quit IRC21:18
comstud(fyi)21:19
edconzelyep21:19
edconzelshared IP group might be replaced with AffinityID21:19
ttxedconzel: what's the timeframe for the decision ? Would it still make the diablo-3 milestone ?21:20
comstudi have a guess that won't make diablo-3 due to it being up in the air21:20
edconzelfinal decision by 7/1321:20
ttxhmm, sounds a bit late to be written and merged for d3. We should probably retarget to D4... vishy ?21:21
vishyagreed21:22
edconzelok21:22
ttxthat doesn't mean work should not start on it asap21:22
edconzelagrred21:22
ttxjust that it would be merged early in D4 rather than late in D3 :)21:22
ttxso nobody feeling up to reviewing the block-migration stuff ? Looks like daily reviewers have been avoiding it like the plague21:23
ttxI'd rather not have it miss another milestone due to lack of reviews :)21:23
ttxIn related news, we also need an assignee for https://bugs.launchpad.net/nova/+bug/803654 -- since it's targeted to diablo-321:24
uvirtbotLaunchpad bug 803654 in nova "availability zone ignored when creating volume" [High,Confirmed]21:24
ttxAnyone interested ?21:24
*** edconzel has quit IRC21:24
comstudcurrent volume api can't really work with zones at all21:25
*** edconzel has joined #openstack-meeting21:25
ttxvishy: ^21:25
comstudif that's what that is21:25
comstudsince you have to create a volume.. and then later attach it21:25
vishythis is actually just ec2 zones21:25
comstud(to an instance)21:25
vishyold school zones21:25
comstudoops, just saw zones21:25
comstudok21:25
ttxhah terminology overload21:26
ttxok, I guess I'll ask for reviewers/takers on the ML, it usually works better21:26
ttx#action ttx to resurrect "stuff needing attantion" emails21:27
*** Shubhangi has quit IRC21:27
ttxvishy: anything else on your mind ?21:27
*** Shubhangi has joined #openstack-meeting21:28
ttxQuestions on Nova ?21:28
ttx#topic Open discussion21:29
*** openstack changes topic to "Open discussion"21:29
vishynope21:29
ttxannegentle asked me to tell everyone that "the Doc/web team meeting is moving to Mondays at 2000 UTC once a month, second Monday of the month".21:29
ttxThe calendar was updated21:29
spectorclan_Any developers wishing to participate in the 1 year OSCON video please contact me so I can work to get your 2 to 5 minute video. Thanks,21:29
carlpAny word if the location of the October summit was finalized?21:29
ttxspectorclan: ^21:30
spectorclan_carlp: It is b/w the Intercontinental Hotel or the Microsoft Research Lab but I think the hotel will win21:30
spectorclan_95% positive it is at the hotel21:30
spectorclan_October 3-521:30
*** MarkAtwood has joined #openstack-meeting21:30
carlpspectorclan, awesome, thanks!21:30
ttxanything else, anyone ?21:31
mrmartinRe, October 3-5 is the final date?21:31
ohnoimdeadwhat is the status of keystone support in swift? doesn't look like it's in for 1.4.2?21:31
spectorclan_mrmartin: yes21:31
spectorclan_conference is 5-7 with 5th just being evening event21:32
ttxohnoimdead: it's not showing up in the plan yet... maybe notmyname knows when this is planned21:32
creihtI thought support was already available through keystone?21:33
ohnoimdeadwould be awesome to get that stitched up in the dashboard since right now it's a tempauthtrocity21:33
mrmartincreiht: do you have any news about lunr?21:33
creihtI should be making an email to the list either this evening or tomorrow21:34
ttxcreiht: oh, it can be used directly ?21:34
creihtttx: I thought... I'm trying to find that doc21:34
creihthttps://github.com/rackspace/keystone21:35
creihtin the README21:35
creiht"Swift Integration - Quick Start"21:35
ttxyes, google just found it for me, reading21:36
* creiht notes that note at the bottom21:36
creihtNote: Keystone currently allows any valid token to do anything with any account.21:36
jaypipescreiht: is there a bug on that somewhere?21:36
ttxhmm, I sure like that21:36
creihtjaypipes: I have no idea, just repeating what I am reading :)21:37
ohnoimdeadyeah, wasn't sure if that was official or not. i tried to get it to work but was getting some errors (sent to the list). i'll try again see if i can get further.21:37
creihtI've been a bit out of the loop on the swift/keystone things, just relaying what I have seen come accross the screen21:37
ttxyes, I need to catch up too. Sign, so many things to look at, and only 24 hours in a day21:38
ttxSigh, even21:38
*** joearnold has quit IRC21:38
creihtohnoimdead: I would ask the keystone devs21:38
ttxwhich makes me think it's getting close to the end of that 24th hour here, so...21:39
*** joearnold has joined #openstack-meeting21:39
ttxif nobody has anything more, I'll close this21:39
*** markvoelker has quit IRC21:39
ttx#endmeeting21:39
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"21:39
openstackMeeting ended Tue Jul  5 21:39:46 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:39
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-07-05-21.02.html21:39
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-07-05-21.02.txt21:39
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-07-05-21.02.log.html21:39
ttxThanks everyone !21:39
*** comstud has left #openstack-meeting21:40
*** spectorclan_ has quit IRC21:40
carlpthanks ttx!21:40
jaypipesttx: thx mate21:40
*** mrmartin has quit IRC21:40
*** johan_-_ has left #openstack-meeting21:41
medberrythanks.21:42
*** markvoelker has joined #openstack-meeting21:42
*** jaypipes has quit IRC21:43
*** renuka has quit IRC21:44
*** jk0 has left #openstack-meeting21:44
*** Vek has left #openstack-meeting21:45
*** mattt has left #openstack-meeting21:54
*** ameade has quit IRC22:00
*** rdc has left #openstack-meeting22:00
danwentgood morning/afternoon/evening netstack...22:01
troytomanhello22:01
salv-orlandoHi!22:01
ryu_ishimotohi22:01
danwentok, anyone from cisco on the line?22:02
danwentotherwise we can wait a few mins.22:02
danwentor troy, perhaps we talk about melange first?  I need some cisco folks around for the quantum stuff.22:03
danwent#startmeeting22:03
openstackMeeting started Tue Jul  5 22:03:20 2011 UTC.  The chair is danwent. Information about MeetBot at http://wiki.debian.org/MeetBot.22:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.22:03
*** dabo has left #openstack-meeting22:03
danwent#topic melange22:03
*** openstack changes topic to "melange"22:03
*** SumitNaiksatam has joined #openstack-meeting22:03
danwenthi sumit, good to see you're here...22:03
SumitNaiksatamhey Dan22:04
danwentwe were waiting for someone from your team to joint to talk about quantum, so we're talking about melange first.22:04
danwenttroy?22:04
troytomanNot much new to report. We're doing some work on IPv6 support and the ability to subnet blocks. Hoped to have the wiki updated by now but should get done this week.22:04
SumitNaiksatamand everyone22:04
*** shwetaap has quit IRC22:04
*** Shubhangi has quit IRC22:04
troytomanAlso looking at the network-refactoring discussion and starting to think about how to integrate with Nova.22:04
danwentOk, I have been going through the existing nova code and want to sync up with you about how the melange stuff will fit in.  can do it offline though.22:04
troytomanwe're also bringing some RAX nova core devs into the team to help us with that analysis22:05
danwentvery cool.22:05
markvoelkero/22:05
*** eperdomo has joined #openstack-meeting22:05
troytomani think that's it unless there are questions22:05
danwent#topic quantum22:05
*** openstack changes topic to "quantum"22:05
danwentwhoops, forgot to send out the agenda: http://wiki.openstack.org/Network/Meetings22:05
danwentfor those just joining, we're switched the order to do melange first.22:06
danwentnova refactoring.  ryu, want to give an update?22:06
ryu_ishimotosure22:07
danwentwiki page is here: http://wiki.openstack.org/network-refactoring22:07
ryu_ishimotowe've made progress ironing out the remaining issues offline with those involved22:07
ryu_ishimotoin particular we are almost there with the libivrt driver refactoring22:07
*** Shubhangi has joined #openstack-meeting22:07
ryu_ishimotosumit made a very nice proposal for that, and I will add that to the wiki22:08
salv-orlandoryu_ishimoto: do you mean the network/linux_net driver?22:08
ryu_ishimotosalv-orlando: I mean the VIF configuration for libvirt(the generation of interface XML section)22:09
salv-orlandook, I see.22:09
danwentryu_ishimoto: btw, I've downloaded your branch and will be playing with it after the meeting today.   What is your preferred method of feedback on the wiki-page content and code?22:09
danwentstill just email?22:09
ryu_ishimotodanwent: Either works for me22:10
danwentI think salvatore and I have found the problem with using launchpad answers for feedback: there doesn't seem to be a way to quote someone previous comments22:10
danwentwhich is too bad because launchpad answers is nice and public, and has a good subscription mechanism :(22:10
*** RamD has joined #openstack-meeting22:10
salv-orlandodanwent: I don't understand actually why you can quote on comments for merge proposals and not answers...22:10
danwentOk, sumit anything to add?22:10
salv-orlandoryu... one last thing22:11
danwentsalv-orlando:  yes, odd indeed :)22:11
ryu_ishimotosalv-orlando: yup22:11
salv-orlandoI would like to play with your branch as well, but which one is exactly? I see 3 branches on the network-refactoring blueprint22:11
SumitNaiksatamsorry i was sleeping :-)22:11
danwenthttps://code.launchpad.net/~midokura/nova/network-refactoring22:11
danwentat the top of the wiki page22:11
salv-orlandook, thanks22:11
SumitNaiksatamso are we all in sync on the VIF driver stuff?22:12
ryu_ishimotodanwent: yup that's it thanks Dan22:12
danwentSumit: I don't think so....22:12
danwentI have an email out to Ryu on that, but I'll let him wake up before he needs to respond :)22:12
danwentI know its early :)22:12
ryu_ishimotoSumitNaiksatam: I have no problem with it, and i was JUST about to reply to that email22:12
SumitNaiksatamok great22:13
ryu_ishimotoI'm really curious what Nova core guys feel about it too!22:13
danwentOk, so let's just keep grinding on that discussion.22:13
danwentryu: +122:13
salv-orlandowould you include me as well in this loop? I'm curious. I promise I will not disturb too much :-)22:13
danwentsalv: sorry, didn't realize you weren't.  I thought ryu CC'd everyone22:14
ryu_ishimotosalv-orlando: Yeah of course.  The plan is to throw what we discussed to the entire community for more discussion as well22:14
ryu_ishimotosalv-orlando: I kept adding people but I forgot to add you, sorry22:14
RamDCould you include us all in that nova discussions22:15
salv-orlandoryu_ishimoto: np22:15
salv-orlandocould we have a netstack mainling list ? :)22:15
ryu_ishimotosure i'll add the entire netstack group, the discussion started with something vey small and grew large22:15
RamDsalv-orlando:+122:15
danwentI'm in favor, I know there were concerns about this that others had mentioned to Rick, but let's revisit this.22:16
danwent#action re-explore getting a netstack list22:16
danwent#action danwent re-explore getting a netstack list22:16
salv-orlandothe fact is that we typically don't use the openstack mailing list to avoid spam22:17
*** bcwaldon has quit IRC22:17
danwentsalv: agreed.  a lot of these discussions are high volume22:17
danwentso we don't want to be spamming the openstack list, but it makes sense that if someone wants the volume, they should be able to get it.22:17
RamDAnother suggestion: Create a design decision web page. and captute all the highlevel points there...22:17
danwentRamD: should blueprints capture this?22:18
danwentor are you talking about something else?22:18
*** Shubhangi has quit IRC22:18
RamDdanwent: I think a highlevel points that shows design decisions...and refer to BPs...that would be great22:18
danwentbtw, in the mean time, before we get a netstack list, please let ryu know if you want to be looped into the nova-refactoring discussion.22:19
*** creiht has left #openstack-meeting22:19
danwentRamD: do you mean kind of general design principles?22:19
danwentthat we've agreed on for quantum?22:20
RamDyes22:20
danwentI think that would be valuable.  I still have a half-written doc on that..... kind of lost momentum.  I will revive it and put it on a wiki.22:20
danwent#action danwent, revive design principles portion of "what is quantum?" doc, post on wiki.22:20
RamDNot to make it as big "documentation" effort...but to syncup any new people joining us22:20
RamDdanwent: Super...let me know if you need another kbd :-)22:21
danwentRamD: agreed.22:21
danwentOK, anything else on nova refactoring?22:21
ryu_ishimotothat's it for now!22:22
danwentthanks ryu.22:22
danwentOk, api auth.22:22
danwentsalvatore.22:22
salv-orlandohttps://answers.launchpad.net/quantum/+question/16309122:22
*** msinhore has quit IRC22:22
danwentsalv: sorry for getting feedback to you so late.22:22
danwentwill respond to your most recent comments later today, I hope.22:23
salv-orlandothis is the address where we are discussing the proposed specification. I already received Dan's feedback and you are all warmly invited to give your feedback22:23
danwentnot being able to "quote" is a real downside here....22:23
salv-orlandoThe interesting thing, is that, as Dan pointed out, authorization for Quantum kinds of goes back to the problem of the interaction with Nova wrt port creation and interface plugging22:23
salv-orlandoa problem we never fully fleshed out. Perhaps now the time is ripe to finalize that discussion22:24
danwentOk, is anyone else planning on commenting on the spec?22:25
danwentJust trying to gauge how long salvatore should be waiting for feedback.22:25
danwentok, anything else on auth?22:25
markvoelkerI wouldn't mind having another read through….if I have anything I'll get it to you by tomorrow night.22:25
danwentmakrvoelker: great, thanks.22:26
danwentok, extensions discussion.22:26
salv-orlandoIs anyone planning to have a discussion around whether plugging an interface into a network is an operation that should be explictly be performed by tenants or by nova on behalf of the tenant (ie: should be an operation of an 'admin API')?22:26
danwentsalv-orlando: I assume you mean logical plugging?22:27
salv-orlandoyeah, logical of course :-)22:27
danwentI believe the plan is that it will be possible for tenants to plug directly, or something else can "orchestrate" on behalf of the tenants.22:27
danwentthat something else could be donabe, or it even could be nova22:27
SumitNaiksatamthat was my understanding22:27
danwentnova already does a far amount of orchestration, though I'm not sure thats the long-term goal.22:28
danwentany other opinions out there?22:28
salv-orlandoOk, so can we be safely sure we don't need a discussion on this point?22:28
carlpsounds reasonable to me22:28
troytomanwe are thinking that we should limit orchestration in Nova as a general rule22:28
*** edconzel has quit IRC22:28
danwentsalv-orlando: one of the things I am thinking about when reviewing ryu's branch is what it would mean for nova to orchestrate quantum22:29
troytomanthat said plugging in a vif within Nova is something that we would probably do22:29
danwentok, extensions.22:29
salv-orlandodanwent: That's why I want to play with the refactoring branch, as this might also affect the way in which we do authorization in Quantum.22:29
danwentsalv-orlando: I agree.22:30
danwentis james here?22:30
salv-orlandofor extensions, is James on line?22:30
danwentor ying?22:30
danwentJames sent an email about discussing extensions.22:30
RamDdanwent: What is the q ..sorry22:30
danwentit will probably happen later this week.22:31
danwentholler if you want to be involved and we'll make sure you get the invite.22:31
troytomanI don't think we've found a time yet.22:31
danwentyeah, last email in the thread was from troy22:31
RamDdanwent: Yes. Will followup with James/Ying on the extensions discussions22:31
danwentRamD: thx.22:31
danwentand last but not least for quantum: Mark22:32
danwentany updates on the GUI?22:32
troytomani think we'll have some updates to the extension merge prop that handles plug-ins etc.22:32
danwent+ client lib stuff?22:32
markvoelkerActually, it might be "least" for this week. =)22:32
danwent:)22:32
danwenttroy: great.22:32
markvoelkerDue to the holidays and folks being on PTO for the US Independence Day holiday and medical reasons there hasn't been a huge amount of progress.22:32
markvoelkerHowever, Arvind did get a prelim mockup branch posted22:33
markvoelkerIt's linked here:22:33
markvoelkerhttps://code.launchpad.net/~asomya/+junk/dashboard-quantum-mockup22:33
danwentcool.22:33
markvoelkerThere are some known issues yet as it's what he had time for before leaving the country (he'll be out all this week as well).  Those are in the whiteboard on the BP:22:33
markvoelkerhttps://blueprints.launchpad.net/quantum/+spec/quantum-client-gui22:33
markvoelkerTyler is beginning work on the refactor but has been out today and yesterday.  I'll have him get a branch linked as soon as he returns.22:34
danwentgreat, thanks for the update.22:34
danwentanything else on quantum?22:34
RamDtest-framework for Qunatum..Is Santosh or any one else doing that?22:34
danwentunit tests?22:34
danwentor system test?22:34
danwentunit test stuff should be in22:35
danwentsalv, somik?22:35
danwentbrad?22:35
bhallsavlatore and I have gotten some pieces for unit testing in and are currently working on more tests22:35
salv-orlandoThankfully, there's no independence day in the UK22:35
bhallfilling out the other pieces22:35
markvoelkerRamD: were you referring to: https://blueprints.launchpad.net/quantum/+spec/quantum-system-test ?22:35
salv-orlandoit would be a bit of a nonsense, after all22:35
danwentbhall: it would be great if we had docs on how to run the unit tests... I think you were going to do that?22:35
danwentsalv: yes... wouldn't expect the UK to celebrate that :)22:36
RamDmarkvoelkar: yes..wanted to find if any other piecees need to be done22:36
bhallsh run_tests.sh .. but yeah, I can create a document :)22:36
somiksalv-orlando: lol22:36
salv-orlandoI said because I used last week to make some progress starting from Brad's branch22:36
markvoelkerbhall: what about getting things into Jenkins/Smokestack?22:36
danwentmark: I think that is waiting on incubation...22:36
danwentreally need to chase down dendrobates and get an update on that22:37
danwent#action danwent: find out current status of incubation from dendrobates22:37
markvoelkerdanwent: Ah, ok.  RamD or myself can harass him. =)22:37
carlpI'm building a Jenkins for Openstack/Ceph, and was planning on running some networking stuff on it too22:37
danwentmark: the more the better :)22:37
danwentcarlp: great.  what's Ceph?22:38
*** romain_lenglet has joined #openstack-meeting22:38
carlpStorage System that we are developing.  Unrelated to networking, but I have interest in both :)22:38
danwentcarlp: ah, cool.22:38
salv-orlandobhall: updated branch for unit tests is in lp:~netstack/quantum/quantum-unit-tests22:38
carlpI'm hoping to get Jenkins running this week, I'll be happy to give logins to those we deem worthy :)22:38
danwentcarlp: very cool.  please keep me in the loop.22:39
carlpwill do22:39
danwent(if you deem me worthy) :P22:39
salv-orlandocarlp: just a curiosity... why is the project call Ceph?22:39
danwentanything else on quantum?22:40
salv-orlandoon unit tests...22:40
salv-orlandoI have implemented several test cases for the API, will complete them by tomorrow.22:40
salv-orlandoFakePlugin has ben enhanced to use in-memory sqlite db with models provided in quantum.db. This will ensure high code coverage.22:41
bhallawesome.. soon it will be time to look at code coverage numbers :)22:41
salv-orlandoWe need unit tests for db, cli, wsgi and plugin-interface as well22:41
somikthat sounds like a good improvement22:41
salv-orlandothe branch is on netstack ownership, so feel free to add stuff!22:41
danwentsalv: great work.  is there a blueprint were we are tracking the areas you think need work?22:42
salv-orlandoIn the meanwhile I did a self "cease and desist" on proposing other branches for merge...22:42
danwentis it: https://blueprints.launchpad.net/quantum/+spec/api-spec-unit-tests22:42
danwentor something else?22:42
salv-orlandoyes, that one22:42
danwentk, thanks.22:42
danwentlast call on quantum...22:42
*** troytoman is now known as troytoman-away22:42
danwentanyone here to talk about donabe?22:43
danwent#topic open discussion22:43
*** openstack changes topic to "open discussion"22:43
salv-orlandoI have a question on the nestack-core team22:43
danwentsure.22:44
salv-orlandoI sent an email to Rick, as we decided a few weeks ago, proposing myself as a core member, but I'm not on the list.22:44
danwentreally?22:44
salv-orlandoI know it is not nice to self-candidate but that's what we agreed :-)22:44
danwent#action dendrobates make salv-orlando a core member22:44
salv-orlandok, thanks22:45
danwentyou've contributed much more code than most people in that group... not sure how that happened.22:45
danwentthanks for bringing it up.22:45
danwentanything else?22:45
*** adjohn has joined #openstack-meeting22:45
danwent(not to mention done reviews, fixed bugs, etc.)22:45
danwentok, folks.  have a good one!22:46
danwent#endmeeting22:46
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"22:46
openstackMeeting ended Tue Jul  5 22:46:11 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-07-05-22.03.html22:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-07-05-22.03.txt22:46
salv-orlandobye!22:46
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-07-05-22.03.log.html22:46
*** Tushar has quit IRC22:46
somiktake care everybody, till next week.22:46
carlpThanks all!22:46
markvoelker'bye!22:46
SumitNaiksatamthanks, bye22:47
*** SumitNaiksatam has quit IRC22:47
carlpdanwent, just an FYI - I worked with the folks at RS who are setting up the Jenkins stuff there.  The goals is for me to be able to link my system to theirs.  Should make life better for everyone :)22:47
*** markvoelker has left #openstack-meeting22:47
danwentcarlp: cool.  i've very new to the jenkins stuff, but I'd love to be able to poke at it.22:48
carlpI'm new at is as well, it's a learning experience for everyone :)22:48
*** eperdomo has quit IRC22:50
*** markvoelker has joined #openstack-meeting22:51
*** markvoelker has left #openstack-meeting22:51
RamDbye22:52
*** RamD has left #openstack-meeting22:52
*** jkoelker has quit IRC22:54
*** carlp has quit IRC23:03
*** romain_lenglet has left #openstack-meeting23:04
*** adjohn has quit IRC23:05
*** adjohn has joined #openstack-meeting23:10
*** ryu_ishimoto has quit IRC23:11
*** medberry is now known as med_out23:13
*** msinhore has joined #openstack-meeting23:24
*** alandman has quit IRC23:25
*** adjohn has quit IRC23:32
*** nati has quit IRC23:39
*** adjohn has joined #openstack-meeting23:50
*** littleidea has quit IRC23:59

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