IT Home 2015 DevOps 研討會

(1)

GOCC Internal Use Only

IT Home 2015 DevOps 研討會

百人工研院團隊如何落實 CI

雙子星雲端運算公司

符儒嘉執行長

http://www.geminiopencloud.com

(2)

Agenda

• DevOps – What does it mean?

• From Agile to DevOps

• ITRI Cloud OS development process

• Tools

• Process

• People

(3)

(4)

Technology changes just as fast

• Digitization, Internet, and Big Data leads to the wide adoption of

Cloud Services and the era of globally-connected society

(5)

DevOps – What does it mean?

• Business evolution is driving the

rate of change of Web applications

• Waterfall model breaks down, Ken

Schwaber brings in iterative,

incremental development, aka

Agile methodology

• Rapid and Frequent delivery by

Development drives pressure into

Operations team

• The same agile methodology for

Development must now also apply

to Operations

• DevOps is the iterative

collaboration model between

Development & Operations

(6)

Agile Development – It all starts here

• Agile Practice

• Frequent delivery of releasable

software

• Empowerment of individuals and teams

• Continuous communication,

collaboration and improvement

• Responsiveness to change

• Velocity

• Prioritize to maximize value

• Attention to quality

• Agile Values (manifesto)

•

Individuals & Interactions over process & tools

•

Working software over comprehensive documenation

•

Customer collaboration over contract negotiation

(7)

From Agile to DevOps

Iterative Deliverables Regression CI Scrum SIT UAT WebApp Scaling + Cloud Infrastructure Need to know WHAT & HOW to test

Products Delivered

(8)

ITRI Cloud OS – a complex system

5. Server Load Balancing 6. Distributed Main Storage 8. System & Network Management 4. Virtual Machine Managemen t 2. Physical Resource Managemen t 10. Repository Manager 7. Distributed Secondary Storage 3. Virtual Cluster Provisioning 1. Cloud Application Managemen t

ITRI

Cloud OS

12. User Management 9. Security 11. Messaging Server 1.5 DCSS API Server

(9)

ITRI Cloud OS SDLC

Coding

Unit &

Function

Test

Commit to

Feature

Branch

Sprint

Reqmts

Code

Review

Feature

Integrate

Commit to

RIB

Chkout

from RIB

Build

CI

SIT

RC Build

Internal

Beta

Release

Continuous build

(10)

Scrum Development

done todo WIP

(11)

Review Board (by Google)

(12)

Branching Methodology

Feature Branch

Feature/Requirement Design Spec Spec Review Coding Code Review Coverity Analysis RIB Daily Build Daily Deploy Regression Test Commit Regression Test Demo

Release Integration Branch

Auto Build Auto Deploy Acceptance Test Acceptance Report (KGB) Regression Test Release Candidate Regression Report Coverity/Understand Analysis

Release Candidate

Branch

Internal Beta Duration/Stress Test Product Platform Release

(13)

Feature Implementation

Unit Test

Checkin to SVN (+ dependent components) Passed ? Daily at 5pm Jenkins driven Feature Integration test Passed ?

Tag

Request

Daily @ Midnight Releng build NNN 9am next morning SIT Brief test Passed ? SIT test vs. BOM list in build NNN Passed ?

SIT Full

Test &

Release

“

NO GOOD” build

Yes

No

Yes

No

Continuous Integration

Known Good Build (KGB)

(14)

Auto-deploy

developers control scripts scripts source code

SVN

Jenkins

build test case statistic bug reports

Spira

JIRA

verify result

STAF

deploy test cell

build archive library

Robot

test cases tag test cases build machine build close

Auto-test

Auto-report

test result test request deploy request tester

(15)

(16)

Release Branch

Jira Issue workflow

Release

Integration

Branch

Jira

7.Hot Fix

7.Fix

_{2.Bug Mgr}

_{3.Team Lead}

4.RD

5.SIT

6.Demo

8.Verify/Close

1.Open

Assign

Investigate

Resolve or Return

(17)

Internal Beta - EYODF

• 2 full racks in the container

• 90+ servers

• 3 storage servers

• >200TB

• Workload

• Developer build/compile/test

• Win 7 Office images

• Test sandboxes

(18)

(19)

(20)

軟體持續整合交付技術 (DevOps)

開發

整合測試

版本發行

產品上線

敏捷開發

持續整合測試

持續整合交付

Toolchain

(21)

Infrastructure as Code (1)

• Leverage Cloud to test Cloud

• Testing sandbox – Virtual containers (Google

Kerbernets)

(22)

(23)

Software Engineering Process Tools

2015/9/3 - Robot - Spira - Selenium - Calabash

(24)

Process

• Tools are abundant to enforce the following

processes:

• Scrum Development

• Code Reviews

• Branching methodology

• Continuous Integration testing

• Test automation and test case management

• Bugs/Problems management

• SIT

• Release methodology

• UAT

(25)

(26)

Summary

• DevOps is an evolution from Agile; It comes

from pressure on operations

• There are tons of tools in place

• Repeatable process improves accountability

• Faster feedback prevents further failures

• But it all depends on people taking ownership

and work collaboratively to suceed

(27)

IT Home 2015 DevOps 研 討 會