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


Help: OASIS Mailing Lists Help | MarkMail Help

camp message

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

Subject: [OASIS Issue Tracker] Commented: (CAMP-29) "Application Component" and "Platform Component" should be collapsed into a single "Component"; "Application Component Template" and "Platform Component Template" should be collapsed into a single "Component Template"

    [ http://tools.oasis-open.org/issues/browse/CAMP-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34437#action_34437 ] 

Mark Carlson commented on CAMP-29:

PCTs are configuration of services offered up by the platform. They could be "natively" supplied by the platform or "resupplied" by the platform from installed components (by other users). In the case of resupplied, it is an interesting problem as to who pays for the usage of the component, but by using a PCT to represent it, the platform can charge for it's usage and the user can have control over it's scaling, etc. Regardless, from an implementation point of view, the Platform needs to instrument these components, providing metrics, configuration scaling, etc. parameters. 

ACTs are configuration of the users' components and the platform doesn't need to instrument these components - it just passes the configuration on to the component opaquely. 

If an SCT is just a piece of code shared by another user and not a "service" that the platform needs to manage the scaling, metering and billing for, then essentially is just part of a Library that can be imported as an ACT for this user.  If an SCT is essentially a URL to an external service, it is outside the management domain of this platform and thus does not need a resource to manage it - thus no SCT, ACT or PCT is needed.

> "Application Component" and "Platform Component" should be collapsed into a single "Component"; "Application Component Template" and "Platform Component Template" should be collapsed into a single "Component Template"
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>                 Key: CAMP-29
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-29
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Improvement
>          Components: Spec
>            Reporter: Gilbert Pilz
>            Assignee: Gilbert Pilz
>            Priority: Critical
> There is no justification for the complexity caused by segregation of components and templates into "Application" and "Platform" sub-types. The methods for discovering a template, figuring out whether that template describes a services that will meet your requirements, indicating that your application will make use of the service described by that template, indicating that your application is using a service, etc. do not vary between "Application" things and "Platform" things. At present, the only purpose of the Application/Platform distinction is to indicate the provenance of a component/template. If such an indication is necessary, it can be provided by some other mechanism such as an attribute (e.g. { "provenance" : "platform" })

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


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