2016 Federal User Group Conference - DevOps Product Strategy

1 Copyright © 2016 CollabNet, Inc. All Rights Reserved.

CollabNet DevOps Product StrategyPutting the Ops back into DevOps for Operational Intelligence

Eric RobertsonDevOps Product Line General Manager


My Background and Story• Responsible for the strategic direction of the DevOps product line at CollabNet.

• Led a solutions and services team at Unisys for migrating legacy environments to Web-scale-IT architectures

• Joined Cisco through a company acquisition (Tidal Software), where he served as Director for Product Management and as a subject-matter expert and solution management leader for Cisco’s cloud orchestration and automation products.

• Spearheaded the joint partnership between Cisco and SAP, whereby, SAP resold Cisco’s Intelligent Automation solution as a SAP Application Lifecycle Management (ALM) extension.

• Successfully held product engineering and management roles (Microsoft, Motorola, HP, BMC Software, Cap Gemini) and has provided consulting to Fortune 500 companies.

• Hold patents in the area of Hardware Abstraction Layers for Microkernel OS and a Bachelor Degree in Computer Science and Master’s Degree in Electrical and Software Engineering from University of Texas in Austin.

3 Copyright ©2015 CollabNet, Inc. All Rights Reserved.

Agile Focus Areas

CollabNet defines three Agile focus areas:• Agile PPM: Agile “planning” capabilities including project, portfolio & program level, backlog and

milestone management, capacity planning, etc.

• Agile Execution: features focused on Agile team execution of iterations and kanban-style workflow

• Downstream Agile: visibility and traceability of engineering activities downstream of planning and tasking (SCM, CI, CD, etc.).

AgilePPM

Upstream Agile

Version control

Continuous Delivery

Continuous Integration

Binary Repository

Downstream Agile

AgileExecution

Operations


Software Development Lifecycle Traceability and Visibility


Our DevOps Focus Areas

Continuous Lifecycle Integration (Plan-to-Ops)

Continuous Integration

Continuous Delivery Management

Focus areas (as per Forrester Research):

Key Benefits:

INTEGRATIONLeverage investment

in existing infrastructure and tools Interchange

tools to match evolving needs

AUTOMATIONDetect events and

take actions (across tools &

workflow systems)

TRACEABILITYFor impact analysis

and fast-fix

VERSION CONTROL

[everything] Across the

pipeline (Source, IaC, OaC)

REPORTINGSingle pane of glass reporting (metrics , KPIs)

across tool chain

CONTINUOUS FEEDBACK

Ops-to-Plan with Collaboration

(ChatOps)

Continuous Lifecycle Integration spanning the tool chain across Plan-to-Ops


Supporting Multi-Variant Software Development Life-cycle

Write(ALM)

Store(SCM)

Deploy - Continuous Delivery

(ARA)

DevOps: Operation

Intelligence(Ops)

Plan-to-Ops Life-cycle Integration

Biz Value through feature

Lifecycle Continuous Feedback, Traceability & Visibility

Teamforge

Teamforge SCM

Electric Cloud / Xebia/ClariveIBM UrbanCode

Mode 2 - Container Deployment EnginesMode 2 - Planning, Dev & Test Tools

MonitoringITIL tools


Trace view – exploring traceability


Associations list view


TeamForge – Leverage Association and Extend Downstream

“Assoc”

Project App


TeamForge – Downstream linkage

“Assoc”

Project App

Provide Lifecycle Automation and Orchestration

Provide Tool Chain Integration

MetaModel (Schemas) Tool Chain Integration


ALERT MONITORING

HEALTH EVENT

WORK ITEM

Continuous Lifecycle Integration Featuring End-to-End Traceability

SERVICE DESK

COMPLIANCE AUDIT

SECURITY CHECK

DEPLOYMENT

EPIC

STORY

TASK

COMMIT

CODE REVIEW

CI BUILD

BINARY

TEST

PLAN CODE BUILD TEST RELEASE DEPLOY OPERATE MONITORREVIEW

RELEASE PACKAGE


DevOps Integration and Workflow Extension

7

Networking

Security

CI/CD/CM Workflows

Security

• Sensors are inbound integration plugins that watch for events from external systems. When an event occurs, it fires a trigger (e.g., NewRelic app performance alert, Github commit, or JIRA issue update).

• Rules use the trigger to select which action or workflow to execute and pass the data needed to execute the action.

• Workflows stitch actions together into “uber-actions” with simple declarative DSL, defining the order, transitions, conditions, and data flow.

• Actions are outbound integrations and can be any scripts with meta-data. Actions are invoked by users via GUI, CLI, API, or ChatOps(*), or triggered by automations - rules and workflows.

