Posts Tagged ‘cloud’

Server Fabric Video

Monday, August 15th, 2011

Xsigo Server Fabric from Jon Toor on Vimeo.

Unified Computing: Who Will Win the Stack Wars? Free Analyst Report

Tuesday, June 14th, 2011

Unified computing solutions are now available from multiple vendors. Who will prevail? Download this thoroughly researched 23-page report from InformationWeek Analytics that exhaustively compares solutions from HP, IBM, Cisco, and Dell/Xsigo.

unified computing reportIt’s an interesting read.

InformationWeek offers it only on their pay-site ($99 to join), but we’re making this report titled, “Unified Computing: Who Will Win the Stack Wars,” available to you for a limited time free of charge.

Register for the report here.

The central question is this: “The battle lines are drawn, but do the benefits of a prebuilt system outweigh the drawbacks of subscribing to a single vendor’s technology vision and product roadmap?”

The report looks at this question — and the question of why unified computing at all — in detail.

Here are a few highlights:

1) “The next big thing in unified computing is the Virtualization of Everything: data and storage networks, block and file storage, even network appliances.”

Needless to say, we would agree completely. In deployment after deployment, we’ve seen that an end-to-end approach — virtualizing the servers and the infrastructure — makes the server virtualization project significantly more effective.

2) “The ultimate goal for the next-generation data center is a cloud-like environment where each application can be dynamically provisioned, configured, orchestrated and decommissioned using set resource profiles.”

Once you have achieved step 1 (the “omni-virtualized data center”) you’re significantly closer to a cloud-like environment. With that end-to-end approach I can:

  • Dynamically connect any network or storage to any server
  • Link resources without regard for physical limitations such as cards cables and switch ports
  • Deliver whatever number of connections and bandwidth each server needs

Those attributes put me a closer to that fully flexible cloud of interchangeable assets.

3) “Bundled unified computing stacks occupy that uncomfortable position common to most all-in-one offerings: When striving to be all things to all people, you end up dissatisfying almost everyone.”

You can look at this point from two angles. One is that any bundled solution is likely to quickly diverge from its prix fixe origins, so some level of integration becomes a fact of life.

The second is the open solutions such as Dell/Xsigo’s have an immediate appeal. They’re designed with simplicity and interoperability in mind, with use of widely-tested, well-known components. Instead of trying to be all-in-one, they strive for easy integration.

Other interesting discussions in the article raise questions such as:

  • Of the technologies in the stacks, which are IT managers most likely to deploy in the next 12 to 24 months?
  • Why the fixation on blades?
  • For storage in these stacks,  what are the pros/cons of FC and iSCSI?

Register for the report here.

Enjoy!

VDI Cloud Provider Saves Cost, Adds Performance with Xsigo

Tuesday, June 7th, 2011

VDI and the cloud would seem like a match made in heaven. By outsourcing your desktops to a 3rd party, you can save a lot of time and capital expenditure. VDI is complex, so why not capitalize on the in-depth planning and execution that someone else has done already?

This is the idea behind dinCloud, a California-based supplier of enterprise cloud services. As their CTO, Mike Chase puts it, “we had to solve 64 major problems” in order to deliver a great user experience that is highly reliable and lightning quick.

In the process, they learned a lot and integrated a number of innovative technologies, including Xsigo virtual I/O. Three objectives drove their thinking in selecting virtual I/O:

  1. Compute density: To minimize costs, dinCloud sought to maximize server utilization without compromising performance. The company’s high-end servers had sufficient compute capacity to accommodate 170 users each, but would have required eight 10G Ethernet connections per server to avoid I/O bottlenecks. With Xsigo, just two connections provided higher performance at ¼ the cost.
  2. Server uptime: To maximize equipment utilization, it was essential to minimize the downtime imposed by server maintenance and configuration change requirements. “Planned maintenance can take equipment offline for hours, often involves many manual steps, and introduces operational risk, all of which drive up costs,” Chase continued. “With Xsigo we can make changes in software, with fewer steps, and with zero downtime, all of which helps us offer a better quality service at less cost.”
  3. Transparency: Enterprise cloud customers demand predictable service levels that match what users experience with their own data center. In a shared cloud environment, traditional infrastructure lacks the granularity to guarantee application performance, forcing providers to over-provision resources to meet service level agreements. Xsigo’s quality of service features let dinCloud ensure bandwidth to specific applications under all conditions without over-provisioning.

