On 23 sep, 14:45, Ohad Levy <ohadl...@gmail.com> wrote:
>
> why not ? :)
>
Let's say that we're doing everything from scratch: new distro, new
apps, new deployment system and at last: puppet+svn.
My colleague and I we've spent almost a year migrating configs to
puppet, creating RPM packages, etc ... so we're pretty good at it.
But there are colleagues who've been fiddling with puppet for only
over a month, and haven't played yet with our "core" classes. Of
course we should give them some "advanced" training but again, there's
a lot of stuff we need to fix first... (like the fact that our current
telco will shutdown our uplink in a bit more than a week while we
still have a few services that haven't been migrated yet to the new
infrastructure ...).
Right now we prefer applying stuff "by hand" (dsh + puppetd) on
servers that are temporarily put offline.
> one option while using reports, instead of parsing them yourself, you can
> use Foreman, to collect and store the data in a database, it should be
> failry simple to display the content that you want once the reports are
> imported.
I'll take a look at "The Foreman" which looks interesting. But I'd
rather not add an extra layer / extra database.
Thanks !
Calimero
--~--~---------~--~----~------------~-------~--~----~
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
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
