It also might be a cheap way of doing it, but if your looking at stuff at the node level anyway you can leverage LDAP. All objects in LDAP in puppet 3.x are treated as top scope variables.
On Fri, Jun 20, 2014 at 6:58 PM, Matthew Hyclak <hyc...@gmail.com> wrote: > I was thinking about this not too long ago myself. It seems a little silly, > but creating a custom fact (let's stick with room number) that gets pushed > out by a paramaterized class in puppet does what you're looking for I think. > > The ENC defines the room number, but by having that show up in the custom > fact, you see the results of that in the puppet reports (and therefore in > your dashboard) in a convenient manner. You're also only managing that > definition in one place. > > So not-quite server-side, but close? > > Matt > > > On Fri, Jun 20, 2014 at 5:34 PM, Fine, Thomas <tf...@cfa.harvard.edu> wrote: >> >> Hi, >> >> As I get more into this and look at what puppet dashboard (and whatever I >> replace it with, sigh) can do and what we've been doing, it's great for >> simple inventory tracking. Except that if it's good at that I might as well >> get all the information in one place, like the room location, the user the >> system is assigned to, what's it's local inventory control number, and are >> there any important notes (like from human beings) on the current status of >> the system. >> >> Is there any system that provides for this functionality? Dashboard? >> Foreman? Anything else? I know about custom facts, and external facts, but >> those are all for client-side facts. I don't want to have to put a file on >> each machine that says what it's room number is, that'd be silly. >> >> I could make an external fact that consults our existing database to get >> the fact into the system, but my whole hope here is to eliminate our >> existing legacy inventory system in favor of having everything in one >> database. >> >> Also, I realize it's probably a bigger issue than simply adding fields, as >> it's sort of a different philosophy. For example renaming a machine >> currently creates a new node in the database (and leaves an old one to be >> cleaned up some day), but with this metadata attached we'd want to somehow >> connect the hardware information so that the metadata that's not changing >> follows automatically after the name change. >> >> So is there anything that provides this? I've searched and have come up >> empty but maybe I just don't know the magic buzzword I should be googling? >> >> Thanks, >> >> tom >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to puppet-users+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/puppet-users/CANVEBdh7Qn7Xvz425DYHSY%2Bm3DLp-p%2BxSxZaQOVVoMU3s52mNA%40mail.gmail.com. >> For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/CAO7w0s7hTKGMV2DRg8sDKx6HeYrPHQY7sgFAXRntTCThBh1i1g%40mail.gmail.com. > > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAMM%2BeSXBxof4RwcnATHh1e0pnK_s7k136Yg5e3%3D6M8Ak%3DEvUYg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
