21:02:27 <ttx> #startmeeting
21:02:28 <openstack> Meeting started Tue Jun 14 21:02:27 2011 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:02:29 <vishy> can we do nova first today?
21:02:30 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic.
21:02:41 <ttx> vishy: if you convince notmyname, yes.
21:02:49 <ttx> Agenda for today:
21:02:53 <ttx> #link http://wiki.openstack.org/Meetings/TeamMeeting
21:02:55 * notmyname defers to vishy
21:03:00 <ttx> #topic Actions from previous meeting
21:03:10 <ttx> * ttx to push update of Swift release PPA to 1.4.0 and creation of a common OpenStack release PPA
21:03:15 <devcamcar> sebastiansadil: sure
21:03:16 <vishy> notmyname: thx.  I'm hoping to get some more sleep :)
21:03:19 <sandywalsh> eday, makes sense
21:03:24 <ttx> That's done. PPAs for common OpenStack releases are now under https://launchpad.net/~openstack-release
21:03:37 <ttx> You can see a map of the available PPAs at: http://wiki.openstack.org/PPAs
21:03:45 <ttx> * ttx to consider untargeting/retrotarget Low specs to decrease noise
21:03:58 <ttx> Not done, been busy sanitizing diablo-2 plans last week, postponing
21:04:04 <ttx> #action ttx to consider untargeting/retrotarget Low specs to decrease noise
21:04:13 <ttx> #topic Nova status
21:04:28 <ttx> vishy: I worked last week to make sure diablo-2 specs were assigned to someone or postponed
21:04:36 <ttx> #link https://launchpad.net/nova/+milestone/diablo-2
21:04:47 <ttx> I still have a few targeted specs without confirmation:
21:04:59 <ttx> * https://blueprints.launchpad.net/nova/+spec/integrate-nova-authn (anotherjesse ?)
21:05:17 <ttx> * https://blueprints.launchpad.net/nova/+spec/extra-data (justinsb ?)
21:05:32 <ttx> You just told me about the two you have
21:05:49 <ttx> I suspect we should defer extra-data, couldn't get hold of Justin
21:06:00 <vishy> yes, sounds good
21:06:12 <ttx> #action ttx to defer extra-data to diablo-3
21:06:31 <ttx> #action vishy to get integrate-nova-authn status from anotherjesse
21:06:39 <ttx> I also have two related ones without assignee:
21:06:45 <ttx> * https://blueprints.launchpad.net/nova/+spec/configuration-drive
21:06:50 <ttx> * https://blueprints.launchpad.net/nova/+spec/instance-transport
21:07:00 <ttx> Anyone interested in them ?
21:07:09 <ttx> Should we defer them to diablo-3 already ?
21:08:02 <vishy> 0x44 was working on prototyping configuration-drive
21:08:19 <vishy> don't know what happened to it though...
21:08:36 <vishy> probably makes sense to defer if we have no one actively working on them
21:08:45 <ttx> vishy: yes
21:08:58 <ttx> I'll send out an email asking for candidates, worked well last time
21:09:02 <vishy> ok
21:09:13 <ttx> #action ttx to defer configuration-drive and instance-transport
21:09:22 <ttx> People still need to come back to me on openstack-api-floating-ips (reldan) and the testing-* ones (mtaylor)
21:09:30 <ttx> The rest if pretty firm.
21:09:43 <ttx> Quick status update on the essential stuff:
21:09:52 <ttx> * https://blueprints.launchpad.net/nova/+spec/no-db-messaging (vishy)
21:10:06 <_0x44> vishy: I have code up on github for it, I showed anotherjesse yesterday.
21:10:37 <vishy> oh there ya go, perhaps we should assign the config drive blueprint to _0x44 then
21:10:50 <ttx> _0x44: would that work for you ?
21:10:54 <_0x44> Yes
21:11:15 <vishy> no-db-messaging is a little bogged down.  I'm going to take one more pass at the volume code and then start an ml thread about it
21:11:37 <ttx> #action ttx to assign _0x44 to configuration-drive
21:11:47 <ttx> * https://blueprints.launchpad.net/nova/+spec/nova-multi-nic (tr3buchet)
21:12:04 <vishy> the main issue is solving that "problem "is creating some other ones
21:12:12 <ttx> tr3buchet: any news ?
21:12:37 <ttx> * https://blueprints.launchpad.net/nova/+spec/distributed-scheduler (sandywalsh)
21:12:42 <ttx> sandywalsh: looks on track ?
21:12:57 <tr3buchet> yes
21:13:02 <tr3buchet> sorry, looked away
21:13:07 <tr3buchet> i'm getting the tests running now
21:13:19 <tr3buchet> physical test after then merge
21:13:20 <sandywalsh> ttx, merging as we speak
21:13:37 <ttx> tr3buchet, sandywalsh: cool, so still on track for diablo-2 delivery.
21:13:43 <tr3buchet> ttx: yes
21:13:48 <ttx> * https://blueprints.launchpad.net/nova/+spec/nova-instance-referencing (dabo)
21:13:58 <sandywalsh> ttx yes
21:13:58 <ttx> dabo: looking good ?
21:14:07 <dabo> code is working, but broke lots of unit tests
21:14:16 <sandywalsh> ttx, merge succeeded
21:14:19 <dabo> we're fixing them now; should be on-track
21:14:26 <ttx> dabo: thanks !
21:14:28 <ttx> vishy: anything else you wanted to mention ?
21:14:31 <vishy> dabo: are you doing volumes too?
21:14:34 <vishy> or just instances?
21:14:42 <dabo> this pass is just instances
21:14:54 <vishy> ok cool
21:14:55 <dabo> volumes will need to be done, too
21:15:06 <vishy> and are you doing ec2 mapping layer?
21:15:10 <dabo> same as with scheduler - only instances work for now
21:15:20 <ttx> dabo: needs to be done as in "sometime in diablo" ? Or "someday" ?
21:15:35 <dabo> vishy: no, we're re-defining the ec2_id to be 'i-' + first 8 chars of UUID
21:15:44 <dabo> ttx: as in 'next'
21:16:05 <ttx> dabo: as part of the same blueprint, or another one ? Want to make sure we track that
21:16:12 <vishy> dabo: hmm ok.  That seems reasonable for the first pass I suppose
21:16:17 <dabo> vishy: mapping layer would require shared db across zones
21:16:38 <vishy> dabo: it is going to be annoying for existing deployments...
21:16:42 <dabo> ttx: a new bp, since the original was instance-specific
21:16:59 <ttx> dabo: ok, feel free to file and ping me to include
21:17:03 <ttx> (or vishy)
21:17:24 <dabo> vishy: yeah, I was thinking of how to convert when the uuid column is generated in the instances table
21:17:55 <vishy> dabo: we can discuss offline
21:17:57 <ttx> Other Nova questions ?
21:18:00 <dabo> sure
21:18:02 <vishy> (later...)
21:18:24 <ttx> ok then, next topic
21:18:33 <ttx> #topic Swift status
21:18:45 <ttx> notmyname: could you announce your plans for 1.4.1 and 1.4.2 ?
21:18:47 <notmyname> all kinds of stuff
21:18:50 <notmyname> ok
21:19:10 <notmyname> 1.4.1 is coming sooner than we all expected. It is scheduled for next week
21:19:29 <notmyname> 1.4.2 won't be until mid-july at the earliest
21:19:37 <jaypipes> notmyname: what is in 1.4.1?
21:19:39 <notmyname> changelog for 1.4.1 is http://bazaar.launchpad.net/~hudson-openstack/swift/trunk/view/head:/CHANGELOG
21:19:57 <ttx> So we should have a QA branch ready tomorrow, where potential release-critical bugfixes will be applied
21:20:02 <notmyname> big things are swuath removed and renamed st
21:20:07 <ttx> Release scheduled for Monday.
21:20:53 <ttx> notmyname: Other announcements or comments ?
21:20:53 <soren> What will be in 1.4.2?
21:21:08 <notmyname> 1.4.2 should have container sync
21:21:35 <notmyname> change post to copy
21:21:45 <notmyname> and removing stats/logging
21:22:03 <soren> Where is that going?
21:22:10 <soren> (stats/logging, that is)
21:22:13 <notmyname> into a separate project (like swauth did)
21:22:34 <soren> Ok.
21:22:56 <ttx> Other Swift questions / announcements ?
21:23:38 <ttx> #topic Glance status
21:23:43 <ttx> jaypipes: Hi!
21:23:45 <jaypipes> https://launchpad.net/glance/+milestone/diablo-2
21:23:56 <ttx> Two weeks away from delivery
21:24:14 <ttx> Looking at that URL I'd say you're a bit behind ?
21:24:15 <jaypipes> ttx: we're doing OK. not great, but OK. Keystone integration is moving along a little slower than expected. bcwaldon is making great progress on wsgi refactoring.
21:24:44 <jaypipes> ttx: yes. still on track for the 2 High BPs. Some of the Low priority ones may slip, but not too concerned.
21:25:00 <ttx> right
21:25:10 <ttx> jaypipes: Other announcements, comments ?
21:25:13 <jaypipes> I *really* want to get the S3 bug out of the way... so I need some reviews from dprince, bcwaldon and others...
21:25:33 <jaypipes> ttx: nothing more from me
21:25:41 <ttx> jaypipes: link to review needed ?
21:26:20 <jaypipes> ttx: https://code.launchpad.net/~jaypipes/glance/bug713154/+merge/59110
21:26:28 <ttx> thx!
21:26:50 <ttx> #action glance-core to review in priority https://code.launchpad.net/~jaypipes/glance/bug713154/+merge/59110
21:27:29 <ttx> if there is nothing else on Glance, let's go to our favorite topic
21:27:36 <ttx> #topic Naming of E
21:27:48 <ttx> I came up with a list of candidates at: http://wiki.openstack.org/ReleaseNaming
21:27:57 <ttx> Personally I like "Exeter" :)
21:28:05 <creiht> how about Effing?
21:28:10 <ttx> If you have other candidate names (that follow the rules described on the page), please edit the wiki
21:28:27 <jaypipes> creiht: lol. ++
21:28:28 <ttx> creiht: does that even exist ?
21:28:33 <heckj> heh
21:28:41 <ameade> Egleston square is in the center of Boston
21:28:59 <ttx> creiht: if you can make that a city or county near Boston, I'll take it
21:28:59 <creiht> there is an Effingham, Illinois
21:29:15 <markwash> creiht: that's an effing good ham
21:29:45 <ttx> Do that soon because I'll throw a Launchpad poll (probably tomorrow) to pick the final name
21:30:00 <ttx> The Launchpad ~openstack group will be able to vote and it will last a week
21:31:08 <ttx> Comments ?
21:32:23 * ttx wonders if the Internet dropped. This discussion usually triggers comment frenzy.
21:32:45 * Vek shrugs
21:32:47 <ttx> then...
21:32:50 <heckj> still here - just nothin' useful to add
21:32:56 <ttx> #topic Open discussion
21:33:02 * Vek will simply throw a dart at the list for the vote
21:33:04 <ttx> heckj: it doesn't have to be useful.
21:33:22 <heckj> ttx: trying to be a little useful.
21:33:43 <heckj> I rather like Exeter, but the poll will take care of it one way or another..
21:34:03 <ttx> Wow. Having vishy in Japan sounds like a good way to finish meetings early.
21:34:20 <heckj> general question - is the packaging under the CI work?
21:34:32 <heckj> (i.e. making deb's, rpm's etc)
21:34:49 <ttx> heckj: it's completely integrated in Jenkins, if that's what you're asking
21:34:50 <heckj> Its a tad inconsistent between the various official and side projects today.
21:35:05 <ttx> (the deb's thing)
21:35:15 <heckj> monty has is set up to build RPM's as well? I knew deb's and PPA's
21:35:29 <mtaylor> no. but he wants to
21:35:33 <mtaylor> that's on my todo
21:35:35 <mtaylor> list
21:35:45 <heckj> mtaylor - sweet.
21:35:46 <ttx> mtaylor: hooking OpenSuse build service ?
21:35:59 <mtaylor> ttx: implementation as yet undecided
21:35:59 <ttx> mtaylor: that's a long todo list.
21:36:32 <mtaylor> I'm not a fan of the interface method for the OpenSuse build service - but it's not off the table
21:36:38 * heckj is installing most of the pieces from source control
21:36:58 <heckj> but I'm going to switch to using Chef shortly and the official PPAs we're creating through Jenkins
21:37:49 <mtaylor> great!
21:37:55 <ttx> anything else before we close this meeting ?
21:38:07 <heckj> nope
21:38:26 <mtaylor> heckj: so - this may be off topic - but the current set of howto's involving installing from chef without using something else to drive the chef install are ... lacking
21:38:27 <ttx> #endmeeting