Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents


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

RanMichael O'BrienGeora BarskyParvez Basha Shaik


see 

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-106

More Useful info Regarding setting the ONAP Env:

...

Blocking Issues for ONAP1.1 Integration

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
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-149

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-95

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-98

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-69

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-88

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-89

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-71

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-178

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyVID-59

Jira Legacyserver

We can proceed as far as creating a serviceforthevFirewall(the VF and VF-Module creation will need a fix.

./demo.shinitnotworkingin all deployment environments

System JiraserverId4733707d-2057-3a0f-ae5e-4fd8aff50176keyPOLICY-211






AAF
not in heat yet






AAI1

20170824

Up

 images available

PASS

Jira LegacyserverSystem Jiracolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

serverId4733707d-2057-3a0f-ae5e-4fd8aff50176keyAAI-249

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-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







AAI2

20170809

Up

  1 image verified

PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-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
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCIMAN-32



CLAMP

?healthcheckneedsupdate

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-115

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyOOM-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
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-71


Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-88


DCAE zldc<dc> vi cdap(3), pstg, coll
5/5 Up &
Running
not all dockerizedn/a

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-131

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-95

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-98

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-69

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-89

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-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
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCIMAN-32


LOG
not in heat yet

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-71


VID

20170823

Up &
Running

 images available

FAIL

500 != 200

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyVID-57

Still tracking

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyVID-38

waiting on

https://gerrit.onap.org/r/#/c/17237/


ROBOT

20170809

Up &
Running

images available




SDC

20170809

Up

 images available

PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-268

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-280

SDC distribution still failing 20170914

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-334



kube2msb (registrator)
not in heat yet



MSB
not in heat yet

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyOOM-113

containershavenexus3 security secret issues

heattemplatepending

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-115

MSO (heat)

SO (k8s)

20170809

Up &
Running

images available

FAIL

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCIMAN-32

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-123

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-161

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-163

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-169

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-192


PORTAL

20170809Up &
Running

 images available

PASS







POLICY

20170809

Up &
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
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDNC-77

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDNC-102

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-235

These two issues are related. BAD request response from






SDNC

. And SDNCdatabasedoesnthaverequiredtablecreated.

SDNC-77 is still an issue







MESSAGE -ROUTER

20170809
/

images available

   /







MULTICLOUD
not in heat yet






USECASE-UI
not in heat yet






VF-C
not in heat yet

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyOOM-19


VNFSDK
not in heat yet



Integration Test Blocking Issues

...