date:20140204

Re: [Puppet Users] Slides of the talk TDD and puppet a gave today in Ghent, cfgmgmtcamp.eu

2014-02-04 Thread Johan De Wit


On 02/04/2014 09:26 PM, Johan De Wit wrote:

Hi all,

http://www.slideshare.net/johandw/test-driven-developmentandpuppetcfgmgmtcampeu20140402 



Jan's slides of his part of the talk, can be found here : 
http://vstone.github.io/puppet-module-testing


I will write a blog on the Belgian Puppet User Group Website, 
http://puppet-be.github.io/ and post a reply when done.


Feel free to comment on this topic.

Grts

Johan


The blog

http://puppet-be.github.io/coding/2014/02/04/Test-Driven-Development-And-Puppet-Talk/

--
Johan De Wit

Open Source Consultant

Red Hat Certified Engineer (805008667232363)
Puppet Certified Professional 2013 (PCP006)
_
 
Open-Future Phone +32 (0)2/255 70 70

Zavelstraat 72  Fax   +32 (0)2/255 70 71
3071 KORTENBERG Mobile+32 (0)474/42 40 73
BELGIUM http://www.open-future.be
_
 


Next Events:
Puppet Fundamentals Training | 
http://www.open-future.be/puppet-fundamentals-training-4-till-6th-february
Puppet Intruction Course | 
http://www.open-future.be/puppet-introduction-course-7th-february
Zabbix Certified Training | 
http://www.open-future.be/zabbix-certified-training-10-till-12th-february
Zabbix for Large Environments Training | 
http://www.open-future.be/zabbix-large-environments-training-13-till-14th-february
Subscribe to our newsletter | http://eepurl.com/BUG8H

--
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.google.com/d/msgid/puppet-users/52F1677A.5040700%40open-future.be.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: [Puppet-dev] Slides of the talk TDD and puppet a gave today in Ghent, cfgmgmtcamp.eu

2014-02-04 Thread Johan De Wit


On 02/04/2014 09:26 PM, Johan De Wit wrote:

Hi all,

http://www.slideshare.net/johandw/test-driven-developmentandpuppetcfgmgmtcampeu20140402 



Jan's slides of his part of the talk, can be found here : 
http://vstone.github.io/puppet-module-testing


I will write a blog on the Belgian Puppet User Group Website, 
http://puppet-be.github.io/ and post a reply when done.


Feel free to comment on this topic.

Grts

Johan



The blog

http://puppet-be.github.io/coding/2014/02/04/Test-Driven-Development-And-Puppet-Talk/

--
Johan De Wit

Open Source Consultant

Red Hat Certified Engineer (805008667232363)
Puppet Certified Professional 2013 (PCP006)
_
 
Open-Future Phone +32 (0)2/255 70 70

Zavelstraat 72  Fax   +32 (0)2/255 70 71
3071 KORTENBERG Mobile+32 (0)474/42 40 73
BELGIUM http://www.open-future.be
_
 


Next Events:
Puppet Fundamentals Training | 
http://www.open-future.be/puppet-fundamentals-training-4-till-6th-february
Puppet Intruction Course | 
http://www.open-future.be/puppet-introduction-course-7th-february
Zabbix Certified Training | 
http://www.open-future.be/zabbix-certified-training-10-till-12th-february
Zabbix for Large Environments Training | 
http://www.open-future.be/zabbix-large-environments-training-13-till-14th-february
Subscribe to our newsletter | http://eepurl.com/BUG8H

--
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.google.com/d/msgid/puppet-users/52F1678D.8000803%40open-future.be.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Slides of the talk TDD and puppet a gave today in Ghent, cfgmgmtcamp.eu

2014-02-04 Thread Johan De Wit


Hi all,

http://www.slideshare.net/johandw/test-driven-developmentandpuppetcfgmgmtcampeu20140402

Jan's slides of his part of the talk, can be found here : 
http://vstone.github.io/puppet-module-testing


I will write a blog on the Belgian Puppet User Group Website, 
http://puppet-be.github.io/ and post a reply when done.


Feel free to comment on this topic.

Grts

Johan

--
Johan De Wit

Open Source Consultant

Red Hat Certified Engineer (805008667232363)
Puppet Certified Professional 2013 (PCP006)
_
 
Open-Future Phone +32 (0)2/255 70 70

Zavelstraat 72  Fax   +32 (0)2/255 70 71
3071 KORTENBERG Mobile+32 (0)474/42 40 73
BELGIUM http://www.open-future.be
_
 


Next Events:
Puppet Fundamentals Training | 
http://www.open-future.be/puppet-fundamentals-training-4-till-6th-february
Puppet Intruction Course | 
http://www.open-future.be/puppet-introduction-course-7th-february
Zabbix Certified Training | 
http://www.open-future.be/zabbix-certified-training-10-till-12th-february
Zabbix for Large Environments Training | 
http://www.open-future.be/zabbix-large-environments-training-13-till-14th-february
Subscribe to our newsletter | http://eepurl.com/BUG8H

--
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.google.com/d/msgid/puppet-users/52F14CF4.50400%40open-future.be.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Understanding script process control

2014-02-04 Thread José Luis Ledesma

Also try removing the subscribe parameter from the service, and check if
the restart works properly.

Regards,
El 04/02/2014 21:09, "José Luis Ledesma" 
escribió:

> Have you tried setting hasstatus => true in the service definition?
>
> Could you provide a puppet agent -t --debug from the node?
>
> Regards,
> El 04/02/2014 20:55, "JonY"  escribió:
>
>> I have an issue where puppet keeps starting additional instances of a
>> process even though it's already running. The 'control script' in question
>> does have a 'status' command but I'm thinking that I'm not properly telling
>> puppet that the process is ok.
>>
>> From the site:
>> The init script's status command must return 0 if the service is running
>> and a nonzero value otherwise. Ideally, these exit codes should conform to 
>> the
>> LSB's 
>> specification
>>  for
>> init script status actions, but Puppet only considers the difference
>> between 0 and nonzero to be relevant.
>>
>> The script is exiting with 'exit 0' when the process is running and it's
>> creating a .PID file for it in /var/run. If I examine 'echo $?' after
>> running 'service myscript status' I see 0. Is there some other indication
>> that I need? Should the script *actually* return 0?
>>
>> When the box in question boots, there are immediately two instances of
>> the service running. Over time it builds up to quite a pile.
>>
>> If I run the script manually it responds as I would expect. "process is
>> running" and doesn't start additional instances.
>>
>> puppet script:
>>
>> class plugpc::local_services::x10monitor inherits plugpc::local_services
>> {
>> package
>> {
>> "x10monitor" :
>> ensure => "latest",
>> require => Package[ "mysql-server-5.1" ];
>> }
>>
>> service
>> {
>> "x10monitor" :
>> ensure => "running",
>> enable => "true",
>> subscribe => Package[ "x10monitor" ],
>> require => [ Service[ "mysql" ], Package[
>> "x10monitor" ]];
>> }
>>
>> file
>> {
>> '/etc/logrotate.d/x10monitor' :
>> mode => 644,
>> source => 'puppet:///modules/plugpc/logrotate/x10monitor',
>> }
>>
>> }
>>
>>  --
>> 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.google.com/d/msgid/puppet-users/e3c410eb-0415-414f-9a0f-b8695efdadb7%40googlegroups.com
>> .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>

-- 
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.google.com/d/msgid/puppet-users/CAF_B3dczneBvCPy4QxZKQVz%3D4u1_0R6wNeyRwKcS3hYrQVgvmA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Understanding script process control

2014-02-04 Thread José Luis Ledesma

Have you tried setting hasstatus => true in the service definition?

Could you provide a puppet agent -t --debug from the node?

Regards,
El 04/02/2014 20:55, "JonY"  escribió:

