Modèles, Architectures et Protocoles du Cloud Computing

Abderrahim Sekkaki

Octobre 2018

1
 • Le Plan de la présentation

1 Le Cloud : Définition et Caractéristiques

2
Modèle de Service
3
Modèle de déploiement
4

A. SEKKAKI FSAC 2
 • Qu’est-ce qu’un Cloud?

Selon le NIST (National Institute of Standards and Technology) aux

Etats-Unis : «L’informatique en nuage offre un accès réseau
universel, pratique et à la demande à un ensemble partagé de
ressources informatiques configurables, telles que des réseaux,
serveurs, systèmes de stockage, applications et services rapidement
disponibles par le biais d’un effort de gestion minimal ou d’une
interaction réduite de la part du prestataire de services ». (2009)

A. SEKKAKI FSAC 3
The first time the term was used in its current
context was in a 1997 lecture by Ramnath Chellappa

“ A new computing paradigm where the

boundaries of computing will be
determined by economic rationale rather
than technical limits alone.”
 • Le Cloud selon NIST

A. SEKKAKI FSAC 4
 • Le Cloud selon NIST

q For a service to be considered "Cloud", it should be:

§ On-demand self-service. The ability for an end user to sign up and receive
services without the long delays that have characterized traditional IT.

§ Broad network access. Ability to access the service via standard

platforms(desktop, laptop, mobile etc).

§ Resource pooling. Resources are pooled across multiple customers.

§ Rapid elasticity. Capability can scale to cope with demand peaks.

§ Measured service. Billing is metered and delivered as a utility service

A. SEKKAKI FSAC 5
• Les caractéristiques principales du Cloud

L’élasticité : capacité de pouvoir augmenter ou réduire les capacités

du service à la demande, en fonction de l’évolution des besoins.
Exemple : offre IaaS "Elastic Compute Cloud (EC2)" de Amazon
Le modèle tarifaire : proposer des offres basées sur l’usage et la
consommation des clients, en rupture avec les modèles de licences et
d’acquisitions. Les charges d’investissement (CAPEX) sont
supprimées au profit de charges d’exploitation(OPEX) plus «
maîtrisables ». Exemple : des modèles de services déjà présents dans
le monde de la téléphonie.

A. SEKKAKI FSAC 6
 Le multi-tenant : utiliser un même environnement technique pour
fournir et gérer plusieurs clients différents tout en leur donnant
l’impression qu’ils disposent de ressources qui leurs sont dédiées.
La personnalisation : possibilité d’enrichir le service commercialisé au
niveau des données ou des traitements pour qu’il répond plus
finement aux besoins de chaque client.

Accès Réseau Service à la Ressources Elasticité

demande Partagées

A. SEKKAKI FSAC 7
Fournir des ressources informatiques
come étant un service à la demande et
payer à l’utilisation.

Elasticité

1 Délivrer des ressources IT comme étant un Service, à la

A. SEKKAKI demande et payer à l'utilisation.
0 8
 Définition du Cloud Computing

De quoi parle-t-on ou ma (modeste)définition:

”Le cloud computing est une technologie

permettant de délocaliser les données et les
applications sur des infrastructures
dématérialisées accessibles depuis Internet.”

9
A. SEKKAKI
Et les entreprises ?

Des peurs...
Maitrise
Sécurité
Compétence
Changement

pérennité

10
A. SEKKAKI
En tant que , vous utilisiez
Le pour depuis longtemps

A. SEKKAKI 10
3 types de Clouds

Fléxibilité Simplicité
IAAS

PAAS

SAAS
12
A. SEKKAKI
 All of it at our
SaaS
fingertips

IaaS
Modèle de service
§ Ensemble d'outils de bas niveau pour gérer une infrastructure
physique comme les systèmes d'exploitation et la connectivité réseau,
qui sont délivrés comme des services payés à l'utilisation.

§ Base sur laquelle pourra être installée une plateforme pour y

exécuter des applications.

§ Ressources comme étant des objets virtualisés gérés via une

interface (web en général).

14
A. SEKKAKI
Modèle de service

§ Achat d’un serveur virtuel (choix hardware)

§ Connectivité Internet Garantie

§ Configuration système

§ Installation de l’application Web

§ Lancement du service

§ Itération sur les performances

15
A. SEKKAKI
Modèle de service

