Cloud Computing basics Introduction, Startup

Origin and Influences
• Idea of computing in a cloud traces back to the origin of unity computing.
• A concept that computer scientist John Mccarthy Publicly proposed in 1968
• In 1969 Leonard Kleinrock, a chief scientist of the advanced research projects agency Network
(ARPANET) project that seeded the internet utilities.
• General public has been using forms of internet – based computer utilities since the mid – 1990s
through various search engines, email services , open publishing platforms and other social
media.
• In 1999, salesforce.com pioneered for remotely provisioned services into enterprises.
• Knowledge Sharing – Groups creations – Appreciations - Issues
• Updates from Clients. ROM & RAM
• Department Information's
• Account wise details.
• In 2006 Amazon.com launches amazon web services(AWS), a suite of enterprise oriented
services, provides remotely provisioned storage, computing resources and business functionality.

• Slightly different recall of the term “network cloud” or “cloud” was
introduced in the early 1990s throughout the networking industry.
• It is referred to an abstraction layer derived from the methods for
delivering data across heterogeneous (diverse) public and semi
public networks that were primarily packed switched, although
cellular networks used the “cloud” term.
• Network method supported the transmission of data from one end
(local network) point to the cloud (Wide Area Network), with the
data being further decomposed to another intended end point.

• Until 2006 cloud computing was not into the commercial arena.
• It was during the time that amazon launched its elastic compute cloud
(EC2), which enable organizations to lease computing capacity and
processing power to run their enterprise applications.
• Google Apps also began to provide browser based enterprise
applications in the same year and three years later, google app
engine became another historical milestone.

• Definitions: (Gartner Report)
• A style of computing in which scalable and elastic IT – enabled capabilities are
delivered as a service to external customers using internet technologies.
• Forrester Research:
• A standardized IT capability (Services, Software or Infrastructure) delivered
via internet technologies in a pay-per-use, self service way.
• NIST – National Institute of Standards and Technology published its
original definition in 2009 after review with industry

• Cloud computing is a model for enabling ubiquitous (global), convenient, on demand
network, access to shared pool of configurable computing resources that can be rapidly
provisioned and released with minimal management effort and service provider.
• Business drivers
• Cost reduction
• Business agility (Quickness)
• Technology Innovations
• Clustering
• Grid computing
• Capacity planning
• Virtualization
• Containerization
• Serverless environments

• Business drivers
• Industry Leaders must understood about clouds and they should get motivated first.
• Origin and inspirations of many of the characteristics, models and mechanisms
covered by the cloud must be traced back by the business drivers.
• Influences shaped clouds and the overall cloud computing market from both ends
must be noticed. These are really motivating organizations to adopt cloud
computing in support of their business automation requirements.
• Cloud Environments and cloud Technology vendors to create demand and fulfill
the customer needs.
• Cost reduction
• Business agility (Quickness)

• Cost Reduction:
• Alignment between IT costs and business performance can be difficult to
maintain.
• Growth of IT Environment often corresponds to the assessment of their
maximum usage requirements.
• Two costs need to be accounted for:
• The cost of acquiring new infrastructure and the cost of its ongoing
ownership

• Common Infrastructure – related operating overhead includes:
• Technical personnel required for environment operational
• Upgrades and patches that introduces additional testing and deployment
cycles
• Utility bills and capital expense investments for power and cooling
• Security and access control measures that need to be maintained.
• Administrative and accounts staff that may be required to keep track of
Licenses and support arrangements.

• Business Agility (Quickness):
• Business need the ability to adapt and evolve to successfully face change
caused by both internal and external factors
• Business Agility (Or Organizational Agility) is the measure of an organizations
responsiveness to change.
• IT enterprises often need to respond the business change by scaling its IT
resources beyond the scope of what was previously planned or predicated for.
• Changing business needs and priorities may require IT resources to be more
available and reliable than before.

