This Page will show the Daily status of the ONAP master branch with info such as issues/WA/relevant info regarding the ONAP components.
In this way we will be able to track the progress of all the Projects under ONAP, and to be able to solve issues faster while everyone is familiar with the latest issues and get info how to solve them with the info below.
For stabilizing the ONAP, we are considering vFW use case (Open loop) as a E2E flow. Below are the issues we are facing while we try to setup a stable environment to run the vFW use case successfully. Please observe the status info below regarding all ONAP (Heat based) components in (Openstack(float/no-float) or Rackspace?).
Component Status
Comp | Stack creation date | Docker download date | VM Deploy openstack | VM Deploy rackspace | Docker Image availability | Dockers open stack | Dockers rack space | Dockers K8S | Robot “health-check” | Occurence Date | JIRA | Comments |
INT / DEMO | 20170906 | 20170906 | All VMs are up. 3 ONAP modules (VID, Policy, DCAE) failed Robot health check. | 20170906 | - INT-149Getting issue details... STATUS - DCAEGEN2-95Getting issue details... STATUS - DCAEGEN2-69Getting issue details... STATUS - DCAEGEN2-88Getting issue details... STATUS - DCAEGEN2-89Getting issue details... STATUS - DCAEGEN2-71Getting issue details... STATUS - INT-178Getting issue details... STATUS | ./demo.sh init not working in OOM | ||||||
AAI1 | 20170809 | 20170824 | Up & | Up not functional | images available | ? | 5/10 20170903 | 10/10 | FAIL | 20170831 | ||
---|---|---|---|---|---|---|---|---|---|---|---|---|
AAI2 | 20170809 | 20170809 | ? | UP not functional | 1 image verified | ? | 1/3 20170903 | 3/3 | ? | 20170828 | based on the fact aai2 used to have 3 containers and aai1 had 10 - OOM is currently bringing up all 13 together as a reference | |
APPC | 20170809 | 20170809 | Up & | images available | 3/3 | PASS | ||||||
CLAMP | 20170903 | UP not functional | ? | 0/2 | pending OOM-12 | 20170903 | (added 20170829) - missing mariadb and clamp containers - it is possible CLAMP is still a WIP? | |||||
DCAE-CONT ROLLER | 20170809 | 20170809 | UP not functional | images available | 0/2 20170903 | n/a | FAIL | 20170903 | The groovy process runs for 45 then exists with orchestration running | |||
DCAE zldc<dc> vi cdap(3), pstg, coll | 20170828 | Missing | not all dockerized | n/a | n/a | 20170903 | The 5 DCAE orchestrated VMs are missing -verified my heat template (I see the new Clamp VM from 20170829) | |||||
DNS -SERVER | 20170809 | 20170809 | Up & | not dockerized | not required | PASS | ||||||
LOG | ||||||||||||
VID | 20170809 | 20170823 | Up & | images available | 2/2 | PASS | ||||||
ROBOT | 20170809 | 20170809 | Up & | images available | 1/1 | |||||||
SDC | 20170809 | 20170809 | Up | images available | 5/5 | 5/5 | FAIL (RS) | |||||
MSB | 4/4 | |||||||||||
MSO | 20170809 | 20170809 | Up & | images available | 2/2 | PASS | ||||||
PORTAL | 20170809 | 20170809 | Up & | images available | 3/3 | PASS | ||||||
POLICY | 20170809 | 20170809 | Up & | images available | 7/7 | PASS | Policy is not coming up from Portal in RS - verifying in K8S before a JIRA arrives | |||||
SDNC | 20170809 | 20170809 | Up & Running | images available | 4/4 | PASS | ||||||
MESSAGE -ROUTER | 20170809 | 20170809 | / | images available | 3/3 | / |
Below you can find more details regarding the latest issues:
Bug | Module | Issue | State | Defect Aging | Resolution/Comments |
SDC | OOM SDC vnc-portal requires a fix in the /etc/hosts file to launch SDC from portal | see workaround | |||
AAI1 AA2 DCAE CLAMP | When modifying the openstack or rackspace yaml templates - it would be good if integration testing results were published - as currently we have issues with the deployment of AAI1, AAI2, DCAE and CLAMP | Working | 20170829 | This is the first of many updates to the templates - each should require test results - so that users of the templates do not pickup a WIP version. DCAE status on https://lists.onap.org/pipermail/onap-discuss/2017-September/004273.html 20170907: discussed with DCAEGEN2 PTL - he is forwarding issue to the legacy DCAE team - we need more traction on DCAE issues related the older 1.1 architecture (as we currently have a gap running the vFirewall) | |
AAI | Error: model-version-id is not populated in A&AI during view/edit service instance | Open | 1 day | Posted mail to defect assignee James Forsyth seeking his inputs/alternates/re-assignment. Debug is in progress. | |
AAI-226 | AAI | AAIthrowsBadRequesterrortoMSO during service instance creation | Open | 3 day | This is working fine in 1.0 ONAP but not working in 1.1 ONAP. |
---|---|---|---|---|---|
- | AAI | Unable to deploy model loader docker in AAI | Closed | NA | Update the port numbers and restart the dockers |
AAI-190 | AAI | AAI-190 AAI was not able to communicate with ASDC. Unable to deploy model loader docker in AAI. | Closed | NA | 1.Stop and remove the old dockers,placenewdockersandupdatethejava.security file like above. 2.Update the port numbers and restart the dockers. |
- | Dockers are not present in the VMs after ONAP 1.1 deployment | Open | 4 days | It was working till last Wednesday 8/23/2017 (when we last checked.) | |
- | SO | Unable to connect to AAI due to SSL | Closed | NA | 1. Comment the certificate partinjava.security file resides in /etc/java-8-openjdk/security 2.Updatemso.asdc.json located in /etc/mso/config.d path. |
VID-38 | VID | Deploy button is not working in VID to distribute Model | Closed | NA | Ofir's work is completed. He closed the defect. |
VID | Unable to create a VNF in VID since Add VNF button is unresponsive in GUI. | Open | 2 days | Ofir Sonsino is working on this issue. Issue is reported with highest priority. | |
Demo | DNS zone configuration error causes BIND can't resolve DNS queries | In progress | 1 day | Submitted the change https://gerrit.onap.org/r/#/c/10713/ | |
VID | VID fails Robot health check. There is Java ClassNotFoundException in log | Open | 1 day | Reported with highest priority | |
POLICY | POLICY fails Robot health check | Open | 1 day | Reported with highest priority |
Testing Environment
Rackspace
key | value/link | notes |
---|---|---|
env | ||
yaml | ||
vFW | zip |
Openstack
key | value/link | notes |
---|---|---|
env | ||
yaml | ||
vFW | zip |
OOM
key | value/link | notes |
---|---|---|
env | ||
yaml | ||
vFW | zip | |
vFW env | ||
vFW yaml |
Deployment Status
ONAP Installation Strategy for Release A | OOM Deployment Status | Installing and Running the ONAP Demos
Openstack Deployment | Rackspace Deployment | OOM Deployment | Vagrant Deployment |
---|---|---|---|
20170906 All VMs are up 3 ONAP modules (VID, Policy and DCAE) fail on Robot health check | 20170903 with latest Clamp VM addition | 20170902 All up except in-review DCAE Console: http://test.onap.info:8880/ | vnc-portal: http://test.onap.info:30211/ SDC 404 issue - JIRA pending when I retest rackspace as well |
Historical Deployment Status
Links
TODO
TD1: Take the robot out of the human - we need to automate CI deployment and testing and minimize manual testing of the build status.