Support de présentation du M'IT us pour "IAC : Tu veux une VM ? Balance ton CURL !"

1. © ANEO – Tous droits réservés 1
Infra as Code : feedback from real world

2. © ANEO – Tous droits réservés 2
SUMMARY
WHAT IS IT ?
ENABLERS
IN REAL LIFE
ONE TO CONTROL THEM ALL
WHAT TO REMEMBER

3. • Abtraction of complexities
• Kind of infrastructure that can be managed and automated via block of code
• Infrastructure can be versionized: rooling upgrade, ZDD
• Code use a descriptive language: adaptive, versatile
• Use same logic as software developement: versionning, testing, iteration
• The developer is independent: he designs the architecture for his application, can POC, can test it easily
• No more manual tasks nor sysadmin contributions
• IAC needs new tools to make it works
• Developers need ops knowledges
• Errors can rapidly propagate through the whole infrastructure
• Overall project complexity increase
© ANEO – Tous droits réservés 3
INFRA AS CODE: WHAT IS IT ?

4. © ANEO – Tous droits réservés 4
INFRA AS CODE: ENABLERS
• TTM grealty reduce
• Technical dept mastered
• Less crabbled tasks
• More to time to code or enhance
• Can CI/CD
• Debug faster
• Can get any infra component with one line of code

5. © ANEO – Tous droits réservés 5
INFRA AS CODE: IN REAL LIFE
• Application called ITaaS – IT as a Service
• APIs broker that redirect calls to proper backend
• Standarized: meant for all departments and regions of the compagny
• Role is to: expose a set of APIs with authentication + authorization + metrology
• Two kind of tasks: synchronous and asynchronous
• API model choosen: REST with JSON
• Managed by a devops team
• Owner of the code, infra (dev/prod) and suppport (client, code)

6. © ANEO – Tous droits réservés 6
INFRA AS CODE: ONE TO CONTROL THEM ALL
Frontend /
Scheduler
Clients / Software Factories
Load Balancer
Frontend /
Scheduler
Authentication //
Authorization
Metrology Database NoSQL
PAAS
DNS
Databases
Cloud
Backend Services
Core application …

7. © ANEO – Tous droits réservés 7
INFRA AS CODE: WHAT TO REMEMBER ?
• Enabled full CI/CD in the compagny
• Autonomous developers
• Centralized all the backend features into one place
• Devs need to learn about infra concepts
• Must be asked by the business
• Too much work for one team, can’t absorb all the needs
• Had to move the work accross all the backend teams: teams must exp in devops pratice

8. Questions

9. © ANEO – Tous droits réservés 9
CONTACT
Cyrille COINTE : ccointe@aneo.fr