Versions Compared

Key

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

...

Top Blocking Issues for ONAP1.1


JIRADescriptionJIRA Reported DateDeployment Platform

ONAP Deployment Date

Comment


Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyINT-149

demo.sh init - failed with ONAP 1.12017-09-07K8S2017-09-05

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVID-59

VID Fails Robot Health Check

2017-09-07Openstack (WindRiver)2017-09-06

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyPOLICY-211

Policy fails Robot health check

2017-09-07Openstack (WindRiver)2017-09-06

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-103

SO failed to add VNF to service instance2017-08-30Openstack (WindRiver)2017-08-21


JIRA Integration Open Issues (label=Integration)

Jira
serverONAP JIRA
columnskey,summary,created,updated,assignee,reporter,priority,status
maximumIssues40
jqlQueryfilter="integration bugs open"
serverId425b2b0a-557c-3c0c-b515-579789cceedb

Component Status

 Comp

Stack creation dateDocker 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 / DEMO2017090620170906

All 19 VMs are up. 3 ONAP modules (VID, Policy, DCAE) failed Robot health check.

19 VMs are up






20170906

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyINT-149

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-95

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-98

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-69

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-88

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-89

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-71

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyINT-178

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVID-59

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyPOLICY-211

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

./demo.sh init not working in all deployment environments

AAI1

2017080920170824

Up

Up  images available

10/10 20170907

10/10

(zookeeper, dmaap, kafka to be removed 20170908 to be 7/7)

PASS

20170831

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyAAI-249

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyAAI-237

AAI-79 is 6 weeks old

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyAAI-79

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

Gremlin is being retired

AAI2

2017080920170809

Up

Up
  1 image verified
3/3 201709073/3

PASS

20170828

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyAAI-237

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 - fixed 20170907

Overall Deployment Architecture#Version1.1.0/R1

APPC

2017080920170809

Up &
Running

Up &
Running

images

available



3/3

PASS


Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCIMAN-32


CLAMP20170903

UP not functional?
0/2

pending OOM-12


healthcheck needs update20170903

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyINT-115

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOOM-12

(added 20170829) - missing mariadb and clamp containers - it is possible CLAMP is still a WIP?

DCAE-CONT

ROLLER

2017080920170809

Up &
Running

UP not functional images available
0/2 20170903n/a

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
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-71

20170903


Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-88

The groovy process runs for 45 then exists with orchestration running

DCAE zldc<dc> vi cdap(3), pstg, coll20170828
5/5 Up &
Running
5/4 Up &
Running
not all dockerized

n/an/a20170903

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyINT-131

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-95

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-98

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-69

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-89

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-71

5 of 5 DCAE vms up as of 20170907

DNS -SERVER

2017080920170809

Up &
Running

Up &
Running
 not dockerized

not required

PASS


Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCIMAN-32


LOG

not in heat yet







pending merge

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOOM-110

VID

2017080920170823

Up &
Running

Up &
Running
 images available

2/2

FAIL

500 != 200


Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVID-57

Still tracking

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVID-38


ROBOT

20170809
20170809

Up &
Running

Up &
Running
images available



1/1





SDC

20170809
20170809

Up


 images available
5/55/5

PASS


Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-268

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-280

OOM workaround:

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOOM-282

ON RS I get a 503

healthcheck shows 500

for OOM fix will be in

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOOM-276

MSB

not in heat yet



4/4

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOOM-113

containers have nexus3 security secret issues

heat template pending

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyINT-115

MSO

20170809
20170809

Up &
Running

Up &
Running
images available

2/2

PASS


Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCIMAN-32


PORTAL

20170809
20170809

Up &
Running

Up &
Running
 images available

3/3

PASS




POLICY

20170809
20170809

Up &
Running

Up &
Running
 images available

7/7

FAIL



Policy is not coming up from Portal in RS - verifying in K8S before a JIRA arrives

SDNC

20170809
20170809

Up & Running

Up &
Running
 images available

4/4

PASS


Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDNC-78
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDNC-77

These two issues are related. BAD request response from SDNC. And SDNC database doesnt have required table created.

MESSAGE -ROUTER

20170809
20170809
//images available

3/3

   /




...