Continuous delivery best practices with a Case Study of a technology-driven media company. Petri Kallberg Cloud Architect, Nordcloud

Transcription

1 Continuous delivery best practices Petri Kallberg Cloud Architect, Nordcloud

2 Nordcloud: European Footprint. Market leader in the Nordics. Established operations Expansion ongoing 2

3 CONTACT US we'll get back to you as soon as possible Leopoldstr OG München, Deutschland

4 Nordcloud introduction Nordcloud Nordcloud is the cloud services specialist based in Helsinki, Stockholm, London, Munich, Oslo & Copenhagen. We are AWS Premier Consulting partner proving cloud strategy consultancy, migration services, 24x7 support, systems automation and official AWS training. 4

5 Continuous Delivery (CD) is a software engineering approach in which teams keep producing valuable software in short cycles and ensure that the software can be reliably released at any time. - Wikipedia 5

6 Sanoma is a leading media group in the Nordic countries with operations in over 10 European countries and yearly revenue of 2000M. 6

7 Starting point Multiple independent products & teams Varying level of build automation No configuration management tools Traditional in-house hosting, DIY-mentality Then IT was out-sourced 7

8 Build Automation is a must! 8

9 Use SaaS vs. re-invent your own if vendor lock becomes a problem solve it later 9

10 10

11 Infrastructure as a Code 11

12 What goes into Cloudformation stack? (and what is left outside of it) Stateless, Fast to deploy, Utilized inside single stack Statefull, Slow to deploy, Shared resources 12

13 Who/What does configure your instances? (and how it knows about the infrastructure) Auto scaling & launch configuration AMI vs. Install Parameters from cloudformation stack to Chef via instance metadata. Cookbooks for common build formats. Cfn-hup will trigger re-config for changes. 13

14 Don t Update Rebuild It! Current production V

15 Don t Update Rebuild It! Testing new production V10 V

16 Don t Update Rebuild It! Deploy new production V10 V

17 Don t Update Rebuild It! Discard old production V10 V

18 Thanks to new deployment process we can deploy builds into production in the middle of the day and have to sweat if it is going to work - Lead developer of the busiest website in Finland 18

19 But rebuilds are taking too long! We need to build every commit and deploy every build! - Anonymous developer 19

20 Cloudformation Production vs. Development & Testing Use same template for all environments! Customize with Parameters Mappings Conditions Allow code deployment to development using stack updates to avoid re-builds. Enable/disable features by stack update. 20

21 TODO improvements and new features Individual teams should be self sufficient while maintaining centralized sanity checks. Create AWS account for each search/product. Connect via central account using VPC peering. Manage Cloudformation stacks with Service Catalog. Replace custom code with AWS services; CodeDeploy, CodeCommit & CodePipeline 21

22 Thank You + Q&A petri.kallberg@nordcloud.fi

23 CONTACT US we'll get back to you as soon as possible Leopoldstr OG München, Deutschland