> I have an issue where puppet keeps starting additional instances of a
> process even though it's already running. The 'control script' in question
> does have a 'status' command but I'm thinking that I'm not properly telling
> puppet that the process is ok.
>
> From the site:
> The init script's status command must return 0 if the service is running
> and a nonzero value otherwise. Ideally, these exit codes should conform to the
> LSB's 
> specification
>  for
> init script status actions, but Puppet only considers the difference
> between 0 and nonzero to be relevant.
>
> The script is exiting with 'exit 0' when the process is running and it's
> creating a .PID file for it in /var/run. If I examine 'echo $?' after
> running 'service myscript status' I see 0. Is there some other indication
> that I need? Should the script *actually* return 0?
>
> When the box in question boots, there are immediately two instances of the
> service running. Over time it builds up to quite a pile.
>
> If I run the script manually it responds as I would expect. "process is
> running" and doesn't start additional instances.
>
> puppet script:
>
> class plugpc::local_services::x10monitor inherits plugpc::local_services
> {
> package
> {
> "x10monitor" :
> ensure => "latest",
> require => Package[ "mysql-server-5.1" ];
> }
>
> service
> {
> "x10monitor" :
> ensure => "running",
> enable => "true",
> subscribe => Package[ "x10monitor" ],
> require => [ Service[ "mysql" ], Package[
> "x10monitor" ]];
> }
>
> file
> {
> '/etc/logrotate.d/x10monitor' :
> mode => 644,
> source => 'puppet:///modules/plugpc/logrotate/x10monitor',
> }
>
> }
>
>  --
> 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.google.com/d/msgid/puppet-users/e3c410eb-0415-414f-9a0f-b8695efdadb7%40googlegroups.com
> .
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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.google.com/d/msgid/puppet-users/CAF_B3dd%3DvYGY0kVbv41A5QeSepD-U4gTzdvhCAGEvYA%3Dd%3DxvAg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Understanding script process control

2014-02-04 Thread JonY

I have an issue where puppet keeps starting additional instances of a 
process even though it's already running. The 'control script' in question 
does have a 'status' command but I'm thinking that I'm not properly telling 
puppet that the process is ok.

>From the site:
The init script’s status command must return 0 if the service is running 
and a nonzero value otherwise. Ideally, these exit codes should conform to the 
LSB’s 
specification
 for 
init script status actions, but Puppet only considers the difference 
between 0 and nonzero to be relevant.

The script is exiting with 'exit 0' when the process is running and it's 
creating a .PID file for it in /var/run. If I examine 'echo $?' after 
running 'service myscript status' I see 0. Is there some other indication 
that I need? Should the script *actually* return 0? 

When the box in question boots, there are immediately two instances of the 
service running. Over time it builds up to quite a pile.

If I run the script manually it responds as I would expect. "process is 
running" and doesn't start additional instances.

puppet script:

class plugpc::local_services::x10monitor inherits plugpc::local_services
{
package
{
"x10monitor" :
ensure => "latest",
require => Package[ "mysql-server-5.1" ];
}

service
{
"x10monitor" :
ensure => "running",
enable => "true",
subscribe => Package[ "x10monitor" ],
require => [ Service[ "mysql" ], Package[ 
"x10monitor" ]];
}

file
{
'/etc/logrotate.d/x10monitor' :
mode => 644,
source => 'puppet:///modules/plugpc/logrotate/x10monitor',
}

}

-- 
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.google.com/d/msgid/puppet-users/e3c410eb-0415-414f-9a0f-b8695efdadb7%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] [JOBS] systems and automation/tooking engineers - Atlanta, GA, USA or remote in US

2014-02-04 Thread Jason Antman

Ahhh. I suppose I was just being naive and thinking that the recruiters
hadn't found out about this list yet... wishful thinking.

Thanks.

On 02/04/2014 02:04 PM, Ken Barber wrote:
> Jason,
>
> The policy afaik is still what was laid down here:
> https://groups.google.com/forum/#!msg/puppet-users/yC0TxrTd0aE/_ffh9H55ssAJ
>
> So these kind of job postings are welcome. FYI we moderate the other
> kind usually before most people see them.
>
> ken.
>
> On Tue, Feb 4, 2014 at 6:55 PM, Jason Antman  wrote:
>> CMG Technology is hiring systems and automation/tooling engineers (and
>> Python developers). We're a web shop that runs the web and mobile
>> presences for 70+ newspaper/tv/radio properties, based off of a
>> Python/Django application (supposedly the largest in production
>> anywhere) serving around 10M page views per day. The company offers
>> excellent benefits, and our workforce is largely split between Atlanta,
>> GA and full-time remotes (within the US).
>>
>> We're committed to Puppet as a technology and DevOps as a culture; we're
>> well on the road to having a fully-puppetized infrastructure both in the
>> data center and with cloud providers, we deploy application code at
>> least daily, and we're trying to do cool stuff and scale.
>>
>> We're looking for talented, passionate system engineers and
>> automation/tooling engineers. Puppet is certainly a big plus, but these
>> aren't pure-puppet roles. Our high-level projects at the moment include
>> speeding up deployments (which means everything from production-like
>> local dev VMs to work with Jenkins, CI, automated testing, and fast
>> production deploys/restarts), increasing automation of infrastructure
>> (we've still got an amount that's not puppetized, but we're working fast
>> to change that), automated testing of Puppet changes, and increasing
>> visibility into our infrastructure (graphite, logstash, puppetized
>> nagios/icinga).
>>
>> On the dev side it's all Python, and ops is partial to Python as well,
>> but we know we're too light in Ruby for how much we rely on Puppet, and
>> would like to change that. We're pretty dedicated to the DevOps culture;
>> not only does dev and ops work and play together, and work extremely
>> well as one team, but developers have the same access to our puppet git
>> repo as engineers, and a few of us engineers have pulled development
>> tickets for our main application.
>>
>> A sample of some of the tech we're working with, pulled from our kanban
>> backlog:
>> Puppet3 / PuppetDB, Python, Jenkins, Selenium, NodeMeister (our in-house
>> ENC), Postgres, Memcached, Solr4, ZooKeeper, F5 Viprion, RabbitMQ, KVM,
>> AWS, Icinga, Graphite, Logstash, git, Vagrant.
>>
>> The job descriptions, and a bit about the company and our group, are
>> available at:
>> http://cmgd-jobs.readthedocs.org/en/latest/
>>
>> Please feel free to ping me with any questions, and to pass this along
>> to anyone you know who may be interested. If you're interested, pass
>> along a resume and any other references/resources, and I'll get back to you.
>>
>> Thanks,
>> Jason Antman
>>
>> PS - I hope the community guidelines are still correct, and job postings
>> are welcome here. I've seen very few, but we're hiring multiple
>> positions (scaling out development by about 20%, and the ops/automation
>> teams likewise), so we're trying hard to find the best...
>>
>> --
>>
>> Jason Antman | Systems Engineer | CMGdigital
>> jason.ant...@coxinc.com | p: 678-645-4155
>>
>> --
>> 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.google.com/d/msgid/puppet-users/52F13795.8090904%40jasonantman.com.
>> For more options, visit https://groups.google.com/groups/opt_out.


-- 
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.google.com/d/msgid/puppet-users/52F13EDC.7030202%40jasonantman.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Port for ENC requests?

2014-02-04 Thread JonY

chown puppet:puppet /etc/puppet/ENC/ENC.log

Perl was refusing to write to the log file when run under Passenger even 
though the file was as open as I could make it. And even though the script 
worked when run via the shell - passenger still wouldn't do it.



On Tuesday, February 4, 2014 11:16:41 AM UTC-8, Jose Luis Ledesma wrote:
>
> Have you looked syslog and apache logs?
>
> BTW /tmp should be 1777, but this shouldn't be the problem.
>
> Regards,
> El 04/02/2014 20:07, "JonY" > escribió:
>
>> I'm stumped then.
>>
>> Folder is 0777. Files are 0777. 
>>
>> I'm running the p-master using Passenger in apache2 which runs as the 
>> 'puppet' account. I used this account to run the app in question without 
>> any problem. 'su - puppet -c "/tmp/test0.pl"'. 
>>
>> SELinux is in 'permissive' mode.
>>
>> What else should I look for?
>>
>> On Monday, February 3, 2014 3:25:32 PM UTC-8, John Warburton wrote:
>>>
>>> On 4 February 2014 09:00, Jon Yeargers  wrote:
>>>
 I'm trying to debug a new ENC setup. I created a short perl script to 
 output a few lines of YAML. It runs fine on the puppet server but when I 
 try it on a client I get this error:

 Warning: Error 400 on SERVER: Failed to find client.domain.org via 
 exec: Execution of the '/etc/puppet/ENC/plug0.pl client.domain.org' 
 returned 13:

>>>  
>>>
 Somewhere else I should be looking for errors? What does error 13 imply?
  
 # grep 13 /usr/include/sys/errno.h
>>> #define EACCES  13  /* Permission denied 
>>>
>>> The user running the puppet master cannot access (read/execute?) your 
>>> script. Try running it as that user from the command line
>>>
>>> John
>>>
>>  -- 
>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/ee479fec-6bd9-41b0-9f7c-0e33f362fb1b%40googlegroups.com
>> .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>

-- 
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.google.com/d/msgid/puppet-users/4cbda3cc-acba-47e4-a352-95027dd54383%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Port for ENC requests?

2014-02-04 Thread José Luis Ledesma

Have you looked syslog and apache logs?

BTW /tmp should be 1777, but this shouldn't be the problem.

Regards,
El 04/02/2014 20:07, "JonY"  escribió:

> I'm stumped then.
>
> Folder is 0777. Files are 0777.
>
> I'm running the p-master using Passenger in apache2 which runs as the
> 'puppet' account. I used this account to run the app in question without
> any problem. 'su - puppet -c "/tmp/test0.pl"'.
>
> SELinux is in 'permissive' mode.
>
> What else should I look for?
>
> On Monday, February 3, 2014 3:25:32 PM UTC-8, John Warburton wrote:
>>
>> On 4 February 2014 09:00, Jon Yeargers  wrote:
>>
>>> I'm trying to debug a new ENC setup. I created a short perl script to
>>> output a few lines of YAML. It runs fine on the puppet server but when I
>>> try it on a client I get this error:
>>>
>>> Warning: Error 400 on SERVER: Failed to find client.domain.org via
>>> exec: Execution of the '/etc/puppet/ENC/plug0.pl client.domain.org'
>>> returned 13:
>>>
>>
>>
>>> Somewhere else I should be looking for errors? What does error 13 imply?
>>>
>>> # grep 13 /usr/include/sys/errno.h
>> #define EACCES  13  /* Permission denied
>>
>> The user running the puppet master cannot access (read/execute?) your
>> script. Try running it as that user from the command line
>>
>> John
>>
>  --
> 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.google.com/d/msgid/puppet-users/ee479fec-6bd9-41b0-9f7c-0e33f362fb1b%40googlegroups.com
> .
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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.google.com/d/msgid/puppet-users/CAF_B3dfj9afBRuKdAy6Knm9LAqm9%3D%3DVo-LdTMtUztRPSu13B%2BA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Packaging Issues with PuppetDB 1.6.0 and Fedora (possible SRPMs on other distros)

2014-02-04 Thread Ryan Senior

The PuppetDB 1.6.0 RPMs for Fedora are currently broken and have been
pulled from the Fedora repos. We are working on a 1.6.1 release this
week that will include a fix for the packaging issue causing the
failure. We have also received reports of rebuilt SRPMs on other
platforms having issues. Users on Fedora should stick to 1.5.2 until
PuppetDB 1.6.1 is released. More details on the issue are below.

The issue was originally found and documented here:
https://tickets.puppetlabs.com/browse/PDB-377 (thanks John!). Part of
the Fedora RPM packaging process includes cracking open the PuppetDB
binary JAR file and manipulating some of the code included in it. The
manipulation of these class files rendered the JAR broken in
subtle ways. The feature of unpacking/repacking the JAR is mainly
useful for JVM code that wants to take advantage of native libraries.
Since PuppetDB doesn't use native dependencies, that feature of the
packaging process doesn't provide any value. Disabling it has fixed
the issue. The binary RPMs on other platforms (i.e.
Debian/Ubuntu/RHEL/CentOS) did not suffer from this issue.

-Ryan

--
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.google.com/d/msgid/puppet-users/CAGDMwd2PB7_2w-0gwmGRycWQ-RtKPPpRnJuyH%3D3G76hJ4YGk7g%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] [JOBS] systems and automation/tooking engineers - Atlanta, GA, USA or remote in US

2014-02-04 Thread Ken Barber

Jason,

The policy afaik is still what was laid down here:
https://groups.google.com/forum/#!msg/puppet-users/yC0TxrTd0aE/_ffh9H55ssAJ

So these kind of job postings are welcome. FYI we moderate the other
kind usually before most people see them.

ken.

On Tue, Feb 4, 2014 at 6:55 PM, Jason Antman  wrote:
> CMG Technology is hiring systems and automation/tooling engineers (and
> Python developers). We're a web shop that runs the web and mobile
> presences for 70+ newspaper/tv/radio properties, based off of a
> Python/Django application (supposedly the largest in production
> anywhere) serving around 10M page views per day. The company offers
> excellent benefits, and our workforce is largely split between Atlanta,
> GA and full-time remotes (within the US).
>
> We're committed to Puppet as a technology and DevOps as a culture; we're
> well on the road to having a fully-puppetized infrastructure both in the
> data center and with cloud providers, we deploy application code at
> least daily, and we're trying to do cool stuff and scale.
>
> We're looking for talented, passionate system engineers and
> automation/tooling engineers. Puppet is certainly a big plus, but these
> aren't pure-puppet roles. Our high-level projects at the moment include
> speeding up deployments (which means everything from production-like
> local dev VMs to work with Jenkins, CI, automated testing, and fast
> production deploys/restarts), increasing automation of infrastructure
> (we've still got an amount that's not puppetized, but we're working fast
> to change that), automated testing of Puppet changes, and increasing
> visibility into our infrastructure (graphite, logstash, puppetized
> nagios/icinga).
>
> On the dev side it's all Python, and ops is partial to Python as well,
> but we know we're too light in Ruby for how much we rely on Puppet, and
> would like to change that. We're pretty dedicated to the DevOps culture;
> not only does dev and ops work and play together, and work extremely
> well as one team, but developers have the same access to our puppet git
> repo as engineers, and a few of us engineers have pulled development
> tickets for our main application.
>
> A sample of some of the tech we're working with, pulled from our kanban
> backlog:
> Puppet3 / PuppetDB, Python, Jenkins, Selenium, NodeMeister (our in-house
> ENC), Postgres, Memcached, Solr4, ZooKeeper, F5 Viprion, RabbitMQ, KVM,
> AWS, Icinga, Graphite, Logstash, git, Vagrant.
>
> The job descriptions, and a bit about the company and our group, are
> available at:
> http://cmgd-jobs.readthedocs.org/en/latest/
>
> Please feel free to ping me with any questions, and to pass this along
> to anyone you know who may be interested. If you're interested, pass
> along a resume and any other references/resources, and I'll get back to you.
>
> Thanks,
> Jason Antman
>
> PS - I hope the community guidelines are still correct, and job postings
> are welcome here. I've seen very few, but we're hiring multiple
> positions (scaling out development by about 20%, and the ops/automation
> teams likewise), so we're trying hard to find the best...
>
> --
>
> Jason Antman | Systems Engineer | CMGdigital
> jason.ant...@coxinc.com | p: 678-645-4155
>
> --
> 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.google.com/d/msgid/puppet-users/52F13795.8090904%40jasonantman.com.
> For more options, visit https://groups.google.com/groups/opt_out.

-- 
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.google.com/d/msgid/puppet-users/CAE4bNTkDZTg0a3m6Fw1VXz-REgHmsb3eATyLjSL58krATMayVA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Port for ENC requests?

2014-02-04 Thread JonY

I'm stumped then.

Folder is 0777. Files are 0777. 

I'm running the p-master using Passenger in apache2 which runs as the 
'puppet' account. I used this account to run the app in question without 
any problem. 'su - puppet -c "/tmp/test0.pl"'. 

SELinux is in 'permissive' mode.

What else should I look for?

On Monday, February 3, 2014 3:25:32 PM UTC-8, John Warburton wrote:
>
> On 4 February 2014 09:00, Jon Yeargers >wrote:
>
>> I'm trying to debug a new ENC setup. I created a short perl script to 
>> output a few lines of YAML. It runs fine on the puppet server but when I 
>> try it on a client I get this error:
>>
>> Warning: Error 400 on SERVER: Failed to find client.domain.org via exec: 
>> Execution of the '/etc/puppet/ENC/plug0.pl client.domain.org' returned 
>> 13:
>>
>  
>
>> Somewhere else I should be looking for errors? What does error 13 imply?
>>  
>> # grep 13 /usr/include/sys/errno.h
> #define EACCES  13  /* Permission denied 
>
> The user running the puppet master cannot access (read/execute?) your 
> script. Try running it as that user from the command line
>
> John
>

-- 
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.google.com/d/msgid/puppet-users/ee479fec-6bd9-41b0-9f7c-0e33f362fb1b%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] [JOBS] systems and automation/tooking engineers - Atlanta, GA, USA or remote in US

2014-02-04 Thread Jason Antman

CMG Technology is hiring systems and automation/tooling engineers (and
Python developers). We're a web shop that runs the web and mobile
presences for 70+ newspaper/tv/radio properties, based off of a
Python/Django application (supposedly the largest in production
anywhere) serving around 10M page views per day. The company offers
excellent benefits, and our workforce is largely split between Atlanta,
GA and full-time remotes (within the US).

We're committed to Puppet as a technology and DevOps as a culture; we're
well on the road to having a fully-puppetized infrastructure both in the
data center and with cloud providers, we deploy application code at
least daily, and we're trying to do cool stuff and scale.

