ONAP Installation Strategy for Release A
Two alternatives:
Using OOM (K8-based strategy), which was approved in the past face-to-face meeting and will be the standard/preferred way in the long run;
Using Heat template, which is what we did for OpenECOMP.
(D: Done | C: Committed, when? | NC: Not Committed)
Project Name | Needed by UC | Heat Template | OOM | Project Tech. Lead | Notes |
|---|---|---|---|---|---|
Yes | D | D | @James Forsyth | Complete | |
No |
| C | @Ramprasad Koya | Not Release A | |
Yes | D | D | @Randa Maher |
| |
Yes | D | D | @Gervais-Martial Ngueko |
| |
Yes | N/A | N/A | @Dan Timoney | As a library, CCSDK is not installed separately but rather is installed as part of the client project(s) that uses it (e.g. APPC, SDNC) | |
Yes | Gen 1 - D Gen 2 - D | D D | @Lusheng Ji | DCAE GEN 2 is in Heat, but the DCAE team is still solving authentication issues that prevent the controller container to come up | |
Yes | D | D | @Ramprasad Koya |
| |
Yes | N/A | N/A | @gg2147@att.com |
| |
No |
|
| @Andy Mayer |
| |
Yes | N/A | N/A | @Guangrong Fu | Managed by DCAE | |
Yes | N/A | N/A | @Helen Chen |
| |
No | NC R2? | C | @Luke Parker | (OOM ) - 3 containers committed (some filebeat config pending) | |
Yes | D | D | @Former user (Deleted) |
| |
No | C |
| @Hui Deng |
| |
Yes | D | D | @Former user (Deleted) | Patch | |
No | D | D | @Former user (Deleted) |
| |
Yes? | N/A | N/A | @David S |
| |
No | N/A | N/A | @Sarat Puthenpura | Not in Release A | |
No | N/A | N/A | @Nermin Mohamed |
| |
Yes | D |
| @Tao Shen | Mike to work on this one | |
Yes | D | D | @Pamela Dragosh | Complete for 1.1 | |
Yes | D | D | @Manoop Talasila |
| |
Yes | D | D | @Dan Timoney |
| |
Yes | D | D | @Michael Lando | SDC will use the heat based deployment For R1 | |
Yes | D | D | @Seshu Kumar Mudiganti |
| |
Yes | D | D
| @Yan Yang |
| |
Yes | D | D | @Amichai Hemli |
| |
Yes | D | D | @Chris Donley |
| |
No | N/A | N/A | @Steven wright | Documentation | |
No | N/A | N/A | @Erik Sundelof | Not in Release A |