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

Photo du profil de mobydock

mobydock

devops.pm father

More Posts - Website

Follow Me:
TwitterFacebook

Splunk – universal forwarder on Raspberry Pi 3 and Splunk enterprise on Labtop

A little post to explain how i succeed to deploy a splunk forwarder on a raspberry pi 3

First install the client splunk enterprise on your labptop
Then configure it to accept receiving data on port 9997
In the upper right, click the dropdown for “Settings”. Under Data, click Forwarding and receiving, and you will be taken to the configuration page where you can set Splunk to listen for data from your Pi.

Click “configure receiving”, and you will be taken to the receive data configuration page. Assuming this is a brand new installation of Splunk, you will have no configurations. Click “New” and you will be taken to the new configuration wizard. For now, we will just add a new listener at port 9997, and click Save.

Then install the universal forwarder on your RPI :

Download the Universal Forwarder from http://apps.Splunk.com/app/1611 to your Pi

You’ll find some help on http://docs.splunk.com/Documentation/Splunk/6.0/Forwarding/Deployanixdfmanually

but it ‘s not necessary

just download the .tar file and use : tar -xvf …. to unzip it

One important thing to know when installing the Universal Forwarder on *nix, is that the default install does NOT autorun on boot.
You can set it to autostart running the following as root:
$SPLUNK_HOME/bin/Splunk enable boot-start

To start Splunk on your forwarder, navigate to $SPLUNK_HOME /bin/ and run ./splunk start. You’ll see the standard output for startup.
At the next prompt, run ./splunk version, and you should see the version output for ARM Linux.

Congratulations, the Splunk Universal Forwarder is running on your Raspberry Pi!

Now, create a script which will be played by splunk to extract data :

edit file : $SPLUNK_HOME/bin/scripts

#! /bin/sh
for c in $(seq 1 60)
do
TIME=$(date +"%D %T.%3N %Z")
TEMP=$(vcgencmd measure_temp)
VOLTS=$(vcgencmd measure_volts)
CPU_TEMP=`echo $TEMP | cut -d \' -f 1`
VOLTS=`echo $VOLTS | cut -d V -f 1`
echo "time=$TIME|$VOLTS|$CPU_TEMP"
sleep 1
done

Then edit :
$SPLUNK_HOME/etc/system/local/inputs.conf

