First incomplete pass on PE 1.2 manual

This commit adds a partial manual for Puppet Enterprise 1.2. There are several
chapters still pending at this time.

Author: nfagerlund

source/pe/1.2/answer_file_reference.markdown

@@ -1,5 +1,12 @@
-Appendix A: Answer File Reference
-=================================
+---
+layout: default
+title: "PE Manual: Answer File Reference"
+---
+
+{% include pe_nav.markdown %}
+
+Answer File Reference
+=====================
 
 When run with the `-a` or `-A` flag and a filename argument, the Puppet Enterprise installer will read its installation instructions from an answer file. `-a` will use the provided answer file to perform a non-interactive installation (which will fail if any required variables are not set), and `-A` will perform a partially-interactive installation, prompting the user for any missing answers. 
 

source/pe/1.2/images/dashboard/01.addclass.png

@@ -0,0 +1,6 @@
+---
+layout: default
+title: "PE Manual: Index"
+---
+
+{% include pe_nav.markdown %}

source/pe/1.2/images/general/dashboard-addclass.png

@@ -3,6 +3,8 @@ layout: default
 title: "PE Manual: Introduction"
 ---
 
+{% include pe_nav.markdown %}
+
 Welcome to Puppet Enterprise!
 =============================
 
@@ -22,7 +24,7 @@ System Requirements
 
 Puppet Enterprise 1.2 supports the following operating system versions:
 
-|     Operating system         |  Version                  |       Arch        |   Support    |
+|       Operating system       |          Version          |       Arch        |   Support    |
 |------------------------------|---------------------------|-------------------|--------------|
 | Red Hat Enterprise Linux     | 5 and 6                   | x86 and x86\_64   | master/agent |
 | Red Hat Enterprise Linux     | 4                         | x86 and x86\_64   | agent        |
@@ -35,31 +37,24 @@ Puppet Enterprise 1.2 supports the following operating system versions:
 | SUSE Linux Enterprise Server | 11                        | x86 and x86\_864  | master/agent |
 | Solaris                      | 10                        | SPARC and x86\_64 | agent        |
 
