Hi,
>>The Exec['installCassandra'] executed correctly immediately prior to the
attempt to create the file['cassandraEnv'] resource. So I know the
appropriate >>information is available from the file system.
It is a new server, so exec['installCassandra'] will install it but after
that, your c
Awesome!!
So, just to wrap it up taking all your answers together, we have two
options:
- Individual certs using Puppet 3.4 policy based autosign feature
(http://docs.puppetlabs.com/puppet/3/reference/ssl_autosign.html#policy-based-autosigning)
and some custom "puppet cert clean " HTTP calls befor
Is anyone using mcollective module from puppetlabs?
is there built-in way to configure activemq clustering between 2 DCs which
I am missing?
Andrey
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receivi
On Thursday, January 9, 2014 3:58:10 PM UTC+1, jcbollinger wrote:
> puppet agent --no-daemonize --debug --verbose --interval=120 --logdest
>> stdout
>
>
The --interval option is not accepted, so being forced to use the default
of 30 minutes I used:
PUPPET_EXTRA_OPTS="--debug --verbose --lo
Hi,
note that running puppet without administrator privileges for initial
server setup is probably pointless. Therefor it is my sincere hope that
there is not yet any solution to kick this off via web interface,
because that would imply serious security concerns.
I suppose you could solve this mo
Hi,
looks like a minor bug with the mount provider. You may want to file a
report, although you should be able to trivially work around it by
fixing your fstabs, correct?
Thanks,
Felix
On 01/10/2014 10:49 AM, zerozerouno...@gmail.com wrote:
> The problem remained the same, of course, and here is
On Friday, January 10, 2014 11:05:47 AM UTC+1, Felix.Frank wrote:
looks like a minor bug with the mount provider. You may want to file a
> report, although you should be able to trivially work around it by
> fixing your fstabs, correct?
Yes, it's not a big problem for me. I just wanted to be
:) OK.
I think your original post to the list was pretty much to the point.
On 01/10/2014 11:31 AM, zerozerouno...@gmail.com wrote:
>
> I'll file a report even though I'm not 100% sure "what" to report… :)
--
You received this message because you are subscribed to the Google Groups
"Puppet Us
Hi Johan,
Thanks for the suggestion, unfortunately it did not work.
It seems that using a scope file
(http://docs.puppetlabs.com/hiera/1/command_line.html#json-and-yaml-scopes)
doesn't load the facts into the global scope. Could this be a hiera
command line bug?
If I change the hiera.yaml hi
On Friday, January 10, 2014 11:32:59 AM UTC+1, Felix.Frank wrote:
> I think your original post to the list was pretty much to the point.
I just realized the machine was still running puppet 2.6.18.
I now upgraded to 2.7.23 and I'll wait some runs before filing the issue.
The bug appears to be
Hi all,
Is there a standard way of dealing with systems (well, in reality any
hardware) that is not actually part of the puppet deployment to keep track
of it? I would like to store data such as each spare hard drive, CPU,
Memory i have at a given location, however it's not connected. My
unde
Unless I am seriously mistaken, "masterless Puppet" is achieved by each node
being its own master.
And since puppet-master does not work on Windows (agent only) I suspect that
masterless Windows puppet is mot currently possible.
I could be mistaken.
"Sometimes I think the surest sign that in
On Friday, January 10, 2014 6:26:25 AM UTC-6, Ygor wrote:
>
> Unless I am seriously mistaken, "masterless Puppet" is achieved by each
> node being its own master.
>
Then I guess you are seriously mistaken. Masterless Puppet is normally
achieved by nodes using "puppet apply" against locally-
On Friday, January 10, 2014 5:53:51 AM UTC-6, zerozer...@gmail.com wrote:
>
> On Friday, January 10, 2014 11:32:59 AM UTC+1, Felix.Frank wrote:
>
>
>> I think your original post to the list was pretty much to the point.
>
>
> I just realized the machine was still running puppet 2.6.18.
> I now
On 01/10/2014 03:19 PM, jcbollinger wrote:
> Myself, I'm stumped. I agree with Felix that it looks like there's a
> bug in the provider, but that's not really saying much more than "it
> shouldn't do that". I am curious, however, whether Puppet is actually
> modifying /etc/fstab on either the fai
On Friday, January 10, 2014 3:19:39 PM UTC+1, jcbollinger wrote:
> A v2.6 agent should work with a v2.7 master, but it is worthwhile checking
> out the effect of the upgrade.
>
The upgrade to 2.7.23 had no effect on the issue.
The master runs 3.3.2 by the way; are there issues with this?
>
Hi Raj,
I am seeing the same error. Usually a couple of page refreshes will
eventually get you the page with your classes. But is seems that not all
classes on your master might be replaced. Not sure yet what the solution
is, I had filed a bug but Puppet support could not come up with a clear
Thank you for setting me straight, John.
Instead of sitting in my ignorance, I now stand, corrected.
“Sometimes I think the surest sign that intelligent life exists elsewhere in the
universe is that none of it has tried to contact us.” (Bill Waterson: Calvin &
Hobbes)
On Jan 10, 2014, at 09
Johan De Wit writes:
> I'm very interested in your improvement. Is it available for the
> public somewhere ?
No, there is just too much site-specific stuff hardcoded in
there. Basically, it:
- grabs the host's entry in LDAP, or bombs out if it doesn't exist
- extracts the puppetclass attribut
Hi Peter,
It all depends wher you use variables.
In manifests, it is best practice to scope facts @ top scope (::), if
you really want to use the fact
you can do something like this :
ipaddress => 192.168.10.0 (the fact)
class { 'x':
$ipaddress = '10.0.0.0'
notify { "fact = ${::ipaddre
On Thursday, January 9, 2014 6:23:23 PM UTC-6, Patrick Hemmer wrote:
>
> There's been an idea floating in my mind for quite a while now about using
> a job queue for compiling puppet catalogs. I just mentioned the idea on IRC
> and a few people really liked the idea, so I thought I'd bring it u
Hi everyone,
It's not exactly a secret that FOSDEM will be taking place during the first
weekend of February at the usual location, the ULB Solbosch campus in
Brussels. It's also not that big of a secret that a lot of Puppeteers
attend especially now that we have a Configuration Management room
Hi all,
The Belgian Puppet User Group will represent all Puppet User Groups @
the puppet stand @ FOSDEM
We hope to see you all passing by the stand and have a nice chat.
If we, as the belgian puppet user group can help out with this, feel
free to contact me, so i can assign some volunteer
On Friday, January 10, 2014 2:42:29 AM UTC-6, Stefan Heijmans wrote:
>
> Hi,
>
> >>The Exec['installCassandra'] executed correctly immediately prior to the
> attempt to create the file['cassandraEnv'] resource. So I know the
> appropriate >>information is available from the file system.
> It is
Hi,
Sounds good. It depends a bit on how big the group gets. If we're a small
amount of people it's easier to just figure out something ad-hoc but if the
group grows we'll need to think of a venue beforehand at which point having
a few local volunteers help out and suggest places would be extre
Hi all,
Well this will be my first time at FOSDEM. And CfgMgMt too. I am looking
forward to the trip with my friend James and I am especially looking
forward to meeting you great people.
My name is Mike and I don't have a photo to share with you guys right now
I'm afraid. I will be the ginger
Same for us, We are presenting the Puppet User Community. And since
this is a home match for us, there will always be people available to
help out if the need arise.
On 01/10/2014 10:45 PM, Daniele Sluijters wrote:
Hi,
Sounds good. It depends a bit on how big the group gets. If we're a
On Fri, Jan 10, 2014 at 1:13 PM, Daniele Sluijters
wrote:
> Hi everyone,
>
> It's not exactly a secret that FOSDEM will be taking place during the first
> weekend of February at the usual location, the ULB Solbosch campus in
> Brussels. It's also not that big of a secret that a lot of Puppeteers a
Hello,
I apologize in advance if this question is redundant.
I'm using puppet version 2.7.11 (because that's what Ubuntu 12.04 LTS has
to offer) and I'd like to override a class default parameter with 'undef'.
For example, the puppetlabs 'apache' module (version 0.10.0) sets 'ensure
=> runnin
29 matches
Mail list logo
