I found solution:
---
environment: development
classes:
php:
source_dir: "${domain}"
init.pp
class php (
$source_dir = params_lookup( 'source_dir' ),
) {
$conf = regsubst($php::source_dir, '\$\{', '#{', 'G')
$conf1 = inline_template("<%= %Q($php::conf) %>"
no
Hi Justin,
Many thanks for your reply. mine goes inline.
On Saturday, March 16, 2013 at 11:23 PM, Justin Stoller wrote:
> Hi Frank -
>
> On Sat, Mar 16, 2013 at 11:03 AM, ureal frank (mailto:urealfr...@gmail.com)> wrote:
> > Hi,
> >
> > I'm trying to setup a Puppet 3.1.1 (master) un
Hi Justin,
Many thanks for your reply. mine goes inline.
On Saturday, March 16, 2013 at 11:23 PM, Justin Stoller wrote:
> Hi Frank -
>
> On Sat, Mar 16, 2013 at 11:03 AM, ureal frank (mailto:urealfr...@gmail.com)> wrote:
> > Hi,
> >
> > I'm trying to setup a Puppet 3.1.1 (master) un
Hi Kirk,
Sorry, I've only just noticed this thread. I've also experienced the same
problem. I've commented on this issue (although it might not be the correct
bug after all, since it's not quite the same problem):
https://projects.puppetlabs.com/issues/18812#note-1
It would be great to disable
you can try 'puppet agent --debug --noop --no-daemonize' to see more
message.
On Fri, Mar 15, 2013 at 11:45 AM, 朱秀龙 wrote:
> First I run puppet master with default webserver webrick, and it work
> well, I have a test module, and when I make any changes to this module,
> when executing puppet ag
puppet working well on centos6 with SELinux=enforce.
On Thu, Mar 14, 2013 at 11:26 PM, Aaron Grewell wrote:
> Do you have selinux in enforcing mode? If so, try setting it to permissive
> mode and see if it starts working.
> On Mar 14, 2013 8:09 AM, "Mike Canty" wrote:
>
>> I am running Centos
Hey Hoof,
did you ever get to the bottom of how to query and print certain facts
about your puppet clients from the command line ?
On Saturday, January 19, 2013 2:21:30 PM UTC+10, Hoof Hearted wrote:
>
> To sort of answer my own question (since it's cached in groups.google.com)
> .. I know cur
I think what you are doing will work, but calling the resource with a
require rather than including it as another class may be more elegant.
Something like:
class hadoop::usr ($usr_name = 'hadoop', $hashed_pw = undef) {
package {'libshadow-ruby1.8':
ensure => installed,
}
group { $usr_name:
ensu
I've created cloudstack_resources as a module, have setup the
transport.yaml and can successfully run "puppet resource
cloudstack_instance" against my cloudstack environment.
The following cloudstack_instance files have been created
/var/lib/puppet/lib/puppet/provider/cloudstack_instance
/var/
I have added cloudstack_resources as a module, created the transport.yaml
and can successfully query my cloudstack environment resources eg "puppet
resource cloudstack_instance"
I have got the following files created from the module.
/var/lib/puppet/lib/puppet/provider/cloudstack_instance
/var/
On Sat, Mar 16, 2013 at 10:08 PM, Nick Wales wrote:
> I've created cloudstack_resources as a module, have setup the
> transport.yaml and can successfully run "puppet resource
> cloudstack_instance" against my cloudstack environment.
>
> The following cloudstack_instance files have been created
>
Hi..
Am still getting the same problem..actually..the certificate is not getting
generated in the agent..then only it is transferred to master for the
signing right?? So..when an trying to find the certificates in master, it
is showing.. couldnot call list: header too long error.
On Friday,
On Mon, Mar 18, 2013 at 12:10 PM, yarlagadda ramya wrote:
> Hi..
>
> Am still getting the same problem..actually..the certificate is not
> getting generated in the agent..then only it is transferred to master for
> the signing right?? So..when an trying to find the certificates in master,
> it is
13 matches
Mail list logo
