Index: script.txt ================================================================== --- script.txt +++ script.txt @@ -82,27 +82,28 @@ - support testbed spanning different CNs? *##* * Community-Lab testbed architecture ** Overall architecture This is the architecture developed by the CONFINE project to handle the -previous challenges. It applies to all testbeds using CONFINE software. *##* +previous challenges. It applies to all testbeds using CONFINE software. -# Axel: Introduce scenario: CNs, nodes, admins. -# Ivan: Don't zoom. -- A testbed consists of a set of nodes managed by the same server. *##* +Here you see two CNs with several nodes connected to them, all managed by +their respective admins. + +- A testbed consists of a set of nodes managed by the same server. - Server managed by testbed admins. - Network and nodes managed by CN members. - Node admins must adhere to testbed terms and conditions. - - This decouples testbed management from infrastructure ownership & mgmt. *##* + - This decouples testbed management from infrastructure ownership & mgmt. - Testbed management traffic uses a tinc mesh VPN: - Avoids problems with firewalls and private networks in nodes. - Uses IPv6 to avoid address scarcity and incompatibility between CNs. - - Mgmt connections are short-lived to tolerate link instability. *##* + - Mgmt connections are short-lived to tolerate link instability. - Gateways are entry points to the mgmt network. - They help extend it over multiple CNs by external means (e.g. FEDERICA, the Internet). - - They can also route the management network to the Internet. *##* + - They can also route the management network to the Internet. - Researchers run experiments in slices spread over several nodes (as slivers). *##* ** Slices, slivers and nodes # Axel: Reverse, from PoV of researcher: select nodes, run as slivers, gruop in slices. Index: slides.svg ================================================================== --- slides.svg +++ slides.svg cannot compute difference between binary files