Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

This guide will illustrate setting up an A&AI development environment for R3 Casablanca in Ubuntu 16.04.  

DRAFT - this guide is in process of being updated - thanks for your patience (smile)

For this exercise, I set up a new instance of Ubuntu in Virtualbox and gave it 16G RAM, 200GB dynamically allocated storage, and 3 processors.

  1. install openjdk 8
    1. sudo apt install openjdk-8-jdk

  2. Install single node hadoop/janusgraph
    1. $ wget http://github.com/JanusGraph/janusgraph/releases/download/v0.2.0/janusgraph-0.2.0-hadoop2.zip
    2. $ unzip janusgraph-0.2.0-hadoop2.zip
    3. $ cd janusgraph-0.2.0-hadoop2/
    4. $ ./bin/janusgraph.sh start, # make sure you are not a root user as elasticsearch cannot be run as root.  Response looks like:
      Forking Cassandra...
      Running `nodetool statusthrift`... OK (returned exit status 0 and printed string "running").
      Forking Elasticsearch...
      Connecting to Elasticsearch (127.0.0.1:9200)...... OK (connected to 127.0.0.1:9200).
      Forking Gremlin-Server...
      Connecting to Gremlin-Server (127.0.0.1:8182).... OK (connected to 127.0.0.1:8182).
      Run gremlin.sh to connect.

    5. you can verify whether everything is running by executing  
      ./bin/janusgraph.sh status

      Gremlin-Server (org.apache.tinkerpop.gremlin.server.GremlinServer) is running with pid 9835
      Elasticsearch (org.elasticsearch.bootstrap.Elasticsearch) is running with pid 9567
      Cassandra (org.apache.cassandra.service.CassandraDaemon) is running with pid 9207


  3. Install haproxy
    1. $ sudo apt-get -y install haproxy
    2. $ <path-to-haproxy>/haproxy -v
      HA-Proxy version 1.6.3 2015/12/25
      Copyright 2000-2015 Willy Tarreau <willy@haproxy.org>

    3. Install the attached haproxy.cfg file in /etc/haproxy

      1. $ wget https://wiki.onap.org/download/attachments/45306687/haproxy.cfg

      2. $ sudo cp haproxy.cfg /etc/haproxy
      3. $ sudo mkdir /usr/local/etc/haproxy

    4. Install the attached aai.pem file in /etc/ssl/private

      1. $ wget https://wiki.onap.org/download/attachments/45306687/aai.pem

      2. $ sudo cp aai.pem /etc/ssl/private/aai.pem
      3. $ sudo chmod 640 /etc/ssl/private/aai.pem
      4. $ sudo chown root:ssl-cert /etc/ssl/private/aai.pem 

    5. Add these hostnames to the loopback interface in /etc/hosts: 

      1. 127.0.0.1 localhost aai-traversal.api.simpledemo.openecomp.org aai-resources.api.simpledemo.openecomp.org

    6. $ sudo service haproxy restart

  4. follow the initial setup instructions in Setting Up Your Development Environment e.g.
    1. sudo apt-get install git
    2. sudo apt-get install npm
    3. sudo apt-get install maven
    4. sudo apt-get install docker.io
    5. If you did not originally create a settings.xml file when setting up the dev environment, you may get an error on some of the repos saying that oparent is unresolvable.  Using the example settings.xml file should solve this problem: Setting Up Your Development Environment#MavenExamplesettings.xml
  5. Set up repos.
    1. $ mkdir -p ~/src/aai
    2. $ cd ~/src/aai
    3. $ git clone ssh://<username>@gerrit.onap.org:29418/aai/aai-common
    4. $ git clone ssh://<username>@gerrit.onap.org:29418/aai/traversal
    5. $ git clone ssh://<username>@gerrit.onap.org:29418/aai/resources
    6. $ git clone ssh://<username>@gerrit.onap.org:29418/aai/graphadmin
    7. $ git clone ssh://<username>@gerrit.onap.org:29418/aai/logging-service
  6. Build aai-common, traversal, graphadmin, logging-service, and resources
    1. $ cd ~/src/aai/aai-common
    2. $ git checkout casablanca
    3. $ mvn -DskipTests clean install
      Should result in BUILD SUCCESS
    4. $ cd ~/src/aai/resources
    5. $ git checkout casablanca
    6. $ mvn -DskipTests clean install
      Should result in BUILD SUCCESS
    7. $ cd ~/src/aai/graphadmin
    8. $ git checkout casablanca
    9. $ mvn -DskipTests clean install
      Should result in BUILD SUCCESS
    10. $ cd ~/src/aai/logging-service
    11. $ git checkout casablanca
    12. $ mvn -DskipTests clean install
      Should result in BUILD SUCCESS
    13. $ cd ~/src/aai/traversal
    14. $ git checkout casablanca
    15. mvn -DskipTests clean install
      Should result in BUILD SUCCESS

  7. Janus setup
    1. Modify both janus-cached.properties and janus-realtime.properties to the following (for all MS’s that will connect to the local Cassandra backend)
      storage.backend=cassandra
      storage.hostname=localhost
      storage.cassandra.keyspace=onap # or different keyspace name of your choosing
      • update ~/src/aai/resources/aai-resources/src/main/resources/etc/appprops/janusgraph-cached.properties
      • update ~/src/aai/resources/aai-resources/src/main/resources/etc/appprops/janusgraph-realtime.properties
      • update ~/src/aai/traversal/aai-traversal/src/main/resources/etc/appprops/janusgraph-cached.properties
      • update ~/src/aai/traversal/aai-traversal/src/main/resources/etc/appprops/janusgraph-realtime.properties
      • update ~/src/aai/graphadmin/src/main/resources/etc/appprops/janusgraph-cached.properties
      • update ~/src/aai/graphadmin/src/main/resources/etc/appprops/janusgraph-realtime.properties
    1. NOTE: The first thing that would need to be done is adding the schema to the local instance. (this will need to be done whenever using a new keyspace or after wiping the data).
    2. Put createDbSchemaLocal.sh on your dev machine.  Adjust your build version accordingly, as of the casablanca release the version is 1.0.1. 
      $ export PROJECT_HOME=~/src/aai/graphadmin/target/aai-graphadmin-1.0.1-SNAPSHOT-build
      $ sh createDbSchemaLocal.sh
      You should see: 

      -- loading schema into JanusGraph
      Successfully loaded the schema to inmemory
      -- loading schema into JanusGraph
      Successfully loaded the schema to inmemory
      -- Loading new schema elements into JanusGraph --
      -- graph commit
      -- graph shutdown

       

  8. Start the "resources" microservice
    1. Resources runs on port 8447.  Go to the resources directory
      $ cd ~/src/aai/resources
    2. Set the debug port to 9447
      $ export MAVEN_OPTS="-Xms1024m -Xmx5120m -XX:PermSize=2024m -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=9447,server=y,suspend=n"
    3. Start the microservice - adjust your build version accordingly, as of the casablanca release the version is 1.3.4
      $ java -DAJSC_HOME=aai-resources -DBUNDLECONFIG_DIR=src/main/resources/ -jar aai-resources/target/aai-resources-1.3.4-SNAPSHOT.jar
      Should see something like this: Resources Microservice Started 

  9. Verify the resources microservice (this example uses Postman utility for Google Chrome)
    1. Use basic auth, user = AAI, pw = AAI
    2. Set the X-TransactionId header (in the example below, the value is 9999)
    3. Set the X-FromAppId header (in the example below, the value is jimmy-postman)
    4. Perform a GET of https://127.0.0.1:8443/aai/v11/network/vces
    5. You should see an error as below, 404 Not Found, ERR.5.4.6114.  This indicates that the service is functioning normally:



  10. Start the "traversal" microservice
    1. Traversal runs on port 8446.  Go to the traversal directory
      $ cd ~/src/aai/traversal
    2. Set the debug port to 9446
      $ export MAVEN_OPTS="-Xms1024m -Xmx5120m -XX:PermSize=2024m -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=9446,server=y,suspend=n"
    3. Start the microservice
      $ java -DAJSC_HOME=aai-traversal -DBUNDLECONFIG_DIR=src/main/resources/ -jar aai-traversal/target/aai-traversal-1.2.0-SNAPSHOT.jar
      Should see something like this: Traversal Microservice Started

  11. Verify the traversal microservice by executing attached postman AAI API calls
    1. Set up the widget models
      This will set up the postman to add widget models: Add Widget Models.postman_collection.json
    2. Create a runner using this file: models.csv
    3. Run the test runner
    4. Add a named query called "getComponentList" (this named query is used by VID): NamedQuery.postman_collection.json
    5. Add objects: Add Instances for Named Query.postman_collection.json (when using vXX in place of v11, replace the xmlns "http://org.openecomp.aai.inventory/v11" with "http://org.onap.aai.inventory/vXX" in the Body of the PUT request)
    6. Execute named-query: Execute Named Query.postman_collection.json
      You should see something like the following:
  12. Your A&AI instance is now running, both the resources and traversal microservices are working properly with a local janus graph. 
  13. Next: Tutorial: Making and Testing a Schema Change in A&AI

Attachments

  File Modified

  • No labels