§ Point d’entrée dans les technologies #cloud

§ 16 % en 2010, 44 % en 2014, de plus en plus d’entreprises

utilisent des services IAAS

§ Le plus souvent comme « data center » :

q Infrastructure serveurs (dédiés)

q Délocalisation du stockage

q Sauvegarde (Backup)

16
A. SEKKAKI
Modèle de service

§ Le plus important: Amazon

v S3 / Simple Storage Service: Utilisée par

Dropbox, Ubuntu One, Second life...

v EC2 / Elastic Cloud Computer: Hébergement

de machine virtuelle Windows, GNU/Linux et
FreeBSD basée sur XEN. Utilisée par The
guardian, SNCF, Amazon, Bakinter... Wikileaks

§ Autres: OpSource, Windows Azur...

§ En France: Gandi, OVH...

Souvent basée sur des solutions
libres et open-source. 17
A. SEKKAKI
 Infrastructure as a Service
Your Application
Your
Your Your
Application
Server
Middleware Database
Your Operating System
Hypervisor

CPU Networking Storage Backup

Datacenter (Power, Cooling, Physical Security)

Their Problem Your Problem

L'IAAS c'est plus de 50% du

marché du cloud dans le monde18
A. SEKKAKI
 IaaS Benefits

• Standard network protocols that use cryptography to

prevent eavesdropping or tampering by third parties

• Consumer can run almost any software he desires,

including a custom operating system

• Ability to quickly set up large networks of VMs without

incurring the expense of purchasing and maintaining the necessary
hardware.

• High level of compatibility between legacy applications

and workloads.
 IaaS Issues and Concerns

• Running legacy software systems in the providers'

infrastructures exposes consumers to their security vulnerabilities

• An inactive virtual machine (VM) can easily become out

of date with respect to important security updates

• Consumers must verify the identity of the provider's

Web site through some means, such as checking with a third party
credential service

• Virtual machines are allocated for different consumers

from a common pool, creating potential security vulnerabilities

• Data residue from previous tenants on virtual machines

must be cleaned to prevent unauthorized release
IaaS Recommendations

• Provide virtual firewalls and virtual private networks to

defend against malicious actions

• Assess whether the provider’s data protection

mechanisms, data location configuration, and processing
technologies will meet the needs of the organization

• Require that a cloud provider offer a mechanism for

reliably deleting data on a consumer's request

• Ensure that only a limited set of trained/trusted users has

administrative access to resources

• Form a strategy for future migration of virtual machines

among alternate cloud providers
 Modèle de service

§ PaaS can be defined as a computing platform

that allows the creation of applications quickly and easily
and without the complexity of buying and maintaining the
software and infrastructure underneath it.

§ PaaS is analogous to SaaS except that, rather

than being software delivered over the web, it is a platform
for the creation of software, delivered over the web.

19
A. SEKKAKI
 Modèle de service
§ Modèle de développement d'applications.

§ Plateforme comme un service à la demande.

§ Ensemble de fonctionnalités qui sont délivrées comme des services

à l'utilisation aux développeurs qui mettent en place des applications.

§ Base sur laquelle une application peut être développée ou

déployée.

19
A. SEKKAKI
 Modèle de service

Platform as a Service (PAAS). Il s’agit d’offrir des

ressources machines et de l’espace de stockage,
mais aussi une plateforme d’exécution pour un
logiciel. Ces plateformes sont spécifiques à un
langage et à une base de données. L’exemple le plus
connu et le plus répandu est celui des plateformes
LAMP : Linux (GNU encore oublié), Apache, MySQL,
PHP. Les offres plus récentes de PaaS incluent la
notion de temps CPU, d’espace de stockage, de
bande passante consommée. On paie donc en
fonction de ce que l’on consomme.
A. SEKKAKI Source: [Link]
Modèle de service

Différences entre I et PAAS

PAAS = IAAS + …
Logiciel au niveau du serveur
(conteneur pour vos applications)

Bases de données

Intégration SOA (composants logiciels)

Runtimes (batch par exemple) 22

A. SEKKAKI
Modèle de service
Comment cela marche ?

23
A. SEKKAKI
 Modèle de service
Le PAAS pour QUI ?
§Les applications:
v Mobiles (iPhone)
vSociales (Web 2.0)

§Les entreprises
consommatricent de standars:
vBanques
vIndustries
24
A. SEKKAKI
Modèle de service

