Yes, I would be interested in this as well. We posited that Puppet and facter could make a nice foundation for a CMDB, but you need more data. It wouldn't be as feature complete as, say BMC's Atrium product, but in most cases you don't need that... But what you do need is the information kept up to date. We use Remedy today to log rack, row, shelf in our DC's for when resources are installed... BUt we have found that it is RAPIDLY out of date as things move, new racks are added, etc.
While I don't agree with all of it as being necessary check out the ITIL v3 CMDB definition for a pretty complete definition. On Sep 22, 11:35 pm, "Ohad Levy" <[EMAIL PROTECTED]> wrote: > Hi, > > I'm interested, I've already done some basic work on the puppet side. > In our setup we decided not to use storeconfig (due to technical limitations > of having too many puppet masters in different locations), therefor, we have > re implemented many of facts importing and collecting. > > I would assume it should not be a big deal to push the data forward to > remedy CMDB. > > Cheers, > Ohad > > On Tue, Sep 23, 2008 at 2:25 AM, Digant C Kasundra <[EMAIL PROTECTED]>wrote: > > > > > Hello Puppet users, > > > I was curious if anyone else works at an institution that uses Remedy, > > particularly as a CMDB infrastructure. We're planning to do that and so > > I've been tasked with writing integration tools so that Puppet can feed data > > of interest up into that system. If anyone is interested in helping > > (whether you use Remedy or not), I'd be interested to build a team around > > this effort. > > > Here is the breakdown: > > > The CMDB wants to know about systems and system facts. This is easy with > > facter and stored configs and stored facts. We'll just be writing a > > collector to query these things out of the puppetmaster storage and feed > > that into the CMDB. The CMDB also wants to know about meta information like > > who the admin in charge is, who the client is, what the purpose and > > description of the services are. These meta facts will be provided as > > either (a) meta resources created as native types in puppet or (b) through > > an external node tool. > > > That's the basic jist of it. I'd love to hear from interested parties or > > parties doing something similar. > > > -- > > Digant C Kasundra <[EMAIL PROTECTED]> > > Technical Lead, ITS Unix Systems and Applications, Stanford University --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
