Skip to main content

VMware love stories: Sunray marries ESX

Unix Admin reports:

The entire sollution sits in two racks, we will scale to 450 DTU's, and we are in the process of installing a system to support another 1200 dtu's with this configuration. The limitation of the ESX Server is not CPU, but memory. Our Future plans are to migrate to 128GB of RAM, onece the memory becomes available. If you have any questions or want more specifics let me know. We run both LAN dtu's and remote. We have 500 remote Sun Rays that are BootP relayed to the mothership (Sun ray server) from switches. We have more than 100 dtu's in a building, I put local Sun Ray servers. The windows servers are allways remote and accessed via RDP.


And it all started with a RDP dilemma! Read more...

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op