muriloavlis/oran-onosCustom docker image based on ONF's SDN ONOS Classic controller, developed for the OpenRAN@Brazil project.
Note: This repository contains the ORAN-ONOS image described in a paper written by Murilo Silva, Matheus Gomes, Victor Dias, Lucas B. Oliveira, Fernando Farias, Antônio Abelém entitled "Redes Definidas por Software para a Orquestração de Diferentes Domínios Tecnológicos" and published in XIV Workshop de Pesquisa Experimental da Internet do Futuro (WPEIF), DOI: [***] May 2023. Please cite the paper if you plan to use it in your publication.
To use the ONOS Classic image on Kubernetes, you need to add the Atomix and Onosproject repositories in Helm.
bashhelm repo add atomix [***] helm repo add onosproject [***] helm update
After adding the repositories, the installation command with Helm should be used to deploy the Atomix and ONOS Classic on the Kubernetes cluster. The following command installs 1 instance of ONOS Classic and Atomix in a namespace called onos-classic, disabling the pod affinity policy.
Note: Don't forget to replace "your-storage-class" with the corresponding storage class of your Kubernetes cluster.
bashhelm install onos-classic -n onos-classic --set atomix.podAntiAffinity.enabled=false --set podAntiAffinity.enabled=false --set replicas=1 --set atomix.replicas=1 --set image.repository=muriloavlis/oran-onos --set image.tag=latest --set atomix.image.tag=3.1.12 --set atomix.persistence.storageClass=<your-storage-class> onosproject/onos-classic --create-namespace
Note: To learn more about the options that can be used, see the section Installation Options with Helm.
Below is a table that presents the options that can be used during the installation of ONOS Classic with Helm, using the '--set' flag.
| Option | Description | Default Value | Change To |
|---|---|---|---|
| atomix.podAntiAffinity.enabled | Pod Affinity Policy for Atomix pods. With "PodAffinity" enabled by default, atomix pods will not start without 3 worker nodes. | true | false |
| podAntiAffinity.enabled | Pod Affinity Policy for ONOS Classic pods. With "PodAffinity" enabled by default, onos-classic pods will not start without 3 worker nodes. | true | false |
| atomix.replicas | Number of Atomix pods that will be instantiated. | 3 | - |
| replicas | Number of ONOS Classic pods that will be instantiated. | 3 | - |
| image.repository | Repository where the ONOS Classic image will be obtained. | onosproject/onos | muriloavlis/oran-onos |
| image.tag | Version of the ONOS Classic image that will be fetched from repository. | latest | latest |
| atomix.image.tag | Version of the Atomix image that will be fetched from repository. | latest | 3.1.12 |
| resources.requests.cpu | Number of CPUs used by ONOS Classic pods | 500m | - |
| atomix.resources.requests.cpu | Number of CPUs used by Atomix pods | 500m | - |
| resources.requests.memory | Amount of RAM memory used by ONOS Classic pods | 512Mi | - |
| atomix.resources.requests.memory | Amount of RAM memory used by Atomix pods | 512Mi | - |
| atomix.persistence.storageClass | Storage class to be used by Atomix to ensure data persistence | - | local-storage |
| atomix.persistence.size | Size of persistent storage to be created by each Atomix pod | 10Gi | - |
| atomix.persistence.enabled | Enables/disables persistent storage used by Atomix | true | true |
| apps | Applications to be launched with the ONOS Classic | {} | - |
[1] [***]
[2] [***]
[3] [***]
[4] [***]
探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
在 Linux 系统配置镜像服务
在 Docker Desktop 配置镜像
Docker Compose 项目配置
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
VS Code Dev Containers 配置
MacOS OrbStack 容器配置
在宝塔面板一键配置镜像
Synology 群晖 NAS 配置
飞牛 fnOS 系统配置镜像
极空间 NAS 系统配置服务
爱快 iKuai 路由系统配置
绿联 NAS 系统配置镜像
QNAP 威联通 NAS 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
无需登录使用专属域名
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
免费版仅支持 Docker Hub 访问,不承诺可用性和速度;专业版支持更多镜像源,保证可用性和稳定速度,提供优先客服响应。
专业版支持 docker.io、gcr.io、ghcr.io、registry.k8s.io、nvcr.io、quay.io、mcr.microsoft.com、docker.elastic.co 等;免费版仅支持 docker.io。
当返回 402 Payment Required 错误时,表示流量已耗尽,需要充值流量包以恢复服务。
通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。
先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。
使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
来自真实用户的反馈,见证轩辕镜像的优质服务