On 10 June 2014 18:18, Irena Berezovsky <ire...@mellanox.com> wrote: > Hi Luke, > > Very impressive solution! >
Thanks for the kind words! > > > I do not think there is a problem to keep agent out of the tree in a short > term, but would highly recommend to put it upstream in a longer term. > > You will benefit from quite valuable community review. And most important > it will allow to keep your code as much as possible aligned with neutron > code base. Once there are some general changes done by other people, your > code will be taken into account and won’t be broken accidentally. > Yes, I agree. We do want to be upstream going forward. For the Juno cycle our modest goal is that users will be able to deploy our software with an unmodified OpenStack Juno. On the OpenStack side this only requires a simple VIF type (Nova) and ML2 mech driver (Neturon). Behind the scenes we are doing a lot of work together with the upstream QEMU community to make this possible. Hopefully we will be able to expand our upstream OpenStack ambitions in the K-cycle. Looking forward to setting the next goals in Paris :-). Currently our project is relatively new and unknown, but I hope there will be a lot of involvement within the OpenStack community going forward. Our goal is to create a practical NFV solution that is 100% open source and we hope this will be useful to a lot of people. (http://snabb.co/nfv.html) P.S. Thanks for the reminder about modular ML2 agent! Cheers, -Luke
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