• Audit trails record action executions, whether manual or automated, and stores them with full details of triggering context and execution results.


Out-of-the-box Rule Based Templates Across Tool Chains and Version Controlled!

Continuous Integration (CI) & Testing Flows

Continuous Release & Deployment Flows

Continuous Monitoring & Operations Flows

Workflows for Sensing and Executing Actions

Environment, Orchestration, Integration and Intelligence captured as Code


Dashboard and SDLC Traceability

Concept


Deployment Drilldown to Health Events


Deployment Drilldown to Security and Compliance Events


Build 51

Server 26Line 27Algorithm.java

Ticket 234

Project App

Visibility & Traceability

Intelligent Orchestration, Integration & Action Platform

Continuous Lifecycle Integration and Automation


Pipeline View – Status across Tool Chains


• Incidents & Problems often have a gap between 1. Knowing that there is a problem and it’s impact, and 2. Knowing where it came from and how to fix it

• Our DevOps traceability functions allows quick…– Identification of the problem’s source, related activities and team involvement – Problem repairs, contextually understanding ‘how it happened’ – Improvement capabilities for teams, activities, process or practices…globally

• Our DevOps fast-fix response capability allows the Enterprise to embrace agility with a continuous improvement strategy– Platform enables quality at speed!

Quick-Fix Visibility and Continuous Improvement

Fixedhere

But fix ithere too

- Ops team & user feedback recorded- Apps performance & use monitored- Process reviewed- List new requirements- Dev team reassigned

8

Cloud/Hybrid & Automation Deployment

Examples: - Amazon, Microsoft Azure, etc.

Developers get Defects/Requirements - via (IDE) Eclipse, Visual Studio, etc. - Global teams leverage productivity and collaboration… …code search for reuse, discussion forums and wikis

Product OwnerBA / QA Submit - New Requirements - or New Defects

Dev / Team Lead

Review, sets priorities, drives team effort

Developers Code and Collaborate - Meet requirements, fix bugs, run unit tests & commit code

Continuous Integration - Hudson/Jenkins (Build Automation – on-success) triggers Test/QA execution- Test/QA/Defect results and activities recorded. - Developers complete all supporting Release Files.

Deploy/Release to create: - Release config. (BOM)- Workflows, Profiles - Cookbook-Recipes Deployment Patterns

Project FRSApp

Enable OperationsProcess review, feedback loops & App monitoring/remediation

1

2

3

4

5

6

Server

Client

Providing Visibility and Traceability

DevOps

End-to-End Continuous Lifecycle for your Value Streams

MobileWeb AppLegacy Apps

Cloud

Dashboards

7

•Visibility across development, delivery pipeline and OPS

•Out of the box rule based templates across tool chains

•Make decisions based on real time information.

Putting the Ops back into DevOps

Operational Intelligence


Team

Forg

e U

I/In

fraW

orkfl

ow &

O

rche

stra

tion

Inte

grati

ons /

As

soci

ation

s

16.06 (Q2 2016) 16.09 (Q3 2016) (Q1 2016) POCDeploy & Release, Mgt, App View

Pipeline View (Planning -> Ops)

Feedback Loop Sample Reports

Demo Deploy Flows (Chef)

Community integrations: Chef, Jenkins, Nexus Powershell, git, Docker, AWS, vmware

NewRelic, uDeploy

Associations View

Deploy/ Release, App View

Pipeline View (Pl -> Ops)

DevOps Reports

Action/Triggering Server

Package Object

Operational Health flows (remediation, APM+ support)

Operational Health (Incidents) – NewRelic,Sensu

Integrated OaC* Console and Versioning

OAC* and IaC in release notes

OaC – Orchestration as Code

Pipeline Analytics

ChatOps (Approvals)

Deployment Strategies & PatternsDeploy Flows (IaC, ARA templates)

SLDC Analytics/Insight (Plan->Ops)

CI Flows & Patterns

EventQ Integration

CollabNet DevOps Roadmap - 2016 *OaC – Orchestration as Code

*ARA – Application Release Automation

*IAC – Infrastructure As Code

CD Integrations+: aws,azure,docker, puppet,ansible, openstack, kubernetes, salt , ARA*Operations+: Nagios, servicenow, sensu, hubot, securitymonkey

CD Integrations+: APM+ support, ARA+, Testing, Governance

Operations+: dripstat,elasticsearch, fireeye, alerlogic, pagerduty splunk, victorops

CI Integrations+: circleci, travisci

Roadmap Subject to Change

23 Copyright ©2015 CollabNet, Inc. All Rights Reserved.23 Copyright ©2015 CollabNet, Inc. All Rights Reserved.

Questions?