Intro Cloud Computing

1,365 views

Published on

This is a breif demonstration about Cloud Computing.

Published in: Technology, Education
1 Comment
3 Likes
Statistics
Notes
No Downloads
Views
Total views
1,365
On SlideShare
0
From Embeds
0
Number of Embeds
14
Actions
Shares
0
Downloads
178
Comments
1
Likes
3
Embeds 0
No embeds

No notes for slide
  • Infrastructure Integration includes networks, servers, app servers, data bases, web servers, and in my mind, even application installation. These are well defined, usually have their own staff… and they take up a large part of budget/effort, but because they are visible, for the most part, they are accounted for (time-wise). Unfortunately, as we all know, this is just the “setup”… next, you have the magic… The magic of DATA integration
  • This is the POINT behind all the infrastructure integration efforts. If not for teasing out information about our data in a way that’s usable, we wouldn’t do any of the other stuff. The other stuff is just necessary evil. It’s the boat ride you have to take to the dive site… it might make you queasy, but you can deal with it because once you get there, you’ll see some neat stuff.
  • It’s Data integration that’s hard (and expensive). And, importantly, it’s hard to explain to others, so they discount it.
  • This is really less of a definition, and more of putting an edge around a concept. And, that edge doesn’t fully surround the concept, only it gives it some shape.
  • This is not really a definition, but it does help keep our eyes on the prize and measure the success we have with it. I prefer to think of it as…
  • Of course, I’ve still not defined anything. Just trying to put some parameters around it. I defined integration earlier, now I’m saying turn commodity integration (defined as necessary, but not differentiating) into a utility.
  • Talk about thinking outside the box. If email is commodity, everything below it in the infrastructure stack is too. And, of course, this is a great example, in some cases, perhaps email is not a commodity. Perhaps there are some Outlook customizations for sales force automation, ACT plugins or whatever, that makes email a tool instead of a commodity. But, even then, it illustrates the point… using salesforce.com, and email, you want to bring that information together. The more you can do that… the more relevant IT will be. Yet, when each app is a closed silo, where the efforts are on integration rather than connectivity, it becomes a real challenge to leverage the cross-app data and relationships.
  • Not talking about ESB- or inter-app style messaging. I’m talking about email messaging. There are messages that are part of the conversation everywhere. But they lose context in email. Yeah, maybe there is a link back to relevant information, but it’s very very basic integration that doesn’t even server technical users well. We want to bring information together. Best example I can think of, however trivial, are those silly facebook messages that say “you have an email” but, I can’t respond, I need to go to facebook and respond. I have messages all over the place, there is no reason why Facebook, LinkedIn, Twitter, Email, Progress, and all these places have different places where I have to go and bring this information together manually.Now, this (messaging) is maybe not important to my enterprise, but other similar things are. How about, customer information. There is customer information all over the place, in the sales force automation system, in the provisioning system, in shipping, maybe in contracts administration, etc. Maybe in multiple places. It’s not just about Master Data Management, and having a uniform customer record (that’s hard too), but it is about having a view on my relationship with the customer so I can make better business decisions.
  • If all IT does is integrate (data and processes), it will have to become more disciplined, and there will be time to do so. I believe clouds help us get rid of the low level things IT focus on, to help us raise the bar and focus on what’s important.New classes of applications: Really more mashup-like, rapidly created, possibly with short lifespans, that help users synthesize and visualize relevant data and events so they can better execute the business. Data is no longer locked into the silo. In fact, silos simply disappear and we have a full federation of services.
  • This is really less of a definition, and more of putting an edge around a concept. And, that edge doesn’t fully surround the concept, only it gives it some shape.
  • Visibility, protect from change, service level management.
  • When I was working at Radianz, I was responsible for delivering a middleware layer on top of a shared network. Forget the technology. One of the big problems was around culture and contracts. If the network was up, but the middleware service was down, it was down from the customer perspective, and they’d want a refund. However, the network people were bonused on network uptime, not on middleware uptime, so they didn’t look at it the same way. Then, our customer support needed to be trained not to say “well, the network is up” to the customer, why would the customer care? It wasn’t working from their perspective. This is a hard problem, least so with respect to technology.
  • Security needs to change to application or message layer security. Today we rely too heavily upon network layer efforts, and frankly, it’s just not secure enough. We know that, but it’s hard to change. I believe this resistance to change will hinder cloud efforts.
  • Intro Cloud Computing

    1. 1. Introduction to ‘Cloud Computing’<br />చక్రవర్తి<br />9/19 - 2009<br />
    2. 2. Expertise level<br />Using Computer for email<br />Use computer for programmingsince <br />0 to 2 yrs<br />2 to 4 yrs<br />4 yrs and Above<br />Will learn later<br />I’m here because of my friend / philosopher / blah .. blah .. <br />ఏదో.. టైమ్పాస్<br />
    3. 3. What, How and Why<br />Do I care<br />Why do I care<br />I don’t care<br />..<br />కెరీర్ఇంకామొదలవ్వలేదు, ఇప్పుడెందుకు?<br />
    4. 4.
    5. 5. Agenda<br />The hype – stats<br />Industry definitions<br />History – a review of computing<br />Issues that matter<br />Origin<br />Grid vs Cloud<br />Details<br />
    6. 6. The hype<br />Cluster Computing<br />Cloud Computing<br />Grid Computing <br />
    7. 7. The hype<br />
    8. 8. Some Definitions<br />
    9. 9.
    10. 10. definitions<br />
    11. 11. .. Moving computing and data away from the desktop and the portable PC and simply displaying the results of computing that takes place in a centralized location and is then transmitted via the internet on the user&apos;s screen ..<br /> - John Makroff<br />
    12. 12. .. a computing paradigm shift where computing is moved away from personal computers or an individual application server to a &quot;cloud&quot; of computers .. <br />- Wikipedia<br />
    13. 13. .. the idea of relayin on Web-based applications and storing data in the &quot;cloud&quot; of the internet<br />- MIT Technology Review<br />
    14. 14. .. it starts with the premise that the data services and architecture should be on servers, We call it cloud computing - they should be in a &apos;cloud&apos; somewhere..<br />- Eric Schmidt<br />
    15. 15. Some other ..<br /><ul><li> Common, Location-independent, Online Utility on Demand*
    16. 16. Common implies multi-tenancy, not single or isolated tenancy
    17. 17. Utility implies pay-for-use pricing
    18. 18. onDemand implies ~infinite, ~immediate, ~invisible scalability
    19. 19. Alternatively, a “Zero-One-Infinity” definition:**</li></ul>0On-premise infrastructure Acquisition cost Adoption cost Support cost<br />1Coherent and resilient environment – not a brittle “software stack”<br />Scalability in response to changing needIntegratability/Interoperability with legacy assets and other services Customizability/Programmability from data, through logic, up into the user interface without compromising robust multi-tenancy <br />* Joe Weinman, Vice President of Solutions Sales, AT&T, 3 Nov. 2008<br />** From The Jargon File: “Allow none of foo, one of foo, or any number of foo”<br />
    20. 20. .. the trend towards online services that run in a web browser and store users information in a provider&apos;s data center ..<br />- చక్రవర్తి<br />
    21. 21. location<br />
    22. 22. location<br />computations & data are not in the place they used to be in..<br />
    23. 23. location<br />why does it matter? a bunch of geeky stuff.. <br />
    24. 24. possession implies control<br />control implies power<br />
    25. 25. history<br />of computing, how is changed<br />
    26. 26. distributed central<br />
    27. 27. history of evolution of computing<br />
    28. 28.
    29. 29.
    30. 30.
    31. 31.
    32. 32. SUN 3 workstation <br />
    33. 33. Distributed<br />Rich user Interface<br />User Autonomy<br />Centralized<br />Low Cost<br />Expert Management<br />
    34. 34. Client<br />Client<br />Client<br />Server<br />Client Server – 80s & 90s<br />Client<br />
    35. 35. Server<br />Client<br />
    36. 36. Server<br />Client<br />
    37. 37.
    38. 38. ASP.NET<br />JavaScript<br />XML<br />C#<br />HTML<br />SQL<br />Data Store<br />Intermediary Application – Cloud Implementation Strategy<br />
    39. 39. enterprise impact<br />
    40. 40. Cultural Challenges<br />
    41. 41. Data<br />Integration is hard<br />Expensive<br />Infrastructure<br />
    42. 42. Data Integration<br />Adds meaning<br />
    43. 43. Data Integration is hard<br />InvisibleHard to quantify<br /> Discounted<br />
    44. 44. Financial & Logistics Challenges<br />
    45. 45. Cost v. Benefit<br />Time (Cost v. Benefit)<br />
    46. 46. Traditional Software Purchase<br />Purchase software<br />Purchase hardware<br />Create migration plan<br />Configure systems<br />Configure networks<br />Find space in data center<br />Setup development & test<br />Configure databases<br />More… <br />
    47. 47. The Easy Way<br />Get a login<br />
    48. 48. Data Integration is hard<br />Costs don’t match benefits<br />
    49. 49. How do we make integration easier, and deliver benefits more quickly?<br />
    50. 50. Define Cloud Computing<br />
    51. 51. How do we make integration easier, and deliver benefits more quickly?<br />Cloud computing is a way to make integration easier, and deliver benefits more quickly<br />
    52. 52. integration^<br />Turn a commodity into a utility<br />Necessary, but not differentiating<br />
    53. 53. Not everything’s a commodity<br />
    54. 54. Web Server Farms. Commodity.<br />
    55. 55. Much Enterprise Software. Commodity<br />
    56. 56. Email. A commodity.<br />
    57. 57. Messaging. Maybe not a commodity.<br />
    58. 58. What if… we just gave IT a platform to create their own data models, interfaces, and processes on a dynamic infrastructure [that met corporate requirements] & simply existed as needed?<br />
    59. 59. Results in elevated IT relevance<br />
    60. 60. Other Results…<br />Focus on integration will evolve to a more disciplined approach<br />Match expenses to benefits<br />Enable new classes of applications<br />
    61. 61. Best Practices<br />
    62. 62. Mediation. A secret weapon.<br />
    63. 63. Service Level Management. Don’t even start with “my piece is working fine!”<br />
    64. 64. Security. It’s not (only) what you think it needs to be.<br />
    65. 65. Build a culture of collaboration.<br />
    66. 66. Example: Google Apps<br />Cloud Platform<br />(Apps Engine)<br />Cloud Services<br />(Word Processing)<br />Cloud Client<br />(Mozilla Firefox)<br />Cloud hardware<br />(Apps Server)<br />Cloud storage<br />(BigTable DB)<br />BigTable<br />Cloud Application<br />(Google Docs)<br />
    67. 67. issues that matter<br />
    68. 68. Implications<br />possession of data<br />
    69. 69. privacy<br />our data is hold by 3rd party<br />
    70. 70. security<br />portability and preservation<br />
    71. 71. “possession” of computation<br />
    72. 72. market power<br />
    73. 73. how big is the problem?<br />
    74. 74. location<br />
    75. 75. Understanding Cloud Computing<br />
    76. 76. Origin<br />“.. Comes from the early days of the Internet where we drew the network as a cloud… we didn’t care where the messages went… the cloud hid it from us” – Kevin Marks, Google<br />First cloud around networking (TCP/IP abstraction)<br />Second cloud around documents (WWW data abstraction)<br />The emerging cloud abstracts infrastructure complexities of servers, applications, data, and heterogeneous platforms<br />(“muck” as Amazon’s CEO Jeff Bezos calls it)<br />
    77. 77. 3 Cloud Service Models<br />Cloud Software as a Service (SaaS)<br />Use provider’s applications over a network <br />Cloud Platform as a Service (PaaS)<br />Deploy customer-created applications to a cloud <br />Cloud Infrastructure as a Service (IaaS)<br />Rent processing, storage, network capacity, and other fundamental computing resources<br />To be considered “cloud” they must be deployed on top of cloud infrastructure that has the key characteristics<br />
    78. 78. Service Model Architectures<br />
    79. 79. 4 Cloud Deployment Models<br />Private cloud <br />enterprise owned or leased<br />Community cloud<br />shared infrastructure for specific community<br />Public cloud<br />Sold to the public, mega-scale infrastructure<br />Hybrid cloud<br />composition of two or more clouds<br />
    80. 80. Common Cloud Characteristics<br />Cloud computing often leverages:<br />Massive scale<br />Virtualization<br />Non-stop computing<br />Free software<br />Geographic distribution<br />Service oriented software <br />Autonomic computing<br />Advanced security technologies<br />
    81. 81. is this GRID Computing?<br />
    82. 82.
    83. 83. Clouds aren’t all the same<br /><ul><li>Not every cloud is a “grid”
    84. 84. Grids imply dynamic arrival/departure
    85. 85. Electrical analogy has limits: CPU cycles aren’t substitutable
    86. 86. Most clouds are not “compute clusters”
    87. 87. Clusters are typically monocultures: just one type of node
    88. 88. Applications may require tuning to a particular cluster size
    89. 89. Some clouds are servers in virtual slices
    90. 90. Virtualized servers can be quickly provisioned
    91. 91. Spin-up of instances = new management task
    92. 92. Hardware gets cheaper, management…not so much
    93. 93. Enterprise cloud computing implies API leverage
    94. 94. Immediate focus on function; immediate delivery of value
    95. 95. Using appropriate frameworks enables a huge head start</li></li></ul><li>Single-Tenant (vs) Multi-Tenant Architecture<br />Shared infrastructure<br />Other apps<br />App 1<br />App 2<br />App 3<br />App Server<br />App Server<br />App Server<br />Database<br />Database<br />Database<br />OS<br />OS<br />OS<br />Server<br />Server<br />Server<br />Storage<br />Storage<br />Storage<br />Network<br />Network<br />Network<br />Single tenancy gives each customer a dedicated software stack – and each layer in each stack still requires configuration, monitoring, upgrades, security updates, patches, tuning and disaster recovery.<br />On a multi-tenant platform, all applications run in a single logical environment: faster, more secure, more available, automatically upgraded and maintained. Any improvement appears to all customers at once.<br />
    96. 96. User Interface<br />Logic<br />Database<br />The technical part : Why multi-tenant matters<br />Build strategic applications<br />Customize any aspect<br />Upgrade when convenient<br />Retain IP ownership<br />Your Clicks<br />Your Code<br />Metadata representations:<br />Partitioned data, logic and customizations for multiple customers<br />Coherent Code Base and Managed Infrastructure<br />
    97. 97. PaaSTaxonamy : Proliferating Platforms<br />PaaS for theInquiring Developer<br />“Servers as a Service”<br />PaaS as anApplication Framework<br />UI as a Service<br />Virtual Servers<br />Virtual Servers<br />Virtual Servers<br />Logic as a Service<br />Virtual Servers<br />Virtual Servers<br />Integration as a Service<br />Python App Server<br />Database as a Service<br />Database as a Service<br />Database as a Service<br />Infrastructure as a Service<br />Infrastructure as a Service<br />Infrastructure as a Service<br />~Familiar Developer Model<br />Rapid Scalability<br /> Offering<br />Innovative Technology<br />Supports Large-Scale SaaS<br />Deep-Dyed Multitenancy<br />
    98. 98.
    99. 99. Thank you<br />

    ×