We're looking for talented, passionate system engineers and
automation/tooling engineers. Puppet is certainly a big plus, but these
aren't pure-puppet roles. Our high-level projects at the moment include
speeding up deployments (which means everything from production-like
local dev VMs to work with Jenkins, CI, automated testing, and fast
production deploys/restarts), increasing automation of infrastructure
(we've still got an amount that's not puppetized, but we're working fast
to change that), automated testing of Puppet changes, and increasing
visibility into our infrastructure (graphite, logstash, puppetized
nagios/icinga).

On the dev side it's all Python, and ops is partial to Python as well,
but we know we're too light in Ruby for how much we rely on Puppet, and
would like to change that. We're pretty dedicated to the DevOps culture;
not only does dev and ops work and play together, and work extremely
well as one team, but developers have the same access to our puppet git
repo as engineers, and a few of us engineers have pulled development
tickets for our main application.

A sample of some of the tech we're working with, pulled from our kanban
backlog:
Puppet3 / PuppetDB, Python, Jenkins, Selenium, NodeMeister (our in-house
ENC), Postgres, Memcached, Solr4, ZooKeeper, F5 Viprion, RabbitMQ, KVM,
AWS, Icinga, Graphite, Logstash, git, Vagrant.

The job descriptions, and a bit about the company and our group, are
available at:
http://cmgd-jobs.readthedocs.org/en/latest/

Please feel free to ping me with any questions, and to pass this along
to anyone you know who may be interested. If you're interested, pass
along a resume and any other references/resources, and I'll get back to you.

Thanks,
Jason Antman

PS - I hope the community guidelines are still correct, and job postings
are welcome here. I've seen very few, but we're hiring multiple
positions (scaling out development by about 20%, and the ops/automation
teams likewise), so we're trying hard to find the best...

-- 

Jason Antman | Systems Engineer | CMGdigital
jason.ant...@coxinc.com | p: 678-645-4155

-- 
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.google.com/d/msgid/puppet-users/52F13795.8090904%40jasonantman.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Pupppet syslog "unrecognised escape sequence" in string

2014-02-04 Thread Andreas Dvorak

Hi,

thank you I think I do understand it.
Here is my solution
exec{ '/bin/sed \'\#^/home#d\' /etc/auto_master > /tmp/sed.tmp.$$ && mv 
/tmp/sed.tmp.$$ /etc/auto_master'
and it works

Best regards,
Andreas

-- 
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.google.com/d/msgid/puppet-users/9d8072bf-fc8b-4890-901f-38378ada6fbb%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Enabling Inventory Support for dashboard give SSL_connect error

2014-02-04 Thread Jason Hatman


>
> Figured it out.  I assumed that since Dashboard used port 3000 that the CA 
> did as well.  I changed "ca_port" to 8140 and now it works.
>
>

-- 
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.google.com/d/msgid/puppet-users/98eb2143-db90-4fa4-94c4-459c4027a304%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] how to copy a file from a network location

2014-02-04 Thread Dan White


wget ?
curl ?

“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 Feb 04, 2014, at 10:18 AM, rstirella  wrote:


I am trying to copy a file to a desktop from a network drive with puppet but I 
keep getting errors.

Does anyone know the script to copy a file from one location to another with 
puppet?


--
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.google.com/d/msgid/puppet-users/f7ce52d8-f28c-42c9-82f1-61c428fdd4d2%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


--
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.google.com/d/msgid/puppet-users/81ca4011-a9fb-4a16-bec0-0b863811dcd3%40me.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Enabling Inventory Support for dashboard give SSL_connect error

2014-02-04 Thread Jason Hatman

*My settings.yml file looks like this, if it helps.*

cn_name: 'dashboard'

ca_crl_path: 'certs/dashboard.ca_crl.pem'

ca_certificate_path: 'certs/dashboard.ca_cert.pem'

certificate_path: 'certs/dashboard.cert.pem'

private_key_path: 'certs/dashboard.private_key.pem'

public_key_path: 'certs/dashboard.public_key.pem'

# Hostname of the certificate authority.

ca_server: 'pmaster3.orchard.fruit.com'

# Port for the certificate authority.

ca_port: 3000

# Key length for SSL certificates

key_length: 1024

enable_inventory_service: false

# Hostname of the inventory server.

inventory_server: 'puppet'

# Port for the inventory server.

inventory_port: 8140

# Set this to true to allow Dashboard to display diffs on files that

# are archived in the file bucket.

use_file_bucket_diffs: false

# Hostname of the file bucket server.

file_bucket_server: 'puppet'

# Port for the file bucket server.

file_bucket_port: 8140

# Amount of time in seconds since last report before a node is considered 
no longer reporting

no_longer_reporting_cutoff: 3600

# How many days of history to display on the "Daily Run Status" graph

daily_run_history_length: 30

use_external_node_classification: true

datetime_format: '%Y-%m-%d %H:%M %Z'

date_format: '%A, %B %e, %Y'

# Set this to the URL of an image. The image will be scaled to the 
specified dimensions.

custom_logo_url: '/images/dashboard_logo.png'

custom_logo_width: 155px

custom_logo_height: 23px

custom_logo_alt_text: 'Puppet Dashboard'

# We will be deprecating using "http://dashboard_servername/reports"; as the 
puppet master's reporturl.

# Set this to 'true' once you have changed all your puppet masters to send 
reports to

# "http://dashboard_servername/reports/upload";

disable_legacy_report_upload_url: false

# Disables the UI and controller actions for editing nodes, classes, groups 
and reports.  Report submission is still allowed

enable_read_only_mode: false

# Default number of items of each kind to display per page

nodes_per_page: 20

classes_per_page: 50

groups_per_page: 50

reports_per_page: 20

# Use this to set the time zone to something other than the default.

time_zone: 'Central Time (US & Canada)'

-- 
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.google.com/d/msgid/puppet-users/2f6d325e-6a77-437f-8a83-a557e132b81d%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Pupppet syslog "unrecognised escape sequence" in string

2014-02-04 Thread Jason Antman

Your exec resource has a double-quoted string.

