Fandogh Cloud workshop slides

Fandogh PaaS
Workshop
#FANDOGH2018

Let the workshop begins
#FANDOGH2018

Lecturer:
Sorena Sarabadani
Software Engineer
@sorena_s

What is container?
#FANDOGH2018

What is container?
History ->
- Containers have been there for a long time, maybe from the beginning of existence.
Container can be a pocket, bag, plastic or a large full metal container used in international
transportations.
- Containers are out there because:
- They are standard for almost everything.
- Can isolate things inside and protect them
- Are easy to transport
- Easy to manage
- Cost efficient
#FANDOGH2018

What is Docker?
It’s simple and clear
#FANDOGH2018

What is a docker container?
#FANDOGH2018

What is a docker container?
A docker container is a standard unit of
software that packages up code and all its
dependencies so the application runs
quickly and reliably from one computing
environment to another.
#FANDOGH2018

Docker VS Virtual Machine
VS
#FANDOGH2018

How to register on
docker hub?
#FANDOGH2018

https://hub.docker.com/
#FANDOGH2018

How To Pull an Image?
#FANDOGH2018

How to:
Run
List
Terminate
Containers?
#FANDOGH2018

How to write Dockerfile?
#FANDOGH2018

- ADD
- COPY
- ENV
- EXPOSE
- FROM
- LABEL
- STOPSIGNAL
- USER
- VOLUME
- WORKDIR
#FANDOGH2018

FROM nginx:alpine
#FANDOGH2018

FROM nginx:alpine
The FROM instruction
initializes a new build
stage and sets the Base
Image for subsequent
instructions.
FROM
#FANDOGH2018

FROM nginx:alpine
FROM can appear
multiple times within a
single Dockerfile to
create multiple images or
use one build stage as a
dependency for another
FROM
#FANDOGH2018

FROM nginx:alpine
COPY index.html /usr/share/nginx/html
COPY has two forms:
COPY
#FANDOGH2018

A
COPY [--chown=<user>:<group>] <src>... <dest>
#FANDOGH2018

B
COPY [--chown=<user>:<group>] ["<src>",... "<dest>"]
#FANDOGH2018

FROM nginx:alpine
The COPY instruction
copies new files or
directories from <src>
and adds them to the
filesystem of the
container at the path
<dest>.
COPY
#FANDOGH2018

FROM nginx:alpine
1- cd to project root dir
2- Docker build -t hello_nginx:1.0 .
3- Docker run -d --name test_container hello_nginx:1.0
#FANDOGH2018

FROM python:3
WORKDIR /code
The WORKDIR instruction
sets the working directory for
any RUN, CMD,
ENTRYPOINT, COPY and
ADD instructions that follow it
in the Dockerfile.
WORKDIR
#FANDOGH2018

FROM python:3
WORKDIR /code
If the WORKDIR doesn’t
exist, it will be created even if
it’s not used in any
subsequent Dockerfile
instruction.
WORKDIR
#FANDOGH2018

FROM python:3
WORKDIR /code
RUN pip install click
RUN has 2 forms
RUN
#FANDOGH2018

A
RUN <command> (shell form, the command is run in a shell, which by
default is /bin/sh -c on Linux or cmd /S /C on Windows)
#FANDOGH2018

B
RUN ["executable", "param1", "param2"] (exec form)
#FANDOGH2018

FROM python:3
WORKDIR /code
The RUN instruction will
execute any commands in a
new layer on top of the
current image and commit
the results. The resulting
committed image will be
used for the next step in the
Dockerfile.
RUN
#FANDOGH2018

FROM python:3
WORKDIR /code
COPY . /code/
COPY has to forms
COPY
#FANDOGH2018

A
COPY [--chown=<user>:<group>] <src>... <dest>]
#FANDOGH2018

B
COPY [--chown=<user>:<group>] ["<src>",... "<dest>"] (this form is
required for paths containing whitespace)
#FANDOGH2018

FROM python:3
WORKDIR /code
COPY . /code/
The COPY instruction copies
new files or directories from
<src> and adds them to the
filesystem of the container at
the path <dest>.
COPY
#FANDOGH2018

FROM python:3
WORKDIR /code
COPY . /code/
CMD ["python", "logger.py"] CMD has 3 forms
CMD
#FANDOGH2018

