On 04/20/10 04:39, Jorgen Lundman wrote:
Zones are intended to appear to be full systems - from the network's perspective. Therefore, each one needs an IP address if it will have network access.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 to not require a new IP for each zone running, and perhaps without loopback mounting? It would seem that I should add Zones back on the table and try it out for myself. (The previous Zones was done by the Jrs). Do you have a limited number of IP addresses? If so, with OpenSolaris, you might be able to use the Project Crossbow features of OpenSolaris 2009.06, including NAT. The features are described at http://hub.opensolaris.org/bin/view/Project+crossbow/ . But simply using NAT to reduce the number of IP addresses visible outside the system creates its own problems, such as non-default SSH port numbers. Another possible solution is accepting all of the logins at one IP address, and automatically logging each user into a different zone via loopback interface. I haven't thought that through, so there is probably a fatal flaw in that, also. :-( The simplest method is one zone per user, if you have the IP addresses. --JeffV --
| ||||
_______________________________________________ sysadmin-discuss mailing list sysadmin-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/sysadmin-discuss
