SRE and DevOps – Site Reliability Engineering

Both SRE and DevOps are methodologies addressing organizations’ needs for production operation management. But the differences between the two doctrines are quite significant: While DevOps raise problems and dispatch them to Dev to solve, the SRE approach is to find problems and solve some of them themselves. While DevOps teams would usually choose the more conservative approach, leaving the production environment untouched unless absolutely necessary, SREs are more confident in their ability to maintain a stable production environment and push for rapid changes and software updates. Not unlike the DevOps team, SREs also thrive on a stable production environment, but one of the SRE team’s goals is to improve performance and operational efficiency.

mobydock

devops.pm father

More Posts - Website

Follow Me:
TwitterFacebook

Shadow IT is back, with a vengeance

Since the rise of Docker, it’s not uncommon to hear the following story: our developers, instead of getting VMs from the IT department, get one giant big VM, install Docker on it, and now they don’t have to ask for VMs each time they need a new environment.

it’s good for developers, because they can finally work quickly; it’s bad for the IT department, because now they have lots of unknown resources lying around and it’s a nightmare to manage and/or clean up afterwards.

Opportunity ? threat ?

source from
https://jpetazzo.github.io/2017/10/31/devops-docker-empathy/

mobydock

devops.pm father

More Posts - Website

Follow Me:
TwitterFacebook

Rapsberry PI Docker Swarm and Portainer.io

Today we will try portainer.io to monitorize dowker containers created with docker swarm on multi piZERO workers with a RPI3 leader

to install docker on rpi :
curl -sSL https://get.docker.com | sh
then
sudo usermod -aG docker pi

To init the leader
docker swarm init

This will give you the command for the workers
docker swarm join \
--token SWMTKN-1-5awy2ej1d55mvgpq1obunnh6u2r8b0jjujel619es-7caoz16dxre2bkplp3sh \
xxx.xxx.xxx.xxx:2377

On the leader you can control your node :
docker node ls

————————–
PORTAINER.IO
————————–

To install to manage your swarm cluster you need to install it on the leader
docker service create \
> --name portainer \
> --publish 9000:9000 \
> --constraint 'node.role == manager' \
> --mount type=bind,src=/var/run/docker.sock,dst=/var/run/docker.sock \
> portainer/portainer \
> -H unix:///var/run/docker.sock

Then enjoy by connecting to :

http://IP_LEADER:9000

mobydock

devops.pm father

More Posts - Website

Follow Me:
TwitterFacebook

Building a NGINX PHP7 PHP-FPM with docker and docker-compose

Setting up Nginx

We’ll start by getting a web server and based on our requirements this will be a container running the official Nginx image. Since we’ll be using Docker Compose, we will create the following docker-compose.yml file, which will run the latest Nginx image and will expose its port 80 to port 8080:

web:
image: nginx:latest
ports:
– « 8080:80 »
Now we can run

docker-compose up
This should give you the default Nginx screen on port 8080 for localhost or the IP of your docker machine.

Now that we have a server let’s add some code. First we have to update the docker-compose.yml to mount a local directory. I will use a folder called code, which is in the same directory as my docker-compose.yml file, and it will be mounted as root folder code in the container.

web:
image: nginx:latest
ports:
– « 8080:80 »
volumes:
– ./code:/code
The next step is to let Nginx know that this folder exists.
Let’s create the following site.conf on the same level as the docker-compose.yml file:

server {
index index.html;
server_name php-docker.local;
error_log /var/log/nginx/error.log;
access_log /var/log/nginx/access.log;
root /code;
}
If you don’t have a lot of experience with Nginx, this is what we define here – index.html will be our default index, the server name is php-docker.local

To activate this setup we need to apply yet another modification to our docker-compose.yml file:

web:
image: nginx:latest
ports:
– « 8080:80 »
volumes:
– ./code:/code
– ./site.conf:/etc/nginx/conf.d/site.conf
This will add site.conf to the directory where Nginx is looking for configuration files to include. You can now place an index.html file in the code folder with contents that is to your heart’s delight. And if we run

docker-compose up
again, the index.html file should be available on php-docker.local:8080.

Adding PHP-FPM

Now that we have Nginx up and running let’s add the PHP in the game. The first thing we’ll do is pull the official PHP7-FPM repo and link it to our Nginx container. Our docker-compose.yml will look like this now:

