Continuous Deployment - Celfinet

Continuous Deployment - Celfinet

• 1.
  25th November |UPTEC Opening Event Devops and Engineering Best Practices
• 2.
  Opening Event Devops andEngineering Best Practices Continuous Deployment Cláudio Ferreira Celfinet
• 3.
  AGENDA • Celfinet Solutions •Importance of DEVOPS at Celfinet • DEVOPS Challenges • Critical Success Factors • Continuous Deployment at Celfinet • Lessons Learnt • Future Challenges
• 4.
  CELFINET SOLUTIONS Celfinet R&Dsolutions for Mobile Network Management: • Vismon Manager – Configuration Management • Vismon Observer – Drive Test Management • Vismon Intelligence – Performance Management • Celreport – Customer Support Tool for Mobile Phones
• 5.
  IMPORTANCE OF DEVOPSFOR OUR COMPANY • Minimize Cycle Time between customer deliveries • Assure consistent deployments
• 6.
  IMPORTANCE OF DEVOPSFOR OUR COMPANY • Involve all teams in successful deployments to customers • Increase teams motivation • Reduce reliance on heroes
• 7.
  DEVOPS CHALLENGES • Defineautomated deployment processes • Select adequate Tool Set • Teams need to learn new automation skills • Align product deliveries with all involved teams
• 8.
  CRITICAL SUCCESS FACTORS •Communication culture (Breaking team silos) • Commitment to frequent and stable customer deliveries – Continuous Deployment • Highly automated processes for: – Tests – Deployments – Infrastructure Provisioning, Orchestration and Monitoring
• 9.
  • Continuous DeploymentPipeline CONTINUOUS DEPLOYMENT AT CELFINET Continuous Integration Server Commit/Pus h Source Code Compile Unit Tests Integration Tests Create Deployment Packages Developer Release Candidate End-2-End Tests Deploy to QC Deploy to LAB Acceptance Tests Deploy to LIVE
• 10.
  • Benefits – FastFeedback / Fail-Fast – Any code change results in a possible Release – Confidence in a Release Candidate increases in each step of the pipeline – Frequent deliveries CONTINUOUS DEPLOYMENT AT CELFINET
• 11.
  LESSONS LEARNT • Full-StackDevelopment Teams (DB, MW, UI) • Frequent releases require extensive automation • Each team is responsible for it’s deployments • Stop informal “Cowboy Deployments” • Infrastructure monitoring
• 12.
  FUTURE CHALLENGES • Infrastructureas Code • Containerization • Automated Quality Gates
• 13.
  25th November |UPTEC