Hi,
For learning puppet follow the link,
http://docs.puppetlabs.com/learning/manifests.html and
http://docs.puppetlabs.com/learning/modules1.html
This will help you in writing simple manifests.
As you have C# code, and you want it to execute on client, am i right?
If this is the case,
1. you j
Hi all,
I'm wondering what would be the best approach to extract a value from the
hostname. In my case, the hostname contains the type of environment (dev,
int, qa, prod) and I would like to have a variable called $env which
contains will be extracted from such FQDNs:
- vm-role-app-prod-1
- vm-ro
Hi Tim,
For managing server specific parameters i will suggest you to use
hiera, please refer link http://docs.puppetlabs.com/hiera/1/puppet.html
So for 1st example: you can either use heira or use parametrized class so
that you can pass server specific parameters ( admin list) from site.pp.
Hi,
My both problems have been solved. I instead of using the pessenger
services started using the *WEBrick web services*. When I stopped the
*puppetmaster
service and started the apache2 service (port 8140)* things went like
rocket !!
Second issue with the .swp file went away when I added the
A custom fact that uses regex to grab the fourth, dash-separated value from the
hostname seems like a good way to go as it would make the $env value accessible
globally.
Alternatively, you can use a selector within your manifests:
$env = $hostname ? {
/-dev-/ => 'dev',
/-int-/ =>
Hi,
I'm newbie to Puppet even i don't know how to configure it.
Could you please tell me how to run scripts from puppet master to puppet
agent without interacting the agent nodes(like rack,bootstrap from puppet
master)?
is there any puppet cook books or any puppet pdfs?
Thanks in advanc
Hi,
you can use fact like,
env.rb
Facter.add("env") do
setcode do
Facter::Util::Resolution.exec('hostname | cut -d"-" -f4')
end
end
I hope this will work fine.
Thanks & Regards,
Sneha More,
NTT DATA GTS, OSS Center, India (Pune)
On Friday, September 27, 2013 3:17:49 PM UTC+5:30,
> Lastly, the puppetdb-ssl-setup script still does not work when the PuppetDB
> does not reside on the Puppetmaster. The fix is pretty simple, and the
> issue is in the bug tracker. I created a question and answer on
> ask.puppetlabs.com to try and help others that run into it:
> https://ask.pupp
Hi Dilip,
If you want to execute any script on client, then just transfer that
script to puppetclient using "File" resource
and execute it using "exec" resource.
Refer link http://www.puppetcookbook.com/ for Puppet cookbook
or http://docs.puppetlabs.com/learning/ral.html for learning resource
i'll try and let u know,Thank You
Thanks,
Dilip
On Fri, Sep 27, 2013 at 5:04 PM, Sneha More wrote:
> Hi Dilip,
>If you want to execute any script on client, then just transfer that
> script to puppetclient using "File" resource
> and execute it using "exec" resource.
> Refer link http://w
On 26.09.2013 20:38, Matthew Arguin wrote:
David, completely possible that there is a bug in my manifest somewhere,
my coworker has been doing most of the work getting our puppet system
set up this way and i am working my way in to it, so i will certainly be
trying to see if there is duplication
> Thanks for the post.
> We don't have internet access in our development servers ,so we can not run
> leiningen shell script file.
> If you know another way to install leiningen which does not require
> internet.
> let me know.
I actually would highly recommend finding a proxy solution as opposed
On 27 September 2013 13:26, Ken Barber wrote:
> > Lastly, the puppetdb-ssl-setup script still does not work when the
> PuppetDB
> > does not reside on the Puppetmaster. The fix is pretty simple, and the
> > issue is in the bug tracker. I created a question and answer on
> > ask.puppetlabs.com t
On Thursday, September 26, 2013 5:39:10 PM UTC-5, Wolf Noble wrote:
>
>
>
>
> On Thu, Sep 26, 2013 at 5:21 PM, jcbollinger
>
> > wrote:
>
>>
>>
>> On Thursday, September 26, 2013 3:11:24 PM UTC-5, Wolf Noble wrote:
>>>
>>> Hi Sergey,
>>>
>>> I've noticed behavior similar to then when resource o
On Thursday, September 26, 2013 4:00:25 PM UTC-5, TimV wrote:
>
> I've got a basic puppet deployment up and running with some basic modules
> in place for configuration management. Running 3.3.0 on server and clients.
>
> My next stumbling block is how to I manage hosts that have host or
> appl
On Friday, September 27, 2013 6:15:02 AM UTC-5, Dilip Varma wrote:
>
> Hi,
>
> I'm newbie to Puppet even i don't know how to configure it.
>
> Could you please tell me how to run scripts from puppet master to puppet
> agent without interacting the agent nodes(like rack,bootstrap from puppet
> m
On Friday, September 27, 2013 4:47:49 AM UTC-5, Romain PELISSE wrote:
>
> Hi all,
>
> I'm wondering what would be the best approach to extract a value from the
> hostname. In my case, the hostname contains the type of environment (dev,
> int, qa, prod) and I would like to have a variable called
On 27 September 2013 16:17, jcbollinger wrote:
>
>
> On Friday, September 27, 2013 4:47:49 AM UTC-5, Romain PELISSE wrote:
>>
>> Hi all,
>>
>> I'm wondering what would be the best approach to extract a value from the
>> hostname. In my case, the hostname contains the type of environment (dev,
>>
Well, I'm getting deeper and deeper into Puppet and loving it!
I'm at the point, now, that I need to start standardizing on modules and
I'm wondering whether someone can share their experience. I've been on
Puppet Forge and there are so many modules to choose from! How do you go
about selecting?
Hi all,
I'm seeing exactly the same issue. Is there some config setting that can
prevent this? I'd rather not just redirect all master logging to /dev/null.
This is with Puppet 3.3.0 and Hiera 1.2.1 on RHEL6.
J
On Wednesday, 31 July 2013 18:50:19 UTC+1, Bill Sirinek wrote:
>
>
> (puppet 3.1.1
I'm having a real trouble getting hiera to work as expected.
My current setup has a puppet master and an agent. On both I have the same
/etc/hiera.yaml file linked into the /etc/puppet directory. I've also been
able to confirm that hiera is seeing the right json files in /var/lib/hiera.
What
Prefix doesn't return a string, it returns an array. I think this gets
stringified in the error message, but it screws up the lookup. Try
hiera($role_value[0]).
On Friday, September 27, 2013 9:32:12 AM UTC-7, Tom Hanstra wrote:
>
> I'm having a real trouble getting hiera to work as expected.
>
>
My concern is that after downloading the PuppetDB RPM from PuppetLabs it
should not throw errors on installation, which it currently does if you
install it on a server that is not the master. I also believe that having
the PuppetDB separate from the Puppetmaster is not an edge case (I'd
actually a
This is amusing to me, because I spent an hour or so the other day
trying to turn hiera logging *on*. If you are using a syslog
facility, the hiera debug stuff does not seem to go to the log
(actually gets logged at level :info, rather than :debug). I had to
add the --logdest option in rack to ha
Hi all,
I've started testing with using Hiera for storing configs and I have a
noobish question.
Here's an example of my yaml file (/etc/puppet/hieradata/vertname.yaml):
---
#icecast
type: vanilla
client1:
cid: 999
cid_hostname: icecast1
cid_ipaddress: 192.168.254.12
password: WhatYoSay
Perhaps make it a defined type and use the create resources function. I
can't really think of any other way to correctly scope the various
parameters. You'd have to tweak your yaml slightly...
---
#icecast
type: vanilla
icecast_clients:
client1:
cid: 999
cid_hostname: icec
Here's what I advise in training classes:
1) Start with puppetlabs/ namespace modules.
2) If you don't find a puppetlabs/ module then you have to know a little
bit about the groups/individuals within the community who have a good rep
for putting out quality modules and identify their namespace. I
Ellison,
Brilliant! Worked like a champ. This opens whole new worlds and should
make managing the config *much* easier!!!
Greg
On Friday, September 27, 2013 12:13:03 PM UTC-7, Ellison Marks wrote:
>
> Perhaps make it a defined type and use the create resources function. I
> can't really th
**Release candidate:**
Pre-release: 3.3.1 has not yet been released.
RC1: September 23, 2013
RC2: September 27, 2013
3.3.1 is to be a bug fix release in the Puppet 3.3 series. The focus
of the release is fixing backwards compatibility regressions that
slipped in via the YAML deprecations in 3.3.
29 matches
Mail list logo