• Clustering:
• A cluster is a group of independent IT resources that are interconnected and work
as a single system.
• System failure rate gets reduced while availability and reliability are increased.
• Grid Computing:
• A computer grid provides a platform in which computing resources are organized
into one or more logical pools (groups).
• Pools are collectively coordinated to provide high performance distributed grid,
some times referred to as super virtual computers
• Grid are more loosely coupled and disturbed
• Grid computing can involve computing resources that are heterogeneous and
geographically dispersed, which is not possible with cluster – based systems.

• Capacity Planning:
• Process of determining and fulfilling future demands of an organizations IT
resources.
• Capacity represents maximum amount of work that an IT resource is capable of
delivering in a given period of time.
• Capacity planning is focused on minimizing this discrepancy to achieve predictable
efficiency and performance.
• Capacity Planning Strategies Exist:
• Lead Strategy: Add capacity to an IT resource in anticipation of demand
• Lag Strategy: Add capacity when the IT resource reached its full capacity
• Match Strategy: Add IT resource capacity in small increments as demand
increases.

Virtualization:
• Process of converting a physical IT resource into virtual IT resource.
IT Resources can be virtualized:
• Servers: A physical server can be abstracted into a virtual server.
• Storage: A physical storage device can be abstracted into a virtual storage device or a
virtual disk.
• Network: Physical routers and switches can be abstracted into logical network
fabrics, such as VLANs
• Power: a Physical UPS and Power distribution units can be abstracted into what are
commonly referred to as virtual UPSs.

• Containerization:
• Its a form of virtualization technology that allows for the creation of virtual
hosting environments referred to as “containers” without the need to deploy
(organize) a virtual server for each solutions.
• Serverless Environments:
• It is a special operational runtime environment that does not require
developers or admins to deploy or provision servers.
• It is equipped with technology that allows for the deployment of special
software package that already include the required server components and
configuration information.

Basic Concepts and Terminology
• Cloud
• Cloud refers to a distinct IT environment that is designed for the purpose of
remotely provisioning scalable and measurable IT resources.
• This term Originated as a metaphor for the internet, which is in essence , a
network providing remote access to set of decentralized it resources.

• Container:
• Container commonly used in clouds to provide highly optimized virtual
hosting environments capable of providing only the resources required for
the software program they host.
• IT Resource:
• An IT resource is a physical virtual IT related articraft that can be either
software based, such as a virtual server or a custom software program or
hardware based, such as a physical server or a network device.

• On Premises(on Ground):
• An on premises IT resource can access and interact with a cloud – based IT
resource
• An on-premises IT resource can be moved to cloud, thereby changing it to a
cloud based IT resource
• Redundant deployments of an IT resource can exists both on premises and in
cloud based environments

• Cloud consumers and cloud providers:
• Party that provides cloud - based IT resources is the cloud provider
• Party that uses cloud based IT resources is the cloud consumer
• Scaling:
• Scaling from an IT resource perspective , represents the ability of
the IT resource to handled increased or decreased usage
demands.
• Types of scaling:
• Horizontal Scaling – Scaling out and Scaling in
• Vertical Scaling – Scaling up and scaling down

• Horizontal Scaling:
• Horizontal scaling or releasing of IT resources that are of the same type is
referred to as horizontal scaling

• Horizontal allocation of resources is referred to as scaling out and
horizontal releasing of resources is referred to as scaling in.
• Horizontal scaling is a common form of scaling within cloud
environment.

• Vertical Scaling:
• When an IT resource is replaced by another with higher or lower
capacity , vertical scaling is considered to have occurred.
• Replacement of an IT resource with another that has a higher capacity
is referred to as scaling up
• Replacement of an IT resource with another that has a lower capacity
is referred to as scaling down

• Cloud service:
• Although a cloud is remotely accessible environment, not all IT
resources residing within a cloud can be made available for remote
access
• Eg: Database or a physical server deployed within a cloud may be
accessible by other IT resources that are within the same cloud.
• A software program with a published API may be deployed to enable
access by remote clients

• A cloud service is any IT resource made remotely accessible via a
cloud

• Cloud Service Consumer:
• Cloud service consumer is a temporary runtime role assumed by a
software program when it accesses a cloud service.

