OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

tosca-interop message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Altering Service Templates


One question that is being discussed here is whether a Service Template is viewed as alterable by a third party or whether it is inviolable.  Clearly TOSCA does not specify digital signing or any other prevention mechanism...so the question is in the realm of Best Practice.

On one hand, the original author of a service template might be uncomfortable with others changing his/her specification.  On the other hand, there is going to be an ecosystem of third party TOSCA-aware applications who aren't limited by "read it and deploy it."

There are several use cases affected by this for template consumers who are not in the deployment business.  Some examples include:

1)  A third party who wants to add instrumentation or monitoring specifications to a service deployment.
2)  A third party who wants to provide recommendations for provisioning where they aren't specified by the original author...or even to suggest "better" ones.
3)  A third party who needs to add non-deployment-related content, such as a marketplace needing to add terms of use files, documentation, etc.

Various approaches suggest themselves:

a) Altering a copy of the service template and propagating it as a replacement.  

b) Creating a separate service template that references the original, leaving the original untouched.

c) Hybrids of the above.

I think this is a question that is going to come up in the outside world and there should be some consensus of opinion (if not actual specification language) about this.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]