DevOps for dummies study sharing - part II

DevOps for Dummies – Part II

Blackie

2015/10/15

AGENDA

Chapter 4 : Looking at How Cloud Accelerates DevOpsChapter 5 : Using DevOps to Solve New ChallengesChapter 6 : Marking DevOps Work : IBM’s StoryChapter 7 : Ten DevOps Myths

LOOKING AT HOW CLOUD ACCELERATES DEVOPSChapter 4

Using Cloud as An Enabler for DevOps

The speed of environment provisioningThe ability to dynamically provision and de-provision these environmentsThe ability to leverage “pattern” technologies that allow organizations to define and version environmentsFrom an automation perspective, the availability of application deployment automation technologiesThe availability of service virtualization technology

Full-Stack Deployments

Deploying the applicationConfiguring the cloud environmentOpenStack Heat Orchestration Template(HOT)

Another example of Docker:

Choosing a Cloud Service Model for DevOps

IaaS - Infrastructure as a ServiceProvides access to computing resources in a virtualized environment. AWS, Azure

PaaS - Platform as a Service a form of cloud computing that provides a platform (runtime) and environment to allow developers to build applications. Heroku, AppFog

SaaS - Software as a Servicea business model where software is licensed and delivered. SaaS Is basically on-demand software for end users. Dropbox, Evernote, Office 365,

BaaS - Backend as a ServiceIs an approach to cloud computing that provides a backend for applications (mostly mobile)Provide an API and tools for deveolpmentParse. Firebase, VS online, Deployd

Understanding What a Hybrid Cloud Is

Public CloudA type of cloud where resources are shared between multiple users and are publicly available to any company/user.

Private CloudA type of cloud where hardware, storage and network are dedicated to a single client. Also to get compliance with PCI, HIPAA is much easier with a private cloud.

Hybrid CloudGood solution if there is institutional hesitancy about the security of the public cloud for sensitive data

USING DEVOPS TO SOLVE NEW CHALLENGESChapter 5

Mobile Applications

User feed back & log tracingFlurry and Google analytics mobile

Automation Test on MobileMonkeyRunner, Robotium, Selenium Mobile Web Driver

Continuous Integration & Continuous Deployment Problem

ALM Processes

Same GoalSimilar ConceptsDifferent way

Scaling Agile

Lean and agile development are the underpinnings of the DevOps approach.Scaled Agile Framework(SAFe)

It is a programming knowledge base that aims to enable you to apply lean-agile practices at enterprise scale.Disciplined Agile Delivery(DAD)

It is a people-first, learning-oriented hybrid agile approach to IT solution delivery.

Multiple-Tier Applications

Consistent deployment practices can help ensure that teams are using reliable, repeatable deployment across platform to provide true business value.Including basic setting, e.g. ASP.NET 5 replace XML to JSON as default

http://docs.asp.net/en/theming/fundamentals/configuration.html

DevOps in the Enterprise

Facing challengesRegulatory hurdles

Get ApprovalProcess complexity

Xuenn YT UserSkill gaps

OPS, APPSOrganization silos

Xuenn YT UserPlatforms and tools that result in long service cycles, unnecessary delays and wasted resources

DEV=>QAT=>UAT=>PROD

Supply Chains

The Relationships among suppliers are managed more by contracts and SLA than by collaboration and communication.Outsourcing management and communication

Report on all itemLet tools help you

GitSlack

Slack 完整教學與上手心得：找到正確的團隊溝通之道

The Internet of Things

The development and testing needs for CI and CD to testing remain the same, Simulators are used test software and hardware during developmentAnit-Pattern

Water-SCRUM-fallNoOps

MARKING DEVOPS WORK : IBM’S STORYChapter 6

Talking a Look at the Executives’s Role

Select the right leaderInvolve stakeholdersMeasure improvements and outcomesBuild momentum with early successesCommunicate and listen

Putting Together to the Team

IBM Software Group (SWG) One of the major divisions of IBM.Over 80 software development tools in the categories of software delivery planningOver 25 locations in 10 countries.Before adopting DevOps approach, the group worked on a yearly release schedule including an additional 3 to 6 months of lead time to actually determine what went into that yearly release.

Setting DevOps Goals

Streamline the process and introduce new methodologiesLeverage tools for consistency, for scalability to other teams, and for traceability and metricsEvolve the culture to continuously improving

Learning from the DevOps Transformation - 1

Expanding agile practicesAllocating and ensuring funding for program execution SuccessDriving, assisting, and supporting program executionEstablishing long-term vision and direction for the BusinessPrioritizing epics and user stories for annual releases that align with the long-term vision

