...

• The global scheduler is fully compatible with kubernetes. Users can operate directly using kubectl;
• Using websocket for the edge-cloud communication;
• In addition to the cluster name, the cluster tag can be added customically. Cluster tag matching through intelligent cluster-selecter to achieve accurate routing of messages;
• Through k8s-cluster-shim to achieve the management of kubernetes cluster, shielding the native implementation within the kubernetes cluster;
• According to the interface of OTE-Stack, the cluster shim of the third party cluster can be realized to access and schedule the third party cluster. The internal implementation of the third party cluster is shielded;
• Each layer can be used as a control entry to control all sub-clusters below this layer. Users can also use kubectl or API to implement custom cluster management and scheduling.

On the edge, OTE-Stack provides the ability to support node autonomy within the cluster.

Image Added

• Use EdgeHub to take over the kubelet, kube-proxy or k3s agent components of the node.
• EdgeHub provides load balancing capabilities for node requests.
• During node autonomy, you can use EdgeController instead of node to complete node status reporting and updating.
• EdgeHub and EdgeController have both the autonomy capabilities of k8s and k3s clusters.

OTE Components 

WebFrontend

...

Operations for a single VM, such as start, stop, etc.

EdgeHub

Proxy between master and node in the edge cluster.

EdgeController

It is used to take over the state management of the node when the node is disconnected from the master.

Software components

APIs

Video Security Monitoring R4 API Document

...