Versions Compared

Key

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

...

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

VM Deploy rackspace

Docker Image availability

Containers openstack

Containers rackspace

Containers Kubernetes
Dockers open stack

Dockers rack space

Dockers K8S

Robot “health-check”

Occurence

Date

JIRA

Comments

AAI1

2017080920170824

Up &
Running

Up not functional images available?

10/10 20170829

5/10 20170903

10/10

FAIL

20170831

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

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

AAI2

2017080920170809

?

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

?

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

Overall Deployment Architecture#Version1.1.0/R1

APPC

2017080920170809

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



20170903

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 not functional images available
0/2 20170903n/a

FAIL

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

Missingnot all dockerized

n/an/a20170903

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

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

DNS -SERVER

2017080920170809

Up &
Running


 images available

not required

PASS


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


VID

2017080920170823

Up &
Running


 images available

2/2

PASS


Still tracking

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


ROBOT

20170809
20170809

Up &
Running


images available



1/1





SDC

20170809
20170809

Up &
Running


 images available

5/5

PASS



SDC is 404 as of 20170902 - JIRA pending

MSO

20170809
20170809

Up &
Running


images available

2/2

PASS


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


PORTAL

20170809
20170809

Up &
Running


 images available

3/3

PASS




POLICY

20170809
20170809

Up &
Running


 images available

7/7

PASS




SDNC

20170809
20170809

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:

...