Card

There is a need to allow the SDC User to manage Entity Requirements and Capabilities - the ability to Add/Edit/Delete them.

Description

Following the work we did on Properties by allowing the User to add/Edit/Delete properties on the Entity (SELF), there is a need also to do the same for Requirements and Capabilities

Comment: In VFC screen SDC User can only view the existing ones (as imported) but since VNF/PNF/Service has the Add Option, User must be able not only to view but also to manage them

Then User can use all Capability and Requirement types supported by SDC:

User should be able to define

• Capability:

  Field	Cardinality	Type	Description	Example
  Name	M	String	Unique name of the capability	binding, link
  Type	M	String	The Capability Type that this capability definition is based upon.Defined in global types.	VirtualBindable, VirtualLinkable, VirtualCompute
  Description	O	String	Textual description of the capability. Read only field that is derived from the capability type.Defined in global types per capability type.
  Valid Source	O	String[]	List of one or more Node Types that are supported as valid sources of any relationship established to the declared Capability. Read only field that is derived from the capability type. Defined in global types per capability type.	Compute, VirtualStorage, VNF
  Occurrences	O	String	Minimum/Maximum occurrences of the capability.Default for min=0, Default for max=Unbound. Other than Unbound, rest of the values are numeric	0-Unbound

• Requirements

  Field	Cardinality	Type	Description	Example
  Name	M	String	Unique name of the requirement	virtual storage, link
  Capability	M	String	The Capability Type that can fulfill the requirement.Defined in global types.	VirtualBindable, VirtualLinkable, VirtualCompute
  Node	O	String	The Node Type that contains the capability definition that can be used to fulfill the requirement.Defined in global types.	Block Storage, Virtual Storage
  Relationship	O	String	The Relationship Type to construct when fulfilling the requirement.Defined in global types.	DependsOn, AttachesTo, LinksTo
  Connected To	O	String
  Occurrences	O	String	Minimum/Maximum occurrences of the requirement. Default for min=0, Default for max=Unbound. Other than Unbound, rest of the values are numeric	0-Unbound

TOSCA

Capabilities and Requirements will be saved under the Service/VF/PNF node the same way as it is saved under VFC: 

Validations:

1. Name is unique within requirement or capability
2. Max >= min
3. Req/Cap can't be deleted/edited if in use in the service composition