[racktables-users] Re: Betr.: RackTables + Nagios + Bacula
- From: "Joep Ingen, van" <j.vaningen@xxxxxxxxxx>
- To: <racktables-users@xxxxxxxxxxxxx>
- Date: Fri, 06 Feb 2009 16:11:41 +0100
Your ideas are very similar to what I'm planning to do, but with one difference:
We are using HPSD 4.5 w/ SP26.
I don't know if there is a big difference between 4.5 and 5.0 CMDB-wise.
If not, could you please forward the scripts when they are ready to publish?
I'm looking forward to it.
Regards,
Joep van Ingen
>>>
Van: Erik Weber <twiztar@xxxxxxxxx>
Aan: <racktables-users@xxxxxxxxxxxxx>
Datum 6-2-2009 15:28
Onderwerp: [racktables-users] Re: Betr.: RackTables + Nagios + Bacula
Joep Ingen, van wrote:
> Hi Frank,
>
> Thanks for sharing these scripts with us.
> At my company we also use Nagios and HP OpenView ServiceDesk for our
> main ITIL processes (incident/problem/change/project mangement, but als
> our CMDB). In adition of hooking up Nagios I'm thinkering about a link
> with our CMDB.
> With tags I can assosiate the object with a location code,also
> synchronising the serial numbers, and other usefull info can ben done.
> Much work to do, but I believe it is feasible.
>
> I'll give an update when there is more than just the idea :-)
We have done some integrations from our HP SD 5 to racktables, but it's
not ready to be published. However, if anyone starts a project for it
we'd be happy to donate some code / queries / ideas.
What we have in place is this:
* Mapping racks from ServiceDesk to RackTables based on Configuration
Item name.
* Population and changes to servers in SD is reflected to RackTables
with a scheduled task.
* We've also modified RackTables to allow a separate 'view' for planned
space allocations (ref image:
http://img187.imageshack.us/my.php?image=racktablescz5.png ). Red space
is allocated based on status in the Configuration Item but not yet
physically placed in the rack. We currently have 68 racks with several
internal departments allocating space, so it was crucial for our
planning to see what was already planned to use. We could of course have
used the normal color but this makes it easy to see what's already there
and what's coming.
Probably some more stuff that I can't remember right now.
--
Erik
###################################################################
* * * D I S C L A I M E R * * *
###################################################################
De informatie in dit e-mailbericht is vertrouwelijk en uitsluitend bestemd voor
de geadresseerde. Wanneer u dit bericht per abuis ontvangt, gelieve
onmiddellijk contact op te nemen met de afzender per kerende e-mail. Wij
verzoeken u dit e-mailbericht te vernietigen en de inhoud ervan aan niemand
openbaar te maken. Afzender aanvaardt geen enkele aansprakelijkheid voor
onjuiste, onvolledige dan wel ontijdige overbrenging van de inhoud van een
verzonden e-mailbericht, noch voor door haar daarbij overgebrachte virussen.
The information contained in this e-mail is confidential and may be privileged.
It may be read, copied and used only by the intended recipient. If you have
received it in error, please contact the sender immediately by return e-mail.
Please delete this e-mail and do not disclose its contents to any person.
Sender does not accept any liability for any errors, omissions, delays of
receipt or viruses in the contents of this message which arise as a result of
e-mail transmission.
Other related posts: