Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
connectivity-suite:architecture [2019/11/01 13:53] voegeli |
connectivity-suite:architecture [2020/03/18 09:18] juraschek ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 8: | Line 8: | ||
| The Connectivity Suite has been designed to have a scalable architecture. It allows to be installed in the cloud or on-premises depending on customer needs. The system architecture is based on Linux running microservices in Docker containers. | The Connectivity Suite has been designed to have a scalable architecture. It allows to be installed in the cloud or on-premises depending on customer needs. The system architecture is based on Linux running microservices in Docker containers. | ||
| - | {{ :cs:software_architecture_basic2.png? }} | + | {{ connectivity-suite:software_architecture_basic2.png? }} |
| *User interface: Web interface accessible by https (SSL + OpenID). | *User interface: Web interface accessible by https (SSL + OpenID). | ||
| - | *Middleware: Establishes the communication between the User Interface and the microservices in the Core for a scalable, robust and distributed system. The Middleware runs in a separated container | + | *Middleware: Establishes the communication between the User Interface and the microservices in the Core for a scalable, robust and distributed system. The Middleware runs in a separate container |
| - | *Core: in the core several microservices (Keycloak, Inventory, Configuration, Deployment, Health, Identity Server) are running which are servicing REST API requests. | + | *Core: In the core several microservices (Keycloak, Inventory, Configuration, Deployment, Health, Identity Server) are running which are servicing REST API requests. |
| The solution can be used in standalone mode by using the interactive user interface provided by NetModule or by integrating the Connectivity Suite into customer applications by using the powerful REST API. | The solution can be used in standalone mode by using the interactive user interface provided by NetModule or by integrating the Connectivity Suite into customer applications by using the powerful REST API. | ||
| Line 54: | Line 54: | ||
| - | {{ :cs:Home2.png? }} | + | {{ connectivity-suite:home2.png? }} |
| === Provisioning network === | === Provisioning network === | ||
| A Provisioning network is a VPN subnet consisting of devices newly detected by the Connectivity Suite but not assigned to a Tenant yet. Only the Platform Administrator has access to this subnet and can move Devices to a Tenant. A Connectivity Suite instance has exactly one Provisioning network. | A Provisioning network is a VPN subnet consisting of devices newly detected by the Connectivity Suite but not assigned to a Tenant yet. Only the Platform Administrator has access to this subnet and can move Devices to a Tenant. A Connectivity Suite instance has exactly one Provisioning network. | ||
| - | {{ :cs:provisioning5.png? }} | + | {{ connectivity-suite:provisioning5.png? }} |
| ==== Tenant network ==== | ==== Tenant network ==== | ||
| A Tenant is a VPN subnet consisting of devices (routers) and generic devices (network devices which are not routers ex. server). Tenants can be used to group Devices. A Tenant is used for separation of devices. A Tenant network is hosted by virtual VPN servers. The certificates used for establishing VPN connections are created in an automated fashion. | A Tenant is a VPN subnet consisting of devices (routers) and generic devices (network devices which are not routers ex. server). Tenants can be used to group Devices. A Tenant is used for separation of devices. A Tenant network is hosted by virtual VPN servers. The certificates used for establishing VPN connections are created in an automated fashion. | ||
| - | {{ :cs:Tenants5.png? }} | + | {{ connectivity-suite:tenants5.png? }} |
| Line 72: | Line 72: | ||
| - | {{ :cs:system_architecture2.png?nolink|}} | + | {{ connectivity-suite:system_architecture2.png?nolink|}} |
| - | [[cs:start|← Back to Connectivity Suite Main Page]] | + | [[connectivity-suite:start|← Back to Connectivity Suite Main Page]] |