Versions Compared

Old Version 148

changes.mady.by.user Michael O'Brien

Saved on

compared with

New Version 149

changes.mady.by.user Michael O'Brien

Saved on

Key

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

...

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 

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

...

Blocking Issues for ONAP1.1 Integration

Component Status

Occurence

Date201708282017080920170903201709032017090320170809201708092017080920170809

 CompComponent

Stack creation dateDocker download date

VM Deploy openstack

(expecting 19)Number of running dockers

Docker Image availability

Dockers open stack

Robot “health-check”

JIRA

Comments

Workdarounds

vFirewallINT / DEMO2017090620170906

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

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 serviceforthevFirewall(the VF and VF-Module creation will need a fix.

./demo.shinitnotworkingin all deployment environments

AAF
not in heat yet



AAI1

2017080920170824

Up

 images available

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

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

2017080920170809

Up

  1 image verified

PASS

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
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
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCIMAN-32


CLAMP

?healthcheckneedsupdate20170903

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

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

https://jira.onap.org/browse/CLAMP-47

(added20170829) -

pending

https://jira.onap.org/browse/CLAMP-47

CLI





CONSUL





DCAE-CONT

ROLLER

2017080920170809

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



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


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

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 in HEAT as of 20170907

10 of 10 DCAE containers up in OOM as of 20170913

DCAEGEN2
not in heat yet



DNS -SERVER

2017080920170809

Up &
Running

 not dockerized

PASS

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


LOG
not in heat yet

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


VID

20170823

Up &
Running

 images available

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

waiting on

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


ROBOT

2017080920170809

Up &
Running

images available




SDC

2017080920170809

Up

 images available

PASS

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

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

SDC distribution still failing 20170914

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



kube2msb (registrator)
not in heat yet



MSB
not in heat yet

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

containershavenexus3 security secret issues

heattemplatepending

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

MSO (heat)

SO (k8s)

2017080920170809

Up &
Running

images available

FAIL

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

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

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

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

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

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


PORTAL

20170809

Up &
Running

 images available

PASS



POLICY

2017080920170809

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

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

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

   /



MULTICLOUD20170915
not in heat yet



USECASE-UI
not in heat yet



VF-C
not in heat yet

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


VNFSDK
not in heat yet

Below you can find more details regarding the latest issues:

...

Important issues:

...

ONAP Deployment Date

Comment

...

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

because of

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

...

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

Verifying your ONAP Deployment#SDCDistributionfailure

...

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

...

different than INT-149

...

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

...

BugModuleIssueStateDefect AgingWork Around

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

AAISince july28 simple gets are returning 404 for v8Closed
6 weeksverified 20170907 rackspace

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

AAIError: model-version-id is not populated in A&AI during view/edit service instanceClosedNA
Closed since it was working with API v11 UTF version.

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

AAIAAIthrowsBadRequesterrortoMSO  during service instance creationClosed
NA-AAIUnable to deploy model loader docker in AAIClosedNAUpdate the port numbers and restart the dockers

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

AAIAAI-190   AAI was not able to communicate with ASDC.
    Unable to deploy model loader docker in AAI.ClosedNA1.Stop and remove the old dockers,placenewdockersandupdatethejava.security file like   above.
2.Update the port numbers and restart the dockers.

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

 - Dockers are not present in the VMs after ONAP 1.1 deployment Open8 days

We see that AAI and Robot dockers are not coming up.

Work around for AAI:

  1. Manually update the aai_instance file from aa1 to aai2 and run the VM_init script and AAI1 VM will have allthe dockers and we can start using it.
  2. And revert the change to aai1 and run the init script again and all the AAI1 dockers are also present.

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

DCAEUntil 20170907 the 5dcaeVMs were not up - fixed todayClosedNA

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

SDNCVF_MODULE_MODEL table is not present in SDNC database.Open5 daysRaised with highest priority. This is a blocker because this functionality doesnt seem to be implemented so far. This blocks the use case progression.

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

SDNCUsername and Password are wrongly configured in SDNC_controller_Container.Open1 day

Work around:

penecomp/sdnc/data/properties in docker sdnc_controller_container

Open aaiclient.properties

Change Username and password as: AAI

-SOUnable   to connect to AAI due to SSLClosedNA1. Comment the certificate partinjava.security file resides in   /etc/java-8-openjdk/security
2.Updatemso.asdc.json located in /etc/mso/config.d path.

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

SOSDC model is not getting distributed into MSO and MSO is throwing an errorOpen28 days

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

SOorg.communda.bpm throws null value exception while creating service instance through VIDOpen20 days

Go to testlab_mariadb_1 docker

Open DB using mysql -uroot –ppassword

And populate the tables with data.

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

SOModel-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

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

SOBad request response from SDNC during VF module creationOpen1 dayin /etc/mso/config.d/mso.sdnc.properties, update the public IPs.

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

VIDDeploy button is not working in VID to distribute ModelClosedNA

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

VIDUnable to create a VNF in VID since Add VNF button is unresponsive in GUI.Open7 days

Ofir Sonsino is working on this issue. Issue is reported with highest priority.

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

VIDModel-version-id is not populated in AAI during view/edit service instance due to version mismatch (v11)Open2 dayUpdate the verrsion from 8 to 11 in  /tmp/vid/stage/WEB-INF/conf/ directory.
JiraserverONAP





JIRA

...

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

...

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

...

Testing Environment

Openstack

...

ONAP Installation Strategy for Release A | OOM Deployment Status | Installing and Running the ONAP Demos

...

20170906 All VMs are up

3 ONAP modules (VID, Policy and DCAE)failonRobothealth check

...

20170913 All up including 10/10 DCAE

Historical Docker Deployment Status

JIRA Integration Open Issues (label=Integration)

...

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

...

Rackspace is deprecated as of Oct 2017

OOM Deployment Status

Heat and OOM JIRA Tracking

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.