...
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(float/no-float) or Rackspace?)..
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
Rackspace 20170928 is failing on nexus3:10003 authentication - Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key INT-235
Component Status
...
Comp
...
VM Deploy openstack
(expecting 19)
...
VM Deploy rackspace
(expecting 19)
...
Docker Image availability
...
Dockers rack space
...
Robot “health-check”
...
Occurence
Date
...
JIRA
...
Comments
...
All 19 VMs are up. 3 ONAP modules (VID, Policy, DCAE) failed Robot health check.
...
19 VMs are up
...
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
...
9/9 20170927
9/9
...
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)
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 |
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
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
Running
images
available
PASS
Jira | ||||||
---|---|---|---|---|---|---|
|
Running
2/2
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
(added20170829) -
pending
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
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
Running
PASS
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
VID
Up &
Running
Running
FAIL
500 != 200
FAIL | |||||||
DCAEGEN2 |
Jira | ||||||
---|---|---|---|---|---|---|
|
Still tracking
Jira | ||||||
---|---|---|---|---|---|---|
|
waiting on
https://gerritROBOT
Up &
Running
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
Running
PASS
POLICY
Up &
Running
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 | ||||||
---|---|---|---|---|---|---|
|
Below you can find more details regarding the latest issues:
...
Important issues:
...
ONAP Deployment Date
Comment
...
Jira | ||||||
---|---|---|---|---|---|---|
|
because of
Jira | ||||||
---|---|---|---|---|---|---|
|
...
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 | ||||||
---|---|---|---|---|---|---|
|
...
different than INT-149
...
Jira | ||||||
---|---|---|---|---|---|---|
|
...
Jira | ||||||
---|---|---|---|---|---|---|
|
...
...
...
Jira | ||||||
---|---|---|---|---|---|---|
|
...
Jira | ||||||
---|---|---|---|---|---|---|
|
...
Jira | ||||||
---|---|---|---|---|---|---|
|
...
We see that AAI and Robot dockers are not coming up.
Work around for AAI:
- 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.
- And revert the change to aai1 and run the init script again and all the AAI1 dockers are also present.
...
Jira | ||||||
---|---|---|---|---|---|---|
|
...
Jira | ||||||
---|---|---|---|---|---|---|
|
...
Jira | ||||||
---|---|---|---|---|---|---|
|
...
Work around:
penecomp/sdnc/data/properties in docker sdnc_controller_container
Open aaiclient.properties
Change Username and password as: AAI
...
Jira | ||||||
---|---|---|---|---|---|---|
|
...
Jira | ||||||
---|---|---|---|---|---|---|
|
...
Go to testlab_mariadb_1 docker
Open DB using mysql -uroot –ppassword
And populate the tables with data.
...
Jira | ||||||
---|---|---|---|---|---|---|
|
...
In MSO-server docker go to
/etc/mso/config.d/mso.bpmn.urn.properties
And change below aai version from v8 to v11 everywhere
PASS | |||||||
---|---|---|---|---|---|---|---|
PORTAL | PASS | ||||||
POLICY | PASS | ||||||
SDNC | PASS | ||||||
MESSAGE -ROUTER | |||||||
MULTICLOUD | |||||||
USECASE-UI | |||||||
VF-C | |||||||
VNFSDK |
JIRA Integration
...
Jira | ||||||
---|---|---|---|---|---|---|
|
...
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
...
...
Ofir Sonsino is working on this issue. Issue is reported with highest priority.
...
Jira | ||||||
---|---|---|---|---|---|---|
|
...
Jira | ||||||
---|---|---|---|---|---|---|
|
...
Jira | ||||||
---|---|---|---|---|---|---|
|
...
Jira | ||||||
---|---|---|---|---|---|---|
|
...
Testing Environment
Rackspace
...
Openstack
...
OOM
...
Deployment Status
ONAP Installation Strategy for Release A | OOM Deployment Status | Installing and Running the ONAP Demos
...
20170906 All VMs are up
3 ONAP modules (VID, Policy and DCAE)failonRobothealth check
...
20170913 All up including 10/10 DCAE
Historical Docker Deployment Status
JIRA Integration Open Issues (label=Integration)
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
JIRA Integration Closed Issues (label=Integration)
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
...
Rackspace is deprecated as of Oct 2017
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.