Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Like this presentation? Why not share!

Virt Cloud.4



A presentation I made at a SUNY conference, this one discusses our efforts in moving more towards a \'cloud\' computing model.

A presentation I made at a SUNY conference, this one discusses our efforts in moving more towards a \'cloud\' computing model.



Total Views
Views on SlideShare
Embed Views



1 Embed 6

http://danbrint.wordpress.com 6



Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

Virt Cloud.4 Virt Cloud.4 Presentation Transcript

  • ITEC - TOWARD CLOUD COMPUTING OAS Dan Brint: Dan@itec.suny.edu Sunday, November 21, 2010 1
  • AGENDA Retrospective Operations and SOPs ITEC’s Cloud Performance Strategy Engineering ‘Cloud’ Computing Sunday, November 21, 2010 2
  • RETROSPECTIVE •A little history (close your eyes for 3 minutes if you must) Sunday, November 21, 2010 3
  • RETROSPECTIVE • Services @ITEC 9'120'( !  "#$%&'( -'#:6%'( ! -08;'+0(<+=2#1$*2+( (a +20 year evolution) !  ")'#$*+,( -./0'1/( ! >8/6+'//(<+0'&&6,'+%'( -./0'1/( !  "#$%&'( ! ?67#$#.(9'%2#;/(@,10( !  -234$#'( !  ")'#$*+,( ! 56/0$+%'(?'$#+6+,( -./0'1/( ! A+0'#)#6/'(B<C<( 56/0#678*2+( ! A+0'#)#6/'(D#2E(@,10( -8))2#0( F2/*+,( • We now directly provide technical support for Confluence, @task and Elluminate as u-wide programs. Sunday, November 21, 2010 4
  • RETROSPECTIVE • Virtualization @ITEC • Storage (2000): EVA, Shark, DS4500, HP24000, Equallogic • Server (2002): pSeries,VMWare, OVM • Network (200X): vlans, multiple ISPs, BGP Sunday, November 21, 2010 5
  • RETROSPECTIVE • Why did we virtualize? • Hardware, power & cooling savings via consolidation • Efficiencies in technology management • Take advantage of the educational cycle (LMS, Library, SIS) • Consolidation of not only technology but skill sets and expertise as well Sunday, November 21, 2010 6
  • Banner on Linux n-tier WWW 01 WWW 02 WWW 03 WWW x WWW y WWW z Binghamton Binghamton Binghamton Binghamton Binghamton Binghamton Web tier • Our Banner on RAC POC Buffalo State Buffalo State Buffalo State Buffalo State Buffalo State Buffalo State Dutchess JCC Dutchess JCC Dutchess JCC Dutchess JCC Dutchess JCC Dutchess JCC INB and SSB Nassau Nassau Nassau Nassau Nassau Nassau NewPaltz NewPaltz NewPaltz NewPaltz NewPaltz NewPaltz Niagara Niagara Niagara Niagara Niagara Niagara Old Westbury Old Westbury Old Westbury Old Westbury Old Westbury Old Westbury SICAS SICAS SICAS SICAS SICAS SICAS Suffolk Suffolk Suffolk Suffolk Suffolk Suffolk • Working with SUNY’s strategic partners Binghamton Buffalo State Dutchess JCC Nassau Banner tier NewPaltz Niagara Old Westbury SICAS Suffolk gurjobs, command line ‘stuff’ • Proved we could run Banner on virtualized / clustered RAC Node1 db1 RAC Node2 RAC Node3 RAC NodeY db1 RAC NodeZ db1 Database tier Database and Application db2 db3 db2 db3 db3 db2 databases DB 1 Binghamton Server technologies DB 2 Buffalo State db4 db4 DB 3 Dutchess DB 4 JCC db5 DB 5 Nassau DB 6 NewPaltz DB 7 Niagara DB 8 OldWestbur db9 DB 9 SICAS db10 db10 DB10 Suffolk • but ... Database Cluster (RAC) Sunday, November 21, 2010 7
  • RETROSPECTIVE • Objective look at our apps and business needs • No single app needed more compute power beyond a single x86 server and no apps had true 24 x 7 x 365 uptime requirements • Chose database ‘virtualization’ via OVM instead of RAC • DBA team hesitant to jump into an emerging technology • Systems team confident and proficient with VM technology Sunday, November 21, 2010 8
  • RETROSPECTIVE • Let’s put that in our mental parking lot for a moment Sunday, November 21, 2010 9
  • OPERATIONS / SOPS • Towards a more consistent datacenter management experience Sunday, November 21, 2010 10
  • OPERATIONS / SOPS • Enterprise Manager as a tool for managing technology • Engaged TUSC to help with template development • Delivered Dashboards to SLN helpdesk (finally) Sunday, November 21, 2010 11
  • OPERATIONS / SOPS • @task as a tool for managing tasks • Confluence as a tool for managing knowledge Sunday, November 21, 2010 12
  • OPERATIONS / SOPS • Adoptionsof Project Managers and project management methodologies • Organizing our projects and business processes • Reviewing and standardizing our operating procedures Sunday, November 21, 2010 13
  • OPERATIONS / SOPS • Long and short of it is that we are improving our services AND making our own lives more tolerable by documenting, standardizing and proceduralizing • Only after we have achieved this can we really look to automation to take it to the next level Sunday, November 21, 2010 14
  • OPERATIONS / SOPS • Put that in the parking lot too :) Sunday, November 21, 2010 15
  • PERFORMANCE ENGINEERING • Some enlightening work with SLN & ANGEL / Blackboard Sunday, November 21, 2010 16
  • PERFORMANCE ENGINEERING • As a result of the ‘overwhelming’ success of ANGEL adoption during fall 2009 we sought to understand • SLN engaged Blackboard’s performance engineering team to help us better understand the past and predict the future Sunday, November 21, 2010 17
  • PERFORMANCE ENGINEERING • Analyzed our web logs • Determined peak loads (peak of peak) • Constructed simulations to test capacity, throughput, ... • Performed tests on a lab representing our new environment to find potential bottlenecks & efficiencies • FYI - No silver bullets (unexpected growth) Sunday, November 21, 2010 18
  • PERFORMANCE ENGINEERING • After the analysis was complete we performed what blackboard calls a TKT - a technical knowledge transfer. •I waited with bated breath* for this !!! The phrase means anxiously or with great anticipation. I don't remember and can't find my source on this but I think that "Bated" is a shortened version of "abated", which means "to slow down". In the case of "bated breath" this would mean to slow down your breathing or hold your breath. Curiously, people hold their breath when in anticipation. Perhaps so as not to be distracted by breathing. "Bated" is no longer commonly used, causing people to believe the expression to be "with baited breath". This common misspelling leads to confusion and strange imagery. http://www.phrases.org.uk/bulletin_board/5/messages/14.html Sunday, November 21, 2010 19
  • PERFORMANCE ENGINEERING “ It’s as though someone put the bloody SCIENCE back in Computer Science !!!! You know theories, hypothesis, tests, analysis, conclusions ... all that good stuff we did back in school ! ” Sunday, November 21, 2010 20
  • PERFORMANCE ENGINEERING •A couple of big takeaways from the TKT: • The science of performance engineering • Emphasis on process, language, communication • The resource commitment to implement • Potential as an internal resource we consume, a value add to our current customers, a standalone service we offer for anyone in SUNY. Sunday, November 21, 2010 21
  • PERFORMANCE ENGINEERING • Another one goes into our mental parking lot Sunday, November 21, 2010 22
  • CLOUD COMPUTING • Good lord he went 15 minutes without saying cloud - now we’re in for it ???!!! • Timefor some definitions Sunday, November 21, 2010 23
  • CLOUD COMPUTING • Melissa Woo (University of Wisconsin-Milwaukee ) • “I find the term cloud computing to be extremely overloaded. In fact, a recent report by McKinsey & Company identified twenty-two different definitions for cloud computing.” • “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.” Sunday, November 21, 2010 24
  • CLOUD COMPUTING • Larry Ellison (Oracle) • "I can't think of anything that isn't cloud computing.... It's complete gibberish.... When is the idiocy going to stop?" Sunday, November 21, 2010 25
  • CLOUD COMPUTING Definition of Cloud Computing: Cloud computing is a model for enabling • NIST (National ubiquitous, convenient, on-demand network access to a shared pool of Institute of configurable computing resources (e.g., networks, servers, storage, applications, Standards and and services) that can be rapidly provisioned and released with minimal Technology) 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. http://csrc.nist.gov/groups/SNS/cloud-computing/ Sunday, November 21, 2010 26
  • CLOUD COMPUTING 1. On-demand self-service Characteristics 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. 2. 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). Sunday, November 21, 2010 27
  • CLOUD COMPUTING 3. Resource pooling Characteristics 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. Sunday, November 21, 2010 28
  • CLOUD COMPUTING 4. Rapid elasticity Characteristics Capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time. 5. Measured Service Cloud systems automatically control and optimize resource use by leveraging a metering capability 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. Sunday, November 21, 2010 29
  • CLOUD COMPUTING Service Models: • Software as a Service (SaaS) • Platform as a Service (PaaS) • Infrastructure as a Service (IaaS) Think of them as decreasing levels of “blissful ignorance” Sunday, November 21, 2010 30
  • CLOUD COMPUTING 1. Software as a Service (SaaS) Service Models 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. Sunday, November 21, 2010 31
  • CLOUD COMPUTING 2. Platform as a Service (PaaS) Service Models 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. Sunday, November 21, 2010 32
  • CLOUD COMPUTING 3. Infrastructure as a Service (IaaS) Service Models 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). Sunday, November 21, 2010 33
  • CLOUD COMPUTING Deployment Models: • Private Cloud • Public Cloud • Hybrid Cloud • Community Cloud Sunday, November 21, 2010 34
  • Deployment Models CLOUD COMPUTING 1. 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. 2. 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. Sunday, November 21, 2010 35
  • Deployment Models CLOUD COMPUTING 3. 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., cloud bursting for load- balancing between clouds). Sunday, November 21, 2010 36
  • Deployment Models CLOUD COMPUTING S U NY ? ood ness 4. Community Cloud G 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. Sunday, November 21, 2010 37
  • CLOUD COMPUTING • And with that our parking lot is full Sunday, November 21, 2010 38
  • REVIEW Retrospective Operations and SOPs Performance Engineering ‘Cloud’ Computing Sunday, November 21, 2010 39
  • Retrospective SOPs • Service Evolution • Grid Control • Virtualization • Standardization • Banner POC • PM Methodologies • Predictable Future • Definitions • Healthy dose of • Community Cloud science Cloud Computing Performance Engineering Sunday, November 21, 2010 40
  • CLOUD STRATEGY • Good lord look at all the circles up there ... Sunday, November 21, 2010 41
  • CLOUD STRATEGY • Weaving these 4 loosely coupled ideas together we can now assemble ITEC’s cloud strategy Keep in mind, I’m mostly concerned about database and application server technology bits of this strategy • First - a tiny bit about our technology/business model • How we see ourselves evolving into a cloud computing like model • Some current initiatives under way Sunday, November 21, 2010 42
  • CLOUD STRATEGY • Campuses use the apps • SICAS, OLIS, SLN manage the big apps • ITEC manages the infrastructure (and some of the smaller apps) Sunday, November 21, 2010 43
  • CLOUD STRATEGY • TODAY - we make use of virtualization at the storage, network and server level • But we still end up (in essence) deploying dedicated environments for every customer for (mostly) every app • i.e. we have not virtualized our databases or applications • Time for a little ‘cloud’ comparative analysis Sunday, November 21, 2010 44
  • (today) CLOUD STRATEGY On Broad Demand Resource Rapid Measured Characteristics Network Self Pooling Elasticity Service Access Service 1/4 Check Check 1/2 Check 1/4 Check 1/2 Check On Demand: Dual ISPs & BGP OS, Network, We can respond We have grid Sort of, (we are Storage YES, fairly quickly for control collecting very SUNY VPN the resources a lot of data accommodating) Database, Apps that we pool points but we’re Burstable NO, not looking at Self Service: consumption. but it’s mostly them WRT No (People Yes) manual. charge back. Sunday, November 21, 2010 45
  • (today) Service Models CLOUD STRATEGY Software aaS Platform aaS Infrastructure aaS Check Check No Check We serve up @task, This is really the core of what We provide VMs that OAS Confluence, Lyris, Elluminate we do today. uses as part of their DR to all ITEC members. solution. Apps are 100% maintained by Banner, ANGEL, ExLibris all We provide the hardware ITEC and our customers operate in this model with and basic networking and simply use them (with some other u-wide entities storage while OAS manages very limited configuration providing application the rest. capabilities) management. Sunday, November 21, 2010 46
  • Deployment Models CLOUD STRATEGY Private Cloud Public Cloud Hybrid Community Tiny Bit NO NO 95% yes (today) We have a few things Too many concerns By definition of being Amazingly YES. for our own internal all of which are well partially Public = No. use but these are very discussed in the Instinct told us that minimal public. was true but looking at it with clinical perspective this is most certainly what we do today. Sunday, November 21, 2010 47
  • CLOUD STRATEGY • Summary of our shortcomings: • Agility and self-service • Need more virtualization, standardization and automation • Observation that you need more structure in order to be more flexible Sunday, November 21, 2010 48
  • CLOUD STRATEGY • Strategy? • Continue to develop our SOPs and then automate • Virtualize our databases and app servers • Choose reasonable pilot projects • Draw on expertise where ever it lies ITEC as a Cloud – Current and Future Projects & The ITEC Cloud sessions by Mike Notarius Sunday, November 21, 2010 49
  • CLOUD STRATEGY So in a concrete sense - what are we doing about it ? • We have a project to revisit our operations and develop well documented SOPs • We’re developing a project to start exploiting EMs provisioning pack • We’re re-embracing RAC and application server clustering (perhaps WebLogic Suite) Sunday, November 21, 2010 50
  • CLOUD STRATEGY So, why the change of heart with respect to RAC? • Re-assessed our current and near future business and application needs • at least 2x databases to manage • More databases are approaching near 24x7 (LMS IS 24x7) • CPU requirements are increasing • Business need to be more agile and elastic • and lastly - it’s now a matured (mainstream) technology Sunday, November 21, 2010 51
  • CLOUD STRATEGY • Specifically with respect to RAC: • Three projects • LMS POC with RAC (and DBFS) • SBIP - Cloud based Business Intelligence • Project Z Sunday, November 21, 2010 52
  • CLOUD STRATEGY #1 - LMS POC / RAC • Our LMS TEAM is already investigating Blackboard and Moodle as options to ANGEL • At the end of these projects we are adding in RAC technology on the back end plus DBFS - a database hosted file system • Performance, scalability, absolute point-in-time recovery • Executing load/stress testing utilizing OATS - Oracle Application Testing Suite (possibly engaging Blackboard to help us) Sunday, November 21, 2010 53
  • CLOUD STRATEGY #2 - SBIP BI Cloud • Hosting SICAS BI program in an internal BI Cloud • Dramatic cost savings and efficiencies for all entities involved • At the expense of flexibility • Single (Enterprise Model) OBIEE install • Multiple campus ODS in a single DB utilizing Oracle Virtual Private Database Sunday, November 21, 2010 54
  • CLOUD STRATEGY Identity Infrastructure Web Server Cluster (WebLogic 11g) GRID / Cluster Local BI Admin Server BI Server Cluster GRID / Cluster (OBIEE 11g) Campus ERP Database Campus Shared ODS (VPD) ERP Rac DB Infrastructure Campus ERP Sunday, November 21, 2010 55
  • CLOUD STRATEGY •Aless conceptual version for those of you who like details Sunday, November 21, 2010 56
  • CLOUD STRATEGY #3 - Project Z • And yes thats ‘Zed’ not ‘Zee’ • Developed by Germans • Purloined by Canadians • (Made by Americans) • An evolutionary REVOLUTIONARY approach to hosted database management Sunday, November 21, 2010 57
  • CLOUD STRATEGY Z as in Zoolander the world greatest male supermodel? The man who brought us .... Blue Steel Ferarri Le Tigra Magnum Sunday, November 21, 2010 58
  • We’re talking Hansel. In your face, off the wall, smashin’ the mold, Hansel !!! Sunday, November 21, 2010 59
  • CLOUD STRATEGY #3 - Self Service Cloning • Self Service cloning of production databases to a cloud environment at ITEC • Campuses will be able to initiate (via automation) clones of PROD databases into this environment • Using RMAN and Grid Control we will clone the DB into the ITEC cloud • Utilizes a cluster of x86 servers running Oracle RAC on Linux to deliver the database to you (and only you) Sunday, November 21, 2010 60
  • CLOUD STRATEGY #3 - Self Service Cloning • Benefits • Removes the need for dedicated development database servers (i.e. saves money) • Gives us time to become proficient in the technology in a lower risk environment (i.e. increased quality of life) • Costs • Investment in automation, infrastructure, training (internal to ITEC) Sunday, November 21, 2010 61
  • CLOUD STRATEGY #3 - Self Service Cloning • Probably will not be as on-demand as one might imagine and will be an overnight process (network considerations) • Cloning will be to a named database so that we can pre- configure integration with other application and web servers • We will probably limit a campus to X non-prod databases Sunday, November 21, 2010 62
  • CLOUD STRATEGY Moving forward • Each of these 3 projects enable us to move forward in a manner that is low(er) risk than if we just said “we’re doing cloud tomorrow” and let er rip. Sunday, November 21, 2010 63
  • CLOUD STRATEGY Summary • Education - to better understand what we were being compared to and diffuse the hype • Analysis - understand what our business needs are and where we stand today and where we should be tomorrow • Insight - in several respects (but not all) we’re already doing computing in a ‘cloud’ style • Found a way to move forward while managing risk One more thing .... Sunday, November 21, 2010 64
  • CLOUD STRATEGY • Cloud computing is an evolving body of work • For as much as many may downplay vendor/media hype the fact is that numerous high profile organizations are working diligently to define cloud computing standards: • NIST, IEEE, OGF (open grid forum), iTL (Information Technology Laboratory), ... • As an example visit http://www.nist.gov/itl/cloud/ cloudworkshopii.cfm Sunday, November 21, 2010 65
  • CLOUD STRATEGY Standards Acceleration to Jumpstart Adoption of Cloud Computing (SAJACC) The goal of the SAJACC initiative is to drive the formation of high-quality cloud computing standards by providing worked examples showing how key use cases can be supported on cloud systems that implement a set of documented and public cloud system specifications. The SAJACC initiative will develop and maintain a set of cloud system use cases through an open and ongoing process engaging industry, other Government agencies, and academia. Simultaneously, the SAJACC initiative will collect and generate cloud system specifications through a similarly open and ongoing process. The SAJACC initiative will develop tests that show the extent to which specific use cases can be supported by cloud systems that implement documented and public cloud system specifications, and will publish test results on the SAJACC web portal (this web site). The SAJACC web portal will provide pointers to known cloud system implementations, use case documents, upcoming events, and will also provide a convenient means to provide feedback to the SAJACC team. These resources will serve to both accelerate the development of high- quality cloud computing standards and reduce technical uncertainty during the interim adoption period before many cloud computing standards are formalized. http://www.nist.gov/itl/cloud/index.cfm Sunday, November 21, 2010 66
  • Questions or Thoughts? • Thank you • I’m always looking for feedback • dan@itec.suny.edu Sunday, November 21, 2010 67