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 23 Current »

Quick Start

Installation and Configuration

Install the HAS project

Installing from the Source Code

Get HAS seed code from the Linux Foundation Projects page.

git clone https://gerrit.onap.org/r/optf/has


Use virtual environment to create and manage libraries and dependencies for HAS project.

virtualenv {virtual_environment_location}
source {virtual_environment_location}/bin/activate


Inside of /has/conductor folder, run the following commands:

python setup.py install
pip install -e .


In {virtual_environment_location}/bin folder, you should see the five components of HAS/Conductor project and you can with the commands below.

conductor-api,conductor-controller, conductor-solver, conductor-reservation, conductor-data
conductor-api --port=8091 -- --config-file={conductor_conf_file_location} 
conductor-controller --config-file={conductor_conf_file_location}
conductor-solver --config-file={conductor_conf_file_location}
conductor-reservation --config-file={conductor_conf_file_location}
conductor-data --config-file={conductor_conf_file_location}


Installing through OOM

Please first follow the steps inside ONAP on Kubernetes with Rancher to build a kubernetes environment for ONAP deployment.

Clone the OOM repository from ONAP Gerrit 

git clone -b casablanca http://gerrit.onap.org/r/oom
cd oom/kubernetes


Install Helm plugins to enable ONAP deployment.

sudo cp -R ~/oom/kubernetes/helm/plugins/ ~/.helm


Configure the values.yaml inside /oom/kubernetes/onap/ folder as the one attached here. Here I only enabled AAF, AAI, OOF and Policy. You can also enable other components if needed. 

Setup the helm server and build local helm repository

cd ~/oom/kubernetes
helm serve &
helm repo add local http://127.0.0.1:8879
make all; make onap


Deploy ONAP through Helm

helm deploy dev local/onap --namespace onap


Process for debuging


Load changes inside the development environment

The changes will be updated through an update of the docker image. Please make sure you've setup the development env according to Setting Up Your Development Environment (i.e. create proper settings.xml file for maven)

git clone http://gerrit.onap.org/r/optf/has
<!- Make code changes here->
cd <path>/has
mvn clean install <!- Build the maven artifact with changes ->

Then create new Dockerfile and build-dockers-debug.sh under has/ folder to build the new image. The artifact can be found in the has/conductor/target folder

sudo <file-path>/build-dockers-debug.sh <tag_for_image> <path_to_artifact_zip> <path_to_folder_with_Dockerfile>

Replace the image name inside the deployment for all HAS components.

Commiting the Code

git commit -am "Initial proj struct"
git review -s
git commit -as --amend
# scroll down 2 lines (above your Change-ID) insert "Issue-ID: {issue_id}"

git review





  • No labels