DevOps

DevOps nima?

DevOps - bu Development (dasturlash) va Operations (operatsiyalar) jamoalarini birlashtiradigan madaniyat, amaliyotlar va vositalar to'plami. Bu shunchaki toollar emas, bu fikrlash tarzi.

DevOps ning asosiy maqsadlari:

• Tezroq delivery - kod yozilganidan production'ga tez yetkazish
• Yuqori sifat - avtomatlashtirilgan testlar va tekshiruvlar
• Barqarorlik - tizim ishonchli va oldindan bashorat qilinadigan
• Hamkorlik - Dev va Ops birgalikda mas'ul

Nega kerak?

Traditional yondashuvda Dev va Ops alohida jamoalar edi. Bu ko'p muammolarga olib kelardi:

Asosiy tushunchalar

Infrastructure as Code (IaC)

Serverlar, network, database - barchasi kod sifatida yoziladi va version control'da saqlanadi:

• Terraform - cloud-agnostic, deklarativ
• Pulumi - real dasturlash tillari (TypeScript, Python)
• CloudFormation - AWS native
• Ansible - configuration management

Monitoring va Observability

Tizimni ichidan ko'rish uchun uchta ustun:

• Metrics - raqamlar: CPU, memory, request count, error rate (Prometheus, Datadog)
• Logs - eventlar: nima bo'ldi, qachon, qayerda (ELK, Loki)
• Traces - so'rov yo'li: request qaysi service'lardan o'tdi (Jaeger, Zipkin)

Site Reliability Engineering (SRE)

Google tomonidan yaratilgan yondashuv - "software engineering lens to operations":

• SLI (Service Level Indicator) - o'lchov (latency, availability)
• SLO (Service Level Objective) - maqsad (99.9% uptime)
• SLA (Service Level Agreement) - shartnoma (buzilsa - kompensatsiya)
• Error Budget - qancha downtime "ruxsat etilgan"

Incident Management

Muammo bo'lganda nima qilish kerak:

• Detection - alert orqali erta aniqlash
• Response - on-call engineer tez javob beradi
• Mitigation - user ta'sirini kamaytirish (rollback, traffic shift)
• Resolution - asosiy sababni tuzatish
• Postmortem - blameless tahlil, o'rganish, oldini olish

Secrets Management

Maxfiy ma'lumotlarni xavfsiz saqlash va tarqatish:

• Kodda HECH QACHON plaintext secret bo'lmasin
• HashiCorp Vault, AWS Secrets Manager, Azure Key Vault
• Rotation - secret'larni muntazam yangilash
• Audit - kim, qachon, qaysi secret'ga kirdi

Amaliy jarayon (step-by-step)

Eng ko'p uchraydigan xatolar

Best practices

• Everything as Code - infra, config, policy, monitoring - hammasi Git'da
• Immutable infrastructure - serverlarni yangilash emas, almashtrish
• Cattle, not pets - serverlar bir xil, almashtiriladigan, special emas
• Shift left - security, testing, quality - boshidan o'ylang
• Blameless postmortems - xatolardan o'rganing, odamlarni ayblamang
• On-call rotation - bir kishi doim mas'ul, rotatsiya bilan
• Error budgets - SLO buzilsa, feature development to'xtaydi, reliability'ga fokus
• Toil automation - takrorlanadigan qo'l ishini avtomatlang
• Chaos engineering - production'da failure simulyatsiya qiling (Netflix Chaos Monkey)
• Documentation - runbooks, architecture diagrams, onboarding guides

Asboblar va texnologiyalar

Mini misol

Terraform bilan AWS EC2 va monitoring:

# Terraform - Infrastructure as Code

terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 5.0"
    }
  }
  
  backend "s3" {
    bucket = "my-terraform-state"
    key    = "prod/terraform.tfstate"
    region = "us-east-1"
  }
}

provider "aws" {
  region = var.aws_region
}

# VPC
module "vpc" {
  source  = "terraform-aws-modules/vpc/aws"
  version = "5.0.0"
  
  name = "${var.project}-vpc"
  cidr = "10.0.0.0/16"
  
  azs             = ["us-east-1a", "us-east-1b"]
  private_subnets = ["10.0.1.0/24", "10.0.2.0/24"]
  public_subnets  = ["10.0.101.0/24", "10.0.102.0/24"]
  
  enable_nat_gateway = true
  single_nat_gateway = true
  
  tags = var.common_tags
}

# ECS Cluster
resource "aws_ecs_cluster" "main" {
  name = "${var.project}-cluster"
  
  setting {
    name  = "containerInsights"
    value = "enabled"
  }
  
  tags = var.common_tags
}

# CloudWatch Alarms
resource "aws_cloudwatch_metric_alarm" "high_cpu" {
  alarm_name          = "${var.project}-high-cpu"
  comparison_operator = "GreaterThanThreshold"
  evaluation_periods  = "2"
  metric_name         = "CPUUtilization"
  namespace           = "AWS/ECS"
  period              = "300"
  statistic           = "Average"
  threshold           = "80"
  
  alarm_actions = [aws_sns_topic.alerts.arn]
  
  dimensions = {
    ClusterName = aws_ecs_cluster.main.name
  }
}

Prometheus alert rules:

groups:
  - name: application
    rules:
      # High error rate
      - alert: HighErrorRate
        expr: |
          sum(rate(http_requests_total{status=~"5.."}[5m])) 
          / sum(rate(http_requests_total[5m])) > 0.05
        for: 5m
        labels:
          severity: critical
        annotations:
          summary: "High error rate detected"
          description: "Error rate is {{ $value | humanizePercentage }}"
          runbook_url: "https://wiki.example.com/runbooks/high-error-rate"
      
      # High latency
      - alert: HighLatency
        expr: |
          histogram_quantile(0.99, 
            sum(rate(http_request_duration_seconds_bucket[5m])) by (le)
          ) > 1
        for: 10m
        labels:
          severity: warning
        annotations:
          summary: "High latency (p99 > 1s)"
          description: "P99 latency is {{ $value | humanizeDuration }}"
      
      # Pod not ready
      - alert: PodNotReady
        expr: |
          kube_pod_status_ready{condition="true"} == 0
        for: 5m
        labels:
          severity: warning
        annotations:
          summary: "Pod {{ $labels.pod }} not ready"

Ko'p so'raladigan savollar (FAQ)

Glossary (Atamalar lug'ati)