...
- Proposed name for the project:
DCAE - Proposed name for the top level repository name: dcaegen2
- For the 4Q17 release, one of major goals for DCAE is to evolve from the "old" controller that is currently in gerrit.onap.org with a new controller that follows the Common Controller Framework. The switch will maintain external (to other ONAP component) compatibility, but NOT backwards compatible internally. That is, subcomponents built for the old controller will not work with the new controller or vice versa. We are proposing to us a new top level naming “dcaegen2” for repos of subcomponents that are compatible with the new controller because it appears to be the cleanest approach to avoid confusion. The existing "dcae" top level still hosts repos of subcomponent projects that are compatible with the old controller. Eventually we will phase out the "dcae" tree but during the transition period both trees co-exist.
- Detailed list of proposed subprojects and their repos
DCAE Platform components:- DCAE Gen2 Controller
- Repo:
- dcaegen2/controller
- dcaegen2/controller/dispatcher
- dcaegen2/controller/inventory
- dcaegen2/controller/sch
- Repo:
- DCAE Gen2 Analytics Platform
- Repo:
- dcaegen2/apod/cdap
- Repo:
- DCAE Gen2 Persistent Storage
- Repo:
- dcaegen2/storage/pgaas
- dcaegen2/storage/esaas
- dcaegen2/storage/mdbaas
- Repo:
- DCAE Gen2 Utilities
- Repo:
- dcaegen2/utils
- dcaegen2/utils
- Repo:
- DCAE Gen2 VES Collector
- Repo:
- dcaegen2/collectors/ves
- Repo:
- DCAE Gen2 SNMP Trap Collector
- Repo:
- dcaegen2/collectors/snmptrap
- Repo:
- DCAE Gen2 Controller
- For the 4Q17 release, one of major goals for DCAE is to evolve from the "old" controller that is currently in gerrit.onap.org with a new controller that follows the Common Controller Framework. The switch will maintain external (to other ONAP component) compatibility, but NOT backwards compatible internally. That is, subcomponents built for the old controller will not work with the new controller or vice versa. We are proposing to us a new top level naming “dcaegen2” for repos of subcomponents that are compatible with the new controller because it appears to be the cleanest approach to avoid confusion. The existing "dcae" top level still hosts repos of subcomponent projects that are compatible with the old controller. Eventually we will phase out the "dcae" tree but during the transition period both trees co-exist.
...
The DCAE team proposes the following subprojects sub-projects/deliverables for 4Q17 R1 ONAP release.
...
- Controller:
- The new ONAP DCAE (gen2) controller follows the paradigm of Common Controller Framework for command and control. Hence the core function of the DCAE Controller code resides within the Common Controller Framework project. This project is for adaptation of the Common Controller Framework for DCAE use.
- Analytics platform:
- CDAP
- Storage: this group of projects provides data storage solutions for DCAE. The common usages include supporting DCAE's own functions; storage for data analytics; persistent data storage; etc. For this release we target three popular database technologies.
- Postgres as a Service (PGaaS)
- Elastic Search as a Service (ESaaS)
- MariaDB as a Service (MDBaaS)
- Utilities: this project contains various utility for DCAE development, testing, and operations.
...
- Demo: this project contains additional , scripts, and miscellaneous data and files for supporting demo use cases (depends on how
(Notes to DCAE team members: previously we also had DMaaP topics and Call Flow proposals. After consulting with other project teams, DMaaP topic related work is better suited under the DMaaP project; and call flow related work overlaps with the CLAMP team work. It would seem that these two do not need separate project proposals under DCAE. In addition, there were items related to code that is done outside of ONAP, e.g. collectd, VES agent. ONAP will use them but do they need separate projects/repos under DCAE?)
...
Primary Contact Person
John F. Murray (AT&T)
Lusheng Ji (AT&T)
Names, gerrit IDs, and company affiliations of the committers
(Note to DCAE team members: due to the scope and number of projects under DCAE, and number of willing committers may exceed Linux Foundation tradition, usually 2~3 committers per project, we may need to partition based on sub-projects/repos if being requested. Please specify the sub-projects/repos that you are interested in. )
Name Gerrit ID Company Email Time Zone DCAE Subproject Vijay Venkatesh Kumar vv770d AT&T New Jersey, USA
EST/EDTcollectors Tony Hansen AT&T tony@att.com New Jersey, USA
EST/EDT
storage Adityakar Jha Jio adityakar.jha@ril.com Mumbai, India UTC +5:30 ??? Aayush Bhatnagar Jio aayush.bhatnagar@ril.com Mumbai, India UTC +5:30 ??? Yog Vashisht Jio yog.vashisht@ril.com Mumbai, India UTC +5:30 ??? Guangrong Fu ZTE fu.guangrong@zte.com.cn Beijing, China. UTC +8 holmes Tang Peng ZTE tang.peng45@zte.com.cn Beijing, China. UTC +8 holmes Avinash S AvinashS Huawei avinash.s@huawei.com Bangalore, India UTC +5:30 ??? Alok Gupta AT&T ag1367@att.com collectors Lusheng Ji AT&T lji@research.att.com Yusuf Mirza IBM ymirza@ae.ibm.com Dubai, UAE. UTC +4 ???
Mike Hwang AT&T mhwang@research.att.com New Jersey, USA EST/EDT controller Yan Yang China Mobile yangyanyjy@chinamobile.com Beijing, China. UTC +8 collectors
Names and affiliations of any other contributors
Company
Name
AT&T
Alok Gupta
Jerry Robinson
Lusheng Ji
Tony Hansen Vijay Venkatesh Kumar Tech Mahindra
Sandeep Singh
Abhinav Singh
Gokul Singraju
Futurewei
Xin Miao
Deutsch Telcom
Mark Fiedler
Intel
Tim Verral
Orange
Vincent Colas
Olivier Augizeau
Pawel Pawlak Reliance Jio
Aayush Bhatnagar
Yog Vashishth Adityakar Jha Intel
Maryam Tahhan
Tim Verral
VMware Sumit Verdi Huawei Avinash S IBM Yusuf Mirza IBM David Parfett China Mobile Yuan Liu
- Project Roles (include RACI chart, if applicable)
...