| Jeremy Mordkoff | 6f07e6f | 2016-09-07 18:56:51 -0400 | [diff] [blame] | 1 | |
| 2 | TO test the LP mocklet via command line: |
| 3 | |
| 4 | Part 1: Run the test server infrastructure |
| 5 | |
| 6 | 1. ssh into a VM, navigate to your workspace rift root and run ./rift-shell |
| 7 | 2. navigate to: |
| 8 | modules/core/mc/rwmc/test |
| 9 | |
| 10 | 3. run: |
| 11 | $ python3 ./mission_control.py -m ethsim -c --skip-prepare-vm --mock --skip-ui |
| 12 | |
| 13 | The --skip-ui option prevents the server infrastructure from loading Composer |
| 14 | and the UI (to save time loading, especially if you are going to be running |
| 15 | the server in your own dev environment). |
| 16 | |
| 17 | Part 2: Run the mocklet |
| 18 | |
| 19 | 1. repeat step 1 above |
| 20 | 2. navigate to: |
| 21 | modules/core/mc/rwlp_dts_mock |
| 22 | |
| 23 | |
| 24 | 3. If the rwlp_dts_mock/node_modules directory does not exist, run: |
| 25 | |
| 26 | $ npm install |
| 27 | |
| 28 | 4. Start the mocklet after the server (mission_control.py) has completed initialization |
| 29 | |
| 30 | To start the mocklet: |
| 31 | |
| 32 | $ node lp_mock_client.js |
| 33 | |
| 34 | 5. After the mocklet has started, open another terminal window (can be |
| 35 | anywhere that can access the restconf server on your VM) and run the following: |
| 36 | |
| 37 | Seed the descriptors and instance config objects, run: |
| 38 | |
| 39 | $ ./set_data.sh <vm-ip-address> |
| 40 | |
| 41 | Now you are ready to test retrieving an ns-instance-opdata object |
| 42 | |
| 43 | $ get_ns_instance_opdata.sh <vm-ip-address> |
| 44 | |