Bug 473008

The feature is designed such that 'yum install condor-ec2-enhanced' will install all components necessary for the feature to run, which includes condor.  However, since all the RPMs aren't in RHN yet, it isn't possible to do this and more manual installation is needed.  From a documentation perspective though, all that should be needed is to say 'yum install condor-ec2-enhanced'.

1. These are just standard public/private RSA keys.  If we need to provide documentation on how to create them, we can add these steps in a note or something:
Create a private key file called 'private key': 'openssl genrsa -out private_key 1024'
Generate a public key file called 'public_key': 'openssl rsa -in private_key -out public_key -pubout'

2. These changes can go in any condor configuration file.  We should use the convention used throughout the document when discussing adding configuration entries to condor's configuration.

There is no need to edit the condor configuration files any more than is documented.  We could reduce the daemons running on the AMI or provide default configs, but this really won't do much other than complicate the installation process.

From Rob's "1" above - yes add the following to step 1 - perhaps in the hint box:

The keys required are NOT the AWS keys needed elsewhere. Generate public and private keys using openssl:

1. openssl genrsa -out private_key 1024
2. openssl rsa -in private_key -out public_key -puboutrs

In response to Rob's points in 2 above:

True changes can go into either configuration file but we should say that and perhaps make a recommendation. (Remembering that elsewhere we recommend few changes to the /etc/condor/condor_config).

The changes described in the following steps (2-5) should be made to a condor configuration file. It is recommended to add these variables to the local configuration (/var/lib/condor/condor_config/local).

woops that's condor_config.local not condor_config/local above.

(In reply to comment #1)
> The feature is designed such that 'yum install condor-ec2-enhanced' will
> install all components necessary for the feature to run, which includes condor.
>  However, since all the RPMs aren't in RHN yet, it isn't possible to do this
> and more manual installation is needed.  From a documentation perspective
> though, all that should be needed is to say 'yum install condor-ec2-enhanced'.
> 
> 1. These are just standard public/private RSA keys.  If we need to provide
> documentation on how to create them, we can add these steps in a note or
> something:
> Create a private key file called 'private key': 'openssl genrsa -out
> private_key 1024'
> Generate a public key file called 'public_key': 'openssl rsa -in private_key
> -out public_key -pubout'

<listitem>
	<para>
		Create a private key file called <parameter>private key</parameter>:
<screen>
$ openssl genrsa -out private_key 1024
</screen>
		Create a public key file called <parameter>public_key</parameter>:
<screen>
$ openssl rsa -in private_key -out public_key -pubout
</screen>
        </para>
	<para>
		The must be placed on the EC2 AMI at <filename>/root/.ec2/rsa_key</filename>. This private key must match the public key set in <filename>set_rsapublickey</filename> for a given route or job.
	</para>
</listitem>

> 
> 2. These changes can go in any condor configuration file.  We should use the
> convention used throughout the document when discussing adding configuration
> entries to condor's configuration.
> 
> There is no need to edit the condor configuration files any more than is
> documented.  We could reduce the daemons running on the AMI or provide default
> configs, but this really won't do much other than complicate the installation
> process.

<listitem>
	<para>
		The following changes can be specified in any condor configuration file:
	</para>
	<para>
		Specify the location of the <command>condor .... [etc]

LKB

(In reply to comment #2)
> From Rob's "1" above - yes add the following to step 1 - perhaps in the hint
> box:
> 
> The keys required are NOT the AWS keys needed elsewhere. Generate public and
> private keys using openssl:
> 
> 1. openssl genrsa -out private_key 1024
> 2. openssl rsa -in private_key -out public_key -puboutrs

<note>
	<para>
		These keys are generated using openssl, and are not the same as the AWS keys needed elsewhere.
	</para>
</note>

LKB

(In reply to comment #3)
> In response to Rob's points in 2 above:
> 
> True changes can go into either configuration file but we should say that and
> perhaps make a recommendation. (Remembering that elsewhere we recommend few
> changes to the /etc/condor/condor_config).
> 
> The changes described in the following steps (2-5) should be made to a condor
> configuration file. It is recommended to add these variables to the local
> configuration (/var/lib/condor/condor_config/local).

<para>
	The following changes can be specified in any condor configuration file, however it is recommended that they are added to the local configuration file at <filename>/var/lib/condor/condor_config/local</filename>:
</para>
<para>
	Specify the location of the <command>condor_sta...[etc]

LKB