TSC subcommittee name:
Architecture Subcommittee (ARC)
Mailing list Moderators Stephen terrill, Lingli Deng, Ramki Krishnan
Casablanca Release Architecture Planning Meeting (Vancouver)
JIRA project for issue prioritization: https://jira.onap.org/projects/ONAPARC/
Next Call
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
2nd week
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Task Forces:
- Platform Maturity Requirements (S3P)
- Microservices Sub-team
- Architecture Tiger Team
- ONAP API Common Versioning Strategy (CVS) Proposal
Meeting logistics:
Recurring meetings: Tuesdays, 1400-1600 UTC (starting June 13)
- Notes and materials 5-30-17
- Notes and materials 7-5-17
- Notes and materials 7-11-17
- Notes and Material 7-18-17
- Notes and Material 8-1-17
- Notes Material Recording 8-8-17
- Notes Material Recording 8-16-17
- Notes Recording 8-22-17
- August 29 Call
- September 5 Call
- September 19 Call
- October 3 Call
- October 10 Call
- October 24 Call
- October 31 Call
- November 7 Call
- November 14 Call
- November 21 Call
- November 28 Call
- December 5 Call
- January 2 Call
- January 9 Call
- January 16 Call
- January 23 Call
- January 30 Call
- February 13 Call
- February 20 Call
- February 27 Call
- March 6-7 Calls
- March 13 Call
- March 20 Call
- April 3 Call
- April 10 Call
- April 17 Call
- April 24 Call
- May 1 Call
- May 8 Call
- May 15 Call
- Casablanca Architecture Planning Meeting
- May 29 Call
- June 5 Call
- June 12 Call
- June 26 Call
- July 3 Call
- July 10 Call
- July 17 Call
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
- Mid-release, we will work with PTLs to schedule a walk-through
...
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 purpose:
The architecture subcommittee is responsible for developing and maintaining a functional ONAP architecture, guided by principles. This functional architecture helps inform 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 not make decisions regarding internal functioning of projects, but may identify synergies across projects.
The architecture subcommittee is advisory by nature, and not authoritative. It may provide advice to projects and to the TSC, such as by providing a forum to help resolve architectural questions that may arise.
...
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:
Chris Donley
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 Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
2nd week
| Anchor | ||||
|---|---|---|---|---|
|
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Followup
Items that are finished from an architecture point of view, but not delived into the the community:
| Anchor | ||||
|---|---|---|---|---|
|
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
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