2. What It Really Takes to Deploy and
Manage Apps
Provision
Install
Configure
Deploy
Monitor
Scale
3. Large Parts Are Mostly Manual
Real
Time
Analyti
cs
Correlate with
Historical Events
Feedb
ack
Execute
Policy
Send
Metrics
Setup Monitoring and
Alerts
Deploy and
Configure
Applications
Setup Machine,
Network, Storage
Push updates
Collect and Analyze
Logs
Troubleshoot
Measure
performance against
expected SLA’s
Set and tune Alerts
thresholds
Match Policy to
Incident
4. The Impact of Human Errors
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
7. Challenges
•80%of outages impacting
mission-critical services will be caused by
people and process
•83%are facing
significant roadblock keeping them from
moving to the next phase (Politics, Budget,
Time, Stuff)
Solution: Automation & Orchestration
•Remove Manual
Intervention out of the
application deployment process
•Reduce
Complexity and
Dynamically align to the business needs
The Solution
8. Automating The Application Deployment
Deploy
Fail-
over
Scale
Cloud Infrastructure
Intelligent OrchestrationHistorical data
Real Time Analytics Real Time
Analytics
Correlate
with
Historical
Events
Feedback
Execute
Policy
Send
Metrics
10. What is TOSCA?
TOSCA defines the
interoperable
description of
applications; including
their components,
relationships,
dependencies,
requirements, and
capabilities….
11. TOSCA in a Nutshell
Mapping of application logic
through plans (workflows),
policies, relationships,
actions
12. TOSCA State of the Union
Top four cloud open standard (Forrester)
5000+ participants
65+ countries
The focus
of this session
13. What is TOSCA?
•Goal: cross cloud,
cross tools
orchestration of
applications on the
Cloud
•Status:
–Version 1 approved (XML )
–Version 2 (YAML!) in design
16. What’s in a TOSCA Topology?
•component in the topology
are called Nodes
•Each Node has a Type (e.g.
Host, BD, Web server).
–The Type is abstract and hence
portable
–The Type defines Properties
and Interfaces
•An Interface is a set of hooks
(named Operations)
•Nodes are connected to
one another using
Relationships
24. Policies TOSCA 1.0 didn’t
elaborate much on
policies
TOSCA 2.0 (draft)
discusses specific DSL
for specific policies
such as SLA of a Node
Out take:
Policies are imperative
25. Workflows TOSCA 1.0 – Workflows
(Plans) are in any WF
language.
Strong preference for BPMN 2.0
TOSCA 2.0 – No change
Cloudify 3.0 take –
Workflows are also tool
specific, currently we use
Radial (Ruby based DSL)
but seeking an alternative
for future versions
26. Putting It All TogetherTOSCA Template
(Blueprint in Cloudify)
contains:
Application Topology
Nodes
Interfaces
Properties
Artifacts (Plugins in Cloudify)
Relationships
Interfaces
Workflows
Policies
30. Proxy
REST
+ File
Server
GUI
Workflow
Engine
Task
Manager
Blueprint + Runtime
Data
Policy
Engine
Agent
Monitoring
Data
Agent
Monitoring
Agent
Application
Stack
Cloudify Manager
App VM
Invokes
Reports
Creates
Metrics VM
Logs +
Events
Remote Agents
Agent
Agent
Agent
Architecture
31. Apache Server DB Server
NodeJS
NodeCeller
MongoDB
TOSCA (Like) Example
• App Network
• App Subnet
• App Port
• Security Group
• Apache Floating IP
• Router Gateway
• Data Network
• Data Subnet
• Data Port
• Security Group
Router
Monitoring, Logging CI