-Puppet's hardware requirements will depend heavily on the number of resources you are managing, but in general, you can expect a 2-4 CPU puppet master with 4GB of RAM to manage approximately 1,000 agent nodes. <!-- TK get this vetted -->
-
-Licensing
-------
-
-Puppet Enterprise can be evaluated with a complementary ten-node license; beyond that, a commercial per-node license is required for use. A license key file will have been emailed to you after your purchase, and the puppet master serving as the certificate authority will look for this key at `/etc/puppetlabs/license.key`. Puppet will log warnings if the license is expired or exceeded, and you can view the status of your license by running `puppet license` at the command line on the puppet master. 
-
-To purchase a license, please see the [Puppet Enterprise pricing page](http://www.puppetlabs.com/puppet/how-to-buy/), or contact Puppet Labs at <[email protected]> or (877) 575-9775. For more information on licensing terms, please see [the licensing FAQ](http://www.puppetlabs.com/licensing-faq/). If you have misplaced or never received your license key, please contact <[email protected]>. 
+Puppet's hardware requirements will depend heavily on the number of resources you are managing, but in general, you can expect a 2-4 CPU puppet master with 4 GB of RAM to manage approximately 1,000 agent nodes. The ActiveMQ server, which runs on the puppet master, will require at least 512 MB of RAM for its Java VM instance.
 
 What's New in PE 1.2
 ----------
 
-Version 1.2 is a major release of Puppet Enterprise, which adds the following high-level features:
+Version 1.2 is a major release of Puppet Enterprise, which adds the following new features:
 
 ### MCollective integration
 
-Puppet Enterprise now bundles Marionette Collective, Puppet Labs' server orchestration framework.  <!-- TK what version are we using? -->
+Puppet Enterprise now bundles version 1.2.1 of Marionette Collective, Puppet Labs' server orchestration framework. 
 
 ### Puppet 2.6.9
 
-This release updates Puppet to version 2.6.9, the latest release in the stable 2.6 series. <!--tk vet this -->
+This release updates Puppet to version 2.6.9, the latest release in the stable 2.6 series.
 
 ### Accounts 1.0 Module
 
-PE now includes a ready-to-use Puppet module for managing user accounts. This module provides both a standard defined type, and a class that lets you store all account data in an external YAML file. 
+PE now includes a ready-to-use Puppet module for managing user accounts. This module provides an account defined type and an optional wrapper class that lets you store all account data in an external YAML file. 
 
 ### Stdlib 2.0 Module 
 
@@ -75,8 +70,13 @@ This helper module extends Puppet with:
 How to Get Help and Support
 --------------
 
-<!-- TK I'm not sure what goes here. -->
+If you run into trouble, you can take advantage of Puppet Labs' enterprise technical support.
+
+* To file a support ticket, go to [support.puppetlabs.com](http://support.puppetlabs.com). 
+* To reach our support staff via email, contact <[email protected]>.
+* To speak directly to our support staff, call 1-877-575-9775.
 
-### Other Documentation
+Other Documentation
+-----
 
 For help with features not specific to Puppet Enterprise, please see the [main Puppet documentation][docs] and the [MCollective documentation][mco].

source/pe/1.2/images/general/dashboard-class-for-node1.png

@@ -1,30 +1,43 @@
+---
+layout: default
+title: "PE Manual: Overview"
+---
+
+{% include pe_nav.markdown %}
+
 Overview
 =====
 
 What Is Puppet Enterprise? 
 -----
 
-Puppet Enterprise is a fully supported software distribution that bundles the Puppet family of systems management tools, adds several premium enterprise-only features, and deploys all of it in a highly scalable default configuration. 
+Puppet Enterprise is a fully supported software distribution of the Puppet family of systems management tools. It adds several premium enterprise-only features, and deploys out-of-the-box into a highly scalable production-ready configuration. 
 
-- **Puppet** is an industry-leading configuration management platform that lets you describe a desired system state as code and enforce that state on any number of machines. 
-- **MCollective** is a message-based server orchestration framework for fast parallel command execution.
-- **Puppet Dashboard** is a web interface to Puppet. It can view and analyze Puppet's reports, and can simplify the process of assigning your existing Puppet classes to nodes.
+- **Puppet** (version 2.6.9) is an industry-leading configuration management platform that lets you describe a desired system state as code and enforce that state on any number of machines. 
+- **MCollective** (version 1.2.1) is a message-based server orchestration framework for fast parallel command execution.
+- **Puppet Dashboard** (version 1.2) is a web interface to Puppet. It can view and analyze Puppet's reports, and can simplify the process of assigning your existing Puppet classes to nodes.
 - **Puppet Compliance** is an enterprise-only extension to Puppet Dashboard that enables a new auditing workflow for unmanaged resources.
-- **Facter** is a system data discovery utility used by both Puppet and MCollective. 
-- **Accounts** is a ready-to-use Puppet module for managing user accounts. 
+- **Facter** (version 1.6.0) is a system data discovery utility used by both Puppet and MCollective. 
+- **Accounts** (version 1.0.0) is a ready-to-use Puppet module for managing user accounts. 
 
-To get maximum compatibility and performance on your existing systems, PE bundles and maintains its own versions of Ruby, Apache, and all required libraries, and sequesters all included software in the `/opt/puppet` directory. This lets us enable advanced features while still shielding users from dependency conflicts, and it offers a relatively seamless transition path for users migrating from a manually maintained Puppet installation.
+To get maximum compatibility and performance on your existing systems, PE bundles and maintains its own versions of Ruby, Apache, and all required libraries, and installs all included software in the `/opt/puppet` directory. This lets us enable advanced features while still shielding users from dependency conflicts, and it offers a relatively seamless transition path for users migrating from a manually maintained Puppet installation.
 
-PE Roles
+Roles
 -----
 
 Puppet Enterprise's features are divided into three main **roles,** any or all of which can be installed on a single computer:
 
 - The **puppet agent** role should be installed on every node Puppet will be managing; it installs Puppet, and enables the puppet agent service (`pe-puppet`) that checks in with the puppet master every half-hour and applies the node's catalog. This role also installs (but doesn't automatically enable) the MCollective server, which listens and responds to messages on the ActiveMQ Stomp bus; to enable MCollective on a node, use Puppet to assign the `mcollectivepe` class to it.
-- The **puppet master** role should be installed on exactly one server at your site[^multi]; it installs Puppet, Apache, the ActiveMQ server, and the MCollective control client. Servers with this role will respond to catalog requests from puppet agent nodes (using instances of puppet master managed by the `pe-httpd` Apache service), and will act as the hub for all MCollective traffic at the site. Puppet master can be configured during installation to submit reports to and request node classifications from Puppet Dashboard.
-- The **Puppet Dashboard** role should be installed on exactly one server at your site; it installs Puppet Dashboard (with the Puppet Compliance extension), Puppet, and Apache, and configures them to respond to requests from the puppet master, serve a web interface to your site's administrators, and act as a machine inventory browser and file content viewer. The Dashboard role should usually be installed on the same machine as the puppet master role; splitting the two roles between different machines can increase performance in some situations, but will require some additional configuration.
+- The **puppet master** role should be installed on exactly one<!-- [^multi] --> server at your site; it installs Puppet, Apache, the ActiveMQ server, and the MCollective control client. Servers with this role will respond to catalog requests from puppet agent nodes (using instances of puppet master managed by the `pe-httpd` Apache service), and will act as the hub for all MCollective traffic at the site. Puppet master can be configured during installation to submit reports to and request node classifications from Puppet Dashboard.
+- The **Puppet Dashboard** role should be installed on exactly one server at your site; it installs Puppet Dashboard (with the Puppet Compliance extension), Puppet, and Apache, and configures them to respond to requests from the puppet master, serve a web interface to your site's administrators, and act as a machine inventory browser and file content viewer. Unlike the other two roles, Puppet Dashboard is an optional component of your site. The Dashboard role should usually be installed on the same machine as the puppet master role; splitting the two roles between different machines can increase performance in some situations, but will require some additional configuration.
+
+<!-- For future releases: [^multi]: A future release of PE may add support for multi-master ecosystems, but for the time being, they require significant extra configuration which won't be covered in this manual. -->
+
+
+Licensing
+------
 
+Puppet Enterprise can be evaluated with a complementary ten-node license; beyond that, a commercial per-node license is required for use. A license key file will have been emailed to you after your purchase, and the puppet master <!-- Notes for future versions where we allow multi-masters: licensing happens on the master that serves as the site's certificate authority --> will look for this key at `/etc/puppetlabs/license.key`. Puppet will log warnings if the license is expired or exceeded, and you can view the status of your license by running `puppet license` at the command line on the puppet master. 
 
-[^multi]: A future release of PE may add support for multi-master ecosystems, but for the time being, they require significant extra configuration which won't be covered in this manual.
+To purchase a license, please see the [Puppet Enterprise pricing page](http://www.puppetlabs.com/puppet/how-to-buy/), or contact Puppet Labs at <[email protected]> or (877) 575-9775. For more information on licensing terms, please see [the licensing FAQ](http://www.puppetlabs.com/licensing-faq/). If you have misplaced or never received your license key, please contact <[email protected]>. 
 
-<!-- TK don't know what else goes here. -->