Loading tutorial/2-2-ofc22.md +2 −2 Original line number Diff line number Diff line Loading @@ -30,8 +30,8 @@ __Important__: The device drivers operating with real devices, e.g., OpenConfigD ## 2.2.3. Deployment and Dependencies To run this functional test, it is assumed you have deployed a MicroK8s-based Kubernetes environment and a TeraFlowSDN controller instance as described in the [Tutorial: Deployment Guide](./1-0-deployment.md), and you configured the Python environment as described in controller instance as described in the [Tutorial: Deployment Guide](./1-0-deployment.md), and you configured the Python environment as described in [Tutorial: Run Experiments Guide > 2.1. Configure Python Environment](./2-1-python-environment.md). Remember to source the scenario settings appropriately, e.g., `cd ~/tfs-ctrl && source my_deploy.sh` in each terminal you open. Loading tutorial/2-4-ecoc22.md +7 −3 Original line number Diff line number Diff line Loading @@ -13,6 +13,8 @@ folder has been defined. This functional test has only been tested with emulated devices; however, if you have access to real devices, you can modify the files `./ecoc22/tests/Objects.py` and `./ecoc22/tests/Credentials.py` to point to your devices, and map to your network topology. Otherwise, you can modify the `./ecoc22/tests/descriptors_emulated.json` that is designed to be uploaded through the WebUI instead of using the command line scripts. __Important__: The device drivers operating with real devices, e.g., OpenConfigDriver, P4Driver, and TransportApiDriver, have to be considered as experimental. The configuration and monitoring capabilities they support are Loading @@ -22,8 +24,8 @@ __Important__: The device drivers operating with real devices, e.g., OpenConfigD ## 2.4.3. Deployment and Dependencies To run this functional test, it is assumed you have deployed a MicroK8s-based Kubernetes environment and a TeraFlowSDN controller instance as described in the [Tutorial: Deployment Guide](./1-0-deployment.md), and you configured the Python environment as described in controller instance as described in the [Tutorial: Deployment Guide](./1-0-deployment.md), and you configured the Python environment as described in [Tutorial: Run Experiments Guide > 2.1. Configure Python Environment](./2-1-python-environment.md). Remember to source the scenario settings appropriately, e.g., `cd ~/tfs-ctrl && source my_deploy.sh` in each terminal you open. Loading Loading @@ -90,6 +92,7 @@ the optical layer and another for the packet layer. Besides, you can check the " rules that have been configured in each device. In the Grafana Dashboard, given that there is now a service configured, you should see the plots with the monitored data for the device. By default, device R1-EMU is selected. ### 2.4.5.3. L3VPN Service removal This step deconfigures the previously created services emulating the request an OSM WIM would make by means of a Mock Loading @@ -101,6 +104,7 @@ When the script finishes, check the WebUI "Services" tab. You should see that th Besides, in the "Devices" tab you can see that the appropriate configuration rules have been deconfigured. In the Grafana Dashboard, given that there is no service configured, you should see a 0-valued flat plot again. ### 2.4.5.4. Cleanup This last step performs a cleanup of the scenario removing all the TeraFlowSDN entities for completeness. Loading Loading
tutorial/2-2-ofc22.md +2 −2 Original line number Diff line number Diff line Loading @@ -30,8 +30,8 @@ __Important__: The device drivers operating with real devices, e.g., OpenConfigD ## 2.2.3. Deployment and Dependencies To run this functional test, it is assumed you have deployed a MicroK8s-based Kubernetes environment and a TeraFlowSDN controller instance as described in the [Tutorial: Deployment Guide](./1-0-deployment.md), and you configured the Python environment as described in controller instance as described in the [Tutorial: Deployment Guide](./1-0-deployment.md), and you configured the Python environment as described in [Tutorial: Run Experiments Guide > 2.1. Configure Python Environment](./2-1-python-environment.md). Remember to source the scenario settings appropriately, e.g., `cd ~/tfs-ctrl && source my_deploy.sh` in each terminal you open. Loading
tutorial/2-4-ecoc22.md +7 −3 Original line number Diff line number Diff line Loading @@ -13,6 +13,8 @@ folder has been defined. This functional test has only been tested with emulated devices; however, if you have access to real devices, you can modify the files `./ecoc22/tests/Objects.py` and `./ecoc22/tests/Credentials.py` to point to your devices, and map to your network topology. Otherwise, you can modify the `./ecoc22/tests/descriptors_emulated.json` that is designed to be uploaded through the WebUI instead of using the command line scripts. __Important__: The device drivers operating with real devices, e.g., OpenConfigDriver, P4Driver, and TransportApiDriver, have to be considered as experimental. The configuration and monitoring capabilities they support are Loading @@ -22,8 +24,8 @@ __Important__: The device drivers operating with real devices, e.g., OpenConfigD ## 2.4.3. Deployment and Dependencies To run this functional test, it is assumed you have deployed a MicroK8s-based Kubernetes environment and a TeraFlowSDN controller instance as described in the [Tutorial: Deployment Guide](./1-0-deployment.md), and you configured the Python environment as described in controller instance as described in the [Tutorial: Deployment Guide](./1-0-deployment.md), and you configured the Python environment as described in [Tutorial: Run Experiments Guide > 2.1. Configure Python Environment](./2-1-python-environment.md). Remember to source the scenario settings appropriately, e.g., `cd ~/tfs-ctrl && source my_deploy.sh` in each terminal you open. Loading Loading @@ -90,6 +92,7 @@ the optical layer and another for the packet layer. Besides, you can check the " rules that have been configured in each device. In the Grafana Dashboard, given that there is now a service configured, you should see the plots with the monitored data for the device. By default, device R1-EMU is selected. ### 2.4.5.3. L3VPN Service removal This step deconfigures the previously created services emulating the request an OSM WIM would make by means of a Mock Loading @@ -101,6 +104,7 @@ When the script finishes, check the WebUI "Services" tab. You should see that th Besides, in the "Devices" tab you can see that the appropriate configuration rules have been deconfigured. In the Grafana Dashboard, given that there is no service configured, you should see a 0-valued flat plot again. ### 2.4.5.4. Cleanup This last step performs a cleanup of the scenario removing all the TeraFlowSDN entities for completeness. Loading
