1 Three Views of the CloudCopyright Dennis Cromwell, Michael Dieckmann, and Melissa Woo, This work is the intellectual property of the authors. Permission is granted for this material to be shared for non-commercial, educational purposes, provided that this copyright statement appears on the reproduced materials and notice is given that the copying is by permission of the author. To disseminate otherwise or to republish requires written permission from the author. Three Views of the Cloud Both Sides Now By Joni Mitchel Rows and floes of angel hair And ice cream castles in the air And feather canyons everywhere I’ve looked at clouds that way But now they only block the sun They rain and snow on everyone So many things I would have done But clouds got in my way I’ve looked at clouds from both sides now From up and down, and still somehow Its cloud illusions I recall I really don’t know clouds at all
2 What is Cloud Computing ?Cromwell Dieckmann Woo New technology energizing old concepts Extension of cloud metaphor used to describe the network Cloud Computing has elasticity and shifts CapEx to OpEx Virtualization and abstraction A not-yet-perfect storm of technologies that allows one to consume services in blissful ignorance of what's under the hood and how to maintain it. Computing services and infrastructure are provided as a scalable and shared "black box” Delivered over the Internet Allowing pay-as-you-consume cost models. The simple definitions of cloud computing. Concepts Presumed Discussed in Opening of Session: What do we mean by “the cloud?” Various views: Anything you do on the Internet. Using web 2.0 applications on the Internet rather than in-house systems. This appears to be the general view of “the cloud” in Katz’s recent EDUCAUSE book. Software as a service. Platform as a service. Infrastructure as a service. “A pool of scalable IT-enabled capabilities which can be utilized over the Internet as a service.” - Torry Harris “A pool of abstracted, highly scalable, and managed compute infrastructure capable of hosting end-customer applications and billed by consumption.” - Forrester “A computing paradigm where services and data reside in shared resources in scalable data centers, and those services and data are accessible by any authenticated device over the Internet.” - Intel Aspects of Cloudiness (of interest in the enterprise infrastructure realm): Abstraction of infrastructure (from the user and from developers/engineers). Built on a massively scalable and highly distributed infrastructure, but (probably) shared and multi-tenant. Publicly accessible over the Internet via some authentication mechanism. For user access, basic requirements are Internet access and a web browser. Often billed by consumption. Combination of software-as-a-service plus “utility computing” (platform-as-a-service, infrastructure-as-a-service, storage-as-a-service, whatever you want to label this category).
3 What some people say? "I can't think of anything that isn't cloud computing.... It's complete gibberish.... When is the idiocy going to stop?" - Larry Ellison "It's stupidity. It's worse than stupidity: it's a marketing hype campaign" - Richard Stallman "While so-called cloud computing remains an emergent concept …it is clear that (1) open information content, software, and services, (2) service orientation and delivery, (3) server and storage virtualization, and (4) standardization of computing across the Internet are leading to what some describe as the democratization and industrialization of IT.” - Richard Katz It is clear that it is a big deal because it is drawing attention and even ire from key industry people.
4 Three Aspects of Cloud Computing Software as a Service (Saas) Platform as a Service (Paas) Infrastructure as a Service (Iaas) Looking at the way clouds are delivered in the commercial setting by reviewing three methods of delivery. Software as a Service, platform as service and infrastructure as a service. One could acquire software as a service that is built on another vendor’s platform as a service that is delivered on yet a third provider’s infrstucture as a service. Thus making this truly something in the cloud. (1)Cloud Computing With Nimbus, Kate Keahey. Computing Techniques Seminar, Fermilab, IL. January 2009
5 Commercial Clouds Software as a Service (SaaS)Student and knowledge worker software Collaboration tools Functional software CRM Application for admission ERP Space Learning management Student, HR, Financial Software as service is sometimes not considered a cloud or maybe not delivered in a “cloudy way.” There probably are good examples of true cloud SaaS such as the Common App or Apply Yourself. Traditional ASP services may or may not be real cloud services, but it is probably ok to think of them in the same context as clouds. They could also be the case where an ASP might deliver some of its support using other cloud service layers. There is one LMS service that is now promoting itself as a cloud service. Student, HR and Finance may not be far behind.
6 Platform Commercial CloudsPlatform as to service might be missed in the discussion. However, in some context, it maybe the least controversial if it is used for development or testing, leaving production to be on site.
7 Infrastructure Commercial CloudsThe traditional cloud computing view. It is worthwhile to consider if the future really means that most mid-small enterprises will not run IT infrastructure just like they do not have power generation or water utilities. vCloud
8 Where does it fit? Student use Pedagogy Application DevelopmentTesting Disaster Recovery/Business Continuity Administrative Student use and pedagogy might be the first really big application that you see. Use of clouds allow greater capacity, more capability and less cost. Also, providers s now are more likely to subsidize some of the cost to get student use, just as vendors give steep discounts on software and hardware to get in student hands. Application development or testing might be great fits as risks may be lower and capacity needs can fluctuate through the life cycle. DR or Business continuity may be a truly good fit because the abase cost for maintaining the environment is lower than doing something on your own and the ability to scale can be accomplished rapidly. Administrative applications, outside of the few SaaS instances, are probably the last item to consider, but still is in our future
9 The Dangers of the Cloud (2)Adoption- Is it viable? Growth - Can it scale? Policy and process Cloud lock-in Compliance issues The mountain behind the cloud….. See the UC Berkeley White Paper “Above the Clouds” for a reference on this slide and earlier points. Adoption – Is this a viable alternative that will sustain or will adoption wane for your provider and leave them questioning the business model. Student is a great example, how long will that be for free? Growth – The promise is elasticity or fast scaling, but will it? What if you are using it for DR and need it to scale rapidly when you need it? Policy and Process The first aspect is what protection do you have for lock in? Can you take your data and move it to other clouds or is it mired in this provider’s? Making sure you that have the security and legal protections to support your institutional policies and compliance aspects. We do not say is it secure? The question is does the security meet your policy and compliance needs? Need to mitigate the risks. Earlier it was stated that this shifts capital expenses to operational expenses. This is not always a good thing for publics and higher ed, who tend to be able to spend on capital but not commit funds every year. Yet, maybe it is good because it forces budget discipline to life cycle. (2) "Above the Clouds: A Berkeley View of Cloud Computing"
10 Multi-Institutional CloudsIt's likely that all areas - research, learning, and administrative uses, could benefit from multi-institutional clouds. As a multi-institutional cloud would consist of other higher ed institutions, it's more likely that collaborators would understand higher ed needs and support for the educational mission. Other higher ed institutions would understand compliance issues such as FERPA in a way that the commercial sector would not. Multi-Institutional Clouds
11 What does "multi-institutional cloud"Ask audience for feedback on what they believe: - a multi-institutional cloud is and - examples of multi-institutional clouds. mean to you?
12 Areas of Promise Research Learning Admin
13 Institutional collaborationMulti-institutional clouds are all about collaboration. Multi-institutional clouds can be collaborations that involve a number of higher ed systems (e.g., different state systems or campuses working together) or within a system (e.g., University of Wisconsin or University of Illinois system). Examples across institutions/systems include: - Hathi Trust - book digitization project (http://www.hathitrust.org); collaboration of the CIC (Committee for Institutional Cooperation) and the University of California - Project Bamboo - collaboration between the arts and humanities with computer and information sciences to create shared technology services; multiple institutions - Eucalyptus - open source elastic compute platform that can be tied into Amazon's Elastic Compute Cloud; UC Santa Barbara; also has a newly commercial offshoot that is developing enterprise products and services based on the open source platform. Many systems provide services across their campuses in the areas of ERP, LMS, etc. inter- or intra-system
14 Collaboration issues are keySame concerns as commercial clouds: service levels compliance lock-in due to loss of control, but... There are a number of forms of collaboration, some less obvious than others. Forms of collaboration (from ECAR Research Bulletin, "IT Collaboration, Multi-Institutional Partnerships to Develop, Manage, and Operate IT Resources" - Philip Goldstein): - Partnership to develop a resource - Shared service collaborations in which multiple organizations band together to jointly operate an IT resource - Collaborations in which one institution elects to operate an IT service behalf of others - Collaborations in which an institution is a recipient of services provided by another institution ... may be less perceived loss of control because of institutional collaborations.
15 Forms of collaborationPartnership to develop service Joint operation One institution operates service Institution as recipient of service From ECAR Research Bulletin "IT Collaboration: Multi-Institutional Partnerships to Develop, Manage, and Operate IT Resources" - Philip Goldstein Collaboration forms: - Partnership to develop an IT resource - Shared service collaborations in which multiple organizations band together to jointly operate an IT resource - Collaborations in which one institution elects to operate an IT service on behalf of others - Collaborations in which an institution is a recipient of services provided by another institution
16 Advantages of multi-institutional cloudsStrength of the collaborations can help address concerns about Service levels Security / privacy compliance Trust Perceived loss of control Advantages of multi-institutional clouds come from collaborations and the relationships needed to maintain those collaborations. The strength of the collaboration sis key to addressing the concerns about: - service levels - security / privacy compliance issues - trust - perceived loss of control - lock-in...?
17 Internal Clouds Part 3: Internal Clouds What is an internal cloud?Part 3: Internal Clouds What is an internal cloud? Why consider internal clouds? Good candidates for internal clouds. How to construct internal clouds.
18 What is an “internal” cloud?Internal service that has the aspects of “cloudiness.” Can be shielded within the university, or exposed to the Internet. Why? Because we desire the benefits of cloudiness, but an external cloud is not appropriate. 1. What is an “internal” cloud? An internal cloud is an application, system, or environment within the organization that has the aspects of “cloudiness” but is not a service delivered from outside the organization. An internal cloud can either be shielded within the organization, or exposed to the Internet so that it appears as just another Internet-based cloud service. Aspects of cloudiness include features such as: High degree of infrastructure abstraction, flexibility, and scalability. Highly shared environment. Low entry costs for users (e.g., don’t have to purchase infrastructure or heavy clients). Available via a network connection and authentication – not place-bound for access. Cost can be based on consumption, if appropriate.
19 Benefits of CloudinessSharing infrastructure Flexibility Simplicity for users Distributed infrastructure 2. Why consider internal clouds? Because we desire the benefits of cloudiness, but an external cloud is not appropriate. Benefits include: Sharing of infrastructure – cost savings, environmental benefits, etc. Flexibility. Simplicity for users – abstraction of the “plumbing.” Distribution of infrastructure – for continuity-of-operations support, etc. Why might an external cloud not be appropriate? Application is not available or not mature. Risks too high. Frequent risks with external clouds include: Vendor lock-in. Security and trust issues. Performance issues. Other problems. Lack of ability to enforce policies. Lack of support for standards. Inability to interoperate or integrate with internal environment. Need for a “single logical cloud.” As we build integrated environments for our clients, an internal cloud environment may be needed as the glue that is the organizationally-branded front-end to many back-end cloud-based services. A “single logical cloud” may become the equivalent of today’s web portals. Need for composite applications. As applications are increasingly multi-sourced – perhaps involving internal systems, multiple external clouds, etc. – the framework for such composite applications may require an internal cloud-like platform. In this fashion, an internal cloud can be a “bridge” to an eventual external cloud environment.
20 Why not an External Cloud?3. Good candidates for internal clouds. Storage environment for the organization. Many or most of us now operate central storage platforms. Making those platforms as cloud-like as possible, and able to serve multiple levels of use (from single-user storage on up to database and server-owned storage) is a logical evolution. Application hosting environments (e.g., server virtualization). The desirability of server virtualization has become obvious for the central IT organization, and also as a means to rein-in distributed servers and get them into the data center. The first generation of server virtualization was of the “make a virtual server seem just like a physical server” variety. Evolving platforms are helping make the concept of a “server” disappear into the background. Flexible provisioning of host environments can assist our clients in easily mounting test or temporary development environments, and other areas of benefit. Client-side environments, especially learning environments. As scholars, instructors, and students increasingly use web 2.0 and cloud environments in research, teaching, and learning, a platform to integrate and “rationalize” those services may become the next generation of course management platform. Likewise, virtual client environments offer the promise of virtualizing our physical computer labs and in offering personalized Internet-based client environments for students. For example, UWF has created “eDesktop,” a mirror of our computer lab environment accessible over the Internet via a web browser. This is now evolving to where we are providing customized virtual environments for different programs – for example, our GIS certificate students now each receive a virtual GIS lab computer that has replaced the previous use of custom-configured laptops which required a laptop for each student in the program. Research computing support. Silos of research computing infrastructure proliferate across most universities, as each research group acquires its own equipment. A cloud environment providing basic research infrastructure services would be one way to give the researchers a view that they “own” their unique infrastructure, yet the infrastructure has been virtualized into a cloud and is professionally managed at the enterprise level. Various problems with external clouds – ranging from “where is the data stored?” to security concerns to controlled technology rules – might make this unsuitable for an external cloud environment.
21 Good Candidates for Internal CloudsStorage Internal application hosting environment Learning environments Research computing support
22 How to Construct Internal Clouds?