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 13 Next »

Quick Start

Installation and Configuration

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

conductor-api,conductor-controller, conductor-solver, conductor-reservation, conductor-data

Installing through docker images

Get HAS seed code from the Linux Foundation Projects page.

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


Use docker scripts inside the repo to start HAS dockers

cd has/

./run-dockers.sh ./conductor.conf

Then you can find all HAS components running.

Configuration

For the configuration inside the config-file, please refer to the README inside Gerrit  

It is worth noting that A&AI and MUSIC may be needed to run HAS project. Please refer to their setup page for installation.

Currently in Beijing release, HAS uses MUSIC 2.5.3 version inside deployment. Please refer to Setup for Developing MUSIC for installation.

Running the example

To start the process, execute the following commands:

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}

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