Card

Current state of SDC on Operations (VNFs and Services) allows a user to specify the operation name which is then placed into a new interface type org.openecomp.interfaces.node.lifecycle.XYZ, where XYZ is the name of the model.

We would like to extend this behavior to allow multiple interfaces for a given model to be defined.

We need to provide a mix of pre-defined (from normative) and user defined ones.

Description

SDC UI should enable the User to select an Interface from a list of pre-defined interfaces OR "Other"

1. If the User selected “Other” than he can name the interface which should be made a local type to this model.  In this case Operation name is a free text as today
2. If the User selected a global one from the normative types then SDC will restrict the Operation Names based on the interface normative definition itself.

As part of this EPIC some Operation related UX changes need to be address 

• Operation list 
  The operation list tab which currently uses panels needs to:
  • Be in-sync with other tabs in the Catalog that use tables instead of tiles
  • Allow a user to see all operations per interface and all operations across all interfaces 
• Operation screen
  • New field for interface
    This field is an editable drop down which allows the user to both select from existing list as well as add new value
  • Operation name
    • If user selected interface from the list - show list of the selected interface operations
    • If user added new value - let the user type in a free operation name
  • Description field:
    The description size for a given interface is too restrictive, we are currently providing a one line description, and it would be good to make this a multi-line text box that the user can control  
  • Validations:
    • Operation name is now unique not only based solely on the name but on the combination of interface and name
    • Manually typed interface should be unique in the context of the operation's service/VF.
      Only one manual interface/operation can be defined in a given context.
• Operations of service input consumption
  • As part of this screen, and likely similar to the operation list need to show all the operations with their interfaces.