On Mon, Mar 19, 2012 at 5:39 AM, Hiroshi DEMPO <d...@ah.jp.nec.com> wrote:
> Hello Dan > > Thanks for the proposed issues. > > > - better model for learning what extensions are supported by the > currently > > running plugin. > > I agree with this point and would contribute for the better model. > > As you know, we talked about our Qutantum plugin in the previous > OpenStack Conference. Now, the plugin is publicly available. > So it would be nice to share our experiences in next summit, which > will be feasible to the topic. > > In the slot, I would discuss other plugin models to have better model. > How do you think of that? > Hi Hiroshi, We look forward to hearing your thoughts. It would be best if you could write-up an email or blueprint with an outline of your thoughts for improvements. This way we can figure out whether your suggestions overlap with other sessions, or if it should be a separate session. Thanks, Dan > > Hiroshi > > > -----Original Message----- > > From: netstack-bounces+dem=ah.jp.nec....@lists.launchpad.net > > [mailto:netstack-bounces+dem=ah.jp.nec....@lists.launchpad.net] On > > Behalf Of Dan Wendlandt > > Sent: Tuesday, March 13, 2012 8:11 AM > > To: netstack@lists.launchpad.net > > Subject: [Netstack] quantum community projects & folsom summit plans > > > > Hi team, > > > > As we start to look forward to Folsom, I know there will be a lot of > excitement > > around shiny new directions we can take Quantum (L3, VPN/DCI, etc.). > This > > is great, and we will be moving in this direction during Folsom. I know > many > > people are looking to participate here. > > > > But I also want to stress the importance of also focusing on less shiny > tasks > > that are central to building a solid and usable platform. To this end, I > wanted > > to highlight a link I sent out during last weeks meeting: > > http://wiki.openstack.org/QuantumStarterBugs > > > > This page has a pointer to low-hanging fruit bugs as well as a list of > > "community projects" that are not necessarily shiny, but are critical to > the > > progress of the project. This includes things like improving the CLI, > > integrating with Horizon/Keystone, building a system test infrastructure, > > updating documentation, multi-host devstack, etc. > > > > In many cases, these are items that we targeted for Essex, but didn't > have > > sufficient core dev resources to tackle. With Quantum becoming core in > > Folsom, we can't afford to have that happen again, as expectations around > > Quantums usability, robustness and integration with other projects will > be > > much higher in Folsom than it was for Essex. > > > > I encourage others to add items to this page as well. My general rule is > that > > something is a community project if its unlikely that someone is doing > the > > work to enable something for their platform/company. As a hint, if a > bunch > > of people who express interesting in working on something, its probably > not a > > community project. If people have been saying "hey, someone should > really > > fix/improve X" for a while, the fix would help just about everyone, but > no > one > > has yet stepped forward, its probably a community project :) > > > > > > So in sum, as an open source project, we must make sure everyone is > > encouraged and rewarded for working on core community projects. I also > > want to make sure sufficient time at the summit is dedicated to how we > will > > progress on both community projects. > > > > Since we will soon be able to register sessions for the Folsom summits, > I'd like > > people to chime in on the list for what they think are the most important > > "community projects", as well as "shiny objects" for us to discuss at the > > summit. Hopefully this will make the process of designing sessions more > > collaborative and community-driver, rather than a game of "I better try > and > > register the session on X before someone else does". > > > > Here are some initial thoughts: > > > > community projects: > > - improve system test / devstack / tempest > > - quantum authn + authz (yes, we still do not have basic API auth) > > - better integration with openstack CI team (we want automated smoketests > > to run on each check-in) > > - quantum CLI / client improvements. (many changes needed to be more > > inline with other core projects) > > - reworking of quantum / nova integration (remove dependence on nova db, > > etc.) > > - better model for learning what extensions are supported by the > currently > > running plugin. > > - quantum + horizon GUI flow (and framework for widgets that use API > > extensions). > > - melange / quantum integration > > - DHCP API / service > > > > shiny objects: > > - L3 API > > - VPN / data-center-interconnect > > - firewalling / security groups. > > > > Please reply with your own input. Thanks, > > > > Dan > > > > > > -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dan Wendlandt Nicira Networks: www.nicira.com twitter: danwendlandt ~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
