Subscribe

One Point of View

Summer time is great for vacation, especially in the North East where we get about 6 good weeks of weather all year! It’s also a great time to reflect and think about where we as an IT community are heading.

I’m going to post a series of blogs on where I think the industry is going, from applications down to infrastructure. Some of this is pretty far out there, but it’s good to stretch a bit and see where it takes you.

I’m hoping the readers of my blog will get engaged. Agree, disagree, but don’t ignore, as I think we are in the midst of a revolutionary change in how applications are sold, delivered, deployed and managed. This change is happening rapidly. We’ll make a lot of mistakes along the way, but I’m convinced we’ll get it right and change the way we look at IT forever.

So, stay tuned for the first entry, coming soon….

On my mind…

I’ve finally put my virtual pen to paper to contribute to our growing blog! I’m Vern Brownell, the founder of Egenera. I was an IT infrastructure customer eight years ago when I decided to create Egenera.
The inspiration for our technology was the frustration that I had with the complexity and brittleness of the computing infrastructure that had been built up in our data centers. The incumbent vendors seemed to lack interest in reducing complexity and were quite happy to sell more servers and infrastructure to exacerbate the problem. A light bulb went off for me and I decided that there was an opportunity to build a company around an architecture that would use virtualization and abstraction to simplify and dramatically improve the agility of data center infrastructure.
My view was that the server environment and the associated infrastructure needed to be simplified first. We took a clean sheet of paper design approach and set out to build the PAN Manager architecture that our customers use today.

I’ve been following the news from LA regarding the Chino Hills earthquake story. Events like this remind of how fragile our lives are. And how fragile our systems and infrastructure can be. Thankfully, this earthquake seems to have been of limited impact, but our thoughts and prayers go out to those who have been effected.

Last month I was in China and was impressed by the universal support and sympathy that poured out from around the world for the victims in Wenchuan, southwest China. Compared to the tragic loss of over 69,000 lives, the loss of infrastructure and systems seems trivial. Nonetheless, it was another stark reminder of what can happen.
I recall that in data center threat analysis that I participated in years ago, earthquakes always seemed to rank as one of the most probable disaster events in earthquake prone areas followed by floods, fires and terrorist events. USGS reports that so far for 2008, there have been 269 earthquakes per month measuring 2.0-5.9 in magnitude in the US. Worldwide, there have been 2261 per month of the same magnitude.
As a former customer, I found providing adequate Disaster Recovery and Business Continuity Planning to prepare for events like earthquakes to be one of the hardest parts of running an enterprise IT shop. There are, of course, many issues which are not technology related, but technology is always an important part of business continuance planning. The classic rapid recovery method that most people seem to use is to provide duplicate hardware at two geographically diverse with some sort of data mirroring between sites. This method can work very effectively, albeit at significant cost and complexity. The lesson that I learned is the frequent testing is absolutely necessary and in fact in many or perhaps even in most cases the tests will not complete flawlessly.
Many of my friends and colleagues in IT in NYC and DC had to exercise their BCP plans with the terrorist attacks of 9/11. Although I was no longer in the IT business in NYC and I did not experience this tragedy first hand, I’ve heard that most firms that had this style of DR did quite well with their recoveries. So what’s the problem? It really comes down to expense, complexity and power.
The classic method requires a significant duplication of hardware, furthermore each time a system is changed in the slightest way, the backup system must also be updated. This is error prone. Most of the failures that I have seen were the result of misconfiguration of infrastructure or applications. It takes tremendous effort to keep two systems in complete sync. It’s always a tough investment to prepare for something that hopefully will never happen. And given the nature of the costs and effort, this type of backup is almost certainly only done for the most critical of applications.
Imagine a solution that would allow for automated synchronization of hardware, network and application changes. Imagine a solution that would allow for the backup of multiple sites with one set of backup hardware. Imagine a solution that could provide this type of automated recovery for applications which are both physical and virtual (running with or without a hypervisor). Egenera PAN customers can do this today and are able to test their recovery with frequencies that provide a much better guarantee that things will work in the event of a real disaster.
Some of our customers back up all of their applications regardless of their criticality, just because they find it can be a small incremental cost to add full DR to a broader spectrum of apps. It’s really the PAN architecture that makes this a simpler, faster and more reliable process.
On a totally unrelated note, I’d like to make a quick comment on Diane Green’s departure from VMware. I think Diane and her team have done a fabulous job of building a great software company in record time. She has been an inspiration to many of us in the technology business and I wish her the best of luck in whatever she decides to do next. I’m a big fan of hers and I look forward to seeing what’s next for her.
Thanks for listening. In further posts, I’d like to explore some of the data center trends and challenges that I hear from our customers and partners all the time. I’d also love to know what’s on your mind!

Yesterday marked what can perhaps be seen as an end to an era with the departure of Diane Greene from VMware. The company’s brilliant and meteoric growth, and its dominance in the “Server Virtualization” space cannot be denied. In some ways, we can all thank VMware for shining a brighter light on how customers can reap the benefits of virtualization in a broad sense. The awareness level for the word “virtualization” has never been higher or more meaningful. The next step is to expand what it means and what it will mean in the future.

