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