Introduction to The Cloud PDF

Tutorial 2- Introduction to the Cloud Data Centre Cloud Location Physical facility whr org Network of remote servers & store, manage, & process data centers hosted &...

Tutorial 2- Introduction to the Cloud Data Centre Cloud Location Physical facility whr org Network of remote servers & store, manage, & process data centers hosted & their data & IT infrastructure managed by 3rd- party providers Can be on-premises (owned Servers & data centers can be & operated by the org)/ located anywhr globally, & colocation facilities (3-rd users access cloud resources party data centers whr org through the internet rent space) Ownership & control Org has full control over the Cloud services are provided hardware, software & by 3rd-party vendors (eg. infrastructure Amazon Web Services, Microsoft Azure, Google Cloud Platform) Org is responsible for Users lease/ rent resources procuring, maintaining, & from these providers & have upgrading all equipment limited control over the underlying infrastructure Scalability Scaling involves physical Elastic scalability, allowing expansion-> time-consuming users to quickly allocate/ & costly de-allocate resources as needed Org need to plan for capacity Easier to adapt to changing in advance workloads & demands Cost model Upfront capital expenses Pay-as-you-go/ subscription- (CapEx) for purchasing & based pricing model setting up equipment Bear ongoing operational Users pay only for the expenses (OpEx) for resources they consume, maintenance, cooling & eliminating the need for large power upfront investments Maintenance & updates Org are responsible for Cloud providers handle maintaining, updating, & infrastructure maintenance, patching their own hardware updates, & security & software Labor- intensive Accessibility Accessible over private Accessible from anywhr with networks/ the internet, an Internet connection depending on their ↑ly accessible configuration Can be limited by physical location Suitable for remote work Disaster recovery & Org need to implement their Often offer built-in redundancy own disaster recover, redundancy & disaster redundancy strategies-> can recovery options, improving be complex & costly data resilience & availability  - Data centre networks vs ISP networks Data centre network ISP network - Interconnects all the data center - Designed to provide internet services resources tgt to end users - Pool of resources (computational, - Connect local neighbourhoods to the storage, network) interconnected using global network of cables that creates a communication network the Internet - Communication is primarily between - The traffic is primarily trying to get to diff servers the Internet/ to the data centre Feature Data Center Network ISP Network Purpose Connect servers & storage Connect end-users to the devices in a data center Internet Topology USually a hierarchical design Usually a mesh/ star design, with multiple layers of with each end-user connected switches, allows for efficient to a local router, allows for routing of traffic & provides efficient routing of traffic redundancy in case of a between end-users & the failure Internet Bandwidth Very ↑ bandwidth, need to be Varies depending on the ISP able to handle the traffic & the plan that the end- user generated by the servers & subscribes to storage devices Latency ↓ latency is critical, any delay Latency is < critical than  in the delivery of data can bandwidth, most applications have a -ve impact on the that are used by end-users are performance of the not latency- sensitive applications Security ↑ security requirements, ↓er security requirements prioritize internal security & than a data center network, access control address external threats, eg. DDoS attacks & malicious traffic, implement robust security measures eg. inc. firewalls, intrusion detection systems, & traffic filtering Network size Smaller in scale, often Vast & cover large contained within a single geographical regions, physical location & serve a sometimes spanning multiple specific org’s needs countries/ even continents Traffic patterns Mainly handle east-west Handle a mix of east-west & traffic-> communication north-south traffic. North- between servers & resources south traffic involves data within the same data center. moving from the ISP’s The traffic is ↑- speed, ↑- network -> external latency connections destinations on the Internet & vice versa. This traffic involves a wide range of applications & services Redundancy & reliability Prioritize ↑ availability & Emphasize reliability but on a redundancy, employing tech larger scale, use diverse eg. load balancing, failover routing paths, multiple data  mechanisms, & redundant centers, & redundancy at hardware to minimize various lvls to ensure internet downtime connectivity even in the face of failures - Data center network topologies - 2- tier topology - Simpler than the 3-tier topology - Consists of only 2 layers: the access layer & the core layer - Access layer - Connecting the servers to the network - Core layer - Providing ↑- speed connectivity between the access layer switches - Mesh topology - Provides redundancy & fault tolerance - Each device is connected to every other device  - If 1 link fails, there are other links that can still be used to communicate - Ring topology - Similar to a mesh topology, but the links are arranged in a ring - Easier to troubleshoot problems, as the problem can be isolated to a specific link - Star topology - The simplest topology - All devices are connected to a central switch - Easy to manage the network, but it can be a bottleneck if the central switch fails  - The best topology for a particular data center will depend on - Size & complexity of the data center - Traffic patterns - Budget - Additional answers from the answer sheet (not in question) - The looped triangle, looped square, loop-free U, & loop- free inverted U are all network topologies that are used to connect switches in a data center - Variations of the mesh topology- > all switches are connected to each other - The main difference between these topologies is the way that they handle loops - A loop occurs when there is > 1 path between 2 points in a network - Loops can cause traffic congestion & instability - The looped triangle topology - Has a loop between each switch - Provides redundancy in case of a link failure, but it can also cause congestion - The looped square topology - Has a loop between each pair of adjacent switches - Provides redundancy & ↓ congestion - > complex to implement & manage - The loop-free U topology - Has ╳ loops - The most efficient in terms of bandwidth utilization - Does ╳ provide redundancy in case of a link failure - The loop-free inverted U topology - Similar to the loop-free U topology, but it has an additional link between the 2 switches at the top of the U - This link provides redundancy in case of a link failure Topology Loops Redundancy Congestion Complexity Looped triangle Yes Yes Yes Simple Looped square Yes Yes < than looped Complex triangle Loop- free U No No No Simple Loop-free No Yes No Complex inverted U Tutorial 3- Data Center Topologies Bob's Role and Objective: Bob is an app developer. Plans to develop a new mobile app within the Android framework. Challenge: Developing the app from scratch would be time-consuming. Solution Sought: Searches for cloud providers on the Internet. Looks for kit services (pre-built tools or components). Intends to integrate cloud-based tools directly into the mobile app. Goal: Save development time by leveraging cloud-based tools. Question Service model? - Platform as a Service (Paas) - Provides a platform & environment for developers to build, test, & deploy applications w/o managing the underlying infrastructure (eg. servers, storage) - Eg. - Google App Engine - Ms Azure - AWS Elastic Beanstalk Provide development tools, middleware, databases & frameworks directly accessible over the Internet - Why? - Bob needs tools & frameworks to accelerate the development process of his Android app, specifically by avoiding starting from scratch - PaaS platforms offer development kits, SDKs (software development kits), APIs (Application Programming INterfaces), & other resources tailored for building & integrating new apps - Allow Bob to access pre-built components & code, significantly ↓ development time - How PaaS saves time & supports app development? - Ready-to-use development tools - With PaaS, Bob can access a full suite of tools & libraries that help streamline coding, testing, & deploying his app within the Android framework - Scalability & flexibility - PaaS allows him to focus on writing the app’s code w/o worrying about scaling infrastructure - Can easily adjust as his app grows, saving both time & costs - Automatic updates & maintenance - Since the PaaS provider manages updates & maintenance of the underlying software, Bob doesn’t have to spend time on backend management, focusing solely on the app’s functionality & user experience  - Role: - You are the Chief Information Officer (CIO) of a company. Company Context: - The company has higher-level security requirements. Boss's Plan: - Intends to introduce a cloud computing solution. - Goal is to replace the current on-premises database. Question: - Determine the best cloud service deployment model among the four options. Public Cloud Private Cloud Community Hybrid Cloud Cloud Overview Services (eg. Infrastructure is Shared Private + public AWS, Google dedicated to a infrastructures cloud-> data & Cloud, Azure)- single org & can used by several applications can available to the be managed org with similar be shared general public, internally/ by a security, between them whr 3rd-party compliance & infrastructure is provider performance shared with requirements other orgs Resources are Offers > control Offers a Provides the managed by over security, collaborative flexibility to 3rd-party resources & data environment whr store sensitive providers-> resources are data in the accessible & tailored for a private cloud cost-effective specific while using the community’s public cloud for needs < sensitive applications/ scalability needs Security Scalability ↑er security-> Like private Allows org to Analysis : Pros infrastructure is clouds, leverage the best ↓er upfront costs not shared community of both worlds- clouds provide ↑ security for control over data sensitive data in & compliance the private cloud & cost- efficiency for non- sensitive operations in the public cloud Wide range of Allows for > The shared Allows for services granular control infrastructure flexibility, of security serves org with scalability & measures, similar concerns disaster recovery customization of (eg. gov options firewalls & data agencies/ encryption industry- standards specific entities), leading to shared Major providers Ideal for compliance & invest heavily in companies with security security strict regulatory responsibilities measures, compliance compliance certs needs (eg. (eg. ISO, healthcare, GDPR) & finance) encryption tech Security Security risks While > secure, While the Can introduce Analysis: Cons stem from the it is expensive to infrastructure is complexity multi-tenant maintain & shared, the num when managing nature of public managed of users is & securing diff clouds- limited infrastructures. resources are compared to the The coordination shared among public cloud, between public multiple orgs making it & private cloud somewhat > services requires While robust, If hosted secure. careful some companies on-premises, the However, it’s integration to are company must still vulnerable ensure consistent uncomfortable ensure to breaches/ security relying on 3rd continuous mismanagement practices across parties for updates, of shared environments security monitoring & resources  security practices Security Might work for Perfect for Ideal for sectors Suitable for org Analysis: Use < sensitive mission-critical eg. gov/ needing both case operations/ data applications, industries whr ↑-lvl security for with fewer sensitive diff orgs sensitive data regulatory financial/ collaborate with (private cloud) restrictions, ubt healthcare data/ common & flexibility/ not ideals for when strict security cost savings for companies with regulatory requirements < critical data stringent compliance (eg. (eg. healthcare (public cloud) security HIPAA, consortiums) requirements PCI-DSS) is required Verdict Not commended ↑ly Recommended if Recommended for ↑ly sensitive recommended org collaborates for org that need data due to for companies within a specific a mix of both potential prioritizing industry that security & security security ^ requires shared scalability, vulnerabilities & control over compliance & allowing lack of direct infrastructure, security sensitive data to control despite ↑er costs practices be protected while leveraging the cost benefits of the public cloud Final evaluation Least secure Best for Suitable for Strong option & not security- focused niche industries alternative if ideal for ↑- org due to whr orgs have your org needs a security complete control common balance between environments, & customizable compliance ↑- lvl security & though it could security requirements scalability be used for measures non-sensitive operations - In a scenario whr your company has a ↑er- lvl security requirement, a Private Cloud/ Hybrid Cloud would be the best options, depending on the need for flexibility & resource mgt  - How can energy efficiency be achieved in cloud computing? May refer to the strategy used by the cloud service provider/ propose own strategy (asked to skip during tutorial- not that important ig?) - Energy efficiency in cloud computing can be achieved through a variety of methods, both at the hardware & software lvls - Software techniques Virtualization Allows multiple virtual machines to run on a single physical server Improve energy efficiency by ↓ing the num of servers that need to be powered on Dynamic Allows servers to be powered down when they are not in use power mgt ↓ energy consumption during periods of ↓ activity Load balancing Distributes traffic across multiple servers Improve performance & ↓ energy consumption Resource Algorithms can be used to ensure that resources are allocated efficiently to allocation workloads ↓ energy consumption by preventing servers from being underutilized/ overloaded Job scheduling Algorithms can be used to optimize the execution of workloads ↓ energy consumption by minimizing the amount of time the servers need to be powered on - Hardware techniques Energy-efficient servers Servers that are designed to consume < power while delivering the same performance Liquid cooling > efficient way to cool servers than traditional air cooling ↓ energy consumption & extend the lifespan of servers Free cooling Uses outside air to cool servers in cooler climates ↓ energy consumption by eliminating the need for mechanical cooling  - Others Renewable energy sources Eg. solar & wind power, to power the data centers, ↓ the environmental impact of cloud computing Choose the right cloud provider Some cloud providers are > energy- efficient than others Look for a provider that has a commitment to sustainability & that uses energy- efficient technologies Right- size your resources Make sure that you are using the right amount of resources for your workloads Overprovisioning resources can lead to wasted energy Monitor your usage Monitor your cloud usage to identify areas whr you can improve efficiency Eg. you may be able to turn off unused servers/ consolidate workloads Tutorial 4- Cloud Deployment Models - Virtual Private Cloud & Inter- Cloud (benefits & drawbacks) - VPC - Private cloud computing environment which is within a public cloud - Provisions logically isolated sections of a public cloud to provide a virtual private environment - Resources are available on demand to scale as needed & are ↑ly configurable - Implementation is a compromise between a public & a private model in terms of price & features - Created by defining a virtual network topology, inc. subnets, routing tables, & security rules Benefits Drawbacks Security Cost - Provide a ↑ lvl of security for cloud - Can be > expensive than other cloud resources hosting options, eg. shared hosting/ - Can isolate VPC from other VPCs & dedicated servers from the public internet - VPCs require you to provision - Can control how resources & manage your own communicate with each other & with infrastructure the outside world Flexibility Complexity - ↑ly customizable - Complex to set up & manage, - Can define own network especially for orgs that are new to topology & security rules cloud computing - Can launch a wide variety of cloud resources into VPC Scalability Performance - Can scale to meet changing needs - Can have a performance impact on - Can easily add/ remove your applications, esp if you are not resources from VPC as needed careful about how you design & implement your VPC Cost- effectiveness Vendor lock-in - Can help save $ on cloud costs. - If you choose to use a managed VPC - By launching resources into a service from a cloud provider, you  VPC, can take advantage of the may become locked into that economies of scale offered by provider’s platform, making it difficult public cloud providers to switch to a diff cloud provider in the future Limited customization - Compared to on- premise solutions, it is challenging to customize VPC completely Dependence on the Internet - Rely on the Internet to connect to the public cloud provider’s infrastructure, so your VPC may be impacted by Internet outages/ performance issues Security risks - Still some risks can be involved - Eg. if your VPC is not properly configured, it could be vulnerable to attack - Commonly used for Web applications Deploy ↑ly scalable web applications that are secure & isolated from the public internet Databases Secure databases, inc. mission-critical enterprise databases DevOps Create isolated development & testing environments Hybrid Cloud Connect on-premises data centres to the cloud, creating a hybrid cloud environment - Inter-Clouds (aka cloud of clouds/ cloud federation) - A theoretical model for cloud computing services based on the idea of combining many diff individual clouds into 1 seamless mass in terms of on-demand operations - Ensure that a cloud could use resources beyond its reach, taking advantage of pre-existing contracts with other cloud providers Benefits Drawbacks ↑ agility & flexibility Complexity - Allows org to choose the best cloud - Complex to set up & manage, esp for services for their specific needs, org that are new to cloud computing regardless of the provider - Help org to be > agile & responsive to changing biz requirements ↓ costs Cost - Help org to save $ on their cloud costs - Can be expensive, esp if you need to by allowing them to take advantage of connect & manage multiple cloud the best pricing & features from diff services from diff providers providers Improved performance & reliability Security risks - Improve the performance & reliability - Introduce new security risks, eg. the of cloud-based applications by risk of data breaches & unauthorized distributing workloads across multiple access to your cloud resources cloud providers - Help to ↓ the impact of outages/ performance issues from a single provider Enhanced security Vendor lock-in - Improve the security of cloud-based - If you choose to use a managed applications by providing a single inter-cloud service from a cloud layer of security for multiple cloud provider, you may become locked into services that provider’s platform, make it - Help to ↓ the risk of data difficult to switch to a diff cloud breaches & other security provider in the future threats Lack of standardization - No standard for inter-cloud connectivity & mgt, make it difficult to connect & manage cloud services from diff providers Performance & reliability challenges - Introduce new performance & reliability challenges, eg. network latency & jitter  Immature ecosystem - Still immature, there are fewer tools & services available to help you manage your inter-cloud environment - Types of Inter-Cloud: Multi Cloud & Federated Cloud (cloud federation)- differences? Multi-cloud Federated Cloud (Cloud Federation) - The use of 2/> cloud computing - Manage multiple internal & external services from several diff cloud cloud computing services for to meet providers biz needs - Environment could be completely - Enables org to share & manage private, completely public/ a resources across multiple cloud combination of both providers - Biz use a multi-cloud environment to - Uses standards-based protocols, eg. allocate computing resources & ↓ the the Open Cloud Computing Interface risk of downtime & data loss (OCCI) - Can also ↑ the computing power & storage available to biz - Cloud innovations in recent years have led a shift from single-user private clouds to multi-tenant publics clouds & hybrid clouds - Benefits of federated cloud Improved manageability Provides a single layer of mgt for multiple cloud services, make it easier to manage & optimize your cloud environment ↑ security Improve the security of your cloud environment by providing a single layer of security for multiple cloud services, ↓ the risk of data breaches & other security threats ↓ costs Help to ↓ cloud costs by allowing you to take advantage of the best pricing & features from diff providers  - SLA? Eg. in each of the 4 cloud deployment models - Service-level agreement (SLA) - A contract between a service provider & its customer that defines the lvl of service that the provider will deliver - Typically inc. metrics eg. uptime, performance & support - Important for cloud computing because they help to ensure that customers are getting the lvl of service that they are paying for - Can also help to resolve disputes between customers & providers Uptime The % of time that a cloud service is available Eg. a cloud provider might offer an SLA of 99.9% uptime-> the service would be expected to be unavailable for < 8 hrs/ year Performance Inc. things eg. response time, throughput, & latency Eg. a cloud provider might offer an SLA of 100 ms average response time for a particular API Support Inc. things eg. response time to tickets & resolution time for problems Eg. a cloud provider might offer an SLA of 4-hr response time to tickets & 24-hr resolution time for critical problems - Key points in SLA beside metrics stated above: Responsibilities of each party Clearly define the responsibilities of both the service provider & the customer, outline what the service provider will deliver & what the customer is expected to do/ provide in return- > helps prevent misunderstandings & disputes Penalties & remedies Inc. penalties/ remedies for the service provider if they fail to meet the agreed-upon service lvls - Could inc. financial compensation to the customer/ other forms of remediation Monitoring & reporting Define how performance will be monitored & reported - May involve regular reporting on key metrics-> allows both parties to track the service’s performance  Termination & exit strategy Outline the T&Cs for terminating the agreement & transitioning to another service provider if necessary. They may specify notice periods & data migration procedures - Public cloud/ private cloud Service Level Agreement (SLA) This SLA is made on [date] between [public/ private cloud provider] (hereinafter referred to as “Provider”) & [customer] (hereinafter referred to as “Customer”) 1. Services Provider agrees to provide Customer with the following services (the “Services”) - [List of services] 2. Uptime Provider agrees that the Services will have an uptime of 99.9% over any calendar month. Uptime is defined as the percentage of time that the Services are available for use by Customer 3. Performance Provider agrees that the Services will meet the following performance metrics: - [List of performance metrics] 4. Support Provider agrees to provide Customer with 24/7 support for the Services. Support is defined as the provision of assistance to Customer in resolving any problems that they may experience with the Services 5. Remedies If Provider fails to meet any of the above SLA commitments, Customer may be entitled to a service credit from Provider. The amount of service credit will be determined by the severity of the breach & the impact on Customer This SLA constitutes the entire agreement between the parties with respect to the Services & supersedes all prior/ contemporaneous communications, representations, / agreements, whether oral/ written No modification of this SLA shall be effective unless in writing & signed by both parties. This SLA shall be governed by & construed in accordance with the laws of the State of [state]. If any provision of this SLA is held to be invalid/ unenforceable, such provision shall be struck from this SLA & the remaining provisions shall remain in full force & effect. IN WITNESS WHEREOF, the parties have executed this SLA as of the date 1st written above. [Public / Private cloud provider] [Customer] - Community Cloud Service Level Agreement (SLA) This Service Level Agreement (SLA) is made on [date] between [community cloud provider] (hereinafter referred to as “Provider”) & the members of the [community cloud name] community (hereinafter referred to as “Members”) 1. Services Provider agrees to provide Members with the following services (the “Servicers”) [List of services] 2. Uptime Provider agrees that the Services will have an uptime of 99.9% over any calendar month. Uptime is defined as the % of time that the Services are available for use by Members  3. Performance Provider agrees that the Services will meet the following performance metrics: [List of performance metrics] 4. Support Provider agrees to provide Members with 24/7 support for the services. Support is defined as the provision of assistance to Members in resolving any problems that they may experience with the Services. 5. Remedies If provider fails to meet any of the above SLA commitments, members may be entitled to a service credit from provider. The amount of the service credit will be determined by the severity of the breach & the impact on members 6. Governance The community cloud will be governed by a steering committee, which will be composed of representatives from Provider & the Members. The steering committee will be responsible for making decisions about the cloud, inc. setting policies & resolving disputes 7. Fair use Members are expected to use the cloud resources in a fair & reasonable manner. Provider may implement fair use policies to prevent Members from consuming excessive resources 8. Billing Members will be billed for their use of the cloud resources on a monthly basis. The billing model will be determined by provider & the members in consultation with each other 9. Exit Members may exit the cloud at any time by providing Provider with 30 days’ notice. Provider will work with the Member to transfer the Member’s data & applications to another cloud provider/ on-premises environment This SLA constitutes the entire agreement between the parties with respect to the Services & supersedes all prior/ contemporaneous communications, representations/ agreements, whether oral/ written No modification of the SLA shall be effective unless in writing & signed by both parties. This SLA shall be governed by & construed in accordance with the laws of the State of [state] If any provision of this SLA is held to be invalid/ unenforceable, such provision shall be struck from this SLA & the remaining provisions shall remain in full force & effect. IN WITNESS WHEREOF, the parties have executed this SLA as of the date 1st written above. [Community cloud provider] Members of the [community cloud name] community - Hybrid Cloud Service Lvl Agreement (SLA) This Service Level Agreement (SLA) is made on [date] between [hybrid cloud provider] (hereinafter referred to as “Provider”) & [customer] (hereinafter referred to as “Customer”). 1. Services Provider agrees to provide Customer with the following services (the “Services”): [List of services] 2. Uptime Provider agrees that the cloud services that are hosted in the public cloud will have an uptime of 99.9% over any calender month. Uptime is defined as the % of time that the Services are available for use by Customer.  3. Performance Provider agrees that the cloud services that are hosted in hte public cloud will meet the following performance metrics: [List of performance metrics] 4. Support Provider agrees to provide Customer with 24/7 support for the Services. Support is defined as the provision of assistance to Customer in resolving any problems that they may experience with the Services 5. Remedies If Provider fails to meet any of the above SLA commitments, Customer may be entitled to a service credit from Provider. The amount of the service credit will be determined by the severity of the breach & the impact on Customer 6. Hybrid Cloud Environment Provider agrees to manage the hybrid cloud environment on Customer’s behalf, inc. the following tasks - Provisioning & managing resources in both the public cloud & private cloud - Migrating workloads between the public cloud & private cloud - Orchestrating workloads across the public cloud & private cloud - Ensuring security & compliance across the hybrid cloud environment This SLA constitutes the entire agreement between the parties with respect to the Services & supersedes all prior/ contemporaneous communications, representations, / agreements, whether oral/ written No modification of this SLA shall be effective unless in writing & signed by both parties. This SLA shall be governed by & construed in accordance with the laws of the State of [state]. If any provision of this SLA is held to be invalid/ unenforceable, such provision shall be struck from this SLA & the remaining provisions shall remain in full force & effect. IN WITNESS WHEREOF, the parties have executed this SLA as of the date first written above. [Hybrid cloud provider] [Customer] Tutorial 5- Cloud Deployment Models - Organization Context: ○ A mid-sized healthcare provider. ○ Core business is providing quality healthcare, not IT management. - Current Challenges with On-Premises System: ○ Frequent updates required. ○ High maintenance costs. ○ Limited scalability. - Decision to Move to the Cloud: ○ Factors to consider in determining whether moving to the cloud is the right decision. - Core biz focus - Since IT mgt isn’t their core biz, outsourcing to a cloud provider could allow them to focus on patient care - Cost-benefit analysis - Cloud solutions may ↓ maintenance & infrastructure costs, though they need to ensure the long-term cost of cloud services aligns with their budget - Scalability - Cloud solutions offer > scalability, enabling the org to handle growth in patient data & services > efficiently - Security & compliance - The provider must ensure the cloud service complies with healthcare regulations eg. HIPAA (if applicable) & provides robust data protection - Provider evaluation - They need to assess if there are reliable cloud providers who can meet their specific requirements for uptime, support & data security - Case Study Context: - Company Type: Software development company. - Project Requirement: Create a custom web application. - Key Needs: - Complete control over user experience. - Ability to customize the application for specific client needs. - Concerns: - Costs. - Ensuring data security. Question: Identify the best cloud service model (SaaS, PaaS, or IaaS) for the company’s needs and explain why. - The software development company should choose the PaaS (Platform as a Service) model - Customizability - PaaS provides complete control over the application & allows developers to customize it according to client needs - Developer tools - PaaS platforms often include integrated tools for development, testing, & deployment, streamlining the workflow - Security - While the company must handle some data security measures, they retain > control than with SaaS - Cost management - PaaS balances cost- efficiency & functionality better than IaaS, as it doesn’t require the org to manage the underlying infrastructure  - Case Study Key Points: Organization Context: ○ A multinational corporation operating in various countries. ○ Subject to strict data privacy regulations. Requirements: ○ Flexibility offered by the public cloud. ○ Control over sensitive data to ensure compliance with local regulations. Question 1: Recommend a suitable cloud deployment model. Considerations: ○ Need to balance flexibility with data control. ○ Must ensure compliance with diverse data privacy laws in multiple countries. Question 2: If public cloud is the only option due to budget constraints: ○ Recommend a suitable service model to meet company requirements. ○ Consideration: Balancing budget with data privacy and security. Identify features or configurations that help maintain compliance. - The multinational corporation should adopt a Hybrid Cloud deployment model Data control A hybrid approach allows the org to store sensitive data in a private cloud to comply with local regulations while leveraging the public cloud for < critical operations Flexibility The model provides the flexibility to scale services across diff regions w/o compromising data privacy Cost By using the public cloud for non-sensitive tasks, they can optimize costs efficiency while maintaining strict control over sensitive data  Risk The hybrid model ↓ the risk of vendor lock-in by diversifying workloads mitigation across private & public environments Revision Tutorial Scenario 1 Company Context: ○ TravelNow, a travel agency. Objective: ○ Launch a mobile application for customers. Application Features: ○ Book trips. ○ Access itineraries. ○ Receive personalized travel recommendations. Cloud Solution Requirements: ○ Supports fast development cycles. ○ Integrates diverse tools (e.g., APIs, SDKs, analytics tools). ○ Offers flexibility for customization to adapt to evolving user demands. - Which cloud service model is most suitable for TravelNow’s app development & why? - PaaS, as it offers a development environment with built-in tools, frameworks, & testing capabilities. - What is a limitation of using PaaS for this project? - Potential vendor lock-in due to proprietary development environments Scenario 2 PharmaNet- pharmaceutical company-> maintain compliance while sharing research data across multiple sites - Which cloud deployment model is best for PharmaNet & why? - Hybrid cloud, as it balances security for sensitive data with the flexibility of public cloud for collaboration  - What compliance challenge might PharmaNet face with this model? - Ensuring that all cloud environments adhere to strict regulatory standards Scenario 3 Company Context: ○ StreamPlay is launching a cloud gaming service. ○ Targets gamers worldwide. Service Requirements: ○ Ultra-low latency for a seamless gaming experience. ○ High computational power to handle demanding gaming workloads. ○ Real-time data processing for smooth gameplay. Cloud Solution Needs: ○ Reliability to ensure uninterrupted service. ○ Scalability to accommodate a growing user base. ○ Global accessibility to reach users worldwide effectively. - Which cloud service model would be most suitable for StreamPlay? - IaaS, as it provides control over infrastructure & ensures ↓ latency for gaming applications - Potential drawback - Network performance issues due to latency in some regions Scenario 4 Company Context: ○ SecureVault, a financial technology firm. Objective: ○ Develop a highly secure online banking platform. Solution Requirements: ○ Compliance with strict regulatory standards (e.g., financial and data privacy regulations).  ○ End-to-end encryption to safeguard sensitive customer data. ○ Environment needs: Total control over infrastructure. Operational transparency for audit purposes. - Which cloud deployment model would you recommend for SecureVault & why? - Private cloud, as it offers complete control over security & compliance, critical for banking applications - What would be a challenge of using a private cloud in this scenario? - ↑ upfront costs for infrastructure & ongoing maintenance Scenario 5 Organization Context: ○ A city council implementing a SmartCity initiative. Project Objectives: ○ Address traffic congestion. ○ Monitor air quality. ○ Improve urban infrastructure management. Solution Requirements: ○ Deployment of IoT devices across the city. ○ Cloud solution capabilities: Support for data collection from IoT devices. Real-time analytics to process and analyze data. Facilitate collaboration among multiple government agencies and private stakeholders. - Which cloud deployment model would be most effective for this initiative? - Community cloud, as it allows multiple stakeholders (eg. gov agencies, private firms) to collaborate & share infrastructure - What is a drawback of using a community cloud for this purpose? - Potential conflicts among stakeholders regarding ownership & responsibilities Lecture 6: Laying the Groundwork for Cloud Computing - Authentication & Authorization: ○ Authentication: Verifying user identity (username, password). ○ Authorization: Specifies user access rights within the system. - Identity Providers (IdP): ○ Manages user credentials for authentication. ○ Types include OpenID, Google, Facebook (OAuth). - Computing Concepts: ○ Utility Computing: Pay-as-you-go model for computing resources. ○ Commodity Servers: General servers used to support scalability. ○ Autonomic Computing: Self-managing systems, minimal human intervention. - Hardware Virtualization: ○ Allows multiple virtual systems on a single machine. ○ Hypervisors: Software enabling virtualization, categorized as Type-1 (bare-metal) and Type-2 (hosted). - Web Development Technologies: ○ HTML5, Java, JavaScript: Widely used for web applications in cloud environments. ○ SOAP and JSON: Protocols for exchanging and structuring data. L7- Cloud Service Models - Introduction to Cloud Service Models: - Cloud computing provides resources like computing, network, storage, databases, and applications on-demand without requiring ownership or maintenance by end users. - These services are managed by the provider, ↓ management efforts for users. - Basic Cloud Service Models - Software as a Service (SaaS) [for end users] - Platform as a Service (PaaS) [for developers] - Infrastructure as a Service (IaaS) [for IT architects] - Software as a Service (SaaS) - Definition - SaaS delivers software over the Internet as an on-demand service, eliminating the need for installation on user devices. - Accessible via lightweight web browsers or thin clients on various devices like laptops, tablets, and smartphones. - Services Provided by SaaS: - Business Services: ERP, CRM, billing, sales, and HR tools, popular with startups. - Social Networks: Leveraging cloud for handling variable user loads. - Document Management: For creating, managing, and tracking digital documents. - Mail Services: Scalable for unpredictable future growth. - Characteristics of SaaS: - One-to-Many: A single instance shared by multiple tenants. - Web Access: Accessible from any location with Internet. - Centralized Management: Providers handle updates and management, ensuring users access the latest version. - Scalability and High Availability: Leveraging cloud resources for efficiency and uptime (99.99% availability). - Suitability of SaaS: - Ideal for on-demand software, startups, applications with varying loads, and multi-device compatibility. - Limitations of SaaS: - Not ideal for Real-time Applications: Dependent on Internet speed. - Data Security Risks: Data stored with third-party providers may lack full control and confidentiality. - Pros and Cons of SaaS: - Pros: Cost savings, no client-side installation, low maintenance, disaster recovery, multitenancy. - Cons: Security concerns, connectivity requirements, and limited control over data. - Platform as a Service (PaaS) - PaaS provides an environment for developers to build, test, and deploy applications online, with tools available from the provider’s data center. - Services Provided by PaaS: - Programming Languages: Java, Python, Ruby, PHP, and more. - Application Frameworks: Node.js, Rails, WordPress. - Databases: ClearDB, PostgreSQL, MongoDB. - Other Tools: Development, testing, and deployment support. - Characteristics of PaaS: - All-in-One: Development, testing, deployment, and hosting all in one platform. - Offline Access: Synchronization capabilities for offline work. - Built-in Scalability: Applications can handle varying loads efficiently. - Collaborative Development: Supports teamwork across locations. - Suitability of PaaS: - Ideal for collaborative projects, automated testing, agile development, and applications requiring fast time-to-market. - Limitations of PaaS: - Vendor Lock-in: Difficulty migrating applications between providers. - Limited Customization: Limited control over the infrastructure and platform configuration. - Pros and Cons of PaaS: - Pros: Simplifies infrastructure management, speeds up development, supports agile development, provides scalability. - Cons: Vendor lock-in, less flexibility in defining the application stack, Internet dependency. - Infrastructure as a Service (IaaS) - Definition: - IaaS provides virtualized computing, storage, and networking resources, using virtualization to offer these as virtual machines (VMs) for users. - Services Provided by IaaS: - Compute: Virtual CPUs and memory. - Storage: Backend storage for VMs and files. - Networking: Virtual routers, switches, and load balancers. - Characteristics of IaaS: - Web Access: Accessible via web browsers. - Centralized Management: Resources managed from a single console. - Elasticity and Dynamic Scaling: Scalable resources based on demand. - Shared Infrastructure: Resources shared among users, with preconfigured VMs for quick setup. - Suitability of IaaS: - Best for unpredictable usage spikes, startups with limited capital, and temporary infrastructure needs. - Limitations of IaaS: - Not ideal for Regulatory Compliance: Sensitive data might require on-premise storage. - Performance and Control: Limited control over physical infrastructure and possible latency issues. - Pros and Cons of IaaS: - Pros: Pay-as-you-go model, elastic resources, better resource utilization, supports Green IT. - Cons: Security concerns, interoperability issues, potential performance limitations due to network latency. - Summary - Service Models - SaaS: Software accessible online without installation. - PaaS: Development environment with tools for application building and deployment. - IaaS: Provides infrastructure resources as virtualized services. - General Advantages: Cost savings, scalability, centralized management. - General Drawbacks: Security, interoperability, and performance issues. Lecture 8: Cloud Selection - Introduction - Choosing the correct cloud service model, deployment model, and provider is critical for an organization’s success. - Once a provider is chosen, data migration to another provider can be difficult, leading to potential vendor lock-in. - A poor choice of provider can damage the IT department’s credibility. - To Go to the Cloud or Not? - Key Considerations: 1. Evaluate the Problem: - Determine the issue the organization needs to solve (technical, functional, or new service capability). - Consider whether the organization can handle the service internally. Even if feasible, it might not align with the organization’s core business focus. 2. Core Business Alignment: - If a service is not part of the organization’s core competencies or is expensive to support internally, consider moving it to the cloud. 3. Expectations for a Provider: - Identify realistic needs that a provider can meet. 4. Choosing the Right Service Model: - Once the needed service is identified, determine the service model (SaaS, PaaS, IaaS) that best fits the requirement. - Choosing a Cloud Service Model - Factors to Consider: 1. User Experience: - SaaS: Limited control over user interface (UI) and customization options. - PaaS/IaaS: Offers > control, allowing for application customization. - Bandwidth: Adequate network bandwidth is crucial for a smooth and responsive user experience. 2. Security: - SaaS: The provider has full control and access to data, which may pose risks. - PaaS: Shared responsibility between the provider and the user. - IaaS: Offers the user full control over security measures, including data encryption. 3. Compliance: - SaaS: Providers assume most compliance burdens, but organizations may still hold legal responsibility. - PaaS: Providers ensure platform-level compliance; users must ensure their applications meet standards. - IaaS: Users bear the majority of compliance responsibility, requiring due diligence to ensure proper implementation. - Choosing a Cloud Deployment Model - Key Factors to Consider: 1. User Experience: - Private Cloud: Ideal for organizations needing full control over the application, network, and client systems for optimal performance. 2. Security: - Trust is key. Determine whether to rely on a third-party provider or trust internal security measures. 3. Responsibilities: - Public Cloud: ↓ internal responsibilities by outsourcing to the provider. - Private/Hybrid Cloud: Retains more control and responsibility within the organization. - Choosing a Public Cloud Service Provider - Tips by Service Model: - SaaS Providers: - Evaluate both the application and the service provider. - Consider: - Pricing structure (e.g., pay-per-use, subscriptions). - Bulk data import/export capabilities. - How are data migrations handled? - Downtime schedules & SLA penalties for non-compliance. - Customization options for applications. - PaaS Providers: - Evaluate the platform compatibility with applications or services. - Consider: - How will you be charged? - Supported operating systems, databases, and development tools. - Scheduled maintenance and associated downtime. - SLAs, performance guarantees, and monitoring capabilities. - IaaS Providers: - Assess if the provider offers all required infrastructure components. - Consider: - Additional software inclusions. - Resource monitoring and data migration capabilities. - Maintenance schedules, SLAs, & associated penalties. - Summary - The decision to move to the cloud depends on the organization's specific needs and problems to solve. - Factors Influencing Cloud Model Selection - Service Model: User experience, security, and compliance are primary considerations. - Deployment Model: User experience, security, and responsibility allocation are key factors. - Choosing a Provider - For public cloud providers, assess application offerings, service reliability (SLAs), and costs.