As we all know though, the landscape is shifting. Not just for VMware (Hyper-V on the horizon, Red Hat embedding Xen-based hypervisor into its next distribution release, etc.) - but for every company that plays here - from the data center to the desktop. I hear more and more customers asking, “what’s next?” and “how can I extend the concepts of virtualization deeper into my organization?”

For Egenera, we answer that question by taking customers to the next phase of virtualization - allowing them to extend virtualization to their physical servers, their business and mission critical applications, and their DR processes.

I hate to speculate on “hype cycles” but perhaps as we look forward, we’ll begin to hear a louder drum beat for “what’s next?”

10 Gigabit Ethernet has brought tremendous excitement and potential for big change in the datacenter I/O infrastructure and connectivity. Everyday, we are being bombarded with new terminologies and buzzwords like DCE (Data Center Ethernet), FCoE (Fibre Channel over Ethernet), CEE (Congestion Enhanced Ethernet), CFE (Congestion Free Ethernet), Unified Wire, Converged Fabrics, etc.

So, what is so special about DCE?

DCE’s promise is use a single Ethernet interface on the server for all the types of traffic (i.e. SAN, LAN, IPC, etc.). The cost of managing and administrating multiple separate networks for LAN and SAN has already become prohibitive in large enterprise datacenters. I’ve seen data from IDC that predicts the cost of management and admin for a server will be 65% of total cost of ownership in 2010. 10G Ethernet provides enough bandwidth to converge and consolidate all of a server’s network and storage traffic out of a single spigot. Users love Ethernet’s high degree of plug-and-play and ease of use. What classical Ethernet MAC layer protocol lacks is delivery guarantees, control over jitter, and decent Layer 2 QoS. This is what DCE brings to the party.

Most, if not all, DCE changes are being standardized in 802.1 Ethernet Bridging standards body of IEEE. There is much coverage on the web on the details of Ethernet facelifts to make it DCE ready, so I will not elaborate much on those here. DCE will benefit not only data centers, but any application that relies on a reliable L2 transport. Most of the enhancements are intended to make Ethernet switches and NICs have more predictable behavior under load and congestion. It also provides a finer grain link level control over different traffic classes traversing the LAN. Ethernet is really a best effort connection-less datagram protocol. Retransmissions above L2 can be expensive and impact performance, especially when you talk about SAN protocols like Fibre Channel that rely on link level congestion management. Even high performance iSCSI which uses TCP congestion management can experience performance issues if the network and the IP stack are not properly tuned and architected.

Looks like vendors are mainly implementing DCE features in their second generation 10 Gb/s NIC and switch products and are not even bothering with the older 1 Gb/s technology. The IEEE802.1au/az work is starting to gel, and semiconductor and system vendors alike are feverishly trying to be first to market with their version of “almost standard” products.

For me, it has been interesting to watch all this excitement about convergence. While the rest of the world is just now learning about the economics and benefits of convergence on unified wire in data centers, we have been delivering and demonstrating the TCO benefits of converged fabric server products for over 8 years now!

Clouds are forming

I’ve been reading a lot about cloud computing lately. Seems like everyone has an opinion. One of my favorites was an interesting comparison on the buzz (measured by Google Trends) that Cloud is getting compared to Utility, Grid, etc.

Me personally… I’m still trying to grok what it all means. Seems to me that Clouds are Grids spiced with virtualization. Grids were great for serving up raw resources for clustered applications or like-minded apps that access the same storage or networking infrastructure. However, they are limited when a user wants to share the grid for dissimilar applications - e.g. ones with differing storage needs or HA needs. With a grid, you basically paid for the whole thing whether you need all the capability or not. This restricts the types of applications you can land on a grid.

Now, add a bit of virtualization to the grid and the rigid boundaries seemingly disappear. Grid hardware can be partitioned using hypervisors so smaller apps can be placed on the grid. It also allows the grid to have a heterogeneous operating system policy, something you can do on a grid but only with great effort. This makes the grid more flexible - a Cloud?

The issues with storage and network access are still there, and while server virtualization can help a bit here, the reality is that the physical connectivity is still an issue. What’s next, an I/O Cloud?

So to me, a Cloud is a Grid with virtualization. Is that your view? I’d be curious to see if someone has a good definition of a Cloud that can stand on its own.

We have just rolled out our updated blog. Please visit us at http://blog.egenera.com/ and update your feeds directly by subscribing at http://feeds.feedburner.com/EgeneraVirtualizationBlog.

Dan Kusnetzky asks an interesting question on his blog, “What is virtualization 2.0?”

Is it a catchphrase? Is it a new term that analysts can cling to? Is it a re-hash of technology from 20 years ago? Is it new?

I think the answer to all of these questions is yes!

Yes, it’s a new category that analysts (most notably IDC) have been pushing and yes, like all virtualization technologies, it’s an extension of what was delivered on the mainframe many years ago, just on commodity processors.

The interesting question, to me anyways, is “is it new?” Taken literally, even that is not that interesting. I think what Dan is asking is – is this really new technology that will have a material impact on how data centers are managed? If not, then it’s just another marketing term that will fall by the wayside in due time.

