On 25/04/17 18:34, Jason McMahan wrote:
> Has anyone else used the foreman puppet module to create a new formean host?
> We used the module, created the host, and manually added it to our f5
> but odd things show up.
>
> If i go to https://foreman.com (load balancer) go to infrastructure >
> smart
I just cannot believe they would do this without any warning for the end
user community, whether open-source or commercial customers. Look at other
open-source projects like Fedora and Ubuntu for an example; they would send
warnings at least two weeks in advance before turning off a service tha
What I seem to be missing is do you have subsequent classes called
sudo::user_alias and sudo::user_priv? I get the Hiera yaml file setup, not
how to use them selectively to have them added to the sudoers file.
Thanks!
--
You received this message because you are subscribed to the Google Group
I guess I should have running a Foreman / Puppet setup, so I am trying to
keep from having to go creating .yaml files as well as editing things
like site.pp and other files.
The object I am trying to accomplish is on the KISS principal.
So for example my sudoers.erb has an array block for *sud
On Wed, Apr 26, 2017 at 10:45 AM James Perry wrote:
> Since all of our Puppet code is in a source code repo and requires a
> change control to push to PROD, I don;t want to have to manually create a
> per host entry, either via the* case* statement or a *node.yaml* file as
> that requires a full
Thanks. I will look at that as we move forward.
To your NFS issue, that was one of the design decisions we made. I have 3
GIT repos (Dev, Stage, Prod). The Stage and Prod are on the same server. On
dev I have every OS we support connected to it to run through all code
before we push to Stage.
Thank you for the quick response Dominic,
When i look under settings
foreman1 = (the original working)
SSL CA file /etc/puppetlabs/puppet/ssl/certs/ca.pemSSL CA file
that Foreman will use to communicate with its proxies
SSL certificate /etc/puppetlabs/puppet/ssl/certs/foreman1.com.pe
I'm sorry we broke people's rsync-based repository mirroring. I should have
communicated this change well in advance. To get you all mirroring our
repositories again, I've configured rsync.puppet.com. You can sync from it
using a command like:
rsync -av --copy-links --del rsync://rsync.puppet.c
Does it make sense to use the puppetlabs-inifile module when trying to
modify the /etc/sudoers file?
>From my observations, the /etc/sudoers file isn't exactly laid out in an
ini-stylized configuration; like the /etc/smb.conf is.
Comments welcomed.
--
Warron French
--
Yo
