Contents
Deployment for Connected Robotics
Infrastructure as code deployment base
Robot onboarding
Onboarding of a new robot requires an Onboarding file that may be available in guide mentioned in the link. If your robot is in this list you may use this template and just adjust it to the minor changes you may have. If your robot, however, is not on the list, you will have to generate the onboarding template before. This template is a json that needs to be included in the body of the http request. Download the script and run it in your robot: The guide for robot onboarding can be found here: https://github.com/5G-ERA/middleware/blob/main/docs/User/Onboarding/Robot.md
Network Application onboarding
This section shows how to deploy a Network Application to the Middleware system. Essentially, this is the execution of robotics tasks that have been previously onboarded. So, for the deployment of a network application, the taskid containing the app to be deployed is necessary. Follow the tutorial: https://github.com/5G-ERA/middleware/blob/main/docs/User/Onboarding/Network%20Application%20Onboarding.md
Cloud Edge onboarding
For the middleware to plan optimal network application placement, it is important to import the network topology into the system. This section shows how to create a new Cloud or edge entity in the Redis backend of the Middleware.
Adding a new entry in the Middleware topology allows Middleware to better optimize the resource and task planning to provide the best network capabilities to the Robot. Thanks to this, the Network Application placement can be adjusted to specific needs like low latency network thanks to the closer placement from the Robot or specific network slice requirement (upcoming!). The full guide on cloud and edge onboarding can be found here : https://github.com/5G-ERA/middleware/blob/main/docs/User/Onboarding/Cloud%20Onboarding.md
AWS deployment with Terraform