web:
image: nginx:latest
ports:
– « 8080:80 »
volumes:
– ./code:/code
– ./site.conf:/etc/nginx/conf.d/site.conf
links:
– php
php:
image: php:7-fpm
The next thing to do is configure Nginx to use the PHP-FPM container for interpreting PHP files. Your updated site.conf should look like this:

server {
index index.php index.html;
server_name php-docker.local;
error_log /var/log/nginx/error.log;
access_log /var/log/nginx/access.log;
root /code;

location ~ \.php$ {
try_files $uri =404;
fastcgi_split_path_info ^(.+\.php)(/.+)$;
fastcgi_pass php:9000;
fastcgi_index index.php;
include fastcgi_params;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
fastcgi_param PATH_INFO $fastcgi_path_info;
}
}
In order to test this let’s rename the index.html file to index.php and replace its content with the standard:

mobydock

devops.pm father

More Posts - Website

Follow Me:
TwitterFacebook

DEVOPS DAYS AMSTERDAM

tis is IT , Next week !!!!

http://www.devopsdays.org/events/2016-amsterdam/welcome/

Wednesday, Jun 29, 2016 – Friday, Jul 1, 2016

The Program
30 June – Thursday
08:00-09:00 Registration, Breakfast, and Sponsor Booths Open
09:00-09:15 Opening Welcome
09:15-09:55 Erica Baker (Slack)
Opening Keynote
09:55-10:00 Sponsors
10:00-10:40 Adam Jacob (Chef)
The Evolution of Automation
10:40-10:45 Break
10:45-11:15 Daniël van Gils (Cloud66)
How the hell do I run my microservices in production, and will it scale?
11:15-11:30 Sponsors
11:30-12:00 Warner Moore (CoverMyMeds)
DevOps has Always Been About Security
12:00-13:00 Lunch (catered)
13:00-13:30 Avishai Ish-Shalom (Fewbytes)
The Mathematics of Reliability
13:30-13:45 Sponsors
13:45-14:15 Ignites
Jody Wolfborn (Chef) – You Don’t Belong Here: Dealing with Imposter Syndrome
Pavel Chunyayev (Levi9) – The importance of ‘why’ for software operations.
Takahiko Ito – Document Writing in CI Environment
Jason Yee (Datadog) – Breaking Brooks’ Law with DevOps.
14:15-15:00 Open Space
Open Space Opening Workshopping Bias:
Designing Solutions to
Improve Decision Making
and Unleash Your Team’s Potential
15:00-15:15 Break
15:15-15:45 Attendee Driven
Open Space #1
breakout discussions
15:45-16:00 Break
16:00-16:30 Attendee Driven
Open Space #2
breakout discussions
16:30-17:00 Closing
17:00-18:00 Sponsor happy hour (Sponsored by Red Hat)
18:00-20:00 BBQ (Sponsored by Chef) & Band
1 July – Friday
08:30-09:20 Registration, Breakfast, and Sponsor Booths Open
09:20-09:30 Opening Welcome
09:30-10:00 Ken Mugrage (Thoughtworks)
What we’re learning about burnout and how a DevOps culture can help
10:00-10:10 Sponsors
10:10-10:40 Victoria Jeffrey (Chef)
Preparing for the Day After Tomorrow – Test-Driven Infrastructure
10:40-10:50 Break
10:50-11:20 Desmond Delissen
Continuous testing in the world of APIs
11:20-11:30 Sponsors
11:30-12:00 Harm Weites (Wehkamp)
One engineer, four environments, no termination protection.
12:00-13:00 Lunch (catered)
13:00-13:45 Ignites
Will Button (Trax) – An ElasticSearch Cluster Named George Armstrong Custer
Bernd Erk – Working in and with Open Source Communities
Hannah Foxwell (Pendrica) – Systems are Simple. Humans are Complex.
Gopal Ramachandran (TMNS) – Test driven Dockerized infrastructure
Marco Ceppi – Open Source Operations – punching up
13:45-14:30 Open Space
Open Space Opening
14:30-15:00 Attendee Driven
Open Space #1
breakout discussions
Security Talk Track:
Melanie Rieback (Radically Open Security)
Pentesting ChatOps
15:00-15:15 Break
15:15-15:45 Attendee Driven
Open Space #2
breakout discussions
Security Talk Track:
Guy Podjarny (Snyk)
Writing Secure Node Code
15:45-16:15 Attendee Driven
Open Space #3
breakout discussions
16:15-16:45 Closing

mobydock

devops.pm father

More Posts - Website

Follow Me:
TwitterFacebook