Skip to end of metadata
Go to start of metadata


Table of Contents

Prerequisites


VM requirments:

  1. VM spec needs to be 8 cores and 8G of ram, ubuntu 14.04 (do not use ubuntu 16.04)
  2. docker engine needs to be installed on the VM to run the containers


Initial Setup


  1. in order for the dockers to start correctly on the VM the following folders need to be created on the VM.
  2. you need the /opt folder:
    1. in it create /opt/config/
    2. place the following files in this /opt/config/ folder:

  3. you need a /data folder
    1. in it create /data/environments/  (Note: Do not forget to configure your (BE/FE/Kibana/Elastic search)  machine IP address in the below file.If they are all planned to run in the same 
      machine, configure the same IP address) copu the file from here: https://git.onap.org/sdc/tree/sdc-os-chef/environments/Template.json
    2. rename it to AUTO.json
    3. change all the yyy to ip of the vm you are running on.
    4. this is an example of an env file
      AUTO.json
    5. this file may change from time to time so keep it updated with the changes done.
  4. now create a /data/scripts/ folder
  5. in folder /data/scripts/ place the following scripts from the sdc repo sdc repo
    • docker_run.sh
    • docker_login.sh
    • docker_health.sh
  6. provide execution permissions to the scripts

    chmod 777 /data/scripts/*
  7. as root user, launch the following script to test the setup is working (it will pull dockers from the LF repo and start them)

    /data/scripts/docker_run.sh -r 1.1-STAGING-latest 

    on script completion, you will see a successful health check. Depending on you VM performance, some containers may take times to be ready and up : sdc-cs takes about 2/3 mn, sdc-BE takes about 7/8 mn.

  8. SDC API are available : http://yourIP:8080  for "internal API"

  9. in order to access SDC you will need to enable SDC Simulator



Setting up the Webseal-Simulator

In order to set up the Webseal-Simulator in your local environment, you can use the following guide: SDC Simulator

Configure Docker Engine

  1. in order to allow building dockers from dev machine to the VM you will need to enable tcp communication to the docker engine.
    use this link to enable tcp communication to the docker https://docs.docker.com/engine/reference/commandline/dockerd/
  2. once enabled you can execute netstat -nap to check the docker d is listening to 2375.

Deploying local dockers to the VM


In order to check our code from our local environment, we'll compile our code locally and upload our local images to the vagrant

This is how to do so:

  1. Add DOCKER_HOST to environment variables with the value: tcp://<ip of the vm where >:<port>

  2. Run mvn clean install and build the whole project.
  3. After the build is finished you'll need to run the sdc-os-chef project with profile docker in order to build docker from your local code and upload them to your local vagrant.
    Run the following command in order to do so: (Need to check the docker repository credentials)

    mvn clean install -pl sdc-os-chef -P docker
  4. After this process is done go to your vagrant and run docker images to check that your local images are on the machine
  5. In order to deploy your local images without pulling the latest images from the nexus you'll need to run the docker_run script with the local flag like so:

    /data/scripts/docker_run.sh -l



  • No labels

25 Comments

  1. Hi ,

    I am trying to setup SDC-C using the instructions in this page and I am getting the following error.. Any workaround or fix ?

    //Br

    [2018-03-26T08:23:29-04:00] FATAL: Stacktrace dumped to /root/chef-solo/cache/chef-stacktrace.out

    [2018-03-26T08:23:29-04:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report

    [2018-03-26T08:23:29-04:00] ERROR: cookbook_file[/usr/share/elasticsearch/config/kibana_dashboard_virtualization.json] (sdc-elasticsearch::ES_6_create_kibana_dashboard_virtualization line 1) had an error: Chef::Exceptions::FileNotFound: Cookbook 'sdc-elasticsearch' (0.0.0) does not contain a file at any of these locations:

      files/debian-8.6/kibana_dashboard_virtualization.json

      files/debian/kibana_dashboard_virtualization.json

      files/default/kibana_dashboard_virtualization.json

      files/kibana_dashboard_virtualization.json



  2. Hi,
    When I try to start the docker containers, it times out. I tweaked the run script to just run
    sdc-fe container alone, it produced the same error. I checked the docker logs and noticed the
    chef error detailed below.
    [2018-05-01T14:10:07+00:00] INFO: Started chef-zero at chefzero://localhost:1 with repository at /root/chef-solo
      One version per cookbook

    [2018-05-01T14:10:07+00:00] INFO: Forking chef instance to converge...
    Starting Chef Client, version 13.5.3
    [2018-05-01T14:10:07+00:00] INFO: *** Chef 13.5.3 ***
    [2018-05-01T14:10:07+00:00] INFO: Platform: x86_64-linux
    [2018-05-01T14:10:07+00:00] INFO: Chef-client pid: 12
    [2018-05-01T14:10:07+00:00] INFO: The plugin path /etc/chef/ohai/plugins does not exist. Skipping...
    [2018-05-01T14:10:08+00:00] INFO: Setting the run_list to ["role[catalog-fe]"] from CLI options

    ================================================================================
    Error expanding the run_list:
    ================================================================================

    Unexpected API Request Failure:
    -------------------------------
    Object not found: chefzero://localhost:1/environments/AUTO

    System Info:
    ------------
    chef_version=13.5.3
    platform=debian
    platform_version=9.2
    ruby=ruby 2.4.2p198 (2017-09-14 revision 59899) [x86_64-linux]
    program_name=chef-solo worker: ppid=7;start=14:10:07;
    executable=/opt/chef/bin/chef-solo


    Running handlers:
    [2018-05-01T14:10:08+00:00] ERROR: Running exception handlers
    Running handlers complete
    [2018-05-01T14:10:08+00:00] ERROR: Exception handlers complete
    Chef Client failed. 0 resources updated in 00 seconds
    [2018-05-01T14:10:08+00:00] FATAL: Stacktrace dumped to /root/chef-solo/cache/chef-stacktrace.out
    [2018-05-01T14:10:08+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
    [2018-05-01T14:10:08+00:00] ERROR: 404 "Not Found"
    [2018-05-01T14:10:08+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

  3. are you building docker locally or pulling them from LF? 

    please check that the auto json your are using is up to date compered to thsi one: https://git.onap.org/sdc/tree/sdc-os-chef/environments/Template.json

  4. I was building locally. However, I've updated my auto.json using the link you shared and I am now pulling the docker images. Am encountering a new error detailed below in the sdc-es. This prevents other images from starting. Thank you

    Running handlers:ESC[0m

    [2018-05-03T22:02:50+00:00] ERROR: Running exception handlers

    Running handlers complete

    ESC[0m[2018-05-03T22:02:50+00:00] ERROR: Exception handlers complete

    Chef Client failed. 0 resources updated in 00 secondsESC[0m

    [2018-05-03T22:02:50+00:00] FATAL: Stacktrace dumped to /root/chef-solo/cache/chef-stacktrace.out

    [2018-05-03T22:02:50+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report

    [2018-05-03T22:02:50+00:00] ERROR: cookbook_file[/usr/share/elasticsearch/config/kibana_dashboard_virtualization.json] (sdc-elasticsearch::ES_6_create_kibana_dashboard_virtualization line 1) had an error: Chef::Exceptions::FileNotFound: Cookbook 'sdc-elasticsearch' (0.0.0) does not contain a file at any of these locations:

      files/debian-8.6/kibana_dashboard_virtualization.json

      files/debian/kibana_dashboard_virtualization.json

      files/default/kibana_dashboard_virtualization.json

      files/kibana_dashboard_virtualization.json


    This cookbook _does_ contain: ['files/default/visualization_JVM-used-CPU.json','files/default/dashboard_BI-Dashboard.json','files/default/visualization_host-used-CPU.json','files/default/dashboard_Monitoring-Dashboared.json','files/default/visualization_JVM-used-Threads-Num.json','files/default/visualization_Show-all-created-Resources-slash-Services-slash-Products.json','files/default/logging.yml','files/default/visualization_number-of-user-accesses.json','files/default/visualization_Show-all-distributed-services.json','files/default/visualization_Show-all-certified-services-ampersand-resources-(per-day).json','files/default/visualization_host-used-Threads-Num.json','files/default/visualization_JVM-used-Memory.json']

    [2018-05-03T22:02:50+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

  5. hi,

    what version of our dockers are you using?

    i recheck our dockers and there is no issue in the lates build.


    based on what i see in you log can it be theat you are tring to use the amsterdam dockers with the latest env and docker run?

  6. I cleared all docker images, volumes , containers I have. I then ran  /data/scripts/docker_run.sh -r 1.1-STAGING-latest

    Output
    performing old dockers cleanup
    8ce029dc32b8
    1320bf1deef2
    docker run sdc-elasticsearch...
    pulling code
    Error response from daemon: manifest for nexus3.onap.org:10001/onap/sdc-elasticsearch:1.1-STAGING-latest not found
    Unable to find image 'nexus3.onap.org:10001/onap/sdc-elasticsearch:1.1-STAGING-latest' locally
    docker: Error response from daemon: manifest for nexus3.onap.org:10001/onap/sdc-elasticsearch:1.1-STAGING-latest not found.
    See 'docker run --help'.
    please wait while ES is starting...
    monitor sdc-es Docker
      % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                     Dload  Upload   Total   Spent    Left  Speed
      0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (7) Failed to connect to 10.20.0.100 port 9200: Connection refused
    Sleep: 20 seconds before testing if sdc-es DOCKER is up. Total wait time up now is: 0 seconds. Timeout is: 900 seconds


  7.  
    Changing the tag to use 1.2-STAGING instead of 1.1-STAGING, I was able to encounter the error below


    root@homa-onap-02:~# docker logs sdc-es
    The environment variable HTTP_PROXY is discouraged.  Use http_proxy.
    [2018-05-07T16:04:50+00:00] INFO: Started chef-zero at chefzero://localhost:1 with repository at /root/chef-solo
      One version per cookbook

    [2018-05-07T16:04:50+00:00] INFO: Forking chef instance to converge...
    Starting Chef Client, version 13.8.5
    [2018-05-07T16:04:50+00:00] INFO: *** Chef 13.8.5 ***
    [2018-05-07T16:04:50+00:00] INFO: Platform: x86_64-linux-musl
    [2018-05-07T16:04:50+00:00] INFO: Chef-client pid: 13
    [2018-05-07T16:04:50+00:00] INFO: The plugin path /etc/chef/ohai/plugins does not exist. Skipping...
    [2018-05-07T16:04:51+00:00] INFO: Setting the run_list to ["role[elasticsearch]"] from CLI options
    [2018-05-07T16:04:51+00:00] INFO: Run List is [role[elasticsearch]]
    [2018-05-07T16:04:51+00:00] INFO: Run List expands to [sdc-elasticsearch::ES_1_setup_elasticsearch, sdc-elasticsearch::ES_2_setup_logging, sdc-elasticsearch::ES_3_prepareProbeFile]
    [2018-05-07T16:04:51+00:00] INFO: Starting Chef Run for d3327a357785
    [2018-05-07T16:04:51+00:00] INFO: Running start handlers
    [2018-05-07T16:04:51+00:00] INFO: Start handlers complete.
    resolving cookbooks for run list: ["sdc-elasticsearch::ES_1_setup_elasticsearch", "sdc-elasticsearch::ES_2_setup_logging", "sdc-elasticsearch::ES_3_prepareProbeFile"]
    [2018-05-07T16:04:51+00:00] INFO: Loading cookbooks [sdc-elasticsearch@0.0.0]
    Synchronizing Cookbooks:
    [2018-05-07T16:04:51+00:00] INFO: Storing updated cookbooks/sdc-elasticsearch/recipes/ES_1_setup_elasticsearch.rb in the cache.
    [2018-05-07T16:04:51+00:00] INFO: Storing updated cookbooks/sdc-elasticsearch/recipes/ES_2_setup_logging.rb in the cache.
    [2018-05-07T16:04:51+00:00] INFO: Storing updated cookbooks/sdc-elasticsearch/recipes/ES_3_prepareProbeFile.rb in the cache.
    [2018-05-07T16:04:51+00:00] INFO: Storing updated cookbooks/sdc-elasticsearch/templates/default/ES-elasticsearch.yml.erb in the cache.
    [2018-05-07T16:04:51+00:00] INFO: Storing updated cookbooks/sdc-elasticsearch/templates/default/ready-probe.sh.erb in the cache.
    [2018-05-07T16:04:51+00:00] INFO: Storing updated cookbooks/sdc-elasticsearch/files/default/logging.yml in the cache.
      - sdc-elasticsearch (0.0.0)
    Installing Cookbook Gems:
    Compiling Cookbooks...

    ================================================================================
    Recipe Compile Error in /root/chef-solo/cache/cookbooks/sdc-elasticsearch/recipes/ES_1_setup_elasticsearch.rb
    ================================================================================

    NoMethodError
    -------------
    undefined method `each' for "10.20.0.100":String

    Cookbook Trace:
    ---------------
      /root/chef-solo/cache/cookbooks/sdc-elasticsearch/recipes/ES_1_setup_elasticsearch.rb:3:in `from_file'

    Relevant File Content:
    ----------------------
    /root/chef-solo/cache/cookbooks/sdc-elasticsearch/recipes/ES_1_setup_elasticsearch.rb:

      1:  elasticsearch_list = ''
      2:  
      3>> node['Nodes']['ES'].each  do |item|
      4:      elasticsearch_list += "- " + item + ":9300\n"
      5:  end
      6:  
      7:  
      8:  template "/usr/share/elasticsearch/config/elasticsearch.yml" do
      9:     source "ES-elasticsearch.yml.erb"
     10:     owner "elasticsearch"
     11:     group "elasticsearch"
     12:     mode "0755"

    System Info:
    ------------
    chef_version=13.8.5
    platform=alpine
    platform_version=3.7.0
    ruby=ruby 2.4.3p205 (2017-12-14 revision 61247) [x86_64-linux-musl]
    program_name=chef-solo worker: ppid=7;start=16:04:50;
    executable=/usr/bin/chef-solo


    Running handlers:
    [2018-05-07T16:04:51+00:00] ERROR: Running exception handlers
    Running handlers complete
    [2018-05-07T16:04:51+00:00] ERROR: Exception handlers complete
    Chef Client failed. 0 resources updated in 01 seconds
    [2018-05-07T16:04:51+00:00] FATAL: Stacktrace dumped to /root/chef-solo/cache/chef-stacktrace.out
    [2018-05-07T16:04:51+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
    [2018-05-07T16:04:51+00:00] ERROR: undefined method `each' for "10.20.0.100":String
    [2018-05-07T16:04:51+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)



    1. This was solved by editing the auto.json and changing the Node ES, CS properites to become arrays.  .each, .first works on arrays and not strings

  8. Michael Lando

    I am getting an error when sdc-cs-init beings to run. I've attachecd the complete log file. The error complains about a titan.properties file. kindly see below. Thank you

    2018-05-08T17:32:26.174Z|||main||SDC-TOOL||INFO|||beFqdn_IS_UNDEFINED||o.o.s.a.impl.TitanGraphInitializer||ActivityType=<createGraph>, Desc=<createGraph : try to load file /tmp/sdctool/config//titan.properties>
    ***********************************
    ***** 3 *********************
    ***********************************
    STDERR: java.lang.IllegalArgumentException: Could not instantiate implementation: com.thinkaurelius.titan.diskstorage.cassandra.astyanax.AstyanaxStoreManager
        at com.thinkaurelius.titan.util.system.ConfigurationUtil.instantiate(ConfigurationUtil.java:55)
        at com.thinkaurelius.titan.diskstorage.Backend.getImplementationClass(Backend.java:473)
        at com.thinkaurelius.titan.diskstorage.Backend.getStorageManager(Backend.java:407)
        at com.thinkaurelius.titan.graphdb.configuration.GraphDatabaseConfiguration.<init>(GraphDatabaseConfiguration.java:1320)
        at com.thinkaurelius.titan.core.TitanFactory.open(TitanFactory.java:94)
        at com.thinkaurelius.titan.core.TitanFactory.open(TitanFactory.java:62)
        at org.openecomp.sdc.asdctool.impl.TitanGraphInitializer.createGraph(TitanGraphInitializer.java:60)
        at org.openecomp.sdc.asdctool.main.DataSchemaMenu.main(DataSchemaMenu.java:64)
    Caused by: java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
        at com.thinkaurelius.titan.util.system.ConfigurationUtil.instantiate(ConfigurationUtil.java:44)
        ... 7 more
    Caused by: java.lang.NumberFormatException: For input string: ""
        at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
        at java.lang.Long.parseLong(Long.java:601)
        at java.lang.Long.valueOf(Long.java:803)
        at com.thinkaurelius.titan.diskstorage.configuration.backend.CommonsConfiguration.get(CommonsConfiguration.java:99)
        at com.thinkaurelius.titan.diskstorage.configuration.BasicConfiguration.get(BasicConfiguration.java:55)
        at com.thinkaurelius.titan.diskstorage.common.DistributedStoreManager.<init>(DistributedStoreManager.java:73)
        at com.thinkaurelius.titan.diskstorage.cassandra.AbstractCassandraStoreManager.<init>(AbstractCassandraStoreManager.java:163)
        at com.thinkaurelius.titan.diskstorage.cassandra.astyanax.AstyanaxStoreManager.<init>(AstyanaxStoreManager.java:272)
        ... 12 more
    ---- End output of "bash"  "/tmp/chef-script20180508-13-13yk8re" ----
    Ran "bash"  "/tmp/chef-script20180508-13-13yk8re" returned 3
    [2018-05-08T17:32:27+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
    [2018-05-08T17:32:27+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)



    1. your issue is coming from the AUTO.json file.

      it looks like you did not configure it properly.

      please provide it so i will be able to assit


      1. Michael Lando Thank you. I've attached the AUTO.json


        AUTO.json

        1. if you are runing a beijing version of sdc then the auto json is not the most updated one. please look at part 3.a

          1. Thank you Michael Lando. I updated the AUTO.json and it worked.

  9. Michael Lando, one question/request, for testing network service distribution, do we need DMaaP? I couldn't find latest/proper doc for setting up dmaap. I am actually exploring sdc-distribution-client.

  10. Bharath Thiruveedula yes. the distribution is based on dmaap as the queue which is used for communication between sdc and the different applications using our client. regarding setting up the dmaap i suggest you look at how dmaap is deployed in csit or the heat based deployment so that you will be able to start it. 

  11. Hi,

    I am having problems with SDC discovering the workflow plugin. I have SDC and sdc-workflow running. I also configured my AUTO.json setting the workflow_source_url.

    I keep getting the error The "WORKFLOW" plugin is currently unavailable. Please try again later.


    Thank you
    Michael Lando

    ====AUTO.json====

     "Plugins": {

                "DCAE": {

                    "dcae_discovery_url": "10.20.0.40",

                    "dcae_source_url": "10.20.0.40"

                },

                "WORKFLOW": {

                    "workflow_discovery_url": "10.20.0.40",

                    "workflow_source_url": "10.20.0.40"

                }

            },


    =====docker ps =====

    CONTAINER ID        IMAGE                                                               COMMAND                  CREATED             STATUS              PORTS                                                                     NAMES
    dff99328fd60        nexus3.onap.org:10001/onap/sdc/sdc-workflow-designer:latest         "/bin/sh -c /home/sd…"   4 hours ago         Up 4 hours          0.0.0.0:9527->8080/tcp                                                    sdc-workflow-designer
    cb8d54ca39df        onap/sdc-simulator:1.3-STAGING-latest                               "/root/startup.sh"       4 hours ago         Up 4 hours          0.0.0.0:8285->8080/tcp, 0.0.0.0:8286->8443/tcp                            sdc-sim
    b7554c8342dd        nexus3.onap.org:10001/onap/sdc-frontend:1.3-STAGING-latest          "/root/startup.sh"       4 hours ago         Up 4 hours          0.0.0.0:5346-5347->5346-5347/tcp, 8080/tcp                                sdc-FE
    c01c0d0ecd19        nexus3.onap.org:10001/onap/sdc-backend:1.3-STAGING-latest           "/root/startup.sh"       4 hours ago         Up 4 hours          0.0.0.0:5348-5349->5348-5349/tcp, 8080/tcp                                sdc-BE
    abbdd7efc7b1        nexus3.onap.org:10001/onap/sdc-onboard-backend:1.3-STAGING-latest   "/root/startup.sh"       4 hours ago         Up 4 hours          0.0.0.0:5350-5351->5350-5351/tcp, 8080/tcp                                sdc-onboard-BE
    f1610b222af9        nexus3.onap.org:10001/onap/sdc-cassandra:1.3-STAGING-latest         "/root/startup.sh /b…"   4 hours ago         Up 4 hours          7000-7001/tcp, 0.0.0.0:9042->9042/tcp, 7199/tcp, 0.0.0.0:9160->9160/tcp   sdc-cs
    56f2aec5ba7b        nexus3.onap.org:10001/onap/sdc-elasticsearch:1.3-STAGING-latest     "/root/startup.sh /b…"   4 hours ago         Up 4 hours          0.0.0.0:9200->9200/tcp, 0.0.0.0:9300->9300/tcp                            sdc-es


  12. I had not configured the AUTO.json and Template.json file in the /opt/sdc/sdc-os-chef/environments directory.

            Presently, I have configured AUTO.json and Template.json files with the IP Address of the SDC Private IP. ( 15.0.0.20)

            Though the Floating IP is 192.168.180.19.

           

           "name" and "description" have been configured with "AUTO" values.


           Please go through the files and let me know if it is correct.

           Thanking You.



    AUTO.jsonTemplate.json

  13. Hello,

             I am trying to setup ONAP Beijing Release and Setup is getting stuck on ONAP-SDC-BE-INIT Container.

            I am getting the Chef Run Process exited unsuccessfully (Exit Code 1 ). So, setup doesn't proceed anyway beyond this.

            I looked into this link and I learnt that we need to configure AUTO.json or Template.json files with the IP Addresses and AUTO values.

            I have configured the files and attached in the previous comment. Could you please look into this and let me know if anything needs to be corrected.

            Please find the docker logs of SDC-BE-INIT below::

    + tar xvfz /tmp/normatives.tar.gz
    + cd /tmp/normatives/scripts/import/tosca/
    + /bin/chmod +x importCategoryTypes.py importCommon.py importDataTypes.py importGroupTypes.py importHeatTypes.py importNfvTypes.py importNodeType.py importNormativeAll.py importNormativeCapabilities.py importNormativeElements.py importNormativeInterfaceLifecycleTypes.py importNormativeNoHeatAndNormativeTypes.py importNormativeTypes.py importONAPNormativeAll.py importOnapTypes.py importPolicyTypes.py importSolTypes.py importUsersFromYaml.py upgradeHeatAndNormativeTypes.py upgradeHeatTypes1707.py upgradeNfvTypes.py upgradeNormative.py upgradeNormativeVersion.py upgradeNormativeVersionAll.py upgradeNormativeVersionProd1702_3537.py upgradeONAPNormative.py upgradeONAPTypes.py upgradeSolTypes.py
    + check_normative=/tmp/check_normative.out
    ++ curl -s -o /tmp/check_normative.out -w '%{http_code}\n' -X GET -H 'Content-Type: application/json;charset=UTF-8' -H 'USER_ID: jh0003' -H 'X-ECOMP-RequestID: cbe744a0-037b-458f-aab5-df6e543c4090' http://15.0.0.20:8080/sdc2/rest/v1/screen
    + status_code=500
    + '[' 500 '!=' 200 ']'
    + exit 500
    ---- End output of "bash" "/tmp/chef-script20180712-13-1jn4x3d" ----
    Ran "bash" "/tmp/chef-script20180712-13-1jn4x3d" returned 244
    [2018-07-12T08:34:30+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
    [2018-07-12T08:34:30+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)


            Thanking You.


    Best Regards,

    Arjun

  14. While building SDC for docker image creation, i got below error

    Running the maven command  mvn clean install -Pdocker in sdc project

    [INFO] ------------------------------------------------------------------------

    [INFO] BUILD FAILURE

    [INFO] ------------------------------------------------------------------------

    [INFO] Total time: 51.608 s

    [INFO] Finished at: 2018-08-02T10:18:21+05:30

    [INFO] ------------------------------------------------------------------------

    [ERROR] Failed to execute goal io.fabric8:docker-maven-plugin:0.23.0:build (docker-build) on project activity-spec-init: Unable to build image [onap/activity-spec-init] : The command '/bin/sh -c apk --update add python' returned a non-zero code: 1  -> [Help 1]

    Any has this issue? Please let me know if you have a solution.



  15. First I docker run sdc-cassandra, and then when I docker run sdc-cassandra-init, I got below error(docker images version is 1.3-STAGING-latest). Any has this issue? Looks like missing some config, but I don't know how to slove it 

    [2018-08-22T12:46:16+00:00] INFO: bash[excuting-schema-creation] ran successfully
    [2018-08-22T12:46:16+00:00] INFO: bash[excuting-schema-creation] ran successfully
    - execute "bash" "/tmp/chef-script20180822-13-1by69vw"
    * bash[excuting-titanSchemaCreation.sh] action run
    [execute] java -Dlogback.configurationFile=/tmp/sdctool/scripts/../config/logback.xml -cp ::/tmp/sdctool/scripts/../asdctool-1.3.0-SNAPSHOT-jar-with-dependencies.jar: org.openecomp.sdc.asdctool.main.DataSchemaMenu create-titan-structures /tmp/sdctool/config
    2018-08-22T12:46:17.138Z|||main||SDC-TOOL||ERROR|MAJOR||beFqdn_IS_UNDEFINED||o.o.s.c.config.EcompErrorLogUtil||ActivityType=<log>, Desc=<Invalid configuration in YAML file. Could not set error info type for message id >
    2018-08-22T12:46:17.159Z|||main||SDC-TOOL||WARN|||beFqdn_IS_UNDEFINED||o.o.s.c.util.YamlToObjectConverter||ActivityType=<log>, Desc=<The file /tmp/sdctool/config/neo4j-errors-configuration.yaml cannot be found. Ignore reading configuration.>
    2018-08-22T12:46:17.160Z|||main||SDC-TOOL||WARN|||beFqdn_IS_UNDEFINED||o.o.s.c.util.YamlToObjectConverter||ActivityType=<log>, Desc=<The file /tmp/sdctool/config/ecomp-error-configuration.yaml cannot be found. Ignore reading configuration.>
    2018-08-22T12:46:17.161Z|||main||SDC-TOOL||WARN|||beFqdn_IS_UNDEFINED||o.o.s.c.util.YamlToObjectConverter||ActivityType=<log>, Desc=<The file /tmp/sdctool/config/distribution-engine-configuration.yaml cannot be found. Ignore reading configuration.>
    2018-08-22T12:46:17.163Z|||main||SDC-TOOL||INFO|||beFqdn_IS_UNDEFINED||o.o.s.a.impl.TitanGraphInitializer||ActivityType=<createGraph>, Desc=<** createGraph with /tmp/sdctool/config//titan.properties>
    2018-08-22T12:46:17.164Z|||main||SDC-TOOL||INFO|||beFqdn_IS_UNDEFINED||o.o.s.a.impl.TitanGraphInitializer||ActivityType=<createGraph>, Desc=<createGraph : try to load file /tmp/sdctool/config//titan.properties>
    2018-08-22T12:46:17.620Z|||main||SDC-TOOL||INFO|||beFqdn_IS_UNDEFINED||c.n.a.c.i.ConnectionPoolMBeanManager||ActivityType=<registerMonitor>, Desc=<Registering mbean: com.netflix.MonitoredResources:type=ASTYANAX,name=ClusterTitanConnectionPool,ServiceType=connectionpool>
    2018-08-22T12:46:17.632Z|||main||SDC-TOOL||INFO|||beFqdn_IS_UNDEFINED||c.n.a.c.i.CountingConnectionPoolMonitor||ActivityType=<onHostAdded>, Desc=<AddHost: 10.185.204.68>
    2018-08-22T12:46:17.839Z|||main||SDC-TOOL||INFO|||beFqdn_IS_UNDEFINED||c.n.a.c.i.ConnectionPoolMBeanManager||ActivityType=<registerMonitor>, Desc=<Registering mbean: com.netflix.MonitoredResources:type=ASTYANAX,name=KeyspaceTitanConnectionPool,ServiceType=connectionpool>
    2018-08-22T12:46:17.840Z|||main||SDC-TOOL||INFO|||beFqdn_IS_UNDEFINED||c.n.a.c.i.CountingConnectionPoolMonitor||ActivityType=<onHostAdded>, Desc=<AddHost: 10.185.204.68>
    2018-08-22T12:46:17.974Z|||main||SDC-TOOL||INFO|||beFqdn_IS_UNDEFINED||c.n.a.c.i.CountingConnectionPoolMonitor||ActivityType=<onHostRemoved>, Desc=<RemoveHost: 10.185.204.68>
    2018-08-22T12:46:48.023Z|||RingDescribeAutoDiscovery||SDC-TOOL||WARN|||beFqdn_IS_UNDEFINED||c.n.a.impl.RingDescribeHostSupplier||ActivityType=<get>, Desc=<Failed to get hosts from sdctitan via ring describe. Will use previously known ring instead>
    2018-08-22T12:46:48.494Z|||main||SDC-TOOL||INFO|||beFqdn_IS_UNDEFINED||c.t.t.d.util.BackendOperation||ActivityType=<executeDirect>, Desc=<Temporary exception during backend operation [getConfiguration]. Attempting backoff retry.>
    com.thinkaurelius.titan.diskstorage.TemporaryBackendException: Temporary failure in storage backend
    at com.thinkaurelius.titan.diskstorage.cassandra.astyanax.AstyanaxKeyColumnValueStore.getNamesSlice(AstyanaxKeyColumnValueStore.java:114)
    at com.thinkaurelius.titan.diskstorage.cassandra.astyanax.AstyanaxKeyColumnValueStore.getNamesSlice(AstyanaxKeyColumnValueStore.java:78)
    at com.thinkaurelius.titan.diskstorage.cassandra.astyanax.AstyanaxKeyColumnValueStore.getSlice(AstyanaxKeyColumnValueStore.java:67)
    at com.thinkaurelius.titan.diskstorage.configuration.backend.KCVSConfiguration$1.call(KCVSConfiguration.java:91)
    at com.thinkaurelius.titan.diskstorage.configuration.backend.KCVSConfiguration$1.call(KCVSConfiguration.java:88)
    at com.thinkaurelius.titan.diskstorage.util.BackendOperation.execute(BackendOperation.java:133)
    at com.thinkaurelius.titan.diskstorage.util.BackendOperation$1.call(BackendOperation.java:147)

  16. When running 

    /data/scripts/docker_run.sh -r 1.1-STAGING-latest

    as root, I get the Errors:

    FATA[0017] Error response from daemon: v1 ping attempt failed with error: Get https://nexus3.onap.org:10001/v1/_ping: dial tcp 199.204.45.137:10001: dial tcp 199.204.45.137:10001: i/o timeout. If this private registry supports only HTTP or HTTPS with an unknown CA certificate, please add `--insecure-registry nexus3.onap.org:10001` to the daemon's arguments. In the case of HTTPS, if you have access to the registry's CA certificate, no need for the flag; simply place the CA certificate at /etc/docker/certs.d/nexus3.onap.org:10001/ca.crt

    Performing old dockers cleanup
    docker run sdc-elasticsearch...
    pulling code
    FATA[0010] Error response from daemon: v1 ping attempt failed with error: Get https://nexus3.onap.org:10001/v1/_ping: dial tcp 199.204.45.137:10001: dial tcp 199.204.45.137:10001: i/o timeout. If this private registry supports only HTTP or HTTPS with an unknown CA certificate, please add `--insecure-registry nexus3.onap.org:10001` to the daemon's arguments. In the case of HTTPS, if you have access to the registry's CA certificate, no need for the flag; simply place the CA certificate at /etc/docker/certs.d/nexus3.onap.org:10001/ca.crt
    flag provided but not defined: --log-opt
    See 'docker run --help'.
    [ ERROR ] Docker sdc-es run command exit with status [2]
    please wait while ES is starting...
    Monitor sdc-es Docker
    % Total % Received % Xferd Average Speed Time Time Time Current
    Dload Upload Total Spent Left Speed
    0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Failed to connect to 192.168.1.13 port 9200: Connection refused
    Sleep: 20 seconds before testing if sdc-es DOCKER is up. Total wait time up now is: 0 seconds. Timeout is: 900 seconds


    And then this runs until timeout.

    If anyone could help me out to try and fix this problem it would be much appreciated.


    1. Christopher Robbertse, is it the first time you're trying to use this registry? 

      There were reports today on onap-discuss mailing list about intermittent Nexus timeouts.

      1. Yes, this is the first time. I have not seen this ONAP-discuss before?


        1. If you are behind a proxy, you will need to configure it in the Docker engine settings. Onap-discuss is a mailing list. See Mailing Lists 

    • Is there any specific reason why Ubuntu 16.06 shouldn't be used ?
    • Do developers use devtool (the automated platform to bring up the interested component in VM using vagrant) to bring up the components or they bring it up manually ? 
    • For development, do developers bring up the components of interest separately in different VMs or can it be brought up in same VM or server ?

    Any advice is much appreciated.