have them look at it in detail. Building a new server total time takes
> under 5 minutes for me, including registration to Satellite.
>
> * Kickstart - host renaming from localhost is easily fixed by writing a
> better kickstart, e.g. using
> https://github.com/stbenjam/junk-drawer/blob
ent and working towards
> implementing Puppet. How do you audit and report your current package
> levels on your servers now that you've moved to this new solution?
>
> Thanks!
>
> On Monday, June 10, 2013 9:04:17 AM UTC-4, Keiran Sweet wrote:
>>
>> Hi Every
Hi Everyone,
I've written a paper that captures the approach that we took when moving
from Redhat Satellite for configuration and software management to Puppet
and Foreman (alongside some other assorted technologies).
The paper contains a number of lessons learnt in the Ruby, Puppet, Foreman
an
Hi There,
Puppetlabs also provide some pre-configured virtual machines that can help
you rapidly learn the structure of the product.
You can check them out here:
http://info.puppetlabs.com/download-learning-puppet-VM.html
K
On Tuesday, May 28, 2013 3:55:07 PM UTC+1, Ripunjay Godhani wrote:
>
>
Regarding Masterless Puppet, Sam Bashton spoke about his approach to
Masterless Puppet at Puppetconf London a few months ago.
You can see his slides here:
http://www.slideshare.net/PuppetLabs/bashton-masterless-puppet
K
On Tuesday, May 14, 2013 4:28:04 AM UTC+1, hmf8...@gmail.com wrote:
>
> No
Hi There,
You can, however once a class is defined you must then apply it to the node
using 'include'
Example:
[ Keiran ~]$ cat /tmp/example.pp
class class1 {
exec { exec1 :
command => "/bin/touch /tmp/${title}",
}
}
class class2 {
exec { exec2
HI There,
I'm not sure if Luke's splunk work has hit the forge, but you may find some
useful splunk/puppet examples here: http://verypowerful.info/
I know he did talk at the Sydney puppet camp last year about this topic,
however i've not been able to locate his slides, his contact details are on
Hi,
Another vote from me for packaging this software, Puppet likes packages and
deals with them well.
John mentioned FPM, If you haven't checked it out, I can't recommend it
enough.
I manage quite a few packages internally in my role, and FPM has shaved
huge amounts of time off generating them.
Hi,
Although I've never used it, this does sound like a task for the auditing
functionality that was added into Puppet 2.6.
Some information about it can be found here:
http://puppetlabs.com/blog/all-about-auditing-with-puppet/
You may also find the Puppet enterprise documentation on audit and
Hi There,
A couple of suggestions if you are starting to learn Puppet.
* Build an environment where you are using the same major release of the
software, ie All 3.x or 2.7 master/clients
Although it is supported to have masters running later versions,
consistency is key when you are learning th
Hi There,
Luke beat me to the punch, but I'd already typed this up so I
figured I'd send it anyway.
You are going about some of these tasks the wrong way a little, and you
should probably have a read of the following:
* Learning Puppet - http://docs.puppetlabs.com/learning/index.html
* Pro Puppe
> [root@testrhel home]#
>
> Sorry but you might receive a similar message twice. Forgot to reply to
> this post.
>
> Thanks,
> -J
>
> On Thursday, December 20, 2012 3:37:30 PM UTC-8, Keiran Sweet wrote:
>>
>> Hi There,
>> The user provider allows you
Hi There,
The user provider allows you to manage the value of the password hash in
the shadow file.
You can see all the options available for this provider via 'puppet
describe user'.
An example would be something like:
user { username:
ensure => present,
password =>
Hi There,
This is the type of task that is best serviced using the packaging
framework of your operating system (ie, RPM, Deb, etc).
In this case, I'd roll the software into RPMs and have them installed via
the package {} type on all your nodes from a central YUM repo, followed by
the deploymen
Hi There,
Rather than building out files dynamically, have you considered possibly
deploying snippets of sudoers configuration out to nodes using the
/etc/sudoers.d/ framework that is available on many operating systems ?
This can be easily handled using the File type and applied to nodes as
re
Hi There,
Thanks for the additional information it actually helps me understand what
you are trying to achieve a bit better.
As per the types documentation, this line is quite important to understand:
"Classes are good for modelling singleton aspects of a system, but to model
repeatable chunks
Hi,
I have found when working with user accounts it is very beneficial to
create a defined type that allows you to wrap alot of functionality into
one definition, thus reducing manual work and being more explicit with your
requirements for user data and account configuration when they are define
Hi There,
I do a similar thing with my environment, I apply a class called "applysoe"
to all nodes that is responsible for applying my modules and classes to
nodes in a specific order as the ENC i use didn't initially support it.
Have you looked at the foreman ?
The imminent release of 1.1 suppo
Hi There,
We take this approach as well with our platform to ensure that puppet
upgrades don't affect any applications that may be using the OS version of
Ruby.
Disclaimer:
I don't actually love our approach to packaging Ruby and am aware of its
flaws, however it has proved to be OK for the tim
Hi There,
Looking at your module approach, I think you are heading for quite a bit of
pain, I've found that packaging tools such as RPM are best for this kind of
task.
In my environment which is all RHEL based I (roughly) do the following:
- I have a number of YUM repositories defined and presen
ired, and I'll happily make
> them.
>
>
> W
>
> On Oct 31, 2012, at 1:26 PM, Keiran Sweet >
>
> wrote:
>
> > Hi Everyone,
> > I'm looking for a way to identify (if possible) the ESX/vSphere version
> that a particular VMWare guest serve
Hi Everyone,
I'm looking for a way to identify (if possible) the ESX/vSphere version
that a particular VMWare guest server is running on without the use of
vmware tools related commands, such as vmware-checkvm, which does seem to
do the trick from what I can gather.
[root@server ~]# vmware-chec
Hi There,
I manage a relatively large RHEL environment, we handle provisioning as
follows:
- PXE + Kickstart to bootstrap and install the base OS + Puppet client onto
the platform, be it VMWare or bare metal
- Kickstart post scripts put a basic puppet configuration file in place on
the host, an
Another option worth mentioning, and this may not be suitable for your
environment, is to allow host overrides of configuration files within your
module using file precedence like the below.
file { '/etc/security/limits.conf' :
ensure => file,
mode=> 755,
owner
I've had quite a bit of success with Puppet 2.7 on 32-bit RHEL
4, specifically:
- Puppet 2.7.3
- Facter 1.6.2
- Ruby Enterprise 1.8.7
- Older EPEL packages for Augeas, and other dependencies , active mirrors
with signed packages are still floating about.
As ruby enterprise is now discontinued, i
25 matches
Mail list logo
