Evaluate container lifecycle support in TOSCA TOSCA – 174 Adhoc TC.

Slides:



Advertisements
Similar presentations
It’s the App, Stupid! Orchestration, Automation, Scaling & What’s in Between Yaron Parasol, Uri
Advertisements

Docker Container Modeling Goals Goals (not requirements) Not proliferate Node Types for “Docker” 1.Consider modeling “Docker” as an (explicit) runtime.
Docker Container Modeling Goals Goals (not requirements) Not proliferate Node Types for “Docker” 1.Consider modeling “Docker” as an (explicit) runtime.
ContainerApp Container -X memory -Y CPU -Z Storage -N Network -Port ContainerManager Container Hypervisor (Java Runtime) -Understands IaaS of Cloud / Provider.
Microsoft Ignite /16/2017 2:42 PM
Features Scalability Availability Latency Lifecycle Data Integrity Portability Manage Services Deliver Features Faster Create Business Value.
FI-WARE – Future Internet Core Platform FI-WARE Cloud Hosting July 2011 High-level description.
Software Component (Container + Containee) Software Component (Container + Containee) WebServer HostedOn Compute (Container) Compute (Container) Exploring.
Container Hierarchies and Related Issues
Software Component (Container + Containee) Software Component (Container + Containee) WebServer HostedOn Compute (Container) Compute (Container) Exploring.
Evaluate container lifecycle support in TOSCA TOSCA – 174 Adhoc TC.
Plan Introduction What is Cloud Computing?
TOSCA Workloads with OpenStack Heat-Translator
Software Component (Container + Containee) Software Component (Container + Containee) WebServer HostedOn Compute (Container) Compute (Container) Exploring.
Additional SugarCRM details for complete, functional, and portable deployment.
A Brief Overview by Aditya Dutt March 18 th ’ Aditya Inc.
Windows Azure Conference 2014 Running Docker on Windows Azure.
Migrating Business Apps to Windows Azure Marc Müller Principal Consultant, 4tecture GmbH
Software Architecture
Proposal by CA Technologies, IBM, SAP, Vnomic
CloudNaaS: A Cloud Networking Platform for Enterprise Applications Theophilus Benson*, Aditya Akella*, Anees Shaikh +, Sambit Sahu + (*University of Wisconsin,
Software Component (Container + Containee) Software Component (Container + Containee) WebServer HostedOn Compute (Container) Compute (Container) Exploring.
What is the cloud ? IT as a service Cloud allows access to services without user technical knowledge or control of supporting infrastructure Best described.
Kind: “Pod” (i.e. Type) kind: “Pod” (i.e. Type) Kubernetes Analysis: 2 types of containers “Dumb” (no HA, no Autoscale) = Pod Template kind: “ReplicationController”
Objective Propose a simple and concise set of “Core” Entities and Relations for TOSCA useful for any application deployment in a cloud Enable users to.
Objective: Enable portability and semi-automatic management of applications across clouds regardless of provider platform or infrastructure thus expanding.
Building micro-service based applications using Azure Service Fabric
Creating highly available and resilient Microservices on Microsoft Azure Service Fabric
How TOSCA Adds Value in the NFV world
Kind: “Pod” (i.e. Type) kind: “Pod” (i.e. Type) Kubernetes Analysis: 2 types of containers “Dumb” (no HA, no Autoscale) = Pod Template kind: “ReplicationController”
TOSCA Topology and Orchestration Specification for Cloud Applications (TOSCA) Standard OASIS TOSCA presentation to ETSI NFV Information Modelling Workshop.
Evaluate container lifecycle support in TOSCA TOSCA – 174 Adhoc TC.
How TOSCA Adds Value in NFV world
Features Scalability Manage Services Deliver Features Faster Create Business Value Availability Latency Lifecycle Data Integrity Portability.
How TOSCA Adds Value in the NFV world
Hello Cloud… Mike Benkovich
Evaluate container lifecycle support in TOSCA TOSCA – 174 Adhoc TC.
ALL INFORMATION PRESENTED AS WELL AS ALL SESSIONS ARE MICROSOFT CONFIDENTIAL AND UNDER YOUR NON-DISCLOSURE AGREEMENT (NDA) AND\OR TECHNOLOGY PREVIEW.
Objective Propose a simple and concise set of “Core” Entities and Relations for TOSCA useful for any application deployment in a cloud Enable users to.
And scales by cloning the app on multiple servers/VMs/Containers Traditional architecture approach Microservices architecture approach A microservice.
TOSCA v1.0 Figures. Definition of building blocks for services … along with the implementation artifacts for manageability operations … and the definition.
INSTANCE MODEL AD HOC GROUP UPDATES Alessandro Rossini Sivan Barzily March 2016.
Instance Model Considerations Instance Model Objectives Provide complete representation of the state of a TOSCA service template deployment.
1 Cluster – defn. TBD Derek: Homogenous set of nodes; in TOSCA that is a single node template. -Matt said this can also be viewed as a stack -- Derek can.
Chapter 12: Architecture
Accelerate your DevOps with OpenShift by Red Hat
Service Delivery and Governance
Cluster – defn. TBD Derek:
Service Delivery and Governance
Windows Azure Cloud Visit – Ravindra verma.
OASIS TOSCA Report for December ONAP Event
Capability issues Shitao li.
Intro to Docker Containers and Orchestration in the Cloud
Cloud Application Marketplaces
Service Model Monitoring Cloud Application Marketplaces
Cloud Application Marketplaces
Cloud Application Marketplaces
Chapter 12: Physical Architecture Layer Design
Learn. Imagine. Build. .NET Conf
Service Delivery and Governance
Managing Services with VMM and App Controller
Saranya Sriram Developer Evangelist | Microsoft
Cloud Application Marketplaces
Lifecycle Management Automation through TOSCA
Cloud Computing: Concepts
SQL Server High Availability
Containers on Azure Peter Lasne Sr. Software Development Engineer
Microsoft Azure Services Platform
Presentation transcript:

Evaluate container lifecycle support in TOSCA TOSCA – 174 Adhoc TC

Container management focus Container grouping definition based on operational behavior – (Scalable VS Non-scalable) Cluster/group level policies scope to define group policies around roles, scale, connectivity and quorum aspects. Scaling is core aspect of cluster/group definition. scaling requires event processing. Use policies to define Event, condition and action model Cluster component deployment order considerations Last updates TOSCA Evaluate container lifecycle support in TOSCA

Tier : Set of load balanced homogeneous nodes, single end point, scalability and availability, limiting cardinality Cluster: Intelligent operations and lifecycle management for group of nodes Clustering requirements – Support simple constructs through policies : Topology, Scalability, Scaling group, placement, membership, availability, homogeneous, – Support concept of subclass cluster (smart group) : load balancing – Groups interactions : within, across, tiered – Support constraint processing – Support lifecycle event Changes to TOSCA – Define group node – Support policy based group behavior Clustering and Tiering TOSCA Evaluate container lifecycle support in TOSCA

Capabilities type for storage and networking to containers Change cardinalities to have zero for server less Abstract type is too declarative - revisit node and relationship type and use capabilities and requirements Limiting the requirement type to use only capability type Current focus TOSCA Evaluate container lifecycle support in TOSCA

Container modeling approach TOSCA Evaluate container lifecycle support in TOSCA Hosted On Software Component Container (Docker Runtime Capability) Container (Docker Runtime Capability) Containee (Docker Runtime Requirement) Containee (Docker Runtime Requirement) Capabilities Container Docker Requiremen ts Docker artifacts: - image: mime_type: Docker repo: xxx URI: xxx Software Component (Container + Containee) Software Component (Container + Containee) WebServer Compute (Container) Compute (Container) Capabilities Requirements Container OpSys Scalable Container Capabilities Container Artifacts Docker Image (Apache.TAR) requirements: - host: capability: tosca.capabilities.Container node: NULL relationship: tosca.relationships.HostedOn capabilities: host: type: tosca.capabilities.Container valid_source_types: [NULL] Requirement s Container IaaS Modeling -Compute is explicit or implicit PaaS Modeling Container is explicit or implicit Agnostic Cloud Foundry Azure directive: substitutable Container