vCPE use case testing

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

   HAS and MUSIC install

   $ 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
   
   

Installation and Configuration

1. Build and start A&AI simulator

2. $ cd ~/has/conductor/conductor/tests/functional/simulators
   $ ./build_aaisim.sh
   $ ./run_aaisim.sh

   Note: DNS name resolution issue may arise during building the simulator, because it needs the **web** Python package. TBD: Provide more detailed instructions. How does one there is an issues? what can one do about it?

3. Verify A&AI Simulator (Hint: in examples, 0.0.0.0 is IPAddress of A&AI container as per $ docker container ls)
   1. $ docker container ls
   2. expected result: image names should include: aaisim
   3. $ curl http://0.0.0.0:8081/healthcheck
   4. expected result: {"status": "success"}
   5. $ curl http://0.0.0.0:8081/aai/v13/cloud-infrastructure/cloud-regions/
   6. expected result: {"cloud-region": [{"group-assignments": ...much more...
4. Build and start MUSIC
   1. Configure access to MUSIC:

   2. Edit music/distribution/dockermusic/music.sh to change user/password:

      ```text
      -CASS_USERNAME=cassandra1
      -CASS_PASSWORD=cassandra1
      +CASS_USERNAME=conductor
      +CASS_PASSWORD=c0nduct0r
      ```

   3. Edit music/distribution/dockermusic/properties/music.properties to change user/password:

      ```text
      -cassandra.user=cassandra1
      -cassandra.password=cassandra1
      +cassandra.user=conductor
      +cassandra.password=c0nduct0r
      ```

   4. Build and start MUSIC containers

      $ cd ~//music/distribution/dockermusic
      $ ./music.sh start

   5. Verify MUSIC components
      1. $ docker container ls
      2. expected result: image names should include: music-tomcat, music-zk, music-war, music-db
5. Build and Start HAS
   1. Configure HAS
      1. Edit has/conductor.conf
      2. search for [music_api]

      ```text
      -server_url = http://localhost:8080/MUSIC/rest/v2
      +server_url = http://<<IP address of 'music-tomcat' container>>:8080/MUSIC/rest/v2
      ```

6. * [aai]
7. ```text
8. -server_url = https://aai.api.simpledemo.onap.org:8443/aai
9. +server_url = http://<<IP address of 'aaisim' container>>:8081/aai
10. ```
11. - Hint: find IPAddress of containers via:
12. $ docker container ls
13. and look at first term in PORTS column
14. 2. Onboard the HAS "conductor" application into MUSIC, E.g.:
15. - $ curl -X POST -H 'Content-Type: application/json' \
16. -d '{"appname" : "conductor","userId": "conductor","password": "c0nduct0r","isAAF": false}' \
17. 0.0.0.0:8080/MUSIC/rest/v2/admin/onboardAppWithMusic
18. - expected result: {"Generated AID":"2895db7e-2746-426a-822f-80c367161c65","Success":"Your
19. application conductor has been onboarded with MUSIC."}
20. 3. Start the HAS containers
21. - $ cd ~/has
22. - $ ./run-dockers.sh
23. 3. Verify HAS components
24. - $ docker container ls
25. - expected result: image names should include:
26. data
27. reservation
28. solver
29. api
30. controller