bz#1152516 don't autostart networking in discovery image

per https://groups.google.com/forum/#!topic/foreman-dev/wg0ETtQBH9k

Signed-off-by: Mike Burns <mburns@redhat.com>
Merge pull request #104 from mburns72h/discovery-no-net

bz#1152516 don't autostart networking in discovery image
Add staypuft-client-installer

Existing staypuft-installer now generates answer file for client
installer. Client installer prepares puppet on target machine and
registers itself in staypuft.

Generates SSH Key for foreman-proxy user and configures the
foreman-proxy service to use puppetssh

It creates foreman .ssh directory and copies the private ssh key
from the foreman-proxy user. This allows DynFlow tasks running as
foreman user to ssh into host machines, allow tasks to test that ssh is
fully configured.
no-daemonize puppetssh commmand

Service puppet stop kills any running puppet agent daemon.  This is
causing any --onetime puppetssh runs to fail mid run when trying to stop
the agent service.  Running in non daemon modes prevents this.
Remove get_ready implementation from ProvisioningWizard

The base class implementation does the same thing. There is no need to
override in the subclass. The subclass implementation has unknown
constants and does not work.
Fix a syntax error
Pass settings as string when using Foreman > 1.6
Make the RPM installable on RHEL 7
Rename param to staypuft_ssh_public_key for consistency

(for consistency with already existing ssh_public_key)
Set staypuft_ssh_public_key as a host parameter

and still keep it set in a smart class parameter in case some host group
includes the foreman::plugin::staypuft_client class.

The problem with previous approach was that if the host was
provisioned without foreman::plugin::staypuft_client puppet class
assigned to it, setting of the authorized key for puppetssh would fail
and the host would be "bricked" until either reprovisioned or set the
authorized key manually.
Remove puppetmaster param from staypuft_client.pp

The param is not used there, and it is not set in the answerfile,
which made it generate a default of local host's fqdn, which was
confusing and incorrect.
Wait for client registration to finish

Add "--no-daemonize" to registration puppet run so that we wait for it
to finish.

Add "-l console" so that it actually writes the output to
foreman-installer log as intended (instead of system journal).
Fail the installer if the registration puppet run fails
Wait for certificate to allow manual signing
Workaround for http://projects.theforeman.org/issues/7975
Revert "bz#1152516 don't autostart networking in discovery image"

This reverts commit 91b9f0d0876d86daadffb3bb54c39c42790b6d4a.
due to rhbz#1155665
BZ #1157819: Set DEFROUTE=no on all interfaces by default

https://bugzilla.redhat.com/show_bug.cgi?id=1157819

Only set DEFROUTE=yes on the gateway interface, and ensure that all other
interfaces have DEFROUTE=no
Merge pull request #107 from bcrochet/bz/1157819

BZ #1157819: Set DEFROUTE=no on all interfaces by default
Correct the config when a bond and vlan are used together

When a bond and a vlan are used together, and the subnet assigned to
the vlan is not set to dhcp mode, there is no IP info for the
bond interface itself. It is gathered and attached on the vlan
interface. This checks that the bond is actually assigned to a subnet
before trying to write out static IP information.
Merge pull request #108 from bcrochet/bond_and_vlan

Correct the config when a bond and vlan are used together