Where PaaS Makes Sense

§ PaaS is especially useful in any situation where

multiple developers will be working on a
development project or where other external
parties need to interact with the development
process.

§ PaaS is useful where developers wish to

automate testing and deployment services.
24
A. SEKKAKI
Modèle de service

Where PaaS is not the best option

§ Where the application needs to be highly portable in

terms of where it is hosted.

§ Where proprietary languages or approaches would

impact on the development process

§ Where a proprietary language would hinder later moves

to another provider ; like concerns are raised about
vendor lock-in
24
A. SEKKAKI
 Platform as a Service
Your Application
Your
Your Your
Application
Server
Middleware Database
Operating System
Hypervisor

CPU Networking Storage Backup

Datacenter (Power, Cooling, Physical Security)

Their Problem Your Problem

21
A. SEKKAKI
Modèle de service

PaaS Benefits
• Reduced disruption through easier installation, lower
distribution costs, and efficient use of software licenses

• Centralized management and data that lower data

management overhead and licensing costs

• Platform issues managed by providers on the provider

side and not the customer side.

• Savings because of provider-supplied IT support and

supporting hardware. 24
A. SEKKAKI
Modèle de service

PaaS Issues and Concerns

• Browser-based risks due to vulnerabilities in
browsers and cryptographic key strength

• Variability of network speed and reliability

• Uncertain inefficiencies of scale

• Portability of new application development

24
A. SEKKAKI
 Modèle de service

PaaS Recommendations
• Evaluate whether the application infrastructure
interfaces provided are sufficiently

• Choose systems that work with standardized

languages and tools

• Candidate systems should work with standard data

access protocols

• Analyze the provider’s data protection mechanisms,

data location configuration and database organization/transaction
processing technologies
24
A. SEKKAKI
Modèle de service

...software that is deployed over the internet... With

SaaS, a provider licenses an application to customers
either as a service on demand, through a subscription, in a
“pay-as-you-go” model, or (increasingly) at no charge.

26
A. SEKKAKI
 Modèle de service
§ Un modèle de déploiement de logiciels

§ Un client peut simplement utiliser et consommer l'application.

§ Les applications sont accessibles via des clients légers (par

exemple un navigateur web ).

26
A. SEKKAKI
 Modèle de service

SAAS
Software as a Service (SAAS). C’est l’application qui
est mise à disposition de l’utilisateur final. Ce dernier
n’a besoin d’avoir aucune connaissance technique
préalable. Il ouvre un compte, paie éventuellement
un abonnement et utilise le logiciel (souvent des
applications web) sans se soucier d’espace de
stockage, de puissance machine ou même de mise à
jour de logiciel.
Source: [Link]
27
A. SEKKAKI
 Modèle de service

Where SaaS make sense

§ Applications where there is significant interplay
between the organization and the outside world. For example, email
newsletter campaign software.

§ Applications that have a significant need for web or

mobile access. An example would be mobile sales management
software.

§ Software that is only to be used for a short term need.

An example would be collaboration software for a specific project.

§ Software where demand spikes significantly, for

example tax or billing software used once a month. 27
A. SEKKAKI
Modèle de service

Where SaaS is not the best option

§ Applications where extremely fast processing of

real time data is required.

§ Applications where legislation or other

regulation does not permit data being hosted
externally.

§ Applications where an existing on-premise

solution fulfills all of the organization’s needs.
27
A. SEKKAKI
 Software as a Service
Application

Application
Middleware Database
Server

Operating System
Hypervisor

Storage
CPU Networking Backup
YOUR DATA

Datacenter (Power, Cooling, Physical Security)

Your Their
Problem Problem
28
A. SEKKAKI
Modèle de service

SaaS Benefits
• Easier installation and lower software distribution
costs.

• Reduction of license management overheads.

• Advantages in backup and disaster recovery, ready

access to data from any location, and the potential for
facilities sharing.

• Reduce IT support needs.

• Lower up-front expenses. 27

A. SEKKAKI
Modèle de service

SaaS Issues and Concerns

• Subtle disclosures of information are

possible

• Network reliability cannot be guaranteed

• Portability for transitioning workloads

from one SaaS cloud to another
27
A. SEKKAKI
 Modèle de service

SaaS Recommendations

• Analyze the provider’s data protection mechanisms,

