Puppet，是基于Ruby的一个工具，可以集中管理每一个重要方面，使用的是跨平台的规范语言，管理所有单独的元素，通常聚集在不同的文件，如用户， CRON作业，和主机一起的离散元素，如包装，服务和文件。
Puppet的简单陈述规范语言的能力提供了强大的classing制定了主机之间的相似之处，同时使他们能够提供尽可能具体的必要的，它依赖的先决条件和对象之间的关系清楚而明确。
发布3.2.3正式版。2013-07-16上个版本是2013-06-19的3.2.2。其他产品线3.1.1 3.0.2 2.7.22 2.6.18 修正一些Windows平台上的bug以及一些性能问题和一些杂项Bug.
完全改进：
Puppet 3.2.3
Released July 15, 2013.
3.2.3 is a bugfix release of the Puppet 3.2 series. It fixes some Windows bugs introduced in 3.2.0, as well as a few performance problems and miscellaneous bugs.
Windows Fixes
This release fixes several Windows bugs that couldn’t be targeted for earlier 3.2 releases.
- #20768: windows user provider can not manage password or home directory — This was a regression in 3.2.0/3.2.1.
- #21043: runinterval setting in puppet.conf ignored on Windows in Puppet 3.2.1 — This was a regression in 3.2.0/3.2.1.
- #16080: Service provider broken in Windows Server 2012 — This affected all previous Puppet versions.
- #20787: ‘puppet resource group’ takes incredibly long on Windows — This affected all previous Puppet versions.
- #20302: Windows File.executable? now returns false on ruby 1.9
- #21280: Don’t create c:\dev\null in windows specs — This was only relevant to Puppet developers.
Logging and Reporting Fixes
- #20383: Bring back helpful error messages like prior to Puppet 3 — This was a regression from 3.0.0, which caused file names and line numbers to disappear from duplicate resource declaration errors.
- #20900: tagmail triggers in –onetime mode without changes after upgrade from 3.1.1 to 3.2.1 — This was a regression in 3.2.0/3.2.1.
- #20919: Logging behaviour issues in 3.2.1 — This was a regression in 3.2.0/3.2.1, which caused noisy logging to the console even if the--logdestoption was set.
Performance Fixes
- #21376: Stack level too deep after updating from 3.1.1 to 3.2.2 — This would sometimes cause total failures when importing a large number of manifest files (such as with theimport nodes/*.ppidiom).
- #21320: Puppet daemon may sleep for 100 years after receiving USR1 on 64 bit systems — MCollective’s Puppet plugin uses puppet agent’s USR1 signal to trigger a run if the agent is running; on 64-bit systems, this could cause puppet agent to keep running, but stop doing scheduled configuration runs. This was caused by a bug in Ruby < 2.0, but we modified Puppet to work around it.
- #20901:puppet --versionis unnecessarily slow — This was a regression in 3.2.0/3.2.1.