Chase explained, “With Xsigo, our environment becomes compartmentalized. If an application misbehaves, we can limit its impact on other applications. When a problem does occur, we can pinpoint the issue to a specific application, something that is nearly impossible with a traditional infrastructure.”

VDI and the cloud looks like an idea that’s bound to take off, and dinCloud is off to a great start. Learn more about them here.

Webcast: Open Solutions for the Private Cloud

Tuesday, April 26th, 2011

Private clouds are in the news for good reason. The elements needed to build a private cloud are now well-proven. Plenty of users can share their experiences. Components are mature. And, enterprise cloud services such as Bluelock now provide the complementary half of the private cloud — public cloud services for on-demand capacity.

But the path to a private cloud raises a fundamental question: open solutions or closed? Is it better to buy from a single-vendor (or in a pre-packaged “block”) solution , or to create a configuration from the components of your choice?

Join this webinar (Tuesday, May 10, 10AM Pacific) to learn what your options are and what factors you should consider when making your private cloud decisions.

The question — open-solutions vs. single-vendor — is not new. In the early days of computing, ALL solutions were single-vendor. It worked OK, but did not always provide the most efficient solution. New companies (including EMC and Cisco) got their start by delivering a better answer.

The private cloud presents the same question again as single vendors (and consortiums that act like single vendors) offer their packaged offerings.

In this webcast we will look at the objectives of the private cloud (both short and long term), the technologies needed to create the cloud, and case studies. We’ll de-mystify the meanings and provide discussion points you can use to both justify a private cloud architecture and plan your path to getting there.

Register here.

How to Run VMware When Your Life Depends on It

Wednesday, April 20th, 2011

Bluelock offers VMware vCloud data center services. Their customers build virtual data centers at Bluelock and then use that environment as an extension of their own VMware deployment… a hybrid cloud model.

Bluelock is very good at this. They are one of only  three global VMware vCloud Datacenter service providers running certified services today. It’s safe to say they’ve thought hard about how best to run VMware. After all, it’s their life.

So we were honored to announce that Bluelock uses Xsigo virtual I/O in their VMware environment. (Read the case study here.)

Aaron Branham, director of information technology at Bluelock, cites numerous reasons why Xsigo helps their VMware environment do more. With Xsigo he achieved (compared with traditional I/O):

  • 40 times more usable bandwidth per server
  • 97.5 percent reduction in network devices
  • Eight times greater virtual machine capacity
  • 17 times more VMs per hardware device
  • 66 percent less cabling

The result of which has been very good for their business. Aaron comments, “With Xsigo virtual I/O now in place, the results speak for themselves: our clients been very impressed with the performance of their Virtual Datacenters and we’ve been able to further build our business by quickly accommodating even the most demanding workloads.”

If you are looking for a cloud provider who can dovetail seamlessly with your VMware deployment, give Bluelock a call.

If you are looking for ways to optimize your own VMware deployment, follow Bluelock’s lead and learn more about Xsigo. Here are a few resources to help:

The Virtual I/O Insurance Policy

Tuesday, February 15th, 2011

The dark side of technology is obsolescence. Technology evolves constantly, leaving a swath of behind-the-times gear in its wake. This problem becomes especially vexing as we transition to private cloud architectures where we’d like all resources, both new and old, to be interchangeable. If I can’t connect my new network to my older servers, those servers are no longer interchangeable.

In a recent Virtualization Review column, Elias Khnaser likens virtual I/O to an insurance policy. Elias states, “Virtual I/O allows you buy a sort of insurance policy against any type of future fabric that you might introduce later in the network. Xsigo has an appliance that you install between the servers and all the different types of fabrics available. Xsigo will accept all these fabrics as inputs and will then output them in a standard format, which means if a new technology is developed tomorrow, you can simply virtualize that behind the Xsigo appliance and maintain the same cabling and the same adapter in your servers.”

