‘Twas the week before Christmas, when all through IT, not a creature was stirring, not even a sysadmin?
Well, not quite. To support the global operations for a Fortune 100 company, the IT staff are always stirring things up at Cisco. But they may be just a little less busy this holiday season. Why? Because Cisco IT deployed a private cloud earlier this year, with a self-service portal and automated provisioning for infrastructure-as-a-service.
This means that employees throughout Cisco can provision and manage the infrastructure resources they need on their own, anytime and anywhere – so our sysadmins can take a break this holiday season (or more likely, they can focus on other IT priorities).
You may have already heard about Cisco IT’s internal private cloud solution, called CITEIS: Cisco ITElastic Infrastructure Services. It’s what we call a “Cisco on Cisco” example, using Cisco’s own Unified Data Center solutions – including Unified Computing, Unified Fabric, and Unified Management with our Cisco Intelligent Automation for Cloud software.
For a quick overview, here’s a short video about the Cisco IT private cloud:
And if you want more detail, watch this on-demand webinar here.
I have had many customers and partners ask me about Cisco Cloudverse in the past 2 weeks. One of the top questions I get asked is whether we support other hypervisors besides VMware. Lew Tucker in his interview in Information week covered it well: http://www.informationweek.com/news/cloud-computing/infrastructure/232300123 . Cisco Intelligent Automation for Cloud works well with many hypervisors and we have seen many successful clouds built on vCenter, HyperV, and Linux KVM. We find many customers look at multiple hypervisors to prevent vendor lock-in and all the issues associated with that. The world of many clouds is indeed a complex place as organizations building a private cloud have to decide on:
Hypervisor(s)
Server Vendor(s)
Network Vendor(s)
Storage Vendor(s)
Whether to use a converged infrastructure model or not
Cloud Automation software, (will the virtualization vendor’s software be enough for a pragmatic cloud?)
IaaS, PaaS or SaaS, or all of these models
Integrations into pre-existing IT operations management tools
What to expose in the Front Office (Service Catalog and Self Service Portal)
Details of the Back office (automation workflows, policies, models)
Whether to have any hybrid cloud models deployed.
I have seen Cisco Partners play a strategic role in helping their customers make sense of this complex playing field. They key item is to first understand what type of cloud an organization wants to deploy and what the Front Office should look like. Oftentimes I find organizations have a lot of opinions and pre-existing work on the technical provisioning, but have not thought much about what to present to end users / consumers of the cloud. Focusing on what the Cloud Portal would present to the ultimate consumers is really where the transformation to cloud needs to start. We tend to get wrapped around the axle with all the details of the infrastructure provisioning and leave little time to the end user experience. That is a really a career limiting move when it comes to your organization adopting cloud.
Our Cisco Intelligent Automation for Cloud solution, a key element of Cisco Unified Management, is a new paradigm for Cloud Automation and Management, derived from the leverage of newScale, Tidal, and Linesider acquisitions. It is both a policy and orchestration centric solution than can solve pragmatic cloud deployment needs, versus simply adopting one model (such as vCloud Director). The following figure details the considerations of policy and console based solutions versus catalog and orchestration centric solutions:
Virtually all of the customer conversations I have highlight the fact that customers want both Physical and Virtual provisioning and cloud automation. This is where Cisco Unified Management which includes the Cisco UCS Manager for Physical Server “virtualization” and Cisco Network Services Management for Physical and Virtual Network Services “virtualization”. These two technologies, alongside the Cisco Cloud Portal and the Cisco Process Orchestrator are key for creating both a physical and virtual cloud. This is what the most pragmatic of customers are looking for when transform to cloud. It is indeed a universe of clouds and Cisco can help.
By now you have may have seen the Cisco announcement of the Unified Data Center and Unified Management http://newsroom.cisco.com/press-release-content?type=webcontent&articleId=578106. This exciting story around Unified Management began in the late summer of 2010 when the engineering team in Cisco’s Tidal Software acquisition began the integration of the Tidal Enterprise Orchestrator and the UCS Manager. We realized that we could take our experience with hundreds of customers in application automation and apply that toward infrastructure automation, specifically around provisioning, virtualization and cloud. Our future was cloudy and that was indeed a good thing.
Five months later after intensive technical and business innovation, in the third week of January in 2011, the Intelligent Automation Solutions Business Unit introduced our cloud automation suite which brought the ease of Amazon EC2 to the private cloud for both physical and virtual clouds. The solution consisted of newScale’s self service and service catalog technology, integrated to the Tidal Enterprise Orchestrator for automation of infrastructure provisioning and IT operations management tool integrations. I had been a customer of both of these companies at a previous job and had experienced the benefits of automating both the end user and back end systems with these two companies. With the new use cases of data center and cloud automation I was convinced that these technologies could be the basis of something transformational for our customers.
Earlier in my career, I ran a corporate IT and managed services tooling team. I wish it was garage type tools, but it was IT operational management tools. My team was responsible for developing and integration a set of ~20 applications that was the “IT for the IT guys”. It was a great training ground for 120 of us; we worked on the bleeding edge and we were loving it. We did everything from product management, development, test, quality engineering deployment, production and operational support. It was indeed an example of eating your own cooking. Applications where king in our group. We had .NET, J2EE, JAVA, C, C+, C++ and other languages. We have custom build and COTS (commercial off the shelf) software applications.
One day on a fateful Friday, my teenagers happily asleep on a Friday night way past midnight (I guess that made it Saturday), I was biting my nails at 2 AM with my management and technical team on a concall wondering what went wrong. We were 5 hours into a major yearly upgrade and Murphy was my co-pilot that night. I had DBAs, architects, Tomcat experts, QA, load testing gurus, infrastructure jockeys, and everyone else on the phone. We had deployed 10 new servers that night and were simultaneously doing an upgrade to the software stack. I think we had 7 time zones covered with our concall. At least for my compatriots in France it was not too bad; they were having morning coffee in their time zone. Our composite application was taking 12 seconds to process transactions; it should have taken no more 1.5 secs. The big question: can we fix this by Sun at 10 PM when our user base in EMEA showed up for work, or do we (don’t say this to the management) roll back the systems and application…. I ran out of nails at this point…. My wife came into my dark home office and wondered what the heck was going on…..
Recently, a customer asked me what was the value of using automation to operate a private cloud? It was a good question. Working in the middle of the reality distorition field of the cloud industry I take it for granted that everyone knows automation’s benefits.
Fundamentally, automation tools help to reduce labor costs, rationalize consumption and increase utilization.
Costs are lower because the labor required to configure and deploy is eliminate. This automation is possible by creating standard infrastructure offerings. Standard infrastructure offering make possible a new operational model: to move from the artesanal approach of delivering infrastructure ,where every system and configuration is uniqe, to the industrialized approach, that ensures repeatability, quality and agility. It’s the difference between custom tailoring and standardized sizes at The Gap. Both have their place, but one costs more.
