Re: [Puppet Users] Re: Importing declarations into node/class scope

2013-09-08 Thread Stepan Seycek
Hi John,

thanks for your reply. Unfortunately that does not solve my actual problem.
I want to avoid maintaining multiple vhost entries inside one file. Instead
I want to be able to add a vhost by simply adding one file dedicated to
that vhost to a directory. This would allow me to easily integrate puppet
with a tool that rolls out whole application stacks including the vhosts.

Regards,
Stepan





On Fri, Sep 6, 2013 at 3:16 PM, jcbollinger wrote:

>
>
> On Friday, September 6, 2013 1:48:45 AM UTC-5, Stepan Seycek wrote:
>>
>> Hello Puppet Users,
>>
>> I am trying to find a solution for the following use case:
>>
>> On a web server I want to manage many virtual hosts. Instead of declaring
>> all these hosts inside one single class (and therefore file) I would prefer
>> to have one vhost declaration per file and then import the declarations
>> from all those files into the scope of the node or a class. I know that the
>> import statement will not work for me but maybe someone here has a solution
>> for  this.
>>
>>
>
> The most direct implementation of what you ask would be to create a
> separate class for each vhost, and then 'include' them all into a class or
> node.
>
> Alternatively, if the vhost parameters are sufficiently similar, then you
> can use an array resource title, possibly with a wrapper defined type, to
> declare all the vhosts compactly in one place:
>
> site::vhost_wrapper { [
>   'vhost1',
>   'vhost2',
>   'vhost3',
>   ...
> ]:
> # parameters as needed
>  }
>
>
> 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 post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.
> 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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.


[Puppet Users] Interface for view puppet reports

2013-09-08 Thread Ankit Mittal
Dear All,

Please give the other interfaces name that can be user instead of 
puppetdashborad for viewing the puppet reports.
I want a interface to see the puppet reports and i don't have MySql 
database also.


Thanks

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [Puppet Users] Puppet Forge max upload size?

2013-09-08 Thread Vamsee Kanakala
On Sep 08 11:23, William Van Hevelingen wrote:
> Usually the module is responsible for downloading external dependencies.
> You should add some execs to download the jar files rather than bundling
> the jar files with the module.
> 


Thanks William, somebody on IRC also suggested the same, so I used
exec+wget to download the files. The module is just about 250kb now :-)


Vamsee.

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.


[Puppet Users] Run a build module on first logon for new puppet clients

2013-09-08 Thread kdo
Hey All,

I have been wondering how it might be possible to run a specific build 
module when a puppet client signs in for the first time after being built. 
So I guess the puppet master would need to be run in auto sign in mode and 
then have a specific build module applied, ideally just once. Anyone looked 
into this before ?

this build module is used to configure a server from start to finish at 
build time only and is the removed. this would remove an additional step in 
our build process




-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [Puppet Users] migrating to puppetdb

2013-09-08 Thread Ken Barber
> Thats strange its working fine for me. What version of Puppet?
>
> [master]
>   storeconfigs = true
>   storeconfigs_backend = puppetdb

Those settings are for PuppetDB, the problem specifically is in the
usage of the 'storeconfigs' face - which at the point of migration
should be using the legacy activerecord storeconfigs settings, not the
newer PuppetDB settings. Are sure you're talking about the same thing
here?

ken.

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [Puppet Users] Puppet Forge max upload size?

2013-09-08 Thread William Van Hevelingen
Usually the module is responsible for downloading external dependencies.
You should add some execs to download the jar files rather than bundling
the jar files with the module.

Cheers,
William


On Wed, Sep 4, 2013 at 11:27 PM,  wrote:

> Hello,
>
> Can somebody here pass on the question to puppetforge maintainers please?
> I'm trying to upload a new release of my module which is about 25MB, but
> I'm getting an nginx error saying the size is too large. But the default
> install case for my module needs the bunch of jar files that come along
> with the stable release of the original software (solr). Can somebody tell
> me what is the max allowed size please? Is there any way to raise the
> upload size limit?
>
> Thanks,
> Vamsee.
>
> --
> 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 post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.
> For more options, visit https://groups.google.com/groups/opt_out.
>



-- 
Thanks,
William

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [Puppet Users] migrating to puppetdb

2013-09-08 Thread William Van Hevelingen
Thats strange its working fine for me. What version of Puppet?

[master]
  storeconfigs = true
  storeconfigs_backend = puppetdb



On Fri, Sep 6, 2013 at 6:55 AM, Darin Perusich  wrote:

> Hi Ken,
>
> Adding the storeconfigs setting to [main] got things working. This
> sounds like an bug/issue to me, or at a minimum something that needs
> to be specified int he documentation. I'll file and issue.
>
> Thanks!
>
> --
> 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 post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.
> For more options, visit https://groups.google.com/groups/opt_out.
>



-- 
Thanks,
William

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [Puppet Users] Puppet Dashboard Error 400 Invalid Parameter at passenger pp:48

2013-09-08 Thread William Van Hevelingen
The bug is fixed in the master branch on Github. I'll see about  getting a
new release on the forge.

Cheers,
William


On Wed, Sep 4, 2013 at 5:31 PM, Cory Stoker  wrote:

> Look at the apache::vhost definition.  It looks to me that "template"
> is no longer a parameter to the defined type.  Since this looks like
> puppetlabs-dashboard I would check out the puppetlabs-apache module to
> find the apache::vhost defined type in
> puppetlabs-apache/manifest/vhost.pp.  If the parameter is not declared
> in the type then you will need to remove that line and figure out what
> you do need to declare in passenger.pp for the apache::vhost resource.
>  It looks to me like $template was a parameter in older versions of
> that module (0.4.0) but is now gone in the current version.
>
> HTH
>
> On Wed, Sep 4, 2013 at 8:08 AM, Mr. Vitriol 
> wrote:
> > Hi,
> > I am new to the job and forum. I installed puppet and puppetmaster and
> set
> > up my first dependencies acording to a manual that we have here in our
> > company. Everything works fine and I can set up new nodes with several
> > modules to choose from. Unfortunatley the Dashboard gives me errors
> instead
> > of starting correctley.
> >
> > Here the message:
> >
> > Error: Could not retrieve catalog from remote server: Error 400 on
> SERVER:
> > Invalid parameter template at
> > /etc/puppet/modules/dashboard/manifests/passenger.pp:48 on node
> > puppet-master.defaultdomain
> > Warning: Not using cache on failed catalog
> > Error: Could not retrieve catalog; skipping run
> >
> > The relevant passage from the passenger is:
> >
> > # Class: dashboard::passenger
> > #
> > # This class configures parameters for the puppet-dashboard module.
> > #
> > # Parameters:
> > #   [*dashboard_site*]
> > # - The ServerName setting for Apache
> > #
> > #   [*dashboard_port*]
> > # - The port on which puppet-dashboard should run
> > #
> > #   [*dashboard_config*]
> > # - The Dashboard configuration file
> > #
> > #   [*dashboard_root*]
> > # - The path to the Puppet Dashboard library
> > #
> > # Actions:
> > #
> > # Requires:
> > #
> > # Sample Usage:
> > #
> > class dashboard::passenger (
> >   $dashboard_site,
> >   $dashboard_port,
> >   $dashboard_config,
> >   $dashboard_root
> > ) inherits dashboard {
> >
> >   require ::passenger
> >   include apache
> >
> >   file { '/etc/init.d/puppet-dashboard':
> > ensure => absent,
> >   }
> >
> >   file { 'dashboard_config':
> > ensure => absent,
> > path   => $dashboard_config,
> >   }
> >
> >   apache::vhost { $dashboard_site:
> > port => $dashboard_port,
> > priority => '50',
> > docroot  => "${dashboard_root}/public",
> > template => 'dashboard/passenger-vhost.erb',
> >   }
> > }
> >
> > That is the default version, since I didn't add anything.
> >
> > I hope someone can help me with this, google wasn't able to.
> >
> > Thanks in advance.
> >
> > --
> > 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 post to this group, send email to puppet-users@googlegroups.com.
> > Visit this group at http://groups.google.com/group/puppet-users.
> > 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 post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.
> For more options, visit https://groups.google.com/groups/opt_out.
>



-- 
Thanks,
William

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [Puppet Users] Need help starting with puppet

2013-09-08 Thread William Van Hevelingen
This look similar to a known bug.

http://projects.puppetlabs.com/issues/21478

It will be released in Puppet 3.3.0

In the meantime I would continue with the tutorial.

Cheers,
William


On Sat, Sep 7, 2013 at 8:16 AM, Ashley Penney
wrote:

> If you haven't already done this you should head over to
> http://apt.puppetlabs.com/ after the vagrant instance boots and grab the
> appropriate http://apt.puppetlabs.com/puppetlabs-release-precise.debpackage 
> first so that you're using our packages rather than the default
> Ubuntu ones.  Hopefully if you use those you should get a better result!
>
>
> On Fri, Sep 6, 2013 at 10:29 PM,  wrote:
>
>> hello world.
>>
>> I found the learning puppet site so I thought that would be a good place
>> to start.
>>
>> I downloaded the vm.
>>
>> I was able to import it into virtualbox.
>>
>> But then it hung during bootup.
>>
>> So I used vagrant to vagrant up a clean precise64 box.
>>
>> I did apt-get install puppet
>>
>> apt-get got me this:
>>
>> vagrant@precise64:~$
>> vagrant@precise64:~$ puppet --version
>> 2.7.11
>> vagrant@precise64:~$
>>
>> vagrant@precise64:~$ which puppet
>> /usr/bin/puppet
>> vagrant@precise64:~$
>> vagrant@precise64:~$ aptitude search puppet
>> p   etherpuppet
>> p   etherpuppet:i386
>> p   mcollective-plugins-puppetca
>> p   mcollective-plugins-puppetd
>> p   mcollective-plugins-puppetral
>> i   puppet
>> i A puppet-common
>> p   puppet-el
>> p   puppet-lint
>> p   puppet-testsuite
>> p   puppetmaster
>> p   puppetmaster-common
>> p   puppetmaster-passenger
>> p   vim-puppet
>> vagrant@precise64:~$
>> vagrant@precise64:~$
>>
>> Then I tried the first command in learning puppet:
>>
>> puppet resource service
>>
>> I saw a screen full of warnings like this 1:
>>
>> warning: Service network-interface-container found in both debian and
>> upstart; skipping the upstart version
>>
>> Then I saw an error at the end:
>>
>> Could not run: Execution of '/sbin/status wait-for-state' returned 1:
>> status: Unknown parameter: WAITER
>>
>> I tried a reboot to see if that helped.
>>
>> Reboot did not help.
>>
>> I'm looking for clues on how to get puppet up in a clean ubuntu 12.04
>> virtual box.
>>
>> If I need to steer clear of Vagrant to make puppet work,
>> that is a non-starter for us.
>>
>> We had planned to do a lot of mixing of Vagrant and 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 post to this group, send email to puppet-users@googlegroups.com.
>> Visit this group at http://groups.google.com/group/puppet-users.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
>
> --
> Ashley Penney
> ashley.pen...@puppetlabs.com
> Module Engineer
>
> *Join us at PuppetConf 2014, September 23-24 in San Francisco*
>
> --
> 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 post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.
> For more options, visit https://groups.google.com/groups/opt_out.
>



-- 
Thanks,
William

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.