...
- Build and start A&AI simulator
Build and start
Code Block language bash $ 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?
- Verify A&AI Simulator (Hint: in examples, 0.0.0.0 is IPAddress of A&AI container as per $ docker container ls)
- $ docker container ls
- expected result: image names should include: aaisim
- $ curl http://0.0.0.0:8081/healthcheck
- expected result: {"status": "success"}
- $ curl http://0.0.0.0:8081/aai/v13/cloud-infrastructure/cloud-regions/
- expected result: {"cloud-region": [{"group-assignments": ...much more...
...
- Build and start MUSIC
...
- Configure access to MUSIC:
...
Edit music/distribution/dockermusic/music.sh to change user/password:
...
Code Block language bash ```text -CASS_USERNAME=cassandra1
...
-CASS_PASSWORD=cassandra1
...
+CASS_USERNAME=conductor
...
+CASS_PASSWORD=c0nduct0r
...
```
...
Edit music/distribution/dockermusic/properties/music.properties to change user/password:
...
Code Block language bash ```text -cassandra.user=cassandra1
...
-cassandra.password=cassandra1
...
+cassandra.user=conductor
...
+cassandra.password=c0nduct0r
...
```
- 2. Build and start MUSIC containers
- = $ cd ~//music/distribution/dockermusic
- - $ ./music.sh start
- 3. Verify MUSIC components
- - $ docker container ls
- - expected result: image names should include:
- music-tomcat
- music-zk
- music-war
- music-db
1. Build and Start HAS
1. Configure HAS
- Edit has/conductor.conf
* 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
```
* [aai]
```text
-server_url = https://aai.api.simpledemo.onap.org:8443/aai
+server_url = http://<<IP address of 'aaisim' container>>:8081/aai
```
- Hint: find IPAddress of containers via:
$ docker container ls
and look at first term in PORTS column
2. Onboard the HAS "conductor" application into MUSIC, E.g.:
- $ curl -X POST -H 'Content-Type: application/json' \
-d '{"appname" : "conductor","userId": "conductor","password": "c0nduct0r","isAAF": false}' \
0.0.0.0:8080/MUSIC/rest/v2/admin/onboardAppWithMusic
- expected result: {"Generated AID":"2895db7e-2746-426a-822f-80c367161c65","Success":"Your
application conductor has been onboarded with MUSIC."}
...