1) You're not doing variable interpolation, so that should be a
single-quoted string (per the accepted style).
2) Puppet *happens* to allow "\#". The docs on Puppet string types and
escaping
(https://docs.puppetlabs.com/puppet/3/reference/lang_datatypes.html#double-quoted-strings)
clearly list the allowed escape sequences. As \# isn't one of them, you
should be doubling the leading "\" to escape it.

If you do keep that as a double-quoted string, you need to escape $ as well.

-Jason

On 02/04/2014 11:15 AM, Andreas Dvorak wrote:
> Dear all,
>
> I have several exec resources that work fine, but the puppet master
> throws a syslog message
>
> "Unrecognised escape sequence \# in file
> /data/git/simulation/modules/base_modification/manifests/only_solaris.pp
> at line 14"
>
> 14: exec{ "/bin/sed '\#^/home#d' /etc/auto_master > /tmp/sed.tmp.$$ &&
> mv /tmp/sed.tmp.$$ /etc/auto_master":
> 15:onlyif => "/bin/grep '^/home' /etc/auto_master"
> 16:  }
>
> I do not want to filter that mesage, but how can tell puppet this is
> fine or do I need to change the exec resource.
>
> Regards
> Andreas
> -- 
> 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.google.com/d/msgid/puppet-users/df83f496-54cb-4c65-9382-dd907c0393d9%40googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.


-- 
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.google.com/d/msgid/puppet-users/52F123A6.4040205%40jasonantman.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Pupppet syslog "unrecognised escape sequence" in string

2014-02-04 Thread David Schmitt

puppet is telling you that it is trying to interpret the backslash-hash
(\#) sequence in the string, but has not found a useful interpretation.
I guess that you'd like to ACTUALLY have a backslash and a has in the
string, in which case you'll need to put backslash-backslash-hash (\\#)
in there as long as you're using double quotes (").

Read more about this in the Language Reference:

http://docs.puppetlabs.com/puppet/latest/reference/lang_datatypes.html#strings

Regards, David

On 04.02.2014 17:15, Andreas Dvorak wrote:

Dear all,

I have several exec resources that work fine, but the puppet master
throws a syslog message

"Unrecognised escape sequence \# in file
/data/git/simulation/modules/base_modification/manifests/only_solaris.pp
at line 14"

14: exec{ "/bin/sed '\#^/home#d' /etc/auto_master > /tmp/sed.tmp.$$ &&
mv /tmp/sed.tmp.$$ /etc/auto_master":
15:onlyif => "/bin/grep '^/home' /etc/auto_master"
16: }

I do not want to filter that mesage, but how can tell puppet this is
fine or do I need to change the exec resource.

Regards
Andreas

--
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.google.com/d/msgid/puppet-users/df83f496-54cb-4c65-9382-dd907c0393d9%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
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.google.com/d/msgid/puppet-users/52F1233A.8080208%40dasz.at.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Pupppet syslog "unrecognised escape sequence" in string

2014-02-04 Thread Andreas Dvorak

Dear all,

I have several exec resources that work fine, but the puppet master throws 
a syslog message

"Unrecognised escape sequence \# in file 
/data/git/simulation/modules/base_modification/manifests/only_solaris.pp at 
line 14"

14: exec{ "/bin/sed '\#^/home#d' /etc/auto_master > /tmp/sed.tmp.$$ && mv 
/tmp/sed.tmp.$$ /etc/auto_master":
15:onlyif => "/bin/grep '^/home' /etc/auto_master"
16:  }

I do not want to filter that mesage, but how can tell puppet this is fine 
or do I need to change the exec resource.

Regards
Andreas

-- 
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.google.com/d/msgid/puppet-users/df83f496-54cb-4c65-9382-dd907c0393d9%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Enabling Inventory Support for dashboard give SSL_connect error

2014-02-04 Thread Jason Hatman

I too would like some insight into this problem.  I'm following the same 
instructions.  Here's my result.

root@pmaster3:/usr/share/puppet-dashboard# sudo -u puppet-dashboard rake 
cert:request

NOTE: Gem.source_index is deprecated, use Specification. It will be removed 
on or after 2011-11-01.

Gem.source_index called from 
/usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21.

config.gem: Unpacked gem rdoc-3.6.1 in vendor/gems has no specification 
file. Run 'rake gems:refresh_specs' to fix this.

config.gem: Unpacked gem json_pure-1.7.7 in vendor/gems has no 
specification file. Run 'rake gems:refresh_specs' to fix this.

config.gem: Unpacked gem rspec-rails-1.3.4 in vendor/gems has no 
specification file. Run 'rake gems:refresh_specs' to fix this.

config.gem: Unpacked gem mocha-0.9.7 in vendor/gems has no specification 
file. Run 'rake gems:refresh_specs' to fix this.

config.gem: Unpacked gem factory_girl-1.3.3 in vendor/gems has no 
specification file. Run 'rake gems:refresh_specs' to fix this.

config.gem: Unpacked gem daemons-1.0.10 in vendor/gems has no specification 
file. Run 'rake gems:refresh_specs' to fix this.

config.gem: Unpacked gem haml-3.1.2 in vendor/gems has no specification 
file. Run 'rake gems:refresh_specs' to fix this.

config.gem: Unpacked gem rspec-1.3.2 in vendor/gems has no specification 
file. Run 'rake gems:refresh_specs' to fix this.

config.gem: Unpacked gem thoughtbot-shoulda-2.10.2 in vendor/gems has no 
specification file. Run 'rake gems:refresh_specs' to fix this.

config.gem: Unpacked gem will_paginate-2.3.15 in vendor/gems has no 
specification file. Run 'rake gems:refresh_specs' to fix this.

config.gem: Unpacked gem rack-1.1.6 in vendor/gems has no specification 
file. Run 'rake gems:refresh_specs' to fix this.

config.gem: Unpacked gem sass-3.1.2 in vendor/gems has no specification 
file. Run 'rake gems:refresh_specs' to fix this.

NOTE: Gem::SourceIndex#initialize is deprecated with no replacement. It 
will be removed on or after 2011-11-01.

Gem::SourceIndex#initialize called from 
/usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/vendor_gem_source_index.rb:100.

NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. 
It will be removed on or after 2011-11-01.

Gem::SourceIndex#add_spec called from 
/usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91.

NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. 
It will be removed on or after 2011-11-01.

Gem::SourceIndex#add_spec called from 
/usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91.

NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. 
It will be removed on or after 2011-11-01.

Gem::SourceIndex#add_spec called from 
/usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91.

NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. 
It will be removed on or after 2011-11-01.

Gem::SourceIndex#add_spec called from 
/usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91.

NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. 
It will be removed on or after 2011-11-01.

Gem::SourceIndex#add_spec called from 
/usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91.

NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. 
It will be removed on or after 2011-11-01.

Gem::SourceIndex#add_spec called from 
/usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91.

NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. 
It will be removed on or after 2011-11-01.

Gem::SourceIndex#add_spec called from 
/usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91.

NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. 
It will be removed on or after 2011-11-01.

Gem::SourceIndex#add_spec called from 
/usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91.

NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. 
It will be removed on or after 2011-11-01.

Gem::SourceIndex#add_spec called from 
/usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91.

NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. 
It will be removed on or after 2011-11-01.

Gem::SourceIndex#add_spec called from 
/usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91.

NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. 
It will be removed on or after 2011-11-01.

Gem::SourceIndex#add_spec called from 
/usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91.

NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. 
It will be removed on or after 2011-11-01.

Gem::SourceIndex#add_spec called from 
/usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91.

NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. 
It will be removed on or after 2011-11-01.

Gem::SourceIndex#add_spec called from 
/usr/l

[Puppet Users] how to copy a file from a network location

2014-02-04 Thread rstirella

I am trying to copy a file to a desktop from a network drive with puppet 
but I keep getting errors.

Does anyone know the script to copy a file from one location to another 
with puppet? 

-- 
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.google.com/d/msgid/puppet-users/f7ce52d8-f28c-42c9-82f1-61c428fdd4d2%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Constructing rvalues from exported resources.

2014-02-04 Thread jcbollinger



On Tuesday, February 4, 2014 2:03:12 AM UTC-6, Krist van Besien wrote:
>
>
>
> On Wednesday, January 29, 2014 3:41:43 PM UTC+1, jcbollinger wrote:
>>
>>
>> I'm uncertain what you mean.  If "doing this" refers to enumerating the 
>> cluster members in advance, then that can only be something that you, as 
>> cluster planner, do yourself, outside the scope of Puppet (c.f. "in 
>> advance").
>>
>> If you're asking how to communicate that data to Puppet, then whatever 
>> data service is available is probably fine.  Hiera would be great for 
>> this.  With an ENC such as Foreman, you can have the ENC pass the member 
>> list to Puppet as a top-scope variable or as a parameter of one or more 
>> classes.  In that case, you may need to create a wrapper class around 
>> whatever third-party module you want to use; its role would be to pass on 
>> the ENC-provided data as module class parameters.
>>
>> If "doing this" is supposed to mean something more general, along the 
>> lines of "using Puppet to arrange my nodes into a cluster," then how best 
>> to approach that depends on a great many factors.  We have already touched 
>> on some of those: what clustering software you want to use (if any), and 
>> the extent to which cluster membership can or must be dynamic.  We can 
>> probably help you with devising manifests that will accomplish your 
>> objectives, but to do so we need more information.
>>
>>
> To give you an idea. I defined the wollowing class:
>
> class sws::services::cluster (
>
>   $control_clu_name= $sws::params::control_clu_name,
>   $control_clu_members = $sws::params::control_clu_members,
>
> ) inherits sws::params {
>
> package { 'ccs' :
>   ensure => installed,
> }
>
> class {'pacemaker::corosync':
>   cluster_name=> $control_clu_name,
>   cluster_members => $control_clu_members,
>   require => Package['ccs']
> }
>
> }
>
> (There's a lot more in there, but I cut out the not so relevant bits...)
>
> Currently this works, if I just declare the control_clu_name and 
> control_clu_members parameters in advance, and then add this class to the 
> nodes I listed in control_clu_members via Foreman.
>
> Now when I add another node to the cluster I need to do two things: Add 
> the class to the node in Foreman, and add it's fqdn to the 
> control_clu_members parameter. I was just wondering if there was a way to 
> do this last thing automatically.
>
>

Although I don't doubt that your class is applied successfully when used as 
you describe, I am less confident that it produces the results you expect.  
Specifically, I recommend you confirm that when adding a node to an 
existing, running cluster, your approach causes the other nodes to be 
updated to know about the new one.  The module appeared geared to not do 
that, but I didn't analyze it deeply enough to be certain.

As Henrik suggested, it is possible for the catalog compiler to query 
puppetdb to glean information about nodes that have already been 
configured.  If in fact I am mistaken about pre-existing nodes not being 
updated, then an approach based on such queries could do what you want.  If 
I am *not* mistaken about that, however, then your approach is 
irretrievably broken -- in that case, with the module you are currently 
using, you would need to tell Foreman what all the cluster nodes are going 
to be before you configure the first one.


John

-- 
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.google.com/d/msgid/puppet-users/a008eef1-e285-43ab-af46-d2b959fa788e%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet vs "typical" release management / change management

2014-02-04 Thread Gareth Rushgrove

On 4 February 2014 14:11, Jason Antman  wrote:
> Steve,
>
> I'll leave it up to others to answer your question more directly, as I'm not
> sure I really can - it's been a while since I worked in an ITIL shop. What I
> will say, though, since inevitably *someone* will, is that ITIL contains
> some good concepts and some bad ones. Overall, I'd never work in an ITIL
> shop again, I find it far too restrictive and slow.
>
> When you mentioned "the devops approach", are you referring to agile and
> deploying/releasing very often? Or... something else?
>
> In my opinion (and yes there are very smart people who feel otherwise) ITIL
> is a band-aid for having poor review processes, poor testing, and people who
> either don't know what they're doing or can't take responsibility. I work in
> a web shop that deploys application code about twice a day, which most of us
> consider to be painfully slow. We treat Puppet as "infrastructure as code" -
> we make a change, have a git branch peer-reviewed, deploy to a development
> server and test there (which will ideally be automated in the future, via
> both rspec and server-spec, and some tests against monitoring), assuming the
> tests pass we push to an identical test environment, and if it passes there
> too, we push to production.
>
> So, to cut short the ITIL-bashing (under the assumption that you probably
> didn't choose ITIL for your organization, and any more of it will have you
> cursing my name), if by "devops" you meant rapid deployment/release or even
> continuous deployment/release, then I'd go so far as to say it's totally in
> conflict with the low-confidence, slow-moving CAB approach of ITIL.
>

One approach here is to move towards things being defined as Standard
Change in ITIL terminology. These are basically low-risk pre-approved
changes, ie. things that you do so often that going to a CAB isn't
needed. Traditionally changes to infrastructure would be infrequent,
scary and definitely require approval. However, if you have automated
review, testing and audit tracking procedures and are releasing
changes daily then it's perfectly possible to view these as standard
changes.

Basically lean in and learn some of the terminology. Build trust and
reduce (and talk about) risk.

Gareth


> The other thing I should mention is that we're a pretty strong devops shop -
> culturally (as is the meaning of devops) and in practice. We work extremely
> closely with dev, engineers/ops are involved in all dev tickets from the
> first elaboration, ops is included on most dev code reviews and vice versa.
> That's probably a requirement to make things work smoothly as I mentioned
> above.
>
> -Jason
>
>
> On 02/04/2014 05:05 AM, Steven James wrote:
>>
>> Hi there.
>>
>> I'm look to see if anybody has any advice to share around how the
>> implementation of Puppet affects the "typical"  ITIL based release
>> management and change management processes.
>>
>> From a change perspective, I'm thinking that the whole risk thing
>> associate with the CAB for example, should get a whole lot better as a
>> result of version controlled infrastructure manifests, ability to provide
>> infrastructure code diffs, noop runs against bare metal, with the option of
>> running a few noop runs against current patch set...will probably help.
>>
>> How else does the ITIL base change process have to typically (er)
>> change...to accommodate the devops approach?
>>
>> Similar question for release management. How does the introduction of
>> Puppet typically affect the release management process?
>>
>> Any input greatly appreciated.
>>
>> SteveJames
>> --
>> 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.google.com/d/msgid/puppet-users/CAB_ORUv5NbgL-L4SattZ5y5V9G0r4BHgfVx6Pd-WVp8frHcdXg%40mail.gmail.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>
>
> --
> 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.google.com/d/msgid/puppet-users/52F0E6E9.5040309%40jasonantman.com.
>
> For more options, visit https://groups.google.com/groups/opt_out.



-- 
Gareth Rushgrove
@garethr

devopsweekly.com
morethanseven.net
garethrushgrove.com

-- 
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.google.com/d/msgid/puppet-users/CAFi_6yLTvrymqbvCAMcLMz_VbiiB7JWiqeOrpbu4wqsu9xXPBA%40mail.gmail

[Puppet Users] Re: ENC - how to set order of operations?

2014-02-04 Thread jcbollinger

On Monday, February 3, 2014 9:13:28 AM UTC-6, JonY wrote:
>
> I need to convert my resource based system to ENC.
>

That statement does not make sense.  You cannot do anything useful with 
Puppet without resources.

I suppose you may mean that you want to drop node blocks, in which you 
sometimes declare resources and resource collections, in favor of 
classifying nodes via an ENC.

> It's mostly straightforward but I'm not sure how to handle operations like 
> these: 
>
> Class['apt'] -> Package<| |>
>
>

ENCs can feed only classes (with or without parameters) and top-scope 
variables to Puppet.  You therefore have two general ways forward:

   1. Do as you said, and drop *all* node blocks in favor of ENC 
   classification.  In this case you need to wrap all resource and resource 
   collection declarations in classes.  Your ENC then specifies the 
   appropriate classes.
   2. Use node blocks together with ENC, and leave resource declarations in 
   the node blocks.  In this case Puppet must be able to match a node block to 
   every node, but that's not an onerous requirement because it can be 
   satisfied trivially via an empty 'default' node block.  In this case, yes, 
   Puppet will combine the ENC-specified and node-block-specified declarations 
   for each node, and use them all.

John

-- 
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.google.com/d/msgid/puppet-users/ea850cb2-45a0-4b41-a026-70c4e41a04ee%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Get Facter Facts for Previously installed module

2014-02-04 Thread jcbollinger

On Monday, February 3, 2014 9:34:51 AM UTC-6, Ralph Bolton wrote:
>
> Custom Providers look interesting, although I can't immediately find a 
> good example to work from (it just me, or is the puppetlabs doco weirdly 
> confusing?). I guess it just matters when the provider is evaluated - if 
> it's evaluated on first use, then I can make this work.
>
> Thanks for the suggestion - I don't suppose you've got an example handy, 
> do you?
>

Custom providers *are* interesting and useful, but they are inseparably 
coupled with custom types.  They have nothing to do with custom facts.  
Since you are trying to inform the catalog compiler generally about details 
of the target node, it's definitely a fact you want, not a custom type and 
associated provider(s).

To your original question, the behavior you describe is absolutely normal.  
A Puppet run proceeds in these general steps:

1) The agent synchronizes its local plugins with the master, including 
custom facts provided as plugins
2) The agent computes facts, and includes them in a request to the master 
for a catalog
3) The master compiles a catalog for the agent based on its manifests and 
the provided facts, and returns it
4) The agent applies the catalog (which may involve additional requests to 
the master for 'source'd files)

