Define global/environment dependencies emphasis on script processors

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major
    • None
    • Affects Version/s: CSD04
    • Component/s: Profile-YAML
    • None

      Per discussion on 05/07/15 TOSCA TC Special 4 Hour Meeting:

      Chapter 11:
      Comments captured: Perhaps need an advanced concept to define features that are not necessarily attached to a particular node. (like things you might include in a manifest). Like the requirement for a global time sync. How do we reference that feature, where is that feature attached to (some node?).

      perhaps add a new keyword like cloud that can hold all these Features that have no immediate Node to attach them to.

      Perhaps a syntax convention, where we might just list the names of the features (in some precedent order (sequence).

      Need to answer:
      -Who requires, it who fulfills it and how do u maintain the relationship?

      Luc: Environmental requirements. e.g., Python or something similar.

      Note: addressing the examples listed, global time server should be a capability (type that is defined) and requirements established for it from nodes that require it

            Assignee:
            Unassigned
            Reporter:
            Sahdev Zala (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: