Alternative HPA Requirements Design

All infrastructure capability types inherit from the basic onap.capabilities.Infrastructure:

capability_types:
  onap.capabilities.Infrastracture:
    derived_from: tosca.capabilities.Root
    description: a basic description of infrastructure resources
    properties:
      architecture:
        description: vendor+architecture, for example, Intel64
        type: string
        required: false          
      custom_features:
        description: |
          Additional features description, serialized in a well-known format.
        type: string
        required: false          

Since all HPA-oriented capability types are derived from this basic type, they will all inherit its properties:

• architecture - allows the VFC vendors to focus their requirements on a specific hardware architecture, for example "Intel x86".
• custom_features - an opaque container for a list of feature definitions. Any text, the only limitation is that it should not break the YAML/TOSCA formatting. The contents of this property is actually not part of the TOSCA model!