Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 2 Next »

One Command to command whole ONAP !
Model-driven CLI

Project Name:

  • Proposed name for the project: onap-cli
  • Proposed name for the repository: onap-cli

Project description:

  • Both carrier and enterprise customers prefer commands over GUI on many situations such as automation, CI, etc. so this project is launched to provide required Command-Line Interface(CLI) as commands to operate ONAP functionalities from Unix or windows shell.
  • Different type of Users like end-user, admin, operator could operate ONAP functionalities.

Scope:

  • Provide a Model driven framework to help ONAP community and ONAP end-user to develop the required commands 
    • By using YAML file and without writing any source code
    • By implementing plug-ins for specific commands
  • Provide direct command mode (useful in scripting based automation) like in CI, docker, etc
  • Provide interactive mode, where user login once and operate ONAP and exit
  • Provide consistent commands schematics across different ONAP functionalities. 

Architecture Alignment:

  • Dependencies
    • ONAP CLI uses REST API to communicate with ONAP, so it depends on the ONAP API documentation project
      • ONAP authendication service REST API
    • Different ONAP projects for respective java SDK, if any
  • Integration project (CI & docker) would depends on this project ONAP CLI for automation

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