A
CMD ["executable","param1","param2"] (exec form, this is the preferred
form)
#FANDOGH2018

B
CMD ["param1","param2"] (as default parameters to ENTRYPOINT)
#FANDOGH2018

C
CMD command param1 param2 (shell form)
#FANDOGH2018

FROM python:3
WORKDIR /code
COPY . /code/
CMD ["python", "logger.py"]
There can only be one CMD
instruction in a Dockerfile. If
you list more than one CMD
then only the last CMD will
take effect.
CMD
#FANDOGH2018

FROM python:3
WORKDIR /code
COPY . /code/
CMD ["python", "logger.py"]
The main purpose of a CMD
is to provide defaults for an
executing container.
CMD
#FANDOGH2018

Lecturer:
Mahdi Zareie
Software Engineer
@call_me_mahdi

Fandogh PaaS
Platform as a service for cloud native services
#FANDOGH2018

Problem
What is the problem we’re trying to solve by Fandogh?

Problem: Heavy operational overhead
#FANDOGH2018

Problem: Heavy operational overhead
Doing it yourself
vs
Using a PaaS
#FANDOGH2018

Problem
● Easier deployment
#FANDOGH2018

Problem
● Less maintenance overhead
#FANDOGH2018

Problem
● Better resource management
● Lower costs
#FANDOGH2018

Problem
● Better resource management
● Lower costs
● More Reliability, Less Concerns
#FANDOGH2018

Fandogh Overview
What does it look like to use Fandogh?
#FANDOGH2018

Fandogh Overview: Daily workflow
Docker Registry
Team
Version Control Server
Ci/Cd Automation Server
Building
1
Fandogh Service
2
Push
#FANDOGH2018

Fandogh Overview: What happens next
Docker Registry
S18
LB
S17
S19
S20
S21
You
Fandogh Service
Deploy command
1
2
3
4
#FANDOGH2018

s1
s1
s1
s1
s1
s1
s1
s4
s1
s1
s1
s1
s1
s1
s1
s3
s1
s1
s1
s1
s1
s1
s1
s2
Fandogh Overview: How does it work?
Fandogh CLI Fandogh Server
you
Command
s1
s1
s1
s1
s1
s1
s1
s1
Manages
Your users
1
2
3 4
#FANDOGH2018

Fandogh Overview: How does it work?
Fandogh CLI Fandogh Server
you
Command
Manages
Your users
1
2
3 4
Fandogh Cloud
#FANDOGH2018

Fandogh Features
● Flexible Docker Registry Interface
○ Internal Docker Registry
○ Docker-hub
○ Your Own Private Docker Registry
#FANDOGH2018

Fandogh Features
● Flexible docker registry interface
● Rich Runtime Environment
○ Internal Network and DNS for your services
○ Shared Persistent Storage
○ Dedicated Block-storage (coming soon)
#FANDOGH2018

Fandogh Features
● Managed Services
○ One-click deployment
○ MySQL + PHPMyAdmin
○ PostgreSQL + Adminer
○ And many more (Coming Soon)
#FANDOGH2018

Fandogh Features
● Flexible Domain management and TLS Certificate Facilities
○ Free Fandogh Domain
○ Easily use your own domain for your services
○ Painless and Free Let’s Encrypt TLS Certificate
○ Automatic Renewal for Certificates
○ Use your Own Certificate (Coming Soon)
#FANDOGH2018

Fandogh Features
● Horizontal Scaling, Painless Upgrades
○ Powerful Replication Mechanism
○ Load Balancing
○ Auto-Scaling (Coming Soon)
○ Offering high SLA with many reliable servers
○ Smart Health-check for rolling-updates
#FANDOGH2018

Fandogh Features
● Horizontal Scaling
● Easy to use Interface
○ Powerful CLI
○ Ci/Cd Compatible commands
○ Multiple Flexible Deployment
○ Simple resource management
○ Runtime command execution
○ Web Dashboard (Coming Soon)
○ Monitoring#FANDOGH2018

Fandogh Features
● Horizontal Scaling
● Easy to use Interface
● Friendly Support
○ Always Available Experts
○ All The Way Migration Technical Scort
#FANDOGH2018

DecisionShould you migrate to Fandogh paas?
#FANDOGH2018

