Re: [Puppet Users] Re: Puppet Dashboard Broken on Debian Jesse
Hi Geoff, I would advise switching from Puppet Dashboard to something that is still actively maintained. Puppetboard and theforeman are both well maintained alternatives. https://github.com/nedap/puppetboard http://theforeman.org/ If you still want to stick with puppet-dashboard, you will want to look at this Github issue: https://github.com/sodabrew/puppet-dashboard/issues/270 Cheers, William On Mon, Mar 17, 2014 at 11:58 AM, Geoff Goehle goe...@gmail.com wrote: I should have also mentioned that puppet-dashboard is not available at all when using the main Debian repositories. As of right now I can't think of a way to get puppet-dasboard running on Debian jessie at all without bypassing the package managers. Geoff. On Monday, March 17, 2014 10:12:38 AM UTC-4, Geoff Goehle wrote: The latest round of updates to Debian Jesse (testing) has really broken puppet-dashboard when using the puppetlabs repo. I currently have my apt sources list set up to use the unstable repo (since there isn't a jessie or testing repo). When I try to install puppet-dashboard I get puppet-dashboard : Depends: ruby1.8 (= 1.8.7) but it is not installable Depends: rubygems but it is not installable This probably has something to do with the lastest upgrades to ruby that came down last week, which include a message that says. The Ruby packages in Debian no longer support switching between different Ruby versions using update-alternatives. All unversioned binary names such as `ruby`, `gem` etc are now provided by the `ruby` package, and will be symbolic links pointing to the binaries corresponding to the current default version in Debian. So it looks like the usual method of switching to ruby 1.8 wont work and as far as I can tell ruby 1.8 isn't even available on Debian jessie. Geoff. -- 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/1256b903-8bfe-44f3-98a7-5a5c9be7af0a%40googlegroups.comhttps://groups.google.com/d/msgid/puppet-users/1256b903-8bfe-44f3-98a7-5a5c9be7af0a%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- 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/CAEXKxLxcQ1ytO%2B%2BOKTmr6jyoMfWCSh0LyXE0VTgy1pk0kR0aVw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] new puppet book revision
Hi All, There was some problem between the publishing company and the printing company that caused the book to be delayed for so long. Amazon now says the book is in stock so I'm assuming the problem has been resolved. Let us know if you have any feedback good or bad. :) Thanks William On Wed, Dec 18, 2013 at 9:58 AM, Stuart Cracraft smcracr...@gmail.comwrote: Okay, let us know your assessment of the book as well after you get further into it. And your critiques. On Wednesday, December 18, 2013 7:32:51 AM UTC-8, Benito Mourelo Caldeiro wrote: On mar, 2013-12-17 at 14:27 -0800, Stuart Cracraft wrote: It looks like Amazon/publishers/authors/etc. have revised the new puppet book date: http://www.amazon.com/Pro-Puppet-Spencer-Krum/dp/ 1430260408/ref=sr_1_3?ie=UTF8qid=1387318030sr=8-3keywords=puppet+3 Fun! I bought the alfa book, and today I could download the PDF of the 2nd edition from apress.com. Saudos, Benito. -- 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/cc4ad721-f2a2-4647-9e10-14386b78b345%40googlegroups.com . 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAEXKxLxR%2Bt9du94WhNQLpDrG%3DLRxa4UvJjQnxniOe0Kc4aJK2w%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Puppetlabs/Apache 0.10.0 Release
A couple of days ago we released puppetlabs/apache 0.10.0, and as busy as all involved people were we were to accomplish the release they are now equally busy to do other amazing things. http://forge.puppetlabs.com/puppetlabs/apache/0.10.0 Among the endless (22) features that we've added in this release two big accomplishments shine, making this an important milestone: added FreeBSD as a supported Platform (Special Thanks to ptomulik) made sure that a great number of tests are /actually/ executed (Special Thanks to Aethylred) The latter really guarantees that this release and the ones coming will be truely backwards compatible. Check out the CHANGELOG for all the changes in this release. https://github.com/puppetlabs/puppetlabs-apache/blob/https://github.com/puppetlabs/puppetlabs-apache/blob/0.10.0/CHANGELOG.md 0.10.0https://github.com/puppetlabs/puppetlabs-apache/blob/0.10.0/CHANGELOG.md /CHANGELOG.mdhttps://github.com/puppetlabs/puppetlabs-apache/blob/0.10.0/CHANGELOG.md Moving forward tampakrap is working on OpenSuse/SLES and Gentoo osfamily support. The module team is working hard on a new systems test framework: [Beaker]( https://github.com/puppetlabs/beaker) that will expand upon our rspec-system tests allowing use to support multinode tests, as well as the ability to test platforms that are usually out of reach for normal developers (AIX…). For the bigger changes we need to make some hard decisions. We know that we need to get started on support for httpd 2.4 as more distributions are finally picking it up. But we don't know yet how to get there exactly. We thus want to ask you to participate in discussions on the issue tracker: https://github.com/puppetlabs/puppetlabs-apache/issues/477 https://github.com/puppetlabs/puppetlabs-apache/issues/337 As we approach a 1.0 release we want to know what features we need to support and what breakage you as the user are willing to take. Please send us feedback if you have use cases for the puppetlabs/apache module that we are not aware of: - your most treasured feature here - Proxy - SSL termination - Apache HTTPd as Application Container - puppetlabs/apache consumed by other modules Cheers, igalic and blkperl -- 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/CAEXKxLz1LNPkaK_jtyE6%3DnPJv1hy4zyLK4HVEgRwM_Lk6eWjbw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppetlabs/Apache 0.10.0 Release
I opened an issue for SUSE/SLES support to track it's progress. https://github.com/puppetlabs/puppetlabs-apache/issues/525 On Tue, Dec 10, 2013 at 5:18 AM, Darin Perusich da...@darins.net wrote: On Tue, Dec 10, 2013 at 3:58 AM, William Van Hevelingen wva...@gmail.com wrote: A couple of days ago we released puppetlabs/apache 0.10.0, and as busy as all involved people were we were to accomplish the release they are now equally busy to do other amazing things. http://forge.puppetlabs.com/puppetlabs/apache/0.10.0 Among the endless (22) features that we've added in this release two big accomplishments shine, making this an important milestone: added FreeBSD as a supported Platform (Special Thanks to ptomulik) made sure that a great number of tests are /actually/ executed (Special Thanks to Aethylred) The latter really guarantees that this release and the ones coming will be truely backwards compatible. Check out the CHANGELOG for all the changes in this release. https://github.com/puppetlabs/puppetlabs-apache/blob/0.10.0/CHANGELOG.md Moving forward tampakrap is working on OpenSuse/SLES and Gentoo osfamily support. I can contribute to openSUSE/SLES support. My apache module is based on the puppetlabs module and fully supports the SUSE osfamily. If there's a forked repo someone could point me at I can compare it with the work I've already done. The module team is working hard on a new systems test framework: [Beaker](https://github.com/puppetlabs/beaker) that will expand upon our rspec-system tests allowing use to support multinode tests, as well as the ability to test platforms that are usually out of reach for normal developers (AIX…). For the bigger changes we need to make some hard decisions. We know that we need to get started on support for httpd 2.4 as more distributions are finally picking it up. But we don't know yet how to get there exactly. We thus want to ask you to participate in discussions on the issue tracker: https://github.com/puppetlabs/puppetlabs-apache/issues/477 https://github.com/puppetlabs/puppetlabs-apache/issues/337 As we approach a 1.0 release we want to know what features we need to support and what breakage you as the user are willing to take. Please send us feedback if you have use cases for the puppetlabs/apache module that we are not aware of: your most treasured feature here Proxy SSL termination Apache HTTPd as Application Container puppetlabs/apache consumed by other modules Cheers, igalic and blkperl -- 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/CAEXKxLz1LNPkaK_jtyE6%3DnPJv1hy4zyLK4HVEgRwM_Lk6eWjbw%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/CADaviKtGJnOz_85BGxrr3WzdjDWdxaYGumrczBwR8kZs%2B%2BbX8A%40mail.gmail.com . 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAEXKxLyi9HTZU9dci%2ByB6K%3DzoTNTS9zt7TDTaxXOj0NfzJ7eNQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Release 1.0.0 of puppet-module-collectd
Hi Everyone, I've just cut the 1.0.0 release of puppet-module-collectd. You can download it from the Puppet Forge, http://forge.puppetlabs.com/pdxcat/collectd or via the Puppet module tool with `puppet module install pdxcat/collectd` or from our Github. Thanks to everyone who has contributed to help make this module a success [1]. The module now supports 5 osfamilies and the configuration of 24 plugins. This release breaks some backwards compatibility so make sure you check the changelog before updating [2]. If you would like assist in the development of this module please send pull requests. There are many plugins that can still be added and we're in need of puppet rspec tests for each plugin. [1] https://github.com/pdxcat/puppet-module-collectd/graphs/contributors [2] https://github.com/pdxcat/puppet-module-collectd/blob/master/CHANGELOG Cheers, William -- William Van Hevelingen Lead Unix System Administrator Maseeh College of Engineering and Computer Science Portland State University 503-725-5497 w...@pdx.edu www.pdx.edu -- 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] Re: [Puppet-dev] Announce: PuppetDB 1.5.0 Available
No packages for precise/raring? Its missing debs for 1.5.0. Lucid seems fine Thanks, William On Mon, Sep 30, 2013 at 4:56 PM, Chris Price ch...@puppetlabs.com wrote: PuppetDB 1.5.0 is now available for download! This is a new feature release that contains a few bug-fixes as well. = ## Downloads ## = Available in native package format at: http://yum.puppetlabs.com and http://apt.puppetlabs.com Puppet module: http://forge.puppetlabs.com/puppetlabs/puppetdb Source (same license as Puppet): http://github.com/puppetlabs/puppetdb/ # Documentation (including how to install): http://docs.puppetlabs.com/puppetdb/1.http://docs.puppetlabs.com/puppetdb/1.2 5 # Issues can be filed at: http://projects.puppetlabs.com/projects/puppetdb/issues ## PuppetDB 1.5.0 Release Notes ## Notable features and improvements: * (#21520) Configuration for soft failure when PuppetDB is unavailable This feature adds a new option 'soft_write_failure' to the puppetdb configuration. If enabled the terminus behavior is changed so that if a command or write fails, instead of throwing an exception and causing the agent to stop it will simply log an error to the puppet master log. * New v3 query API New `/v3` URLs are available for all query endpoints. The `reports` and `events` endpoints, which were previously considered `experimental`, have been moved into `/v3`. Most of the other endpoints are 100% backwards-compatible with `/v2`, but now offer additional functionality. There are few minor backwards-incompatible changes, detailed in the comments about individual endpoints below. * Query paging This feature adds a set of new HTTP query parameters that can be used with most of the query endpoints (`fact_names`, `facts`, `resources`, `nodes`, `events`, `reports`, `event-counts`) to allow paging through large result sets over multiple queries. The available HTTP query parameters are: * `limit`: an integer specifying the maximum number of results to return. * `order-by`: a list of fields to sort by, in ascending or descending order. The legal set of fields varies by endpoint; see the documentation for individual endpoints for more info. * `offset`: an integer specifying the first result in the result set that should be returned. This can be used in combination with `limit` and `order-by` to page through a result set over multiple queries. * `include-total`: a boolean flag which, if set, will cause the HTTP response to contain an `X-Records` header indicating the total number of results that are available that match the query. (Mainly useful in combination with `limit`.) * New features available on `events` endpoint * The `events` data now contains `file` and `line` fields. These indicate the location in the manifests where the resource was declared. They can be used as input to an `events` query. * Add new `configuration-version` field, which contains the value that Puppet supplied during the agent run. * New `containing-class` field: if the resource is declared inside of a Puppet class, this field will contain the name of that class. * New `containment-path` field: this field is an array showing the full path to the resource from the root of the catalog (contains an ordered list of names of the classes/types that the resource is contained within). * New queryable timestamp fields: * `run-start-time`: the time (on the agent node) that the run began * `run-end-time`: the time (on the agent node) that the run completed * `report-receive-time`: the time (on the puppetdb node) that the report was received by PuppetDB * Restrict results to only include events that occurred in the latest report for a given node: `[=, latest-report?, true]` * New `event-counts` endpoint `v3` of the query API contains a new `event-counts` endpoint, which can be used to retrieve count data for an event query. The basic input to the endpoint is an event query, just as you'd provide to the `events` endpoint, but rather than returning the actual events, this endpoint returns counts of `successes`, `failures`, `skips`, and `noops` for the events that match the query. The counts may be aggregated on a per-resource, per-class, or per-node basis. * New `aggregate-event-counts` endpoint This endpoint is similar to the `event-counts` endpoint, but rather than aggregating the counts on a per-node, per-resource, or per-class basis, it returns aggregate counts across your entire population. * New `server-time` endpoint This endpoint simply returns a timestamp indicating the current time on the PuppetDB server. This can be used as input
Re: [Puppet Users] Re: Announce: Puppet 3.3.0 Available
Hi Henrik or Eric,
Is it possible to error on failed lookups? This is useful for replacing the
fail('osfamily not supported') lines in most params.pp files. Ryan
mentioned the same thing in the ticket and I wasn't sure if it was resolved.
It currently returns undef if the value is not found.
On Sat, Sep 14, 2013 at 8:26 AM, Henrik Lindberg
henrik.lindb...@cloudsmith.com wrote:
On 2013-14-09 9:05, Robin Powell wrote:
In the announcement,
http://projects.puppetlabs.**com/issues/16856http://projects.puppetlabs.com/issues/16856is
introduced as data in modules, and that we should see ARM-9 (
https://github.com/puppetlabs/**armatures/blob/master/arm-9.**
data_in_modules/index.mdhttps://github.com/puppetlabs/armatures/blob/master/arm-9.data_in_modules/index.md).
But #16856 itself never references ARM-9 that I can see, but only
references ARM-8 (
https://github.com/puppetlabs/**armatures/blob/master/arm-8.**
puppet_bindings/index.mdhttps://github.com/puppetlabs/armatures/blob/master/arm-8.puppet_bindings/index.md).
Please tell me, which of ARM-8 and ARM-9 are actually implemented in
3.3.0? I understand in either case it's not considered a completed
work, but I'd like to know at least what to be looking at.
ARM-9 ('data in modules') is fully implemented as described and is
included in 3.3.0. It is considered to be a complete work. It is based on
the ideas in ARM-8 'puppet bindings' (which thus is partially implemented;
usage of the bindings system for an updated ENC, the concrete Puppet DSL
syntax, and a couple of the more exotic types of bindings are not
implemented in 3.3.0)
I updated issue 16856 with links to ARM-9 and to the example that was just
posted from ProPuppet.
It is experimental in the respect that we want to get it in-front of
people to get feedback on usability and to find issues. Based on that
feedback and when later released it may change in a backwards incompatible
way compared to the experimental version. We will do our best to not
introduce such breakage.
Hope that better explains the status of ARM-9 (data in modules) and the
difference between it and ARM-8.
Regards
- henrik
--
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+unsubscribe@**googlegroups.compuppet-users%2bunsubscr...@googlegroups.com
.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at
http://groups.google.com/**group/puppet-usershttp://groups.google.com/group/puppet-users
.
For more options, visit
https://groups.google.com/**groups/opt_outhttps://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
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 ashley.pen...@puppetlabs.comwrote: 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, audrey.lee.is...@gmail.com 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.
Re: [Puppet Users] Puppet Dashboard Error 400 Invalid Parameter at passenger pp:48
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 cory.sto...@gmail.com 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 patrick.marv.b...@gmail.com
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] migrating to puppetdb
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 da...@darins.net 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 Forge max upload size?
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, vkanak...@gmail.com 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] Error with service: invalid byte sequence in US-ASCII
I get the same error when running puppet-lint puppet 3.1.x regression? rake aborted! invalid byte sequence in US-ASCII /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/lexer.rb:120:in `[]' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/lexer.rb:120:in `block in tokenise' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/lexer.rb:119:in `each' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/lexer.rb:119:in `tokenise' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/plugin.rb:40:in `load_data' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/plugin.rb:54:in `run' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint.rb:155:in `run' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/tasks/puppet-lint.rb:23:in `block (3 levels) in initialize' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/tasks/puppet-lint.rb:21:in `each' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/tasks/puppet-lint.rb:21:in `block (2 levels) in initialize' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/tasks/puppet-lint.rb:13:in `block in initialize' Tasks: TOP = lint On Tue, May 21, 2013 at 2:43 AM, David Schmitt da...@dasz.at wrote: On 19.05.2013 14:18, Mateusz Fiołka wrote: I'm not sure if it is related to the services. It rather looks like puppet related to me. I'm having a similar problem on a newly created vps. When I do puppet apply first time I get the message: Error: Could not set 'present' on ensure: invalid byte sequence in US-ASCII at 3:/root/mf-prod.pp I've seen this error when the puppet master process started by init receives a different locale environment than when it is started from the command line. Check /proc/$pid/env of the running puppet master process for LANG/LC_* and compare that to your shell env. Regards, David -- 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+unsubscribe@**googlegroups.compuppet-users%2bunsubscr...@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?hl=enhttp://groups.google.com/group/puppet-users?hl=en . For more options, visit https://groups.google.com/**groups/opt_outhttps://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] Error with service: invalid byte sequence in US-ASCII
Found the bug that Jeff created http://projects.puppetlabs.com/issues/11303 On Mon, Sep 2, 2013 at 11:42 PM, William Van Hevelingen wva...@gmail.comwrote: I get the same error when running puppet-lint puppet 3.1.x regression? rake aborted! invalid byte sequence in US-ASCII /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/lexer.rb:120:in `[]' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/lexer.rb:120:in `block in tokenise' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/lexer.rb:119:in `each' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/lexer.rb:119:in `tokenise' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/plugin.rb:40:in `load_data' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/plugin.rb:54:in `run' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint.rb:155:in `run' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/tasks/puppet-lint.rb:23:in `block (3 levels) in initialize' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/tasks/puppet-lint.rb:21:in `each' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/tasks/puppet-lint.rb:21:in `block (2 levels) in initialize' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/tasks/puppet-lint.rb:13:in `block in initialize' Tasks: TOP = lint On Tue, May 21, 2013 at 2:43 AM, David Schmitt da...@dasz.at wrote: On 19.05.2013 14:18, Mateusz Fiołka wrote: I'm not sure if it is related to the services. It rather looks like puppet related to me. I'm having a similar problem on a newly created vps. When I do puppet apply first time I get the message: Error: Could not set 'present' on ensure: invalid byte sequence in US-ASCII at 3:/root/mf-prod.pp I've seen this error when the puppet master process started by init receives a different locale environment than when it is started from the command line. Check /proc/$pid/env of the running puppet master process for LANG/LC_* and compare that to your shell env. Regards, David -- 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+unsubscribe@**googlegroups.compuppet-users%2bunsubscr...@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?hl=enhttp://groups.google.com/group/puppet-users?hl=en . For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out . -- Thanks, William -- 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] Error with service: invalid byte sequence in US-ASCII
Actually the umbrella bug is now. http://projects.puppetlabs.com/issues/20522 On Mon, Sep 2, 2013 at 11:47 PM, William Van Hevelingen wva...@gmail.comwrote: Found the bug that Jeff created http://projects.puppetlabs.com/issues/11303 On Mon, Sep 2, 2013 at 11:42 PM, William Van Hevelingen wva...@gmail.comwrote: I get the same error when running puppet-lint puppet 3.1.x regression? rake aborted! invalid byte sequence in US-ASCII /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/lexer.rb:120:in `[]' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/lexer.rb:120:in `block in tokenise' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/lexer.rb:119:in `each' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/lexer.rb:119:in `tokenise' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/plugin.rb:40:in `load_data' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/plugin.rb:54:in `run' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint.rb:155:in `run' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/tasks/puppet-lint.rb:23:in `block (3 levels) in initialize' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/tasks/puppet-lint.rb:21:in `each' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/tasks/puppet-lint.rb:21:in `block (2 levels) in initialize' /shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/tasks/puppet-lint.rb:13:in `block in initialize' Tasks: TOP = lint On Tue, May 21, 2013 at 2:43 AM, David Schmitt da...@dasz.at wrote: On 19.05.2013 14:18, Mateusz Fiołka wrote: I'm not sure if it is related to the services. It rather looks like puppet related to me. I'm having a similar problem on a newly created vps. When I do puppet apply first time I get the message: Error: Could not set 'present' on ensure: invalid byte sequence in US-ASCII at 3:/root/mf-prod.pp I've seen this error when the puppet master process started by init receives a different locale environment than when it is started from the command line. Check /proc/$pid/env of the running puppet master process for LANG/LC_* and compare that to your shell env. Regards, David -- 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+unsubscribe@**googlegroups.compuppet-users%2bunsubscr...@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?hl=enhttp://groups.google.com/group/puppet-users?hl=en . For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out . -- Thanks, William -- Thanks, William -- 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] Fwd: [Module team] Much ado about modules
On Fri, Jul 5, 2013 at 11:05 AM, Ashley Penney ashley.pen...@puppetlabs.com wrote: Hello! Now that Puppetlabs has a module team we thought we should start trying to keep the community informed as to what we're doing and why on earth we're doing it. I wanted to put together a short update (I'm aiming to do these every friday) as to where we stand. This is awesome I've been waiting for this to be prioritized as well. :) We appreciate each and every PR you send us (unless you forgot specs, which makes me shout at a puppy) and hopefully we'll be able to shorten the cycle of merging them as this work goes forward. Specs are really hard for first time contributors, a lot of Pull Requests are still in the backlog of unmerged PRs due to the submitter being asked to submit Spec tests. I would like to see some documentation we can point first time contributors too. The corresponding ticket is: https://projects.puppetlabs.com/issues/14456 Also perhaps the new module team can make the final decision on: https://projects.puppetlabs.com/issues/8 Looking forward I would like to see Puppet modules development remove the bottleneck on Puppetlabs staff and other module maintainers to merge PRs. Often times I submit PRs for new OS support or additional features to really good modules on Github or the Forge and the maintainer does not have the time or OS to review, test and merge the PR. A possible solution might be to mirror The Openstack Project. They have a pretty effective process of using Gerrit + Jenkins to review, test, and merge code. The goal would be to allow us to have community supported official modules kind of like how the Nagios project has a nagios-plugins repo. I think a system like this or similar would allow us to: * Submit new modules for inclusion as official community modules * Support faster iteration on more operating systems * Reduce the number of competing modules on the forge, everyone doesn't need there own custom Apache module * Improve the quality of modules and increase the amount of testing * Reduce the number of bad modules on the Forge I look forward to hearing people's ideas and continuing the discussion. 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] 2.7 - 3.1 upgrade path?
Hi Bruce, What we did was bring up a second puppetmaster with puppetdb and started testing clients against it. Generate a cert on the old puppetmaster and give it to the new one so that it is trusted by the clients. You will want to specify the ca_server on the new puppetmaster to be the old puppetmaster. There should be docs on how to do this. It is the same as setting up multiple puppetmasters. Then you can start testing clients against the new master with: puppet agent --test --server=newpuppetmaster.example.org This should allow you to start catching all the incompatibilities in your current puppet code. Once you feel comfortable you can start switching all of your clients over. Watch the puppetmaster logs or dashboard to make sure everything is working as expected if your doing large numbers of nodes at a time. After a few days or weeks of a puppet3 master start updating puppet and facter on your clients. You may wish to read this as well http://somethingsinistral.net/blog/the-angry-guide-to-puppet-3/ The update went really smooth for us, just a few issues across our 80 modules, good luck. Cheers, William Van Hevelingen https://github.com/blkperl/ On Wed, May 8, 2013 at 9:03 AM, Dan White y...@comcast.net wrote: Server first. Always “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) -- *From: *Bruce bly...@yahoo.com *To: *puppet-users@googlegroups.com *Sent: *Wednesday, May 8, 2013 11:58:14 AM *Subject: *[Puppet Users] 2.7 - 3.1 upgrade path? Hi, We have hosts running 2.7 client, a single puppet master, and we're using Puppet Dashboard for ENC. What would be a recommended order of operations to get to 3.1 on client/server, and using PuppetDB instead? 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?hl=en. 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?hl=en. 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] IPS repo module or provider/type for Solaris/OpenIndiana
Hi Everyone, Does anyone know of a good IPS repo module or provider/type for Solaris/OpenIndiana? I looked on the forge and github and didn't find anything promising. I've created this snippet for the Oracle supported repo but I'm looking for a more functional solution for more than just the Oracle supported repo. https://github.com/blkperl/puppet-snippets/blob/master/manifests/publisher.pp If anyone would like to collaborate on an IPS repo module please respond or ping me on IRC blkperl @ freenode -- Thanks, William Van Hevelingen https://github.com/blkperl -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Automating nagios_service resource type
Is there a reason your not using exported nagios resources instead? http://docs.puppetlabs.com/guides/exported_resources.html We're using it in production and it works quite well with puppetdb as the backend. William On Thu, Feb 14, 2013 at 4:56 PM, Peter Brown rendhal...@gmail.com wrote: On 15 February 2013 10:49, Sans r.santanu@gmail.com wrote: Thanks Pete, for the heads-up! I'm gonna give it a try now. Cheers!! Awesome! I do admit the docs are a bit sparse but I have tried to name everything with sensible descriptive names. If you get stuck, find a bug or would like a new feature give me a shout. I use github for my code so you can also submit a bug there if you like so I can keep track of it. I do use it in my infrastructure and it gets updated when I fix things. I do also test the crap out of it before I push it to forge so that is the best version to use. Good luck!. Pete. On Friday, February 15, 2013 12:17:49 AM UTC, Pete wrote: I found this a while ago to so I wrote a module to do it easily. It's on the forge here. https://forge.**puppetlabs.com/rendhalver/** monitoring https://forge.puppetlabs.com/rendhalver/monitoring I also have an nrpe module which may help here https://forge.puppetlabs. **com/rendhalver/nrpe https://forge.puppetlabs.com/rendhalver/nrpe -- 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?hl=en. 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?hl=en. 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] New NRPE Puppet module
Hello Puppet Users and Dev, I have just a pushed a puppet module for NRPE to github. Initially it supports the Debian, Redhat, and Solaris based operating systems. I plan on adding FreeBSD support in the near future. In the meantime I will be updating the documentation and getting it ready for a forge release. I would appreciate any feedback or pull requests to add additional functionality. https://github.com/pdxcat/puppet-module-nrpe My nick is blkperl in #puppet if you want to bounce ideas. -- Thanks, William Van Hevelingen -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Managing community modules.
Hi Jon, On 02/26/2012 10:17 AM, Jonathan Proulx wrote: Hi All, I'm building out my first puppet install and obviously want to leverage modules from the forge. Since I'm using git as the VCS for my puppet configs and most community modules are hosted on github it seems the obvious thing to do is to use either git submodules or subtree merging, but I haven't used those features in the past so it's not clear to me the added features are worth the complexity over pulling a tarball of the module into my local git. It does seem contributing back would be easier with one of the git options anyway, what methods are you using and how do you like them? Thanks, -Jon We use git submodules for both internal and public modules since the github repositories are often ahead of the tarballs on the forge. Make sure to have an internal mirror of any submodules you clone from github in case github is down or the owner deletes the repository. We try to use modules forked or created by puppetlabs and contribute back any features we need. Otherwise we fork a module on github configure it for our environment or improve it and push it back to github. Using git submodules allows us to share non-secret puppet code internally to devs and junior sysadmins who can then push back test branches that the Senior Sysadmins can review and merge in. Also using git/puppet environments you can branch in a submodule and test your changes quite easily and then push them to github and click the pull request button in github. :) -- William Van Hevelingen https://github.com/blkperlhttps://github.com/pdxcat -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet resource, and parameters that take arrays...
Its helpful if you include error messages, but the answer is puppet resource host some.example.com ip=127.0.0.1 host_aliases=[' www.example.com','mail.example.com'] -- William Van Hevelingen wva...@gmail.com -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet resource, and parameters that take arrays...
Sorry, nope: Ack my bad misread the output. I think its a bug, I seem to remember that the parsedfile provider doesn't always work correctly under puppet resource http://mail.example.com/ -- William Van Hevelingen wva...@gmail.com -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Resources on Windows
Hi Patrick, On Wed, Sep 8, 2010 at 11:10 PM, Patrick kc7...@gmail.com wrote: I was going to try puppet on Windows and was wondering if anyone has advice before I start. I found http://projects.reductivelabs.com/projects/puppet/wiki/Puppet_Windows I attempted to get puppet running on windows about a week ago and ran into this bug. http://projects.reductivelabs.com/issues/4649 I mostly wondering if these work/exist: *) file exists (not sure if it works) *) exec not sure *) package (msi) I don't see an msi.rb or win32.rb in the source code for providers so I'm guessing no *) The registry provider that people were talking about. It might just be an idea. I believe it hasn't been created yet, it would be cool if there was one :) Also, is http://github.com/reductivelabs/puppet; the unstable trunk, the stable trunk, or the most recent 2.6 release? depends on the branch, you can also git checkout using git tags for specific versions 'gem install puppet' should get you 2.6 Also I just updated the wiki to use facter 1.5.8. Theres a patch for windows uptime if you grab branch master theres a patch from me adding manufacturer, model, and serial number. http://projects.reductivelabs.com/issues/4575 Also note install.rb doesn't work on windows http://projects.reductivelabs.com/issues/4644 Hope this helps. Regards -- William Van Hevelingen Computer Science Major Portland State University wva...@gmail.com -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Easy way to determine if theres duplicate Documentation Tickets in Redmine?
Currently it is incredibly difficult to determine if a duplicate ticket already exists. If the url of the broken page was an option in redmine then it would be easy to search for all tickets relating to a certain page and determine if a bug has already been reported for specific pages. There is a 'support url' filter that already exists but it is not accessible from the New Issue tab. http://projects.reductivelabs.com/projects/puppet-docs/issues Comments? suggestions? Am I missing another easy way to find doc tickets based off url? Cheers -- William Van Hevelingen Portland State University w...@cs.pdx.edu -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Easy way to determine if there's duplicate Documentation Tickets in Redmine?
You should be able to paste the URL into the keywords box and that should aid searching. It works if the keyword is set to the URL, but most people have been putting the URL in the description or not at all. In fact most of the current tickets have titles/descriptions that barely reference the correct page. If possible, I think it would be useful if a URL field was available. Keywords are a bit general and most people don't initially think to put the URL there. Cheers William Van Hevelingen -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Easy way to determine if there's duplicate Documentation Tickets in Redmine?
The Forge, Dashboard and Documentation projects all now have a field called Affected URL. +1 Thanks James :) -- William Van Hevelingen Portland State University Computer Science Student w...@cs.pdx.edu -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: [Puppet-dev] GSoC - Introducing myself
Hello Everybody, I'm William and I am the other Google Summer of Code 2010 student. I will be working on a Puppet type to manage advanced provisioning and configuration of network interfaces (initially on various Linux distributions). I'm really excited to start working on this project and I would like to thank Michael DeHaan for being a great mentor so far. I'm on freenode in #puppet as blkperl if you want to say hello or offer some tips :) and email works too. Regards -- William Van Hevelingen Computer Science Major Portland State University w...@cs.pdx.edu http://blkperl.blogspot.com/ -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