data location configuration and database
organization/transaction processing technologies

• Ensure that the provider protects client devices

• Require that strong encryption be used for Web

sessions
27
A. SEKKAKI
 Modèle de service

SAAS
Software as a Service (SAAS). C’est l’application qui
est mise à disposition de l’utilisateur final. Ce dernier
n’a besoin d’avoir aucune connaissance technique
préalable. Il ouvre un compte, paie éventuellement
un abonnement et utilise le logiciel (souvent des
applications web) sans se soucier d’espace de
stockage, de puissance machine ou même de mise à
jour de logiciel.
Source: [Link]
29
A. SEKKAKI
 Modèle de service
SAAS le Saint Graal du cloud
Tout est chez le fournisseur de service SAAS

Les utilisateurs doivent adapter leur processus

aux applications proposées. On ne peut pas, pour l'instant,
tout faire en SAAS.
Quelques exemples connus:
Communications unifiées (VoIP)
Gestion de la relation client (CRM...)
Messagerie électronique (Google APPS...)
Réunion virtuelle (Chat, Visio, Share...)
Portail d'entreprise (Extranet / Intranet...)
etc...
30
A. SEKKAKI
 Modèle de service
SAAS & les technologies Web
Les services SAAS se basent massivement sur les technologies
Web. En effet, coté client, seul un navigateur est disponible.

SAAS & les craintes

Sécurité des données
Pérennité du fournisseur
Changement des processus
Perte de contrôle des DSI
Localisation des données
Et problématique juridique
31
A. SEKKAKI
Modèle de service

25
A. SEKKAKI
 Cloud Computing
Services

IaaS PaaS SaaS

Hardware and Set of tools and
Applications are
software that services designed
designed for end-
powers it all – to make coding and
users, delivered
servers, storage, deploying those
over the web
networks, applications quick
operating systems and efficient

Deploy Build Consume

32
Cloud Computing Stack
X as a Services
Cloud Computing
Services

SaaS PaaS IaaS

FaaS CaaS
Cloud Computing Stack
Container as a Services

• Operating-system-level virtualization, also known as

containerization, is a technique where the kernel of an
operating system allows the existence of multiple isolated user-
space instance (container), instead of just one.
Cloud Computing Stack
Container as a Services

• Operating-system-level virtualization, also known as

containerization, is a technique where the kernel of an
operating system allows the existence of multiple isolated user-
space instance (container), instead of just one.
Cloud Computing Stack
Container as a Services

• A container generally contains an application, and all of its

relevant libraries, binaries, and other dependencies, packaged
and presented as a comprehensive container.

• Readily shipped, run, and managed in any local as well as

remote environments.

• Containers are exceptionally lightweight, highly portable,

rapidly deployable, extensible…
Cloud Computing Stack
Container as a Services

• The user-space refers to the various programs and libraries that

the OS uses to interact with the kernel (i.e. I/O, file system
manipulation, application software, etc.).

• Each user-space process (instance of a program that is being

executed) runs in its own virtual memory space and cannot
access to the memory of other processes (memory protection).

• The kernel allocates CPU shares, memory and network I/O to

each container and can provide file system isolation.
Cloud Computing Stack
Container as a Services

Its characteristics are:

• The software which run in the containers has to be able to run

on the OS and CPU architecture the host is running on.

• Containers do not run their own OS kernels, but instead rely on

the underlying kernel for OS services.

• Container can only see the container's contents and devices

assigned to the container.
Cloud Computing Stack
Container as a Services

The main differences between those two types of virtualizations

are:

• Containers do not get their own virtualized hardware but use

the hardware of the host system

• Do not have to emulate hardware and boot a complete

operating system (this is one reason why they are more
efficient)

• Container images do not need to contain a complete toolchain

to run a operating system (this means that container images are
smaller than virtual machine)
Cloud Computing Stack
Container as a Services
OS-level virtualization vs hardware virtualization
Cloud Computing Stack
Container as a Services

• Containers as a service (CaaS) is a cloud service that allows

software developers to upload, organize, run, scale, manage
and stop containers by using a provider's API calls or a web
portal interface.

• As is the case with most cloud services, users pay only for the
CaaS resources – such as compute instances, load balancing and
scheduling capabilities -- that they use.
Cloud Computing Stack
Container as a Services

Benefits:

• Reduce complexity through container abstractions.

