You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 87 Next »

This Page will show the Daily status of the ONAP master branch with info such as issues/WA/relevant info regarding the ONAP components.

In this way we will be able to track the progress of all the Projects under ONAP, and to be able to solve issues faster while everyone is familiar with the latest issues and get info how to solve them with the info below.

For stabilizing the ONAP, we are considering vFW use case (Open loop) as a E2E flow. Below are the issues we are facing while we try to setup a stable environment to run the vFW use case successfully. Please observe the status info below regarding all ONAP (Heat based) components in (Openstack(float/no-float) or Rackspace?). 

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

INT-149 - Getting issue details... STATUS

DCAEGEN2-95 - Getting issue details... STATUS

DCAEGEN2-98 - Getting issue details... STATUS

DCAEGEN2-69 - Getting issue details... STATUS

DCAEGEN2-88 - Getting issue details... STATUS

DCAEGEN2-89 - Getting issue details... STATUS

DCAEGEN2-71 - Getting issue details... STATUS

INT-178 - Getting issue details... STATUS

VID-59 - Getting issue details... STATUS

POLICY-211 - Getting issue details... STATUS

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 &
Running

Up not functional images available?

5/10 20170903

10/10

FAIL

20170831

AAI-249 - Getting issue details... STATUS

AAI-237 - Getting issue details... STATUS

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

AAI2

2017080920170809

?

UP not functional  1 image verified?1/3 201709033/3

?

20170828

AAI-237 - Getting issue details... STATUS

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

Overall Deployment Architecture#Version1.1.0/R1

APPC

2017080920170809

Up &
Running

Up &
Running

images

available



3/3

PASS


CIMAN-32 - Getting issue details... STATUS


CLAMP20170903

UP not functional?
0/2

pending OOM-12



20170903

INT-115 - Getting issue details... STATUS

OOM-12 - Getting issue details... STATUS

(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

20170903


DCAEGEN2-88 - Getting issue details... STATUS

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

INT-131 - Getting issue details... STATUS

DCAEGEN2-95 - Getting issue details... STATUS

DCAEGEN2-98 - Getting issue details... STATUS

DCAEGEN2-69 - Getting issue details... STATUS

DCAEGEN2-89 - Getting issue details... STATUS

DCAEGEN2-71 - Getting issue details... STATUS

5 of 5 DCAE vms up as of 20170907

DNS -SERVER

2017080920170809

Up &
Running

Up &
Running		 not dockerized

not required

PASS


CIMAN-32 - Getting issue details... STATUS


LOG

not in heat yet







pending merge

OOM-110 - Getting issue details... STATUS

VID

2017080920170823

Up &
Running

Up &
Running		 images available

2/2

PASS


VID-57 - Getting issue details... STATUS

Still tracking VID-38 - Getting issue details... STATUS


ROBOT

20170809
20170809

Up &
Running

Up &
Running		images available



1/1





SDC

20170809
20170809

Up


 images available
5/55/5

FAIL (RS)


SDC-268 - Getting issue details... STATUS

SDC-280 - Getting issue details... STATUS

OOM workaround: OOM-282 - Getting issue details... STATUS

ON RS I get a 503

healthcheck shows 500

for OOM fix will be in OOM-276 - Getting issue details... STATUS

MSB

not in heat yet



4/4

OOM-113 - Getting issue details... STATUS

containers have nexus3 security secret issues

heat template pending

INT-115 - Getting issue details... STATUS

MSO

20170809
20170809

Up &
Running

Up &
Running		images available

2/2

PASS


CIMAN-32 - Getting issue details... STATUS


PORTAL

20170809
20170809

Up &
Running

Up &
Running		 images available

3/3

PASS




POLICY

20170809
20170809

Up &
Running

Up &
Running		 images available

7/7

PASS



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




MESSAGE -ROUTER

20170809
20170809
//images available

3/3

   /





Below you can find more details regarding the latest issues:


BugModuleIssueStateDefect AgingResolution/Comments

DCAEGEN2-98 - Getting issue details... STATUS

DCAE

Until 20170907 the 5 dcae VMs were not up - fixed todayClosed

AAI-249

AAIError: model-version-id is not populated in A&AI during view/edit service instanceOpen1 day

Posted mail to defect assignee James Forsyth seeking his inputs/alternates/re-assignment. Debug is in progress.

AAI-226AAIAAIthrowsBadRequesterrortoMSO  during service instance creationOpen3  dayThis   is working fine in 1.0 ONAP but not working in 1.1 ONAP.
-AAIUnable   to deploy model loader docker in AAIClosedNAUpdate   the port numbers and restart the dockers
AAI-190AAIAAI-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.

CIMAN-32

 - Dockers are not present in the VMs after ONAP 1.1 deployment Open 4 days It was working till last Wednesday 8/23/2017 (when we last checked.)
-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.
VID-38VIDDeploy   button is not working in VID to distribute ModelClosedNAOfir's work is completed. He closed the defect.

VID-57

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

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

INT-178 - Getting issue details... STATUS

DemoDNS zone configuration error causes BIND can't resolve DNS queriesChange has been merged2017/09/06the change https://gerrit.onap.org/r/#/c/10713/

VID-59 - Getting issue details... STATUS

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

POLICY-211 - Getting issue details... STATUS

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


Testing Environment

Rackspace

keyvalue/linknotes
env

yaml

vFWzip


Openstack

keyvalue/linknotes
env

yaml

vFWzip

OOM

keyvalue/linknotes
env

yaml

vFWzip
vFW env

vFW yaml

Deployment Status

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

Openstack DeploymentRackspace DeploymentOOM DeploymentVagrant Deployment

20170906 All VMs are up

3 ONAP modules (VID, Policy and DCAE) fail on Robot health check

20170903 with latest Clamp VM addition

20170902 All up except in-review DCAE

Console: http://test.onap.info:8880/ | vnc-portal: http://test.onap.info:30211/

SDC 404 issue - JIRA pending when I retest rackspace as well



Historical Deployment Status



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.






  • No labels