Back in June I was chatting about how this year the server and the network will get closer to each other than ever before. We also said that every time networks evolve and get faster and more capable two things happen: -- Networks Consolidate -- Servers DisaggregateAnd lastly we said that application architectures are evolving -- that the SOA and Cloud eras we are stepping boldly into are the most network-centric application development environments we have ever seen.So now let’s do a classic technology mash-up. What does this all mean? I am sitting here at our annual Global Sales Meeting with eight to ten thousand of Cisco’s Finest and everyone keeps asking me about these topics. They also apparently read the same financial message boards I do and also pedantically ask about our M&A strategies in this space as well, but we’ll leave that discussion for another time. Here’s what I think you will see happen-1) There will be one network in the data center. It will connect all the servers and storage together as well as link the Data Center to the outside world.2) The Virtual Machine will become the atomic unit du jour of the DC. Network equipment will morph to embrace the virtual-port rather than the physical3) As these VMs move network technologies that enable larger, flatter, and more scalable broadcast domains will emerge. We have a few racks and maybe a row at a time addressed today -- then we will go for multiple rows or pods, then a whole data cneter, then inter-site connectivity.4) We will have to re-think how Firewalls and Load Balancers are deployed, where they are deployed, the actual performance numbers needed, and how much state needs to be maintained. I would imagine an architectural shift from monolithic box-based to a federated model for these may emerge and the capabilities may become more ingrained into some of the hardware platforms as well as extend the SW logic into the hypervisor.5) There will be a strong integration between the hypervisor and the network, allowing for increased transparency to the operating characteristics of a VM and enabling policy portability from one physical machine to the next in a dynamically scheduled environment6) It may be a stretch, but I think within some reasonable 1-2m distance RAM may be able to be networked at a reasonable speed and access rate for many applicatins, but by no means all.7) If that’s the case the role of the hypervisor gets very very interesting -- imagine a data center with one network, connecting all resources, that understands the virtual machine and enabled VM mobility. Then imagine racks of servers with central pools of RAM, and centralized storage systems that are synchronously replicated between multiple facilities. Now the role of the hypervisor gets very very interesting… gathering pools of resources and abstracting the physical manifestations of workload processing resources and presenting them to the Guest OSs on an as needed and true on-demand model.Data Centers are a lot like Oreo Cookies or Reese’s Peanut Butter cups. From the outside an Oreo looks more or less like any other cookie to the untrained eye. Bite into it though and there is ‘something special’ in the middle that differentiates it, makes it unique amongst other cookies. The network and the hypervisor will get closer together -- and that is some of the secret sauce inside the cookie so to speak that makes data centers unique.
So I have had the opportunity over the last few weeks to talk to a number of folks about server virtualization--likes, dislikes, where its going. Depending on your choice of market research or anecdote, it seems that the number of virtualized production x86 servers in the the neighborhood of 10%. Again, depending on your favorite flavor of Kool-Aid, the expectation is for this to jump to 40-60% in the next 2-3 years. Even the most conservative scenario shows a significant increase in server virtualization.The question I have--and I’d love to hear from folks who have deployed some form of server virtualization--is what needs to happen in your data center to make the jump from 10% to the aforementioned 40-60% range. Do you see any inhibitors to having more of your servers virtualized?One of the areas we see some challenges is around ensuring network and storage services follow virtual machines as the undergo live migration. More than one customer has noted the challenges of using VMotion or DRS in a VMware environment. There are certainly workarounds, but they are often operationally burdensome, and what may work when you have 10% of your production servers virtualized may not be tenable when half your servers are virtualized. Because, by its nature, there is a degree of abstraction in server virtualization, I have also heard a number of concerns around areas like troubleshooting and regulatory compliance.As always, the industry is evolving to meet these new challenges. For example, one of the advantages of unified fabric is the ability to deliver a consistent set of network and storage services to all the attached servers in the data center, which simplifies live migration to some degree. However, there still seem to be gaps. Some gaps might be technological, while others might be more along the lines evolving the org structure to deal more effectively with shared, virtualized infrastructure.Anyway, what do you think--what needs to happen to drive a higher rate of virtualization for production servers?
An interesting write-up from Greg Ferro at ‘Ethereal Mind’ on how a lot of what we do as a company pulls together to create cloud computing style infrastuctures for our customers. What thoughts do you all have on this -- make sense, or way off base?
You want to read as well Building the Cloud with Cisco Unified Computing System , EMC and VMware
Was reading this really interesting article on Data Center Knowledge about Wall Street Grids. This is one of those applications that I am not sure will move to a cloud architecture. My reasons are as follows:1) Latency is of paramount importance in this space. The faster a transaction models, and transmits, ehte faster the trade may execute, and trading is a race. First come, first served. So these architectures tend to be hyper-optimized on transaction latency reductions.2) Corporations tend to not outsource areas of strategic advantage. I was meeting with the CTO of a large investment bank who commented- “IT contributed $7B to the bottom-line of our firm this year, talk to me about how we can grow that next year.” In Financial Services IT can provide tremendous strategic and sustainable competitive advantage. If a resoure is that critical to your business you usually don’t delegate or entrust it to anyone else.3) Growth rates in this area are larger and faster than many people realize. I know of an almost arms race between some firms where the number of servers is north of 10,000 for Monte Carlo simulations to build risk analysis infrastructure. What do you all think? Is this a space that lends itself to a cloud architecture, and if so- what properties and capabilities does the cloud need to offer in order to offer a credible service, and if the environment is that competitive how could the cloud provider sustain more than one customer?dg
Just read the following article published by Mario Apicella from Infoworld. Mario’s article espouses the value of FCoE in providing storage connectivity ubiquitously to a host. When coupled with an application such as VMotion that demands perfect state synchronization not having to move a huge runtime image speeds the move. Having all of the servers connected to a common infrastructures overcomes the addressing and segmented connectivity challenges imposed by a SAN island architecture.Mario- appreciate your testing, and validation that what we have here is a technology that is not only easy to use and real, but is also adding value to virtualization and VMotion.dg