Hi Vishal,

I’ve restarted my work on the blueprint last week now that Juno is open for 
development and OVS 2.1.0 is available, targeting juno-1. My plan is to have a 
working implementation available by the summit design discussion to make sure 
we cover all our bases. Between the blueprint page you referenced[0], this wiki 
page[1], and the Gerrit review[2] site, that is all the up-to-date information. 
Outside of those links, any other updates will be on this mailing list or the 
ML2 weekly IRC meeting.

I’m open to collaboration and interested in anything you are able to 
contribute. Do you have any existing work to share or feedback?

Amir

[0] https://blueprints.launchpad.net/neutron/+spec/ovs-firewall-driver
[1] https://wiki.openstack.org/wiki/Neutron/blueprint_ovs-firewall-driver
[2] https://review.openstack.org/#/q/topic:bp/ovs-firewall-driver,n,z

On Apr 7, 2014, at 3:33 AM, Thapar, Vishal (HP Networking) 
<vtha...@hp.com<mailto:vtha...@hp.com>> wrote:

Hi,

I am working on an OVS based implementation of Neutron Security Groups and came 
across this blueprint:
https://blueprints.launchpad.net/neutron/+spec/ovs-firewall-driver

I’ve gone through every mail, document and IRC chat log on this to get a good 
grasp of history on this, but couldn’t find any recent activity on this 
blueprint. It is listed on Meetings page on wiki but last meeting seems to have 
been held last year in December. I’ve just started working on prototyping this 
and would like to work with community to see it to completion.

Could anyone suggest on how to proceed on this? Do I need to request a meeting 
for this?

Thanks and Regards,
Vishal.
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to