5. Heard on the street… Move to cloud and cut your costs by 1/2 ! No way! Not secure enough. No need anymore for the IT department Users can now run IT. Dump all our existing mainframes…let’s move to the cloud!!! I’m the CEO…I do not give a darn about that techy stuff… No. We will not use this application anymore as it’s not SaaS! True Cloud is only when… Private Cloud is nonsense!!! We are a very small/large company…Cloud is not for us. IT Governance, what IT Governance? Beware of Extremes
6. Reality Check – back to the basics Revenue increaseCost reduction Strategic advantage ???
8. Definition NIST :“Cloud computing is a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. This cloud model promotes availability and is composed of five essential characteristics, three service models, and four deployment models.” Gartner: “Cloud computing (including both private and public clouds) is a style of computing where scalable and elastic IT-enabled capabilities are delivered as a service to customers using Internet technologies.”
9. A more balanced approach IT evolution…business revolution Rooted in the eBusiness concepts No one-fits-all solution IaaS, PaaS and SaaS…towards IT as a Service Business and IT alignment a must (more than ever) It’s a journey more than a destination
10. Real show stoppers? Security ...is this really just about the Cloud? Existing investments …correct timing and planning is the key Size of enterprise …a solution for each one
11. Some areas to evaluate Systems utilization Current IT governance and processes New IT role (business unit vs. cost center) and staff training Critical applications list New model implications (i.e. customizations and PaaS) Security approach Network bandwidth Mobile force impact
12. Some simple but crucial hints It’s an enterprise transformation… Do not bypass IT Plan for IT transformation Focus on enterprise architecture New budgeting models Think big, start small Enterprise planning, phased implementation Select key applications Large enterprise (*) think Private then Hybrid Cloud Small enterprise (*) thorough study, then Public Cloud Avoid addiction... (*) the definition of large and small in this context needs to be discussed
13. Should you need some help… Roberto AGNOLI http://www.linkedin.com/in/robertoagnoli Based in Paris, France – open to missions across Europe. Available for: Advisory Consulting Program Management Interim Management Missions
Editor's Notes
cost-minimizationAgilitybusiness continuity
Essential Characteristics:On-demand self-service. A consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with each service’s provider.Broad network access. Capabilities are available over the network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs).Resource pooling. The provider’s computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand. There is a sense of location independence in that the customer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter). Examples of resources include storage, processing, memory, network bandwidth, and virtual machines.Rapid elasticity. Capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out, and rapidly released to quickly scale in. To theconsumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time.Measured Service. Cloud systems automatically control and optimize resource use by leveraging a metering capability1 at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency for both the provider and consumer of the utilized service.Service Models:Cloud Software as a Service (SaaS). The capability provided to the consumer is to use the provider’s applications running on a cloud infrastructure. The applications are accessible from various client devices through a thin client interface such as a web browser (e.g., web-based email). The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.Cloud Platform as a Service (PaaS). The capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations.Cloud Infrastructure as a Service (IaaS). The capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, deployed applications, and possibly limited control of select networking components (e.g., host firewalls).Deployment Models:Private cloud. The cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on premise or off premise.Community cloud. The cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on premise or off premise.Public cloud. The cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services.Hybrid cloud. The cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloudbursting for load balancing between clouds).NOTE:See also “NIST Cloud Computing Standards Roadmap”
See “Compelling Cases for Clouds by Joe Weinman”What are Some Advantages of Private Cloud Computing? (MS)What are the advantages of private cloud over the traditional data center model? Examples include:The on-demand capability enables teams to quickly develop, test and deploy solutions that would otherwise take weeks or months to instantiate in a non-cloud environment. The service team just fills in the online request form, virtual machines with the appropriate computing capabilities are spun up and the team creates the solution – all without the intervention of the private cloud management team.The rapid elasticity capability enables you to save money on compute, memory, network and storage resources because these resources scale up and are released when needed. When projects start, the resources are allocated to consumers of the cloud service, and when the project ends, these resources are released back into the cloud infrastructure’s resource pool.The metered services capability makes it possible for IT to be seen as a true service provider and moves IT from a cost-center to a business enabler by monitoring cloud infrastructure resource usage by cloud service consumers and then providing comprehensive reports on usage and charge back to the departments consuming the cloud service.These are just a few of the advantages enabled by the private cloud. The big difference between traditional data center computing, (where the focus was on infrastructure and operations and “keeping the lights on”) and private cloud is that private loud computing is all about “service delivery”. The core architecture of any private cloud environment is focused squarely on this central tenet of service delivery.
Server utilization -- Reg Spike and Weekly Wave: unknown unknowns and known unknownsSOA, BP, processes and methods etc.Lack of IT governance Cloud Computing disappointmentWhen it comes to managing and governing cloud initiatives, IT leaders earned their lowest scores from respondents: 1.69 from advisors and 2.19 from providers. Among the key challenges in mobile cloud computing that were identified include:Decreasing network latency to allow apps and code offload interactivity.Improving network bandwidth to speed up data transfer within the cloud and other devices.A scalable way of monitoring network conditions to maximize network and device costs that are parallel to the performance of cloud applications.Security: There is an ongoing (r)evolution of the threat landscape that requires significant rethinking the traditional perimeter-based security model independent of cloud computing (e.g. mobility, viruses...).Mobile malware can enter a device at many points, so security should take an end-to-end approachSLAs -- New SLAs mean new types of clouds. The road to better service level agreements will require the vendor to articulate the service offering and expected performance clearly in a way that is visible, actionable by the customer and with clear metrics for recovery. So if the service includes back up, the customer understands the scope, can see when the backup failed, and can on their own recover from failure within the promised window (mean time to recover). New SLAs will likely lead to two types of clouds –or at least make this bifurcation of clouds more visible. One cloud will be for apps designed for failure, scale out and mobility: perfect for single app startups coming out of Silicon Valley and some new field applications. Which makes sense because startups have more labor than money.The other is built to bring existing enterprise applications into a more cloud-like operating model; meaning transitioning existing applications and workloads to be more on-demand, elastic and pay-per-consumption, using either a private cloud or an enterprise cloud provider. I call them “city clouds” because they have to work within existing infrastructure, follow rules, customs, and are constrained by other applications. And thanks to better SLAs customers can know what they are choosing and price that into their estimates.Customizations -- You have three major options for addressing this diversity:»» Take it or leave it — Give users a basic, standard cloud service with no customization, regardless ofwhat they want.»» A thousand shades of cloud — Give users precisely what they want, creating a library of images to meeteach need.»» The modular cloud service — Construct a modular way of giving each user what they want by piecingtogether component parts on demand.
-- Large enterprises: the journey typically involves multiple steps of resource efficiency (e.g. virtualization), operational efficiency (automation), and sourcing flexibility (between private, hybrid and public services from differing vendors).-- Small enterprises: might also use both private and public cloud but have more incentive to move quickly since they cannot match the economies of scale of the cloud providers-- Startups: Are very often 100% public cloud from the beginning. Most compelling case since the have be the economy of scale incentive and the utility pricing incentive (since their success and growth rates have most uncertainty). Also of course the lack of capex makes it easier to fund initially.-- Cloudbursting is an approach to handling spikes in demand that overwhelm enterprise computing resources by acquiring additional resources from a cloud services provider. Cloudbursting as a concept refers to moving data and applications instantly from one cloud to another.
