unifying application logic with datacenter automation

Unifying Application Logic with

Datacenter AutomationJacoby Thwaites

jacoby@sparkl.com

@sparklhq

Why are both enterprise and IoT stuck in the weeds?

• Apps & Infrastructure• Where we are today

• Black Box Swamp• How did we get here?

• Clear Box Solution• How can we escape?

• Examples

Agenda

Apps and Infrastructure (v1)In the beginning...

Physical Network

New App

Infinite bandwidth Zero latency 100% reliable

Physical Stack

Apps and Infrastructure (v2)Virtualized compute, storage and network

Physical Network

New App

Infinite bandwidth Zero latency 100% reliable

Virtualised Stack (SDC, SDS, SDM, SDN, NFV)

Apps and InfrastructureThe devops view...

Network

Stack

AppDev

Java, HTML, CSS, Javascript

Chef, Puppet, Juju

APIC-EM, VIRL, OpenSDN ControllerOps

Conway's Law

"Any organization that designs a system will produce a design whose structure is a copy of the organization's communication structure".

Apps and InfrastructureThe CEO View

Communications Network

App #1

App #2

App #3

New App

App #5

App #6

App #7

App #8

My Business

MicroservicesDivide and conquer...

Communications Network

Stack

Component

Stack

Component

Stack

Component

Stack

ComponentApp #1

App #2

Microservices

Communications Network

Service

App #1

App #2

Service Service Service

If I change this service,

what breaks?Is orchestration done in here?

Do these services have a choreography

between them?

The regulator fines me when your

stuff goes wrong!

A Global Bank

$20bn+

fines in

2 years

Conduct RiskRight data. Right path. Right place. Right reason

Black Boxes• Internal behaviour is opaque

• External behaviour cannot be predicted

Communications Network

Service Service Service Service

Level of communication

Black Box Choreography

Service B

Service A

Service C Service D

1

2

3

4

5

6

Can you answer three questions...?

The Black Box SwampKills agility. Kills flexibility. Maximizes conduct risk

Black Box Swamp

Internet of Things• Internal behaviour is opaque

• External behaviour cannot be predicted

• We're trapped in datacenters and slow negotiated partnerships

• We are entering a black box swamp on the scale of billions

Internet

Thing

Component ComponentThing Thing Thing

Level of communication

© 2015 Cisco and/or its affiliates. All rights reserved. Cisco PublicPresentation ID

Clear Boxes

Microservices

Communications Network

Service

App #1

App #2

Service Service Service

If I change this service,

what breaks?Is orchestration done in here?

Do these services have a choreography

between them?

We saw this slide earlier...

Clear BoxVisible configuration replaces opaque orchestration code.

SPARKL Sequencing Engine

Stack

Component

Stack

Component

Stack

Component

Stack

Component

App #2

App #1

SPARKL Config Tree

Unification of Flow with Automation• SPARKL "Clear Box" configuration expresses:

• Intents• External events with desired results

• Capabilities• Operations available on services

• Services• Provision and control with reason

• SPARKL Sequencing Engine• Determines optimal sequence• Drives the flow of events• Everything is visible• Everything is measured• Everything is logged – with reason

really important!

My Business

• Orchestrates these black boxes:• Motors (left, right, forward, back)• Sensors (light sensor, bumpers)• Compute (compare L/R brightness etc)

• Result• Compute service starts automatically• Car drives towards the light!

Clear Box config drives a Robot Car

Clear Box config does Complex TransactionsUnifying App Logic, Service Provisioning and SDN Topology

SPARKL clear box configuration that processes payments and receipts of money.

Works across 6 distributed black-box systems including sales.

Implements two-phase commit with rollback across 3 ledgers with journal.

Drives OpenSDN-capable topology constrained by jurisdiction, priority, cost.

Provisions services at runtime with reason.

• Black boxes are the root cause of today's problems• IT cost $100m+ on scale of 1000 things/systems = On scale of billions?!• Fractured audit logs, metrics, analytics = $$$ conduct risk• Infrastructure is divorced from app logic = $$$ complexity

• Clear boxes are needed now by enterprise and IoT• Understand event choreography = achieve agility• Infrastructure provisioning with reason = achieve flexibility• Log, measure and audit everything = reduce conduct risk

Clear Box Summary

22

Fix agility, flexibility and conduct risk

Thank you