If you use openstack or vmware you could try foreman for deployment
and puppet for configuration.
On Tue, Mar 18, 2014 at 2:09 AM, plane123 wrote:
> I need to deploy some linux servers on a private cloud. I see only aws and
> other public cloud deployments in the puppet doc.
> How can I deploy s
Hi,
I am trying to use puppet facts to push the latest facts to my puppetmaster
after a puppet run but the command doesn't seem to work.
#bash: puppet facts upload
Error: execution expired
Error: Try 'puppet help facts upload' for usage
It appears like the command is timing out, but I don't kno
I need to deploy some linux servers on a private cloud. I see only aws and
other public cloud deployments in the puppet doc.
How can I deploy servers in my environment.
thanks
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from
Ensure that the the user running the puppetmaster service can read and
execute the script and can write to the debug file.
`sudo -u puppet /usr/local/bin/autosign.sh`
Instead of using "echo $@" you may want to try using 'logger', which should
be easier to debug.
logger -f /var/tmp/debugme "$@"
>
> Ok,
>
> I figured this out. I probably worded my issue badly but what i was
> looking for is the following:
>
> #this sets a variable at the entry[#] level
> defvar syslog /files/etc/syslog.conf/*[ ./action/file =
> "/var/log/messages"]
>
> #these two add in the new selector entries.
> se
Ok,
I figured this out. I probably worded my issue badly but what i was
looking for is the following:
#this sets a variable at the entry[#] level
defvar syslog /files/etc/syslog.conf/*[ ./action/file = "/var/log/messages"]
#these two add in the new selector entries.
set $syslog/selector[last
Forget it, it was late, i get confused by the title of the package, got it
now :)
Le lundi 17 mars 2014 22:21:00 UTC+1, Julien Deloubes a écrit :
>
> Hello there,
> i recently bought the new Pro Puppet 2nd edition.
> There is something i don't understand, it's about the syntax of top scope
> roo
On Monday, March 17, 2014 1:26:03 PM UTC-5, st...@wtfast.com wrote:
>
> Hi,
> I've been having issues with certificates being revoked without any human
> intervention or oversight; one day a node will try to do an update and it
> can't because its certificate is revoked.
>
> There is definitely
I also increased bgwriter_lru_maxpages to 500 from the default 100.
--
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
Hello there,
i recently bought the new Pro Puppet 2nd edition.
There is something i don't understand, it's about the syntax of top scope
rooted variable, here is an example (page 38 of the book):
class ssh_example::params{
case $::osfamily {
'Debian': { $sshd_package = 'ssh'}
'RedHat':
Thanks for your review of the book John, good job!
Le dimanche 16 mars 2014 05:07:02 UTC+1, Jon Forrest a écrit :
>
> Here are the issues I found in Chapters 10.
>
> Jon Forrest
>
> M = mistake - all readers should be aware of this
> U = unclear - chances are readers will wonder about this
> T
Thank You! :)
--
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
I deployed the open source puppet-dashboard 2.0.0 this past weekend for our
production environment. I did a fair amount of testing in the lab to
ensure I had the deployment down, and I deployed as a passenger service
knowing that we have a large environment and that webrick wasn't likely to
cu
Hi,
I'm trying to have Policy-Based Autosigning working with puppet 3.4.3;
but my script is never called
# /etc/puppet/puppet.conf
[master]
autosign = /usr/local/bin/autosign.sh
# ls -l /usr/local/bin/autosign.sh
puppet.puppet rwxr-xr-x /usr/local/bin/autosign.sh
# cat /usr/local/bin/autosig
Turns out to be a denial of service on a machine in the same subnet.
Machine in question has been sequestered.
All of my puppet clients are hung. Fortunately there are only a few dozen
as I'm having to touch each one, stop the puppet service, kill the hung
process and rerun manually.
On Mond
I should have also mentioned that puppet-dashboard is not available at all
when using the main Debian repositories. As of right now I can't think of
a way to get puppet-dasboard running on Debian jessie at all without
bypassing the package managers.
Geoff.
On Monday, March 17, 2014 10:12:38
Hi,
I've been having issues with certificates being revoked without any human
intervention or oversight; one day a node will try to do an update and it
can't because its certificate is revoked.
There is definitely no one issuing 'puppet cert clean nodename' on the
commandline.
puppet --version
On Saturday, March 15, 2014 12:26:57 PM UTC-7, Stig Sandbeck Mathisen wrote:
>
> Ryan McKern > writes:
>
> > * Create a `$confdir/environments` directory on your puppet master.
>
> Does it have to be $confdir/environments, or is it configurable?
>
Hi Stig,
No, you can set 'environmentpath' i
On Mon, Mar 17, 2014 at 9:08 AM, Andy Spiegl wrote:
> > What is the user that the service is running under?
> Good questions. Aren't all services running as administrator?
>
Not necessarily. It all depends on whether you took the default SYSTEM or
set your own credentials on install or afterwar
Hello =)
I would like to either replace "enabled=True" to "enabled=False" in a bunch
of files or rename those files to end with "_false".
Right now I replace content is files with e.g.
replace { 'dummy5':
file => '/etc/xdg/user-dirs.conf',
pattern => "enabled=True",
replacement =>
http://yum.puppetlabs.com/el/6Server/products/SRPMS/
On Mon, Mar 17, 2014 at 10:43 AM, Konstantin Boyanov wrote:
> Hello List,
>
> A simple question - where can I find a src.rpm Package for the latest
> stable Puppet release? googling did not get me anythign so I guess this is
> some "classifie
The best way I've found to handle folders that contain items puppet later needs
to act on is to use fpm to turn them into an rpm/deb and add them to a repo.
This way you're not using puppet as a file server -- something you should avoid
wherever possible. Puppet can use a package resource to ins
On Monday, March 17, 2014 12:59:07 PM UTC+1, nhadie ramos wrote:
>
>
> HI All,
>
> Im trying vagrant and puppet, i would like to be able to launch an VM on
> virtualbox then call puppet for installing packages and configuration.
> I would be using this for all developers and loaded on their loca
I have several machines that occasionally go "unresponsive" in Dashboard.
Not all computers do, but all machines are receiving the same manifests to
control the launchd plist. What's going on.
All computers are running puppet 3.4.3.
*Here is my Launchd plist (com.puppetlabs.puppet.plist):*
Over the weekend there were some intermittent outages at our data center.
The puppet server would let clients connect but they would eventually time
out.
Unf this timeout wasn't handled gracefully and the clients would hang.
Doing a 'ps -ax | grep puppet' would show the service and the 'puppet
On 17/03/14 12:59, nhadie ramos wrote:
HI All,
Im trying vagrant and puppet, i would like to be able to launch an VM
on virtualbox then call puppet for installing packages and configuration.
I would be using this for all developers and loaded on their local
machine's Virtualbox.
so on vagra
Hello List,
A simple question - where can I find a src.rpm Package for the latest
stable Puppet release? googling did not get me anythign so I guess this is
some "classified" info :)
And if there is no SRC Package, how do I build my own Puppet RPM from the
puppet-3.4.3.tar.gz Archive?
Thanks
Hi all,
I am new to Puppet and I'm trying to accomplish a fairly simple task. I
need to deploy a folder to the server and, once it's copied, I need to run
a shell script in that folder.
Basically I have something like this:
file { "/home/user/res":
ensure => "directory",
HI All,
Im trying vagrant and puppet, i would like to be able to launch an VM on
virtualbox then call puppet for installing packages and configuration.
I would be using this for all developers and loaded on their local
machine's Virtualbox.
so on vagrant i launch a machine and set hostname to
I'm wondering what's the current # of Puppet Professionals so far?
--
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
Hi,
I am trying to configure MCollective with RabbitMQ.
MCollective with RabbitMQ is working fine on Non Encrypted port 61613 but
it's not working on secure port.
I configure my RabbitMQ as following and check with "*netstat*" command,
secure port is open.
*Configuration on RabbitMQ Server:*
The latest round of updates to Debian Jesse (testing) has really broken
puppet-dashboard when using the puppetlabs repo. I currently have my apt
sources list set up to use the "unstable" repo (since there isn't a
"jessie" or "testing" repo). When I try to install puppet-dashboard I get
puppe
> What is the user that the service is running under?
Good questions. Aren't all services running as administrator?
> What version is the puppet agent on? The master?
Client: 3.4.3 (Windows 7 with all updates)
Server: 3.4.3-1puppetlabs1 (Debian stable)
Thanks,
Andy.
> > Hi!
> >
> > I've got a
It is hard to say without more information.
What is the user that the service is running under?
What version is the puppet agent on? The master?
On Fri, Mar 14, 2014 at 5:51 AM, Andy Spiegl wrote:
> Hi!
>
> I've got a problem with Windows clients:
>
> When running "puppet agent -t" manually e
MSIs can be installed from a url which may help keep the packages off of
each individual box. This means they are installable from a file share as
well. I am not sure about FTP support with MSIs.
Note that MSIs, not exe installers are the ones that work in this way.
Those would need to be accessib
By the way: this was a plain RPM install from puppet's yum repo ( RH EL6).
Don't know if this directory permission stuff was intended and has to be
manually aligned when using the RPM to run as a master...
Am Montag, 17. März 2014 12:56:33 UTC+1 schrieb bjoern pohl:
>
> Answering myself :)
> A
Answering myself :)
Actualle the error message was a bit misleading:
Error: Could not request certificate: Error 400 on SERVER: Permission
denied - /etc/puppet/auth.conf
This was not because of the content IN the auth.conf , it was because of
missing file permissions: the /etc/puppet directory wa
Hi,
i've got a strange problem with my server-side /etc/puppet/auth.conf.
The auth.conf is out-of-the-box, so the cert stuff looks basically like
this:
# allow access to the CA certificate; unauthenticated nodes need this
# in order to validate the puppet master's certificate
path /certificate/c
38 matches
Mail list logo
