Hi Neil,

Coda should suit well, if you only serve static files from there.

You do not need multiple replication of Coda servers,
2 or 3 is enough, as the clients cache the files being
used and survive even if all servers would disappear.

Availability of SCM does not influence the availability
of the file service, only the possibility to change the configuration
(create/remove volumes or Coda accounts)

On Thu, Mar 24, 2011 at 10:46:16AM -0500, Neil Aggarwal wrote:
> 1. Does the SCM need to run on a Coda server?

I assume you mean "Coda file server". Well, no. SCM is just the place
of the master copy of the Coda databases (the "update" service), this has
nothing to do with the file or authentication service. The usual choice
is though to run both services (file and authentication) on each of the
hosts designated as "Coda servers". The db-update service is normally
run on one of those machines (all of them have identical copies of the
databases anyway) and the machine is then called SCM.

> 2. Is it possible to run more than one SCM in a
>   master/slave setup? 

See above.
Coda servers exchange the internal databases in a master/slave fashion
and SCM means "the master".

Regards,
Rune