Hi trey,
I put it here: https://github.com/alexfouche/rvm
On 19 oct, 21:07, Robert Mortimer wrote:
> I got it installed in the end:
>
> 1) Only install dev libraries for the architecture you are using (gcc
> and mysql dev)
> 2) Gems from source (not RPM) were used
> 3) Active record can not be
I also had such a scheme, but having the puppetmaster on an internal
private IP network, not even a DMZ. Puppet runs were triggered, there
was no puppet client daemon or crontabed runs.
server with Puppet client is on interent with public IP
Local intranet:
Puppetmaster
a Squid proxy
When i want
Hello!
I'm trying to install puppet dashboard according to the instructions
in the documentation :
http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html
I am installing it from the .deb package, however after installation I
cannot find the "settings.yml" file.
Also, when trying to
> On Fri, Oct 21, 2011 at 10:25 AM, Aaron Grewell
> wrote:
> > If tomcat::enable is in a separate file you'll want to 'include' it in
> > tomcat::server to ensure it's in scope.
On Oct 21, 3:50 pm, Douglas Garstang
replied:
> Isn't the net result of including something the same as it's really
I've been trying to find information, suggestions, etc. for how to combine
scaling Puppet with the use of management tools like Dashboard/Foreman and
MCollective. Our current thinking for an initial deployment is two VMs as
Puppet Master worker nodes fronted by a pair of NetScalers. However, I'm no
Hello
I'm experimenting with the new resource chaining syntax. Here's the
code:
class first { notice("first") }
class second { notice("second") }
class third { notice("third") }
include third
include second
include first
Class["first"] -> Class["second"] -> Class["third"]
Shouldn
The ordering only applies to the order in which resources are applied, not
the order in which the code is processed.
It will work like you expect if you switch out the calls to the notice
function with notify resources.
On Mon, Oct 24, 2011 at 3:48 AM, Andre Nathan wrote:
> Hello
>
> I'm experi
On Oct 24, 5:38 pm, Justin Lloyd wrote:
> I've been trying to find information, suggestions, etc. for how to combine
> scaling Puppet with the use of management tools like Dashboard/Foreman and
> MCollective. Our current thinking for an initial deployment is two VMs as
> Puppet Master worker nod
Excuse my first misclick ;)
On Oct 24, 5:38 pm, Justin Lloyd wrote:
> I've been trying to find information, suggestions, etc. for how to combine
> scaling Puppet with the use of management tools like Dashboard/Foreman and
> MCollective. Our current thinking for an initial deployment is two VMs as
- Original Message -
> For MCollective, start reading about subcollectives[1] and Stomp
> failover pools [2]. There's no reason why each of your Puppet Masters
> can't also be Stomp servers. ActiveMQ has some nice abilities to send
> messages between ActiveMQ servers that I started readin
On Mon, Oct 24, 2011 at 6:38 PM, Justin Lloyd wrote:
> I've been trying to find information, suggestions, etc. for how to combine
> scaling Puppet with the use of management tools like Dashboard/Foreman and
> MCollective. Our current thinking for an initial deployment is two VMs as
> Puppet Master
I'm new to anything more than very basic puppet. I need to create a
(differently named) working directory which like /tmp has 1777 mode
and is also a mounted file system. I need to avoid the underlying
mount point picking up these permissions (it needs to be 755). How can
I arrange this with puppet
We have discovered a security vulnerability (“AltNames Vulnerability”)
whereby a malicious attacker can impersonate the Puppet master using
credentials from a Puppet agent node. This vulnerability cannot cross
Puppet deployments, but it can allow an attacker with elevated
privileges on one Puppet-m
Puppet 2.6.12 is a security update release in the 2.6.x branch.
The only changes since 2.6.11 are security fixes for the following
vulnerability:
* CVE-2011-3872, Altnames Vulnerability
For more details on this vulnerability, follow the link on our
blog post:
http://puppetlabs.com/blog/importan
Puppet 2.7.6 is a feature and security update release in the 2.7.x branch.
The security changes in 2.7.6 addres CVE-2011-3872
* CVE-2011-3872, Altnames Vulnerability
For more details on this vulnerability, follow the link on our
blog post:
http://puppetlabs.com/blog/important-security-announceme
In my experimental area at the moment -
http://buildfarm.opencsw.org/experimental.html#markp
It's been submitted to the catalog though.
--Mark
--
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@g
I'm trying to upgrade from 2.6.7 to to 2.7.6 and I'm running into an
issue in my extlookup() calls. A lot of the variables which should be
defined aren't defined within extlookup.rb. I've tested 2.6.7 agent
and 2.7.5 agent against the 2.6.7 master and 2.7.6 master. I adjusted
extlookup.rb slight
I diff'd the extlookup.rb between 2.6.7 and 2.7.6 and noticed this was
different, so I changed it back and things are working again:
--> git diff ./lib/puppet/parser/functions/extlookup.rb
diff --git a/lib/puppet/parser/functions/extlookup.rb b/lib/puppet/
parser/functions/extlookup.rb
index 5fbf
- Original Message -
> I'm trying to upgrade from 2.6.7 to to 2.7.6 and I'm running into an
> issue in my extlookup() calls. A lot of the variables which should
> be
> defined aren't defined within extlookup.rb. I've tested 2.6.7 agent
> and 2.7.5 agent against the 2.6.7 master and 2.7.
looks like that's it. i'll use the workaround nigel recommended in
that issue (same as my diff above) until that issue is resolved.
thanks for the quick response, R.I.!
On Oct 24, 6:10 pm, "R.I.Pienaar" wrote:
> - Original Message -
> > I'm trying to upgrade from 2.6.7 to to 2.7.6 and I
On Oct 24, 2:25 am, "ollies...@googlemail.com"
wrote:
> On Oct 21, 12:55 pm, Andrew Thompson wrote:> On Oct
> 20, 10:18 am, "ollies...@googlemail.com" wrote:
> > > Taking a brief look at extlookup()
>
> > > We have a module to setup resolv.conf based on location so we have a %
> > > {domain}.c
Base on CVE-2011-3872, i want to upgrade all puppet master and agent,
my plan upgrade puppet master first then the agent, whether the
configuration I can still be used?
if use version 2.6.12 as a puppet master and agent still 2.6.6 for
temporary then after that i upgrade to 2.6.12 for the agent?
22 matches
Mail list logo
