How to Take the CI/CD Plunge

Transcription

1 How to Take the CI/CD Plunge or How I Learned to Stop Worrying and Love OpenStack

2 Introductions Christopher Aedo Product Architect Christopher is an IT veteran for consulting, design and technology companies. He is also an outspoken public advocate for OpenStack, cloud computing, software defined networking and software defined storage. He often speaks at OpenStack and Open Source related conferences around the world. Nick Chase Technical Content Nick Chase is the Editor-in-Chief of OpenStack:Now and Senior Manager of Technical Content at Mirantis. With 20+ years' experience as a developer and author, Nick has written several books and hundreds of articles as an IBM developerworks Certified Master Author. He also founded NoTooMi.com and has done Web application development for companies such as Lucent Technologies, Sun Microsystems, Oracle, and the Tampa Bay Buccaneers.

3 A little housekeeping You ll see a window like this; it s a little different on a Mac. You can see a list of participants. Please can submit questions on the bottom window: If we can answer during the webcast, we ll do so Questions of broader interest will be saved and curated for the end We ll provide a link where you can download the slides at the end of the webcast. If you ask about slides during the webcast, you will get the same answer: A link will be provided at the end of the webcast.

4 Agenda What is CI/CD? How it differs from traditional software development Test driven development Cultural changes Repository requirements How CI/CD works

5 What is CI/CD? Continuous Integration / Continuous Deployment Designed for rapid release of software Integrates testing and deployment into the release cycle Slows down deployment (in a good way)

6 Software Development vs. Physical Product PHYSICAL SOFTWARE Fixed components Components must interface, but not fixed Finite interactions Interactions difficult to predict Limited entropy Entropy prone Tolerances / Scale understood and defined Should scale forever

7 In the beginning...

8 The advantages of agile

9 The problem is... Traditional is waterfall, but even with agile, at the end of the day it s about deployment.

10 Why deployment is complicated This is where everything hits the fan The development environment is not the same as production Now you deal with the differences

11 The blame game

12 How deployment happens now Blame game Operators manage to get it running by bouncing back and forth with developers Bend and hack and make it fit

13 Then there's DevOps... Describes the system as code (Puppet, Chef, etc.) Declarative Part of CI/CD, but not all of it

14 The trouble with DevOps... Still linearly dependant First waterfall development, now waterfall deployment

15 Why CI/CD is different BEFORE AFTER 4 Processes: 1 Process Authorship Testing Acceptance Deployment

16 A brief look at CI/CD I want to make a change I make a change and commit it Change gets picked up by review system/process Code gets deployed to test system Review system kicks off automated testing Code gets deployed to production Spinning up the same systems as in test test system Copyright 2015 Mirantis, Inc. to All rights reserved Instead of destruction, switches monitoring of code

17 Testing and reviews Testing should be done at the same time as code The review process can find missing tests such as negative unit tests, functional tests, performance tests, and so on

18 Hierarchy of testing types Performance Testing Integration Testing Functional Testing Unit Testing

19 Types of testing Unit testing Tests discrete functionality, may include negative tests Functional testing Verifies a user story, less discrete than unit testing Integration testing Ties together microservices and widgets (e.g., creating a VM would be integration) Performance testing Designed around expected usage patterns, should try and break things

20 Cultural change, not just technological Eliminating silos and making cross-functional teams Not just engineering needs to change -- also management, product people, individual engineers People don't like to write tests Standards need to be implemented Management needs to be involved -it's hard to do this without executive sponsorship CI/CD changes the way the schedule looks Not added time, just orderly time More realistic Image by Artem Popov is licensed under CC 2.0

21 The business reality If you can't iterate and release fast enough, you WILL be put out of business by the little guy who can. Image by Larry & Teddy Page is licensed under CC BY 2.0

22 Release cycles In software, release cycles are a yearly model, or even a monthly model. Not even necessarily a weekly cycle. It's an app release cycle.

23 Systems are the key Must be systems in place to enforce these changes Systems are deterministic, people are not

24 Choosing a repository In order to be appropriate for CI/CD, a repository must: Allow multiple concurrent branches and concurrent work Make merging into mainline code as painless as possible Bonus: reverting, rebasing, cherry picking, and so on

25 Repositories good for CI/CD SVN Git Mercurial

26 CI/CD and OpenStack: Money Transfer App (Part 1) 1. Code is submitted via git-review to Gerrit which notifies the appropriate people there is code to review 2. In parallel, the new code is made visible to a Jenkins build server. This is done via Zuul, an OpenStack CI project.

27 CI/CD and OpenStack: Money Transfer App (Part 1) 3. Zuul tells Jenkins to fire off several automated testing suites among them: Code quality analysis Functional and unit testing for micro-services Integration testing for top-level interactions Selenium job for web interface validation Security analysis test suite, checks for new undocumented files, permissions, log leaks, vulnerable SQL queries, etc Performance job which tries real hard to break things Build test repositories for artifacts and updated Puppet manifests, simulate deployment on fresh Linux container

28 CI/CD and OpenStack: Money Transfer App (Part 2) 4. Zuul reports success of all tests 5. Code-reviewers all approve the code change 6. Code is sent to merge into the repository

29 CI/CD and OpenStack: Money Transfer App (Part 2) 7. Zuul again intercepts the merge event and fires off several Jenkins jobs Make sure that the code really can merge (might need a rebase depending on order and repository) Run entire test suite from step 3 again Update Puppet and artifact repositories, verify no conflicts Notify group of intent to deploy Add deployment probes into real time metric and log collection analysis tool Start deployment Success! 8. Zuul reports status to Gerrit

30 Q&A Any Questions? Please submit in Question pane.

31 Thank you Thanks for attending our webcast! The slides and recording will be available at: