On Nov 7, 2010, at 10:45 PM, Nigel Kersten wrote:
>
>
> On Sun, Nov 7, 2010 at 9:52 AM, Christopher McCrory
> wrote:
> Hello...
>
> # the hostname data is added via something like:
> # shell> ec2-run-instances ... --user-data "myservername" ami-123abc
> # by definition, the first line MUST b
Does puppet-dashboard support something like 'default' node? I want to
assign base classes to 'default' node, for applying for all nodes.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegro
Not yet, but see this ticket:
https://projects.puppetlabs.com/issues/4412
Brian
walexey wrote:
Does puppet-dashboard support something like 'default' node? I want to
assign base classes to 'default' node, for applying for all nodes.
--
You received this message because you are subscribed t
That only speaks to the initial install.
Let's say in 6 months, I update my local mirror to a yet newer version
of the kernel. I'm in the same boat.
The point of using a tool like Puppet, isn't just to automate your
installs, but also upgrades.
I'm surprised that this bug is this old, but it see
> When a generic EC2 instance is started it has a hostname of
> localhost.localdomain (or something like ip-10-111-222-33), a
> searchdomain of ec2.internal, and only the loopback address
> in /etc/hosts. To get a puppet client to bootstrap correctly all three
> of these things need to be changed
Hi,
Excerpts from Christopher McCrory's message of Sun Nov 07 12:52:48 -0500 2010:
>
> I wanted to be able to startup an EC2 instance with one command and
> have a fully functioning server without having to shell into each new
> instance and configure the bits to allow puppet to finish the
> co
Hi,
I try to serve a file
file { "/root/test3.txt":
ensure => file,
source => "puppet:///yum/test.txt",
}
On the puppetmaster this files look like this
#$ ls -n test.txt
-rw-r--r-- 1 502 301 4 8 Nov 16:25 test.txt
Finally, here is my question: What ownership may I expect on
- "Markus Falb" wrote:
> Hi,
>
> I try to serve a file
>
> file { "/root/test3.txt":
> ensure => file,
> source => "puppet:///yum/test.txt",
> }
>
> On the puppetmaster this files look like this
>
> #$ ls -n test.txt
> -rw-r--r-- 1 502 301 4 8 Nov 16:25 test.txt
>
>
* Bruce Richardson [2010/11/05 09:01]:
> [...] If developers, then there is always a way round - sudo,
> fakeroot, giving them virtual hosts to play with.
I'd like to second the virtual host suggestion -- throwaway VMs (or
zones, in solaris) work really well for this kind of situation.
Additiona
On Nov 8, 2010, at 8:03 AM, R.I.Pienaar wrote:
>
> - "Markus Falb" wrote:
>
>> Hi,
>>
>> I try to serve a file
>>
>> file { "/root/test3.txt":
>>ensure => file,
>>source => "puppet:///yum/test.txt",
>> }
>>
>> On the puppetmaster this files look like this
>>
>> #$ ls -n
Hi all,
I'm a new puppet user and new to the forum.
I just switched my Puppetmaster to running inside Apache (via
Passenger). When I make a change to a resource on the master, it
sometimes takes a given node TWO runs before the master will realize
the resource has changed and recompile a new cata
I am still new to the ruby language and I figured I'd share my file_exists
function to see if it is the correct approach and to offer it out there for
people who may have the same issue. We build our vhosts based off a template
and have come across the need to add in items for specific customers in
I have inherited some puppet configurations; there is an exec resource
that looks like this:
exec { "force-reload-httpd":
command => "/etc/rc.d/init.d/httpd force-reload",
refreshonly => true,
}
Should this be paired with a "subscribe" or "notify" somewhere?
--
You received this message bec
Refreshonly will execute when it is either notified or the subscribe
resource changes. If there is none of those definition then that Exec
will never execute.
On Nov 8, 9:49 am, Sean Carolan wrote:
> I have inherited some puppet configurations; there is an exec resource
> that looks like this:
>
Oops I guess that'll teach me for trying to use a shortcut for
posting.
On Nov 8, 11:57 am, "Matthew Black" wrote:
> I am still new to the ruby language and I figured I'd share my file_exists
> function to see if it is the correct approach and to offer it out there for
> people who may have the s
On 08.11.10 17:03, R.I.Pienaar wrote:
>
> - "Markus Falb" wrote:
>
>> Hi,
>>
>> I try to serve a file
>>
>> file { "/root/test3.txt":
>> ensure => file,
>> source => "puppet:///yum/test.txt",
>> }
>>
>> On the puppetmaster this files look like this
>>
>> #$ ls -n test.txt
>>
On Mon, Nov 8, 2010 at 2:17 AM, Patrick wrote:
>
> On Nov 7, 2010, at 10:45 PM, Nigel Kersten wrote:
>
> On Sun, Nov 7, 2010 at 9:52 AM, Christopher McCrory
>
> # yes, thrice
>> /usr/sbin/puppetd --no-daemonize --onetime --server
>> puppetmaster.example.com
>> /usr/sbin/puppetd --no-daemonize --
On Mon, Nov 8, 2010 at 6:49 AM, Sean Carolan wrote:
> I have inherited some puppet configurations; there is an exec resource
> that looks like this:
>
> exec { "force-reload-httpd":
> command => "/etc/rc.d/init.d/httpd force-reload",
> refreshonly => true,
> }
>
> Should this be paired with a "s
I am trying to implement stages in 2.6.2 (both client and server)
stage { [baseos, pre, post, brsoft]: }
class runstages { Stage[baseos] -> Stage[pre] -> Stage[main] ->
Stage[post] -> Stage[brsoft] }
node default {
include runstages
include debian::base_packages
On Nov 8, 2010, at 9:54 AM, Nigel Kersten wrote:
>
>
> On Mon, Nov 8, 2010 at 2:17 AM, Patrick wrote:
> On Nov 7, 2010, at 10:45 PM, Nigel Kersten wrote:
>
> On Sun, Nov 7, 2010 at 9:52 AM, Christopher McCrory
>> # yes, thrice
>> /usr/sbin/puppetd --no-daemonize --onetime --server
>> puppet
On Nov 8, 2010, at 9:36 AM, Markus Falb wrote:
> On 08.11.10 17:03, R.I.Pienaar wrote:
>>
>> - "Markus Falb" wrote:
>>
>>> Hi,
>>>
>>> I try to serve a file
>>>
>>> file { "/root/test3.txt":
>>>ensure => file,
>>>source => "puppet:///yum/test.txt",
>>> }
>>>
>>> On the p
On Nov 8, 2010, at 9:10 AM, Kent wrote:
> Hi all,
>
> I'm a new puppet user and new to the forum.
>
> I just switched my Puppetmaster to running inside Apache (via
> Passenger). When I make a change to a resource on the master, it
> sometimes takes a given node TWO runs before the master will r
Going to post this again as I posted by accident in another thread..
I am still new to the ruby language and I figured I'd share my
file_exists
function to see if it is the correct approach and to offer it out
there for
people who may have the same issue. We build our vhosts based off a
template
a
On Mon, Nov 8, 2010 at 10:51 AM, Patrick wrote:
>
> On Nov 8, 2010, at 9:54 AM, Nigel Kersten wrote:
>
>
> On Mon, Nov 8, 2010 at 2:17 AM, Patrick wrote:
>>
>> On Nov 7, 2010, at 10:45 PM, Nigel Kersten wrote:
>
>
>>
>> On Sun, Nov 7, 2010 at 9:52 AM, Christopher McCrory
>>>
>>> # yes, thrice
>>>
On Nov 8, 2010, at 10:27 AM, chris mague wrote:
> I am trying to implement stages in 2.6.2 (both client and server)
Chris / kekai? Are you back to doing sysadmin work? Good to see you man. I
haven't made the leap to 2.6 yet so I can't help with your question but wanted
to say hi.
(Assuming I
Ack, sorry list. That was obviously meant to be unicast.
Reply-To Considered Harmful.
http://marc.merlins.org/netrants/reply-to-harmful.html
-=Eric
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-u
>> 3) One last chance just in case something didn't work, timed out, or I
>> forgot a require. (Finishes in seconds for me)
>
> Honestly, you should be discovering such missing requires in your testing
> process. It's not good practice to simply run another one "just in case" in
> my opinion.
+1.
On Nov 8, 2010, at 12:12 PM, Richard Crowley wrote:
>>> 3) One last chance just in case something didn't work, timed out, or I
>>> forgot a require. (Finishes in seconds for me)
>>
>> Honestly, you should be discovering such missing requires in your testing
>> process. It's not good practice to
On Nov 8, 2010, at 11:10 AM, Nigel Kersten wrote:
> On Mon, Nov 8, 2010 at 10:51 AM, Patrick wrote:
>>
>> On Nov 8, 2010, at 9:54 AM, Nigel Kersten wrote:
>>
>>
>> On Mon, Nov 8, 2010 at 2:17 AM, Patrick wrote:
>>>
>>> On Nov 7, 2010, at 10:45 PM, Nigel Kersten wrote:
>>
>>
>>>
>>> On Su
Hi I'm trying to setting http_proxy environment variable by adding it
to the /etc/environment file.
I was wondering how I can force puppet to reload this file whenever
the file changes.
I have tried a few things and none of them have worked,
1.)
exec { "source_environment":
command =
>> +1. Catalogs that need to "converge" or are anything but a no-op on
>> their second run should be considered broken.
>
> *) My philosophy is this puppet.conf should be managed by puppet.
> *) Sometimes a run won't be completed correctly unless puppet.conf is up to
> date at the start of a run.
> Hi I'm trying to setting http_proxy environment variable by adding it
> to the /etc/environment file.
>
> I was wondering how I can force puppet to reload this file whenever
> the file changes.
>
> I have tried a few things and none of them have worked,
>
> 1.)
> exec { "source_environment":
>
Thanks for you help.
Does that mean that there is no way to do it from inside of a puppet
module?
On Nov 8, 5:11 pm, Richard Crowley wrote:
> > Hi I'm trying to setting http_proxy environment variable by adding it
> > to the /etc/environment file.
>
> > I was wondering how I can force puppet t
Hi,
For a long time now when we run puppetd --test I get the following double
output on our custom facts,
info: Retrieving plugin
info: Loading facts in scratch
info: Loading facts in os_name
info: Loading facts in pam_limits_d
info: Loading facts in os_platform
info: Loading facts in nvidia_gra
On Nov 8, 2010, at 2:03 PM, Richard Crowley wrote:
>>> +1. Catalogs that need to "converge" or are anything but a no-op on
>>> their second run should be considered broken.
>>
>> *) My philosophy is this puppet.conf should be managed by puppet.
>> *) Sometimes a run won't be completed correctly
Nigel Kersten writes:
> Honestly, you should be discovering such missing requires in your
> testing process. It's not good practice to simply run another one "just
> in case" in my opinion.
That's easy to say in theory, but extremely difficult to test in practice,
since order is non-deterministi
On Mon, Nov 8, 2010 at 3:14 PM, Derek Yarnell wrote:
> For a long time now when we run puppetd --test I get the following double
> output on our custom facts,
>
>
> Anyone seen this behavior?
Yes there's a bug filed with this issue:
http://projects.puppetlabs.com/issues/3741
Please append any
> Why would you use Capistrano to manage puppet.conf on your masters? Does it
> give you some advantage over just using puppet to manage itself?
We have about half a dozen different web applications that we deploy,
all via git-archive(1) and Capistrano. The Puppet master is one of
those and is
I am having a great deal of trouble using a custom fact in a module and I am
hoping someone can help me out.
I am using facter-1.5.0-2.el4 and puppet-0.24.5-1.el4. I know these are
really old versions.
The custom fact is defined using an environmental variable
export FACTER_VERTICAL="dev fit"
Hi James.
Could you tell if you found a resolution to this problem? I seem to
experience it as well.
Thanks in advance,
Regards,
Roman
On Oct 20, 2:31 am, "luke.bigum" wrote:
> Hi all,
>
> I'm having a stupid moment getting a remote file bucket working. My
> client only file buckets locally, n
40 matches
Mail list logo
