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
...
For stabilizing the ONAP, we are considering vFW use case (Open loop) asa as a E2E flow. Below are the issues we are facing while wetrytosetup we try to setup a stable environment torunthevFW to run the vFW use case successfully. Please observe the status info below regarding all ONAP (Heat based) components in Openstack.
Contacts
Ran, Michael O'Brien, Geora Barsky, Parvez Basha Shaik,
see
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | INT-106 |
---|
|
More Useful info Regarding setting the ONAP Env:
...
Component Status
Component | Docker download date | Number of running dockers | Docker Image availability | Robot “health-check” | JIRA | Workdarounds |
vFirewall |
20170906 | All 19 VMs are up. 3 ONAP modules (VID, Policy, DCAE) failed Robot health check. | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | INT-149 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DCAEGEN2-95 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DCAEGEN2-98 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DCAEGEN2-69 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DCAEGEN2-88 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DCAEGEN2-89 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DCAEGEN2-71 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | INT-178 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | VID-59 |
---|
|
Jira Legacy |
serverWe can proceed as far as creating a serviceforthevFirewall(the VF and VF-Module creation will need a fix. ./demo.shinitnotworkingin all deployment environments | System Jira | serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | POLICY-211 |
---|
not in heat yet | 20170824 | | images available | PASS | Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | AAI-249 |
---|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | AAI-237 |
---|
|
Unable to view/edit the service instance created to trigger VNF creation. Model-version-id is not available. missing traversal, data-router, service, search-data-service, model-loader-service - fixed 20170907 Gremlinisbeingretired | 20170809 | | 1 image verified | PASS | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | AAI-237 |
---|
|
| basedonthefact aai2 used to have 3 containers and aai1 had 10 - OOM is currently bringing up all 13 together as a reference - fixed 20170907
Overall Deployment Architecture#Version1.1.0/R1 |
|
|
|
|
| |
APPC | 20170809 | Up & Running | images available | PASS |
---|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | CIMAN-32 |
---|
|
| |
|
---|
CLAMP |
|
| ? | healthcheckneedsupdate |
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | INT-115 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | OOM-12 |
---|
|
| (added20170829) - pending https://jira.onap.org/browse/CLAMP-47 |
CLI |
|
|
|
|
|
|
CONSUL |
|
|
|
|
|
|
DCAE-CONT ROLLER | 20170809 | Up & Running
| images available | 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'} Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DCAEGEN2-71 |
---|
|
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DCAEGEN2-88 |
---|
|
|
|
---|
DCAE zldc<dc> vi cdap(3), pstg, coll |
| 5/5 Up & Running
| not all dockerized | n/a | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | INT-131 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DCAEGEN2-95 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DCAEGEN2-98 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DCAEGEN2-69 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DCAEGEN2-89 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DCAEGEN2-71 |
---|
|
| 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 | Up & Running | not dockerized | PASS | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | CIMAN-32 |
---|
|
|
|
---|
LOG |
| not in heat yet |
|
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | LOG-71 |
---|
|
| |
VID | 20170823 | Up & Running | images available | FAIL 500 != 200 | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | VID-57 |
---|
|
Still tracking Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | VID-38 |
---|
|
waiting on https://gerrit.onap.org/r/#/c/17237/ | |
---|
ROBOT | 20170809 | Up & Running | images available |
| |
|
---|
SDC | 20170809 | Up
| images available | PASS | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SDC-268 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SDC-280 |
---|
|
SDC distribution still failing 20170914 Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SDC-334 |
---|
|
| |
---|
kube2msb (registrator) |
| not in heat yet |
|
|
|
|
MSB |
| not in heat yet |
|
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | OOM-113 |
---|
|
| containershavenexus3 security secret issues heattemplatepending Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | INT-115 |
---|
|
|
MSO (heat) SO (k8s) | 20170809 | Up & Running | images available | FAIL | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | CIMAN-32 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SO-123 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SO-161 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SO-163 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SO-169 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SO-192 |
---|
|
|
|
---|
PORTAL |
---|
20170809 | Up &
Running images available | PASS | 20170809Up & Running | images available | FAIL | Policyisnotcoming up from Portal in RS - verifying in K8S before a JIRA arrives | SDNC | 20170809 | Up & Running | images available | FAIL | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SDNC-77 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SDNC-102 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | INT-235 |
---|
|
| These two issues are related. BAD request response from . And SDNCdatabasedoesnthaverequiredtablecreated.SDNC-77 is still an issue
20170809
| /images available | / | not in heat yetnot in heat yet |
|
|
|
|
|
|
VF-C |
| not in heat yet |
|
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | OOM-19 |
---|
|
|
|
VNFSDK |
| not in heat yet |
|
|
|
|
...