Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 2 Next »

Project Name:

  • Proposed name for the project: AAI
  • Proposed name for the repository: aai

Project description:

  • Active and Available Inventory (AAI) is the ONAP subsystem that provides real-time views of Resources and Services and their relationships. AAI not only forms a registry of active, available, and assigned assets, it also maintains up-to-date views of the multidimensional relationships among these assets, including their relevance to different components of ONAP. 

Scope:

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

    • Titan has no active Open Source community. No community updates for over 1 year.
    • Need to put A&AI onto Active graph project.
    • Janus good candidate.
    • Janus supports Tinkerpop Abstraction.
    • Janus is 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
    • Different VIMs have different levels of detail.
    • MSO has this UC also.
    • Variety of different options here (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 Usecases

    • 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

    • How does A&AI serve local orchestrator, local DCAE across large geographical  regions
    • Resource data, interim data cant be centralized - too costly.

Describe the functionality to be provided by the project.  Please provide the full intended scope of the project; not just what is intended for the project's first release.

  • Specify any interface/API specification proposed,
  • 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.

Architecture Alignment:

Architecture diagram

 

  • How does this project fit into the rest of the ONAP Architecture?
    • Please Include architecture diagram if possible
    • What other ONAP projects does this project depend on?
  • How does this align with external standards/specifications?
    • APIs/Interfaces
    • Information/data models
  • Are there dependencies with other open source projects?
    • APIs/Interfaces
    • Integration Testing
    • 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)

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

Project Name:

  • JIRA project name:
  • JIRA project prefix:

Repo name: Lifecycle State: Primary Contact: Project Lead: mailing list tag [Should match Jira Project Prefix]  Committers: foo@bar.com baz@qux.com *Link to TSC approval: 
Link to approval of additional submitters: 

  • No labels