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

Compare with Current View Page History

« Previous Version 5 Next »

Here's the list of requirements that need to be met at each of the components for the homing call from SO to succeed for the vCPE use case. 

Requirements from the downstream dependencies

AAI

Data needed

  • vGMuxInfra (run the vcpe flows that create the vGMuxInfra)
  • list of Cloud regions, one of which should have the vGMuxInfra

MultiCloud

Data needed

Policy

Policy models to be created:

Policies to be uploaded: 

  • vG demand

vGMuxInfra demand

  • objective function (distance) 
  • colocation constraint 

HAS


OSDF 

Requirements for Functional Features


HPA

  • upload HPA policies into policy framework


Capacity checks

  • upload Capacity check policy into policy framework


Sequence of actions (how to..)

  • Deploy OOF
    • HEAT: 
      1. Go to the OOF VM
      2. Run /opt/oof_vm_init.sh - this will pull the docker images and install OSDF + HAS, and perform the required configurations to pass the healthcheck. 
    • OOM:

  • populate the cloud region data into AAI
  • upload the policies into policy framework 

Run the vcpe flows that create the vGMuxInfra

vCPE use case standalone testing on a single machine

Goal: Running the vCPE use case of the Beijing release of ONAP in a local setup, with minimal hardware and software requirements.
The work should be done in the ONAP MUSIC and ONAP HAS repositories with tag 2.0.0-ONAP.

Prerequisites


  1. Install Docker CE, an example tutorial can be found here.
  2. Make local copies of the HAS and MUSIC repos
    - $ cd "your workspace"
    - $ git clone https://gerrit.onap.org/r/music
    - $ cd music
    - $ git checkout 2.0.0-ONAP
    - $ cd ../
    - $ git clone https://gerrit.onap.org/r/optf/has
    - $ cd has
    - $ git checkout 2.0.0-ONAP

  3. (Optional) Install Insomnia REST API client for handling REST requests. Some prepared requests and variables are available can be imported to Insomnia.
  4. (Optional) For advanced debugging of the inter-component communication use Wireshark



  • No labels