...
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.
Contacts
Ran Pollak, Michael O'Brien, Geora Barsky, Parvez Shaik,
see
Jira | ||||||
---|---|---|---|---|---|---|
|
More Useful info Regarding setting the ONAP Env:
- 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
...
Component
...
Number of running dockers
...
Docker Image availability
...
Robot “health-check”
...
JIRA
...
Workdarounds
...
All 19 VMs are up. 3 ONAP modules (VID, Policy, DCAE) failed Robot health check.
...
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
...
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
...
Up
...
PASS
Automated R1 Deployments Testing Healthcheck
Environment | Results |
---|---|
OOM | Every 2 hours |
HEAT | Pending |
Run every 2 hours
http://jenkins.onap.info/job/oom-cd/
Integration Test Blocking Issues
Gildas TSC Daily JIRA link https://lists.onap.org/pipermail/onap-tsc/2017-October/003766.html
JIRA Integration Open Issues (label=Integration)
Jira | ||||
---|---|---|---|---|
|
...
|
...
|
...
...
|
|
Blocking Issues for ONAP 1.1 R1 Integration - workarounds
Component Status (20171023 currently determining)
Unable to view/edit the service instance created to trigger VNF creation. Model-version-id is not available.
missing traversal, data-router, service, search-data-service, model-loader-service - fixed 20170907
Gremlinisbeingretired
AAI2
Up
PASS
Jira | ||||||
---|---|---|---|---|---|---|
|
basedonthefact aai2 used to have 3 containers and aai1 had 10 - OOM is currently bringing up all 13 together as a reference - fixed 20170907
APPC
Up &
Running
images
available
PASS
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
(added20170829) -
pending
Component | Docker download date | Number of running dockers | Docker Image availability | Kubernetis Robot “health-check” | Robot “health-check” | JIRA | Workdarounds |
vFirewall | |||||||
AAF | |||||||
AAI1 | |||||||
---|---|---|---|---|---|---|---|
AAI2 | |||||||
APPC | PASS | ||||||
CLAMP | PASS |
CLI | |||||||
CONSUL | |||||||
DCAE-CONT ROLLER |
---|
Up &
Running
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 | ||||||
---|---|---|---|---|---|---|
|
DCAE zldc<dc> vi cdap(3), pstg, coll |
Running
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
5 of 5 DCAE vms up in HEAT as of 20170907
10 of 10 DCAE containers up in OOM as of 20170913
DNS -SERVER
Up &
Running
PASS
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
VID
Up &
Running
FAIL
500 != 200
Jira | ||||||
---|---|---|---|---|---|---|
|
Still tracking
Jira | ||||||
---|---|---|---|---|---|---|
|
waiting on
FAIL | |||||||
DCAEGEN2 |
ROBOT
Up &
Running
SDC
Up
PASS
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
SDC distribution still failing 20170914
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
containershavenexus3 security secret issues
heattemplatepending
Jira | ||||||
---|---|---|---|---|---|---|
|
onap-discuss/2017-October/005378.html | |||||||
DNS -SERVER | |||||||
---|---|---|---|---|---|---|---|
LOG | |||||||
VID | PASS | ||||||
ROBOT | PASS | ||||||
SDC | PASS | ||||||
kube2msb (registrator) | |||||||
MSB | |||||||
MSO (heat) SO (k8s) |
Up &
Running
FAIL
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
PORTAL
Up &
Running
PASS
POLICY
Up &
Running
FAIL
Policyisnotcoming up from Portal in RS - verifying in K8S before a JIRA arrives
SDNC
Up & Running
FAIL
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
These two issues are related. BAD request response from SDNC. And SDNCdatabasedoesnthaverequiredtablecreated.
SDNC-77 is still an issue
MESSAGE -ROUTER
/
Jira | ||||||
---|---|---|---|---|---|---|
|
Integration Test Blocking Issues
...
PASS | |||||||
---|---|---|---|---|---|---|---|
PORTAL | PASS | ||||||
POLICY | PASS | ||||||
SDNC | PASS | ||||||
MESSAGE -ROUTER | |||||||
MULTICLOUD | |||||||
USECASE-UI | |||||||
VF-C | |||||||
VNFSDK |
...
JIRA Integration Closed Issues (label=Integration)
...