Software Defined Operator

Preview:

DESCRIPTION

During the past few years we’ve seen how our entire data-center becomes software defined. This include the Compute, Storage, Network and also Configuration. This new data centre is the cloud. The missing piece in the puzzle: While this is pretty much old news there is one big thing that is missing in this puzzle and that is the operator itself. The operator is responsible for running processes such: * Installation of new apps * Upgrades and update of new features or patches * Performance tuning * Handling failure * Managing the capacity to meet the scaling demand. Most of those tasks today involves lots of human intervention. Users who realised that gap try to mitigate that by putting their own custom automation - usually that comes in a form of scripts on-top of the configuration management. Those custom scripts tend to grow fairly quickly to the point where they become unmanageable. This presentation will introduce how we can use an orchestrator to automate those tasks and by that create a software defined Operator.

Citation preview

Software Define Operator

Nati ShalomCTO & Founder GigaSpaces@natishalom

DevOps Through the Car Industry

Analogy

The Biggest Revolution?

Gasoline Engine

Sports Car

Model T Assembly Line

“You can choose any color you want as long as its black...” - Henry Ford

Transformed the Entire Industry

• Automobile enters the mass market• 10x more cars a day• 4 months pay to

buy a car

How is this Relevant to DevOps?

DevOps is the Industrialization of IT

IT Pre DevOps IT Post DevOps

DevOps is all about...

• Releasing new features and products faster and at scale• 1000s of updates

per day is typical

What’s Changed?

It seems like everything BUT the kitchen sink is software defined these

days.You were saying?

Everything is Software Defined

We Can Automate Everything

Configuration

NetworkingComputeStorage

The Missing Piece in the Puzzle

The Missing Piece In the Puzzle?The Missing Piece in the Puzzle…

Software Defined

Operator

Human vs Software Operator

• Human Operator • Software Operator

Input: DSL

Execute: APIInput:

Email, DocsExecute: GUI, CLI

Control:Policy Engine

Control: Monitoring, SMS

The Impact of Human Error

14

80%of outages impacting mission-critical services will be caused by people and process issues

50%of those outages will be caused by change/configuration/release integration and hand-off issues

Orchestration = Software Operation

Typical Orchestration Model

TOSCA: A Standard Blueprint

Topology View

Real Life Example

(HP Print)

• 30 HP Helion Public Cloud accounts

• 500+ compute instances

• 1400 Peak deployments per day

• 100+ compute instances per management cluster

• 100x developers doing deployments in a consistent fashion

• <2H Move from HP Helion Public Cloud tenant to a fully provisioned and deployed service

Orchestrating Networks and Apps

Does this Mark the End of IT Operations?

Ops in a DevOps World

Apps & Ops speaks the same language

Ops can deliver real value – ensuring that SLAs are met

More control Over the Environment

The Demand For DevOps..

Orchestration Is the Next Big Thing

Learn More

getcloudify.org

DocumentationArchitectureCommunity ForumBlog

Thank You

Nati Shalom@natishalom

Recommended