Connect to condor after being launched by cloud scheduler

Add cloud_type to configure ephemeral storage depending on whether the
VM exosts on a nimbus, openstack or GCE cloud.  Add central_manager fact
to configure condor client to connect to the condor queue linked to the
cloud scheduler that booted the VM.  Add grid secutrity directory to
contain certificates for condor.  In the future fill these certificates
from the metadata server.

Changes:
   * new file:   condor/lib/facter/central_manager.rb
   * modified:   condor/manifests/client.pp
   * modified:   condor/templates/condor_config.local.csnode.erb
   * new file:   gce_node/lib/facter/cloud_type.rb
   * modified:   gce_node/manifests/grid_setup.pp
   * modified:   gce_node/manifests/init.pp
   * new file:   storage/manifests/init.pp
Place ephemeral storage mount in site manifest

Mount ephemeral storage in site manifest.  Remove dependence on cloud
type custom fact.  Align storage approach with Henrik's manifest for GCE
nodes. Use internal ruby functionality to establish facts.

Changes:
   * modified:   condor/manifests/client.pp
   * modified:   gce_node/manifests/init.pp
   * deleted:storage/manifests/init.pp
   * modified:   condor/lib/facter/central_manager.rb
   * modified:   gce_node/lib/facter/cloud_type.rb