Primary message point for slide:Explosive growth is measureable now and will continue trending upwards rapidly for at least the next 3-7 years. These are just four examples looking at year 2015, of this worldwide phenomenon.Along with the business impacting transitions, we are able to see distinct trends in explosive IP traffic growth and changeCisco’s projections for four significant indicators or numbers in 2015 are:767 Quintrillion – the projected number of bytes of global IP traffic – up from 176 quintrillion in 20097 Billion – the number of mobile-connected devices in an overall population of 12 billion connected devices18000 – the 5 year (to 2015)percentage growth in web video conferencing91 – the percentage share of video in all consumer traffic – across all devices
Primary message point for slide:A perfect storm of technology and economics have brought about the confluence of computing and networking again to propel the industry into yet another major transition which represents both a threat and an opportunity for network operators, and it is fast movingOur industry is seeing a significant change in how computing is doneThis represents both threat and opportunity for network operatorsA recent Cisco IBSG demand-side study worldwide revealed a projection of $43B revenue in 2013 for outsourced IT services via a cloud business model, including the three major categories: SaaS, PaaS, IaaSA market this size and growth rate is a big opportunity for network operators but also a threat because such transitions attract new market entrants which can disrupt current businessAmazon Cloud is an example of a successful new entrant and one which demonstrates that cloud can scale and is growing rapidly. Amazon Cloud operated at >200,000 requests per second at end of 2010 and supported 262B objects up from 14B objects just in 2007Cisco’s IBSG study also revealed that netowrk operators do have an inherent advantage; the top 3 differentiators in the minds of CIOs across several industry segments are: end-to-end SLA,s provisioning across access network and IT data centers, enterprise-ready billing. All these are core capabilities of network operators should they choose to leverageOne more significant number for 2015 is 0 (Zero) – according to Saugatuch technology, this is the number of business computing categories NOT moved to cloud by 2015The average monthly traffic in 2014 will be equivalent to 32 million people streaming Avatar in 3D, continuously for the entire month.From Amazon.com:Stats, measured at the end of the fourth quarter of each year:2006 - 2.9 billion objects2007 - 14 billion objects2008 - 40 billion objects2009 - 102 billion objects2010 - 262 billion objectsThe peak request rate for S3 is now in excess of 200,000 requests per second.
Cloud Computing started with the needs of the largest Internet Companies serving millions of users everyday. Could only be accomplished with very large scale data centers, ten’s of thousands and servers, and fully automated management systems. In such an environment there will always be components that fail yet the application needs to survive.
Definition of Private Cloud Computing for purposes of this presentation: Cloud infrastructure and processes for the exclusive usage of one enterprise/entity, hosted within the scope of the enterprise, and encompassing physical as well as virtual resources.Basis of this diagram is in Gartner’s document: Q&A: The Many Aspects of Private Cloud Computing authored by Thomas Bittman in October 2009 in response to the question ‘What are the basic elements of a private cloud service?’
Part of a larger story that goes to down to the infrastructure includes HCS, SP-Wifi,
So what is it about the cloud computing that makes it so much more desirable as a model for how data centers are run? Here we have a simplified model of an enterprise IT organization supporting multiple departments. This same approach works for managed service providers if you imagine the departments are actually different customers or tenants.Watch what happens when the data center grows as more applications are added. As each new application is added, a new system configuration is created consisting of a server, operating system, storage, and the app itself. As more applications are added, the system grows in complexity. There is very little scaling advantage. Because each application setup took getting approval, and months of development, even those apps that are only used occasionally never leave for fear the department wouldn’t ever get the servers back again. This leads to the so-called “server hugging” and the resulting poor utilization and inflexible infrastructure.(While we are showing this for an enterprise, the same holds true for a managed services provider by viewing each application as a different tenant.)
In the cloud computing model things are different. In this case, the services organization provides a cloud infrastructure service, on top of which applications are deployed fully configured with their own operating system and configuration. We have de-coupled the complexity of applications from the underlying infrastructure. The application layer and the infrastructure layer are managed independently.
As shown in green, the infrastructure service provider is now responsible for provisioning and managing physical resources and running in essence the single “cloud infrastructure application” as a service across all resources. This organization can therefore become very very efficient and almost completely automated, which dramatically reduces their costs.Of course, in a way, all we’ve done is to push the problem of application management up to the individual application owners or another part of the organization. For some organizations, like the engineering department, this is just the way they want it anyway. They would rather manage their applications without interference. For others, this self-service model means they only have to pay for what they use. This makes it possible for them to move more quickly and be less dependent. The need for application management doesn’t go away, but by separating it from the management of the infrastructure, it can be performed in a much more cost effective way.This de-coupling of the application layer from the physical infrastructure, along with self-service and automation is what makes cloud computing so much more cost effective.
The impact for our customers is taking what was very long and complex legacy management process – that can take weeks for end-to-end, often manual delivery of a request, from the upfront architecture and design of the system to the deployment – to minutes in an automated self-service provisioning environment.And this is exactly what we did at Cisco IT, which deployed Cisco UCS and Nexus – together with Cisco Intelligent Automation for their private cloud.
How we are gonna use it
Dependencies outside of the MT/IaaS boundaries are subject to their local add/move/change policies and procedures, including freezes Tenants likely to have dependencies outside the MT/IaaS pod which won’t be covered by the no-freeze SLAServices run in the MT/IaaS pod are exempt from external change and freeze restrictions Services and applications external to the MT/IaaS environment may over time develop dependencies inside the MT/IaaS environment These dependencies will be difficult to predict/trackComparision to external cloud providNOTE: Above applies to both freeze and maintenance policies
To enable automation, virtualize the server environment and design a wire-once network that eliminates the need to individually cable new servers.Use commercial, off-the-shelf components instead of developing the software internally. “Using the Cisco Intelligent Automation Cloud accelerated development from 24 months to 2 months,” says Morgan. “In addition, we didn’t have to train internal IT resources to maintain custom software, and have the option to out-task management of the IaaS program to Cisco Services or a third party.” Develop the operational model early. Map out every step for a service before you take it live.Hide the complexities of the offering by creating short, simple online forms. Know your clients and their expectations. “Early communication with customers is essential,” says Jim Heil, with the CITEIS Client Engagement Team. “They will always want additional capabilities, so you have to draw a line for the first release and constantly follow up, keeping a close eye on the competition.”Start small. Make sure you can provision the simplest resource end-to-end before offering more complex resources.Make a simple user experience a high priority. “It doesn’t matter how great the automation is if the service portal isn’t easy to use,” says Cinque.Calculate the TCO for the environment if you are going to implement a chargeback model.