VTU Open Elective 6th Sem CSE - Module 2 - Cloud Computing

VTU Open Elective 6th Sem CSE - Module 2 - Cloud Computing

• 1.
  Module 2 Chapter 4:Cloud Computing Architecture Chapter 5: Aneka Cloud Application Platform
• 2.
  The Cloud ReferenceModel
• 3.
  Types of Services •Infrastructure or hardware-as-a-service • Platform as a service • Software as a service
• 5.
  Infrastructure(IaaS) or hardware-as-a- service(HaaS) • Most popular and developed market segment of cloud computing • Customizable infrastructure on demand • On demand computing resources • No up-front commitment – Start small and grow as required – No contract, Only credit card! • Pay for what you use • No maintenance • Measured service • Scalability • Reliability
• 6.
  Infrastructure-as-a-Service reference implementation
• 7.
  Example • https://cloud.google.com/compute/ • https://www.google.co.in/about/datacenters/ inside/streetview/
• 8.
  Platform as aservice
• 10.
  PaaS Characteristics • Runtimeframework • Abstraction • Automation • Cloud services
• 11.
  Example • https://cloud.google.com/appengine/
• 12.
  Intro to SaaS- Definition • Software as a service (SaaS) is a model of software delivery where the software company provides maintenance, daily technical operation, and support for the software provided to their client. • It assumes the software is delivered over the internet. • Software delivered to home consumers, small business, medium and large business
• 13.
  Software Trends Traditional enterpriseSoftware – Delivered as a large package – Charge high license fee – High deployment and maintenance fee Business Trend – Smaller package with flexible coupled component – Cost effective – Easily deployed, reconfigured and updated – Standardized industrial application
• 14.
  Characteristics of SaaS •The product sold to customer is application access. • The application is centrally managed. • The service delivered is one-to-many. • The service delivered is an integrated solution delivered on the contract, which means provided as promised.
• 15.
  Examples
• 16.
  Types of clouds •Public clouds. • Private clouds • Hybrid or heterogeneous clouds • Community clouds
• 17.
  Public Cloud • Thecloud is open to the wider public • Anyone, from anywhere, and at any time • one or more datacenters connected together • Any customer can easily sign in with the cloud provider • minimizing IT infrastructure costs • handling peak loads on the local infrastructure • Multitenancy • QoS
• 18.
  Public Cloud • Apublic cloud can offer any kind of service: infrastructure, platform, or applications. • scale on demand and sustain peak loads.
• 19.
  Private clouds • Thecloud is implemented within the private premises • Public clouds are cut IT costs and reduce capital expenses, but they are not applicable in all scenarios • loss of control • control of the infrastructure • core logic and sensitive data • government and military agencies will not consider public clouds as an option for processing or storing their sensitive data
• 20.
  Private clouds hardwareand software stack.
• 21.
  Advantage of PrivateCloud • Customer information protection • protection Infrastructure ensuring SLAs • Compliance with standard procedures and operations
• 22.
  Hybrid or heterogeneousclouds • The cloud is a combination of the two previous solutions • IT infrastructure + Security • Private clouds are the perfect solution when it is necessary to keep the processing of information within an enterprise’s • Drawback – Scalability • Public Cloud Helps to Scaling Infrastructure
• 23.
  Hybrid or heterogeneousclouds • maintain sensitive information within the premises, • Service-oriented computing already introduces the concept of integration of paid software services with existing application deployed in the private premises. • OpenNebula
• 25.
  A community cloud. •Community clouds are distributed systems created by integrating the services of different clouds to address the specific needs of an industry
• 26.
  Candidate sectors forcommunity clouds are • Media industry • Healthcare industry • Energy and other core industries. • Public sector • Scientific research.
• 28.
  Benefits of CommunityCloud • Openness • Community • Graceful failures • Convenience and control • Environmental sustainability
• 29.
  Economics of thecloud • Reducing the capital costs associated to the IT infrastructure • Eliminating the depreciation or lifetime costs associated with IT capital assets • Replacing software licensing with subscriptions • Cutting the maintenance and administrative costs of IT resources
• 30.
  Open challenges • Clouddefinition characterizes cloud computing : on-demand self-service, broad network access, resource-pooling, rapid elasticity, and measured service • Cloud interoperability and standards • Scalability and fault tolerance • Security, trust, and privacy • Organizational aspects
• 31.
  31 Chapter 5: Aneka CloudApplication Platform
