...
When is the next OpenSync release?
OpenSync should be released on bi-monthly cadence although the monthly releases Next release and milestone is mentioned in Download OpenSync. OpenSync releases monthly releases that are treated as code drops and not recommend recommended to be used in production. In 2023 there is a target to release Quarterly releases are long term support releases (LTS) that can be used in production. In 2023, OpenSync will be releasing three long-term (LTS) releases which can be used in production. Next release and milestone is mentioned in Download OpenSync .
...
What does monthly vs. long-term versioning look like?
| Code Block |
|---|
X.1.0
X.1.1
X.1.2 (Q1) -> LTS X.2.Y
X.3.0
X.3.1
X.3.2 (Q2) -> LTS X.4.Y
X.5.0
X.5.1
X.5.2 (Q3) -> LTS X.6.Y
X.7.0
X.7.1
X.7.2 (Q4) -> LTS X.8.Y
|
...
What is the difference between “mainline”, “stable”, and “longterm” releases?
Mainline - The latest stable release is marked as “mainline”. Although it has successfully exited its stabilization cycle, it is likely to be amended with “bugfix” releases.
Stable - Releases marked as “stable” typically already have a number of adopters, who use it in production. Additional “bugfix” or “maintenance” releases are less likely at this stage.
Long term - If a release is widely adopted, it may receive bug fixes for a longer period. Such releases are marked as “longterm” also known as long-term support branch (LTS).
Oldest Old releases are eventually ‘retired’ and are marked as “end-of-life”. Maintainers will not release any additional bug fixes for such releases. Adopters of existing integrations should consider moving to a newer stable release. No support will be provided for adopters wishing to create new integrations based on “end-of-life” releases.
...
Qualcomm
Broadcom
Mediatek
Maxlinear
Quantenna
NXP
Celeno
OpenWRT (All SoC supported under OpenWRT using platform/cfg80211. Reference board is Linksys MR8300)
All SoC supported under the RDK-B community. Reference board is Turris Omnia
Additionally, SoC vendors compliant to the open-source RDK and OpenWRT SDK and target layer APIs are supported. SDK and driver versions can be seen in Check Compatibility or Download OpenSync. If your platform is not listed here, please contact integration@opensync.io and let’s talk about how OpenSync can be supported on other SoC platforms.
...
What is the required BCM SDK version for OpenSync builds?
In Check Compatibility you will see, shows where OpenSync was stabilized and deployed. All other SDK which are not labeled, it doesn’t that is not compatible but maybe you will need Any deviations requires an adaptation. It is your responsibility to adapt OpenSync or SDK overlay to your flavor of SDK and best that you also upstream those the changes , so next OpenSync will include those changesto OpenSync.
...
How to synchronize OVSDB and TR-069/TR-181 data models?
...
FUT does not require any connection to the cloud, as the tests are intended to verify OpenSync implementation before going into next test stage and that is end to end test.
...
Is SSH access to the DUT necessary?
SSH management access (VLAN) to the device under test (DUT) is essential for FUT as well as for the OpenSync integration process in general. This is the default way to execute commands on devices.
...
Is CRATOS/OSRT
...
necessary to run FUT?
OpenSync Reference Testbed (OSRT) or Comprehensive Reference Apparatus for Testing OpenSync (CRATOS) / OSRT is mandatory to run FUT. In future we plan to give option to also be run outside of OSRT/CRATOS but that comes with limitation since some test requires additional HW like clients/power switch/…
...
Are any HW changes on OSRT/CRATOS supported?
The OSRT/CRATOS comes equipped with reference devices which are ready for executing of the FUT directly. To validate OpenSync integration on your devices, these devices will have to be used instead of the reference devices provided in OSRT/CRATOS reference devices.
...
Which modifications of the FUT are required to test my specific device?
...
If you detect that your tests are not passing after starting the OpenSync integration, use these steps to diagnose the cause of failures:
...