Note in particular that synchronizing custom fact plugins is not part of 
applying the catalog; the relative timing of this operation is completely 
unaffected by anything in any of your manifests.

As you can see, it's a bit infelicitous to use a custom fact that depends 
on a separate custom binary.  Installation and update of such a binary via 
Puppet will always trail computation of the fact value, and you have to 
somehow account for that.  If you can put the whole value computation 
directly into your fact plugin then you will be better off.

If you cannot avoid your fact relying on an external custom binary, then 
you might consider overcoming the need to install that binary via Puppet.  
For example, you might put it on a network filesystem from which clients 
could run it without any local installation.  If the binary is not expected 
to change during the lifetime of a system (and maybe even otherwise) then 
you could install it as part of the initial provisioning process.

If you want to manage the binary via Puppet, then you need to accept that 
two catalog runs will be required to sync systems when they are first 
installed and when the binary needs to be updated.  There are various ways 
to dress that up to better suit your specific objectives, but that's the 
bottom line.

John

-- 
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.google.com/d/msgid/puppet-users/fbce8335-d584-4bd3-8a18-14c2a96e3a87%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet vs "typical" release management / change management

2014-02-04 Thread Jason Antman

Steve,

I'll leave it up to others to answer your question more directly, as I'm
not sure I really can - it's been a while since I worked in an ITIL
shop. What I will say, though, since inevitably *someone* will, is that
ITIL contains some good concepts and some bad ones. Overall, I'd never
work in an ITIL shop again, I find it far too restrictive and slow.

When you mentioned "the devops approach", are you referring to agile and
deploying/releasing very often? Or... something else?

In my opinion (and yes there are very smart people who feel otherwise)
ITIL is a band-aid for having poor review processes, poor testing, and
people who either don't know what they're doing or can't take
responsibility. I work in a web shop that deploys application code about
twice a day, which most of us consider to be painfully slow. We treat
Puppet as "infrastructure as code" - we make a change, have a git branch
peer-reviewed, deploy to a development server and test there (which will
ideally be automated in the future, via both rspec and server-spec, and
some tests against monitoring), assuming the tests pass we push to an
identical test environment, and if it passes there too, we push to
production.

So, to cut short the ITIL-bashing (under the assumption that you
probably didn't choose ITIL for your organization, and any more of it
will have you cursing my name), if by "devops" you meant rapid
deployment/release or even continuous deployment/release, then I'd go so
far as to say it's totally in conflict with the low-confidence,
slow-moving CAB approach of ITIL.

