Issue #8268 has been updated by Josh Cooper.
>From meeting July 8th Action Items: * Team to provide Jason with machine specifications for running Windows Server 2008 R2 * Nigel to verify that 2003 support is out of scope Decisions: * Customers will be required to install ruby 1.8.7 and necessary gems prior to installing puppet. * We will try to avoid dependencies on native code, but if we end up using a gem that contains native code, customers will be required to install the RubyInstaller development kit to compile the native code. * Puppet installation can consist of ruby/batch scripts, delivered in a zip file. * ACL support will be limited to simple use cases, e.g. make this directory, all subdirectories and file, look like "this". We will not support adding or removing specific types of access control entries from the list. * We expect puppet will need to install MSI packages from a network share, e.g. UNC paths or mapped drives. * We expect puppet will be deployed in a Windows workgroup environment. Out of scope: * Running puppet agent as a windows service * Delivering executable puppet installer (MSI, Wise, etc) nor as a gem * Windows event log destination * Support for 2003 * Support for domain-joined servers ---------------------------------------- Feature #8268: Basic Puppet agent support on Windows https://projects.puppetlabs.com/issues/8268 Author: Jacob Helwig Status: Accepted Priority: Normal Assignee: Jacob Helwig Category: Target version: Affected Puppet version: Keywords: Branch: Target Platforms: ================= At a minimum we need to target Windows Server 2008 R2. Whether we support 2003 depends upon the initial technical investigation. Core Features: ============== * Full agent support talking to a master * File resource, owner, group, some form of ACL/mode support * Local User management * Local Group management * Task scheduling via Windows scheduler (new type, not as a provider for the cron type) * MSI package provider support without a central repository/WSUS. * Service management (no DACLs, just ensure/enable as per other providers) * Exec support via WinRM (and/or Powershell, depending upon initial tech evaluation) Secondary, Optional Features: ============================= * Registry management (e.g. inserting installer license keys) * Package installation via .exe installers Explicitly out of scope Features: ================================= * Puppet master support on Windows * Group Policy * Active Directory Support * Network interfaces Supporting Documentation: ========================= * [Opscode Knife using WinRM example](https://gist.github.com/4f9a34f7f8bd95dfa703) * ['Unattended' deployment tool installer functionality](http://unattended.sourceforge.net/installers.php) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
