Thanks everyone,
Zones: I have been reading some of the documentation, but the requirement that
each customer/zone needs own IP feels too "bloated". There are already half a
million customers in LDAP, and even though the load on CGI and FTP servers is
only a fraction of that, it feels unwieldy.
I tend to agree that zones are probably your best bet, but in the interest of
providing other solutions you might also consider using the ChrootDirectory
functioniality in sshd (you'll need OpenSolaris for this). You can then make
user by user config changes to your sshd_config (it'll be annoyin
On 04/20/10 04:39, Jorgen Lundman wrote:
Hmm that is interesting. We used Zones on the test version of the clusters, and found that at around 6 zones on a 4 core 2GHz intel, it became painfully slow.
But perhaps we set that up incorrectly, or just with a very early version of zones (snv_40)
On 04/20/10 03:24, Jorgen Lundman wrote:
Solaris 10/OpenSolaris x86
Customer data on NFSv4 from x4540s.
Researching various ways to setup a SSH cluster for customers, for full shell access (to compile, and crontab etc).
But it would be "nicer" if I could somehow restrict what the customer
On Tue, Apr 20, 2010 at 3:39 AM, Jorgen Lundman wrote:
> Hmm that is interesting. We used Zones on the test version of the clusters,
> and found that at around 6 zones on a 4 core 2GHz intel, it became painfully
> slow.
>
> But perhaps we set that up incorrectly, or just with a very early versio
Hmm that is interesting. We used Zones on the test version of the clusters, and
found that at around 6 zones on a 4 core 2GHz intel, it became painfully slow.
But perhaps we set that up incorrectly, or just with a very early version of
zones (snv_40).
Can Zones then be made very lightweight, as
On Tue, Apr 20, 2010 at 8:24 AM, Jorgen Lundman wrote:
> Solaris 10/OpenSolaris x86
> Customer data on NFSv4 from x4540s.
>
> Researching various ways to setup a SSH cluster for customers, for full shell
> access (to compile, and crontab etc).
Use zones.
> But it would be "nicer" if I could som
[...]
> Solaris Zones is not a realistic options, with some
> 200-300 customers per server. (Solaris zones tend to
> handle 5-10 per server before becoming unusable).
That would depend on memory (and core or thread count),
I would think. ISTR reading about someone creating
100 or more zones on a
Solaris 10/OpenSolaris x86
Customer data on NFSv4 from x4540s.
Researching various ways to setup a SSH cluster for customers, for full shell
access (to compile, and crontab etc).
But it would be "nicer" if I could somehow restrict what the customer sees of
other customers. Ie, Privacy laws, and
