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

Compare with Current View Page History

« Previous Version 48 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

 Components

Stack creation dateDocker download date

VM Deploy openstack

VM Deploy rackspace

Docker Image availability 

Containers openstack

Containers rackspace

Containers Kubernetes

Robot “health-check”

Occurence

Date

JIRA

Comments

AAI1

8/9/20178/24/2017

Up & Running

Up not functional images available?

10/10 20170829

5/10 20170903

10/10

FAIL

20170831

AAI-249 - Getting issue details... STATUS

Unable to view/edit the service instance created to trigger VNF creation. Model-version-id is not available.

AAI2

8/9/2017

?

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

8/9/20178/9/2017

Up & Running


images

available



3/3

PASS


CIMAN-32 - Getting issue details... STATUS


CLAMP9/3/2017

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

8/9/20178/9/2017


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, coll8/28/2017

Missingnot all dockerized

n/an/a20170903

INT-131 - Getting issue details... STATUS

The 5 DCAE orchestrated VMs are missing -verified my heat template (I see the new Clamp VM from 20170829)

DNS-SERVER

8/9/20178/9/2017

Up & Running


 images available

not required

PASS


CIMAN-32 - Getting issue details... STATUS


VID

8/9/20178/23/2017

Up & Running


 images available

2/2

PASS


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


ROBOT

8/9/20178/9/2017

Up & Running


images available



1/1





SDC

8/9/20178/9/2017

Up & Running


 images available

5/5

PASS



SDC is 404 as of 20170902 - JIRA pending

MSO

8/9/20178/9/2017

Up & Running


images available

2/2

PASS


CIMAN-32 - Getting issue details... STATUS


PORTAL

8/9/20178/9/2017

Up & Running


 images available

3/3

PASS




POLICY

8/9/20178/9/2017

Up & Running


 images available

7/7

PASS




SDNC

8/9/20178/9/2017

Up & Running


 images available

4/4

PASS




MESSAGE-ROUTER

8/9/20178/9/2017/
images available

3/3

   /





Below you can find more details regarding the latest issues:


BugModuleIssueStateDefect AgingResolution/Comments

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.


Deployment Status

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

Openstack DeploymentRackspace DeploymentOOM DeploymentVagrant Deployment

20170903 with latest Clamp VM addition

20170902 All up except in-review DCAE

http://dev.onap.info:30211/

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



Historical Deployment Status









  • No labels