Donabe

http://etherpad.openstack.org/Donabe

Debo~ Dutta (dedutta), Rick Clark (rickclar) @cisco

Conjecture: Applications are all that really matter to the end user!

Anecdotal evidence: A CIO never sits around lamenting about infrastructure

"I wish I had more servers so we could manage our customer relationships better“

"SugarCRM's social media features would help our sales force be more responsive to the needs of our

customers. How can I have that tomorrow?"

Donabe is a multi-tier Application Container Service and a top level orchestrator that will

provision/deploy complex apps.

Use case: e.g. ruby/rails guy: cares for 1) a scalable ruby tier and 2) scalable mysql tier network segments.

ScalableRuby/Rails Container

scalableMySQL

container

ScalableRuby/Rails Container

scalableMySQL

container

LB

Apachepassenger

Mysql master

Stdby master

Mysql slaves

Whats new?

LB

Apachepassenger

Mysql master

Stdby master

Mysql slaves

LB

Apachepassenger

Mysql master

Stdby master

Mysql slaves

Rails container

Mysql container

LB

Apachepassenger

Mysql master

Stdby master

Mysql slaves

Rails container

Mysql container

What is Donabe (again!)?

• A collection of widgets?– interconnected …

• Bunch of configs?– Bundled in a profile …

• N-tier apps?• Flexible app profiles?• …….. And more?

What should we focus on first?

Applications have requirements

Compute Logical Network (including topology!) Security Availability Data Storage Spending boundries and triggers(Cloud specific) Service assurance

A simple thought

• Donabe –abstract container model – (mimics a network of widgets)– Abstraction of resources

• Infrastructure• Apps (bundles)

– Nested containers/widgets– Each container has ports (widget level ports?)

• for connecting to other containers• Ways to connect nested containers

• Wont delve into policies here!– Container definition will point to policy object

API

• Resources– Container

• Name• Type• (contains) List of containers• Relationships of lower level containers (aka sub-widget graph)

– Policy • Policy

– Opaque, known only to the SPs who implement containers• Separate template from instance

– Templates need a specification language – Our choice: Declarative Languages– Thus API will have a manifest property

Declarative Domain-Specific-Language

• We need a DSL to declare the relationships between the containers and declare requirements that are not specifically owned by a container.

In prelim talks with puppet folks to extend the puppet manifest language for this purpose

• The language needs to be declarative, because we want to be done, but not how to do it. – I should be able to say I need a 2Gb/s connection

between this point in container 1 and this point in container 2,

– without knowing anything about the networking devices or the commands and values that need to be supplied to accomplish my request.

Container Types

• Compute – VMs, clusters, processes

• Network – Virtual Network Segments– L2 container (like Quantum)

• Storage– Objects, files, blocks, blobs

• App – higher layer – Abstracts workloads

Compute Containers

• Generic VMs or lightweight VM containers. – Encompasses current VM semantics– Can be used for openVZ or LXC– Connected via virtual or real switches

• A server connected to an access– Blade server/chassis (cisco, hp, ibm etc)– Connects to the same access switch

• Simple example: – apache container has a nested compute container

• This container specifies a VM or a LXC container to run

Network containers

• Forms the pipes/segments used by other containers to talk to each other. – Refine attachment points/ports semantics

• VMs vNIC• Quantum/L2 network ports• Apps socket/ports • Widgets in/out ports

– Can support point-point or multipoint communication– Services containers can be injected using a filter

path/graph model e.g. a bump-in-the-wire chain • E.g. Quantum is a good L2 network container ….

Key work areas for Essex

• Model/APIs – Agreement of models needed for 1st phase.

• Declarative languages – Puppet network additions– Integration with OVF 2.0 profiles

• Widget library/container template design• Orchestration (stretch)– Scheduling

Who is doing something similar?

• In openstack - ? … • Heroku?• Cloudscaling?• Opscode?