Containers don't require dependencies on the application
infrastructure. Thus, you don't need a complex native interface
to deal with platform services.
Cloud Computing Stack
Container as a Services

Benefits:

• Leverage automation to maximize portability.

Automation replaced manual scripting. These days, it's much
more difficult to guarantee portability when using automation.
Cloud Computing Stack
Container as a Services

Benefits:

• Provide enhanced distributed computing capabilities.

This is due to the fact that an application can be divided into
many domains, all residing within containers. The portability
aspect of containers means they can execute on a number of
different cloud platforms. This allows engineers to pick and
choose the platforms that they run on, based upon cost and
performance efficiencies.
Cloud Computing Stack
Container as a Services

When to consider :

• Do you have more than 10 unique, discrete, and interconnected

services in your deployment?

• Do you have three or more programming languages you need to

support on the hosts?

• Are your ops resources constantly deploying and upgrading

services?
Cloud Computing Stack
Container as a Services

When to consider :

• Do any of your services require "four 9s" (99.99%) or better

availability?

• Do you have a recurring pattern of services breaking in

deployments because developers are not considerate of the
environment that the services will run in?

• Do you have a talented Dev or Ops team that's sitting idle?

Modèle de service

Epitaphe, Enquête sur l’évolution du Cloud Computing au Maroc, Octobre 2012.

34
A. SEKKAKI
 Cloud Computing Stack
Container as a Services

6 Cloud Computing. -FSAC 3i, 2018/2019-

7
Cloud Computing Stack
Container as a Services
Cloud Computing Stack
Function as a Services
Serverless

• Serverless applications still require servers to run

• Serverless approach is a process where we deploy the code into
a cloud and it is executed automatically, without worrying
about the underlying infrastructure

• Developers need not worry about provisioning, deploying, and

running applications, and managing physical or virtual servers in
the cloud.

• The cloud automatically provisions the infrastructure required

for your function to run and scale your serverless application
with high availability.
Cloud Computing Stack
Function as a Services
Serverless

• Amazon kicked off the “serverless” craze with AWS Lambda

(2014)

• Offering light-weight containerized event handling on top of

their virtual infrastructure platform.

• Like other Amazon Web Services, Lambda is hosted-only.

• So a market quickly sprang up for on-premises alternatives, filled
by [Link] (2014), Apache OpenWhisk (2016), Fission (2016),
Galactic Fog’s Gestalt (2016), OpenLambda (2016).
Cloud Computing Stack
Function as a Services

Serverless

The real goal of the serverless computing movement is to provide a

high level of abstraction of the compute infrastructure so that
developers can focus on solving critical business problems, deploy
them rapidly, and reduce the time it takes for business ideas to be
marketed, as opposed to the time it takes if you use traditional
infrastructure for your applications.
Cloud Computing Stack
Function as a Services

Serverless

• Atomic unit of scale has been changing from the virtual machine
to the container

• There is a new category called function -a single- purpose block

of code. It can:
• Process an image
• Transform a piece of data
• Encode a piece of video
Cloud Computing Stack
Function as a Services
Cloud Computing Stack
Function as a Services
Serverless and event-driven collision

• Event-driven computation is an architecture pattern that

emphasizes action in response to or based on the receptions of
events.

• This pattern promotes loosely coupled services and ensures that

a function executes only when it is triggered.

• It also encourages developers to think about the type of events

and responses a function needs in order to handle these events
before programming the functions
Cloud Computing Stack
Function as a Services

A system built with event-driven

architecture consists of Event
Producers that produce a stream of
events that are ingested using Event
Ingestion, and then Event
Consumers that listen for the events.
Cloud Computing. -FSAC 3i, 2018/2019-
Cloud Computing Stack
Function as a Services

Serverless and event-driven collision

• Function platforms operate along the same lines as application platforms,

except they also include language-specific frameworks.

• Instead of writing applications with multiple endpoints, the developer just

writes event handlers and maps triggers to handlers with the platform API.

• Function platforms often come with or integrate with an API Gateway to

handle proxying, load balancing, and centralized service discovery.

• Unlike application platforms, function platforms transparently incorporate

load-based auto-scaling, because they control all ingress points and
multiplexing.
Cloud Computing Stack
Function as a Services

,, FaaS is a small program or function that performs small tasks

