SDC Runtime Catalog Project scope change

Project Name:

• Proposed name for the project: SDC Runtime Catalog
• Proposed name for the repository:  sdc/rtc

Project description:

     The SDC RT-Catalog project aims to provide unified catalog management in ONAP runtime environment.

• Problem Resolved
  
  
  
  
  • Benefits

• • • Separation of concerns – Model Design  vs. Runtime Using
    • Simplification of Design time to Runtime model distribution
    • Consolidation of Runtime Data storage and management

Scope:

• • Management Objects:

          All Certified Design Model

          Consistent definitions with SDC Design Catalog

• 
  

• • •  Functions:

      
      

      • Provide RT-catalog GUI, storage and management functions, including CRUD, distribution.

      • Provide RT-catalog data status & Tracking
      • Provide search capacity for fast access across run-time catalog data
      • Provide portal for the Human Interface
      • Provide S3P related capacity for RT-Catalog

Architecture Alignment:

• RT-Catalog Storage

What other ONAP projects does this project depend on?

• SDC(DT-Catalog)
• RT-Components(UI\SO\VFC\APPC\Policy\.......)
• Common service(MSB/DMaaP/Parser.....)
  
  

How does this align with external standards/specifications?

• APIs/Interfaces - REST/PubSub
• Information/data models - Swagger JSON

Are there dependencies with other open source projects?

• APIs/Interfaces 
• Integration Testing
• etc.

Other Information:

link to seed code (if applicable)

Vendor Neutral

• if the proposal is coming from an existing proprietary codebase, have you ensured that all proprietary trademarks, logos, product names, etc., have been removed?

Meets Board policy (including IPR)

Use the above information to create a key project facts section on your project page

Key Project Facts:

Primary contact: michael.lando@att.com