<div dir="ltr">i wish hp would open source their cmdb code... that stuff was pretty neat.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 26, 2015 at 10:03 AM, George Shuklin <span dir="ltr"><<a href="mailto:george.shuklin@gmail.com" target="_blank">george.shuklin@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 bgcolor="#FFFFFF" text="#000000">
<div>In my earlier days I had tried many
formal schemes, but it always cause problems.<br>
<br>
For now I settle to following scheme:<br>
<br>
machine-used database (dns, chef, etc) for explit details like mac
addresses, hardware, rack location, network communication. That
database should be constantly used, not 'write only', otherwise
everyone will starts to forget to update, and suddenly it will
loose it authority over 'I wrote you about it in hipchat and than
send you update via sms, and final version is in your other skype
account'. Usually it some kind of 'work', or 'control panel', or
chef data bags.<br>
<br>
All topological schemes should be hand written. Whiteboards is
just perfect for that. Why? Because all tools, except
pen/pencil/marker are restrain you, forcing to use terminology and
linking type of that tool. Even inkscape is restricting, because
you can not just 'undersubscribe' link, or draw funny spiral
("here it goes somewhere...").<br>
<br>
And text in corporate wiki in free form. Yes, updates will change
everything, but even after updates original picture and text will
be precious, because they will say history and will help to debug
strange issues with historical reasons. Corporate blogs are
perfect place for updates and ideas for future update.<br>
<br>
Yes, it is a mess, but it is better than 'not enough information
because of the format restrictions'.<div><div class="h5"><br>
<br>
<br>
On 01/26/2015 03:45 PM, matt wrote:<br>
</div></div></div><div><div class="h5">
<blockquote type="cite">
<div dir="ltr">
<div>
<div>I really liked using sphinx for documentation back in the
day, it has the benefit of being community compatible. I
also enjoyed graphviz integration in sphinx for diagrams...
and then there was templating gnuplots....<br>
<br>
</div>
but i think I was probably considered a masochist on this
front. at the very least management types did not like that
they couldn't really edit our documentation.<br>
<br>
</div>
-matt<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Jan 26, 2015 at 5:10 AM, George
Shuklin <span dir="ltr"><<a href="mailto:george.shuklin@gmail.com" target="_blank">george.shuklin@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 bgcolor="#FFFFFF" text="#000000">
<div>We using chef to manage hosts. Data bags contains all
data of all hosts. We keep hardware configuration and
DC-wide-name in databags too.<br>
<br>
For the flowcharts we mostly use markers and whiteboard,
sometime I sketch stuff in dia [1] or with wacom tablet
in mypaint.<br>
<br>
[1] <a href="http://sourceforge.net/projects/dia-installer/" target="_blank">http://sourceforge.net/projects/dia-installer/</a>
<div>
<div><br>
<br>
<br>
On 01/25/2015 04:15 PM, Daniel Comnea wrote:<br>
</div>
</div>
</div>
<blockquote type="cite">
<div>
<div>
<div dir="ltr">
<div>
<div>
<div>Hi all,<br>
<br>
</div>
Can anyone who runs Openstack in a production
environment/ data center share how you
document the whole infrastructure, what tools
are used for drawing diagrams(i guess you need
some pictures otherwise is hard to understand
it :)), maybe even an inventory etc?<br>
<br>
<br>
<br>
</div>
Thanks,<br>
Dani<br>
<br>
<br>
<br>
</div>
P.S in the past - 10+ - i used to have maintain a
red book but i suspect situation is different in
2015<br>
</div>
<br>
<fieldset></fieldset>
<br>
</div>
</div>
<pre>_______________________________________________
OpenStack-operators mailing list
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a>
</pre>
</blockquote>
<br>
</div>
<br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br></div>