that are triggered by an event, unlike a monolithic app,
which does lots of things.
It breaks an app into small, self-contained programs or
functions instead of the monolithic app that runs on PaaS and
performs multiple functions.
FaaS can be seen running on stateless, ephemeral
containers created and maintained by the cloud.
Cloud Computing Stack
Function as a Services
Cloud Computing Stack
Function as a Services

Serverless and event-driven collision

• Function platforms operate along the same lines as application platforms,

except they also include language-specific frameworks.

• Instead of writing applications with multiple endpoints, the developer just

writes event handlers and maps triggers to handlers with the platform API.

• Function platforms often come with or integrate with an API Gateway to

handle proxying, load balancing, and centralized service discovery.

• Unlike application platforms, function platforms transparently incorporate

load-based auto-scaling, because they control all ingress points and
multiplexing.
Cloud Computing Stack
Function as a Services
Cloud Computing Stack
Function as a Services

• Functions are limited in how long each invocation is allowed to

run.

• Each cloud provider has different time limits for their FaaS
offering, after which the function execution will be terminated.
• AWS Lambda—5 minutes
• Azure Functions—10 minutes
• Google Functions—9 minutes

• As the execution of the functions are limited by the time limit

set by the providers, certain architectures with long running
processes are not suited for the FaaS architecture.
Cloud Computing Stack
Function as a Services

Benefits

• Reduced operational cost

• Rapid development
• Scaling costs
• Easier packaging and deployment
 Cloud Computing Stack
Function as a Services

Benefits - Reduced operational cost

• The cloud provider is able to utilize the economy of scale effect

and reduce the operational cost required to run the functions.

• The gains in cost that the cloud provider gets are also due to the
fact that everyone shares the same infrastructure, including
networking, and everyone will be using it only for a certain
period of time rather than using it all the time, like in a
traditional application.

8
3
 Cloud Computing Stack
Function as a Services

Benefits - Rapid development

• Developers can just focus on writing the code that is required to

solve the business problem rather than spending time figuring
out how to spin up the server, making sure that it is highly
available and scales based on the load.

• AWS, Microsoft Azure, and GCP all provide various tools to

develop and deploy functions to their environment easily.

8
4
 Cloud Computing Stack
Function as a Services

Benefits - Scaling costs

• With FaaS offerings, horizontal scaling is something that is

automatically managed by the cloud provider.

• They also take care of scaling up and scaling down the

infrastructure that is required to process your functions.

• The big benefit with FaaS offerings is that for the compute
infrastructure you only pay for what you need down to 100 ms
execution time (AWS Lambda).

8
5
 Cloud Computing Stack
Function as a Services
Benefits - Easier packaging and deployment

• With FaaS, all you will be doing is creating your artifact (JAR
(JVM)/ZIP ([Link] or Python)) and then uploading them directly
to the FaaS offerings.

• No need for any additional deployment or configuration

management tools to deploy your applications to a FaaS
environment.

• As there is no need to have additional configuration or

deployment tools, system administration is significantly
reduced.
8
6
 Cloud Computing Stack
Function as a Services

Limitations

• Infrastructure control
• Long running application
• Vendor lock-in
• Cold start (time it takes to boot a computer system)
• Shared infrastructure
• Server optimizations is a thing of past
• Security

8
7
 Cloud Computing Stack
Function as a Services

Use Case: Weather Application

source : [Link]
_Application_Use_Cases
8
8
Cloud Computing Stack
Function as a Services

Use Case: Mobile Backend For Social Media App

source : [Link]
ss_Application_Use_Cases
Cloud Computing Stack
Function as a Services

Use Case: Image Thumbnail Creation

source : [Link]
ess_Application_Use_Cases
Cloud Computing
Services
Cloud Computing
Services
Cloud Computing
Services
Modèles de déploiement

35
A. SEKKAKI
 Modèles de déploiement

§ Infrastructure disponible en publique ou pour un large groupe

industriel appartenant à une organisation qui vend des services
de type Cloud.

36
A. SEKKAKI
Modèles de déploiement

The Public Cloud concept stands for the following;

§ On-demand: the infrastructure or hardware is already

setup and ready to be deployed

§ Self-service: the customer chooses what they want,

when they want it

§ Scalable: customers can choose how much they want

and ramp up if necessary

§ Measureable: there’s metering/reporting so you know

you are getting what you pay for 36
A. SEKKAKI
 Modèles de déploiement
