Versions Compared

Old Version 15

changes.mady.by.user Martin Skorupski

Saved on

compared with

New Version Current

changes.mady.by.user Paulo Costa

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

In the community lab at Rudgers University Winlab, called OWL (open wireless lab) are 12 bare metal servers running for 3 different and independent instances of ONAP.

Each of the three environments is build-out of three servers - one controller for the environment and three compute nodes.

Each environment exists for a different reason.

  • Experimental (EXPERI)
    • The name is self-explaining, here is an environment to test strange ideas and to figure out how it works. Everybody using this environment should be prepared for the unexpected. 
    • From time to time the entire setup will be wiped out - daily? weekly
  • Development (DEV)
    • The development environment is used to develop and test the current underdevelopment ONAP release.
    • continues integration and continues deployment are established. 
  • Stable (STABLE)
    • The stable environment runs the latest released ONAP version. Only officially updates are made. 

Status: 2020-05-03

Please update when you know the current status (wink)

Experimental

The environment is running! 

Blocked for MWC demos!

Development

The environment is down

The environment will be refactored until mid of January 2020.

Here code artifacts of ONAP El Alto with Frankfurt updates are installed.

The environment is used for automated and manually Integration Tests with existing radios, simulators and other complementary systems, including O-RAN-SC components.

Stable

The environment is down

The environment will be refactored until mid of January 2020.

ONAP El Alto version - as described: SDN-R with OOM Rancher/Kubernetes Installation

Physical setup

Experimental (target)

(initial setup: see Development environment) 

Server-OS: Ubuntu 18.04

OpenStack: stein (dual-stack; IPv4 and IPv6)

Kubernetes: 1.16 (IPV6 only) (currently IPv4 only)

1x Kubertnes cluster

  • Experimental

    • ONAP: pre-Frankfurt
    • Java11
    • ODL: neon (or sodium-SR1)

1x OpenStack Controller

3x Compute Nodes

DrawiobordertrueviewerToolbartruefitWindowfalsediagramNameENV-EXPERIsimpleViewerfalsewidthdiagramWidth193revision7

Development + Stable

Server-OS: Ubuntu 18.04

OpenStack: stein (dual-stack; IPv4 and IPv6)

Kubernetes: 1.16 (IPV4 only)

2x Kubertnes cluster

  • Development
    • ONAP: pre-Frankfurt
    • Java8
    • ODL: neon 
  • Stable
    • ONAP ElAlto (plus patches)
    • Java8
    • ODL: neon

3x OpenStack Controller

1x Load balancer for OpenStack controllers

6x Compute Nodes

DrawiobordertrueviewerToolbartruefitWindowfalsediagramNameENV-DEVsimpleViewerfalsewidthdiagramWidth493revision4How to access a VM using ssh

Table of Contents

Table of Contents



Introduction

Rutgers University's OWL (Open Wireless Lab) at WINLAB has 16 running bare metal servers.

In order to run several ONAP instances, the servers are split into "environments" or OpenStack instances.

Please note that the detailed setup may change at any point in time.

In addition, always be prepared in case your settings get lost. We make efforts to avoid this issue, but cannot guarantee it won't happen.

Sub pages:

Child pages (Children Display)

Planned: 2022-10-13

Hosts

Currently there is one gateway to control access from the internet into OWL and vice versa.

  • host: console.sb10.orbit-lab.org

Up to 6 servers act as control nodes for OpenStack instances.

The remaining 9 servers are a bit more powerful and are used as compute nodes for OpenStack instances.

Please note:

The entire domain "orbit-lab.org" does not answer ICMP pings. SSH is possible from the internet only to console.sb10.orbit-lab.org using your orbit-lab account username once you have uploaded your public key.

Inventory

Html bobswift

Setup

How to access a VM using SSH tunneling?
Once you have access and uploaded you your private keys, you may want to access a dedicated VM for your service.
In the following example, the IP of a running SDN-R is used to view the Web UI on your localhost the WebUi. Please replace '<username>' with the your the username of your orbit-lab.org account.
 Code Block
ssh -A -t <username>@console.sb10.orbit-lab.org -L 31202:localhost:31202 \
ssh -A -t native@exper-control-1 -L 31202:localhost:31202 \
ssh -A -t ubuntu@10.31.3.21 -L 31202:localhost:31202


Screenshot:
Image Added