GOALS and BENEFITS
• Increased responsiveness
• Reduced investments and proportional costs
• Increased scalability
• Increased Availability and Reliability

Risks and Challenges
• Increased Vulnerability due to overlapping trust boundaries
• Increased vulnerability due to shared security responsibility
• Increased exposure to cyber Threats
• Reduced operational governance control
• Limited portability between cloud providers
• Multiregional compliance and legal issues
• Cost Overruns

Increased Vulnerability due to overlapping
trust boundaries
• Moving business data to cloud means the organizations responsibility
over data security is shared with the cloud providers.
• It is difficult to establish security architecture that spans such a trust
boundaries without introducing vulnerabilities unless cloud consumers
and cloud providers happen to support the same or compactible
security frameworks, which is improbable with public clouds.
• Another consequences of overlapping – Trust boundaries relates to the
cloud providers privileged access to cloud consumer data. Since cloud
IT resources are commonly shared.
•

Increased Vulnerability due to overlapping trust
boundaries

Increased vulnerability due to shared security
responsibility
• Information security related to on- premises resources is clearly the
responsibility of the organization that owns those resources
• Information security related to cloud based resources is not sole
responsibility of the cloud providers, even if the cloud based
resources are owned by the cloud providers.
• Because information shared and processed in them is owned by
cloud consumers.
• Information security in the cloud is shared responsibility with both
the cloud providers and the consumers having a role to play in
securing the cloud environment.

Increased Exposure to Cyber Threats

Reduced Operational Governance Control

Limited portability between cloud providers

Multiregional compliance and legal issues
• Third party cloud providers will establish data centers often in affordable or
convenient geographical locations.
• UK Laws require personal data belonging to UK citizens to be kept within the UK.
• Some Organizations Pose serious legal concerns pertaining to industry or
government.
• Accessibility and disclosure of data. – potential legal issue.
• Countries have laws – data to be disclosed to certain govt agencies.
• European cloud consumer data located in US can be accessed easily by govt
agencies. –using USA Patriot Act, when comparing with many European union
countries.

Cost Overruns
• Creating business case for cloud computing can be difficult
undertaking due to the number of requirements, considerations, and
stakeholders that need to be accommodated.
• Many organizations proceed with cloud migration initiatives without
creating a proper business case for those projects
• This is one of the root causes of cost overruns and leads to poor
planning or absence governance.

Roles and Boundaries
• Cloud providers
• Cloud Consumers
• Cloud Broker
• Cloud service Owner
• Cloud resource Administrator
• Additional Roles
• Organizational Boundary
• Trust Boundary

• Cloud providers – provides cloud based IT resources (OWNS/ RESELL)
• Cloud Consumers – use IT resources made available by cloud providers

• Cloud Broker: Third party organization assumes the responsibility of
negotiating, managing and operating cloud services on behalf of cloud
consumers.

• Cloud Service Owner:
• Person or organization that legally owns a cloud service is called cloud
service owner.
• cloud service owner can be the cloud consumer or provider.

• Cloud Resource Administrator:
• Person or organization responsible for administering a cloud based IT
resource including cloud services.
• Example : Cloud service owner can contract a cloud resource
administrator to administer a cloud service

• Additional Roles:
• Cloud Auditor – third party that conducts independent
assessments of cloud environment assumes the role of the cloud
auditor
• Cloud carrier – the party responsible for providing the wire level
connectivity between cloud consumers and cloud providers
assumes the role of the cloud carrier.

• Organizational Boundary: physical perimeter that surrounds a set of IT
resources that are owned and governed by an organization.
• Only IT assets and Resources.

• Trust Boundary: logical perimeter that spans physical boundaries to
represent the extent to which IT resources are trusted

Cloud Characteristics
• On – demand usage
• A cloud consumer can unilaterally access cloud based IT resources, giving the
cloud consumer the freedom to self provision these IT resources.
• Once Configured usage of the self provisioned can be automated, requiring no
further human involvement by the cloud consumer or cloud provider. This
results in an on Demand Usage or On demand self service Usage
• Ubiquitous access
• Ability for a cloud service to be widely accessible, it requires range of devices,
transport protocols, interfaces and security technologies.
• Multitenancy ( and resource pooling)
• Characteristics of a software program that enables an instance of the program
to serve different consumers (Tenants) whereby each is isolated from other
called multitenancy