The other thing I should mention is that we're a pretty strong devops
shop - culturally (as is the meaning of devops) and in practice. We work
extremely closely with dev, engineers/ops are involved in all dev
tickets from the first elaboration, ops is included on most dev code
reviews and vice versa. That's probably a requirement to make things
work smoothly as I mentioned above.

-Jason

On 02/04/2014 05:05 AM, Steven James wrote:

Hi there.

I'm look to see if anybody has any advice to share around how the
implementation of Puppet affects the "typical" ITIL based release
management and change management processes.

From a change perspective, I'm thinking that the whole risk thing
associate with the CAB for example, should get a whole lot better as a
result of version controlled infrastructure manifests, ability to
provide infrastructure code diffs, noop runs against bare metal, with
the option of running a few noop runs against current patch set...will
probably help.

How else does the ITIL base change process have to typically (er)
change...to accommodate the devops approach?

Similar question for release management. How does the introduction of
Puppet typically affect the release management process?

Any input greatly appreciated.

SteveJames
--
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.google.com/d/msgid/puppet-users/CAB_ORUv5NbgL-L4SattZ5y5V9G0r4BHgfVx6Pd-WVp8frHcdXg%40mail.gmail.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
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.google.com/d/msgid/puppet-users/52F0E6E9.5040309%40jasonantman.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] ENC - how to set order of operations?

2014-02-04 Thread Jason Antman

Disregard some of what I said. Sorry for the confusion. Stages can only
be used on classes not individual resources, so that won't work as
cleanly with forge modules (or anything that isn't specifically setup to
use stages).

On 02/04/2014 07:43 AM, Jason Antman wrote:

Jon,

I've been using ENCs for quite a while, and have never used them with
site manifests (or any other manifests outside of modules). At the
moment, when I do things like that, I either do them inside a class
(i.e. put what you have in a wrapper class), or use "require" on all
resource instances.

My plan in the near future, which AFAIK is at least close to best
practice and is (at least in my opinion) the most elegant and "right"
way to do this, the is to use run stages to handle all Package
resources in a "setup" stage, and then add a stage before that that
handles repository setup. Though this will probably also require a
site.pp to setup the stage for all Package resources.

For more information on run stages, see:
- http://docs.puppetlabs.com/puppet/3/reference/lang_run_stages.html
- the default stages setup by puppetlabs-stdlib -
https://github.com/puppetlabs/puppetlabs-stdlib/blob/master/manifests/stages.pp

-Jason

On 02/03/2014 01:51 PM, Jon Yeargers wrote:
So if a given node is named in both an ENC and the site manifest...
it will use both? IE If I have some definitions that I want to send
everywhere and others that are node specific.. I can use both types
of node entries?

On Monday, February 3, 2014 10:14:52 AM UTC-8, Dan Bode wrote:

On Mon, Feb 3, 2014 at 9:45 AM, Jon Yeargers > wrote:

Right. So how would I declare this dependency setup if I stop
using node files?

Even if you use an ENC, Puppet will still consult your site
manifest, so using an ENC does not preclude you from setting
resource dependencies via collection in your site manifest.

On Monday, February 3, 2014 9:33:40 AM UTC-8, Jose Luis
Ledesma wrote:

Perhaps I'm confused but an ENC stores node definition
and not collector nor dependencies...doesn't it?

Regards,

El 03/02/2014 16:13, "Jon Yeargers"
escribió:

I need to convert my resource based system to ENC.
It's mostly straightforward but I'm not sure how to
handle operations like these:

|Class['apt'] -> Package<| |>|

--
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...@googlegroups.com.

To view this discussion on the web visit

https://groups.google.com/d/msgid/puppet-users/b6324c21-3725-480d-b2ab-33ee48577ba6%40googlegroups.com

.
For more options, visit
https://groups.google.com/groups/opt_out
.

--
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...@googlegroups.com
.
To view this discussion on the web visit

https://groups.google.com/d/msgid/puppet-users/89c4d5d6-1f79-454c-8d22-1e1fb9ce15d6%40googlegroups.com

For more options, visit
https://groups.google.com/groups/opt_out
.

--
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.google.com/d/msgid/puppet-users/d0568d5a-450f-45e3-9d4e-7d85e2e07d60%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
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.google.com/d/msgid/puppet-users/52F0E059.7000602%40jasonantman.com.

For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] ENC - how to set order of operations?

2014-02-04 Thread Jason Antman

Jon,

My plan in the near future, which AFAIK is at least close to best
practice and is (at least in my opinion) the most elegant and "right"
way to do this, the is to use run stages to handle all Package resources
in a "setup" stage, and then add a stage before that that handles
repository setup. Though this will probably also require a site.pp to
setup the stage for all Package resources.

-Jason

On 02/03/2014 01:51 PM, Jon Yeargers wrote:
So if a given node is named in both an ENC and the site manifest... it
will use both? IE If I have some definitions that I want to send
everywhere and others that are node specific.. I can use both types of
node entries?

On Monday, February 3, 2014 10:14:52 AM UTC-8, Dan Bode wrote:

On Mon, Feb 3, 2014 at 9:45 AM, Jon Yeargers > wrote:

Right. So how would I declare this dependency setup if I stop
using node files?

Even if you use an ENC, Puppet will still consult your site
manifest, so using an ENC does not preclude you from setting
resource dependencies via collection in your site manifest.

On Monday, February 3, 2014 9:33:40 AM UTC-8, Jose Luis
Ledesma wrote:

Perhaps I'm confused but an ENC stores node definition
and not collector nor dependencies...doesn't it?

Regards,

El 03/02/2014 16:13, "Jon Yeargers"
escribió:

I need to convert my resource based system to ENC.
It's mostly straightforward but I'm not sure how to
handle operations like these:

|Class['apt'] -> Package<| |>|

--
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...@googlegroups.com.

To view this discussion on the web visit

https://groups.google.com/d/msgid/puppet-users/b6324c21-3725-480d-b2ab-33ee48577ba6%40googlegroups.com

.
For more options, visit
https://groups.google.com/groups/opt_out
.

--
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...@googlegroups.com
.
To view this discussion on the web visit

https://groups.google.com/d/msgid/puppet-users/89c4d5d6-1f79-454c-8d22-1e1fb9ce15d6%40googlegroups.com

For more options, visit
https://groups.google.com/groups/opt_out
.

--
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.google.com/d/msgid/puppet-users/d0568d5a-450f-45e3-9d4e-7d85e2e07d60%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
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.google.com/d/msgid/puppet-users/52F0E059.7000602%40jasonantman.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet vs "typical" release management / change management

2014-02-04 Thread José Luis Ledesma

We are currently setting up puppet in our infrastructure. We have a very
enforcing change management process.

Moreover, is impossible to make changes in all the development servers at
the same time, so using the standard Dev, test, pre, pro environments is
not an options.

We have decided to work in noop mode, and set environments by version,
I.e., our first initial configuration is environment v1. All new servers
will be provisioned in v1.

Meanwhile we will create v2. And we will start to move servers from v1 to
v2 using the change management process.
I don't know if there is a better approach to this problem.

Regards,
El 04/02/2014 11:05, "Steven James" 
escribió:

> Hi there.
>
> I'm look to see if anybody has any advice to share around how the
> implementation of Puppet affects the "typical"  ITIL based release
> management and change management processes.
>
> From a change perspective, I'm thinking that the whole risk thing
> associate with the CAB for example, should get a whole lot better as a
> result of version controlled infrastructure manifests, ability to provide
> infrastructure code diffs, noop runs against bare metal, with the option of
> running a few noop runs against current patch set...will probably help.
>
> How else does the ITIL base change process have to typically (er)
> change...to accommodate the devops approach?
>
> Similar question for release management. How does the introduction of
> Puppet typically affect the release management process?
>
> Any input greatly appreciated.
>
> SteveJames
>
> --
> 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.google.com/d/msgid/puppet-users/CAB_ORUv5NbgL-L4SattZ5y5V9G0r4BHgfVx6Pd-WVp8frHcdXg%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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.google.com/d/msgid/puppet-users/CAF_B3df_1os8P3BBRLdXg10yK%2BL7YJKfCnHf6rMRzQbaU-Q8-w%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Puppet Enterprise Answers file install and Policy based autosign

2014-02-04 Thread Adam Clark

HI Eric,
  Thanks for the reply.  I'm using PE 3.3.1 with naive autosigning which 
works well, I just assume policy based was working too. 
I'm new to Puppet and just doing some proof of concept work.

One thing I haven't got a good grip on is when does facter go out and 
gather the facts?  Can it gather them independently of or puppet agent 
being run?  Are they available before puppet agent is run for the first 
time?
I can't really answer this question as puppet is always run as part of the 
install script.

