forked from ChameleonCloud/docs
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
0 parents
commit 7e19657
Showing
381 changed files
with
40,748 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
# Sphinx build info version 1 | ||
# This file hashes the configuration used when building these files. When it is not found, a full rebuild will be done. | ||
config: 62c9285f16fe2cd036973936c421ae3e | ||
tags: 645f666f9bcd5a90fca523b33c5a78b7 |
Empty file.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,60 @@ | ||
.. _container-basic: | ||
|
||
========================= | ||
Running a basic container | ||
========================= | ||
|
||
This guide will walk you through the steps of running a very basic container on a worker node. | ||
|
||
Step 1: Reserve a worker node | ||
============================= | ||
|
||
See the "reservation of a worker node" section. | ||
|
||
Step 2: Create a container | ||
========================== | ||
|
||
* From the ExPECA home page, click *Container* -> *Containers* | ||
|
||
.. figure:: containers.png | ||
:alt: Containers main page | ||
:figclass: screenshot | ||
|
||
* Click *+ Create Container* | ||
* Under *Info* tab, give the container a name of your choosing, which can NOT contain the "underscore" (_) character | ||
* Type "alpine" as image name (or a Docker hub image of your choosing) | ||
|
||
.. figure:: create_container01.png | ||
:alt: Create container, first screen | ||
:figclass: screenshot | ||
|
||
* Under *Scheduler Hints* tab, add "reservation" as hint | ||
|
||
.. figure:: create_container02.png | ||
:alt: Create container, second screen | ||
:figclass: screenshot | ||
|
||
* Paste the "reservation ID" for the worker node lease you have created. Note that the | ||
"reservation ID" can be obtained from *Reservations* -> *Leases* -> click on your lease. | ||
|
||
.. figure:: lease_details.png | ||
:alt: Lease details | ||
:figclass: screenshot | ||
|
||
.. figure:: create_container03.png | ||
:alt: Create container, third screen | ||
:figclass: screenshot | ||
|
||
* Now click on *Create* to create your container. After a short time, the container is created, and by default should be running. | ||
|
||
.. figure:: running_container.png | ||
:alt: Running container | ||
:figclass: screenshot | ||
|
||
* Click on your container and then on the *Console* tab. You then have an interactive console where you can give commands in your | ||
container. It is created from a Linux image, so basic Linux commands are available. | ||
|
||
.. figure:: container_console.png | ||
:alt: Container console | ||
:figclass: screenshot | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,80 @@ | ||
.. _container-vs-ep5g: | ||
|
||
================================ | ||
Running a container towards EP5G | ||
================================ | ||
|
||
This guide will walk you through the steps of running a server container on a worker node, complete with networking definitions that allow | ||
clients using EP5G to communicate with the server container application. | ||
|
||
Step 1: Reserve a worker node | ||
============================= | ||
|
||
See the "reservation of a worker node" section. | ||
|
||
Step 2: Reserve EP5G and define edge networking | ||
=============================================== | ||
|
||
See the "Network definittion for EP5G" section. The subnet "10.70.70.0/24" subnet defined at the end there, for | ||
communication with a container in a worker node, will be used here towards the container application. | ||
|
||
Step 3: Create a container | ||
========================== | ||
|
||
We will here create a container with the "Openrtist" backend application. "Openrtist" has two parts, a client and a backend application. | ||
The client sends a video feed to the backend, which processes it and sends it back to the client with the appearance | ||
inspired by famous paintings. The client, in this case, will run on a user of the EP5G system. | ||
|
||
* From the ExPECA home page, click *Container* -> *Containers* | ||
|
||
.. figure:: containers.png | ||
:alt: Containers main page | ||
:figclass: screenshot | ||
|
||
* Click *+ Create Container* | ||
* Under *Info* tab, give the container the name "openrtist" | ||
* Type "cmusatyalab/openrtist:stable" as image name | ||
|
||
.. figure:: create_container01.png | ||
:alt: Create container, first screen | ||
:figclass: screenshot | ||
|
||
* Under *Networks* tab, click the arrow to the right of the network you have defined for local communication with containers. | ||
It will then move up to the "allocated" section. In this case, that network name is "edge-net" | ||
|
||
.. figure:: create_container02.png | ||
:alt: Create container, second screen | ||
:figclass: screenshot | ||
|
||
* Under *Labels* tab, define the network interface we will use in the worker node, the IP address to use for the container, and the running_container | ||
we will use to route traffic back towards the EP5G network. In this case, it is | ||
"networks.1.interface=ens1,networks.1.ip=10.70.70.30/24,networks.1.routes=172.16.0.0/16-10.70.70.1" | ||
* Note that the interface is picked from the Hardware Discovery section for your chosen worker node, the IP is picked from the subnet of your "local network", | ||
and the route back to EP5G uses the subnet of EP5G (172.16.0.0/16) and the default gateway of your "local network". "Local network", in this case, is | ||
"edge-net". | ||
|
||
.. figure:: create_container03a.png | ||
:alt: Create container, second screen | ||
:figclass: screenshot | ||
|
||
.. figure:: create_container03.png | ||
:alt: Create container, second screen | ||
:figclass: screenshot | ||
|
||
* Under *Scheduler Hints* tab, add "reservation" as hint | ||
* Paste the "reservation ID" for the worker node lease you have created. Note that the | ||
"reservation ID" can be obtained from *Reservations* -> *Leases* -> click on your lease. | ||
|
||
.. figure:: create_container04.png | ||
:alt: Create container, second screen | ||
:figclass: screenshot | ||
|
||
.. figure:: create_container05.png | ||
:alt: Create container, third screen | ||
:figclass: screenshot | ||
|
||
* Now click on *Create* to create your container. After a short time, the container is created, and by default should be running. | ||
* You should now be able to run the "openrtist" client from a user device using the EP5G system. The IP address of the server application would | ||
be the 10.70.70.30 address picked for the container in the worker node. | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,59 @@ | ||
.. _container-vs-public: | ||
|
||
==================================== | ||
Assigning a public IP to a container | ||
==================================== | ||
|
||
This guide will walk you through the steps of assigning a public IP to a container. | ||
This will allow worker node containers to have an IP address that can be used for access from the internet. | ||
|
||
.. figure:: public_ip.png | ||
:alt: Public IP networking | ||
:figclass: screenshot | ||
|
||
Step 1: Reserve a worker node | ||
============================= | ||
|
||
See the "reservation of a worker node" section. | ||
|
||
|
||
Step 2: Create a container | ||
========================== | ||
|
||
Here, we connect a container application, running on a worker node, to a public IP. This involves including the container in the "serverpublic" network | ||
when starting the container. | ||
|
||
* From the ExPECA home page, click *Container* -> *Containers* | ||
|
||
.. figure:: container_run1.png | ||
:alt: Containers main page | ||
:figclass: screenshot | ||
|
||
* Click *+ Create Container* | ||
* See "Running a basic container" for the steps involved. We will here only focus on the data entered for network connection. | ||
* Under "Networks" tab, bring "serverpublic" to the top | ||
* Under "Miscellaneous" tab, enter environment variables needed for the container. | ||
* Under "Labels" tab, enter a public IP address in the 130.237.11.[113-126]/27 range, as well as the "serverpublic" gateway. | ||
|
||
.. figure:: container_run2.png | ||
:alt: Containers networks page | ||
:figclass: screenshot | ||
.. figure:: container_run3.png | ||
:alt: Containers miscellaneous page | ||
:figclass: screenshot | ||
.. figure:: container_run4.png | ||
:alt: Containers labels page | ||
:figclass: screenshot | ||
|
||
* Click *Create* | ||
|
||
.. figure:: container_run5.png | ||
:alt: Containers main page | ||
:figclass: screenshot | ||
|
||
* You should now be able to connect with SSH to your container from the internet. | ||
|
||
.. figure:: container_run6.png | ||
:alt: Container console page | ||
:figclass: screenshot | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,56 @@ | ||
.. _container-vs-telenor: | ||
|
||
======================================== | ||
Running a container towards Telenor Edge | ||
======================================== | ||
|
||
This guide will walk you through the steps of defining networking for Telenor Edge. | ||
This will allow worker node containers, SDR networks (actually containers running on worker nodes), and EP5G to communicate with Telenor Edge applications. | ||
|
||
.. figure:: telenor_netw.png | ||
:alt: Telenor Edge networking | ||
:figclass: screenshot | ||
|
||
Step 1: Reserve a worker node | ||
============================= | ||
|
||
See the "reservation of a worker node" section. | ||
|
||
|
||
Step 2: Create a container | ||
========================== | ||
|
||
Here, we connect a container application, running on a worker node, to the Telenor Edge. This involves including the container in the "telenor-shared-net" network | ||
when starting the container. | ||
|
||
* From the ExPECA home page, click *Container* -> *Containers* | ||
|
||
.. figure:: container_run1.png | ||
:alt: Containers main page | ||
:figclass: screenshot | ||
|
||
* Click *+ Create Container* | ||
* See "Running a basic container" for the steps involved. We will here only focus on the data entered for network connection. | ||
* Under "Networks" tab, bring "telenor-shared-net" to the top | ||
* Under "Labels" tab, enter IP subnet and address to connect to the "telenor-shared-net" network, and to provide routing towards the Telenor Edge. | ||
|
||
.. figure:: container_run2.png | ||
:alt: Containers networks page | ||
:figclass: screenshot | ||
.. figure:: container_run3.png | ||
:alt: Containers labels page | ||
:figclass: screenshot | ||
|
||
* Click *Create* | ||
|
||
.. figure:: container_run4.png | ||
:alt: Containers main page | ||
:figclass: screenshot | ||
|
||
* You should now be able to ping Telenor edge from within your container. | ||
* In this case, we only ping the CPE Router (gateway to Telenor Edge), but you should be able to ping all the way to whatever application you have running on Telenor Edge. | ||
|
||
.. figure:: container_run5.png | ||
:alt: Container console page | ||
:figclass: screenshot | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,54 @@ | ||
===================== | ||
Welcome to Chameleon | ||
===================== | ||
|
||
.. toctree:: | ||
:maxdepth: 1 | ||
:caption: Introduction | ||
|
||
index | ||
getting-started/index | ||
|
||
.. toctree:: | ||
:maxdepth: 1 | ||
:caption: Use Cases | ||
|
||
case-1/index | ||
|
||
.. toctree:: | ||
:maxdepth: 1 | ||
:caption: Users and Projects | ||
|
||
user/federation | ||
user/pi_eligibility | ||
user/project | ||
user/profile | ||
user/help | ||
|
||
.. toctree:: | ||
:maxdepth: 1 | ||
:caption: Testbed interfaces | ||
|
||
technical/gui | ||
technical/cli | ||
technical/jupyter | ||
|
||
.. toctree:: | ||
:maxdepth: 1 | ||
:caption: Technical guide | ||
|
||
technical/index | ||
technical/discovery | ||
technical/reservations | ||
technical/baremetal | ||
technical/images | ||
technical/metrics | ||
technical/complex | ||
technical/swift | ||
technical/shares | ||
technical/networks | ||
technical/fpga | ||
technical/ep | ||
technical/sharing | ||
technical/daypass | ||
technical/kvm |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
================= | ||
Welcome to ExPECA | ||
================= | ||
|
||
.. toctree:: | ||
:maxdepth: 1 | ||
:caption: Introduction | ||
|
||
index | ||
|
||
.. toctree:: | ||
:maxdepth: 1 | ||
:caption: Testbed operation | ||
|
||
reservation-worker/index | ||
reservation-sdr/index | ||
reservation-advantech/index | ||
reservation-ep5g/index | ||
container-basic/index | ||
network-ep5g/index | ||
container-vs-ep5g/index | ||
container-vs-telenor/index | ||
container-vs-public/index | ||
|
||
|
Oops, something went wrong.