Cloud Characteristics
• Elasticity: Automated ability of a cloud to transparently scale IT, as
required in response to run time conditions or as predetermined by the
cloud consumer or cloud provider.
• Cloud providers with vast IT resources can offer the greatest range
of elasticity.
• Measured usage: ability of cloud platform to keep track of the usage of
its IT resources.
• Resiliency: resilient computing is a form of failover that distributes
redundant implementations of IT resources across physical locations

Cloud Delivery Models
• Cloud delivery model represents a specific, prepackaged combination
of IT resources offered by a cloud provider.
• There are 3 cloud delivery models available:
• Infrastructure as a Service (IaaS)
• Platform as a Service (PaaS)
• Software as a Service (SaaS)
• These three models integrated together as combining cloud delivery models.

• Infrastructure as a Service(Iaas)
• Iaas Delivery model represents a self contained IT environment comprised of
Infrastructure centric IT resources that can be accessed and managed via
cloud service based interfaces and tools.
• Environment includes hardware, network, Connectivity, Operating System,
and other “raw” IT resources.
• Than Traditional, Outsourcing environments with Iaas IT resources are
typically virtualized and packed into bundles
• Iaas Environment provides cloud consumers with a high level of control and
responsibility over its configuration and utilization.
• IT resources are not preconfigured in Iaas.

• Iaas:
• Some times cloud providers will contract Iaas offerings from other
cloud providers to scale their own cloud environment.
• Types and brands of the IT resources provided by the Iaas
products offered by different cloud providers may vary.
• A central and primary IT resource within a typical Iaas environment
is the virtual server.
• Virtual servers are leased by specifying server hardware
requirements, such as processor capacity, memory and local
storage space.

• Platform as a Service (Paas):
• The PaaS delivery model represents a predefined “ready to use” environment
typically comprised of already deployed and configured IT resources.
• PaaS relies on the usage of a ready made environment that establishes a set of
prepacked products and tools used to support the entire delivery lifecycle of
custom applications
• Common reasons of cloud consumer to use and invest in PaaS.
• Cloud Consumer wants to extend on – premises environment into the cloud for
scalability and economic purposes.
• Cloud Consumer uses the ready made environment to entirely substitute an on
premises environment.
• Cloud Consumer wants to become a cloud provider and deploys its own cloud
services to be made available to other external cloud consumers.

• PaaS products are available with different stacks.
• Example: Google App Engine offers Java and Python based environments
• Software as a Service (SaaS):
• A Software program positioned as a shared cloud service and made available
as a product or generic utility represents the typical profile of SaaS offering
• The SaaS delivery model is typically used to make a reusable cloud service
widely available to a range of cloud consumers.
• An Entire Market place exists around SaaS Products that can be leased and
used for different purposes and via different terms

Cloud Delivery Submodels
• Many Specialized variations of the cloud delivery models exists. Each
comprised of a distinct combination of IT resources.
• Cloud delivery Submodels are also typically named using the “as a
service” convention, each can be mapped to one of the three basic
cloud delivery models.
• Example: Database as a service submodel belongs to the PaaS
model.
• DB is commonly a component of the readymade environment that is
a part of PaaS.

Cloud Delivery Submodels
• Security as a service submodel of SaaS that is used to provide access to the features
that can be used to secure cloud consumer IT Assets
• Storage as a Service submodel of IaaS, which a cloud provider can use to deliver cloud
storage services to cloud consumers.
• Submodel of SaaS - Cloud Native delivery submodel allows for cloud – native
applications to be built and deployed as collection of self contained services
packaged in lightweight containers.
• These cloud native applications have no preference – it runs on infrastructure that is
virtualized, shared and elastic.
• They need to align with underlying infrastructure to dynamically grows and shrink in
response to load fluctuations.

