Versions Compared

Key

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


Info

 - New Location as of 01-Apr-2020

TSC Architecture subcommittee purpose:

The architecture subcommittee is responsible for developing and maintaining a functional ONAP architecture, guided by principles. This functional architecture helps maintain relationships and interaction between functional modules, which may include high level information flows between the modules supporting the use case(s) driving each release. It also helps the community with project proposals by clarifying the new project relationship with existing components.

...

The architecture subcommittee will consult with Projects to help drive alignment between components and with the functional architecture.

TSC subcommittee expected deliverables:

The architecture subcommittee will develop and maintain a functional architecture diagram and any explanatory material.

Periodically, or midway through a release, the architecture subcommittee will schedule a walk-through with each project to understand API interactions between components.

TSC subcommittee starting participants:

The architecture subcommittee is open to all interested participants, and meetings are open.

...

Architecture Principles (New)

Open Issues (New)

Dublin Architecture Planning Meeting (Copy)  (Montreal, Oct 29-31)

JIRA project for issue prioritization: https://jira.onap.org/projects/ONAPARC/

Next Call

Anchor
Next Call
Next Call

Jira
serverONAP JIRA
columnskey,summary,labels
maximumIssues20
jqlQueryproject=onaparc and priority=Highest and status IN ("Open", "Submitted", "To Do", "Reopened", "In Progress") AND (Labels not in (ARC-REQ-DUBLIN) or labels is EMPTY)
serverId425b2b0a-557c-3c0c-b515-579789cceedb

2nd week

Anchor
2nd week
2nd week

Jira
serverONAP JIRA
columnskey,summary,labels
maximumIssues20
jqlQueryproject=onaparc and priority=High and status IN ("Open", "Submitted", "To Do", "Reopened", "In Progress")
serverId425b2b0a-557c-3c0c-b515-579789cceedb

Followup

Items that are finished from an architecture point of view, but not delived into the the community:

...

Jira
serverONAP JIRA
columnskey,summary,labels
maximumIssues20
jqlQueryproject=onaparc and status IN ("Delivered")
serverId425b2b0a-557c-3c0c-b515-579789cceedb

Task Forces:

The architecture sub-committee can initiate tasks forces to progress specific topics.  The output of the tasks forces are always reported back into the architecture sub-committee before further progressing towards the TSC or the ONAP projects.  As per the nature of the architecture sub-committee the Task Forces are advisory by nature.  The creation and termination of tasks forces are clearly announced in the architecture sub-committee meetings.

The current task forces are can be found here: ONAP Architecture TaskForces - Ongoing (New)


Meeting Contributions:

The meeting input and conributions can be found here: ArchCom Contributions (New)

Meeting logistics:

Recurring meetings: Tuesdays, 1400-1600 UTC (starting June 13) 


Meeting Minutes:

The meeting minutes can be found here:  ONAP Architecture Meeting Notes (New) 

...