Skip to main content

HP: Blades Virtualization on cClass Chassis with Virtual Connect Technology



Blades really want revenge real bad. When I look at the blades project we started a coupel of years back, it just kind of died down in out test environment. It still runs but no one has even come to testing it.

Well HP is hell bent to change that. Look at what El Registero is reporting...


In short, Virtual Connect maps all of your storage area network connections to the blade chassis rather than individual blades. So, you can pop blades in and out all day – or until someone notices – without having to reconfigure the servers' storage ties.

As it turns, HP only "laid the foundation" for Virtual Connect at the c-Class product launch. The Ethernet and Fibre Channel modules that really make the technology work only went on sale this month.


The blades are coming back, but are you ready to welcome them too?

Check out the rest...

From the PDF:

HP Virtual Connect – Breaking down barriers to change HP Virtual Connect modules for HP BladeSystem make LAN and SAN connections available to a pool of up to 64 servers, allowing administrators to define a server’s I/O connections to independently manage blade servers and their connectivity. Connections and configurations between server blades and the LAN and SAN can then be deployed at the click of a button, and migrated to another server bay instantly – all without disturbing the LAN or the SAN settings or administrators. Provisioning and maintenance time are slashed, productivity is improved, and customers gain the ability to more easily pool server resources.
Labels:

Comments

Post a Comment

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
Post a Comment
Read more

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
Post a Comment
Read more