Today’s governments around the world look to technology to improve operational efficiency, to enable collaboration across agencies, and to provide on-demand and more engaged services to really transform the citizen experience. So…for those of you who work in government, where are you getting information that will help enable you to learn about which solutions or technologies align to or fit your specific needs?
VMworld 2012 is around the corner, and like the past years , Cisco as a key player in the word of network, virtualization and now servers with the Unified Computing Systems, is a sponsor .
In the following days you will read on this blogs a series of information on our participation . But I encourage you to check today the following website to have a good overview of what we will present in terms of demos on our booth (#1213) , but also what are the key sessions we are leading . Visit here
Amongst the numerous solutions, I know for a fact (based on the numbers of readers of our blogs), that VXLAN is a very compelling topic. So I invited Han Yang to introduce his session:
Best Practice for deploying VXLAN with Cisco Nexus 1000V and VMware Cloud Director
INF–NET2373, Tuesday August 28 5:00 pm – 6:00 pm
If you want to know more about VXLAN, please check the recent blogs on this topic by Gary Kinghorn and Omar Sultan:
Last week, I introduced my concept of the 3 C’s of Cloud: Confine, Clover, and Cost and began outlining a simple strategy for maximizing your benefits during the process of adopting a cloud solution by confining the scope of your business problems. What comes next?
Let’s now talk about the second of my “C” concepts—Clover.
Before you can ‘roll in the clover’ of a successful cloud implementation you need to address one of the most common pitfalls to success: failing to build an appropriate business justification for migrating to cloud. If you enter the process with the attitude that “I’ll just experiment with this new Cloud thing and see what happens; maybe it will give me what I need,” you may not end up ‘in clover’ but in the weeds. So, what do you need to do?
Cloud is a journey. This post discusses our approach to crawl, walk and run.
A cloud architecture has multiple facets and requirements, a key part of which is the need for cloud orchestration and provisioning, coupled with a self-service end user portal. Let’s call this “Cloud Automation” for now. If you are designing and/or building a cloud, then, part of your work will be to deliver a cloud automation solution to deliver on that promise. How do you plan to go about that? One approach is to define your extensive list of requirements, based upon your business needs and current capabilities, and go about building out that solution.
Another approach is what I’ll call “Crawl Walk Run”. The incremental approach.
Cloud is a change to the operational model: a change in behavior, accounting, process and people. You can’t do it overnight. Trying to deliver every service doesn’t work.
It’s very important to set a roadmap of where you want go with your cloud services so you don’t get stuck in the VM Azores — this is where all the focus is on VM provisioning and then you deploy technology that does that. And only that.
You need that roadmap of services and a technology platform that supports your vision. Even if all you first is crawl.
Stretching the Olympic theme of my previous blog, where I used the analogy of a 100m sprinter and his backup team to introduce the new Cisco Intelligent Automation for Cloud Deployment Services, I’d like to now discuss how to roll out new cloud projects in the data center. Thinking again about a team of Olympic champions -- and the Team GB (Great Britain) cycling team, illustrate this principle so well -- with their fabulous winning streak, not least the incredibly exciting keirin event win by my countryman Sir Chris Hoy (yes, fellow Scot, however that’s where the association ends ). Such teams don’t often win with a “big bang” all-at-once, approach. Their training and successes usually builds incrementally, over several years and phases.
In the case of Team GB Cycling, they have developed from practically “also rans” in 1998 to consistent world beaters in Beijing 2008 and now London 2012. They have improved incrementally, event by event, year by year, demonstrating incremental successes as they went along, to be world beaters. In essence, they have used an approach we in Cisco sometimes call “Crawl, Walk, Run”, illustrating the progress to success. From my experience over the past 25 years in IT, there are big lessons here for IT project delivery. Let’s use a Cloud Automation project as an example.