Hi all, We've gotten LDOMs up and running on murphy \o/ It's currently laid out as follows: -------------------------------------------------------- Control 136.206.15.14 murphy.redbrick 4VCPUs (1 core), 1GB RAM This is what has become of our original solaris install -------------------------------------------------------- Webserver 136.206.15.31 murphy-ldg1.redbrick (not set yet) 16VCPUs (4 cores), 10GB RAM To be a webserver/login machine? -------------------------------------------------------- (Unused) 12 VCPUs (3 cores), 5GB RAM Maybe a databases LDOM, and another one for tiny services? -------------------------------------------------------- This is just a starting point, and the result of me playing with things. I'd suggest a few things.. one, that we give the name "murphy.redbrick" to the webserver/login machine, as that's what we'll be letting users log into. Also give it the .14 IP. Give all LDOMs an IP in the .30-.40 range (so, give control .30, and webserver .31 *and* .14). We can reassign resources as we see fit without reinstalling things. Memory can be added or removed to a domain with a reboot of that domain, and cores/VCPUs can even be hotswapped :) And we can have up to 32 of these things. Although I'd be against assigning VCPUs in chunks of less than four, otherwise you'll get contention for core resources (4 VCPUs/threads per core). The "ldg1" thing is just a suggestion from the sun LDOM manual.. maybe give the control domain -ldg0 or something. Then the next ldom ldg2..etc.. I'd still like us to add some more LDOMs to play with and do things with. We saved a load of resources on the control domain by not using ZFS. LDOM images are being stored in /ldoms/ldgX/bootdisk.img on the control domain. LDOM management stuff is stored in /opt/SUNWldm/bin on the control domain, and controlled by the service ldmd. Serial access to the guest ldoms is available by telnetting to localhost:5000 from the control domain (we should *never* let users log in here). You'll also notice that Solaris has gone into nazi mode, being strict about password strength, and things, because it's the control domain. To any admins interested in setting up an LDOM to play with, read the LDOM manual :) We're using version 1.0.3 if anything asks. Oh, also, the latest T2000 firmware update (which ldoms required) has made our CD-ROM drive disappear. Go figure. Nothing's been installed in the guest domain that's been set up yet. Em...yes..that's about it I think. I'm half asleep so this may not be the most coherent email I've written in a while. -Andrew On Wed, May 28, 2008 at 02:18:27PM +0100, Andrew Martin wrote:
The whole thing runs Solaris :P
On Wed, May 28, 2008 at 02:01:16PM +0100, Andrew Harford wrote:
On Wed, May 28, 2008 at 01:56:04PM +0100, Andrew Martin wrote:
Yeap, that was my thinking too. We could give away 2 or 3GB of that to the web server/login server. The major benefit is the ability to snapshot/clone with ease, but that's just administrative nicities when you think about it.
As for resource allocation, we can actually add or remove resources (CPU/RAM) to each LDOM after it's been created anyway, and it'll take effect the next time that LDOM is rebooted.
This all seems too nice and easy, there must be a catch somewhere ;)
-- Andrew Harford CA3 Class Rep System Administrator, DCU Networking Society Ordinary Member, Societies & Publications Committee
What we were after now was the old surprise visit. That was a real kick and good for laughs and lashings of the old ultraviolence. -- Alex (A Clockwork Orange)
-- RedBrick/Gamessoc/Filmsoc Webmaster 08/09
_______________________________________________ Admin-discuss mailing list Admin-discuss@lists.redbrick.dcu.ie http://lists.redbrick.dcu.ie/mailman/listinfo/admin-discuss
-- RedBrick/Gamessoc/Filmsoc Webmaster 08/09