Krishnan Subramanian's Library tagged iaas → View Popular

VPDC is built on Cisco's Nexus 5000 and 7000 switches and VMware vSphere software.
VPDC is built on Cisco's Nexus 5000 and 7000 switches and VMware vSphere software.
2 more annotations...
- VPDC is built on Cisco's Nexus 5000 and 7000 switches and VMware vSphere software.
- VPDC is built on Cisco's Nexus 5000 and 7000 switches and VMware vSphere software.

02 Sep 09

Savvis unveils cloud-based service

www.sfgate.com/...article.cgi - Preview

cloudcomputing iaas savvis vpc vpdc datacenter vmware vsphere vcloud cisco

Savvis has built its VPDC platform using Cisco Nexus 5000 and 7000 switches and VMware vSphere software.

01 Sep 09

Cloud Developer Tips: How to Keep Your AWS Credentials on an EC2 Instance Securely

How to store your aws credentials

clouddevelopertips.blogspot.com/...ur-aws-credentials-on-ec2.html - Preview

cloudcomputing iaas amazon aws ec2 security credentials

02 Jun 09

Cloud Computing Provider GoGrid Enables Highly Scalable Web Applications Using Zeus Technology

www.prweb.com/...prweb2487324.htm - Preview

pr gogrid iaas

28 May 09

Building a Real-World IaaS Cloud Foundation | Cloud Computing Magazine

Most Popular
SYS-CON's Virtualization Conference & Expo: Themes & Topics
Application Virtualization: Instant Migration to Vista, Fast Delivery, Secure Access, Side-by-Side Deployments
Cloud Computing Expo Europe 2009 in Prague: Themes & Topics
Comments
Cloud Computing Expo: Where Are Europe's Cloud Providers?
dparrilla wrote: This is something we detected time ago. May be there are not enough Cloud Computing providers in Europe yet, but there are companies building software blocks to help companies (Service Providers, Telcos and Hosters) to become Cloud Computing Providers. I think Abiquo and our product Abicloud is an example of this trend. Diego Parrilla Abiquo Business Development Manager
May. 25, 2009 10:02 AM EDT

cloudcomputing.ulitzer.com/...976449 - Preview

cloudcomputing iaas infrastructure datacenter build fabric cloudfabric

This "state" meant that the server retained static data, specifically things like I/O addressing and storage connectivity naming, not to mention data on the local disk. Usually the local network had state too - ensuring that the IP and MAC address of the motherboard were attached to switches and LANs in a particular way. Add to this the fact that for critical applications, all of these components (plus naming/addressing) were frequently duplicated for redundancy.

This meant that if you had to replace (or clone) this server, say because of a failure, you had to reconfigure all of these addresses, names, storage connections, and networks - and sometimes in duplicate. This resulted in lots of things to administer to, and lots of room for error. And frankly, this is where fundamental "data center complexity" probably arose.
The logical follow-on question is: What if servers hadn't originally been designed as "stateful" entities? What if they were truly only CPUs and memory, with I/O and storage connections that could be reconfigured in software? And, what if the network "fabric" interconnecting these CPUs could be infinitely reconfigurable too? That way, network interconnections, multi-paths, virtual LANs, even things like load balancing, could also all be defined in software. That would get us closer to the ideal IaaS.
1 more annotations...
- The first approach is a ground-up design in which the server motherboards are designed without the traditional NIC and HBA adapters at all, and where the board interconnections consist of a converged high-speed "fabric" that conveys both I/O and storage data. No Ethernet, no iSCSI, no Fibre Channel (except between the system and the "outside world"). Drivers are written for the OS so that it "thinks" it's talking to ordinary NICs and HBAs, but in reality, those entities are logical, not physical; hence they can be configured at will. Within the fabric's converged control are logical switches and load balancers, plus the ability to create secure single or redundant interconnections. This "purist" architecture was first brought to market by Egenera in 2001 with its BladeFrame product, which is still available today. This architecture has also more recently been brought to market by Cisco with their Unified Computing System.