[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (TOSCA-126) Specifying connectivity to endpoints hosted outside a Service Template
[ http://tools.oasis-open.org/issues/browse/TOSCA-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=36332#action_36332 ] Paul Lipton commented on TOSCA-126: ------------------------------------ On January 16th, the TC discussed this issue (see latest minutes at: https://www.oasis-open.org/apps/org/workgroup/tosca/download.php/51983/latest/TOSCA Minutes 2014-01-16.docx). Most of the minutes are below: Paul Lipton (co-chair) WebEx: https://tools.oasis-open.org/issues/browse/TOSCA-126 Frank Leymann (scribe - IBM): Derek gives an overview on TOSCA-126 Frank Leymann (scribe - IBM): Dale - what in the case of two different engines hosting instances of the two different service templates? Frank Leymann (scribe - IBM): Dale - are the two different templates self-contained? Frank Leymann (scribe - IBM): Derek - we need a mechanism to publish deployed endpoints. Frank Leymann (scribe - IBM): Dale - need an API to pull metadata from a TOSCA engine about deployed service instances Frank Leymann (scribe - IBM): Derek - need a use case to refine this Paul Lipton (co-chair) WebEx: Dale referenced OData as an example (client requesting metadata on what data is available) type of use case. More decoupled. Frank Leymann (scribe - IBM): We need a mechanism to make TOSCA engine-scoped instance IDs to be globally (some sort of URIs) --- Frank, scribe hat off Frank Leymann (scribe - IBM): Then, the Plan Portability API supports the discovery of metadata. I.e. we could fold in these requirements into the API Frank Leymann (scribe - IBM): Matt - solving this "connectivity" problem (ie connecting to endpoints) is important Frank Leymann (scribe - IBM): Matt - this must include navigation capabilities through a service structure Frank Leymann (scribe - IBM): Richard - every service template and/or deployed services should be connectable with others, across TOSCA engines/domains. Frank Leymann (scribe - IBM): Richard - semantics of connects_to should cover scenarios not only "inside firewall" Frank Leymann (scribe - IBM): Matt - need to include aspects like credentials in our models, also in our normative types > Specifying connectivity to endpoints hosted outside a Service Template > ---------------------------------------------------------------------- > > Key: TOSCA-126 > URL: http://tools.oasis-open.org/issues/browse/TOSCA-126 > Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC > Issue Type: Improvement > Components: Interop > Reporter: Derek Palma > > Specifying connectivity to endpoints hosted outside a Service Template is a common requirement since components in services must often connect to other services or other components which are already deployed or offered by a completely different administrative entity at possibly different locations. > The two major variations are: > 1) Connection to an endpoint hosted in a component in another TOSCA service. I.e. how to model inter Service Template dependencies loosely > 2) Connection to an endpoint outside of TOSCA such as an arbitrary endpoint on the Internet. -- 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]