edgenos

KO | EN

gitlite — search

#typescript #ai-agents #ai #dsh-plugin #deepseek-harness #open-source #cli #claude-code #codex #developer-tools #react #windows

★ 57 Open GitHub ↗

EdgeNOS: a unified, multi-architecture / multi-ASIC network OS for bare-metal switches — Edgecore AS5610-52X (PowerPC/BCM56846) and AS4610-54T (ARM/Helix4 BCM56340)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# EdgeNOS

A unified, **multi-architecture / multi-ASIC** network operating system build system.
One **switch database** describes every supported switch; from it, EdgeNOS builds a
**per-switch ONIE installer** carrying a base system for that CPU + ASIC plus its
software components as packages.

Pick your switch → download its installer → `onie-nos-install`. That's it.

```
$ edgenos catalog
EdgeNOS 0.1.0 — supported switches

MODEL                  ARCH     ASIC       KERNEL  STATUS      DOWNLOAD
accton as4610-54       armhf    bcm56340   6.1     production  EdgeNOS-0.1.0-arm-accton-as4610-54-r0.swi
accton as5610-52x      powerpc  bcm56846   6.1     production  EdgeNOS-0.1.0-powerpc-accton_as5610_52x-r0.bin
```

## How it fits together

Four layers, each feeding the next — all driven by the switch database:

```
switchdb/         one YAML per switch (arch, asic, kernel, component list)
   │              + per-axis entries: arch/<arch>.yml, asic/<asic>.yml
   ▼
.epk packages     each software piece, tagged <name>_<ver>_<arch>-<asic>.epk
   │                base   = the whole base rootfs (one per switch)
   │                edged/bcmd/quagga/bde/platform-svc = the components
   ▼
imgbuild          base + components → stamp version → squashfs → installer
   │
   ▼
ONIE installer    one downloadable file per switch (.bin or .swi)
```

The three axes — **arch** (CPU), **asic** (silicon), **platform** (board) — are kept
orthogonal, so adding a switch is data + a folder, never a fork. The platform layer is
ONL-inspired (a per-board class with `baseconfig()` + an ONLP-style HAL + a resolver),
but images are **per switch**, not one-image-per-arch. See [`DESIGN.md`](DESIGN.md) and
the [ONL comparison](DESIGN.md#prior-art-onl-and-where-edgenos-mirrors-vs-differs).

## Install on a switch

Each switch has its own page under [`docs/switches/`](docs/switches/). In short:

```sh
# on the switch, in ONIE install mode:
onie-nos-install http://<server>/EdgeNOS-<ver>-<your-switch>.<bin|swi>
```

Download the file from [Releases](../../releases).

## CLI

```sh
edgenos catalog                       # the "pick your switch" index
edgenos db validate | show <plat>     # the switch database
edgenos version <plat>                # the build identity for a switch
edgenos pkg base  --from <rootfs> …   # capture a base system as a package
edgenos pkg build <spec> …            # build a component .epk
edgenos pkg install|verify|list …     # on-box package manager (epkg)
edgenos build <plat>                  # assemble that switch's ONIE installer
edgenos platform name|show|init       # resolve / bring up the board (ONL-style)
edgenos docs                          # regenerate the per-switch instruction pages
```

## Build from source

The datapath compiles in a cross-build container (no host toolchain needed):

```sh
build/build-sdk-and-edged.sh                 # AS5610: OpenMDK SDK libs + linked edged (PowerPC)
edgenos pkg build packaging/specs/as5610-52x/edged.yml --source-root .. --arch powerpc --asic bcm56846
edgenos build powerpc-accton_as5610_52x-r0 --source-root ..
```

The AS5610 `edged` is built from this tree (verified: 11/11 sources compile + link to an
18.8 MB PowerPC binary). The AS4610 `bcmd` builds via its OpenBCM recipe (`build-bcmd.sh`).

## Layout

| Dir | What |
|-----|------|
| `switchdb/` | the database — platforms, archs, asics, JSON schema |
| `core/` | shared, arch/ASIC-agnostic code (`datapath/`, `control-plane/`, `platform/`) |
| `arch/<arch>/` | per-CPU toolchain + build fragments |
| `asic/<asic>/` | per-ASIC SDK glue + chip code |
| `platform/<board>/` | per-board: drivers, config, DTS, services, platform class |
| `packaging/` | `version/` stamper, `pkgtool/` (.epk + on-box `epkg`), `specs/`, `imgbuild.py` |
| `images/` | per-platform image recipes |
| `build/` | cross-build scripts |
| `tools/`, `bin/` | DB/catalog/docs tooling + the `edgenos` CLI |
| `docs/switches/` | per-switch install pages (generated) |

## Status

Production-capable on two switches (AS5610-52X, AS4610-54T), both fully package-composed
and self-describing (each image records its component list under
`/var/lib/edgenos/epkg/installed`). The unified AS5610 `edged` is built and linked from
source. Adding a third switch is a `switchdb/` entry + a `platform/<board>/` folder.

## Licensing

All components are distributable. Kernel / BDE-KNET / Buildroot / Quagga are GPL; the
Broadcom OpenBCM SDK, OpenMDK, and PHY firmware are source-available (distribution +
derivative grant). Keep the Broadcom notices; the result is source-available, not pure
OSI. See the per-component licenses.

edgenos

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README