VID R4 M3 Architecture Review

1. Brief Project Overview (brief as it should be known)
   1. VID is a used by Operations to instantiate services, and apply changes on them
      
      
2. New component capabilities for Dublin, i.e. the functional enhancements.
   1. Initiate workflows designed in SDC.
      Today VID is using a predefined list of workflows. After the change, list of workflows will be digested from SO.
   2. Display cloud-owner of each cloud region
      Each cloud-region will be presented to the user along with its owner, based on A&AI data
      
      
3. New or modified interfaces
4. If they are modified, are the backwards compatible?
5. Interface naming (point to an example)

6. Reference to the interfaces.

   New or modified	backward compatible		Interface naming		References
   Modified	No	Consume from A&AI	PNF	Get pnf data using new /network/pnfs/?pnf-name={pnf-name}, instead of /network/pnfs/pnf/{pnf-name}.	Proposal to Change AAI PNF Entity to use PNF-ID as key
   Modified	Yes	Send new property to SO	Service Instantiation	Add cloudOwner field to existing POST requests
   New	n/a	Consume from SO	Workflows	Get list of available Workflows by VNF model-id	n/a

7. What are the system limits?

H/A using Kubernetes, user-facing UI so low-intensity usage.

1. Involved use cases, architectural capabilities or functional requirements.
   1. 5G - PNF Plug and Play (Casablanca carry-over items) (VID A&AI Schema Changes PNF-id vs PNF-name.)
   2. Consistent ID of a Cloud Region (Dublin)
   3. Change Management Dublin Extensions
      
      
2. Listing of new or impacted models used by the project (for information only).
   
   1. None