How DevOps Can Boost Productivity

Artem ChernikovSUSE Customer Center DevOps Engineer/Evangelist

achernikov@suse.com

https://github.com/kalabiyau

2

Reality can be harsh sometimes:

3

CHANGE CHANGE

But we can embrace the change:

CHANGE

CHANGE

4

What is DevOps?

5

Meaning of DevOps “by the book”

6

DevOps and Classic approach

• Communications quality

• Development/Operations/QA cycle speed

• Infrastructure confidence

• Responsibility in the team and beyond

• Goal and vision

7

Implementations

• For bigger companies Unified goal for distributed departments Shared management per project or per task A lot of direct communication

• For startups and small business One cross-functional team per project

8

Key components

• People and good habits

• Get things done (Agile and/or Lean)

• Automate all the things!

• Continuous delivery – 10 deployments per day should not be a problem

• Lean development (less resources delivered just in time)

9

People and habits

• Group of passionate people

• Set of good habits

• Habitual loops to introduce new ones

• Maintain and groom habits and surrounding tools

10

Get Things Done (development)

• Delivered working product is the ultimate goal

• The smaller the step, the easier is to revert one

• Solve a problem at hand or “right here, right now”

11

Automate (operations)

• Automate everything you can but not more

• Revisit automation periodically

• Treat your tools same way your treat your product

• Metrics

12

Deliver, review and repeat

• Smooth delivery process allows you to fix almost any problem in a timely manner

• More frequent deliveries gives you more confidence in your infrastructure

• More deploys = more features/bug fixes(theoretically)

13

Be closer to production

• Ideally team should be able to manage it's own infrastructure

• The closer your environment to production, the easier the twist

14

“Eat your own dog's food”

• First consumer of a product is the Team

• Fastest Feedback loop possible

• QA by usage

15

Lean resource usage

• Premature optimization is evil indeed

• Solve what is on the table right now

• Keep focus on what you are working on

DevOps team in actionOne person's show

17

Agenda

• Prepare new nodes

• Make a change

• Test the change

• Review the change

• Deploy the change

• QA the change

• Add new node to the cluster

Thank you.

18

DevOps could be your very good friend

19

Unpublished Work of SUSE LLC. All Rights Reserved.This work is an unpublished work and contains confidential, proprietary and trade secret information of SUSE LLC. Access to this work is restricted to SUSE employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of SUSE. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability.

General DisclaimerThis document is not to be construed as a promise by any participating company to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. SUSE makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for SUSE products remains at the sole discretion of SUSE. Further, SUSE reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All SUSE marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.