<div dir="ltr">I would prefer not to be strict on the requirements for diagrams.<div>If it looks ok in ascii - that's fine, <span style="font-family:arial,sans-serif;font-size:13px">nwdiag is fine as well.</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px">I think both of tools worth mentioning in bp template.</span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Thanks,</span></div>
<div><font face="arial, sans-serif">Eugene.</font></div><div><font face="arial, sans-serif"><br></font></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Apr 17, 2014 at 12:06 AM, Alan Kavanagh <span dir="ltr"><<a href="mailto:alan.kavanagh@ericsson.com" target="_blank">alan.kavanagh@ericsson.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Tend to agree Nachi, that would be my preference, especially when the diagrams are fairly complex which is the case most of the time in Neutron. However if the BP is long lived then I think it makes sense to use ASCII, but if its short for a small feature to be included in next release then I agree the simplest and quickest way is a better use of our time.<br>
<span class="HOEnZb"><font color="#888888"><br>
/Alan<br>
</font></span><div class="im HOEnZb"><br>
-----Original Message-----<br>
From: Nachi Ueno [mailto:<a href="mailto:nachi@ntti3.com">nachi@ntti3.com</a>]<br>
Sent: April-16-14 3:19 PM<br>
To: OpenStack Development Mailing List (not for usage questions)<br>
Subject: Re: [openstack-dev] [neutron] Neutron BP review process for Juno<br>
<br>
</div><div class="HOEnZb"><div class="h5">Hi folks<br>
<br>
I don't think to use ASCII digrams is good idea because it is hard to maintenance & update diagrams..<br>
so I would like to recommend Blockdiag & Netdiag which are plugins for sphinx.<br>
<br>
Blockdiag<br>
<a href="http://blockdiag.com/en/blockdiag/" target="_blank">http://blockdiag.com/en/blockdiag/</a><br>
<br>
blockdiag {<br>
A -> B -> C -> D;<br>
A -> E -> F -> G;<br>
}<br>
<br>
will be<br>
<a href="http://blockdiag.com/en/_images/blockdiag-69b48ddf499e79e437fbdf9f0e767e365f846d7a.png" target="_blank">http://blockdiag.com/en/_images/blockdiag-69b48ddf499e79e437fbdf9f0e767e365f846d7a.png</a><br>
<br>
(see more example<br>
<a href="http://blockdiag.com/en/blockdiag/examples.html" target="_blank">http://blockdiag.com/en/blockdiag/examples.html</a> )<br>
<br>
or you can try online <a href="http://blockdiag.appspot.com/" target="_blank">http://blockdiag.appspot.com/</a><br>
<br>
NetDiag<br>
<a href="http://blockdiag.com/en/nwdiag/" target="_blank">http://blockdiag.com/en/nwdiag/</a><br>
<br>
nwdiag {<br>
network dmz {<br>
address = "210.x.x.x/24"<br>
<br>
web01 [address = "210.x.x.1"];<br>
web02 [address = "210.x.x.2"];<br>
}<br>
network internal {<br>
address = "172.x.x.x/24";<br>
<br>
web01 [address = "172.x.x.1"];<br>
web02 [address = "172.x.x.2"];<br>
db01;<br>
db02;<br>
}<br>
}<br>
<br>
will be<br>
<br>
<a href="http://blockdiag.com/en/_images/nwdiag-472a0e8ead9b236d7d929e645767514615bb2392.png" target="_blank">http://blockdiag.com/en/_images/nwdiag-472a0e8ead9b236d7d929e645767514615bb2392.png</a><br>
<br>
try<br>
<a href="http://blockdiag.appspot.com/nwdiag/" target="_blank">http://blockdiag.appspot.com/nwdiag/</a><br>
<br>
<a href="http://blockdiag.com/en/nwdiag/nwdiag-examples.html" target="_blank">http://blockdiag.com/en/nwdiag/nwdiag-examples.html</a><br>
<br>
We have more diagrams can be generated<br>
<br>
Activity diagram<br>
<a href="http://blockdiag.appspot.com/actdiag/" target="_blank">http://blockdiag.appspot.com/actdiag/</a><br>
<br>
Sequence diagram<br>
<a href="http://blockdiag.appspot.com/seqdiag/" target="_blank">http://blockdiag.appspot.com/seqdiag/</a><br>
<br>
Best<br>
Nachi<br>
<br>
2014-04-16 10:42 GMT-07:00 Kyle Mestery <<a href="mailto:mestery@noironetworks.com">mestery@noironetworks.com</a>>:<br>
> On Wed, Apr 16, 2014 at 12:23 PM, Russell Bryant <<a href="mailto:rbryant@redhat.com">rbryant@redhat.com</a>> wrote:<br>
>> On 04/16/2014 09:51 AM, Russell Bryant wrote:<br>
>>> On 04/16/2014 09:39 AM, Salvatore Orlando wrote:<br>
>>>> if the image you're adding is a diagram, I would think about<br>
>>>> <a href="http://asciiflow.com" target="_blank">asciiflow.com</a> <<a href="http://asciiflow.com" target="_blank">http://asciiflow.com</a>> first!<br>
>>><br>
>>> In all seriousness, I think that's a very nice solution for simple<br>
>>> diagrams. :-)<br>
>>><br>
>>> For other diagrams, I wonder if it makes sense to just upload them<br>
>>> to the wiki and include links to them from the spec using the image directive.<br>
>>><br>
>><br>
>> Another thread got started on this topic for Nova.<br>
>><br>
>> I put up a proposal to require ASCII digrams for nova-specs here:<br>
>><br>
>> <a href="https://review.openstack.org/#/c/88028/" target="_blank">https://review.openstack.org/#/c/88028/</a><br>
>><br>
> Great idea! I've done the same for neutron-specs here:<br>
><br>
> <a href="https://review.openstack.org/88037" target="_blank">https://review.openstack.org/88037</a><br>
><br>
><br>
>> --<br>
>> Russell Bryant<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>
> 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>
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>
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>