[default]
host = raspberrypi
[script:///opt/Splunkforwarder/bin/scripts/cpu.sh]
index = main
interval = 60
source = cpu_details
sourcetype = pi_system_scripts

Then edit :
$SPLUNK_HOME/etc/apps/SplunkUniversalForwarder/default/outputs.conf

# Version 6.0
[tcpout]
defaultGroup=my_indexers
[tcpout:my_indexers]
server=XX.XXX.XX.XXX:9997

Where XX… is the IP of your labtop

BE CAREFUL to accept on your labtop firewall (Windows) the port 9997
if you don’t you will have in the log file on the rpi in $SPLUNK_HOME/var/log/splunk/splund.log
the error :

connection to ip=ip.address:9997 timed out

When it done just start splunk on the RPI :
$SPLUNK_HOME/bin/splunk start

and you ll receive data on the search screen of the plunk enterprise client installed on your labtop :
http://localhost:8000/fr-FR/app/search/search#fr-FR/app/search/search

CONGRATULATION !! and have fun

Photo du profil de mobydock

mobydock

devops.pm father

More Posts - Website

Follow Me:
TwitterFacebook

Raspberry PI ZERO

    https://www.raspberrypi.org/

The raspberry PI ZERO : the 5$ computer

featuring:

A Broadcom BCM2835 application processor
1GHz ARM11 core (40% faster than Raspberry Pi 1)
512MB of LPDDR2 SDRAM
A micro-SD card slot
A mini-HDMI socket for 1080p60 video output
Micro-USB sockets for data and power
An unpopulated 40-pin GPIO header
Identical pinout to Model A+/B+/2B
An unpopulated composite video header
Our smallest ever form factor, at 65mm x 30mm x 5mm

I bought it yesterday and wait for te delivery

Will keep you in touch when tested

Photo du profil de mobydock

mobydock

devops.pm father

More Posts - Website

Follow Me:
TwitterFacebook

HowTo build an Docker infrastructure

What :

An infrastructure based on Varnish + Nginx + PHP-FPM + MariaDB

On Docker Containers

Why :

For a personnal blog or website

 

How : Build,Ship, Run

(Because the what is famous , we won’t do it from Dockerfiles . We will use Dockerhub images)

Step 1:

mkdir p $HOME/data/webstack/conf $HOME/data/webstack/www

 

Step 2: install NGinx

docker pull nginx

Controle your image with docker images

Launch your container

docker run name webstack_nginx_1 v $HOME/data/webstack/www:/usr/share/nginx/html:ro p 8080:80 d nginx
You can control by open your navigator and try
http://youserver:8080
Our container name is  webstack_nginx_1, the port TCP/8080 of our host will be tranfer to the port TCP/80 of the container (default port for NGinx) and it assigne in readonly the directory volume : /usr/share/nginx/html to the host directory $HOME/data/www .
To test we create some static pages :
echo « My first page » > $HOME/data/webstack/www/index.html
echo « <?php phpinfo(); ?>«  > $HOME/data/webstack/www/phpinfo.php
You can also confirm tha everythnig work fine by using :
curl http://localhost:8080
it will say : « My first page »
Step 3 : PHP-FPM

docker pull jprjr/phpfpm

Let run the container :

docker run name webstack_php_01 p 9000:9000 d jprjr/phpfpm

 

Step 4 : Make them talk together

Docker option : –link

We will copy the nginx configfile to the host

docker cp webstack_nginx_1:/etc/nginx/nginx.conf $HOME/data/webstack/conf/nginx.conf

 

 

vi $HOME/data/webstack/conf/nginx.conf

 

Add the server part

 

daemon off;
user  nginx;
worker_processes  1;
error_log  /var/log/nginx/error.log warn;
pid        /var/run/nginx.pid;
events {
    worker_connections  1024;
}
http {
    include       /etc/nginx/mime.types;
    default_type  application/octetstream;
    log_format  main  ‘$remote_addr – $remote_user [$time_local] « $request » ‘
                      ‘$status $body_bytes_sent « $http_referer » ‘
                      ‘ »$http_user_agent » « $http_x_forwarded_for »‘;
    access_log  /var/log/nginx/access.log  main;
    sendfile        on;
    #tcp_nopush     on;
    keepalive_timeout  65;
    #gzip  on;
    server {
        listen       80;
        server_name  localhost;
        location / {
            root   /usr/share/nginx/html;
            index  index.html index.htm;
        }
        #error_page  404              /404.html;
        # redirect server error pages to the static page /50x.html
        #
        #error_page   500 502 503 504  /50x.html;
        #location = /50x.html {
        #    root   /usr/share/nginx/html;
        #}
        # Pass PHP scripts to PHP-FPM
        location ~* \.php$ {
            fastcgi_index   index.php;
            fastcgi_pass    webstack_php:9000;
            #fastcgi_pass   unix:/var/run/php-fpm/php-fpm.sock;
            include         fastcgi_params;
            fastcgi_param   SCRIPT_FILENAME    /srv/http$fastcgi_script_name;
            fastcgi_param   SCRIPT_NAME        $fastcgi_script_name;
        }    
        # deny access to .htaccess files, if Apache’s document root
        # concurs with nginx’s one
        location ~ /\.ht {
            deny  all;
        }
    }
}

 

 

In our usecase we need that the nginx container webstack_nginx_1 can communicate with the PHP container (webstack_php_01).

We delete the existing containers

docker stop webstack_php_01 && docker rm webstack_php_01

docker stop webstack_nginx_1 && docker rm webstack_nginx_1

 

And we recreate them by using a docker-compose command

Before create a docker-compose.yml file

 

php:
image: jprjr/php-fpm
ports:
– « 9000:9000 »
volumes:
– $HOME/data/webstack/www:/srv/http

web:
image: nginx
ports:
– « 8080:80 »
volumes:
– $HOME/data/webstack/www:/usr/share/nginx/html
– $HOME/data/webstack/conf/nginx.conf:/etc/nginx.conf
links:
– php

 

Then run the command

docker-compose up

 

and try it :

curl http://localhost:8080

 

 

 

 

 

Photo du profil de mobydock

mobydock

devops.pm father

More Posts - Website

Follow Me:
TwitterFacebook

waffle.io an automatic kanban report

WAFFLE.IO

Waffle creates a free project management solution from your existing GitHub Issues.

Track Your Work Automatically
Your Waffle board shows your GitHub Issues and Pull Requests in real time. Never wonder if an Issue is still in progress or not. Waffle listens to the actions in your workflow to know when work is finished and updates your status automatically.

Photo du profil de mobydock

mobydock

devops.pm father

More Posts - Website

Follow Me:
TwitterFacebook