[OASIS Issue Tracker] (TOSCA-299) Fix VNF Forwarding Graph schema

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

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

Chris Lauwers edited comment on TOSCA-299 at 6/16/16 12:53 AM:
---------------------------------------------------------------

The only thing wrong with the VNFFG type is the use of the keyname "targets" to specify valid member node types. In the published Simple Profile spec, this has been replaced with the keyname "members". When using the members keyname, this type passes validation just fine (in fact you can see this type in the Group Types section on http://ubicity.com/types.html)

Do you believe there is anything else wrong with this type?


was (Author: lauwers):
The only thing with the VNFFG type is the use of the keyname "targets" to specify valid member node types. In the published Simple Profile spec, this has been replaced with the keyname "members". When using the members keyname, this type passes validation just fine (in fact you can see this type in the Group Types section on http://ubicity.com/types.html)

Do you believe there is anything else wrong with this type?

> Fix VNF Forwarding Graph schema
> -------------------------------
>
>                 Key: TOSCA-299
>                 URL: https://issues.oasis-open.org/browse/TOSCA-299
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Bug
>          Components: Profile-NFV
>    Affects Versions: CSD03
>            Reporter: John Crandall
>
> Fix existing VNF Forwarding Graph schema. It is not parsing as a valid schema at this time. 



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