How to Docker setup on Single VM HEAT Deployment

This guide describes the HEAT installation of A&AI

Prerequisites

The following software is needed in order to do HEAT installation of A&AI

  • docker

  • docker-compose

  • bash

Step-by-step guide

  1. You would need to have root access to the vm



  2. sudo su - root



  3.  Add/Update the /etc/hosts file to add the following entry:

    127.0.0.1 aai.hbase.simpledemo.onap.org





  4. cd /opt











  5. In deploy_vm1.sh comment out the lines 89-94 which should be an if statement checking for the /opt/message-router folder

  6. Create a directory called /opt/config





  7. Create a file called /opt/config/nexus_username.txt containing the text: docker





  8. Create a file called /opt/config/nexus_password.txt containing the text: docker





  9. Create a file called /opt/config/dmaap_topic.txt containing the text: AAI-EVENT





  10. Create a file called /opt/config/nexus_docker_repo.txt containing text: nexus3.onap.org:10001





  11. Create a file called /opt/config/docker_version.txt containing text: 1.2-STAGING-latest





  12. Please note that in the previous step, docker version is currently 1.2-STAGING-latest and this will be changed later






Troubleshooting FAQ

1. Cassandra throwing seedy exceptions

If you encounter the following errors:

ERROR 13:31:16 Directory /var/lib/cassandra/data doesn't exist

ERROR 13:31:16 Directory /var/lib/cassandra/commitlog doesn't exist

ERROR 13:31:16 Directory /var/lib/cassandra/saved_caches doesn't exist

ERROR 13:31:48 Exception encountered during startup

java.lang.RuntimeException: Unable to gossip with any seeds

You can try to resolve the problem by commenting out the line "- CASSANDRA_SEEDS=aai.hbase.simpledemo.onap.org" in the file "docker-compose-db.yml"

2. Containers are unable to connect to Cassandra DB

If any docker container is unable to connect to cassandra container, edit "docker-compose-db.yml", and remove the "network_mode: host" config option from the cassandra docker config block, and repeat step 15

3. Disabling AAF authentication

If for any reason you want to disable AAF you can edit the following files aai-traversal/appconfig/application.properties and aai-resources/appconfig/application.properties and replace the following:

with

4. Unable to resolve aaf-onap-test.osaaf.org

Either add a line

to /etc/hosts

OR

you can edit the files aai-resources/appconfig/aaf/org.osaaf.location.props aai-traversal/appconfig/aaf/org.osaaf.location.props and replace

with

Note: The current certificate allows only for a defined set of hostnames (like aaf-onap-test.osaaf.org) and does not allow IPs. The the AAF server (aaf-onap-test.osaaf.org) is currently located in the Windriver lab and the IP address is subject to change and might not be the current one in use at present. Alternatively use the property aaf_locate_url to point to your local AAF instance.

Related articles