<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 14, 2014 at 6:24 AM, darren chan <span dir="ltr"><<a href="mailto:dazzachan@yahoo.com.au" target="_blank">dazzachan@yahoo.com.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="color:#000;background-color:#fff;font-family:arial,helvetica,sans-serif;font-size:10px"><div><div><div style="color:rgb(0,0,0);background-color:rgb(255,255,255);font-family:arial,helvetica,sans-serif;font-size:10px"><div><div><div style="color:rgb(0,0,0);background-color:rgb(255,255,255);font-family:arial,helvetica,sans-serif;font-size:10px"><div>
</div><div>In [2], I prefer the Compute node, and in [3], I prefer the Network node color scheme. The font color for the node labels could be lighter so it is easier to read.</div><div><br clear="none"></div><div dir="ltr">This is a good step towards having some consistency with diagrams in the upstream docs. When this is finalized, can we add this information to the documentation conventions wiki, and include other conventions such as file formats, graphics resolution and size, and recommended tools? It would also be helpful to have some guidelines about creating different diagrams, such as network architecture diagrams and process flow diagrams.</div><div dir="ltr"><br clear="none"></div><div dir="ltr"><br></div></div></div></div></div></div></div></div></div></blockquote><div><br></div><div>+1 to all of this, thanks Matt for working on it.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="color:#000;background-color:#fff;font-family:arial,helvetica,sans-serif;font-size:10px"><div><div><div style="color:rgb(0,0,0);background-color:rgb(255,255,255);font-family:arial,helvetica,sans-serif;font-size:10px"><div><div><div style="color:rgb(0,0,0);background-color:rgb(255,255,255);font-family:arial,helvetica,sans-serif;font-size:10px"><div dir="ltr"></div><div dir="ltr">Regards,</div><div dir="ltr"><span style="font-size:10px"><br></span></div><div dir="ltr"><span style="font-size:10px">Darren </span></div><div><div class="h5"> <div><br clear="none"><br clear="none"></div><div style="display:block"> <div style="font-family:arial,helvetica,sans-serif;font-size:10px"> <div style="font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif;font-size:12px"> <div><br><br></div><div><div dir="ltr"> <font face="Arial"> On Friday, 14 November 2014, 12:50, Nick Chase <<a href="mailto:nchase@mirantis.com" target="_blank">nchase@mirantis.com</a>> wrote:<br clear="none"> </font> </div> <br clear="none"><br clear="none"> <div><div><div>
On the color, I definitely prefer the light version; much easier to
read. Any of the colors actually work, I think.<br clear="none">
<br clear="none">
On the monotone, I actually LIKE the object storage nodes the best,
though that's not saying much; I don't like the monotone much at
all, actually, particularly compared with the color. At small font
sizes, I don't tink there's enough contrast on the baqckground
colors. The content colors are good, though. That's why the Object
Storage nodes work, I think. (Still prefer the color/light version,
though.)<br clear="none">
<br clear="none">
Nice job finding this.<br clear="none">
<br clear="none">
---- Nick<br clear="none">
<br clear="none">
<br clear="none">
<div><div>On 11/13/2014 8:28 PM, Matt Kassawara
wrote:<br clear="none">
</div>
<blockquote type="cite">Needless to say, our existing diagram color schemes
vary by document and sometimes look rather hideous. For example, I
used the red-green-blue theme in the installation guide to improve
contrast among the networks, but it lacks the civility you would
find in other professional documentation. Similar to networking,
colors are hard. For example, themes that implement many shades of
one or two colors look professional but limit the ability to
contrast important items. On the other hand, themes that implement
many diverse colors offer many ways to contrast important items,
but look harsh. I haven't found a theme that provides a decent
balance until Robb Romans (a coworker at Rackspace) pointed out
the Solarized theme [1] today. Although somewhat optimized for
text, this theme provides several decent dark/light combinations
for diagrams requiring less contrast and a series of diverse yet
soft colors for diagrams requiring more contrast. After messing
around a bit, I came up with a few potential color variants using
this theme. Please review the dark/light example for simple
diagrams [2] and the diverse color example for complex/contrasty
diagrams [3] and provide comments. For the first diagram, indicate
which of the controller node, network node, compute node, and
block storage node objects look the best (ignore the object
storage nodes). For the second diagram, indicate which of the
nodes (dark/light) and network colors look best. You can also
reject this theme completely. However, if you do, please provide
one or more suitable alternatives. I would like to upload a series
of revitalized diagrams to the installation guide as soon as
possible.
<div><br clear="none">
</div>
<div>Matt</div>
<div><br clear="none">
</div>
<div>[1] <a rel="nofollow" shape="rect" href="http://ethanschoonover.com/solarized" target="_blank">http://ethanschoonover.com/solarized</a></div>
<div>[2] <a rel="nofollow" shape="rect" href="http://23.253.231.218/rpc-diagrams/os-examplearchneutron-hw.png" target="_blank">http://23.253.231.218/rpc-diagrams/os-examplearchneutron-hw.png</a></div>
<div>[3] <a rel="nofollow" shape="rect" href="http://23.253.231.218/rpc-diagrams/os-examplearchneutron-networks.png" target="_blank">http://23.253.231.218/rpc-diagrams/os-examplearchneutron-networks.png</a></div>
<br clear="none">
<fieldset></fieldset>
<br clear="none">
<pre>_______________________________________________
OpenStack-docs mailing list
<a rel="nofollow" shape="rect" href="mailto:OpenStack-docs@lists.openstack.org" target="_blank">OpenStack-docs@lists.openstack.org</a>
<a rel="nofollow" shape="rect" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a>
</pre>
</blockquote>
<br clear="none">
</div></div></div><br clear="none"><div>_______________________________________________<br clear="none">OpenStack-docs mailing list<br clear="none"><a rel="nofollow" shape="rect" href="mailto:OpenStack-docs@lists.openstack.org" target="_blank">OpenStack-docs@lists.openstack.org</a><br clear="none"><a rel="nofollow" shape="rect" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br clear="none"></div><br clear="none"><br clear="none"></div></div> </div> </div> </div> </div></div></div></div></div></div></div></div></div></div><br>_______________________________________________<br>
OpenStack-docs mailing list<br>
<a href="mailto:OpenStack-docs@lists.openstack.org">OpenStack-docs@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
<br></blockquote></div><br></div></div>