21:02:06 <markmcclain> #startmeeting quantum
21:02:06 <openstack> Meeting started Mon Mar 25 21:02:06 2013 UTC.  The chair is markmcclain. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:02:07 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:02:10 <openstack> The meeting name has been set to 'quantum'
21:02:19 <gongysh> hi
21:02:21 <sthakkar> hi
21:02:39 <markmcclain> #info agenda: https://wiki.openstack.org/wiki/Network/Meetings
21:03:04 <SumitNaiksatam> hi
21:03:07 <markmcclain> #topic Announcements
21:03:13 <markmcclain> danwent: RC2 update
21:03:35 <danwent> #info we expect to release RC2 pretty soon after the meeting today, assuming nothing unexpected pops up
21:03:53 <danwent> #info barring a real blocker, this will be our final grizzly release
21:04:19 <danwent> #info additional bugs will be tagged for backport, but will wait until the next stable release.
21:04:25 <danwent> that's it for me for announcments
21:04:39 <markmcclain> Any other announcements from the team?
21:05:00 <markmcclain> #topic Grizzly RC2 bugs
21:05:23 <markmcclain> We currently have two bugs left to backport to RC2
21:05:30 <markmcclain> https://bugs.launchpad.net/quantum/+bug/1158468
21:05:31 <uvirtbot> Launchpad bug 1158468 in quantum "Syntax error in XML Serializer" [High,Fix committed]
21:05:37 <markmcclain> https://bugs.launchpad.net/quantum/+bug/1097992
21:05:40 <uvirtbot> Launchpad bug 1097992 in quantum "SQL DB Pools throwing stacktrace" [Medium,Fix committed]
21:06:11 <markmcclain> Otherwise, we there are no known release blockers.  Have we missed any relevant bugs for the release?
21:06:13 <danwent> markmcclain: i can probably backport and post reviews during mtg.
21:06:32 <markmcclain> using your new found free time? :)
21:06:39 <danwent> markmcclain: you know it!
21:07:23 <markmcclain> #topic  Quantum Client
21:07:40 <markmcclain> gongysh: How are the client docs?
21:07:57 <markmcclain> https://bugs.launchpad.net/openstack-manuals/+bug/1156505
21:07:59 <uvirtbot> Launchpad bug 1156505 in openstack-manuals "document for quantum client 2.2.0" [High,Confirmed]
21:08:26 <gongysh> in progress
21:08:53 <markmcclain> ok.. do you have all of the information you need?
21:09:19 <gongysh> I will do as what I have and then we can review.
21:09:33 <markmcclain> sounds good
21:09:52 <markmcclain> Any questions for the client sub-team?
21:10:23 <markmcclain> # topic Grizzly Documentation
21:10:36 <danwent> ok
21:10:38 <markmcclain> danwent: want to update?
21:10:51 <danwent> we got some key patches merged last week
21:11:03 <danwent> general updates to install documentation, and to nova configuration (for Ubuntu)
21:11:18 <danwent> i'm not sure, but I think the fedora stuff still needs equivalent updates.
21:11:34 <danwent> i don't see garyk or rkukura around today… i think they are both OOO
21:11:48 <danwent> #todo #danwent talk to garyk and rkukura about updating fedora install
21:12:06 <danwent> in terms of what is still left.   a couple of links:
21:12:09 <danwent> #link https://wiki.openstack.org/wiki/Network/GrizzlyDocImpact
21:12:23 <danwent> https://bugs.launchpad.net/openstack-manuals/+bugs?field.tag=quantum
21:12:32 <danwent> #link api guide: https://bugs.launchpad.net/openstack-api-site/+bugs?field.tag=netconn-api
21:12:46 <danwent> salv-orlando: since you were out last week and we skipped the api guide stuff, how about we talk about that first.
21:12:55 <salv-orlando> ok
21:12:56 <danwent> what are biggest gaps we need to plug, and are they currently assigned?
21:13:04 <salv-orlando> All the gaps are assigned.
21:13:23 <salv-orlando> I think we also have patches for lbaas
21:13:48 <salv-orlando> nati-ueno has not yet confirmed he will work on security groups ands extra_route
21:14:11 <salv-orlando> (or I've missed an email from him confirming that he will take these two extensions)
21:14:14 <danwent> salv-orlando: so are api docs now on a different gerrit reivew page than admin guide?
21:14:25 <salv-orlando> they're still there
21:14:32 <salv-orlando> but the project is net conn-api
21:14:36 <salv-orlando> not openstack-manuals
21:14:52 <danwent> https://review.openstack.org/#/q/status:open+project:openstack/netconn-api,n,z
21:15:03 <danwent> i don't see lbaas patch, or am i looking in wrong place?
21:15:38 <salv-orlando> nope you're right
21:15:53 <danwent> Ok, well, release is about a week away, so we really need to push and close out the key documentation
21:16:02 <salv-orlando> I misinterpreted an email I received this afternoon, sorry about that
21:16:25 <danwent> if something is highlighted as something we "delivered" in grizzly, and people aren't able to find docs, that reflects badly on openstack
21:16:29 <salv-orlando> I will sync up with enikanorov as the LBaaS API doc is vast, and he might need help
21:16:40 <danwent> (btw, that comment was not directled at anyone in particular… we all need to pitch in)
21:17:00 <danwent> #info all key grizzly api doc items are assigned, but  many of them are not yet in review
21:17:06 <danwent> ok, on to admin guide
21:17:43 <danwent> lbaas is currently assigned to me, but has been lower priority than other patches
21:17:44 <danwent> https://bugs.launchpad.net/openstack-manuals/+bug/1156828
21:17:45 <uvirtbot> Launchpad bug 1156828 in openstack-manuals "q-admin: basic lbaas workflow" [High,Confirmed]
21:17:50 <danwent> https://bugs.launchpad.net/openstack-manuals/+bug/1157034
21:17:52 <uvirtbot> Launchpad bug 1157034 in openstack-manuals "quantum lbaas install - Ubuntu" [High,New]
21:18:13 <danwent> if someone wants to steal that from me, i would not complain, otherwise I will get to it, but only after i'm back from travel (i.e., later this week)
21:18:29 <danwent> arosen: it looks like security groups are in good shape for admin guide?
21:18:43 <danwent> i saw some minor enhancements you have posted, but the bulk seems in
21:18:46 <arosen> yup, i have this doc patch out for review https://bugs.launchpad.net/openstack-manuals/+bug/1158527
21:18:47 <uvirtbot> Launchpad bug 1158527 in openstack-manuals "update enable_ping_and_ssh example to include quantum security groups" [Undecided,In progress]
21:19:03 <arosen> but after that i think we should be good.
21:19:15 <danwent> markmcclain: on your end, i believe you said you will have db-migration and metadata stuff posted for review soon?
21:19:23 <markmcclain> yep
21:19:40 <danwent> arosen: is sameer no longer doing security groups API work?
21:19:57 <danwent> arosen: i thought i heard salv-orlando say that nati_ueno may be doing it.
21:20:10 <nati_ueno> yes I'm working on it.
21:20:11 <arosen> danwent:  I believe sameer is still doing it. I
21:20:20 <nati_ueno> I'll push the doc in this week for review
21:20:31 <arosen> nati_ueno:  have you started i believe sameer already has.
21:20:44 <nati_ueno> gaha
21:20:50 <arosen> i'll send out an email with him and you on it so we can sort this out offline.
21:20:53 <nati_ueno> ok could you send me the point?
21:20:56 <danwent> gongysh: multi-agent stuff is still up for review, but will merge soon i suspect? https://review.openstack.org/#/c/18650/
21:21:02 <nati_ueno> s/point/pointer/
21:21:13 <gongysh> danwent: yes, it is a slow progress.
21:21:57 <danwent> gongysh: ok, i reviewed and it looks like you addressed my comments.  i have not tested it though.  i'm ok approving as is if others have done a thorough test
21:22:42 <danwent> ok, so i think lbaas, metadata, and db migration are most critical items that need to go into review soon.
21:23:07 <danwent> fedora install is a question mark… they may be waiting until the fedora test day (april 2nd?) to update
21:23:12 <gongysh> danwent:  garyk is not vocation, often he will test it for me.
21:23:19 <gongysh> not -> on.
21:23:30 <danwent> anything else major that people see as missing?
21:23:57 <danwent> is amotoki out today?
21:24:28 <danwent> #todo #danwent ping amotoki about horizon + quantum docs.
21:24:47 <danwent> we at least need to make sure we've documented how to enable certain things (e.g., lbaas) when running horizon
21:25:15 <danwent> the new horizon has a lot of great quantum support, if you guys haven't seen it recently (we just recently updated our prod cloud to it… very cool!0
21:25:17 <danwent> )
21:25:25 <danwent> ok, markmcclain i think that's it for docs
21:26:21 <markmcclain> good stuff
21:26:54 <markmcclain> looks like we have one big push left to get the docs ready for the Grizzly release
21:27:16 <markmcclain> #topic Horizon
21:27:50 <markmcclain> amotoki updated the agenda and it looks like there are no release blockers in Horizon that relate to Quantum
21:28:02 <markmcclain> #topic Havana Summit
21:28:18 <markmcclain> #info The summit is three weeks away
21:28:25 <markmcclain> #link http://www.openstack.org/summit/portland-2013/
21:28:39 <markmcclain> #info Quantum sessions are Monday, Tuesday, and Wednesday
21:28:58 <markmcclain> #info Use http://summit.openstack.org to propose sessions.
21:29:25 <markmcclain> A couple of reminders:
21:30:15 <markmcclain> It's not who about who proposes first…. if we have multiple proposals we will most likely merge the sessions
21:30:43 <markmcclain> It is critical that have we have a healthy balance of Community Projects vs Shiny Features
21:31:15 <gongysh> what is ' Community Projects'?
21:31:29 <markmcclain> gongysh: good questsion
21:31:42 <gongysh> yeah, I think it is. :)
21:31:45 <markmcclain> Your work on Mutli-host L3 is a perfect example of a community project
21:32:11 <danwent> yeah, its about something that is of value to the whole community
21:32:25 <gongysh> I thought it is shiny feature too. :)
21:32:41 <danwent> and often is important to achieving a key team goal, like nova parity, or better usability, .etc
21:32:59 <danwent> lbaas or any Xaas is my best definition of a "shiny feature"
21:33:12 <markmcclain> that's my definition too
21:33:39 <markmcclain> danwent and I have been keeping a list of community projects and I'd like to highlight a few
21:33:45 <gongysh> ok, got it. thanks.
21:33:48 <danwent> i think the metadata improvements markmcclain this year, and the db-migration, are other examples of great community projects
21:34:19 <danwent> not specific or strategic to any vendor in particular, but critical to making quantum better for everyone
21:34:44 <danwent> one other note on session proposals
21:35:17 <danwent> not everything we plan on doing in havana needs to be a session.  we should reserve session in particular for things that need a lot of discussion and or coordination with other projects.
21:35:52 <danwent> if you have someone that you plan on working on, but is likely small, we may do a "lighting session" approach were people get 15 minute slots just to alert the team about what they are doing.
21:36:09 <danwent> so in your proposals, its great if you can comment on whether you think you need a full slot or not
21:36:10 <nati_ueno> +1 for lighting session
21:36:39 <danwent> ok, i'm done.  markmcclain, sorry for interrupting
21:36:58 <gongysh> so what about multihost, do we need a session or lighting sesssion, or just do it as is?
21:37:02 <sthakkar> yep lightening rounds seem like a good idea
21:37:06 <sthakkar> brainstorm and tackle what we can
21:37:08 <markmcclain> danwent: thanks filling in the gaps
21:38:16 <markmcclain> sthakkar: just make sure to indicate in your proposal if it is a lightning talk
21:38:41 <markmcclain> gongysh: not sure if we need a full session on multi-host
21:38:43 <danwent> gongysh: multi-host is critical to potential discussions around deprecating nova-network
21:38:56 <danwent> so it may come up in that session as well.
21:39:18 <markmcclain> russellb and I have already scheduled sessions to discuss Nova and Quantum
21:39:23 <danwent> i think the key thing to highlight would be any differences from what people can do today we nova.
21:39:37 <danwent> (that was referring to yong's question abotu multi-host)
21:40:03 <markmcclain> to examine the remaining gaps and discuss the steps to deprecate nova-network
21:40:18 <gongysh> I can make a presentation what I have and what nova can do. I can show nova's old way, and quantum's new way.
21:40:41 <danwent> markmcclain: who is point on the nova/quantum sessions?
21:40:52 <markmcclain> russellb and I sharing
21:41:06 <markmcclain> gongysh: can you file a proposal so it's tracked?
21:41:18 <gongysh> what is the URL of the nova/quantum sessions?
21:41:27 <gongysh> markmcclain: ok
21:41:43 <danwent> markmcclain: ok, gongysh has done some good investigation into gaps beyond multihost (e.g., dhs mechanisms)
21:42:56 <danwent> ok, and markmcclain deadline for sessions is end of march?
21:43:40 <markmcclain> yes… the deadline is March 31st as we would like to build the schedule next week
21:44:19 <danwent> #info deadline for summit proposals is March 31st
21:44:43 <danwent> if need be, I believe PTL can register sessions beyond then, so if we identify any gaps at next week's team meeting, we can still get sessions in for those.
21:44:53 <markmcclain> thanks for adding the info tag
21:45:05 <markmcclain> right.. I can add sessions if we miss something
21:45:21 <gongysh> http://summit.openstack.org/cfp/edit/203  quantum multihost
21:45:29 <danwent> gongysh: thx
21:45:33 <markmcclain> gongysh: thanks for adding
21:45:42 <markmcclain> On agenda there's a list of several of community topics that Dan and I would like to see discussed
21:45:51 <zyluo> S/edit/details/g
21:46:44 <danwent> i particularly would like everyone to spend some time thinking about "how to make quantum simpler"
21:46:48 <gongysh> zyluo: thanks
21:46:54 <markmcclain> danwent: +1
21:46:56 <zyluo> Gongysh's url I'm referring to
21:47:25 <danwent> we spend a lot of time adding config options, new capabilities, etc.  we should also spend time making sure its easy to get things going from a basic setup, making it harder to make common config mistakes we see asking about on the MLs, etc.
21:48:15 <salv-orlando> danwent: make quantum simpler -> -2 each patch which adds a new config option!
21:48:19 <salv-orlando> jk
21:48:27 <danwent> :P
21:48:30 <arosen> salv-orlando:  lol
21:48:37 <markmcclain> salv-orlando: haha
21:48:54 <salv-orlando> every time a new config option is added a system engineer somewhere in the world, cries
21:48:56 <danwent> and +2 each patch that removes one?
21:49:11 <sthakkar> lol
21:49:25 <salv-orlando> please give a smile to system engineers throughout the world - help us removing config options is they're not strictly needed
21:50:06 <markmcclain> I definitely hear it from our SysEng staff about config options
21:50:29 <gongysh> that is the fact of communit project. we have many features, they are optional, or have many choice.
21:51:27 <gongysh> the core is to make the basic features work without many options needed.
21:51:37 <markmcclain> gongysh: choice is good when deployers understand the options available, but we need to make sure the basic deployment is straight forward
21:52:19 <markmcclain> We have several L3 community topics to think about: IPv6 Support, Pluggable IPAM, modular L3
21:52:33 <gongysh> markmacclain: yes. So I sugguest to remove metadata's REST API call, and then we can remove some options changed.
21:53:03 <salv-orlando> I think those suggestions are best moved offline
21:53:16 <salv-orlando> (only 7 minutes left)
21:53:25 <danwent> yeah… markmcclain is there anything on improving extensions to the db model?
21:53:43 <markmcclain> oops… missed that in the cut in paste
21:54:03 <markmcclain> yeah.. I'd like to revisit the DB model extensions
21:54:04 <danwent> salv-orlando: i wonder if there's something similar with the authz framework
21:54:22 <danwent> basically, it should be easy for a plugin to add a field to an existing object like a network
21:54:33 <danwent> without having to add new tables, or new authz-related calls
21:55:13 <danwent> ok, 5 mins left
21:55:23 <salv-orlando> danwent: I have already a blueprint in progress for freeing up from authZ calls
21:55:31 <danwent> salv-orlando: ok, great
21:55:46 <markmcclain> Another area I'd like to discuss is testing: better unit tests, Tempest tests, and Quantum calls within Nova
21:56:27 <markmcclain> so if you want to propose some of the items listed in the agenda please do
21:56:33 <salv-orlando> I think these are 3 distinct projects
21:56:58 <salv-orlando> I mean, they deserve to be 3 distinct projects
21:57:09 <markmcclain> salv-orlando: correct
21:57:09 <danwent> salv-orlando: i might also suggest that we have sync sessions with other projects, like horizon + heat
21:57:31 <danwent> as its much easier to coordiante at the summit, and helpful to let those projects know what we expect to do, and what changes will be required from them.
21:57:38 <markmcclain> I've been in the process of reaching out to the other projects
21:58:10 <danwent> markmcclain: awesome
21:58:38 <markmcclain> So file your summit proposals… we will also be reaching out to community members to lead some sessions on important community topics
21:58:54 <markmcclain> #topic Open Discussion
21:59:08 <danwent> (but not until you're done writing your documentation!  remember, its not about who files first :P)
21:59:12 <danwent> https://review.openstack.org/#/q/status:open+project:openstack/quantum+branch:milestone-proposed,n,z
21:59:20 <danwent> those are last two fixes for RC2
21:59:26 <danwent> on milestone-proposed
21:59:34 <markmcclain> danwent: thanks for backporting
21:59:58 <gongysh> I think HP's guy will interested in 'DNS in quantum'.
22:00:15 <markmcclain> yep
22:00:18 <danwent> markmcclain: i am running to a meeting for next 1.5 hours.  but will be online after that if anything else is needed.  can you contact ttx once they merge and let him know we're good to go?
22:00:30 <markmcclain> Ok.. we're out of time.. I'll be around for little longer
22:00:32 <markmcclain> #endmeeting