The document discusses the benefits of using infrastructure as code (IAC) to provision and manage infrastructure. It provides examples of using tools like Ansible, Terraform, and CloudFormation to automate the configuration of servers and cloud resources rather than manually configuring them. Some benefits mentioned are reusability, automation, version control, reviewability, documentation, and ease of migrating to another cloud system. Potential issues discussed include state files, manual configuration when using tools, maturity of some tools, and social challenges when changing processes.

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

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

3. Yeni bir projeye başlıyoruz

4. Biz Ruby on Rails’ı seçtik

5. > gem install rails

6. > 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

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

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

9. > gem install rails

10. > gem install rails
Fetching: nokogiri-1.6.7.2.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
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 ***

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

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

13. > gem install rails

14. > gem install rails
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
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... 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
*** extconf.rb failed ***

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

17. > gem install rails

18. > gem install rails
...
Success!

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

20. > 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>`

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

23. Production

25. > bundle update rails

26. > bundle update rails
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
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... 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
*** extconf.rb failed ***

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

29. Configuration
Management
IAC
Provisioning

30. Configuration
Management

31. nginx
conf

32. - tek tek elle?

33. - tek tek elle?
- script?

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

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

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

37. - 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

38. - 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
“production” başlığı altındaki makinalar

39. - 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
“deployment” kullanıcısı ile

40. - 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
sudo yetkisi ile

41. - 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
“nginx” paketini kur

42. - 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
önceden hazırlanmış nginx
yapılandırma dosyasını ilgili
yere kopyala

43. - 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
nginx servisini reload et

44. Provisioning
cloud

45. LoadBalancer
Instance Group
Network
Firewall
Disks & Images

46. 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”
zone = “europe-west1-d”
instances = [
“${google_compute_instance.prod-1.self_link}”,
]
}

47. 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”
zone = “europe-west1-d”
instances = [
“${google_compute_instance.prod-1.self_link}”,
]
}
- resource tipi
- resource ismi
- GCE’deki instance ismi

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

49. resource “google_compute_instance” “prod-1” {
name = “prod-1”
machine_type = “n1-standard-1”
zone = “europe-west1-d” makinenin açılacağı datacenter bölgesi
boot_disk {
initialize_params {
image = “debian-cloud/debian-8”
}
}
}
resource “google_compute_instance_group” “prod” {
name = “prod”
zone = “europe-west1-d”
instances = [
“${google_compute_instance.prod-1.self_link}”,
]
}

50. 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” debian 8 imajıyla boot diski oluştur
}
}
}
resource “google_compute_instance_group” “prod” {
name = “prod”
zone = “europe-west1-d”
instances = [
“${google_compute_instance.prod-1.self_link}”,
]
}

51. 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”
zone = “europe-west1-d”
instances = [ oluşturduğun makineyi
“${google_compute_instance.prod-1.self_link}”, bu instance group’a
] koy
}

52. > terraform plan
> terraform apply

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

54. 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(!)

55. 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

57. 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/