Managing distributed-cloud-apps

Managing Distributed Cloud Native
Applications Made Easy

Spring Music 2.0
Spring Music inspired sample
✘ web – songs and albums
✘ news provider
✘ external news provider
spring-music
Lifecycle
Management
Unit
Version 1.0.0
news
provider
web
DB
service
instance
external news
provider

What are the Challenges?
✘ Develop…
✘ Deployment-specific configuration…
✘ Package and deliver…
✘ Deploy…
✘ Update…
✘ …with no downtime…
✘ Undeploy…
Application
DevOps
Team (~ 2
Pizzas)
Other Service
Business capability
Lifecycle
Management Unit
Version x.y.z
Java
(heavy data
processing)
“BACKEND”
Node.Js
(heavy data
processing)
”FRONTEND”
DB service
instance
“PERSISTE
NCE”
Geo-spatial
Service
“EXTERNAL
RESOURCE“

Multi-Target Application (MTA)
Business capability
Lifecycle
Management Unit
Version x.y.z
Java
(heavy data
processing)
“BACKEND”
Node.Js
(user request
processing)
”FRONTEND”
DB service
instance
“PERSISTEN
CE”
Geo-spatial
service
“EXTERNAL
RESOURCE“
MTA: my-app
Module
type
Resource
type
Module
type
Resource
type
Version x.y.z

MTA Descriptors
✘ YAML files
extends
MTA
deployment
descriptor
MTA
extension
descriptor
*1
extends

MTA Descriptors
✘ YAML files
✘ MTA Deployment Descriptor (mtad.yaml)
extends
MTA
deployment
descriptor
MTA
extension
descriptor
*1
extends

MTA Descriptors
✘ YAML files
✘ MTA Deployment Descriptor (mtad.yaml)
✘ MTA Extension Descriptor (*.mtaext)
extends
MTA
deployment
descriptor
MTA
extension
descriptor
*1
extends

MTA Deployment Descriptor
_schema-version: 3
ID: org.cf.samples.spring-music
version: 1.0.0
modules:
- name: spring-music-web
type: java.tomcat
path: build/libs/spring-music.jar
requires:
- name: news-provider
properties:
NEWS_URL: ~{url}
- name: spring-music-db
- name: spring-music-news-external
parameters:
buildpack: java_buildpack
properties:
POPULATE_ALBUM_REPOSITORY: true
- name: spring-music-news
type: javascript.nodejs
path: spring-music-news/
provides:
properties:
url: ${default-url}/news
resources:
type: managed-service
parameters:
service: postgresql
service-plan: v9.4-container
type: user-provided-service
parameters:
config:
url:
spring-music
Lifecycle
Management
Unit
Version 1.0.0
news
provider
web
DB
service
instance
external
news
provider

MTA header
✘ spec version
✘ app ID
✘ version
_schema-version: 3
version: 1.0.0
modules:
type: java.tomcat
requires:
properties:
NEWS_URL: ~{url}
parameters:
properties:
provides:
properties:
resources:
parameters:
service: postgresql
parameters:
config:
url:

Modules
✘ name
✘ type
✘ path
_schema-version: 3
version: 1.0.0
modules:
type: java.tomcat
requires:
properties:
NEWS_URL: ~{url}
parameters:
properties:
provides:
properties:
resources:
parameters:
service: postgresql
parameters:
config:
url:

Modules
✘ buildpack
✘ route
✘ other parameters
_schema-version: 3
version: 1.0.0
modules:
type: java.tomcat
requires:
properties:
NEWS_URL: ~{url}
parameters:
properties:
provides:
properties:
resources:
parameters:
service: postgresql
parameters:
config:
url:

Modules
✘ properties/env
_schema-version: 3
version: 1.0.0
modules:
type: java.tomcat
requires:
properties:
NEWS_URL: ~{url}
parameters:
properties:
provides:
properties:
resources:
parameters:
service: postgresql
parameters:
config:
url:

Modules
✘ expose config
_schema-version: 3
version: 1.0.0
modules:
type: java.tomcat
requires:
properties:
NEWS_URL: ~{url}
parameters:
properties:
provides:
properties:
resources:
parameters:
service: postgresql
parameters:
config:
url:

Modules
✘ placeholders like
${default-url}
resolved automatically
_schema-version: 3
version: 1.0.0
modules:
type: java.tomcat
requires:
properties:
NEWS_URL: ~{url}
parameters:
properties:
provides:
properties:
resources:
parameters:
service: postgresql
parameters:
config:
url:

