[OASIS Issue Tracker] (TOSCA-200) REVIEW - Query based on capability

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/TOSCA-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61828#comment-61828 ] 

Paul Lipton commented on TOSCA-200:
-----------------------------------

Formally introduced to the TC on 2016-02-18. From the minutes:

[13:07] Damian A. Tamburri (PoliMi - SCRIBE): Sivan is reporting that the issue aims at tagging instances that exhibit certain characteristics and providing the ability to query using this additional information

[13:08] Damian A. Tamburri (PoliMi - SCRIBE): Simon remarks that it may be an issue for the Instance-Model but Matt may comment that it could be already addressed elsewhere

[13:09] Damian A. Tamburri (PoliMi - SCRIBE): Matt is reporting on the concept of meta-data, this can be used at instance-model or catalog to tag things... in open-stack this could be used to coalesce or aggregate type-meaning information and creating groups with it

[13:11] Damian A. Tamburri (PoliMi - SCRIBE): action item should be to capture the use-cases that are not covered by the meta-data concept and its usages - further details may be needed to close the issue. However, there are instance-model concerns on the issue and therefore there may be perspectives which are not covered by the meta-data concept

[13:13] Damian A. Tamburri (PoliMi - SCRIBE): Derek comments that the issues may be separated, perhaps additional details should be tweaked in the service template definition

[13:14] Damian A. Tamburri (PoliMi - SCRIBE): Sivan agrees that issue can be passed to Instance-model ad-hoc to proceed with its further exploration and resolution

> REVIEW - Query based on capability 
> -----------------------------------
>
>                 Key: TOSCA-200
>                 URL: https://issues.oasis-open.org/browse/TOSCA-200
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>          Components: Profile-YAML
>            Reporter: Yaron Parasol
>            Assignee: Avi Vachnis
>              Labels: function, instances
>
> In order to act on specific instances based on their capability - for example RabbitMQ nodes that are disk based, we need the intrinsic function that will filter out these instances. If capability doesn't make sense for this, we need tags on instacnes



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)