CASE STUDY: A SERVICE DESK AS THE ENTRY POINT FOR NO-OPS
summary
Shows how an Atlassian tool chain (Jira Service Desk frontend with Bamboo, Bitbucket and Artifactory pipelines) is used as the user-facing entry to automate infrastructure provisioning toward a no-ops goal. The implementation provisions per-request container sets (application frontend plus database) on OpenStack, Docker and Kubernetes backends, stores images in a local registry, and can shift workloads across regions; a demo reports first-run image build and container boot in about 6–10 seconds with faster subsequent requests.
AI-written summary · about
chapters (13)
- 0:00No-Ops case study
- 5:35Atlassian in enterprise
- 8:11Breaking silos with DevOps
- 12:38Dev vs ops
- 15:55Overcoming change resistance
- 20:52Automation and governance
- 23:10Multi-region global services
- 26:49Security and compliance in distributed systems
- 32:45Service Desk as No-Ops entry
- 38:53Service architecture and containers
- 40:18Demo: Gira provisioning speed
- 51:50No-Ops results and benefits
- 54:23Q&A
related talks
50mDevOps To NoOps: The JIRA Development Team's Journey to NoOps Freedom
24mBringing Service Desk and DevOps Together: Yes, It Can Be Done!
44mPlatform Engineering in action
36mWild Microservices and Imaginary DevOps
23mOrchestration and CI/CD
30mBringing DevOps Success to Every App, Tool & Role in Your Org
41mThe Introduction of DevOps in Large-Scale Organizations
49mThe road to continuous deployment: a case study