Deploy to the cloud: an unexpected journey

CloudConf 2015 Turin, Italy
Co-speaker with Alessandro Nuzzo

Transcript

1. DEPLOY TO THE CLOUD AN UNEXPECTED JOURNEY Alessandro / Antonio / @aleinside @runc0m
2. FIRST THINGS FIRST: WHO WE ARE AND WHAT WE DO
3. TEAM in the beginning: 2 programmers now: 4 programmers NO SYSADMIN
4. DEVELOPMENT MODEL: AGILE 200 gr of SCRUM 400 gr of KANBAN a pinch of XP
5. CONTINUOUS DEPLOYMENT deploy new features development speed automation
6. AWS cut down server management time scalability mandatory choice
7. DEVOPS sysadmin from the point of view of a developer new environments, automatic script manage deploy, fix errors
8. THE PROJECT
9. FIRST INFRASTRUCTURE 2 XL RDS
11. BARE METAL !== CLOUD No simple horizontal scaling
12. FIRST INFRASTRUCTURE - DEPLOY Meet Capifony + Easy + Cloud plugins - Barely maintained - Complex to extend
13. AVOID "WORKS ON MY MACHINE" Problem: how we efficiently manage updates, packages and configuration of new technologies? No bash VAGRANT & ANSIBLE YAML Roles SSH connections handling, no thanks
14. ANSIBLE AS CAPIFONY . . . ­ n a m e : C h e c k o u t t h e p r o j e c t f r o m r e m o t e g i t r e p o s i t o r y g i t : > r e p o = g i t @ g i t h u b . c o m : p r i m a i t / p r i m a . g i t d e s t = { { r e l e a s e _ f o l d e r } } v e r s i o n = { { b r a n c h } } a c c e p t _ h o s t k e y = t r u e d e p t h = 1 ­ n a m e : S a v e r e v i s i o n s h e l l : > g i t r e v ­ p a r s e ­ ­ v e r i f y H E A D > R E V I S I O N c h d i r = { { r e l e a s e _ f o l d e r } } c r e a t e s = { { r e l e a s e _ f o l d e r } } / R E V I S I O N . . . ­ n a m e : R u n c o m p o s e r c o m m a n d : > " e n v C O M P O S E R _ H O M E = / h o m e / u b u n t u / . c o m p o s e r { { r e l e a s e _ f o l d e r } } / c o m p o s e r . p h a r i n s t a l l ­ n ­ ­ n o ­ d e v ­ ­ p r e f e r ­ d i s t ­ ­ o p t i m i z e ­ a u t o l o a d e r c h d i r = { { r e l e a s e _ f o l d e r } } " . . .
15. INSTANCE TAGS
16. OUR SIMPLE COMMAND
18. ANSIBLE DYNAMIC INVENTORY # c o n f i g f i l e f o r a n s i b l e ­ ­ h t t p : / / a n s i b l e . c o m / # = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = [ d e f a u l t s ] h o s t f i l e = b i n / h o s t s # o u r p h p c o m m a n d ! . . . { " w e b s e r v e r s " : { " h o s t s " : [ " 1 0 . 0 . 3 3 . 2 " , " 1 0 . 0 . 3 3 . 3 " ] } } ­ ­ ­ ­ h o s t s : w e b s e r v e r s r o l e s : ­ b u i l d
19. http://docs.ansible.com/developing_inventory.html
20. TIME GOES ON more features change requests adoption of new technologies: RabbitMQ, sockets, elasticsearch
21. CONTINUOUS TESTING
22. DIFFERENT ENVIRONMENTS FOR DIFFERENT APPS Micro services
23. Pluggable infrastructure BIG PROBLEM: AUTO SCALING EC2 auto-scaling with ansible was not an option
24. MOVING ON: ELASTIC BEANSTALK
25. ELASTIC BEANSTALK
26. ELB: HASSLES? provided amis and packages management ebextensions docker zip? deploy hooks failed deploy hooks
27. CONTINUOUS DEPLOY: ARTIFACT . . . z i p ­ y ­ r ­ q $ F I L E N A M E . m v $ F I L E N A M E . z i p $ C I R C L E _ A R T I F A C T S / w e b _ $ F I L E N A M E . z i p c p w e b _ $ F I L E N A M E . z i p $ C I R C L E _ A R T I F A C T S / c o n s u m e r _ $ F I L E N A M E . z i p z i p ­ d c o n s u m e r _ $ F I L E N A M E . z i p " . e b e x t e n s i o n s / 0 6 _ p r i m a _ w e b . c o n f i g " z i p ­ d w e b _ $ F I L E N A M E . z i p " . e b e x t e n s i o n s / 0 6 _ p r i m a _ c o n s u m e r . c o n f i g " z i p ­ d c o n s u m e r _ $ F I L E N A M E . z i p " . e b e x t e n s i o n s / 0 6 _ p r i m a _ c r o n . c o n f i g " z i p ­ d w e b _ $ F I L E N A M E . z i p " . e b e x t e n s i o n s / 0 6 _ p r i m a _ c r o n . c o n f i g " . . .
28. AUTOMATION / NOTIFICATION Laziness The quality that makes you go to great effort to reduce overall energy expenditure. It makes you write labor-saving programs that other people will find useful and document what you wrote so you don't have to answer so many questions about it. Larry Wall, three great virtues of a programmer
29. AUTOMATION / NOTIFICATION
30. CONTINUOUS DEPLOY: FLOW
31. LESSON LEARNT micro services know your tools stay up to date (!) [fridevs] embrace the cloud: get rid of your bare metal
32. LAST BUT NOT LEAST: STAGING & TESTING
33. NOTABLY ABSENT: MIGRATIONS doctrine migrations script to update data maintaince mode with swap url
34. THAT'S ALL, FOLKS - THANK YOU Alessandro / Antonio / @aleinside @runc0m cloudconf2015@prima.it