Cloud Delivery Sub Models
• Common Cloud delivery submodels includes
• Communication as a Service(Submodel of SaaS)
• Integration as a Service(Submodel of PaaS)
• Testing as a Service(Submodel of SaaS)
• Process as a Service(a Submodel of SaaS)
• Desktop as a Service(Submodel of IaaS)

Cloud Deployment Models
• This model represents a cloud environment, distinguished by
ownership, size and access.
• There are 4 common Cloud deployment models:
• Public Cloud
• Private Cloud
• Multicloud
• Hybrid Cloud

• Public Clouds:
• Public clouds are publicly accessible cloud environment owned by a third
party cloud provider.
• IT resources on public clouds are usually provisioned via the previously
described cloud delivery models and are generally offered to cloud
consumers at a cost or are commercialized via other avenues.
(Advertisements)
• Cloud providers is responsible for creation and ongoing maintenance of the
public cloud and its IT resources.

• Private Clouds:
• Private clouds is owned by a single organization
• Private clouds enable an organization to use cloud computing
technology as a means of centralizing access to IT resources.
• Private clouds exists, there is no risks and challenges.
• Administration is carried out by internal or outsourced staff.

• Multiclouds:
• A cloud consumer organization can be cloud services and IT resources from
different public clouds provided by multiple cloud providers.
• This deployment model can be used to improve redundancy and system
backups.

• Hybrid Clouds:
• Cloud Environment comprised of two or more different cloud
deployment models
• Example: Cloud Consumer may choose to deploy cloud services
processing sensitive data to a private cloud and other less sensitive
cloud services to a public cloud. Result of this combination us a
hybrid deployment model.
• Potential disparity when we maintain hybrid cloud architectures.

Cloud Enabling Technology
• Network and Internet Architecture
• Cloud Data Center Technology
• Modern Virtualization
• Multitenant Technology
• Service Technology and Services APIs
• Case Study Example

Network and Internet Architecture
• All clouds must be connected to network
• Internet allows for remote provisioning of IT resources and are
directly supportive for universal network access.
• Cloud consumers have the option of accessing the cloud using only
private and dedicated network links in LANs, although most clouds
are internet-enabled.

Internet Service Providers (ISPs)
• Established and deployed by ISPs, the internets largest backbone
networks are strategically interconnected by core routers that connect
the worlds multinational networks
• Concept of ISP based on a decentralized provisioning and
management model.
• ISP can freely deploy, operate, and manage their networks in addition
to selecting partner ISPs for interconnection.
• No centralized entity comprehensively governs the internet, although
ICANN supervise and coordinate the internet communications.
• ICANN – Internet Corporation for Assigned Names and Numbers.

• Internet topology becomes a dynamic and complex aggregate of ISPs that
are highly interconnected via its core protocols.
• World wide connectivity it enabled through a hierarchical topology
composed of Tiers.
• Tier 1 – large Scale International Cloud Providers that oversee massive
interconnected global networks, which are connected to Tier2 large regional
providers.
• Interconnected ISPs of Tier2 connect with Tier 1 providers as well as the local
ISPs of Tier3.
• Cloud Consumers and Providers can connect directly using a Tier1 provider.

• Two fundamental components used to construct the
internetworking are
• Connectionless packet Switching (Datagram Networks)
• Router-based Interconnectivity

Connectionless packet Switching (Datagram Networks)
End to End data flows are divided into packets of a limited size that are
received and processed through network switches and routers, then
queued and forwarded from one intermediary node to the next.

Router-based Interconnectivity
• Router is a device that is Connected to multiple networks through
which it forwards packets.
• Routers manage network traffic and gauge (Measure) the most
efficient hop for packet delivery.
• Depicted router receives and forwards packets from multiple data
flows.

• Connectionless Packet switching (datagram Networks)
• End to End data flows are divided into packets of a limited size that are
received and processed through network switches and routers
• Router Based Interconnectivity
• Physical Layer
• Transport Layer Protocol – TCP & UDP
• Application Layer Protocol – HTTP, SMTP,

