Infrastructure as code - Python Saati #36

Infrastructure as Code
Aybüke Özdemir
@aybuke_ozdemir
Halil Kaya
@halilkaya

Kısa bir örnekle kod tabanlı altyapının önemi

Biz Ruby on Rails’ı seçtik

> gem install rails
Fetching: i18n-0.7.0.gem (100%)
Fetching: json-1.8.3.gem (100%)
Building native extensions. This could take a while…
ERROR: Error installing rails:
ERROR: Failed to build gem native extension.
/usr/bin/ruby1.9.1 extconf.rb
creating Makefile
make
sh: 1: make: not found

Tabii ki önce make’i kurmamız gerek!

> sudo apt-get install make
...
Success!

> gem install rails
Fetching: nokogiri-1.6.7.2.gem (100%)
checking if the C compiler accepts ... yes
Building nokogiri using packaged libraries.
Using mini_portile version 2.0.0.rc2
checking for gzdopen() in -lz... no
zlib is missing; necessary for building libxml2
*** extconf.rb failed ***

Hmm. Stackoverflow’a baksak iyi olacak sanki...

> sudo apt-get install zlib1g-dev
...
Success!

> gem install rails
checking for gzdopen() in -lz... yes
checking for iconv... yes
Extracting libxml2-2.9.2.tar.gz into tmp/x86_64-pc-linux-
gnu/ports/libxml2/2.9.2... OK

Infrastructure as code - Python Saati #36

Stackoverflow’da 2 saat geçirdikten sonra...

> gem install rails
...
Success!

> rails new my-project
> cd my-project
> rails start

> rails new my-project
> cd my-project
> rails start
/source/my-project/bin/spring:11:in `<top (required)>`:
undefined method `path_separator` for Gem:Module
(NoMethodError)
from bin/rails:3:in `load`
from bin/rails:3:in `<main>`

… uzunca bir süre sonra
bir şekilde proje çalışır!

> bundle update rails
checking for gzdopen() in -lz... yes
checking for iconv... yes
Extracting libxml2-2.9.2.tar.gz into tmp/x86_64-pc-linux-
gnu/ports/libxml2/2.9.2... OK

Aslında problem Rails ya da Django değil.
Problem sunucuyu elle yapılandırmakta!

Configuration
Management
IAC
Provisioning

- tek tek elle?
- script?
- scp veya rsync?

- tek tek elle?
- script?
- scp veya rsync?
- tmux cluster ssh?

- hosts: production
remote_user: deployment
become: true
tasks:
- name: Install nginx
apt:
name: nginx
state: present
- name: Copy nginx conf file
template:
src: nginx.conf.j2
dest: /etc/nginx/nginx.conf
- name: Reload nginx
service:
name: nginx
state: reloaded

- hosts: production
become: true
tasks:
apt:
name: nginx
state: present
template:
src: nginx.conf.j2
service:
name: nginx
state: reloaded
“production” başlığı altındaki makinalar

- hosts: production
become: true
tasks:
apt:
name: nginx
state: present
template:
src: nginx.conf.j2
service:
name: nginx
state: reloaded
“deployment” kullanıcısı ile

- hosts: production
become: true
tasks:
apt:
name: nginx
state: present
template:
src: nginx.conf.j2
service:
name: nginx
state: reloaded
sudo yetkisi ile

- hosts: production
become: true
tasks:
apt:
name: nginx
state: present
template:
src: nginx.conf.j2
service:
name: nginx
state: reloaded
“nginx” paketini kur

- hosts: production
become: true
tasks:
apt:
name: nginx
state: present
template:
src: nginx.conf.j2
service:
name: nginx
state: reloaded
önceden hazırlanmış nginx
yapılandırma dosyasını ilgili
yere kopyala

- hosts: production
become: true
tasks:
apt:
name: nginx
state: present
template:
src: nginx.conf.j2
service:
name: nginx
state: reloaded
nginx servisini reload et

LoadBalancer
Instance Group
Network
Firewall
Disks & Images

resource “google_compute_instance” “prod-1” {
name = “prod-1”
machine_type = “n1-standard-1”
zone = “europe-west1-d”
boot_disk {
initialize_params {
image = “debian-cloud/debian-8”
}
}
}
resource “google_compute_instance_group” “prod” {
name = “prod”
instances = [
“${google_compute_instance.prod-1.self_link}”,
]
}

name = “prod-1”
boot_disk {
initialize_params {
}
}
}
name = “prod”
instances = [
]
}
- resource tipi
- resource ismi
- GCE’deki instance ismi

name = “prod-1”
machine_type = “n1-standard-1” GCE’deki makine tipi
boot_disk {
initialize_params {
}
}
}
name = “prod”
instances = [
]
}

name = “prod-1”
zone = “europe-west1-d” makinenin açılacağı datacenter bölgesi
boot_disk {
initialize_params {
}
}
}
name = “prod”
instances = [
]
}

name = “prod-1”
boot_disk {
initialize_params {
image = “debian-cloud/debian-8” debian 8 imajıyla boot diski oluştur
}
}
}
name = “prod”
instances = [
]
}

name = “prod-1”
boot_disk {
initialize_params {
}
}
}
name = “prod”
instances = [ oluşturduğun makineyi
“${google_compute_instance.prod-1.self_link}”, bu instance group’a
] koy
}

> terraform plan
> terraform apply

Faydalar
- tekrar kullanılabilirlik
- otomasyon
- version control
- gözden geçirme
- döküman
- başka bir cloud sistemine geçiş kolaylığı

Olası Sorunlar
- state dosyası!
- araç kullanırken elle yapılandırma!
- hala tam anlamıyla olgunlaşmış değil!
- uygulama yöntemindeki muhtemel sosyal sorunlar!
- var olan bir projeyi IAC’a taşıma(!)

Chef Puppet Ansible SaltStack CloudFormation Terraform
Code Open Source Open Source Open Source Open
Source
Closed Source Open Source
Cloud All All All All AWS Only All
Type Config Mngt Config Mngt Config Mngt Config Mngt Provisioning Provisioning
Infrastructure Mutable Mutable Mutable Mutable Immutable Immutable
Language Procedural Declarative Procedural Declarative Declarative Declarative
Architecture Client/Server Client/Server Client-Only Client/Server Client-Only Client-Only

Kaynaklar
- Infrastructure as code: running microservices on
AWS using Docker, Terraform and ECS
- Why we use Terraform and not Chef, Puppet,
Ansible, SaltStack, or CloudFormation
- https://www.ybrikman.com/writing/2016/03/31/i
nfrastructure-as-code-microservices-aws-docker-
terraform-ecs/

Infrastructure as code - Python Saati #36

More Related Content

What's hot (20)

Recently uploaded (20)

Infrastructure as code - Python Saati #36