[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (TOSCA-185) DEFER - CSD05 - Instance model (design considerations)
[ https://issues.oasis-open.org/browse/TOSCA-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60509#comment-60509 ]
Alessandro Rossini edited comment on TOSCA-185 at 8/12/15 8:35 AM:
-------------------------------------------------------------------
I support the definition of an instance model and I believe that it could allow the full exploitation of TOSCA models at run-time.
At SINTEF, we have developed the Cloud Modelling Framework (CloudMF) (see http://www.cloudml.org/ ) in the context of the EU-funded projects MODAClouds (see http://www.modaclouds.eu/ ) and PaaSage (see http://www.paasage.eu/ ). It consists of two main ingredients: the Cloud Modelling Language (CloudML) and a models@run-time environment.
CloudML is a domain-specific language for specifying the deployment topology of cloud-based applications. It is akin to TOSCA, but it supports the instance model to allow the full exploitation of CloudML models at run-time.
Models@run-time (see http://dx.doi.org/10.1109/MC.2009.326 ) is an architectural pattern for dynamically adaptive systems that leverages upon models at both design-time and run-time. In CloudMF, the models@run-time environment provides a CloudML model causally connected to the running cloud-based application, whereby any modification to the model is enacted on-demand in the running application, and any change in the running application is automatically reflected in the model.
CloudML and the models@run-time environment enable not only modellers but also reasoning engines to manipulate CloudML models at run-time. This way, CloudMF enables self-adaptive cloud-based applications; i.e., cloud-based applications that automatically adapt to changes in the environment.
I will present the models@run-time approach to the TC at the upcoming meeting.
was (Author: alessandro.rossini):
I support the definition of an instance model and I believe that it could allow the full exploitation of TOSCA models at run-time.
At SINTEF, we have developed the Cloud Modelling Framework (CloudMF) (see http://www.cloudml.org/) in the context of the EU-funded projects MODAClouds (see http://www.modaclouds.eu/) and PaaSage (see http://www.paasage.eu/). It consists of two main ingredients: the Cloud Modelling Language (CloudML) and a models@run-time environment.
CloudML is a domain-specific language for specifying the deployment topology of cloud-based applications. It is akin to TOSCA, but it supports the instance model to allow the full exploitation of CloudML models at run-time.
Models@run-time (see http://dx.doi.org/10.1109/MC.2009.326) is an architectural pattern for dynamically adaptive systems that leverages upon models at both design-time and run-time. In CloudMF, the models@run-time environment provides a CloudML model causally connected to the running cloud-based application, whereby any modification to the model is enacted on-demand in the running application, and any change in the running application is automatically reflected in the model.
CloudML and the models@run-time environment enable not only modellers but also reasoning engines to manipulate CloudML models at run-time. This way, CloudMF enables self-adaptive cloud-based applications; i.e., cloud-based applications that automatically adapt to changes in the environment.
I will present the models@run-time approach to the TC at the upcoming meeting.
> DEFER - CSD05 - Instance model (design considerations)
> ------------------------------------------------------
>
> Key: TOSCA-185
> URL: https://issues.oasis-open.org/browse/TOSCA-185
> Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
> Issue Type: Improvement
> Components: Profile-YAML
> Reporter: Derek Palma
> Assignee: Jacques Durand
>
> We have reached a point where we need to define an instance model. We should consider describing the following:
> 1) How a template causes node and relationship instances to be created
> 2) The schemas of node and relationship instances based on their respective types
> 3) The ability of a TOSCA runtime to add its own properties to an instance
> 4) The ability of a node or relationship operations to set attributes
> 5) Navigation of the instance model
> 6) Navigation from the instance to their respective templates and types.
> 7) Serialization of the instance model in YAML
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]