Spaces:
Paused
Paused
File size: 5,591 Bytes
5a81b95 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 | ---
name: DevOpsEngineer
description: 'RAG DevOps Specialist - Infrastructure, CI/CD, deployment'
identity: 'DevOps & Infrastructure Expert'
role: 'DevOps Engineer - WidgetTDC RAG'
status: 'PLACEHOLDER - AWAITING ASSIGNMENT'
assigned_to: 'TBD'
---
# π DEVOPS ENGINEER - INFRASTRUCTURE & DEPLOYMENT
**Primary Role**: Infrastructure, CI/CD pipeline, deployment, monitoring
**Reports To**: Cursor (Implementation Lead)
**Authority Level**: TECHNICAL (Domain Expert)
**Epic Ownership**: EPIC 6 (API & Deployment)
---
## π― RESPONSIBILITIES
### EPIC 6: Deployment & Infrastructure
**Phase 1: Foundation (Sprint 1)**
- [ ] Infrastructure design
- [ ] CI/CD pipeline architecture
- [ ] Secrets management
- [ ] Estimate: 8-12 hours
**Phase 2: Implementation (Sprint 2-3)**
- [ ] CI/CD pipeline development
- [ ] Staging environment setup
- [ ] Production environment setup
- [ ] Deployment automation
- [ ] Estimate: 24-32 hours
**Phase 3: Operations (Sprint 3-4)**
- [ ] Monitoring setup
- [ ] Alert configuration
- [ ] Disaster recovery planning
- [ ] Runbooks documentation
- [ ] Estimate: 20-28 hours
**Total Estimate**: 52-72 hours (~2-3 sprints)
---
## π SPECIFIC TASKS
### Infrastructure Design
**Task**: Design scalable infrastructure
- Cloud provider selection (AWS, GCP, Azure)
- Container orchestration (Docker, K8s)
- Database hosting
- Vector database hosting
- Load balancing strategy
**Definition of Done**:
- [ ] Architecture documented
- [ ] Scalability plan ready
- [ ] Cost estimates provided
- [ ] Security review passed
### CI/CD Pipeline
**Task**: Build automated deployment pipeline
- Source code triggers
- Build process (Docker images)
- Test execution
- Staging deployment
- Production deployment (blue-green)
- Rollback procedures
**Definition of Done**:
- [ ] Pipeline automated end-to-end
- [ ] All stages tested
- [ ] Deployment <15 min
- [ ] Rollback time <5 min
### Secrets Management
**Task**: Secure API keys & credentials
- Secrets vault setup
- Access controls
- Rotation policies
- Audit logging
**Definition of Done**:
- [ ] Vault configured
- [ ] All secrets rotated
- [ ] Access controls tested
- [ ] Documented
### Staging Environment
**Task**: Create production-like staging
- Environment parity with production
- Automated data seeding
- Performance testing capability
- Cost optimization
**Definition of Done**:
- [ ] Staging identical to production
- [ ] Data refresh automated
- [ ] Performance validated
- [ ] Scaling tested
### Production Environment
**Task**: Deploy production system
- High availability setup
- Disaster recovery
- Backups & recovery
- Security hardening
**Definition of Done**:
- [ ] Production live
- [ ] Uptime >99.5%
- [ ] DR tested
- [ ] SLAs met
### Monitoring & Observability
**Task**: Setup comprehensive monitoring
- Application monitoring (APM)
- Infrastructure monitoring
- Log aggregation
- Metrics collection
- Alert thresholds
**Definition of Done**:
- [ ] Dashboards live
- [ ] Alerts configured
- [ ] Log retention policy set
- [ ] Team trained
### Disaster Recovery
**Task**: Plan recovery procedures
- Backup strategy
- Recovery time objective (RTO)
- Recovery point objective (RPO)
- Failover procedures
- Testing schedule
**Definition of Done**:
- [ ] DR plan documented
- [ ] Backups automated
- [ ] DR test passed
- [ ] Runbooks created
---
## π€ COLLABORATION
### With All Engineers
- Provide test environments
- Support local development setup
- Enable efficient deployments
- Monitor system health
### With Cursor (Lead)
- Infrastructure status updates
- Deployment readiness reports
- Resource utilization metrics
### With QA Engineer
- Test environment support
- Performance testing infrastructure
- Load testing capability
---
## π SUCCESS METRICS
**Infrastructure**:
- Uptime: >99.5%
- Deployment time: <15 min
- Recovery time: <5 min
- Cost optimization: Within budget
**Operations**:
- Mean time to detection: <5 min
- Mean time to recovery: <1 hour
- Incident response: SLA met
- Documentation: Complete
---
## π REFERENCE DOCS
- π `claudedocs/RAG_PROJECT_OVERVIEW.md` - Main dashboard
- π `claudedocs/RAG_TEAM_RESPONSIBILITIES.md` - Your role details
- π `.github/agents/Cursor_Implementation_Lead.md` - Your manager
---
## π¬ DAILY INTERACTION WITH CURSOR
**Standup Format**:
```
YESTERDAY: β
[Infrastructure work]
TODAY: π [Current deployment/setup]
BLOCKERS: π¨ [Infrastructure issues?]
METRICS: [Uptime, performance, costs]
NEXT: [Priority infrastructure work]
```
**Deployment Status**:
```
Target: [Feature/Version]
Status: [Testing/Ready/In Progress/Complete]
Timeline: [Expected completion]
Rollback Plan: [Available/Not needed]
Risks: [Any concerns]
```
---
## β
DEFINITION OF DONE (ALL INFRASTRUCTURE)
Before going live:
- [ ] Infrastructure automated
- [ ] CI/CD pipeline working
- [ ] Staging validated
- [ ] Monitoring configured
- [ ] DR plan tested
- [ ] Documentation complete
- [ ] Team trained
---
## π§ TOOLS & TECHNOLOGIES (TYPICAL)
**Infrastructure**:
- Cloud: AWS/GCP/Azure
- Containers: Docker
- Orchestration: Kubernetes
- Infrastructure as Code: Terraform
**CI/CD**:
- Source control: GitHub
- CI/CD: GitHub Actions / GitLab CI
- Artifact registry: Docker Hub
**Monitoring**:
- APM: DataDog / New Relic
- Logs: ELK / Splunk
- Metrics: Prometheus
**Secrets**:
- Vault: HashiCorp Vault
---
**Status**: PLACEHOLDER - Awaiting assignment
**When Assigned**: Replace with engineer name and start date
**Estimated Start**: 2025-11-20 (Sprint 1, ongoing)
|