Why This Matters

A cloud infrastructure by definition relies on flexible connectivity. The whole point is to make server resources interchangeable so you have the flexibility to move workloads around, scale your environment in response to changing demands, and boost utilization by minimizing wasted server time.

But this relies on the ability for any server to connect to any network or storage when needed. (Conversely, it also requires that connectivity can be removed from a server when it would introduce compliance or security concerns.)

The obvious problem is this: what happens when new networks or storage are added? Are they connected to all of my servers or only to some of them? There are lots of reasons why servers might get excluded. They might lack the number of ports needed or types of ports. Or it might be difficult to justify the expense of connecting them. Or there could simply be schedule pressures.

Whatever the reason, when servers get left out, they are no longer fully interchangeable resources. You’ve just destroyed your “cloud.”

Virtual I/O Provides Universal Connectivity

Virtual I/O alleviates that issue in two ways:

1) I/O modules can be added as needed: The I/O modules in the I/O Director effectively become the I/O for the servers. They replace the Ethernet and FC ports that would otherwise be found in the servers themselves. When a new type of I/O is needed (such as 8G FC or 10G Ethernet), you simply add that module to the I/O Director. That I/O is immediately accessible to all attached servers. The same is true if you need new ports for new isolated networks (such as VMware vMotion or FT networks). Or if you simply need more uplink bandwidth.

2) Connectivity isolation: Each network and storage port on the Xsigo I/O Director is an isolated connection. When a virtual NIC is assigned to a port, that vNIC alone has access to that network, exactly as if you had pulled a cable between that server and that network. (Of course you can also assign multiple vNICs across multiple servers to a single port.)

As a result, this “insurance policy” works two ways. It ensures that the I/O technology is evergreen. You can always add new physical I/O when needed. And it ensures that any server can be connected at any time.

This combination removes several significant nightmares from the data center planning process and from the ongoing maintenance/updating process. And isn’t getting a better night’s sleep the whole point of insurance?

Game Developer Digital Chocolate Enjoys Virtual I/O

Monday, October 25th, 2010

With over 15 million active users on Facebook alone, Digital Chocolate’s games keep their infrastructure very busy. Which is why Digital Chocolate has deployed Xsigo to support at portion of that traffic.

Founded by video game pioneer Trip Hawkins (he also founded EA), Digital Chocolate boasts some hot titles including Millionaire City, MMA Pro Fighter, Rollercoaster Rush, and Tower Bloxx.

Their data center architecture is built in a cloud architecture to support the development and production of these highly popular games.

In their private cloud, they now use Xsigo to help accelerate processes and get more from their servers.

According to their team, they gained three important benefits with Xsigo:

  • Performance: MySQL servers can now support 35% more requests per second than before
  • Fast management: Virtual machine migrations now take from two to ten seconds, verses as much as 30 minutes with 1G Ethernet
  • Agility: I/O configuration changes can be completed in seconds without having to touch the servers

The latter point is significant for them.  Development and production networks are kept physically isolated in their environment (which also includes VMware ESX 4.0, Dell servers, and Compellent storage). With virtual I/O, they can move a server from one to the other in seconds, entirely in software, without sacrificing any of the isolation that separate networks provide. That can be a real time saver when putting new code into production.

The team at Digital Chocolate was initially interested in virtual I/O for the cost savings: fewer cards, cables and switch ports. What they quickly found, though, is that the operational benefits can be a lot of fun, too!

Why VMware Uses Xsigo Virtual I/O

Friday, October 22nd, 2010

Tim Myers, Sr. Architect at VMware, sat down to discuss why VMware uses Xsigo virtual I/O. Topics covered include:

  • How and why VMware uses Xsigo virtual I/O
  • Why virtual I/O is needed for the cloud
  • How virtual I/O supports VDI
  • Why VMware trusts Xsigo virtual I/O