• 33.
  33 Cloud middleware Open SourcePrivate Cloud Middleware Joyent /Reasonably Smart Eucalyptus Globus Nimbus Reservoir OpenNebula
• 34.
  34 Many of thegrid & cloud products only Support Open Source– what can we use on Microsoft based systems ?? Any thing new !!
• 35.
  35 ANEKA
• 37.
  37 What is Aneka? •Platform for deploying Clouds developing applications. • Service Oriented Architecture (SOA). • Provides a runtime environment and set of APIs. • Choice for flexible, extensible .NET enterprise Cloud application and deployment.
• 38.
  38 Who provides anAneka? • Manjrasoft • Named as manjrasoft due to the river called Manjira • CloudSim – Simulation Sofware • Aneka is the first Product. • Dr. Rajkumar Buyya CEO – Manjrasoft Pty Ltd Director, GRIDS Laboratory, University of Melbourne, Australia
• 39.
  39 Why Aneka? – Aneka(Sanskrit): many, in many ways, many in one… – This means: • Multiple programming models • Multiple Application Scenario • Multiple deployment models • Multiple platform and OSs
• 40.
  40 Why Aneka? • Aneka& Clouds Infrastructure as a Service Platform as a Service Software as a Service Aneka fits into the cloud architecture at the platform layer. This means that it provides a programming based interface for developing distributed application and a virtual execution environment in which the applications developed according to the published APIs can run. Public Cloud Private Cloud Aneka
• 42.
  42 Features • Current Applications –Scientific • Distributed evolutionary computation • Proteine structure prediction – Commercial • Engineering: Go Front (China): Train models rendering • Media and games: platform for on-line gaming • Financial: risk analysis • Office automation: Excel integration – Educational • Image filtering • Image rendering • Distributed systems teaching
• 43.
  43 Private Cloud SetupUsing Aneka
• 44.
  44 Aneka Network Configuration
• 45.
  45 System Requirements • HardwareRequirements: – 1G RAM, 40 GB disk space • Software Requirements: – Microsoft Windows XP Professional Edition SP 2 – Microsoft .NET framework 2.0+ – Microsoft SQL Server 9.0.x / SQL Server Express 9.0.x / MySQL Server 5.1.3.0 (Optional, if database support is required) – IIS 5.0+ (optional, if the role based security web service is required)
• 46.
  46 Installation of MaterNode • Specify the Name of the Cloud • Used for future node references • Name
• 47.
  47 Node Selection Select Typeis used to selects either Master or Slave Node
• 48.
  48 After the Installation, Starta Aneka By Service Mode / Console Mode
• 49.
  49 Aneka Enterprise CloudManagement Studio Used to monitor the master and slave nodes Enter the master URL Click Connect
• 50.
  50 Windows Credentials Windows Authentication Details
• 51.
  51 After Connecting… Master NodeDetails
• 52.
  52 Aneka Node Management Starta Aneka Select Aneka Management Studio
• 53.
  53 Aneka Node Management Enterthe IP Address of Master Node in the URL
• 54.
  54 Aneka Network Overview Slaveis connected to the Master
• 55.
  55 System Performance Monitor Usedto monitor CPU & Power Usage and Availability
• 56.
  56 Accounting Manager Account Detailssuch as Name , Status Completion time , Execution time and so on..,
• 57.
  57 What Aneka Expectfrom User • Build new applications – Custom Model • Make use of Aneka in existing applications to speed up the execution • Build Commercial relationships • Discuss investment and Business Opportunities
• 58.
  Aneka Overview
• 59.
  Aneka Frameworks
• 60.
  Platform Abstraction Layer(PAL) •Core infrastructure of the system is based on .NET technology • PAL provided features: – Uniform and platform-independent implementation interface for accessing the hosting platform access to remote nodes management interfaces – Uniform access to extended and additional properties of the hosting platform
• 61.
  Anatomy of theAneka container • Fabric Services – A) Profiling and Monitoring Services – B) Resource Management Services • Foundation Services – A) Storage management for applications – B) Accounting, billing, and resource pricing – C) Resource reservation • Application Services – A) Scheduling – B) Execution
• 62.
  Fabric Services • Lowestlevel of the software stack representing Aneka container • Consists of – A) Profiling and Monitoring Services – B) Resource Management Services
• 63.
  Fabric Services contd.. •A) Profiling and Monitoring Services – Heartbeat, Monitoring and Reporting services – Heartbeat service periodically collects the dynamic information about the node – The basic information about memory space, disk space, CPU and operating system are collected. – All these information can be stored on RDBMS or a flat file.
