This Page will show the Daily status of the ONAP master branch with info such as issues/WA/relevant info regarding the ONAP components - latest update now on vCPE Integration Test Progress
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)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 - INT-106Getting issue details... STATUS
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)
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 | |||||||
DCAE zldc<dc> vi cdap(3), pstg, coll | FAIL | ||||||
DCAEGEN2 | https://lists.onap.org/pipermail/onap-discuss/2017-October/005378.html | ||||||
DNS -SERVER | |||||||
LOG | |||||||
VID | PASS | ||||||
ROBOT | PASS | ||||||
SDC | PASS | ||||||
kube2msb (registrator) | |||||||
MSB | |||||||
MSO (heat) SO (k8s) | PASS | ||||||
PORTAL | PASS | ||||||
POLICY | PASS | ||||||
SDNC | PASS | ||||||
MESSAGE -ROUTER | |||||||
MULTICLOUD | |||||||
USECASE-UI | |||||||
VF-C | |||||||
VNFSDK |
JIRA Integration Closed Issues (label=Integration)
10 Comments
Helen Chen
Ran, where did you run those testing? Could you please do it at ONAP community developer lab? Therefore, it is easier for developer to come over check the issue quickly.
Ran Pollak
Helen, Of course our goal is to run the tests in the ONAP community developer lab and to update this page regarding the results, for now the results are from our own environment.
Michael O'Brien
Ran, Hi, very good page and initiative. Could you post the exact details of your deployment environment (openstack version, heat template type (float/no-float), whether you are testing on Rackspace as well) - see heat/k8s and vf versions at Installing and Running the ONAP Demos#ONAPDeploymentEnvironments. We should also be able to post K8S status as well soon. I only ask this because ONAP as you know behaves differently in all 3 environments currently. This way we could get the best possible current reference environment posted.
We should correlate with the status for the heat and k8s deployment versions in
ONAP Installation Strategy for Release A | OOM Deployment Status
thank you
/michael
Josef Reisinger
If we talk about "master" branch.. what is the correct configuration for the heat template? I downloaded the latest (as it was for me this morning) HEAT onap_openstack_float dated 29.8.2017 and, after filling the "PUT YOUR xyz" HERE", created an ONAP stack. The results I could see are not in-line with the table above. Maybe the HEAT template does not represent the master branch as
in DCAE controller's cloud-init-output, I can see a
docker stop/waiting
docker start/running, process 10087
Cloning into 'dcae-startup-vm-controller'...
Already up-to-date.
./dcae_vm_init.sh: line 8: make: command not found
2017-08-31 10:34:11,552 - util.py[WARNING]: Failed running /var/lib/cloud/instance/scripts/part-001 [127]
2017-08-31 10:34:11,564 - cc_scripts_user.py[WARNING]: Failed to run module scripts-user (scripts in /var/lib/cloud/instance/scripts)
2017-08-31 10:34:11,565 - util.py[WARNING]: Running scripts-user (<module 'cloudinit.config.cc_scripts_user' from '/usr/lib/python2.7/dist-packages/cloudinit/config/cc_scripts_user.pyc'>) failed
Cloud-init v. 0.7.5 finished at Thu, 31 Aug 2017 10:34:11 +0000. Datasource DataSourceOpenStack [net,ver=2]. Up 219.71 seconds
After installing make, I could to the "make up" and DCAE started to do it's stuff.
In Portal's cloud-output I can see lots of error messages
The version(s) from the HEAT template are
nexus_url_snapshot: https://nexus.onap.org/content/repositories/snapshots
gitlab_branch: master
dcae_code_version: 1.1.0
Apparently, something went terribly wrong.... Any ideas/hits what it could ?
Josef Reisinger
Seems as if I had bad luck yesterday ... downloaded and executed a number of XXX_install scripts and, well, as far as I could see, the install worked (Except aai, which I am looking after right now)
Michael O'Brien
20170907: getting all 5 dcae vms now in rackspace - very nice
Michael O'Brien
DCAE 1.0 in ONAP 1.1 is deployment-ok for now - but in order to move forward with the vFirewall sanity - we need AAI stable (both the v8 and during our move to v11)
We need to address rest calls failing like the following
AAI-79 - Getting issue details... STATUS
and
https://{{aai_ip}}:8443/aai/v8/service-design-and-creation/models
used to work - Triaging the issue further and I'll advise
/michael
Michael O'Brien
To check your results of any robot command during vFirewall testing - everything is ready in OOM
Yogini and I needed the logs in OOM Kubernetes - they were already there and with a robot:robot auth
http://nnnn.onap.info:30209/logs/demo/InitDistribution/report.html
for example after a
root@ip-172-31-57-55:/dockerdata-nfs/onap/robot# ./demo-k8s.sh distribute
find your path to the logs by using for example
root@ip-172-31-57-55:/dockerdata-nfs/onap/robot# kubectl --namespace onap-robot exec -it robot-4251390084-lmdbb bash
root@robot-4251390084-lmdbb:/# ls /var/opt/OpenECOMP_ETE/html/logs/demo/InitD
InitDemo/ InitDistribution/
path is
http://nnnn.onap.info:30209/logs/demo/InitDemo/log.html#s1-s1-s1-s1-t1
Andrew Fenner
Hi,
I've had an issue with PORTAL on an install today.
Seems to be a mismatch between docker-compose.yml and where the properties files are copied to in the portal_vm_init.sh
portal_vm_init.sh copies them to /PROJECT/OpenSource/UbuntuEP/etc but docker-compose.yml is getting them from
${PROPS_DIR}/ECOMPSDKAPP/portal.properties
PROPS_DIR=/PROJECT/OpenSource/UbuntuEP/properties
see bug PORTAL-113 - Getting issue details... STATUS
/Andrew
Michael O'Brien
We need to consolidate this page - as in deleting content - I am guilty of this - deleting now