[Puppet Users] Disable Cron Script using puppet resource
How can I disable / enable a cron job using puppet resource cron? Thanks, Corey Osman co...@logicminds.biz Green IT and Data Center Automation Specialist -- 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] Puppet Support for Windows
Hi All, I am currently looking at using PE to provide our config management (and orchestrated deployment via MCollective) for our app stack. It is currently used to manage the Linux OS estate but not yet for Windows. I'd like to use the same tool so that the people who develop and manage apps on both OS only have a single learning curve and given PE is already used in the organisation that is my first choice. In my initial investigation there are a number of critical functions that currently cannot be managed out the box (or via modules on PuppetForge) which i would have expected from a tool such as this. (I appreciate that Windows support on Puppet is relatively new and that I could create my own modules. However that would mean learning Ruby *and* Puppet, diverting resource away from their main job, and convincing management to allow custom coding something that they'd expect out of the box of such a tool is going to be tricky!). So, are there currently any plans to provide - NTFS file support to allow detailed control of permissions settings and not relying on the very limited POSIX - Windows mapping in the current File resource. (And yes i understand the RAL and reasons behind it, but this is kind of a deal breaker for us for the Windows side of our estate)? - Setting the user for a Service on Windows? (I know i could probably exec out to sc.exe to achieve this but would like it config managed) And probably not for this forum (but i know PuppetLabs employees are reading)... - Do you have any idea of of when MCollective support in Puppet Enterprise will be provided for Windows. Thanks, Damian -- 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. 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] OS X Lion group membership not updated
Sorry to revive an old thread, but this seems to be the only other thing I can find on this exact issue I'm having. Nigel - do you have any idea if the fixes have ever made it into a 2.7.x release? I'm using 2.7.20 (as that's what is used in our non-OSX hosts) and still getting this same error. Thanks! Doug On Wednesday, September 7, 2011 8:07:00 AM UTC-5, Nigel Kersten wrote: On Tue, Sep 6, 2011 at 12:42 PM, James Turnbull ja...@puppetlabs.comjavascript: wrote: David Thompson wrote: Switching to puppet (2.7.3) for managing my OS X Lion systems, I'm finding group membership not being updated. Any help much appreciated... David I think there are a bunch of OSX Lion bugs in the ticket DB that might be worth checking if this one is picked up. We've got code for some and need to do some refactoring for others. So that people understand, Apple have changed a bunch of things around DirectoryServices that caused our provider to break under Lion. I just got Lion installed recently on my laptop, and I'm planning to churn through these issues in the next few days, targeting the fixes at 2.7.x. -- Nigel Kersten Product Manager, Puppet Labs *Join us for **PuppetConf * http://www.bit.ly/puppetconfsig Sept 22/23 Portland, Oregon, USA. * * -- 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. 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] OS X Lion group membership not updated
Hi Doug, Yep, I did the work on that and it was merged in around 2.7.10, I believe -- http://projects.puppetlabs.com/issues/11293 Can you provide me with what specific error you're getting, the version of OS X you're running, and the versions of Facter/Puppet you're using? On Fri, Jan 25, 2013 at 2:33 PM, d...@ebackpack.com wrote: Sorry to revive an old thread, but this seems to be the only other thing I can find on this exact issue I'm having. Nigel - do you have any idea if the fixes have ever made it into a 2.7.x release? I'm using 2.7.20 (as that's what is used in our non-OSX hosts) and still getting this same error. Thanks! Doug On Wednesday, September 7, 2011 8:07:00 AM UTC-5, Nigel Kersten wrote: On Tue, Sep 6, 2011 at 12:42 PM, James Turnbull ja...@puppetlabs.comwrote: David Thompson wrote: Switching to puppet (2.7.3) for managing my OS X Lion systems, I'm finding group membership not being updated. Any help much appreciated... David I think there are a bunch of OSX Lion bugs in the ticket DB that might be worth checking if this one is picked up. We've got code for some and need to do some refactoring for others. So that people understand, Apple have changed a bunch of things around DirectoryServices that caused our provider to break under Lion. I just got Lion installed recently on my laptop, and I'm planning to churn through these issues in the next few days, targeting the fixes at 2.7.x. -- Nigel Kersten Product Manager, Puppet Labs *Join us for **PuppetConf * http://www.bit.ly/**puppetconfsig http://www.bit.ly/puppetconfsig Sept 22/23 Portland, Oregon, USA. * * -- 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. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- Gary Larizza Professional Services Engineer -- 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. 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] Announce: Puppet 3.1.0-rc2 Available!
Puppet 3.1.0-rc2 is a feature release candidate for the 3.x series of Puppet. To see a list of the issues addressed by this release, check out the 3.1.0 version in our issue tracker at: https://projects.puppetlabs.com/versions/288 This is the first minor release in the Puppet 3 series. It introduces some new functionality and fixes a number of bugs, but is intended to be completely backwards-compatible with 3.0. There will be no further 3.0.x point releases, so any current Puppet 3 users should upgrade to 3.1.0. For users upgrading from a 2.x series release, please read through the [long-form Puppet 3 release notes](http://docs.puppetlabs.com/puppet/3/reference/release_notes.html) for a full list of new features, deprecations, and backwards-incompatible changes. Downloads are available at: * Source https://downloads.puppetlabs.com/puppet/puppet-3.1.0-rc2.tar.gz Available in native package format in the pre-release repositories at: http://yum.puppetlabs.com and http://apt.puppetlabs.com For information on how to enable the Puppet Labs pre-release repos, see: http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#enabling-the-prerelease-repos Gems are available via rubygems at https://rubygems.org/downloads/puppet-3.1.0.rc2.gem or by using `gem install puppet` Mac packages are available at https://downloads.puppetlabs.com/mac/puppet-3.1.0-rc2.dmg Windows packages are available at https://downloads.puppetlabs.com/windows/puppet-3.1.0-rc2.msi Please report feedback via the Puppet Labs Redmine site, using an affected puppet version of 3.1.0-rc2: https://projects.puppetlabs.com/projects/puppet/ === ## Puppet 3.1.0-rc2 Contributors ## === Aaron Hicks, Andrew Parker, Branan Purvine-Riley, Chris Barker, Dave Dash, Dustin J. Mitchell, Eric Sorenson, Erik Dalén, Henrik Lindberg, Jeff McCune, Joachim de Groot, John Julien, Josh Cooper, Lauri Tirkkonen, Matthaus Owens, Michael Hall, Moses Mendoza, Nick Fagerlund, Nick Lewis, Patrick Carlisle, Paul Morgan, Peter Eisentraut, Rahul Gopinath, Ryan Uber, Stefan Schulte, Steven Lindberg, mruzicka ## Puppet 3.1.0-rc2 Release Notes ## ### Ruby DSL Deprecated, new Puppet Ruby DSL removed We introduced deprecation warnings for the (not-well-documented, mostly-unused) Ruby DSL; if you are using the Ruby DSL in production we want to hear from you to learn what you're doing with it -- please reply to this message on puppet-...@googlegroups.com! Additionally, after testing the revamped Ruby DSL that was in RC1, we made the call not to ship it. This was a tough decision, but the number and severity of issues that came up in exploratory testing led us to the conclusion that it was not supportable code. Again, if there are issues you run into with the Puppet DSL that you wanted to solve with the Ruby DSL, we want to hear about this on the puppet-dev mailing list. ## Headline Features ### Improvements When Loading Ruby Code A major area of focus for this release was loading extension code. As people wrote and distributed Faces (new puppet subcommands that extend Puppet's capabilities), bugs like [#7316](https://projects.puppetlabs.com/issues/7316) started biting them. Additionally, seemingly simple things like retrieving configuration file settings quickly got complicated, causing problems both for Puppet Labs' code like Cloud Provisioner as well as third-party integrations like Foreman. The upshot is that it's now possible to fully initialize puppet when using it as a library, loading Ruby code from Forge modules works correctly, and tools like puppetlabs_spec_helper now work correctly. ### YARD API Documentation To go along with the improved usability of Puppet as a library, we've added [YARD documentation](http://yardoc.org) throughout the codebase. YARD generates browsable code documentation based on in-line comments. This is a first pass through the codebase but about half of it's covered now. To use the YARD docs, simply run `gem install yard` then `yard server --nocache` from inside a puppet source code checkout (the directory containing `lib/puppet`). ### YAML Node Cache Restored on Master In 3.0.0, we inadvertently removed functionality that people relied upon to get a list of all the nodes checking into a particular puppet master. This had actually flip-flopped a few times but now it's enabled for good, added to the test harness, and available for use as: # shell snippet export CLIENTYAML=`puppet master --configprint yamldir` puppet node search * --node_terminus yaml --clientyamldir $CLIENTYAML ### Other bugfixes and improvements In addition to the headline features, Puppet 3.1 includes a number of improvements and bugfixes, many of which were community-contributed -- many thanks to the community members who submitted documentation, test, and code improvements. Some of the more interesting ones follow. * The Solaris
[Puppet Users] Extending a standard type
I'm trying to extend the standard 'user' type to add maintenance of some of
the contents of a user's home directory, and I'm trying to avoid creating
an entirely new custom type if I can. The approach I'm taking is to create
a site::user defined type which in turns calls the standard user type. I'm
having a problem figuring out how to manage the optional parameters.
The most likely path seems to be something like this (simplified for
example):
define site::user (
$comment,
$ensure,
$home,
$name = $title,
$password,
) {
user { $title:
comment = $comment,
ensure = $ensure,
home = $home,
name = $name,
password = $password,
}
}
The problem with this, of course, is that the parameters to site::user
aren't optional, and I'd like them to be. I've tried setting their
defaults to null strings, but I get errors about reassigning variables if I
do that.
Of course, this would be even better.. but doesn't appear to be a valid
syntax in puppet:
define site::user ( $**args ) {
user { $title:
$args
}
}
This seems to me to be the sort of thing that'd be in a puppet cookbook,
but google hasn't shown me any useful docs or examples for what I'm trying
to do. Does this approach even make sense, or is there a better way?
--
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.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