Decision
● Being Cloud-Native (or easy to become)
○ How is your design?Stateless or Stateful services?
○ Dockerization Cost
#FANDOGH2018

Decision
○ How is your design?Stateless or Stateful services?
○ Dockerization Cost
● Load and Cost relationship
○ How does your services loads affect your costs?
○ Do you predict high load in near future?
○ Do you predict the need for flexible scalability in near future?
#FANDOGH2018

Decision
○ How is your design? Stateless or Stateful services?
○ Dockerizing Cost
● Load and Cost relationship
○ How does your services loads affect your costs?
○ Do you predict high load in near future?
○ Do you predict the need for flexible scalability in near future?
● Geolocation dependency
○ Do you have strict criteria on physical location of servers?
(except enterprise plans)
#FANDOGH2018

Using Fandogh
A few examples of using fandogh for different scenarios
#FANDOGH2018

Fandogh docker registry
How to use Fandogh internal docker registry
#FANDOGH2018

Image management has two steps
#FANDOGH2018

● Creating Image for your codebase (Only once)
#FANDOGH2018

● Creating Image for your codebase (Only once)
● Releasing new version for your codebase (for every version)
#FANDOGH2018

Deploying new service
How to deploy a new service
#FANDOGH2018

Deploying service has two steps
● Write a manifest
#FANDOGH2018

Writing service manifest
From fandogh registry
Name of the service:
ebtehaj-com-hooshang.fandogh.cloud
#FANDOGH2018

Writing service manifest
From docker hub
Name of the service:
hello-world-hooshang.fandogh.cloud
#FANDOGH2018

Deploying service has two steps
● Write a manifest
● Deploy the service using manifest
#FANDOGH2018

Deploy new service using manifest
#FANDOGH2018

Lecturer:
Soroosh Sarabadani
Founder
@SorooshPsycho

Example Voting app
● Understand Architecture
● Deploy the services manually on Fandogh
● Automate the deployment via
○ Github
○ Travis-ci
○ Fandogh-cli
#FANDOGH2018

Voting architecture
Voting App
(Python)
PostgreSQL
Worker
(Java)
Redis
Result App
(Node.js)
#FANDOGH2018

Where to find the project
git clone https://github.com/fandoghpaas/fandogh-workshop.git
#FANDOGH2018

How to deploy on
fandogh
The project manifests are located at /manifests directory.
Every service has a specific fandogh manifest that introduces
how the service should behave on fandogh.
#FANDOGH2018

Vote manifest
kind: ExternalService
name: vote
spec:
image: fandoghpaas/vote:${VERSION}
port: 80
resources:
memory: 100Mi
#FANDOGH2018

Redis service
kind: InternalService
name: redis
spec:
image: library/redis:alpine
port_mapping:
- port: 6379
target_port: 6379
resources:
memory: 100Mi
#FANDOGH2018

Worker manifest
kind: InternalService
name: worker
spec:
image: fandoghpaas/worker:${VERSION}
resources:
memory: 100Mi
#FANDOGH2018

Postgresql manifest
kind: ManagedService
name: db
spec:
service_name: postgresql
version: 9.4
parameters:
- name: adminer_enabled
value: 'true'
- name: postgres_password
value: db123
#FANDOGH2018

kind: ExternalService
name: result
spec:
image: fandoghpaas/result:${VERSION}
env:
- name: PGPASSWORD
value: db123
resources:
memory: 100Mi
Result manifest
#FANDOGH2018

Result manifest
fandogh service apply -d -f manifests/postgres-manifest.yml
#FANDOGH2018

Result manifest
fandogh service apply -d -f manifests/redis-manifest.yml
#FANDOGH2018

Result manifest
fandogh service apply -d -f manifests/result-manifest.yml -p VERSION=?
Hint:
Find version in docker hub
#FANDOGH2018

Result manifest
fandogh service apply -d -f manifests/vote-manifest.yml -p VERSION=?
#FANDOGH2018

Result manifest
fandogh service apply -d -f manifests/vote-manifest.yml -p VERSION=?
fandogh service apply -d -f manifests/worker-manifest.yml -p VERSION=?
#FANDOGH2018

Fandogh Cloud workshop slides

Recommended

More Related Content

What's hot (20)

Similar to Fandogh Cloud workshop slides (20)

Recently uploaded (20)

Fandogh Cloud workshop slides

Editor's Notes