[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (TOSCA-246) Define global/environment dependencies emphasis on script processors
[ https://issues.oasis-open.org/browse/TOSCA-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Rutkowski updated TOSCA-246: ------------------------------------- Due Date: 30/Jun/15 Component/s: Profile-YAML > Define global/environment dependencies emphasis on script processors > -------------------------------------------------------------------- > > Key: TOSCA-246 > URL: https://issues.oasis-open.org/browse/TOSCA-246 > Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC > Issue Type: Task > Components: Profile-YAML > Affects Versions: CSD04 > Reporter: Sahdev Zala > > 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 -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]