Leveraging test automationAutomate repetitive and labor-intensive tests. Automate in areas where bugs are frequently found.Run automation on every build; run early and often.Create automation that’s resistant to user interface (UI) changes — use a framework that separates the UI from the tests.Make it easy to create, deliver, and maintain the automation establishing strong feature team ownership.Plan automation development work into your estimates and ensure developers have time to work on it.Develop metrics so you can evaluate whether your automation is useful (you can’t improve what you can’t measure).Constantly re-evaluate if your automation is finding bugs and refactor it if it’s not.

21

Learning from the DevOps Transformation – Part 2

Build a delivery pipeline - Needed to embrace Shift-left testing and automate as much as possibleUse the same deployment mechanisms everywhereStrive to maintain a constant state of ship-readinessTreat infrastructure as code

Build a delivery pipeline - Following Treat pattern definitions, script packages, and services as code.Version everything.Automate deployment of topology patterns to the cloud.Manage versions of patterns across multiple cloud environments.Automate the testing of patterns.Cleanup catalog resources to avoid sprawl.

22

Learning from the DevOps Transformation – Part 3

Experimenting rapidlyEstablish metrics and success/failure criteria.Figure out what works by running experiments — tiny tests for a small subset of users to help determine the usefulness of a feature.Run multiple experiments continuously.Make fact-based decisions quickly.Deliver faster and you can experiment faster.Establish a mechanism to enable system-wide experimenting(Google Analytics, IBM Digital Analytics, and so on).Consider different models of experimenting (classical A/B testing, multi-armed bandit, and so on).Follow two paths simultaneously for related projects: experiment on a cloud-based project and use the data from the experiments to not only drive the direction of that project but also related on-premise projects.

23

Learning from the DevOps Transformation – Part 4

Continuously improvingThe business metrics consist of measured improvements in

Faster time to deliveryImproved client satisfactionReduced maintenance spending while increasing innovation investmentIncreased client adoption

Operational metrics impact team’s efficiency over time and measure the following:Time to initiate a new projectBuild timeIteration test time

Looking at the DevOps Results

TEN DEVOPS MYTHSChapter 7

26

1. DevOps Is Only for “Born on the Web” Shops

Example of Mobile app

http://www.continuousagile.com/unblock/cd_mobile.html

27

2. DevOps Is Operation Learning How to Code

Have to betterCommunication, tools and work as a team are Major

28

3. DevOps Is Just for Development and Operations

Not for each side, DevOps is for whole team, including stakeholders in the delivery of software, lines of business, practitioners, executives, partners suppliers, and so on.http://www.baselinemag.com/it-management/slideshows/devops-strategies-beef-up-the-bottom-line.html

29

4. DevOps Isn’t for ITIL Shops

ITIL’s life-cycle model is compatible with DevOpsDevOps care the end-to-end deliveryThe key is to identify the areas where you will get the most bang for buck through improved collaboration and automation.1. List out your top/key ITIL processes2. Gather representatives from each relevant team to review them3. Identify the points in each process where things break down4. Ask how/if improved collaboration or automation could help?5. Prioritize based on effort and reward6. Start at #1ITIL Guide to DevOps eBook

30

5. DevOps Isn’t for Regulated Industries

Why Are Some Industries So Far Behind on DevOps?

31

6. DevOps Isn’t for Outsourced Development

IBM DevOps: Outsourcing Governance

Managing Your Outsourced IT Services Provider

32

7. No Cloud Means No DevOps

33

8. DevOps Isn’t for Large, Complex Systems

2014 State Of DevOps Findings! Velocity Conference

34

9. DevOps Is Only about Communication

https://xebialabs.com/periodic-table-of-devops-tools/

35

10. DevOps Means Continuous Change Deployment

Cotainer Shipping of Docker – Build, Ship, Run

CD with Docker

MORE ABOUT DEVOPSChapter ?

37

DevOps is a Karma

38

Simple CI in DevOps

39

DevOps on VS ALM

40

Final DevOps

41

Who we need?

Reference

Introducing the scaled agile frameworkIntroduction to DADPrivate vs. Public vs. Hybrid Cloud: Which One to Choose?DevOps for mobile developmentwiki – ITILWater-Scrum-Fall: Agile reality for Large Organisations DevOps vs OutsourcingTransform DevOps with Application Release Automation[Phonegap]FlurryPlugin 使用(on iOS)[Phonegap]FlurryPlugin 使用part2(on android) 與項目介紹