Re: [Openstack-operators] :document an OpenStack production environment

Hi Dani, I’m currently working on development of a product that supports complex hardware solution design, resulting in ‘active diagrams’ having detailed knowledge of configured riser cards, adapters, processor trays, drive bays, physical cabling etc. It also then assists management of or

Re: [Openstack-operators] :document an OpenStack production environment

If anyone can share more info will be much appreciated. Thanks, Dani On Mon, Jan 26, 2015 at 8:55 PM, Daniel Comnea wrote: > Excellent input, please keep it going. > > Maybe someone from HP will shed more light on their cmdb? > > > Dani > > On Mon, Jan 26, 2015 at 4:28 PM, j wrote: > >> I use

Re: [Openstack-operators] :document an OpenStack production environment

Excellent input, please keep it going. Maybe someone from HP will shed more light on their cmdb? Dani On Mon, Jan 26, 2015 at 4:28 PM, j wrote: > I use LibreOffice Draw for architecture diagrams. VRT Network Equipment >

Re: [Openstack-operators] :document an OpenStack production environment

I use LibreOffice Draw for architecture diagrams. VRT Network Equipment [2] pretty much blows everything out of the water. For text documentation that I manually create (chef for example does this automatically) I'll put in plaintext files per environment that includes basic stuff such as host

Re: [Openstack-operators] :document an OpenStack production environment

i wish hp would open source their cmdb code... that stuff was pretty neat. On Mon, Jan 26, 2015 at 10:03 AM, George Shuklin wrote: > In my earlier days I had tried many formal schemes, but it always cause > problems. > > For now I settle to following scheme: > > machine-used database (dns, chef

Re: [Openstack-operators] :document an OpenStack production environment

In my earlier days I had tried many formal schemes, but it always cause problems. For now I settle to following scheme: machine-used database (dns, chef, etc) for explit details like mac addresses, hardware, rack location, network communication. That database should be constantly used, not 'w

Re: [Openstack-operators] :document an OpenStack production environment

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 but i think I was probably considered a masochist on this front. at the very l

Re: [Openstack-operators] :document an OpenStack production environment

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. For the flowcharts we mostly use markers and whiteboard, sometime I sketch stuff in dia [1] or with wacom tablet in mypaint. [1] http://sourceforge.net/pro