Create an Node.js webservice to define the following:

NodeSelector View
The Node Selector view allows the user to select the available Orion nodes from a pre-compiled list of supported notes

1. Read-only view of interfaces and parameters.
2. Toggle of whether the node is being used or not

NodeEditor View
The Node Editor View allows you to define the following parameters

1. Name of the Node Instance
2. Pre-filled target location (http url) (only targets of the same version may be used together)

NodeConnector View
The Node Connector has a schematic view where connections between various nodes can be defined. This then auto generates the router object for the system_config.json file.

• Config Node
• RTCM Node
• UbxGpsNode

Integrate ROS2 cross compile environment for Xavier

here is the information that we need for setting up Jenkins
cd ~/workbench
git clone https://github.com/go360-io/orion-ros2-reference.git
sudo ln -s ~/workbench/orion-ros2-reference /opt/ws_kros
cd /opt/ws_kros/docker

creates the build environment in a docker

./build_dev.sh

creates the shared libraries and puts them in the install/ folder

./build.sh

Add mechanism to deploy .so files that are not ros-nodes. This is needed for example to dynamically link common.lib

Change orion-ros2-reference/docker/build_dev.sh to be part of the CI/CD pipeline

This compiles the binaries for x86 and also enables the user to use it as a run time environment. We can integrate this into the Jenkins release pipeline.

Specs:
jenkins.orion.go360.io

dev.orion.go360.io
qa.orion.go360.io
staging.orion.go360.io
prod.orion.go360.io

Abstract "colcon build" --cmake-args ' -DCMAKE_BUILD_TYPE=Debug' -DCMAKE_CXX_FLAGS="-Werror -Wall"
to be in a bash script in file: https://github.com/go360-io/orion-ros2-reference/blob/develop/docker/build.sh

common lib is currently linked statically, as ConfigNode is not supporting deploy of non-ros-node libraries.

depends on #20

Currently the GGA Value send to the ntrip caster to calculate a virtual correction station is fixed to tiergarten/berlin. function to set is already available, only position from GPS must be subscribed and updated based on this information.

creates the infrastructure docker that allows you to grab the target gz files

./build_infra.sh <-- replace this script with Jenkins deployment into the S3 target

modify the target location of the binaries in the config/ folder

install/config/lib/config/ConfigNode_exec ./config

the ConfigNode_exec will run the application and use the system_config.json to pull the appropriate tar.gz files for each node, we need to change this to our s3 targets.

test and validate the end to end deployment with S3 and Jenkins and the Config Node

format is:

bucket/builds/[git_hash]/[target_architecture]/[node_name].tar.gz
bucket/builds/[branch_name]/[target_architecture]/[node_name].tar.gz

example branch names:

• develop
• qa
• staging
• master

example target_architecture:

• armv8 64bit
  -x86 64bit

example node_names:
start with lib + CamelCase(node_name) + "Node.so"

• libRtcmNode.so
• libGnssNode.so

Implement a generic v4l2 ROS2 node that supports different 4vl2 devices as USB Webcams, but also the MIPI Connected Cams.

In build.sh we source some ros bash scripts, which currently stalls for 20s on each build.

A simple solution would be to manage the LD_LIBRARY_PATH ourselves, as this is the main reason for sourcing the script

Server side implementation of the custom SSL certificates and domains with CloudFront.

Setup an EC2 instance to run jenkins.

Setup Route53 DNS for
dev.orion.go360.io
qa.orion.go360.io
staging.orion.go360.io
prod.orion.go360.io

Setup ECS Clusters for orion nodes
dev_cluster
qa_cluster
staging_cluster
prod_cluster

Setup Load Balancers to point DNS records to appropriate clusters

Setup DocumentDB for each branch with daily sync in the databases