Hi Peter,
On 04 Aug 2015, at 21:37, Peter Berghold wrote:
> Is there a newer set of documents on doing Spec testing of Puppet modules
> than this link?
> https://puppetlabs.com/blog/the-next-generation-of-puppet-module-testing
>
> I am running into a brick wall getting this to work so I have
On 4 August 2015 at 20:37, Peter Berghold wrote:
> Is there a newer set of documents on doing Spec testing of Puppet modules
> than this link?
> https://puppetlabs.com/blog/the-next-generation-of-puppet-module-testing
>
> I am running into a brick wall getting this to work so I have to assume I'm
Hi,
I'm updating an existing Puppet module so that I can use it with Hiera.
The node yaml files contains the following
selinux::mode: 'enforcing'
selinux::booleans:
'httpd_can_network_connect':
ensure: true
'httpd_setrlimit':
ensure: true
I can get the lookup to work using the follo
- Original Message -
> From: "Alexander Dacre"
> To: "puppet-users"
> Sent: Wednesday, August 5, 2015 10:51:24 AM
> Subject: [Puppet Users] hiera behaviour
> Hi,
>
> I'm updating an existing Puppet module so that I can use it with Hiera.
>
> The node yaml files contains the following
A, that makes sense.
Thank you!
On Wednesday, August 5, 2015 at 10:54:45 AM UTC+1, R.I. Pienaar wrote:
>
>
>
> - Original Message -
> > From: "Alexander Dacre" >
> > To: "puppet-users" >
> > Sent: Wednesday, August 5, 2015 10:51:24 AM
> > Subject: [Puppet Users] hiera behaviour
>
Hello guys,
I am trying to specify in the Hiera file which website should be a CMS like
wordpress and which should just be a static website, however, doesn't
matter what value I am having in the Hiera, my code always resolves to
false. It is this a bug or I am doing something wrong?
Below is t
- Original Message -
> From: "Sergiu Cornea"
> To: "puppet-users"
> Sent: Wednesday, August 5, 2015 11:41:38 AM
> Subject: [Puppet Users] Hiera lookup
> Hello guys,
>
> I am trying to specify in the Hiera file which website should be a CMS like
> wordpress and which should just be a s
- Original Message -
> From: "Sergiu Cornea"
> To: "puppet-users"
> Sent: Wednesday, August 5, 2015 11:41:38 AM
> Subject: [Puppet Users] Hiera lookup
> Hello guys,
>
> I am trying to specify in the Hiera file which website should be a CMS like
> wordpress and which should just be a s
Oh I beg your pardon, typo mistake yes it should be $static instead of $cms
On Wednesday, 5 August 2015 11:45:18 UTC+1, R.I. Pienaar wrote:
>
>
>
> - Original Message -
> > From: "Sergiu Cornea" >
> > To: "puppet-users" >
> > Sent: Wednesday, August 5, 2015 11:41:38 AM
> > Subject: [
Hi,
I'm trying to take a new version of a custom type into use, but keep
getting the following error message when doing an agent run:
"Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: Invalid parameter seconds on Wait_for[40 seconds] at
/etc/puppet/environments/developme
Am 05.08.2015 um 13:33 schrieb Dirk Heinrichs:
> I've already restarted the puppetserver process on the master as well
> as the agent.
Nevermind, another server restart seems to have fixed the problem.
Bye...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recomm
Hi,
I'm going through an initial deployment of Puppet and was looking to use
hiera as much as possible, but it seems that many existing modules do not
have hiera support.
The question I have is, is it 'OK' to have some bits of configuration for a
node defined in hiera, and others in site.pp?
Hi Alexander,
If you use the roles and profiles design pattern [0] then as suggested
at [1], your profile class could look up the required parameters from
hiera, do any validation required on it, then pass that data in as
standard class parameters.
Regards,
Matt.
[0] http://www.craigdunn.org/20
Hi,
I have tried the solution that you've proposed but with no luck :( now it
is complaining that couldn't find any 'cms' item in the hiera file.
Also, I am running Puppet 3.7 (master & agent) on CentOS 6.5
Thank you,
Regards,
Sergiu
On Wednesday, 5 August 2015 11:47:06 UTC+1, R.I. Pienaar wr
Hi,
I want to write a type/provider for Sun Grid Engine/Open
Grid Scheduler/etc. configuration.
The configuration is (for the most part) managed by a pair
of commands, for example "qconf -sc" will show ("s") the
"complex" configuration, "qconf -mc" will invoke an editor
to modify ("m") it, and fo
I've got something similar I built a while ago (and need to update again
since I'm back in the Puppet world).
Magnum: https://github.com/tehmaspc/magnum
It will help you create a new module dir with a bunch of puppet tools setup
for you - including rspec-puppet for spec testing and serverspec f
See for example our openldap
module:
https://github.com/camptocamp/puppet-openldap/blob/master/lib/puppet/provider/openldap_database/olc.rb
On Wednesday, August 5, 2015 at 4:20:17 PM UTC+2, Tim Landscheidt wrote:
>
> Hi,
>
> I want to write a type/provider for Sun Grid Engine/Open
> Grid S
Hi Julio,
You may have better luck getting questions about PE answered on the PE
specific mailing
list: https://groups.google.com/a/puppetlabs.com/forum/#!forum/pe-users
For this particular issue, there's no way to add a component after
installation, I'm afraid. I'd follow the directions to ba
On 8/4/15 3:37 PM, Peter Berghold wrote:
> Is there a newer set of documents on doing Spec testing of Puppet
> modules than this link?
> https://puppetlabs.com/blog/the-next-generation-of-puppet-module-testing
>
> I am running into a brick wall getting this to work so I have to assume
> I'm doin
I have a problem where a virtual resource has, in an early run, got the
wrong value. I've fixed the manifest so that the virtual resource gets the
correct values and I've rerun Puppet on the node that populates the virtual
resource. However when it is instantiated it still gets the old value.
I
On 5 Aug 2015 19:10, "Steve Wray" wrote:
>
> I have a problem where a virtual resource has, in an early run, got the
wrong value. I've fixed the manifest so that the virtual resource gets the
correct values and I've rerun Puppet on the node that populates the virtual
resource. However when it is i
Oh thanks, that worked.
I guess I was confused with the semantics of 'clean' and 'deactivate' and
thought 'deactivate' would... deactivate the node not just 'clean' out its
virtual resources :)
It would be nice if there was a curl interface for puppetdb to delete
specific virtual resources! S
I am facing issues with path of customs facts and with forge modules in
the latest PE 2015.2 version of puppet.
Custom facts are located at : /var/opt/lib/pe-puppet/lib/facter/
Common forge modules are located at :
/etc/puppetlabs/puppet/modules/production/modules
But I keep getting below
On Wed, Aug 5, 2015 at 3:11 PM, Maneesh M P wrote:
> I am facing issues with path of customs facts and with forge modules in
> the latest PE 2015.2 version of puppet.
>
> Custom facts are located at : /var/opt/lib/pe-puppet/lib/facter/
> Common forge modules are located at :
> /etc/puppetlabs/p
24 matches
Mail list logo
