CCSDK : Common Controller SDK Project Landing Page
<CCSDK> Documentation
Formal Documentation - End users and implementers |
Developer Documentation - Builders and contributors |
Key Information About CCSDK
Project Approval Date | Jun 9, 2017 |
Lifecycle Status | Mature |
Project Technical Lead (PTL) | @Dan Timoney |
Current Committers | @Dan Timoney @Brinda Santh Muthuramalingam @jh245g@att.com @gaurav.agrawal @Kapil Singal (Deactivated) @nullop |
Meeting Info | [ccsdk][sdnc] Team ONAP3, Wed UTC 13:00 / China 21:00 / Eastern 09:00 / Pacific 06:00 |
Meeting Minutes | |
Mailing- List | mailto:onap-discuss@lists.onap.org - include tag #ccsdk in Subject |
Repo(s) | https://gerrit.onap.org/r/admin/repos/q/filter:ccsdk |
JIRA* | |
Community Statistics |
Description:
This project provides a common set of reusable code that can be used across multiple controllers. The code could be used in other components but would not be an end solution for use cases by itself and would not be deployed on its own.
- 2 Formal Documentation - End users and implementers
- 3 Developer Documentation - Builders and contributors
- 3.1 Project Approval Date
- 3.2 Lifecycle Status
- 3.3 Project Technical Lead (PTL)
- 3.4 Current Committers
- 3.5 Meeting Info
- 3.6 Meeting Minutes
- 3.7 Mailing- List
- 3.8 Repo(s)
- 3.9 JIRA*
- 3.10 Community Statistics
- 4 Description:
- 5 Release Lifecycle Artifacts
- 6 Other Project Material
Release Lifecycle Artifacts
Honolulu
Guilin
Frankfurt
M1 Deliverables (Jira):
El Alto
M1 Deliverables (Jira):
M3/M4 Deliverables (Jira):
Dublin
Casablanca
Beijing
Amsterdam
Other Project Material
Meeting Minutes : CCSDK/SDNC Weekly Meeting Agenda/Minutes
Architecture Component Description : ARC Controller Component Description – Honolulu-R8
High & Highest Priority Open Bugs