<div dir="ltr">Hi Murali,<div><br></div><div> There is already a ServiceVM project (Tacker), currently under development on stackforge:</div><div><br></div><div><a href="https://wiki.openstack.org/wiki/ServiceVM">https://wiki.openstack.org/wiki/ServiceVM</a><br></div><div><br></div><div> If you are interested in this topic, please take a look at the wiki page above and see if the project's goals align with yours. If so, you are certainly welcome to join the IRC meeting and start to contribute to the project's direction and design.</div><div><br></div><div>Thanks,</div><div>- Stephen</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 10, 2014 at 7:01 AM, Murali B <span dir="ltr"><<a href="mailto:mbirru@gmail.com" target="_blank">mbirru@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi keshava,<div><br></div><div>We would like contribute towards service chain and NFV </div><div><br></div><div>Could you please share the document if you have any related to service VM</div><div><br></div><div>The service chain can be achieved if we able to redirect the traffic to service VM using ovs-flows</div><div><br></div><div>in this case we no need to have routing enable on the service VM(traffic is redirected at L2).</div><div><br></div><div>All the tenant VM's in cloud could use this service VM services by adding the ovs-rules in OVS</div><div><br></div><div><br></div><div>Thanks</div><span class="HOEnZb"><font color="#888888"><div>-Murali</div><div><br></div><div><br></div><div><br></div></font></span></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>