Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
cs:architecture [2019/08/09 17:12]
voegeli [Services]
cs:architecture [2019/08/09 17:23]
voegeli
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_basic.png? }}+{{ :cs:software_architecture_basic2.png? }}
  
   *User interface: Web interface accessible by https (SSL + OpenID).   *User interface: Web interface accessible by https (SSL + OpenID).
Line 32: Line 32:
 The Health microservice provides health data from devices to monitor the connectivity status and the uptime of each device and network. The Health microservice provides health data from devices to monitor the connectivity status and the uptime of each device and network.
  
-=====Home===== +
-The Home represents the Connectivity Suite which may be running on a single machine, or as a distributed system with several instances of each microservice. The Home is running on a Home server which includes an OpenVPN server as one of the Docker components. It is used to securely connect to devices in the customer networks, and for network devices to connect to the Home server (notify about new devices, update IP when switching VPN servers).+
  
 ===== Provisioning ===== ===== Provisioning =====
Line 60: Line 59:
 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:provisioning2.png? }}+{{ :cs: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:Tenants2.png? }}+{{ :cs:Tenants5.png? }}
  
  
Line 73: Line 72:
  
  
-{{ :cs:system_architecture.png?​nolink|}}+{{ :cs:system_architecture2.png?​nolink|}}
  
  
 [[cs:​start|← Back to Connectivity Suite Main Page]] [[cs:​start|← Back to Connectivity Suite Main Page]]