Public Cloud Benefits

§ Cost Savings – Public Cloud is in most cases less expensive than

traditional on-premise computing and will often be cheaper than
others Clouds

§ Reduced Infrastructure Footprint – Since the Public Cloud is

located on the vendor’s property, there is no physical
infrastructure footprint for Public Cloud customers

§ Increased Flexibility – Public Cloud gives high degrees of flexibility

which allows capacity to be closely mapped to demand

§ Software that can be Decoupled from Infrastructure Constraints –

by moving to the Public Cloud, organizations can scale software
without concerns about related infrastructure needs 36
A. SEKKAKI
 Modèles de déploiement

§ Private Cloud takes many of the design cues from Public Cloud,
but delivers IT resources in a way that the infrastructure or
software is operated solely for an individual organization on
dedicated hardware. Essentially, Private Cloud is a dedicated server
or group of servers running multiple instances of virtual machines
with the ability to scale up or down as demand changes.

36
A. SEKKAKI
Modèles de déploiement

§ Private Cloud can either be managed by the organization

itself or a third party and may exist on premise or off
premise.

§ The four approaches to Private Cloud:

• On-premise, managed by the organization
• Off-premise, managed by the organization
• On-premise, managed by a third party
• Off-premise, managed by a third party

36
A. SEKKAKI
 Cloud Computing Deploiment
Private Cloud Beneficts

§ Reduce costs
§ Lead to a reduced Infrastructure footprint with some
approaches
§ Drive increased flexibility around IT
§ Increase utilization rates by consolidating servers
§ Provide the benefits of Cloud Computing for organizations that
have specific requirements in terms of a technology stack (e.g.
a particular operating system or hypervisor not available from
a Public Cloud provider)

§ Can reduce the risks associated with vendor lock in

A. SEKKAKI
Modèles de déploiement

§ Hybrid Cloud is any pairing of Public Cloud with any other IT

infrastructure. In other words, Hybrid Cloud refers to Public
Cloud mixed with dedicated in-house servers, servers hosted
at a service provider, or even Cloud-based servers either
(Public or Private) at one or more Cloud providers. Like
Public Cloud, Hybrid Cloud (sometimes also called Hybrid IT)
can take several different forms.

37
A. SEKKAKI
Modèles de déploiement

There are several distinct approaches and design paradigms for

Hybrid IT;
• Cloud/Dedicated Hybrid - combination of a service providers
or a customer’s own dedicated hardware and a Public Cloud
offering. This can be single or multi-tenant, physical or
virtualized hardware

37
A. SEKKAKI
Modèles de déploiement

There are several distinct approaches and design paradigms for

Hybrid IT;
• A customers own hardware, running as a Private Cloud and
linked to a Public Cloud

37
A. SEKKAKI
Modèles de déploiement

There are several distinct approaches and design paradigms for

Hybrid IT;
• A mix of Public Cloud and logically or physically separated
Private Cloud in a Cloud providers Cloud

37
A. SEKKAKI
 Modèles de déploiement
Hybrid Cloud benefits:

§ Flexibility – It gives an organization the ability to retain specific

parts of their IT infrastructure while moving some aspects
(archiving or disaster recover, for example) to the Cloud. Hybrid
essentially adds flexibility onto existing infrastructure.

§ Maximizing ROI on Existing Infrastructure – Hybrid allows

organizations to continue to utilize their existing infrastructure
while moving excess workloads or specific parts of their operation
to the Cloud.

§ Compliance – A hybrid approach acknowledges the fact that some

organizations in particular industries wish to retain particular
workloads on-premise or on dedicated infrastructure.
37
A. SEKKAKI
 Modèles de déploiement

Specific situations where a Hybrid approach is best include;

§ Where the cost of having backups on-premise for disaster recovery

is prohibitive

§ Where web applications require high database performance but

need to scale via the Cloud for web serving

§ Where organizations wish to prototype applications cheaply

before deploying them on in-house infrastructure

§ Where avoiding vendor lock-in is a primary concern

37
A. SEKKAKI
 Modèles de déploiement

Specific situations where a Hybrid approach is best include;

§ Where the organization has legacy applications that do not make

sense to move to the Cloud

§ Where compliance requirements create a demarcation between

what can be stored on the Public Cloud and what must remain on
dedicated servers

