Hi Willian, All,
Thanks for your thoughts on this. The discussions around L3 abstractions/API have been ongoing for a while now. To be precise, the discussions started during the Essex design summit, and we took action items away from the summit to work during the past few months. Subsequently, a fair amount of thought and work have gone into this resulting in a blueprint: https://blueprints.launchpad.net/quantum/+spec/quantum-l3-api, wiki: http://wiki.openstack.org/quantum-l3 and, also a working framework which realizes this blueprint: https://github.com/CiscoSystems/quantum/tree/int/l3apiframework. There has been good feedback around this from several folks, and I encourage others to comment as well so that we can have a good plan going into the summit. Thanks, ~Sumit. From: netstack-bounces+snaiksat=cisco....@lists.launchpad.net [mailto:netstack-bounces+snaiksat=cisco....@lists.launchpad.net] On Behalf Of Willian Molinari Sent: Thursday, March 29, 2012 12:50 PM To: netstack@lists.launchpad.net Subject: [Netstack] Kickstart for Layer 3 discussions Æ!! Hi folks, I just want to start the discussions around the layer 3 on quantum. We developed a plugin to handle firewalls and dhcps, but reading the melange spec I found that melange would handle DHCP too. For firewall we have an agent to handle rules using python-iptables library on a different package installed on the firewall server and we're planning to implement routing tables as well. These are our ideas on L3. What do you have in mind? -- Willian Molinari (a.k.a PotHix)
-- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