I think it is “new.” It’s really an evolutionary step in the virtualization of the data center. And yes, the technology will sound familiar to the mainframe crowd, but the data center is so much more than mainframes today. Virtualizing the data center means virtualizing servers and infrastructure across the data center, including commodity servers.

If Virtualization 1.0 is defined as virtualizing the server – think hypervisors like VMware and Xen, then Virtualization 2.0 is the natural extension to the infrastructure surrounding the server. Why does this matter?

It matters because the entire story can’t be told until all the components in the path of – pick your favorite name; utility computing, ubiquitous computing, agile IT, etc. – must be virtualized. This is critical. In order to create a truly dynamic data center, applications must be able to run on any server, at any time, with guaranteed service levels. To do this, the infrastructure must be as flexible as the servers. This is Virtualization 2.0. Creating a flexible, dynamic, fluid infrastructure to match the servers ability for the same.

Again, this is evolutionary, and it doesn’t stop at 2.0. Once the infrastructure is virtualized, we need to deal with other parts of the stack that that are inflexible. Dan writes a follow up blog examining the barriers to V2.0. He’s spot on, though I see these as Virtualization 2.0+ and the next step in the natural evolution to make the data center more dynamic.

That wise prophet Kermit once said, “It’s not easy being green.” Actually, it is, but you wouldn’t get that impression based on some of the “green solutions” we’re seeing in the market.

Isn’t the easiest way to reduce power and cooling to remove those things that create demand for power and cooling? Physical devices are the culprit here. The more we add, the more power and cooling we need. Simple math.

Turning down fan speeds, slowing CPUs, etc…these are nice tweaks that nibble at the edges but in reality, don’t address the root problem. Solutions from VMware and Citrix for instance definitely help, as they drive up utilization by allowing the customer to consolidate – and REMOVE – servers. This is great first step, but now it’s time to go farther. Server Infrastructure Virtualization is the enabling technology that allows you to take it to the next level.

Why not remove server infrastructure such as NICs, HBAs and their corresponding switches? Why not remove the dedicated failover servers for each application? How about the dedicated DR systems? See where I’m going?

The beauty of Server Infrastructure Virtualization is that it allows you to be much more efficient. Virtual devices don’t require additional power and cooling. Infrastructure virtualization allows you to pool resources, eliminating the dedicated backup and DR servers.

This is the real key to being green..remove unnecessary hardware through virtualization. And not just the boxes, but the infrastructure around the boxes.

“It’s not easy being green” is the part of Kermit’s song that we all remember. At the end of the song Kermit sings “It’s beautiful! And it’s what I want to be.” That’s really what customers want and the next step in virtualization is the key making it happen.

I’d love to hear what you think. How are you taking the next step in your green journey?

Today we announced our products with Dell and Fujitsu-Siemens, with support for both bladed and rack mount servers. This is a significant milestone in the company’s history, as it’s the first time we’ll deliver product on other vendors’ hardware.

It’s an especially poignant moment for me, as I’ve been at Egenera since the early days and have watched the product grow from a single OS (Linux) and a single chip (Intel 2 socket, single core) to what it is today, which is a broad based management platform that runs multiple operating systems, multiple hypervisors, multiple chip architectures, and now on multiple hardware platforms.

It’s part of our strategy to deliver PAN in as many form factors as possible, broadening the addressable market and distribution channels for PAN while at the same time, delivering tremendous value for our customers.

Some may see this as an indictment of our hardware…it’s anything but. In fact, it’s more a validation of our PAN architecture. Delivering PAN on different hardware will allow our customers a choice of platform, including BladeFrame, which remains our business critical flagship hardware platform.

So this is a big day in the history of Egenera, but it’s really another beginning, as we pursue getting PAN delivered in multiple ways through multiple channels. Our mission remains the same – to simplify the data center for our customers.

Yesterday, we announced our support for VMware Infrastructure 3 support on the Egenera BladeFrame. What’s the big deal, as everyone supports VMware today?

The big deal is the combination of the best-in-class server virtualization from VMware combined with the best-in-class I/O virtualization from Egenera. That combination is very powerful.

Why? Because server virtualization technology is enhanced greatly by I/O virtualization. Take virtual server migration (VMware VMotion) as an example. Doing this in an environment without I/O virtualization means open-zoning SANs and/or complicated clustered file systems. Either situation can create configuration and security nightmares. But, add a secure I/O virtualization environment and these problems go away. Storage devices can now follow the virtual server, meaning no need for open-zoned SANs or clustered file systems. Much more manageable and much more secure.

That’s just one example of where the combination is a win-win for customers. Another area is the ability to manage physical and virtual servers in the same system. With PAN, physical servers can be deployed, managed, failed-over, and easily set up for disaster recovery. The same is true with VMware Infrastructure 3 and virtual machines. Combining the two gives the customer the best of both worlds.

This is a great announcement for Egenera customers, as it adds a key technology to our portfolio and adds greater capability for managing and securing virtual machines.

Older Posts »