...

• Interoperability  

  • SDO specifications supported: 
  • APIs/Interfaces:
    • http/https northbound towards web browser
  • Information/data models:
    • Relies on customer data from keycloak
    • Current approach is to work dataless except for caching southbound requests
  • If there is an existing ONAP project that does something similar to this project explain why this being a new stand-alone project?
    • ONAP project is unmaintained. Telekom has a portal it uses internally and would like to donate parts of it's code

• Other Dependencies

  • Upstream open source projects: 
    • Keycloak 
  • Non ONAP APIs/Interfaces:
    • KeyCloak
  • Specific IDE integration requirements:
    • None
  • Integration Testing: 
    • TBD and aligned with existing ONAP processes. Extensive E2E tests for DT use cases existing but not yet stripped down for smaller feature set
  • etc.

Community Alignment:

• Vendor Neutrality:
  • The PortalNG does not include any vendor specific code nor require any vendor specific integrations (e.g. Element Manager)
• Seed code Location (if any):
  • In-House
• If "In-House" please answer the the following questions:
  • Code is ready to be uploaded
    • Theoretically yes
  • Approved by project leadership team
    • approval from DT open source responsible available, approval from DT
    XXX
    • project lead available
  • All proprietary trademarks, logos, product names and internal company secrets were removed
    • yes
• No waivers to ONAP policies (including IPR) are required by this project.
  
  TODO
  

• Plan for providing education to onboard the ONAP developer community : Currently no plan available for this.
  
  TODO
  

...