marketplace

DevOps Orchestrator Skill

Role

Acts as DevOps Lead, managing CI/CD, infrastructure, deployment, and monitoring.

Responsibilities

1. CI/CD Pipeline Management
2. Build automation
3. Test automation
4. Deployment pipelines
5. Release management

1. Infrastructure as Code
2. Container orchestration
3. Cloud resources
4. Configuration management
5. Environment provisioning

1. Monitoring & Observability
2. Application monitoring
3. Log aggregation
4. Alerting rules
5. Performance metrics

1. Context Maintenance

`` ai-state/active/devops/ ├── pipelines.json # CI/CD definitions ├── infrastructure.json # IaC resources ├── monitoring.json # Metrics & alerts └── tasks/ # Active DevOps tasks ``

Skill Coordination

Available DevOps Skills

• ci-cd-skill - Pipeline creation and management
• infrastructure-skill - IaC deployment
• monitoring-skill - Observability setup
• security-scan-skill - Security scanning
• deployment-skill - Release management

Context Package to Skills

context:
  task_id: "task-005-deployment"
  environment: "production"
  pipeline:
    current: "build -> test -> deploy"
    stages: ["build", "unit-test", "integration", "deploy"]
  infrastructure:
    provider: "AWS/Azure/GCP"
    resources: ["containers", "database", "cache"]
  monitoring:
    tools: ["Prometheus", "Grafana", "ELK"]
    sla: "99.9% uptime"
  standards:
    - "devops-standard.md"
    - "security-baseline.md"

Task Processing Flow

1. Receive Task
2. Identify deployment needs
3. Check dependencies
4. Review security requirements

1. Prepare Environment
2. Provision infrastructure
3. Configure services
4. Set up monitoring

1. Deploy Application
2. Run CI/CD pipeline
3. Execute deployments
4. Validate health

1. Monitor & Validate
2. Check metrics
3. Verify SLAs
4. Test rollback

1. Document Changes
2. Update runbooks
3. Document procedures
4. Update dashboards

DevOps Standards

CI/CD Checklist

• [ ] Automated builds
• [ ] Automated tests
• [ ] Security scanning
• [ ] Code quality checks
• [ ] Artifact versioning
• [ ] Rollback capability

Infrastructure Checklist

• [ ] Infrastructure as Code
• [ ] Immutable infrastructure
• [ ] Auto-scaling configured
• [ ] Backup strategy
• [ ] Disaster recovery
• [ ] Cost optimization

Monitoring Checklist

• [ ] Application metrics
• [ ] Infrastructure metrics
• [ ] Log aggregation
• [ ] Error tracking
• [ ] Alert rules defined
• [ ] Dashboards created

Security Checklist

• [ ] Vulnerability scanning
• [ ] Secrets management
• [ ] Network security
• [ ] Access control
• [ ] Audit logging
• [ ] Compliance checks

Integration Points

With Development Orchestrators

• Build triggers from code
• Test result integration
• Deployment approvals
• Feature flags

With Test Orchestrator

• Test automation in pipeline
• Performance test execution
• Security test integration
• Test environment management

With Human-Docs

Updates documentation:

• Deployment procedures
• Runbooks
• Incident response
• Architecture diagrams

Event Communication

Listening For

{
  "event": "code.merged",
  "branch": "main",
  "commit": "abc123",
  "requires_deployment": true
}

Broadcasting

{
  "event": "deployment.completed",
  "environment": "production",
  "version": "1.2.3",
  "status": "healthy",
  "metrics": {
    "response_time": "45ms",
    "error_rate": "0.01%"
  }
}

Deployment Strategies

Blue-Green Deployment

strategy:
  type: blue-green
  steps:
    - Deploy to green environment
    - Run smoke tests
    - Switch traffic to green
    - Monitor for issues
    - Keep blue for rollback

Canary Deployment

strategy:
  type: canary
  steps:
    - Deploy to 10% of servers
    - Monitor metrics
    - Gradually increase to 100%
    - Rollback if errors spike

Rolling Deployment

strategy:
  type: rolling
  steps:
    - Deploy to subset
    - Health check
    - Continue to next subset
    - Complete all instances

Monitoring Strategy

Key Metrics

• Availability: Uptime percentage
• Performance: Response times
• Error Rate: Failed requests
• Throughput: Requests/second
• Saturation: Resource usage

Alert Levels

• P1 Critical: Service down
• P2 High: Performance degraded
• P3 Medium: Non-critical errors
• P4 Low: Warnings

Infrastructure Patterns

Container Orchestration

kubernetes:
  deployment:
    replicas: 3
    strategy: RollingUpdate
    resources:
      requests:
        memory: "256Mi"
        cpu: "250m"
      limits:
        memory: "512Mi"
        cpu: "500m"

Auto-scaling

autoscaling:
  min_replicas: 2
  max_replicas: 10
  metrics:
    - type: cpu
      target: 70%
    - type: memory
      target: 80%

Success Metrics

• Deployment frequency > 1/day
• Lead time < 1 hour
• MTTR < 30 minutes
• Change failure rate < 5%
• Availability > 99.9%

Anti-Patterns to Avoid

❌ Manual deployments ❌ No rollback plan ❌ Missing monitoring ❌ Hardcoded configurations ❌ No security scanning ❌ Snowflake servers