3. About Me
Director of Product - Cloudify, GigaSpaces
I come from
● OpenStack Product Manager @Red Hat
● DevOps @LivePerson
● Linux Services, Field
and Support @Matrix
4. About Me
Director of Product - Cloudify,
GigaSpaces - 1 Month In
Where do I come from
● OpenStack Product Manager @Red Hat
● DevOps @LivePerson
● Linux Services, Field
and Support @Matrix
8. What It Really
Takes to
Deploy and
Manage Apps
Provision
Install
Configure
Deploy
Monitor
Scale
9. Large Parts Are Mostly Manual
Real Time
Analytics
Correlate
with
Historical
Events
Feedback
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
10. 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
12. What is
TOSCA?
• Goal: cross-cloud,
cross-tool
orchestration of
applications on the
Cloud
• Status:
– Version 1 approved (XML ☹)
– Version 2 (YAML!) in design
13. Why TOSCA?
• Open Standard
• Can Describe
– Any Topology
– Any Automation
Process
• (Theoretically)
portable between
Clouds and Tools
20. Types & Nodes
• Each component in the topology is a node:
• For example, a VM is a node, a Webserver is a Node
• The node holds the configuration (properties) and the relationships to
other nodes
• A node has a type
• The type is where the lifecycle interface operations are defined
• The type specified the properties schema
• Default lifecycle operations are:
• create, configure, start, stop, delete
22. Relationships
• There are 3 types of relationships:
• depends_on – which is the base type
• conataind_in – a component is hosted / contained / deployed within another
• connected_to – a component needs to establish a connection to another and
therefore this needs to be configured
• The relationship can define operation to be
applied on the source of the target instances
22
23. Relationships
• Possible operations on each:
• preconfigure – before node configure is called
• postconfigure – after node configure is called but before start
• establish – after start when connection needs to be established
• unlink – remove the connection
23
26. One Way of Putting This
Nodecellar_app
IS CONNECTED to mongod
27. Another Way of Putting This
Nodecellar_app
NEEDS a database of type
‘MongoDB’
28. Requirements and Capabilities
• Relationships will soon be replaced by a more
declarative model created by the latest TOSCA
work draft
• “This type needs a database connection” instead
of
“This node is connected to a node that happens
to be a database”
• Cloudify to follow once spec approved
29. Requirements and Capabilities
• A node type declares a certain capability
• Another type in a blueprint declares that it
requires this capability
• A node in a blueprint can also declare that it
needs a capability
30. Requirements and Capabilities
tosca.nodes.Database:
derived_from: tosca.nodes.Root
properties:
db_user:
type: string
db_password:
type: string
db_port:
type: integer
db_name:
type: string
description: the logical name of the database
capabilities:
- database_endpoint: tosca.capabilities.DatabaseEndpoint
...
32. Workflows
• TOSCA 1.0 – Workflows (Plans) are in any WF
language.
– Strong preference for BPMN 2.0
• TOSCA 2.0 – No change
• Cloudify 3 take – Workflows are currently python
based
– Tinkering with a more declarative approach
(OpenStack Mistral?)
33. Policies
• Still not defined by TOSCA, under discussion
• Cloudify 3 – YAML mostly, uses Riemann.io under
the hood
– You can create very sophisticated custom policies,
in Clojure…
34. Putting it all together
• TOSCA Template (Blueprint in Cloudify) contains:
– Application Topology
• Nodes
– Interfaces and operations
– Properties
– Relationships
– Workflows (install, uninstall, scale out, CD)
– Policies (scale trigger, recovery trigger)
37. The Only Constant Is Change!
Web 2.0 > ITIL > SOA > Virtualization > Public Clouds > SaaS > IaaS > PaaS > Docker Docker
Docker.. > Kubernentes > What’s next to come?
