Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The diagram below shows the current configuration.  The entry point is an Ubuntu machine console.sb10.orbit-lab.org on which you will have an account.  There are currently three Ubuntu 18.04 servers: node1-1, node2-1 and node2-2, which are managed by OpenStack (several other servers will arrive the week of Nov. 4).  Node1-1 is the controller node, and node2-1 and node202 are compute nodes.  The console and the three servers are connected by two networks: control (10.30.0.0/16) and data (10.31.0.0/16).  All of the physical wireless network equipment, shown in the far right of the diagram, will be connected to the data network.  The 10.50.30.0/16 network on the left supports access from the grfeater greater Internet, and the network 10.1.110.0/16 is internal and used for out-of-band interfaces to the machines.  These latter two networks are of less interest for the proof-of-concept.  All machines and VMs created in the servers have outbound access to the greater Internet via the sw-rt1-top machine shown on the bottom with a NAT and firewall.

...

We use OpenStack (Rocky version) to manage the servers.  Team members can obtain an OpenStack account to create and manage their VMs.  We have installed ONAP using the OOM Rancher/Kubernetes instructions into four VMs, shown here.

Image Added

Access using ssh tunnels

Team members will want to access the OpenStack Horizon dashboard, the Rancher GUI, and their VMs.  Because these resources are on private networks, the only means of access is a ssh tunnel through console.sb10.orbit-lab.org.    The following are example commands that create these tunnels.  If others can provide more efficient methods of creating the tunnels, please share them by editing this page.

To access the OpenStack Horizon dashboard

This command opens a tunnel from one's local machine to the dashboard.

Code Block
ssh -A -t -l <username>@console.sb10.orbit-lab.org -L 8585:localhost:8585 \
ssh -A -t -l <username>@node1-1 -L 8585:localhost:80


The dashboard is listening on port 80, and this command creates a multi-hop ssh tunnel that listens on port 8585, which is a random high number port, on one's local machine and relays through the console to appear at port 80 on node1-1.  Team members can then access the dashboard by opening a browser on their local machine and navigating to http://localhost:8585/horizon/auth/login.  Before executing the command, though, team members should install their public keys in each machine in the multi-hop tunnel in the ~/.ssh/authorized_keys file.

To access the Rancher GUI

You can access the Rancher GUI by opening a tunnel with this command.

Code Block
ssh -A -t <username>@console.sb10.orbit-lab.org  -L 9999:localhost:9999 \
ssh -A -t <username>@node1-1                     -L 9999:localhost:9999 \
ssh -A -t <username>@<ip-address-of-sb4-rancher> -L 9999:localhost:8080

In this tunnel, one can access the Rancher GUI by opening a browser on a local machine and pointing it to http://localhost:9999/env/1a7/infra/stack.  As before, 9999 is a random high number port and public keys should be installed in each machine in the tunnel.