What I would like to do is this:
* Create a website in which takes request that have a vmware uuid (or ec2 
instance id) and certname and returns a csr_attributes.yaml file with an 
autogenerated PSK
   * the website stores all of this in a DB with a timestamp so I can age 
them out.
* Create an autosign script that validates a CSR against the DB and the 
cloud provider

My puppet bootstrap process is:
1 update system
2 download PE tarball and answers file
3 extract tarball
4 run installer with anwsers files

What would be great is if there was an empty hooks directory that could 
contain some well-known named scripts that are run at certain times. 
 pre_agent.sh or something could be downloaded between steps 3 and 4 and 
placed into the hooks directory.
This would allow me to use facter post install, but pre-agent run to get my 
data.

What do you thing?

Adam

On Monday, February 3, 2014 12:20:19 PM UTC+11, Adam Clark wrote:
>
> Hi all,
>   I am trying to proof of concept an automated install of Puppet 
> Enterprise using policy based autosign.
>
> I have read the following documents and understand what I need to do
>
> http://docs.puppetlabs.com/puppet/latest/reference/ssl_autosign.html#policy-based-autosigning
>
> http://docs.puppetlabs.com/puppet/latest/reference/ssl_attributes_extensions.html
>
> I would like to include some vmware attributes as extensions for 
> verification.  These attributes are identified by facter.
>
> The problem arises in that the automated installer creates and attempts to 
> contact the master as part of the installer operation.
> I need to interrupt the installer and update the csr_attributes.yaml file 
> prior to the CSR is created.
>
> I can't create the file prior to PE install as I need facter.
>
> Is there a way to break this chicken/egg situation?
>
> Cheers
>
> Adam
>

-- 
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.google.com/d/msgid/puppet-users/17014f3d-0591-4512-9d24-0605d96735f7%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: puppet jobs list?

2014-02-04 Thread dilippanwar

Hi Jacob,

I am a Puppet Developer and developed few Puppet modules. I am looking for 
a change. It would be nice if you can share the JD. Also , I am a bit 
doubtful about the location. I am Indian citizen and currently working with 
Dell India. 

On Saturday, February 1, 2014 8:44:09 PM UTC+5:30, Jason Antman wrote:
>
> Is there a puppet jobs list or board anywhere? (not jobs at PL, jobs 
> dealing with Puppet) 
>
> If not, where would you advertise/post (or look, I guess) for engineers 
> with strong puppet skills, both on the usage/admin side, and skilled 
> ruby devs (preferably with some Puppet experience)? 
>
> We'er hiring, and having abysmal luck with wherever our internal and 
> external recruiters have posted. 
>
> Thanks for any tips/ideas, 
> Jason 
>
> -- 
>
> Jason Antman | Systems Engineer | CMGdigital - Atlanta, GA, USA 
> jason@coxinc.com  | p: 678-645-4155 
>
>
>

-- 
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.google.com/d/msgid/puppet-users/f50bebed-9441-41c4-9e84-8ea2c565e861%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet vs "typical" release management / change management

2014-02-04 Thread Steven James

Hi there.

I'm look to see if anybody has any advice to share around how the
implementation of Puppet affects the "typical"  ITIL based release
management and change management processes.

>From a change perspective, I'm thinking that the whole risk thing associate
with the CAB for example, should get a whole lot better as a result of
version controlled infrastructure manifests, ability to provide
infrastructure code diffs, noop runs against bare metal, with the option of
running a few noop runs against current patch set...will probably help.

How else does the ITIL base change process have to typically (er)
change...to accommodate the devops approach?

Similar question for release management. How does the introduction of
Puppet typically affect the release management process?

Any input greatly appreciated.

SteveJames

-- 
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.google.com/d/msgid/puppet-users/CAB_ORUv5NbgL-L4SattZ5y5V9G0r4BHgfVx6Pd-WVp8frHcdXg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Constructing rvalues from exported resources.

2014-02-04 Thread Krist van Besien



On Wednesday, January 29, 2014 3:41:43 PM UTC+1, jcbollinger wrote:
>
>
> I'm uncertain what you mean.  If "doing this" refers to enumerating the 
> cluster members in advance, then that can only be something that you, as 
> cluster planner, do yourself, outside the scope of Puppet (c.f. "in 
> advance").
>
> If you're asking how to communicate that data to Puppet, then whatever 
> data service is available is probably fine.  Hiera would be great for 
> this.  With an ENC such as Foreman, you can have the ENC pass the member 
> list to Puppet as a top-scope variable or as a parameter of one or more 
> classes.  In that case, you may need to create a wrapper class around 
> whatever third-party module you want to use; its role would be to pass on 
> the ENC-provided data as module class parameters.
>
> If "doing this" is supposed to mean something more general, along the 
> lines of "using Puppet to arrange my nodes into a cluster," then how best 
> to approach that depends on a great many factors.  We have already touched 
> on some of those: what clustering software you want to use (if any), and 
> the extent to which cluster membership can or must be dynamic.  We can 
> probably help you with devising manifests that will accomplish your 
> objectives, but to do so we need more information.
>
>
To give you an idea. I defined the wollowing class:

class sws::services::cluster (

  $control_clu_name= $sws::params::control_clu_name,
  $control_clu_members = $sws::params::control_clu_members,

) inherits sws::params {

package { 'ccs' :
  ensure => installed,
}

class {'pacemaker::corosync':
  cluster_name=> $control_clu_name,
  cluster_members => $control_clu_members,
  require => Package['ccs']
}

}

(There's a lot more in there, but I cut out the not so relevant bits...)

Currently this works, if I just declare the control_clu_name and 
control_clu_members parameters in advance, and then add this class to the 
nodes I listed in control_clu_members via Foreman.

Now when I add another node to the cluster I need to do two things: Add the 
class to the node in Foreman, and add it's fqdn to the control_clu_members 
parameter. I was just wondering if there was a way to do this last thing 
automatically.

Krist




 

-- 
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.google.com/d/msgid/puppet-users/b451c26d-7f58-4d00-b9a6-4c54e03f9177%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Slides of the talk TDD and puppet a gave today in Ghent, cfgmgmtcamp.eu

[Puppet Users] Re: [Puppet-dev] Slides of the talk TDD and puppet a gave today in Ghent, cfgmgmtcamp.eu

[Puppet Users] Slides of the talk TDD and puppet a gave today in Ghent, cfgmgmtcamp.eu

Re: [Puppet Users] Understanding script process control

Re: [Puppet Users] Understanding script process control

[Puppet Users] Understanding script process control

Re: [Puppet Users] [JOBS] systems and automation/tooking engineers - Atlanta, GA, USA or remote in US

Re: [Puppet Users] Port for ENC requests?

Re: [Puppet Users] Port for ENC requests?

[Puppet Users] Packaging Issues with PuppetDB 1.6.0 and Fedora (possible SRPMs on other distros)

Re: [Puppet Users] [JOBS] systems and automation/tooking engineers - Atlanta, GA, USA or remote in US

Re: [Puppet Users] Port for ENC requests?

[Puppet Users] [JOBS] systems and automation/tooking engineers - Atlanta, GA, USA or remote in US

Re: [Puppet Users] Pupppet syslog "unrecognised escape sequence" in string

[Puppet Users] Re: Enabling Inventory Support for dashboard give SSL_connect error

Re: [Puppet Users] how to copy a file from a network location

[Puppet Users] Re: Enabling Inventory Support for dashboard give SSL_connect error

Re: [Puppet Users] Pupppet syslog "unrecognised escape sequence" in string

Re: [Puppet Users] Pupppet syslog "unrecognised escape sequence" in string

[Puppet Users] Pupppet syslog "unrecognised escape sequence" in string

[Puppet Users] Re: Enabling Inventory Support for dashboard give SSL_connect error

[Puppet Users] how to copy a file from a network location

[Puppet Users] Re: Constructing rvalues from exported resources.

Re: [Puppet Users] Puppet vs "typical" release management / change management

[Puppet Users] Re: ENC - how to set order of operations?

Re: [Puppet Users] Get Facter Facts for Previously installed module

Re: [Puppet Users] Puppet vs "typical" release management / change management

Re: [Puppet Users] ENC - how to set order of operations?

Re: [Puppet Users] ENC - how to set order of operations?

Re: [Puppet Users] Puppet vs "typical" release management / change management

[Puppet Users] Re: Puppet Enterprise Answers file install and Policy based autosign

[Puppet Users] Re: puppet jobs list?

[Puppet Users] Puppet vs "typical" release management / change management

[Puppet Users] Re: Constructing rvalues from exported resources.

34 matches

Site Navigation

Mail list logo

Footer information