• 64.
  Fabric Services contd.. •B) Resource Management Services – Comprises tasks: resource membership, resource reservation and resource provisioning service – Equivalent services: Index Service(Membership catalogue), Reservation Service, Resource Provisioning Service – The Membership catalogue tracks the performance information of nodes – The Resource Provisioning Service tracks the provisioning and lifetime information of virtual nodes.
• 65.
  Foundation Services • Logicalmanagement of the distributed system built on top of the infrastructure • A) Storage management for applications • B) Accounting, billing, and resource pricing • C) Resource reservation
• 66.
  Foundation Services contd.. •A) Storage management • Centralized file storage • More suitable for compute-intensive applications • Distributed file storage • More suitable for data intensive applications • FTP is default option installed in Aneka • To support different protocols, the concept of file channel, is introduced. • File Channel identifies a pair of components: • file channel controller : server part • file channel handler : client part • Storage service supports the execution of Different programming Model
• 67.
  Foundation Services contd.. •B) Accounting, Billing, and Resource Pricing • Accounting keeps track of the status of applications in the Aneka cloud • Shows the usage of infrastructure and the execution of applications • Billing service provides detailed information about the resource usage of each user with the associated costs. • Each resource can be priced differently according to the different set of services that are available on the corresponding Aneka container or the installed software in the node.
• 68.
  Foundation Services contd.. •B) Resource Reservation • Supports the execution of distributed applications • Allows for reserving resources for exclusive use by specific applications
• 69.
  Application Services • Managethe execution of applications • Constitute a layer that differentiates according to the specific programming model • Scheduling Service and Execution Service • Scheduling Service tasks: • Job-to-node mapping • Rescheduling of failed jobs • Job status monitoring • Application status monitoring
• 70.
  Application Services contd.. •Execution Service tasks: • Controls the execution of single jobs that compose applications • Unpacking the jobs received from the scheduler • Retrieval of input files required for the job execution • Sandboxed execution of jobs • Submission of output files at the end of execution • Execution failure management • Performance monitoring • Packing jobs and sending them back to the scheduler
• 71.
  Application Services contd.. •Currently supported programming model in the Aneka Cloud: • Task Model • Thread Model • MapReduce Model • Parameter Sweep Model
• 72.
  Building Aneka clouds •Aneka is primarily a platform for developing distributed applications for clouds • Infrastructure management tools • Administrators • public, private, and hybrid clouds.
• 73.
  Infrastructure organization
• 74.
  Logical organization • dependson the configuration • The most common scenario is to use a master- worker configuration with separate nodes for storage
• 75.
  Master Node • Acommon configuration of the master node is as follows: • Index Service (master copy) • Heartbeat Service • Logging Service • Reservation Service • Resource Provisioning Service • Accounting Service • Reporting and Monitoring Service • Scheduling Services for the supported programming models
• 76.
  Storage Node • Thecommon configuration of a storage node is the following: • Index Service • Heartbeat Service • Logging Service • Monitoring Service • Storage Service
• 77.
  Worker Node • IndexService • Heartbeat Service • Logging Service • Allocation Service • Monitoring Service • Execution Services for the supported programming models
• 79.
  Private cloud deploymentmode
• 80.
  Public cloud deploymentmode
• 81.
  Hybrid cloud deployment
• 82.
  Cloud programming andmanagement • Aneka SDK -Application model -Service model • Management tools -Infrastructure management -Platform management -Application management
• 83.
  Cloud programming andmanagement • Provide a scalable middleware product • distributed applications • Application development – Developer • Management – System administrator • Aneka SDK • Management Tools
• 84.
  Aneka SDK • ApplicationModel • Service Model • Aneka provides APIs for developing applications • use of existing features • both programming models and services
• 85.
  Application Model • Anekaprovides support for distributed execution in the Cloud with the abstraction of programming models. • used by the developers and the runtime support for the execution of programs on top of Aneka • The Application Model represents the minimum set of APIs that is common to all the programming models
• 88.
  Service model • TheAneka Service Model defines the basic requirements to implement a service that can be hosted in an Aneka Cloud. • IService interface • Name and status • Control operations such as Start, Stop, Pause, and Continue methods • Message handling by means of the HandleMessage method
• 90.
  Management tools • Infrastructuremanagement • Platform management • Application management