On Thu, Jan 28, 2010 at 07:49:18AM -0000, Thierry Carrez wrote:
> The NC additional preseed (downloaded from the CC) contains the CC host
> eucalyptus public key, which is generated at CC host install time. So
> your preseed would probably miss that.
>
I'd add a late_command that would automatically provide a well-known
public/private key for the eucalyptus user to all installations. Granted it's
not the safest thing to do, but for testing purposes it would help (this is
what I do in the puppet recipes).
> Could you explain the use case for installing, with the UEC installer, a
> NC in a cloud without CC ? You'd be better off doing a regular server
> install and choose the cloud node task, if you want to bypass what
> eucalyptus-udeb does completely.
>
I'd rather fire off all systems to install what they're supposed to be and not rely on having the systems to be installed in specific sequence:
1. Install CLC
2. Once CLC is installed, install CC+SC, install Walrus
3. Once CC+SC is installed, install all NCs.
Automating the installation of multiple systems as a sequence is harder than
firing off all the systems at the same time and wait for the infrastructure to
settle (thanks to auto-registration).
The main usage of the option is to facilitate automated testing. There doesn't
even need to be a question asked. Having the possibility to preseed it is
enough.
Hi Thierry,
On Thu, Jan 28, 2010 at 07:49:18AM -0000, Thierry Carrez wrote:
> The NC additional preseed (downloaded from the CC) contains the CC host
> eucalyptus public key, which is generated at CC host install time. So
> your preseed would probably miss that.
>
I'd add a late_command that would automatically provide a well-known
public/private key for the eucalyptus user to all installations. Granted it's
not the safest thing to do, but for testing purposes it would help (this is
what I do in the puppet recipes).
> Could you explain the use case for installing, with the UEC installer, a
> NC in a cloud without CC ? You'd be better off doing a regular server
> install and choose the cloud node task, if you want to bypass what
> eucalyptus-udeb does completely.
>
I'd rather fire off all systems to install what they're supposed to be and not rely on having the systems to be installed in specific sequence:
1. Install CLC
2. Once CLC is installed, install CC+SC, install Walrus
3. Once CC+SC is installed, install all NCs.
Automating the installation of multiple systems as a sequence is harder than
firing off all the systems at the same time and wait for the infrastructure to
settle (thanks to auto-registration).
The main usage of the option is to facilitate automated testing. There doesn't
even need to be a question asked. Having the possibility to preseed it is
enough.
-- www.ubuntu. com
Mathias Gug
Ubuntu Developer http://