Versions Compared

Old Version 126

changes.mady.by.user Yang Xu

Saved on

compared with

New Version 127

changes.mady.by.user Yang Xu

Saved on

Key

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

...

  1. 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


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

DescriptionJIRA Reported DateDeployment Platform

ONAP Deployment Date

Comments

INT / DEMO2017090620170906

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

19 VMs are up






20170906
Comment

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

SDNC

INT-

77VF_MODULE_MODEL table is not present in SDNC database.2017-09-09Openstack2017-09-09

149

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

Blocker

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

VID-57Unable to create a VNF in VID since Add VNF button is unresponsive in GUI.2017-09-06Openstack2017-09-09

DCAEGEN2-98

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

Blocker

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

INT-149because of

DCAEGEN2-88

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

SDC

DCAEGEN2-

334demo.sh init - failed with ONAP 1.1 - see the same manual SDC distribution failure2017-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

89

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

Verifying your ONAP Deployment#SDCDistributionfailure

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

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

INT-178

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

2017-08-21

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

INT-197demo.sh init failed on Openstack ONAP1.12017-09-12Openstack(WindRiver) +K8S (AAI related during SDC distribution - JIRA pending)2017-09-06

different than INT-149

Component Status

INT149DCAEGEN295

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

AAI1

2017080920170824

Up

Up  images available

10/10 20170907

10/10

(zookeeper,dmaap,kafkatoberemoved 20170908 to be 7/7)

PASS

20170831

 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
serverId

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId

425b2b0a-557c-3c0c-b515-579789cceedb
key

AAI-

249

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

AAI-

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

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

Up
  1 image verified
3/3 201709073/3

PASS

20170828 Jira

Jira

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

2017080920170809

Up &
Running

Up &
Running

images

available



3/3

PASS

DCAEGEN2-69


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

DCAEGEN2-88

CIMAN-32


CLAMP20170903

UP not functional?
0/2

pendingOOM-12


healthcheckneedsupdate20170903

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

DCAEGEN2

INT-

89

115

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

DCAEGEN2

OOM-

71

12

https://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

AAI1

2017080920170824

Up

Up  images available

10/10 20170907

10/10

(zookeeper,dmaap,kafkatoberemoved 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

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

Up

.onap.org/browse/CLAMP-47

(added20170829) -

pending

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

CLI






1/1



DCAE-CONT

ROLLER

2017080920170809

Up &
Running

UP not functional images available
0/2 201709031/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'}

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

20170903  1 image verified3/3 201709073/3

PASS

20170828

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

2017080920170809

Up &
Running

Up &
Running

images

available

3/3PASS


Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
key
CIMAN
DCAEGEN2-
32
88


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

9/9n/aCLAMP20170903UP not functional?0/2

pendingOOM-12

healthcheckneedsupdate20170903

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

115

131

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

OOM

DCAEGEN2-

12

95

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

(added20170829) -

pending

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

CLI1/1

DCAE-CONT

ROLLER

2017080920170809

Up &
Running

UP not functional images available0/2 201709031/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'}

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

20170903

5 of 5 DCAE vms up in HEAT as of 20170907

10 of 10 DCAE containers up in OOM as of 20170913

DNS -SERVER

2017080920170809

Up &
Running

Up &
Running not dockerized

notrequired

PASS


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

DCAEGEN2-88DCAE zldc<dc> vi cdap(3), pstg, coll201708285/5

CIMAN-32


LOG

not in heat yet



3/3



VID

2017080920170823

Up &
Running

5/5 Up &
Runningnot all dockerized9/9n/a20170903 images available

2/2

FAIL

500 != 200


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

INT-131

VID-57

Still tracking

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

DCAEGEN2-

VID-38


ROBOT

20170809
20170809

Up &
Running

Up &
Runningimages available



1/1





SDC

20170809
20170809

Up


 images available
5/55/5

PASS

95


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

DCAEGEN2

SDC-

98

268

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

DCAEGEN2-69

SDC-280

SDC distribution still failing 20170914

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

DCAEGEN2-89

SDC-334



MSB

notinheatyet



0/0

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

DNS -SERVER

2017080920170809

Up &
Running

Up &
Running not dockerizednotrequiredPASS

keyOOM-113

containershavenexus3 security secret issues

heattemplatepending

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

CIMAN

INT-

32

115

MSO

LOGnot in heat yet3/3VID20170809
2017080920170823

Up &
Running

Up &
Running images available

2/2

FAIL

500 != 200

PASS


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

Still tracking

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

CIMAN-32


PORTAL

20170809
20170809

Up &
Running

Up &
Running images available

3/3

PASS




POLICY

ROBOT

20170809
20170809

Up &
Running

Up &
Running images available1/1SDC

7/7

FAIL



Policyisnotcoming up from Portal in RS - verifying in K8S before a JIRA arrives

SDNC

20170809
20170809

Up & Running

Up &
Running images available5/55/5

4/4

PASS


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

SDC

SDNC-

268

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

SDC-280

SDC distribution still failing 20170914

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

MSBnotinheatyet0/0

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

containershavenexus3 security secret issues

heattemplatepending

SDNC-77

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

   /




MULTICLOUD20170915





2/2



USECASE-UI












Below you can find more details regarding the latest issues:

  • Please update the below issues, organized according to A-Z.

    Important issues:

    JIRADescriptionJIRA Reported DateDeployment Platform

    ONAP Deployment Date

    Comment


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

...

  • 149

    because of

...

MSO

...

Up &
Running

...

  • Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    key

...

  • SDC-

...

PORTAL

...

Up &
Running

...

PASS

...

POLICY

...

Up &
Running

...

FAIL

...

Policyisnotcoming up from Portal in RS - verifying in K8S before a JIRA arrives

  • 334

    		demo.sh init - failed with ONAP 1.1 - see the same manual SDC distribution failure2017-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

    Verifying your ONAP Deployment#SDCDistributionfailure

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

    		demo.sh init failed on Openstack ONAP1.12017-09-12Openstack(WindRiver) +K8S (AAI related during SDC distribution - JIRA pending)2017-09-06

    different than INT-149

...

SDNC

...

Up & Running

...

PASS

...

  • Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    key

...

  • SO-

...

These two issues are related. BAD request response from SDNC. And SDNCdatabasedoesnthaverequiredtablecreated.

SDNC-77 is still an issue

...

MESSAGE -ROUTER

...

   /

  • 103

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


    Other Issues:

...

Below you can find more details regarding the latest issues:

  • Please update the below issues, organized according to A-Z.
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.

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

DemoDNS zone configurationerrorcausesBINDcan't resolve DNS queriesChange has been merged2017/09/06thechangehttps://gerrit.onap.org/r/#/c/10713/

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

VIDVID fails Robot health check. There is Java ClassNotFoundExceptioninlogOpen2017/09/06Reported with highest priority

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

POLICYPOLICY fails Robot health checkOpen2017/09/06Reported with highest priority

...