Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
slapos slapos
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Labels
    • Labels
  • Merge requests 122
    • Merge requests 122
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • slaposslapos
  • Merge requests
  • !1858

Open
Created Jul 21, 2025 by Joanne Hugé@jhugeMaintainer20 of 21 tasks completed20/21 tasks
  • Report abuse
Report abuse

WIP: simpleran/ors: new release (reorganize JSON Schemas, add parameters, update eNB/gNB configuration)

  • Overview 1
  • Commits 32
  • Changes 48

Current JSON input schemas do not pass tests because of wrong usage of "$ref" to include whole JSON input schema files into another, this is fixed in this MR by using allOf and unevaluatedProperties : d2a96fd1 (comment 237636)

However, this MR does not fix the other problematic usage of "$ref" such as here: https://lab.nexedi.com/nexedi/slapos/-/blob/master/software/simpleran/cell/nr/input-schema.json#L16 These have been here since a long time but were never detected in tests because they are in subfolders, and the tests simply searches for all JSON files in the root SR folder. One big issue for fixing this is that it seems to me there is no way to include a JSON input schema file and redefine it later to modify part of it (such as the title or description). /cc @kirr @jerome

ORS JSON Schemas have also been completely re-organized, and a migration script will be needed to upgrade ORS services. Since upgrading an ORS instance already takes some work (many clicks to do in panel) and is always done by ORS team this shouldn't cause too many issues. However since ORS services belong to Project clients and not to managers the procedure will be:

  • Feed service XML parameters to migration script
  • Paste back XML input using the panel Web GUI (we can't use CLI API since we don't own the service)

List of changes in this MR:

  • Reorganize JSON parameters: JSON Input Schema
  • Reorganize JSON parameters: Buildout
  • Fix Handover wrong configuration: https://support.amarisoft.com/issues/34946
  • Add websocket to core network
  • Update tests and add ORS Duo tests
  • Remove unused published parameters
  • Show default tac, add tac in connection parameters
  • Add required parameters for plmn, amf and mme lists
  • publish UL Frequency and ARFCN
  • eSIM needs res_len = 16 parameter
  • Change amarisoft.version published parameter to 20XX-XX-XX (Revision: XXX)
  • Redo GTP Address logic for Core Network and eNB / gNB
  • Add cipher_algo_pref, integ_algo_pref parameters
  • Add two NR TDD Frame Structure
  • Add all LTE TDD Frame configurations
  • Upgrade Amarisoft to newest version
  • Write parameter migration script
  • publish 4G 5G subnet on core network
  • Remove handover code duplication
  • Forbid additional parameters on json objects
  • Change objects to array in JSON schemas

/cc @tomo @lu.xu

Edited Jul 31, 2025 by Joanne Hugé
Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: ors-dev
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7