<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, Sans-Serif;font-size:13px"><div><span>Nice articles Akilesh. </span></div> <div class="qtdSeparateBR"><br><br></div><div class="yahoo_quoted" style="display: block;"> <div style="font-family: HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 13px;"> <div style="font-family: HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 12px;"> <div dir="ltr"> <font size="2" face="Arial"> On Tuesday, 30 September 2014 12:56 PM, Akilesh K <akilesh1597@gmail.com> wrote:<br> </font> </div> <br><br> <div class="y_msg_container"><div id="yiv7482734996"><div><div dir="ltr">Sorry the correct links are<br clear="none">1.<a rel="nofollow" shape="rect" target="_blank" href="http://fosskb.wordpress.com/2014/06/25/a-bite-of-virtual-linux-networking/">
Comparison between networking devices and linux software components</a><br clear="none">2. <a rel="nofollow" shape="rect" target="_blank" href="http://fosskb.wordpress.com/2014/06/10/managing-openstack-internaldataexternal-network-in-one-interface/">Openstack ovs plugin configuration for single/multi machine setup</a><br clear="none">3. <a rel="nofollow" shape="rect" target="_blank" href="http://fosskb.wordpress.com/2014/06/19/l2-connectivity-in-openstack-using-openvswitch-mechanism-driver/">Neutron ovs plugin layer 2 connectivity</a><br clear="none">4. <a rel="nofollow" shape="rect" target="_blank" href="http://fosskb.wordpress.com/2014/09/15/l3-connectivity-using-neutron-l3-agent/">Layer 3 connectivity using neutron-l3-agent</a><br clear="none"></div><div class="yiv7482734996yqt4305982045" id="yiv7482734996yqt12390"><div class="yiv7482734996gmail_extra"><br clear="none"><div class="yiv7482734996gmail_quote">On Tue, Sep 30, 2014 at 12:50 PM, Andreas
Scheuring <span dir="ltr"><<a rel="nofollow" shape="rect" ymailto="mailto:scheuran@linux.vnet.ibm.com" target="_blank" href="mailto:scheuran@linux.vnet.ibm.com">scheuran@linux.vnet.ibm.com</a>></span> wrote:<br clear="none"><blockquote class="yiv7482734996gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi Ageeleshwar,<br clear="none">
the links you provided are wordpress admin links and require a login. Is<br clear="none">
there also a public link available?<br clear="none">
Thanks<br clear="none">
--<br clear="none">
Andreas<br clear="none">
(irc: scheuran)<br clear="none">
<div><div class="yiv7482734996h5"><br clear="none">
<br clear="none">
On Tue, 2014-09-30 at 09:33 +0530, Akilesh K wrote:<br clear="none">
> Hi,<br clear="none">
><br clear="none">
> I saw the table of contents. I have posted documents on configuring<br clear="none">
> openstack neutron-openvswitch-plugin, comparison between networking<br clear="none">
> devices and thier linux software components and also about the working<br clear="none">
> principles of neutron-ovs-plugin at layer 2 and neutron-l3-agent at<br clear="none">
> layer 3 . My intention with the posts was to aid begginers in<br clear="none">
> debugging neutron issues.<br clear="none">
><br clear="none">
><br clear="none">
> The problem is that I am not sure where exactly these posts fit in the<br clear="none">
> topic of contents. Anyone with suggestions please reply to me. Below<br clear="none">
> are the link to the blog posts<br clear="none">
><br clear="none">
><br clear="none">
> 1. Comparison between networking devices and linux software components<br clear="none">
><br clear="none">
> 2. Openstack ovs plugin configuration for single/multi machine setup<br clear="none">
><br clear="none">
> 3. Neutron ovs plugin layer 2 connectivity<br clear="none">
><br clear="none">
> 4. Layer 3 connectivity using neutron-l3-agent<br clear="none">
><br clear="none">
><br clear="none">
> I would be glad to include sub sections in any of these posts if that<br clear="none">
> helps.<br clear="none">
><br clear="none">
><br clear="none">
> Thank you,<br clear="none">
> Ageeleshwar K<br clear="none">
><br clear="none">
><br clear="none">
> On Tue, Sep 30, 2014 at 2:36 AM, Nicholas Chase <<a rel="nofollow" shape="rect" ymailto="mailto:nchase@mirantis.com" target="_blank" href="mailto:nchase@mirantis.com">nchase@mirantis.com</a>><br clear="none">
> wrote:<br clear="none">
> As you know, we're always looking for ways for people to be<br clear="none">
> able to contribute to Docs, but we do understand that there's<br clear="none">
> a certain amount of pain involved in dealing with Docbook. So<br clear="none">
> to try and make this process easier, we're going to try an<br clear="none">
> experiment.<br clear="none">
><br clear="none">
> What we've put together is a system where you can update a<br clear="none">
> wiki with links to content in whatever form you've got it --<br clear="none">
> gist on github, wiki page, blog post, whatever -- and we have<br clear="none">
> a dedicated resource that will turn it into actual<br clear="none">
> documentation, in Docbook. If you want to be added as a<br clear="none">
> co-author on the patch, make sure to provide us the email<br clear="none">
> address you used to become a Foundation member.<br clear="none">
><br clear="none">
> Because we know that the networking documentation needs<br clear="none">
> particular attention, we're starting there. We have a<br clear="none">
> Networking Guide, from which we will ultimately pull<br clear="none">
> information to improve the networking section of the admin<br clear="none">
> guide. The preliminary Table of Contents is here:<br clear="none">
> <a rel="nofollow" shape="rect" target="_blank" href="https://wiki.openstack.org/wiki/NetworkingGuide/TOC">https://wiki.openstack.org/wiki/NetworkingGuide/TOC</a> , and the<br clear="none">
> instructions for contributing are as follows:<br clear="none">
><br clear="none">
</div></div>> 1. Pick an existing topic or create a new topic. For new<br clear="none">
<span class="yiv7482734996">> topics, we're primarily interested in deployment<br clear="none">
> scenarios.<br clear="none">
</span>> 2. Develop content (text and/or diagrams) in a format<br clear="none">
<span class="yiv7482734996">> that supports at least basic markup (e.g., titles,<br clear="none">
> paragraphs, lists, etc.).<br clear="none">
</span>> 3. Provide a link to the content (e.g., gist on<br clear="none">
<span class="yiv7482734996">> <a rel="nofollow" shape="rect" target="_blank" href="http://github.com/">github.com</a>, wiki page, blog post, etc.) under the<br clear="none">
> associated topic.<br clear="none">
</span>> 4. Send e-mail to reviewers <a rel="nofollow" shape="rect" ymailto="mailto:networking@openstacknow.com" target="_blank" href="mailto:networking@openstacknow.com">networking@openstacknow.com</a>.<br clear="none">
> 5. A writer turns the content into an actual patch, with<br clear="none">
<div class="yiv7482734996HOEnZb"><div class="yiv7482734996h5">> tracking bug, and docs reviewers (and the original<br clear="none">
> author, we would hope) make sure it gets reviewed and<br clear="none">
> merged.<br clear="none">
><br clear="none">
> Please let us know if you have any questions/comments.<br clear="none">
> Thanks!<br clear="none">
><br clear="none">
> ---- Nick<br clear="none">
> --<br clear="none">
> Nick Chase<br clear="none">
> 1-650-567-5640<br clear="none">
> Technical Marketing Manager, Mirantis<br clear="none">
> Editor, OpenStack:Now<br clear="none">
><br clear="none">
> _______________________________________________<br clear="none">
> OpenStack-dev mailing list<br clear="none">
> <a rel="nofollow" shape="rect" ymailto="mailto:OpenStack-dev@lists.openstack.org" target="_blank" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br clear="none">
> <a rel="nofollow" shape="rect" target="_blank" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br clear="none">
><br clear="none">
><br clear="none">
><br clear="none">
> _______________________________________________<br clear="none">
> OpenStack-dev mailing list<br clear="none">
> <a rel="nofollow" shape="rect" ymailto="mailto:OpenStack-dev@lists.openstack.org" target="_blank" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br clear="none">
> <a rel="nofollow" shape="rect" target="_blank" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br clear="none">
<br clear="none">
<br clear="none">
_______________________________________________<br clear="none">
OpenStack-dev mailing list<br clear="none">
<a rel="nofollow" shape="rect" ymailto="mailto:OpenStack-dev@lists.openstack.org" target="_blank" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br clear="none">
<a rel="nofollow" shape="rect" target="_blank" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br clear="none">
</div></div></blockquote></div><br clear="none"></div></div></div></div><br><div class="yqt4305982045" id="yqt46735">_______________________________________________<br clear="none">OpenStack-dev mailing list<br clear="none"><a shape="rect" ymailto="mailto:OpenStack-dev@lists.openstack.org" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br clear="none"><a shape="rect" 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 clear="none"></div><br><br></div> </div> </div> </div> </div></body></html>