This Page will show the Daily status of the ONAP master branch with info such as issues/WA/relevant info regarding the ONAP components - latest update now on vCPE Integration Test Progress
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)asa E2E flow. Below are the issues we are facing while wetrytosetup a stable environment torunthevFW use case successfully. Please observe the status info below regarding all ONAP (Heat based) components in (Openstack(float/no-float) or Rackspace?).
see INT-106 - Getting issue details... STATUS
More Useful info Regarding setting the ONAP Env:
- Please note that you might have to update the existing private IPs to Public IPs of the VMs in Properties and hosts files to communicate with each other.
Blocking Issues for ONAP1.1 Integration
Rackspace 20170928 is failing on nexus3:10003 authentication - INT-235 - Getting issue details... STATUS
Component Status
Comp | Stack creation date | Docker download date | VM Deploy openstack (expecting 19) | VM Deploy rackspace (expecting 19) | Docker Image availability | Dockers open stack | Dockers rack space | Dockers K8S | Robot “health-check” | Occurence Date | JIRA | Comments |
| INT / DEMO | 20170906 | 20170906 | All 19 VMs are up. 3 ONAP modules (VID, Policy, DCAE) failed Robot health check. | 19 VMs are up | 20170906 | INT-149 - Getting issue details... STATUS DCAEGEN2-95 - Getting issue details... STATUS DCAEGEN2-98 - Getting issue details... STATUS DCAEGEN2-69 - Getting issue details... STATUS DCAEGEN2-88 - Getting issue details... STATUS DCAEGEN2-89 - Getting issue details... STATUS DCAEGEN2-71 - Getting issue details... STATUS INT-178 - Getting issue details... STATUS VID-59 - Getting issue details... STATUS POLICY-211 - Getting issue details... STATUS | We can proceed as far as creating a serviceforthevFirewall(the VF and VF-Module creation will need a fix. ./demo.shinitnotworkingin all deployment environments | |||||
| AAF | not in heat yet | 2/2 | ||||||||||
AAI1 | 20170809 | 20170824 | Up | Up | images available | 9/9 20170927 | 9/9 | PASS | 20170831 | Unable to view/edit the service instance created to trigger VNF creation. Model-version-id is not available. Rackspace missing traversal, data-router, service, search-data-service, model-loader-service - fixed 20170907 Gremlinisbeingretired | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
AAI2 | 20170809 | 20170809 | Up | Up | 1 image verified | 3/3 20170907 | PASS | 20170828 | AAI-237 - Getting issue details... STATUS | basedonthefact aai2 used to have 3 containers and aai1 had 10 - OOM is currently bringing up all 13 together as a reference - fixed 20170907 | ||
APPC | 20170809 | 20170809 | Up & | Up & Running | images available | 3/3 | PASS | CIMAN-32 - Getting issue details... STATUS | ||||
| CLAMP | 20170903 | Up & Running | ? | 2/2 | 2/2 | healthcheckneedsupdate | 20170903 | (added20170829) - pending | ||||
| CLI | 1/1 | |||||||||||
| CONSUL | 4/4 | |||||||||||
DCAE-CONT ROLLER | 20170809 | 20170809 | Up & | UP not functional | images available | 0/2 20170903 | 1/1 | FAIL Health check failed {u'service': u'cdap-helloworld', u'instance': u'iad4', u'status': u'UNDEPLOYED', u'healthTestStatus': u'YELLOW', u'healthTestMessageCode': u'Cluster not deployed'}
DCAEGEN2-71
-
Getting issue details...
STATUS
| 20170903 | |||
| DCAE zldc<dc> vi cdap(3), pstg, coll | 20170828 | 5/5 Up & Running | 5/5 Up & Running | not all dockerized | 9/9 | n/a | 20170903 | INT-131 - Getting issue details... STATUS DCAEGEN2-95 - Getting issue details... STATUS DCAEGEN2-98 - Getting issue details... STATUS DCAEGEN2-69 - Getting issue details... STATUS DCAEGEN2-89 - Getting issue details... STATUS DCAEGEN2-71 - Getting issue details... STATUS | 5 of 5 DCAE vms up in HEAT as of 20170907 10 of 10 DCAE containers up in OOM as of 20170913 | |||
| DCAEGEN2 | not in heat yet | |||||||||||
DNS -SERVER | 20170809 | 20170809 | Up & | Up & Running | not dockerized | notrequired | PASS | CIMAN-32 - Getting issue details... STATUS | ||||
| LOG | not in heat yet | 3/3 | LOG-71 - Getting issue details... STATUS | |||||||||
VID | 20170809 | 20170823 | Up & | Up & Running | images available | 2/2 | FAIL 500 != 200 | |||||
ROBOT | 20170809 | 20170809 | Up & | Up & Running | images available | 1/1 | ||||||
SDC | 20170809 | 20170809 | Up | images available | 5/5 | 5/5 | PASS | |||||
| kube2msb (registrator) | not in heat yet | 1/1 | ||||||||||
| MSB | not in heat yet | 4/4 | OOM-113 - Getting issue details... STATUS | containershavenexus3 security secret issues heattemplatepending INT-115 - Getting issue details... STATUS | ||||||||
MSO (heat) SO (k8s) | 20170809 | 20170809 | Up & | images available | 2/2 | FAIL | ||||||
PORTAL | 20170809 | 20170809 | Up & | Up & Running | images available | 3/3 | PASS | |||||
POLICY | 20170809 | 20170809 | Up & | Up & Running | images available | 7/7 | FAIL | Policyisnotcoming up from Portal in RS - verifying in K8S before a JIRA arrives | ||||
SDNC | 20170809 | 20170809 | Up & Running | images available | 4/4 | FAIL | These two issues are related. BAD request response from SDNC. And SDNCdatabasedoesnthaverequiredtablecreated. SDNC-77 is still an issue | |||||
MESSAGE -ROUTER | 20170809 | 20170809 | / | / | images available | 3/3 | / | |||||
| MULTICLOUD | 20170915 | not in heat yet | 4/4 | |||||||||
| USECASE-UI | not in heat yet | |||||||||||
| VF-C | not in heat yet | 7/13 | OOM-19 - Getting issue details... STATUS | |||||||||
| VNFSDK | not in heat yet | 2/2 |
Below you can find more details regarding the latest issues:
- Please update the below issues, organized according to A-Z.
Important issues:
JIRA Description JIRA Reported Date Deployment Platform ONAP Deployment Date
Comment
demo.sh init - failed with ONAP 1.1 - see the same manual SDC distribution failure 2017-09-07 K8S
Rackspace
2017-09-05
2017-09-07
vFirewall blocker
Partial workaround consists of running ./demo.sh distribute (subset of init) after inserting the "Demonstration" customer and associated region via postman PUTs
INT-197 - Getting issue details... STATUS
demo.sh init failed on Openstack ONAP1.1 2017-09-12 Openstack(WindRiver) +K8S (AAI related during SDC distribution - JIRA pending) 2017-09-06 different than INT-149
SO-103 - Getting issue details... STATUS
SO failed to add VNF to service instance 2017-08-30 Openstack(WindRiver) 2017-08-21
Other Issues:
| Bug | Module | Issue | State | Defect Aging | Work Around |
AAI-79 - Getting issue details... STATUS | AAI | Since july28 simple gets are returning 404 for v8 | Closed | 6 weeks | verified 20170907 rackspace |
| AAI | Error: model-version-id is not populated in A&AI during view/edit service instance | Closed | NA | Closed since it was working with API v11 UTF version. | |
AAI-226 - Getting issue details... STATUS | AAI | AAIthrowsBadRequesterrortoMSO during service instance creation | Closed | NA | |
|---|---|---|---|---|---|
| - | AAI | Unable to deploy model loader docker in AAI | Closed | NA | Update the port numbers and restart the dockers |
AAI-190 - Getting issue details... STATUS | 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. |
CIMAN-32 - Getting issue details... STATUS | - | Dockers are not present in the VMs after ONAP 1.1 deployment | Open | 8 days | We see that AAI and Robot dockers are not coming up. Work around for AAI:
|
DCAEGEN2-98 - Getting issue details... STATUS | DCAE | Until 20170907 the 5dcaeVMs were not up - fixed today | Closed | NA | |
SDNC-77 - Getting issue details... STATUS | SDNC | VF_MODULE_MODEL table is not present in SDNC database. | Open | 5 days | Raised with highest priority. This is a blocker because this functionality doesnt seem to be implemented so far. This blocks the use case progression. |
SDNC-80 - Getting issue details... STATUS | SDNC | Username and Password are wrongly configured in SDNC_controller_Container. | Open | 1 day | Work around: penecomp/sdnc/data/properties in docker sdnc_controller_container Open aaiclient.properties Change Username and password as: AAI |
| - | 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. |
SO-82 - Getting issue details... STATUS | SO | SDC model is not getting distributed into MSO and MSO is throwing an error | Open | 28 days | |
SO-100 - Getting issue details... STATUS | SO | org.communda.bpm throws null value exception while creating service instance through VID | Open | 20 days | Go to testlab_mariadb_1 docker Open DB using mysql -uroot –ppassword And populate the tables with data. |
SO-122 - Getting issue details... STATUS | SO | Model-version-id is not populated in A&AI during view/edit service instance due to version mismatch (v11) | Open | In MSO-server docker go to /etc/mso/config.d/mso.bpmn.urn.properties And change below aai version from v8 to v11 everywhere | |
SO-123 - Getting issue details... STATUS | SO | Bad request response from SDNC during VF module creation | Open | 1 day | in /etc/mso/config.d/mso.sdnc.properties, update the public IPs. |
VID-38 - Getting issue details... STATUS | VID | Deploy button is not working in VID to distribute Model | Closed | NA | |
| VID | Unable to create a VNF in VID since Add VNF button is unresponsive in GUI. | Open | 7 days | Ofir Sonsino is working on this issue. Issue is reported with highest priority. | |
VID-61 - Getting issue details... STATUS | VID | Model-version-id is not populated in AAI during view/edit service instance due to version mismatch (v11) | Open | 2 day | Update the verrsion from 8 to 11 in /tmp/vid/stage/WEB-INF/conf/ directory. |
INT-178 - Getting issue details... STATUS | Demo | DNS zone configurationerrorcausesBINDcan't resolve DNS queries | Change has been merged | 2017/09/06 | thechangehttps://gerrit.onap.org/r/#/c/10713/ |
VID-59 - Getting issue details... STATUS | VID | VID fails Robot health check. There is Java ClassNotFoundExceptioninlog | Open | 2017/09/06 | Reported with highest priority |
POLICY-211 - Getting issue details... STATUS | POLICY | POLICY fails Robot health check | Open | 2017/09/06 | Reported with highest priority |
Testing Environment
Rackspace
| key | value/link | notes |
|---|---|---|
| env | ||
| yaml |
Openstack
| key | value/link | notes |
|---|---|---|
| env | ||
| yaml |
OOM
| key | value/link | notes |
|---|---|---|
| env | ||
| yaml |
Deployment Status
ONAP Installation Strategy for Release A | OOM Deployment Status | Installing and Running the ONAP Demos
| OpenstackDeployment | Rackspace Deployment | OOM Deployment | Vagrant Deployment |
|---|---|---|---|
20170906 All VMs are up 3 ONAP modules (VID, Policy and DCAE)failonRobothealth check | 20170903 with latest Clamp VM addition | 20170913 All up including 10/10 DCAE |
Historical Docker Deployment Status
JIRA Integration Open Issues (label=Integration)
JIRA Integration Closed Issues (label=Integration)
Links
Rackspace is deprecated as of Oct 2017
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.