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] (CAMP-208) Hierarchical Platforms

Michael Norman created CAMP-208:

             Summary: Hierarchical Platforms
                 Key: CAMP-208
                 URL: https://issues.oasis-open.org/browse/CAMP-208
             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
          Issue Type: Bug
            Reporter: Michael Norman
            Assignee: Anish Karmarkar

This is a placeholder jira to ensure discussion of an issue before 1.2 closeout.

We have had much discussion of the case where we are managing multiple platforms through a coordinated set of CAMP API endpoints which reference each other across Platform boundaries.  This feature comes from the Hateos/REST nature of the API and is extremely powerful and well-received by users. We also have a notion of a set of platform endpoints which is disembodied from the Platform - it is in some senses free-standing, but intuitively seems wrong. 

We have a number of use cases where we want to create Assemblies on "whichever platform can instantiate them". We also have use cases where people instantiate PaaS on other PaaS.

It may actually make more sense to introduce the notion of hierarchical platforms and to have a Root platform that references other Platforms

This message was sent by Atlassian JIRA

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