21:02:46 <ttx> #startmeeting
21:02:47 <openstack> Meeting started Tue Oct 18 21:02:46 2011 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:02:48 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic.
21:03:01 <ttx> Welcome everyone to our weekly meeting... Today's agenda is at:
21:03:06 <ttx> #link http://wiki.openstack.org/Meetings/TeamMeeting
21:03:17 <ttx> #info Please use #info #link #idea #action for a richer summary.
21:03:31 <ttx> #topic Actions from previous meeting
21:03:40 <ttx> * ttx to set up some survey monkey for summit feedback
21:03:59 <ttx> in progress, will probably be common with the conference feedback, marketing plans to send on Thursday
21:04:13 <ttx> * ttx to ask powers that be about next design summit location plans
21:04:25 <ttx> done, it looks like they want the next summit to be held somewhere in the US, for a change
21:04:41 <soren> Wow, I've always wanted to vist.
21:04:42 <ttx> * vishy to schedule nova blueprint prioritizing meeting for Thursday and send an email to the list
21:04:44 <soren> visit, even.
21:04:44 <vishy> o/
21:04:56 <ttx> vishy: that was done, right ?
21:05:39 <comstud> i was there, so i'd say so
21:05:46 <comstud> :)
21:05:49 <ttx> * devcamcar to set "Maintainer" at https://launchpad.net/openstack-dashboard to ~openstack-admins: DONE
21:05:58 <ttx> * ttx to update the "How to Contribute" page and add dashboard & keystone to wiki.openstack.org overview: DONE
21:06:00 <vishy> yes
21:06:09 <vishy> sorry internet is spotty
21:06:09 <ttx> #topic Keystone status
21:06:16 <ttx> zns: Looking at:
21:06:20 <ttx> #link https://blueprints.launchpad.net/keystone/essex
21:06:27 <ttx> Looks a bit empty at this point :)
21:06:34 <zns> Weekly meetings started. First one was today.
21:06:44 <zns> Info here: http://wiki.openstack.org/Meetings/KeystoneMeeting
21:06:53 <ttx> zns: you should:
21:06:53 <zns> Minutes here: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-10-18-17.59.html
21:07:07 <ttx> #info 1. create blueprints (or ask people to file blueprints) matching your feature plan (if you have any feature)
21:07:10 <zns> Hi level roadmap and schedule:
21:07:11 <zns> http://wiki.openstack.org/EssexReleaseSchedule
21:07:11 <zns> Schedule:
21:07:11 <zns> - E1: implement 2.0 API & doc sprint
21:07:11 <zns> - E2: RBAC (big feature)
21:07:11 <zns> - E3 (Jan 5th-Feb 1st): stabilizing/performance, etc... actively working code
21:07:12 <zns> - E4 (Feb 2-March 1st): bug fixing, supporting users – prep for RC
21:07:12 <zns> - E5 (March 1st-April 5): starting on BPs, prototypes for F
21:07:13 <zns> - F Summit: April 19th
21:07:21 <ttx> #info 2. set the "Series goal" to Essex so thet it appears at the above link
21:07:27 <ttx> #info 3. set "Milestone" to one of the milestones
21:07:40 <ttx> any chance you could convert that roadmap to that ?
21:07:45 <zns> We're working on the blueprints and will get them done by end of next week. Will report status next Tuesday. We have sopme in already.
21:07:58 <ttx> cool !
21:08:21 <ttx> Note that E1 is in 3 weeks now
21:08:31 <ttx> zns: I'll maintain the milestones for you... but first you need to fix the group permissions:
21:08:38 <ttx> #action zns to set "Maintainer" at https://launchpad.net/keystone to ~openstack-admins
21:08:39 <zns> ttx: yes, we have not targetted them (or entered them) yet. But the roadmap is under discussion and planning (per minutes of meeting today).
21:09:14 <zns> ttx: uyes. will set the series and milestones.
21:09:15 <ttx> Are you planning to freeze the API by E3 or earlier ?
21:09:34 <vishy> afk for 10 minutes
21:09:52 <ttx> zns: i can maintain that for you with the right dates -- just set the maintainer on keystone project to ~openstack-admins
21:09:59 <zns> No API changes in E3. The last changes will be worked on in E2. So everyone can have a stable API to work on from E3 on.
21:10:08 <zns> ttx: will do.
21:10:08 <ttx> so that I can add myself as release manager for keystone
21:10:21 <ttx> that sounds great
21:10:30 <ttx> zns: Anything else ?
21:10:48 <zns> ttx: No. THanks!
21:10:56 <ttx> everyone: Raise your hand if you have questions on Keystone...
21:11:07 <westmaas> o/
21:11:14 <ttx> westmaas: shoot
21:11:32 <zns> ttx: openstack-admins set as maintainer on Keystone.
21:11:43 <ttx> zns: coolio
21:11:50 <westmaas> zns: do you anticipate a lot of change between now and E1 on 2.0?  Especially in terms of backwards compatibility
21:11:59 <westmaas> or is it mostly adding things
21:12:13 <westmaas> not asking for a garauntee or anything just curious where you expect most changes to be
21:12:40 <zns> No. No changes will happen to 2.0. 2.0 API is fixed.
21:13:00 <jaypipes> zns: where is the proposed 2.0 API spec?
21:13:03 <westmaas> sorry, I mean in implementation
21:13:14 <westmaas> seems like its working in a basic way now
21:13:21 <zns> westmaas: from the Keystone meeting:
21:13:22 <zns> - v2.0 API is final. Only extensions to it will be pubished.
21:13:22 <zns> - Any core changes needed/requested will trigger next version (v2.1)
21:13:22 <zns> - During F summit, we will discuss v3 and if any extensions should be promoted to v3 (core)
21:13:34 <westmaas> kk
21:13:35 <westmaas> thanks
21:13:52 <jaypipes> gotcha. thx.
21:14:00 <ttx> anything else ?
21:14:22 <ttx> #topic Swift status
21:14:27 <ttx> notmyname: o/
21:14:31 <notmyname> hi
21:14:34 <ttx> notmyname: did you come to a decision wrt the milestone plan (common vs. specific) ?
21:14:46 <zns> westmaas: The 2.0 API spec is complete. It's available here: http://docs.openstack.org/
21:15:27 <notmyname> ttx: we will be continuing our previous path of releasing as needed and not necessarily following the nova milestones
21:15:34 <ttx> ok
21:15:51 <notmyname> #info swift will be continuing our previous path of releasing as needed and not necessarily following the nova milestones
21:15:57 <ttx> do you have a date in mind and a version number for the next one ?
21:16:41 <notmyname> 1.4.4 I expect. and in 2-3 weeks. I want to see the currently in-review features land first. then we'll be ready for a release
21:16:54 <devcamcar> o/
21:17:16 <ttx> notmyname: do you have features targeted to that already ?
21:17:17 <zns> jaypipes, westmaas: sorry, correct URL for API specs is: https://github.com/openstack/keystone/tree/master/keystone/content/admin
21:17:27 <jaypipes> zns: ah, cheers
21:17:54 <notmyname> ttx: ah, probably not in LP. I was looking at that this morning (before I got pulled aside for some personal things)
21:18:10 <notmyname> I'm currently trying to clean up the blueprints and bugs in LP for swift
21:18:12 <zns> jaypipes, westmaas: if you see the roadmap above, first thing we are doing is updating the docs to make it easier to find this stuff. Consolidating and simplifying.
21:18:16 <notmyname> devcamcar: did you have a question?
21:18:25 <ttx> notmyname: could you create / link blueprints to 1.4.4 by next week ?
21:18:33 <notmyname> ttx: I'll do my best
21:18:36 <ttx> notmyname: I'll create the milestone if it's missing
21:18:37 <devcamcar> notmyname: nope, just running behind schedule and finally got here
21:18:50 <ttx> #action notmyname to create/target blueprints to 1.4.4
21:19:02 <ttx> #action ttx to create 1.4.4 milestone if it doesn't exist yet
21:19:20 <ttx> notmyname: Anything else ?
21:19:45 <ttx> Questions on Swift ?
21:20:49 <ttx> ok, moving on...
21:20:53 <ttx> #topic Glance status
21:20:55 <jaypipes> https://launchpad.net/glance/+milestone/essex-1
21:21:08 <ttx> jaypipes: How complete is that ?
21:21:16 <jaypipes> Essex 1 looking good. Got SSL support into trunk today.
21:21:20 <ttx> I mean, is that the full essex-1 plan ?
21:21:22 <jaypipes> Open reviews: https://review.openstack.org/#q,status:open+project:openstack/glance,n,z
21:21:32 <jaypipes> Would appreciated reviews on there... if anyone has some time
21:22:00 <jaypipes> ttx: I am fleshing out the 2.0 API blueprints and proposal this week. 2.0 API stuff should be targeted to E2.
21:22:09 <jaypipes> ttx: so yes, that is correct for E1.
21:22:27 <jaypipes> ttx: focusing on getting bugs done and some refactoring work done before work on 2.0 API.
21:22:37 <ttx> jaypipes: Would you consider setting a milestone target and an assignee for all the "High" blueprints on https://blueprints.launchpad.net/glance/essex ?
21:22:49 <ttx> or is that too early ?
21:23:17 <ttx> (I tend to think that things taht are important should have someone committed to delivering them)
21:23:19 <jaypipes> ttx: I've tried. If the assignee is missing, it's for a areason :) same for missing milestones...
21:23:35 <jaypipes> ttx: should have those filled in by next week.
21:23:51 <jaypipes> ttx: just need to get the proposed images API 2.0 out the door and get feedback on it.
21:24:04 <jaypipes> ttx: after that, I'll negotiate some resources with pvo and westmaas  ;)
21:24:04 <ttx> #action jaypipes to try to get a complete Essex plan
21:24:13 <ttx> jaypipes: Anything else ?
21:24:22 <jaypipes> ttx: nope.
21:24:23 <ttx> everyone: Questions on Glance ?
21:25:01 <ttx> vishy: are you back ?
21:25:36 <ttx> let's skip to dashbaord first
21:25:40 <ttx> #topic Dashboard status
21:25:44 <ttx> devcamcar: o/
21:25:48 <ttx> So what's the new name ? :)
21:26:26 <devcamcar> ttx: i am actually crafting the email to announce the name right now - it'll hit the list in about an hour :)
21:26:37 <ttx> cool
21:26:39 <ttx> devcamcar: Looking at your empty Essex plan:
21:26:43 <ttx> #link https://blueprints.launchpad.net/openstack-dashboard/essex
21:26:44 <devcamcar> dashboard update - i'm triaging a number of new blueprints from the essex summit
21:26:50 <devcamcar> today
21:26:54 <ttx> devcamcar: see steps I outlined for Ziad above
21:27:17 <devcamcar> ttx: will review
21:27:24 <ttx> on how to link existing blueprints to essex
21:27:33 <devcamcar> ttx: oh, yea i'm good on how to do that
21:27:36 <ttx> #info Producing such a plan really helps in communicating your goals and completion targets outside your project, which is critical to attracting outside participation
21:27:47 <ttx> cool
21:27:50 <devcamcar> that was all done for diablo in dashboard
21:28:06 <devcamcar> so today we'll have the official dashboard roadmap, a new name, and a timeline for gerrit migration
21:28:25 <ttx> (it's also about the only way to filter down the blueprints list in launchpad to something that makes sense)
21:28:50 <ttx> devcamcar: once we know the name we'll work to align the project with other core projects in terms of team names etc
21:29:04 <devcamcar> sounds good!
21:29:09 <ttx> devcamcar: Anything else ?
21:29:14 <devcamcar> thats all for today
21:29:17 <ttx> Questions on Dashboard ?
21:29:38 <ttx> vishy: around now ?
21:30:26 <ttx> hmm, skipping again
21:30:32 <ttx> #topic Incubated projects and other Team reports
21:30:42 <ttx> #info This (new) topic is about having a moment for the various other team leads to communicate stuff that is happening in their teams
21:30:54 <zns> ttx: in fairness to Vishy, he was here at the correct meeting time...
21:30:57 <ttx> We have plenty of teams now:
21:30:57 <ttx> #link http://wiki.openstack.org/Teams
21:31:13 <ttx> zns: correct meeting time ?
21:31:24 <ttx> that's him in disguise
21:31:26 <vishyweb> hi
21:31:36 <vishyweb> having trouble with the internet here, had to webclient it
21:31:42 <ttx> vishyweb: back to Nova in a bit
21:31:51 <ttx> So if you're a team lead and want to talk about something, you can raise your hand during this topic
21:31:54 <danwent> hi
21:31:58 <zns> ttx: PPB meeting 90 minutes ago.
21:32:03 <ttx> Or just add a line to the agenda at: http://wiki.openstack.org/Meetings/TeamMeeting
21:32:12 <danwent> on quantum: E1 is starting to fill up: https://launchpad.net/quantum/+milestone/essex-1
21:32:14 <danwent> still more to add
21:32:18 <ttx> zns: this is a different meeting :P
21:32:33 <zns> ttx: Oh! Felt like a PPB :-)
21:32:41 <danwent> as always, our netstack meeting agenda is available at: http://wiki.openstack.org/Network/Meetings if you're interested in what we are talking about next.
21:32:45 <zns> ttx: albeit an efficient one ;-)
21:32:55 <ttx> zns: the PPB is much more chaotic :P
21:33:05 <carlp> Quick question: is there a reason Netstack is not on the Teams page?
21:33:26 <ttx> hmm, I guess it could fit on that page
21:33:36 <danwent> carlp:  we can add it.
21:33:44 <ttx> Quantum is not (and Nova is not) because they are a project, not a team
21:33:49 <carlp> \o/ Yay!
21:34:07 <ttx> but the "netstack" group could, I think. Hey, it's a wiki.
21:34:16 <danwent> also, some more quantum improvements will be hitting nova soon.  reviews are much appreciated :)
21:34:29 <ttx> danwent: you can also edit http://wiki.openstack.org/Meetings
21:34:48 <ttx> any other team lead with news ?
21:34:48 <danwent> ttx: will do
21:35:05 <ttx> QA, CI , docs ?
21:35:36 <annegentle> docs - formed the nova-doc team with Razique and kbringard
21:35:46 <zykes-> quicky question, when is the Quantum meeting ?
21:35:59 <annegentle> docs - Keystone sprinting on admin/install docs
21:36:00 <ttx> annegentle: does it make sense to have project-specific doc teams ?
21:36:01 <danwent> top of the hour, right after this one
21:36:20 <annegentle> ttx: when people volunteer for it, yes :) but seems only that nova needs it right now.
21:36:27 <ttx> annegentle: in addition to the horizontal "docs" team ?
21:36:35 <ttx> ok
21:37:10 <ttx> unless some other team has something, we'll move back to the nova topic
21:37:14 <annegentle> but we can always revisit, it's just that docs for nova/keystone are in dire need
21:37:32 <ttx> #topic Nova status
21:37:37 <ttx> vishy: yo
21:37:45 <ttx> vishyweb: ^
21:37:55 <vishyweb> hi
21:37:59 <ttx> #link https://blueprints.launchpad.net/nova/essex
21:38:11 <ttx> Still very empty, except the nova-rootwrap one that I filed (targeted to essex-2)
21:38:22 <_0x44> Sorry I'm late.
21:38:28 <ttx> vishy: Any way I can help in filling this up ?
21:40:09 <ttx> vishyweb: ?
21:40:50 <ttx> not sure the webclient works really better :/
21:41:44 <ttx> My other question was, do we have any significant thing that is already merged and that we should retrospectively add to the Essex list ?
21:42:03 <ttx> but I guess I'll have to solve those off-meeting
21:42:14 <ttx> Questions on Nova ?
21:42:31 <ttx> that another nova-core dude would answer ? :)
21:42:47 <vishyweb> worst internet in history
21:42:49 <vishyweb> sorry ttx
21:42:52 <ttx> vishyweb: feeling better now ?
21:43:02 <vishyweb> switched to mobile hotspot
21:43:05 <vishyweb> hopefully it stays
21:43:06 <ttx> vishyweb: in what country did they send you this time ?
21:43:18 <ttx> vishy: reposting
21:43:18 <vishyweb> anyway the quick update is that I haven't targetted blueprints yet
21:43:28 <ttx> Any way I can help in filling this up ?
21:43:45 <vishyweb> As per my email I am going to do a rough triage and assign them to various teams
21:43:52 <ttx> My other question was, do we have any significant thing that is already merged and that we should retrospectively add to the Essex list ?
21:43:57 <vishyweb> then work with team leads to narrow down the milestones
21:44:07 <vishyweb> there was the volume cleanup stuff
21:44:10 <ttx> I admit having not followed day-to-day essex merges
21:44:14 <vishyweb> i think it had a blueprint already though
21:44:23 <ttx> yes. I can resurrect that one
21:44:58 <ttx> #action ttx to dig the diablo blueprint grave and exhume the volume-cleanup blueprint and target it to essex1
21:45:09 <ttx> vishy: Anything else ?
21:46:07 <zykes-> ttx: question, is there any DNSaaS going on or that's thought of ?
21:46:24 <ttx> Let's move to open discussion before I answer that one
21:46:24 <ttx> #topic Open discussion
21:47:02 <ttx> zykes-: I guess it depends on what you mean by DNSaaS exactly. There is some effort on IP resources management
21:47:17 <ttx> through the "Melange" project
21:47:37 <ttx> if it's pure DNS, I don't think so
21:47:38 <danwent> melange is mostly focused on ip address management, as related to DHCP for now
21:47:53 <danwent> zykes: interested in chatting if this is something you'd like to work on.
21:48:00 <ttx> I had one open discussion topic... with more meetings being set up, calling this meeting "the Team meeting" is a bit misleading
21:48:10 <ttx> So I'm open to a rename...
21:48:24 <ttx> For example we can call it the "General meeting" or something like it, to emphasize the fact that all teams can ultimately report progress here
21:48:35 <ttx> Thoughts ?
21:48:37 <zykes-> ttx: i was more thing of a project to leverage typically PowerDNS which supports MySQL
21:48:44 <comstud> 'DNSaaS'
21:48:47 <comstud> a service as a service.
21:49:11 <zykes-> comstud: rs calls it i thing dnsaas ?
21:49:18 <ttx> Also, do you find the meeting reminder (on the ML) helpful ? Or just another email you ignore ?
21:49:20 <comstud> i think the name changed :)
21:49:24 <comstud> but i could be wrong
21:49:27 <ttx> I could send it out only when extra participation is needed.
21:49:46 <comstud> either way, I'll still make fun of it
21:49:49 <zns> #idea Rackspace uses a tool called UserVoice to capture customer feedback and requests (http://feedback.rackspacecloud.com/). At the Boston summit there was talk of finding a way to capture user (non-developer) feedback to help drive the roadmaps for projects. I'd like to propose we set up UserVoice for OpenStack to capture that. Let me know if this is the right meeting or if that should be a PPB topic.
21:50:55 <zykes-> danwent: sure i could be helping in creating something that could leverage either bind or powerdns in making authorative dns work
21:51:16 <ttx> looks like we don't have a quorum of opiniated people left
21:51:25 <danwent> zykes: sounds like fun.  we can help with how to plug it into quantum networks
21:51:36 <zykes-> or melange?
21:51:39 <zns> ttx: last part of that question was for you; on whether this is the right meeting to discuss this idea.
21:52:01 <danwent> zykes:  from a dataplane perspective, it would probably plug into quantum, from a network data perspective, might plug into melange.
21:52:09 <ttx> zns: I don't know enough about that tool to have an opinion
21:52:21 <ttx> looking
21:52:33 <ttx> oh, brainstorm like
21:53:10 <zns> Yes. Users use a limited number of votes to vote on the features they want most.
21:53:43 <zns> And they can request new features or vote on features others have proposed.
21:53:47 <jdg_> I don't know anything about the format, but capturing user input is something I think is a great idea
21:53:47 <ttx> zns: that sounds mostly useful when you don't really know what you want to work on
21:53:59 <zykes-> danwent: is there any design docs or something for Quantum ?
21:54:19 <zns> ttx: or when you don't know for sure what to work on first.
21:54:28 <ttx> zns: unfortunately, in some projects, that would end up with grumpy users complaining that the feature with 800+ votes never got done
21:54:38 <danwent> zykes: http://wiki.openstack.org/Quantum is the starting point
21:54:52 <danwent> there are also docs on http://docs.openstack.org/incubation
21:54:54 <ttx> zns: I definitely think it can help, at least for some projects
21:55:02 <ttx> zns: you should talk to stefano about it
21:55:17 <zykes-> ttx: whatever happened to spector
21:55:26 <danwent> zykes: developer docs are non-existent… netstack mailing list can help with that.
21:55:35 <zns> ttx: that would be a vlid complaint. 800+ votes means it is in demand. Why would a PTLignore that…
21:55:52 <zns> OK. Will reach out to him.
21:55:57 <ttx> zns: because a PTL has no real control over his developers ?
21:56:27 <ttx> zns: swift and keystone might have some reasonable control over their devs, but nova...
21:56:58 <ttx> zns: but I agree it could be a good resource for development teams to decide what's most needed
21:57:42 <ttx> last words ?
21:57:44 <zns> ttx: good point about PTL control. I sent Stefano and email. Will pick it up with him and/or the PPB. Thanks.
21:57:54 <zns> Bye? :-)
21:57:59 <ttx> #endmeeting