§ Where peaks in traffic (after specific marketing campaigns for an

example) demand that traffic be “burst” to the Cloud

37
A. SEKKAKI
Modèles de déploiement

Epitaphe, Enquête sur l’évolution du Cloud Computing au Maroc, Octobre 2011.

38
A. SEKKAKI
 Cloud Computing
Multi-tenancy in its simplest form implies use of same resources or
application by multiple consumers that may belong to same
organization or different organization. The impact of multi-tenancy is
visibility of residual data or trace of operations by other user or
tenant.

From a provider’s perspective, multi-tenancy suggests an architectural

and design approach to enable economies of scale, availability,
management, segmentation, isolation, and operational efficiency.
These services leverage shared infrastructure, data, metadata,
services, and applications across many different consumers.

Multi-tenancy in cloud service models implies a need for policy-driven

enforcement, segmentation, isolation, governance, service levels, and
chargeback/billing models for different consumer constituencies.
37
A. SEKKAKI
Cloud Computing

37
A. SEKKAKI
Cloud Computing
Benefits

A. SEKKAKI
Cloud Computing
General Assumptions

• Network dependency
• Consumer’s IT skills
• Risks from multi-tenancy
• Data import/export and performance limitations

A. SEKKAKI
Cloud Computing
Promises

• Availability (SLA)

• Remedies for failure to perform

• Data preservation

• Legal care of consumer information

A. SEKKAKI
Cloud Computing
in numbers
• In 2017, the “cloud” word is not new anymore, but still
relevant and a big part of the IT transformation process.
Here are some numbers that highlight the importance
of cloud adoption:

• Gartner predicts the worldwide public cloud

services market will grow 18% in 2017 to $246.8B,
up from $209.2B in 2016.

• Gartner also predicts that just Infrastructure-as-a-

Service (IaaS) is projected to grow 36.8% in 2017
and reach $34.6B.

A. SEKKAKI
Okay !! Now how can I make
that ?
Un nouveau réseau pour 2020?
Virtualisation

39
A. SEKKAKI
La nouvelle génération
Virtualisation

40
A. SEKKAKI
 Les idées de base
Virtualisation
§Mettre en place des réseaux en fonction des applications
§Passer de réseaux matériels à des réseaux logiciels
Tout devient virtuel
Déploiement rapide des réseaux logiciels

§Séparer le plan de contrôle et le plan de données

§Introduire une intelligence plus importante
Plan de connaissance
§Centraliser le contrôle
ØBesoin d’une grande capacité de mémoire
ØBesoin d’une puissance de calcul importante
41
A. SEKKAKI
 Les nouvelles idées de base
Virtualisation
§Intégration simultanée Stockage, Calcul, Réseaux
ØAjout des modules sécurité et gestion & contrôle
§Passage à des environnements libres
ØBaisse des coûts?
ØDisparition des équipementiers tel qu’ils existent?
§Intégration d’une forte automatisation
ØOrchestration
ØPilotage automatique
§Distribution versus centralisation

42
A. SEKKAKI
Les trois révolutions du domaine des réseaux
Virtualisation

43
A. SEKKAKI
Virtualisation
Virtualisation
La virtualisation permet de mieux exploiter les performances et
ainsi baisser la consommation d’énergie à service équivalent.

Installer un serveur Intranet et un serveur Extranet sur la même

machine est devenu possible grâce à la virtualisation.

L’utilisation florissante de la virtualisation est née de ces constats:

On ne peut pas mettre tous les services sur une

même machine, les machines sont devenues trop
puissantes pour ce que l’on en fait, comme elles
consomment beaucoup d’énergie, on gaspille donc
énormément et ce n’est plus le moment
44
A. SEKKAKI
Virtualisation
Virtualisation

45
A. SEKKAKI
Les machines virtuelles

46
A. SEKKAKI
Les machines virtuelles

47
A. SEKKAKI
Réseau virtuel et datacenter

48
A. SEKKAKI
 49
A. SEKKAKI
 50
A. SEKKAKI
 51
A. SEKKAKI
 52
A. SEKKAKI
 53
A. SEKKAKI
 54
A. SEKKAKI
 55
A. SEKKAKI
 56
A. SEKKAKI
 57
A. SEKKAKI
 58
A. SEKKAKI
 59
A. SEKKAKI
 60
A. SEKKAKI
 61
A. SEKKAKI