Infra as Code – GITOPS – part 1 : TERRAFORM on scaleway provider



curl -fsSL | sudo apt-key add -

sudo apt-add-repository "deb [arch=amd64] $(lsb_release -cs) main"

sudo apt-get update && sudo apt-get install terraform

verify it s insalled by using :

$ terraform version

STEP 2 on your scaleway account Create API credential on scaleway admin interface

STEP 3 create a project folder then create a terraform declarative configuration file

Add the following content to it to deploy a General Purpose C1 instance running the Ubuntu Bionic base image in the fr-par-1 zone:

terraform {
required_providers {
scaleway = {
source = "scaleway/scaleway"
required_version = ">= 0.13"

provider "scaleway" {
access_key = "YOUR ACCESS KEY"
secret_key = "YOUR SECRET KEY"
organization_id = "YOUR ORGANIZATION ID"
zone = "fr-par-1"
region = "fr-par"

resource "scaleway_instance_ip" "public_ip" {}

resource "scaleway_instance_volume" "data" {
size_in_gb = 50
type = "l_ssd"

resource "scaleway_instance_server" "my-ubuntu-instance" {
type = "C1"
image = "ubuntu_bionic"

tags = [ "devops_terraformC1", "MyUbuntuInstance" ]

ip_id =

additional_volume_ids = [ ]


STEP 4 Run terraform init to load the newly created configuration file into Terraform

STEP 5 Plan the execution of the tasks to be done by terraform using the command terraform plan

STEP 6 terraform apply.

Confirm the execution of the plan by typing yes when prompted

STEP 7 Go to the Instances section in your Scaleway Console. You can see that the instance has been created

! You can delete everything by using terraform destroy in your terminal

mobydock father

More Posts - Website

Follow Me:

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 father

More Posts - Website

Follow Me:

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

mobydock father

More Posts - Website

Follow Me:


tis is IT , Next week !!!!

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 father

More Posts - Website

Follow Me: