Puppet Compatibility
Version 6 (T.J. Yang, 03/13/2011 01:47 pm)
| 1 | 1 | # Will Puppet Work on My System? |
|
|---|---|---|---|
| 2 | 1 | ||
| 3 | 1 | Puppet can be used to manage any POSIX or nearly-POSIX system at |
|
| 4 | 1 | the OS-level, but many of the |
|
| 5 | 5 | Nick Fagerlund | [[Glossary\_Of\_Terms#provider|providers]] , which |
| 6 | 1 | interface with other system management utilities, are |
|
| 7 | 1 | platform-specific. Detailed information about which platforms |
|
| 8 | 1 | Puppet has been most successful in supporting can be found on the |
|
| 9 | 1 | [[Stable Platforms]] page. |
|
| 10 | 1 | ||
| 11 | 1 | There is currently no official support for Windows-based operating |
|
| 12 | 6 | T.J. Yang | systems, see [[Puppet Windows]]. |
| 13 | 1 | ||
| 14 | 1 | # Can I Use Puppet to Manage *X*? |
|
| 15 | 1 | ||
| 16 | 1 | Chances are, the answer is yes, but our community maintains a |
|
| 17 | 1 | [[Managed By Puppet]] page, a list of software solutions we have |
|
| 18 | 1 | been successful managing with Puppet. |
|
| 19 | 1 | ||
| 20 | 1 | # Does Puppet Work Identically on Every System? |
|
| 21 | 1 | ||
| 22 | 5 | Nick Fagerlund | Puppet lets you use the same [[Glossary\_Of\_Terms#type|types]] |
| 23 | 4 | Simon Hürlimann | to accomplish the same task on different machines with |
| 24 | 1 | potentially different utilities installed. For example, given |
|
| 25 | 1 | simply a description of what package you'd like installed, Puppet |
|
| 26 | 1 | knows to use apt to install the package on a Debian system, but |
|
| 27 | 1 | would use yum to install the same package on a Red Hat system. |
|
| 28 | 1 | ||
| 29 | 1 | Because system utilities don't always offer the same features, not |
|
| 30 | 5 | Nick Fagerlund | every [[Glossary\_Of\_Terms#provider|provider]] provides |
| 31 | 1 | the same functionality. For instance, not every package provider |
|
| 32 | 1 | supports uninstalls. The |
|
| 33 | 1 | [provider functionality charts](ProviderSuitabilityReportTest) |
|
| 34 | 1 | provide a clear picture of what functionality can be expected from |
|
| 35 | 1 | different providers. |