Improvements to chef-client firstboot script
 - Chef for network connectivity before going ahead with the chef-client download. This is to resolve what I've found to be a common cause of the firstboot script failure.
 - Make the use of validation_client_name optional.
 - If a server role is set, use it.
 - Use the proper service start convention, instead of the init.d script directly.
 - Some remarks for posterity.
Adding one more symlink for trusty
Adding lanplus as the default interface type
fixing bootdev selection to be first drive
adding 5 tries for ipmi, because. ipmi.
Merge pull request #43 from hughsaunders/rekick_cluster_by_name

Match cluster name in rekick cluster API
Merge pull request #44 from hughsaunders/configurable_ssh_keys

Add SSHkey model with FK from Host
Merge pull request #40 from jcannava/master

Adding one more symlink for trusty
Merge pull request #35 from odyssey4me/chef-client-firstboot

Improvements to chef-client firstboot script
Local Changes

These were local changes made in a lab djeep deploy that had not been
committed upstream and consequently prevent further pulls.