Minimum hardware specification

Once OpenSync is running on a device (gateway or extender), you can expect memory and CPU usage as stated in the table below.

Temporary file system

OpenSync requires a minimum of 16 MB storage for the tmpfs (temporary file system).

Persistent storage

There should be a minimum of 7 MB persist storage for features like reboot reasons, WAN configuration. For details refer to Requirements | Persistent Storage

Dependent libraries

OpenSync is optimized for Linux operating systems with kernel version 3.3 or higher. In addition, OpenSync requires minimal the following libraries:

Device identification parameters

To correctly identify and manage the connected devices, OpenSync requires basic device information parameters.

Device identification parameters (stored in AWLAN_Node table):

• ID - must be unique per node

• model name - Defines the node model

  • Case sensitive

  • Should not have leading or trailing spaces

  • Must be unique in the world

  • Match regex pattern: ^[A-Za-z0-9_-]*

• firmware version - details below

Firmware version format

To ensure node compability with the SDN controller, the firmware package version must be named using a specific format. The firmware package version starts with at least two numerals, split by a dot. The expected format is:

• major.minor[.revision][.patch][-build][-githash][-profile]

Example: 1.2.4-8-ga46f46c-dev

Secure cloud connection

One of the top OpenSync priorities is ensuring the highest level of data privacy by enforcing state-of-the-art security standards, such as client authentication and data encryption for all the nodes that connect to the OpenSync SDN contoller. These security mechanisms require node certificates and encryption keys. Connection is secure by using TLS 1.2 and two way SSL mutual authentication.

Firewall rules

OpenSync is a cloud-controlled and cloud-managed software. As such, OpenSync requires cloud connectivity. Firewall rules must allow the necessary cloud connection:

• allow 443 port for OVSDB and MQTT connection to the SDN controller

Node reboot method

OpenSync requires the ability to enforce a safe full-node reboot and general OpenSync implementation is in OSP layer.

Remote upgrade support

To enable OpenSync updates, the connected nodes must support full firmware upgrades which we provide over generic tool called safeupdate. Images should be encrypted.

Switching from native Linux to Open vSwitch (OVS)

OpenSync services take full advantage of the OVS networking features. The integrators should switch from native networking (such as native Linux bridge implementation) to the OVS networking (OVS bridges).

WAN information

OpenSync needs to be aware of WAN configuration and state.

LAN information

OpenSync must be aware of all clients connected to the LAN network. Information about the client devices and their basic configuration is mandatory.

Watchdog

OpenSync runs as embedded software and therefore requires a mechanism that detects potential malfunctions and automatically initiates the recovery procedure. One such mechanism is the Watchdog.

Currently OpenSync does not provide implementation and we suggest to use software or hardware-based watchdog. Hardware watchdog is recommended.

WiFi virtual access points (VAP)

There should be 8 VAP per radio available (1 STA + 7 AP’s) for OpenSync to use simultaneously. SDN controller will orchestrate them per customer needs in runtime.

Additional Requirements