Uploaded image for project: 'OASIS Cloud Application Management for Platforms (CAMP) TC'
  1. OASIS Cloud Application Management for Platforms (CAMP) TC
  2. CAMP-175

Could remove "artifacts" or make them optional

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 1.2
    • Fix Version/s: None
    • Component/s: Spec
    • Labels:
      None
    • Resolution:
      Hide

      (1) artifacts are already optional,
      (2) the issue of wanting to create an instance of a service is covered in issue CAMP-218 (https://issues.oasis-open.org/browse/CAMP-218)

      Show
      (1) artifacts are already optional, (2) the issue of wanting to create an instance of a service is covered in issue CAMP-218 ( https://issues.oasis-open.org/browse/CAMP-218 )

      Description

      Some people we've talked to find the "artifacts" entry point for the plan confusing. Personally I like it and IMHO it should become the standard way to do things.

      But right now people mostly seem to be building things up and so the "services" entry point is preferred – look at how docker/fig/compose do it, and cloud foundry, and apache brooklyn.

      To simplify we could remove all mention of "artifacts" or make them optional.

      Or not ... this is just something to be aware of.

        Attachments

          Activity

            People

            • Assignee:
              alex.heneveld Alex Heneveld (Inactive)
              Reporter:
              alex.heneveld Alex Heneveld (Inactive)
            • Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated: