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] Updated: (CAMP-69) Need interoperable means to obtain the endpoint(s) of an Application Component

     [ http://tools.oasis-open.org/issues/browse/CAMP-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Chapman  updated CAMP-69:

    Proposal: close no action, we are not going to add an endpoint attribute at the component level. However should someone want to propose a new type  that should be raised as a new issue.

> Need interoperable means to obtain the endpoint(s) of an Application Component
> ------------------------------------------------------------------------------
>                 Key: CAMP-69
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-69
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>          Components: Spec
>            Reporter: Derek Palma
>            Priority: Minor
> My perspective is as someone who wants to write clients which can interface and do pretty much the same operations across clouds. If each cloud requires different logic for common operations, then the value of CAMP becomes a common REST syntax which is less attractive since platforms may not expose their most interesting features via CAMP initially (so why switch if I don't gain much). I don't have a problem doing platform unique things with unique logic to take advantage of unique capabilities. I'd expect to be able to do closer to the 80% of the operations common across all platforms.
> I consider obtaining an endpoint of a deployed app as part of the deployment process and even the endpoint information as part of the deployed application's assembly mainly because it's intuitively hard to accept this is missing if I can get the whole assembly. I.e., why not finish and go the last mile?
> Regardless, there needs to be a way to get the endpoint(s) (maybe just the raw one in the platform's DNS space) or compute it using some input data and some out of band information. This would require documentation for each 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]