Open Stack

we are not sure if we can or should have multi-host feature of 
nova-network flavour.
the merged 
https://blueprints.launchpad.net/quantum/+spec/quantum-scheduler is 
allowing us to have multiple l3 agents.
There each l3 agent can host many routers, but one router can be hosted 
just by one l3 agent.

On 03/05/2013 10:55 AM, Shake Chen wrote:
>
>
>
>
> On Tue, Mar 5, 2013 at 10:00 AM, Nathanael Burton 
> <nathanael.i.burton at gmail.com <mailto:nathanael.i.burton at gmail.com>> 
> wrote:
>
>     Shake, I believe that was moved to this [1] blueprint and
>     (mostly?) merged.
>
>     [1] - https://blueprints.launchpad.net/quantum/+spec/quantum-scheduler
>
>
>
> Thanks.
>
>
>
>
>     On Mon, Mar 4, 2013 at 8:35 PM, Shake Chen <shake.chen at gmail.com
>     <mailto:shake.chen at gmail.com>> wrote:
>
>
>
>         On Tue, Mar 5, 2013 at 3:59 AM, Mark McClain
>         <mark.mcclain at dreamhost.com
>         <mailto:mark.mcclain at dreamhost.com>> wrote:
>
>             Hi-
>
>             I'm writing to announce my candidacy for the Quantum PTL.
>              The Quantum team has done a great job during the Grizzly
>             cycle and I'm excited about what's ahead for the Havana
>             cycle.  My work at DreamHost provides me a unique
>             perspective of deploying Quantum at scale using both IPv4
>             and IPv6.  Working for a deployer also reinforces my
>             desire for a vibrant, multi-vendor ecosystem within Quantum.
>
>             Qualifications
>             -------------------
>
>             I am a Quantum core developer with 13 years of commercial
>             Python development experience.  During my career, I have
>             developed and deployed network applications based on the
>             same underlying libraries as Quantum.  I started
>             contributing to Quantum during the Essex development
>             cycle.  In Folsom, I was promoted to core and was the
>             primary developer of the DHCP implementation and Quantum's
>             network namespace library.
>
>             Grizzly Accomplishments
>             ----------------------------------
>
>             In the Grizzly cycle,  I worked both as a developer and a
>             core team member.
>
>             Grizzly Development:
>             - Added Metadata Service Support to Quantum. (Quantum High
>             Priority)
>             - Developed database migration framework for Quantum to
>             support all plugins. (Quantum Essential Priority)
>             - Developed the LBaaS Agent Reference Implementation.
>             (Quantum High Priority)
>             - Added support for preserving NIC ordering when booting
>             an instance attached to Quantum. (Nova High Priority Bug)
>
>             Grizzly Core Team:
>             - Second most active reviewer on the Quantum team.
>             - Leader of the L3/IPAM/DHCP and Database sub teams.
>             - Led triaging and sub-team assignment of bugs.
>             - Assisted members of the community to further their
>             understanding of Quantum and improve Python development
>             best practices.
>             - Interfaced with vendors new to Quantum and helped in the
>             integration of their plugins.
>                     (core reviewer on 4 of the new vendor plugins
>             included with Grizzly)
>             - Worked to promote Quantum by presenting at regional
>             OpenStack Meetups in both Atlanta and Los Angeles.
>
>
>             Havana
>             -----------
>
>             During the Havana development cycle, I'd like to see the
>             team focus on:
>
>             - Continuing to grow the community of contributors and
>             code reviewers.
>             - Improving documentation for both deployers and developers.
>             - Improving database resource modeling and extension
>             management.
>             - Collaborating with the Nova team to make Quantum the
>             default network implementation.
>             - Leveraging the service insertion framework to add new
>             services (i.e. VPN).
>             - Modularization of L2 and L3.
>             - L3 improvements (ACLs, better IPv6, pluggable IPAM).
>             - Integrating plugins from vendors new to the community
>             including LBaaS plugins/drivers.
>             - Further work to ease deploying at scale.
>             - More efficient Quantum system testing and gating.
>             - Supporting the Horizon team for better Quantum integration.
>
>
>         I have question: seem miss the feature  Quantum Multi-host
>         DHCP and L3
>         https://blueprints.launchpad.net/quantum/+spec/quantum-multihost
>
>         lack of the feature, seem impossible instead of the nova network.
>
>
>             I'd love the chance to be the PTL and work with the
>             Quantum team to fill in gaps in this list during the
>             summit in Portland.
>
>             Thanks,
>
>             mark
>             _______________________________________________
>             OpenStack-dev mailing list
>             OpenStack-dev at lists.openstack.org
>             <mailto:OpenStack-dev at lists.openstack.org>
>             http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
>         -- 
>         Shake Chen
>
>
>         _______________________________________________
>         OpenStack-dev mailing list
>         OpenStack-dev at lists.openstack.org
>         <mailto:OpenStack-dev at lists.openstack.org>
>         http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>     _______________________________________________
>     OpenStack-dev mailing list
>     OpenStack-dev at lists.openstack.org
>     <mailto:OpenStack-dev at lists.openstack.org>
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
> -- 
> Shake Chen
>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130305/f1088137/attachment.html>