Add puppetserver support

[danieldreier]

This somewhat duplicates the PR I submitted, but I wanted to track work, outstanding tasks, and resources of use toward adding puppetserver support.

Relevant Documentation

Known Issues
Puppet Server vs. Apache/Passenger Puppet Master
Puppet Server Configuration
Configuring The Webserver Service
Puppet Server and Gems
External CA configuration
External SSL termination

Known Challenges

• The /etc/puppetserver/bootstrap.cfg config file uses an odd syntax; stdlib file_line is probably an easier way to handle this than writing a new augeas lens.
• Gems in the new master are in a different place to isolate them; see Puppet Server and Gems for details. We may want to add a new package provider to wrap that command to allow us to manage gems in the new environment.
• The new master service takes longer to start, but the init scripts are non-blocking, so testing with beaker will require workarounds to watch log files or wait a fixed amount of time.

Features To-Do

• Determine expected paths on supported platforms for files that correspond to /etc/puppetserver/bootstrap.cfg, /etc/default/puppetserver, /etc/puppetserver/conf.d, etc.
• Add ability to configure puppetserver webserver
• CSR signing proxying
• Handle directory environments deprecation
• Manage static file serving via embededed webserver to serve puppet explorer
• Need to identify which puppet.conf features are not supported in puppetserver and handle those specially

What else? I'm adding this for discussion / tracking rather than trying to dictate how we handle puppetserver.

[igalic]

given the realease of puppetserver 2.0, i think it's time to revisit this.