You can get the package directly on packages.debian.org, e.g.
https://packages.debian.org/stretch/puppet or
https://packages.debian.org/stretch/facter. Additionally you can browse the
source of the package on http://sources.debian.net/search/facter/
Debian offers a great visibility and transpar
Hi All,
Brand new to puppet and am trying to get a simpler master server set up to
test it out. I've been following the install guide
at http://docs.puppetlabs.com/guides/install_puppet/install_el.html. This
is on CentOS 7 on AWS. Everything goes fine, through the installation of
passenger.
On Friday, May 8, 2015 at 10:42:03 AM UTC-5, James Oden wrote:
>
> I created a custom fact file to generate home_$user entries for all
> users on the system containing their respective home directories:
>
>require 'etc'
>
>while pwEnt = Etc.getpwent do
>name = pwEnt.name
>
On Sunday, May 10, 2015 at 8:03:25 AM UTC-5, Martin Alfke wrote:
>
> Hi,
>
> I am working on some types and providers for opennebula network
> management.
>
> I have one type already finished, which creates the network itself.
> Each network can have multiple address ranges.
>
> My idea so f
That was exactly what was confusing me. I had figured this out
shortly after sending the email...but I'm glad I didn't reply as I got
your structured facts answer which is good information to know.
Thanks...James
On Mon, May 11, 2015 at 10:01 AM, jcbollinger wrote:
>
>
> On Friday, May 8, 2015
Hi John,
many thanks for your explanation.
I will stay with auto require to allow managing resource B without the need for
having the depending A resource declared within puppet too.
Best,
Martin
On 11 May 2015, at 16:17, jcbollinger wrote:
>
>
> On Sunday, May 10, 2015 at 8:03:25 AM UTC-
Hello list.
I'm using open source Puppet 3.7.4 with Puppet Server 1.0.2 and I'm
evaluating how to load balance two or more Puppet Servers, specially about
centralizing the CA. Is the doc
http://docs.puppetlabs.com/guides/scaling_multiple_masters.html up to date
and is it the way to go? If so,
Hey there,
On 10/05/15 10:15 PM, j...@poweriep.com wrote:
> Message from application: Permission denied - /etc/puppet/modules
> (Errno::EACCES)
make sure to also verify permissions on /etc/puppet itself. If the
puppet user can't traverse the directory then the process won't be able
to open up t
Hi Karen,
On Sat, May 9, 2015 at 12:53 AM, Karen Ellrick
wrote:
> Having already used Puppet a bit by way of a pre-packaged ZIP file created
> by the PuPHPet online tool, I decided to try building a simpler VM without
> the tool. I have VirtualBox and Vagrant already installed and happy. What
>
On Mon, May 11, 2015 at 3:22 PM, Rob Reynolds wrote:
> Hi Karen,
>
> On Sat, May 9, 2015 at 12:53 AM, Karen Ellrick
> wrote:
>
>> Having already used Puppet a bit by way of a pre-packaged ZIP file
>> created by the PuPHPet online tool, I decided to try building a simpler VM
>> without the tool.
After successfully launching the CentOS VM and logging in, I got to the #
prompt. But when I type 'puppet resource service' or just the word puppet
I get a command not found. If I type whereis puppet I get puppet:
--
You received this message because you are subscribed to the Google Groups
far4d writes:
> You can get the package directly on packages.debian.org, e.g.
> https://packages.debian.org/stretch/puppet or
> https://packages.debian.org/stretch/facter. Additionally you can browse the
> source of the package on http://sources.debian.net/search/facter/
>
> Debian offers a gr
The canonical way to do this is like this:
http://serverfault.com/questions/350230/how-can-i-have-puppet-only-set-password-when-creating-a-user
There's an open feature request
here: https://tickets.puppetlabs.com/browse/PUP-1331
Feel free to add yourself as a watcher and add a comment describin
On Monday, May 11, 2015 at 11:24:02 AM UTC-5, Gabriel Filion wrote:
>
> Hey there,
>
> On 10/05/15 10:15 PM, j...@poweriep.com wrote:
> > Message from application: Permission denied - /etc/puppet/modules
> > (Errno::EACCES)
>
> make sure to also verify permissions on /etc/puppet itself. If t
I do have one update to this. The issue seems to be the modulepath, and
what comes after the ':'
modulepath = $confdir/environments/dev/modules:
$confdir/environments/dev/site/modules
Puppet is not finding catalogs/modules after the ':'
err: Could not retrieve catalog from remote server: Error
On 11/05/15 08:51 PM, Joe Koenig wrote:
> On Monday, May 11, 2015 at 11:24:02 AM UTC-5, Gabriel Filion wrote:
> On 10/05/15 10:15 PM, j...@poweriep.com wrote:
> > Message from application: Permission denied - /etc/puppet/modules
> > (Errno::EACCES)
> # su -s /bin/bash - puppet
>
Still wrestling with this. Puppet is now seeing 'part' of the module paths
but not all of them, one thing I had to change was using an absolute path
and not '$confdir' and it's not using the correct site.pp file
"non-prod_site.pp"
[ ~ ]# puppet config print --environment test |grep env
environ
And finally when I add back to puppet.conf my environment, everything is
found correctly:
[test]
manifest = $confdir/manifests/non-prod_site.pp
modulepath =
$confdir/environments/test/modules:$confdir/environments/test/site/modules
[ ~ ]# puppet config print --environment test |grep
18 matches
Mail list logo
