Hi Gaurav, from what I see in the logs attached to the linked email, I am getting a bit confused. This URL=http://10.110.208.162:5000/v3/tokens looks like you are trying to talk to the V3 keystone API - which is not (yet) supported while this REQUEST BODY: {"auth":{"RAX-KSKEY:apiKeyCredentials":{"username":"admin","apiKey":"yyyyyyy"}}}
seem you are using the protocol to a Rackspace authentication server. and this "exception": "java.lang.IllegalArgumentException: !Absolute URI: null/servers", is a typical sign that the dcae_controller cannot talk to the Openstack keystone. I had a conversation about this topic earlier today, see https://lists.onap.org/pipermail/onap-discuss/2017-August/003663.html I can confirm that DCAE runs - i installed it on a 2nd environment yesterday, using docker 1.0 for all except DCAE and DCAE code 1.1 artifacts_version: 1.1.0-SNAPSHOT docker_version: 1.0-STAGING-latest gerrit_branch: master and I changed a line in the heat template for the dcae controller vm to use docker version 1.1 echo "__docker_version__" > /opt/config/docker_version.txt echo "1.1-STAGING-latest" > /opt/config/docker_version.txt Finally; Be patient. Be even more patient, I also saw three of the five docker container on collector and retried a couple of times. It seems as if the remaining two docker container are created _after_ pg & cdap are up. Mit freundlichen Grüßen / Kind regards Josef Reisinger From: "Gaurav Gupta (c)" <[email protected]> To: Ran Pollak <[email protected]> Cc: "[email protected]" <[email protected]> Date: 22.08.2017 14:37 Subject: Re: [onap-discuss] Stabilized the ONAP master branch Sent by: [email protected] Hello Ran We are trying to Deploy DACE on VIO . We have been successful in rest of the VM's and their dockers But have issues in Collector VM , PostGreSql and CDAP VM's . The situation is - on Collector VM - 3 dockers are up and on PostgreSql and CDAP VM - there is no dockers . our DCAE VM's have Floating and Private ip assigned to . from inside the VM We can reach to open internet . We have tried on both the Release Version and situation is same . Test.No Project Name Artifacts version docker version ONAPVersion/gerrit DCAE Version Observation 1 OPEN-ECOMP 1.1.0-SNAPSHOT 1.1-STAGING-latest master 1.1.0 DCAE's 5 Additional VMs are created. Collector VM downloads 2 Dockers but NO Containers start 2 onap 1.1.0-SNAPSHOT 1.0-STAGING-latest 1.0.0 1.1.0 DCAE's 5 Additional VMs are created. Collector VM downloads 6 Dockers and start 3 containers but the remaining dockers are not started Whatever we tried have been captured in the given link - . https://lists.onap.org/pipermail/onap-discuss/2017-July/002414.html . with best regards gaurav From: Ran Pollak <[email protected]> Sent: 22 August 2017 15:18 To: Gaurav Gupta (c) Cc: [email protected] Subject: FW: [onap-discuss] Stabilized the ONAP master branch Thanks Gaurav! We attend to have a different format for the daily mail that will include all the Components with the relevant issues, so we will have DCAE as well. Also if you can send me the relevant info regarding DCAE issues that will be very helpful ! BR, Ran Pollak From: [email protected] [ mailto:[email protected]] On Behalf Of Gaurav Gupta (c) Sent: Tuesday, August 22, 2017 06:35 To: Ran Pollak <[email protected]>; [email protected] Subject: Re: [onap-discuss] Stabilized the ONAP master branch Hi Ran Pollak amazing intiative . May I request you to include DACE Init issues also in your list of items to be resolved . Do let me know if you need any specifics of the issues . with best regards Gaurav From: [email protected] < [email protected]> on behalf of Ran Pollak < [email protected]> Sent: 21 August 2017 21:34 To: [email protected] Subject: [onap-discuss] Stabilized the ONAP master branch Hello ONAP Community Members, This is the first Daily status for the ONAP community regarding the status of the Master branch, this format will change into all the ONAP components with their issues/Status and we will add also info regarding ?health -check? scenarios. Part of our efforts to stabilize the 1.1 ONAP and certify Open loop, we are troubleshooting the issues and below is the issue we are now stuck at. We need more help on this since this is reported as high and still in Open state. Bug Module Issue State Defect Aging Resolution - AAI Unable to deploy model loader docker in AAI Closed NA Update the port numbers and restart the dockers - SO Unable to connect to AAI due to SSL Closed NA 1. Comment the certificate part in java.security file resides in /etc/java-8-openjdk/security 2. Update mso.asdc.json located in /etc/mso/config.d path. AAI-190 AAI AAI was not able to communicate with ASDC Closed NA Stop and remove the old dockers, place new dockers and update the java.security file like above. VID-38 VID Deploy button is not working in VID to distribute Model Open 10 days We have this issue reported and been followed up for more than ten days yet no update. Posted on community as well. Please, if you have something to add or ask please contact me. BR, Ran Pollak This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer _______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