Technical and Business Considerations
• Connectivity Issues
• Network Bandwidth (transmission Capacity) and Latency Issues
(Packet Travels from one node to another)
• Wireless and Cellular
• Cloud access need to be received anywhere from outside
• Cloud Carrier and Cloud Provider selection:
• QoS across multiple ISPs is difficult to achieve in practice

Cloud Data Center Technology
• Grouping IT resources in close proximity with one another, rather than having them
geographically dispersed, allows for power sharing, higher efficiency in shared IT
resource usage and improved accessibility for IT personnel.
• Data Centers are typically comprises of following technologies and components:
• Virtualization – Physical Computing and Network IT resources as virtualized components that are
easier to allocate, operate release, monitor and control.
• Standardization and Modularity – Data Centers are built on hardware's and designed with modular
architectures as multiple identical blocks to support scalability, growth and speedy hardware
replacements.
• These helps in reducing investments and operational costs
• Autonomic Computing - Self Configuration, Self Optimization, Self Healing, Self protecting
• Remote Operation and Management – Except these tasks like Equipment handling and cabling or
hardware level installation and maintenance , all other tasks are done on remote consoles
• High Availability – data centers are designed to operate with increasingly higher levels of
redundancy to sustain availability .
• Security –Aware Design, Operation and Management -

• Facilities: Data center facilities are customer – designed locations, that regulate
heating, ventilation, air conditioning, fire protection and other related sub systems.
• Computer Hardware: Substantial power and storage capacity are needed – several
hardware technologies are integrated into these modular servers.
• Storage Hardware – Special storage systems involves following technologies
• Hard Disk Array
• I/O Catching
• Hot Swappable Hard Disks
• Storage virtualization
• Fast Data Replication Mechanisms
Network Storage devices divided into
SAN – Storage Area Network (SAN)
NAS – Network Attached Storage (NAS)

• Network Hardware:
• Carrier and External Network Interconnection
• Web Tier load balancing and Acceleration
• LAN fabric
• SAN Fabric
• NAS Gateways
• Serverless Environments – offered by public cloud providers on virtual
machines/ container engines
• Automation
• Virtualization
• Infrastructure and software deployment and management

• No SQL Clustering – NoT Only SQL – to generate next generation non – relational
databases that are highly scalable and fault tolerant.
• These are designed as cluster of services that acts as a single database or storage entity
called NoSQL Clustering.
• Clusters are centrally managed group of nodes connected together via a network to
process tasks in parallel.
• Features or principles of NoSQL:
• Schema less Data Model
• Scale out rather than scale up
• High Available
• Lower Operational Costs
• Eventual Consistency
• BASE, Not ACID
• API Driven Data Access
• Auto sharding and Replication
• Integrated Caching
• Distributed Query Support
• Polygot persistence
• Aggregate Focused

Modern Virtualization
• Hardware Independence – Installation of an OS configuration and application software in a
unique IT Hardware Platform results in many software – hardware dependencies.
• Virtualization is a conversion process that translates unique IT hardware into emulated and
standardized software – based copies.
• Server Consolidation – Virtualization technology enables different virtual servers to share
one physical server. This process is called server consolidation.
• Resource Replication -
• Operating System Based Virtualization
• Hardware based Virtualization
• Containers and Application based Virtualization
• Virtualization Management
• Other Considerations

Multitenant Technology
• Features:
• User Interface
• Business Process
• Data Model
• Access Control
• Characteristics:
• Usage Isolation
• Data Security
• Recovery
• Application Upgrades
• Scalability
• Metered Usage
• Data Tier Isolation

Service Technology and Service APIs
• REST services
• Six REST constraints are:
• Client – Server
• Stateless
• Cache
• Interface/Uniform Contract
• Layered System
• Code on Demands
• Web Services:
• Web Service Description Language (WSDL)
• XM Schema Definition Language(XML Schema)
• SOAP- Simple Object Access Protocol
• Universal Description, Discovery and Integration (UDDI)
• Service Agents
• Service Middle ware
• Web Based RPC

Cloud Computing basics Introduction, Startup

More Related Content

Similar to Cloud Computing basics Introduction, Startup

Recently uploaded

Cloud Computing basics Introduction, Startup