On Thu, Jan 28, 2010 at 11:26:16AM -0000, Thierry Carrez wrote:
> Public bug reported:
>
> On package installs, authorized_keys must be manually set on components.
> There is no point in starting publication jobs if the the component is not ready to be autoregistered.
>
> Two options:
> - Fail the publication job is authorized_keys is missing (requires the user to manually start the publication job after keys are setup)
> - Poll for authorized_keys presence in the upstart script (slightly heavier on resource usage)
>
Another option:
* fire off an upstart event when the authorized_keys file is installed on the
system (inotify?). The eucalytpus-nc job would also have to check for the
authorized_keys file and fire off the same upstart event to handle an
environment where authorized_keys has already been installed.
On Thu, Jan 28, 2010 at 11:26:16AM -0000, Thierry Carrez wrote:
> Public bug reported:
>
> On package installs, authorized_keys must be manually set on components.
> There is no point in starting publication jobs if the the component is not ready to be autoregistered.
>
> Two options:
> - Fail the publication job is authorized_keys is missing (requires the user to manually start the publication job after keys are setup)
> - Poll for authorized_keys presence in the upstart script (slightly heavier on resource usage)
>
Another option:
* fire off an upstart event when the authorized_keys file is installed on the
system (inotify?). The eucalytpus-nc job would also have to check for the
authorized_keys file and fire off the same upstart event to handle an
environment where authorized_keys has already been installed.
-- www.ubuntu. com
Mathias Gug
Ubuntu Developer http://