Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Move to Active OS Graph Database (e.g.Janus)

    • Titan has no active Open Source community. No community updates for over 1 year.
    • Janus good candidate (http://janusgraph.org/)
    • Janus supports Tinkerpop Abstraction.
    • Janus is an evolution of Titan
  • Scalable, HA A&AI

    • Back end needs to be HA. Need to confirm, explore.
    • Testing vs performance, throughput 
    • Scaling A&AI
  • A&AI Reconciliation from Network/Cloud.

    • Need to refresh from VIM
      • data integrity checks and reconciliation 
      • event based updates from VIM/SO/Controller
    • Different VIMs have different levels of detail.
    • MSO has this UC also.
    • Variety of different options here (VIM/SO/Controller).
  • SO, COntroller, VIM).
    • This could be covered by an ONAP level requirement for HA
    • Scaling may be ONAP Controller domain

    Extend Model-driven A&AI UsecasesUse cases

    • Move forward the A&I model-driven story, driven by3 use-case requirements
    • For Resource, service and schema change.
    •  Includes definition of (model-driven) API
    • Model evolution 
  • Track Change through Time
    • Tracking the Service, Resource changes across time
    • Support for point in time service/resource detail, e.g. for assurance 
  • Distributed A&AI

...

  • Specify any interface/API specification proposed,
    • Updated REST API for AAI aligned with updated model as per the 3 use cases
    • Updated API to support query of  time series data
  • Identity a list of features and functionality will be developed.
  • Identify what is in or out of scope. During the development phase, it helps reduce discussion.
    • Scalable, HS AAI
      • This could be covered by an ONAP level requirement for HA
      • Scaling may be ONAP Controller domain

Architecture Alignment:

Architecture diagram

...

  • What other ONAP projects does this project depend on?
  • SDC / Modelling
  • Multi VIM / SO / SDN-C
  • CommServ1 /MSB
  • Integration
  • OpenLab
  • How does this align with external standards/specifications?
    • APIs/Interfaces - TinkerPop, Gremlin
    • Information/data models - ONAP TOSCA model
  • Are there dependencies with other open source projects?
    • APIs/Interfaces
    • Integration Testing
      • Tinkerpop
    • etc.

Resources:

  • Primary Contact Person
  • Names, gerrit IDs, and company affiliations of the committers
  • Names and affiliations of any other contributors
  • Project Roles (include RACI chart, if applicable)

...

  • 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)

...