For more on virtual I/O and the cloud, download the Yankee Group white paper, How Ethernet-Based Virtual I/O Paves the Way for Cloud Computing, here.

Cloud Mangement Comes to Virtual I/O

Monday, October 11th, 2010

How does a private cloud architecture change your server I/O? This is an important question if you’re looking at moving to a fully virtualized data center. Because the decisions you make today about how to connect your servers will directly impact your application performance and your ability to fully leverage your assets down the road.

Take a quick look at this video. Then read below for two new features from Xsigo that deliver scalable management and 4X the performance of 10G Ethernet.

Cloud deployments up the ante for server I/O in at least two ways.

Cloud Requirement: More I/O Bandwidth

Server bandwidth demands have changed… a lot. When Xsigo introduced 10Gb server connections three years ago, our customers though that was plenty. And it was… for the servers and software they had then. A year later, Xsigo’s launch of 20Gb connections again provided ample headroom. But now customers tell us they want more. And there are at least three good reasons for this.

1) IT managers now want to virtualize more applications, including Exchange, and database. These I/O-intensive applications, previously considered taboo for virtualization, are more and more becoming fair game.

2) There are now more VMs per server. It used to be “five VMs per server,” then ten. Now 20 VMs per server is pretty common. This increased loading directly increases I/O requirements.

3) The hardware and software are more capable. Nehalem and vSphere tripled your I/O capacity vs. the previous generation products. That’s huge. If you’re still operating with the same old pipes out of the server, that may be your bottleneck.

The bottom line is that bandwidth needs are much higher today.

NEW 40Gb Server Links

Xsigo is responding with new 40Gb server links. That’s a lot of bandwidth, the equivalent of 15,000 simultaneous Netflix HD video streams. But it’s needed if you’re planning on running I/O intensive apps.

Cloud Requirement: Fluid I/O management

The second fundamental change is that I/O must be managed in a way that is fluid.

Face it, managing every port and NIC and HBA on a one-by-one basis (and dealing with the cables in between) does not foster agility.

If you want to change something on 100 servers, how do you accomplish that quickly? If you want to deploy a new network (to support a new VMware feature such as fault tolerance, for example), how do you do that? With traditional I/O, you’d probably rather deploy a new server than take a production server down to install new cards and cables.

The cloud has to be different. I/O must be re-configurable when needs change.

NEW XMS 3.0 Management Interface

Xsigo’s new management interface introduces several important new capabilities that address the needs of the cloud:

  • User-defined I/O templates: rollout or modify connectivity on thousands of servers in seconds
  • Unified connectivity management: deploy, view and manage connectivity on thousands of servers from a single pane of glass
  • Performance monitoring: monitor and manage I/O performance across all servers to quickly identify and remedy I/O bottlenecks
  • Simplified disaster recovery: wide-area I/O management lets users manage and migrate I/O across sites to simplify disaster recovery, move entire I/O identities from one site to another, and recreate an entire configuration at a remote site so applications can be back up and running in minutes
  • iPad accessable: the new management interface can be accessed through an iPad. With the touch of a finger, users can create and manage data center server I/O using drag-and-drop features.

The combination changes I/O management in ways that would not have been possible before virtual I/O.

But that’s the point. You don’t virtualize to do things the old way. You virtualize to achieve fundamental change that makes the data center and the people that run it all more efficient and productive. That’s the whole idea of the private cloud, right? Now that fundamental change — and the private cloud — has come to I/O.

VMworld: Cloud powered by Xsigo

Wednesday, September 1st, 2010

VMworld is all about the cloud. And what you’ll find in that cloud is Xsigo.

Behind the scenes at VMworld, now happening in San Francisco, there are 14 Xsigo I/O Directors connected to hundreds of physical hosts. This gear, which is running hands-on labs, booth demos, and classes, is located at several locations around the country. I’m told that one is on the east coast. The idea of course is to help validate the cloud concept. You don’t care where the server is, just that a server is always available and accessible.

Click to the next page for a look behind the scenes. (more…)