[Swift-devel] Re: Issues to resolve for new coaster modes

[Mihael Hategan]

I think uI'll need to tackle these, but for low hanging fruits, maybe
-nosec and the ssh passphrase.

Mihael


On Tue, 2010-08-31 at 09:49 -0600, wilde at mcs.anl.gov wrote:
> Here's the issues that I am aware of so far. Many of these need more discussion and/or debug/reproduction info.
> 
> - -nosec doesnt seem to work on coaster-service command
> 
>   alternative: a wrapper script automatically installs an insecure SimpleCAbased proxy and necessary CA certs. We're using wrappers anyways, to start manual workers.
> 
> - need -passive option on coaster-service command (for now, can run a dummy swift job to force coaster service into passive mode?)
> 
> - file protocol for coaster provider staging seems broken
> 
> - -port option on coaster-service command seems to print confusing messages and its unclear how the specified port vs the default port is being used (try to probe with netstat).
> 
> - its unclear how to specify URIs for the service in sites.xml, in particular http: vs https: protocol and ports. Both are printed by the service: which to use?
> 
> - still need an easy way to enable users to use remote coasters without an X509 certificate
> 
> - in initial tests, the persistent coaster service seemed to work for a few swift commands, then hung or stopped responding. Workers timed out? Need to reproduce this and check logs.
> 
> - in initial tests, both David and Mike have seen coaster service go into a rapid heartbeat (~ 1 per sec) mode.
> 
> - distantly related: verify if ssh to a set of hosts that use the same ssh key only request the passphrase once from the user. If not, can that caching be implemented to avoid multiple passphrase entry?
> 
> David, do you have additional issues, or clarifications/details on any of these?
> 
> Mihael, and suggestions for approaches on any of these that are low hanging fruit which people other than you can work on?
> 
> 
>