smarter-brokerage | Brokerage for shared IoT infrastructure

smarter-brokerage is a Python library. smarter-brokerage has no bugs, it has no vulnerabilities and it has low support. However smarter-brokerage build file is not available. You can download it from GitLab.

The Brokerage for shared IoT infrastructure allows each node in a [SMARTER edge infrastructure] to be partitioned, where each tenant has full control of a partition. The diagram below shows the brokerage architecture. A set of physical nodes are managed by an instance of SMARTER Node Manager. This SMARTER Node Manager managing physical nodes is connected to a SMARTER Brokerage Manager that provides the brokerage API. The brokerage Manager API allows virtual nodes (partitions of physical nodes) to be allocated into physical node with each virtual node behaving as a SMARTER node itself and is managed by a separate instance of SMARTER Node Manager (one per tenant). Brokerage API server supports two types of users, brokers and tenants. A broker is a superuser for the Brokerage API server and is able to create,modify and delete tenants and virtual nodes. A tenant has limited access to brokerage API and is only able to manage their virtual nodes (creation, deletion). A tenant SMARTER Node Manager is used to deploy applications on those virtual nodes. A tenant is expected to have full access to their SMARTER Node Manager. The SMARTER Brokerage API is a REST API and it is described by the swagger definition at [Swagger API definition] The section "API Notes" describe the API in more detail. The SMARTER Brokerage Manager is stateless, all the API operations interact with objects in the SMARTER Node Manager that is managing the physical nodes. Each virtual node appears as a pod running on the physical node it is associated with. ![SMARTER virtual nodes] Brokerage-API-diagram.png "Standard SMARTER virtual node network topology"). ![SMARTER time line] Timeline-brokerage.png "Standard SMARTER time line"). A node in a k3s/k8s context is a system that is managed by an k3s/k8s server where pods can be deployed. In the figure there are three SMARTER Node Managers (k3s/k8s servers). The blue one that is managing the physical infrastructure (edge nodes). The red and green are managing partitions running on the edge nodes, they do not have direct access to the edge nodes themselves but only to the designated partition. Each partition behaves as a node to k3s/k8s.