RE: [tosca] [OASIS Issue Tracker] (TOSCA-258) Define an C.8.5.4 tosca.artifacts.Implementation.generator

[Luca Gioppo <luca.gioppo@csi.it>]

Yes!

In my orchestrator's implementation I need to generate artifacts from freemarker templates.

The templates are in the csar file and I need to create/generate the real template merging the node properties in the template.

I can have 2 type of "templates" one that generate a real artifact and one that generate content to be used in another template tipically the father's one.

 

To make an example:

I need to generate a puppet manifest for Apache, but th manifest needs to contain both the Apache node information (this will become an apache class in the manifest) together with the apache::virtual_host node information (for me the virtual host is a child node of the apache one); also the virtual host content needs to end up in the same manifest.

So I need to take the template of each virtual host generate witht the properties the content and NOT save to a file, but keeping the content and pass it the the apache node so that the apache template can include also that content.

 

I'm thinking on how to model this in a way that is not "just my own" it could be an artifact of some type that containd the template behaviour and the "do not persist content" behaviour.

 

First I think that we should talk about the use case and validate it as a proper option to have than find out if we want to offer a proposed definition for it. Otherwise it will remain a specific implementation of mine.

 

A proposal can be that accordingly to relations VH have to processed before the tosca.artifact.implementation.template with element persist=false will instruct the orchestrator to merge the properties from the content=[prop1, prop2] and keep the content

 

In the apache the tosca.artifact.implementation.template with persist=true will really write the file in location=path using content=[art1, prop1]

 

Is a bit messy in a mail but I will produce a word file for this so we can better discuss it

 

Luca

 

 >  _________________________________________________________________________

 >  

 >  > Il 18 giugno 2015 alle 16.57 Chris Lauwers <lauwers@ubicity.com> ha scritto:

 >  >

 >  >

 >  > Are you suggesting support for templating perhaps?

 >  >

 >  > -----Original Message-----

 >  > From: tosca@lists.oasis-open.org [mailto:tosca@lists.oasis-open.org] On Behalf Of OASIS Issues Tracker

 >  > Sent: Wednesday, June 17, 2015 12:04 AM

 >  > To: tosca@lists.oasis-open.org

 >  > Subject: [tosca] [OASIS Issue Tracker] (TOSCA-258) Define an C.8.5.4 tosca.artifacts.Implementation.generator

 >  >

 >  >

 >  > [ https://issues.oasis-open.org/browse/TOSCA-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59808#comment-59808 ]

 >  >

 >  > Luca Gioppo commented on TOSCA-258:

 >  > -----------------------------------

 >  >

 >  > The needs is to create artifacts starting from blueprint of artifacts.

 >  > Using env variables is not always possible and having a means to allow the orchestrator to generate some content is an useful option.

 >  >

 >  > > Define an C.8.5.4 tosca.artifacts.Implementation.generator

 >  > > ----------------------------------------------------------

 >  > >

 >  > > Key: TOSCA-258

 >  > > URL: https://issues.oasis-open.org/browse/TOSCA-258

 >  > > Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC

 >  > > Issue Type: Improvement

 >  > > Components: Profile-YAML

 >  > > Reporter: Luca Gioppo

 >  > >

 >  > > The need is to generate an artifact from a template that is in the csar archive.

 >  > > This artifact will be than used by the orchestrator in following steps.

 >  > > Generation merge values from properties or attributes of nodes with the template.

 >  > > This allows dynamic generation of artifacts like puppet manifests

 >  >

 >  >

 >  >

 >  > --

 >  > This message was sent by Atlassian JIRA

 >  > (v6.2.2#6258)

 >  >

 >  > ---------------------------------------------------------------------

 >  > To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at:

 >  > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

 >  >

 >