Please note that the Architecture subcommittee page has moved to a new location within in this wiki.
Click on the link below to access the new location
New Location for Architecture Subcommittee wiki Page
TSC Architecture subcommittee
TSC subcommittee name:
Architecture Subcommittee (ARC)
Mailing list Moderators Stephen Terrill, Lingli Deng, ramki krishnan
Dublin Architecture Planning Meeting (Montreal, Oct 29-31)
JIRA project for issue prioritization: https://jira.onap.org/projects/ONAPARC/
Next Call
...
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
2nd week
...
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Task Forces:
<DRAFT> (Maybe this should be moved lower)
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:
...
Platform Maturity Requirements (S3P)
...
</DRAFT>
- Platform Maturity Requirements (S3P)
- Microservices Sub-team
- Architecture Tiger Team
- ONAP API Common Versioning Strategy (CVS) Guidelines
Meeting logistics:
Recurring meetings: Tuesdays, 1400-1600 UTC (starting June 13)
Participating in ARC meetings
Architecture subcommittee is contribution-driven
People can sign up for slots on the agenda
We will request people to develop proposals/presentations to discuss during meetings and via email
- Looking for input from the community, including EUAG
- Mid-release, we will work with PTLs to schedule a walk-through
...
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.
...
.
...
Input / driver for the architecture decision are business objectives / goals.
...
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.
Proposer:
...
Mailing list Moderators Stephen Terrill, Lingli Deng, ramki krishnan
Dublin Architecture Planning Meeting (Montreal, Oct 29-31)
JIRA project for issue prioritization: https://jira.onap.org/projects/ONAPARC/
Next Call
Anchor | ||||
---|---|---|---|---|
|
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
2nd week
Anchor | ||||
---|---|---|---|---|
|
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Followup
Items that are finished from an architecture point of view, but not delived into the the community:
Anchor | ||||
---|---|---|---|---|
|
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
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
Meeting Contributions:
The meeting input and conributions can be found here: ArchCom Contributions
Meeting logistics:
Recurring meetings: Tuesdays, 1400-1600 UTC (starting June 13)
Meeting Minutes:
The meeting minutes can be found here: ONAP Archecture Meeting Notes
Participating in ARC meetings
Architecture subcommittee is contribution-driven
People can sign up for slots on the agenda
We will request people to develop proposals/presentations to discuss during meetings and via email
- Looking for input from the community, including EUAG
- Mid-release, we will work with PTLs to schedule a walk-through