Modules
✘ inject config via
reference notation
like ~{url}
_schema-version: 3
version: 1.0.0
modules:
type: java.tomcat
requires:
properties:
NEWS_URL: ~{url}
parameters:
properties:
provides:
properties:
resources:
parameters:
service: postgresql
parameters:
config:
url:

Resources
✘ name
✘ type
_schema-version: 3
version: 1.0.0
modules:
type: java.tomcat
requires:
properties:
NEWS_URL: ~{url}
parameters:
properties:
provides:
properties:
resources:
parameters:
service: postgresql
parameters:
config:
url:

Resources
✘ service label
✘ plan
✘ other parameters
_schema-version: 3
version: 1.0.0
modules:
type: java.tomcat
requires:
properties:
NEWS_URL: ~{url}
parameters:
properties:
provides:
properties:
resources:
parameters:
service: postgresql
parameters:
config:
url:

Resources
✘ some parameters
unknown on design
time
_schema-version: 3
version: 1.0.0
modules:
type: java.tomcat
requires:
properties:
NEWS_URL: ~{url}
parameters:
properties:
provides:
properties:
resources:
parameters:
service: postgresql
parameters:
config:
url:

Modules
✘ service bindings
_schema-version: 3
version: 1.0.0
modules:
type: java.tomcat
requires:
properties:
NEWS_URL: ~{url}
parameters:
properties:
provides:
properties:
resources:
parameters:
service: postgresql
parameters:
config:
url:

MTA Extension Descriptor
Deployment context dependent
Add property values and parameters
_schema-version: 3
ID: cf.samples.spring-music.prod-config
extends: cf.samples.spring.music
modules:
parameters:
memory: 1G
instances: 2
properties:
POPULATE_ALBUM_REPOSITORY: false
parameters:
memory: 128M
resources:
parameters:
config:
url: https://news-external.my.domain/news

What is an MTA Archive (MTAR)?
✘ Container, compliant with the
JAR specification
✘ Contains modules…
… a manifest and the MTA
deployment descriptor
✘ Used for distribution of the
packaged app
MTA
deployment
descriptor
Java
WAR
Node.Js
Code
…
...

CF Deploy Service
CF CLI plugin to deploy MTA with
a single operation
MTA
deployment
descriptor
MTA archive
module
MTA
extension
descriptor
CF CLI
operator
Cloud Foundry
Cloud
Controller
CF Deploy Service
PostgreSQL
database
target
state
workflows
cf deploy
current
state

CF Deploy Service
MTA
deployment
descriptor
MTA archive
module
MTA
extension
descriptor
CF CLI
operator
Cloud Foundry
Cloud
Controller
CF Deploy Service
PostgreSQL
database
target
state
workflows
cf deploy
current
state
”Server” app with the goal to
bring the app to desired state

Supported Operations
✘ Deploy (incl. from Git, in future from directory)
✘ Update (incremental)
✘ Blue-green deploy
✘ Cross-MTA configuration

Enterprise Qualities
✘ Deterministic deployment order and timing
✘ Recoverability of a multi-step operation
✘ Logging and auditability
✘ Version evolution policies
✘ Deletion of non-relevant artifacts

>1000Deploys per day
>100Real apps
>1500Distinct MTAs (incl. test ones)
@ SAP Cloud Platform

Open Source Availability
MTA model guide
MTA parsers, validators, persistence and utilities
CF MTA plugin
CF MTA deploy service
Spring Music MTA

Outlook
Evaluation from CF Controller API team – Pivotal tracker item [done]
Proposal for incubation in CF Extensions [pending]

Outlook
Evaluation from CF Controller API team – Pivotal tracker item [done]
Proposal for incubation in CF Extensions [pending]
Planed features:
✘ Parallel materialization of artifacts
✘ Rolling updates
✘ Version rollbacks
✘ Application configuration update
✘ Docker support
✘ Lifecycle hooks
✘ Secure configuration management

thanks!
Any questions?
You can find me at
nikolay.valchev@sap.com
nvvalchev@gmail.com

Credits
Special thanks to all the people who made and released
these awesome resources for free:
✘ Presentation template by SlidesCarnival
✘ Photographs by Unsplash

SlidesCarnival icons are editable shapes.
This means that you can:
● Resize them without losing quality.
● Change fill color and opacity.
Isn’t that nice? :)
Examples:

Managing distributed-cloud-apps

Recommended

Recommended

More Related Content

Similar to Managing distributed-cloud-apps

Similar to Managing distributed-cloud-apps (20)

Recently uploaded

Recently uploaded (20)

Managing distributed-cloud-apps

Editor's Notes