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