Welcome to the Slices documentation hub!¶
This documentation site describes how you can get started on using the testbeds available in Slices, or how to integrate your testbed into the Slices Research Infrastructure.
To learn more about the Slices project, please visit the general Slices Research Infrastructure homepage.
Slices End User Documentation¶
This section guides you through the first steps into using the resources available within the Slices Research Infrastructure, and refers you to the proper documentation of each of the testbeds for more specific information.
An overview of the testbeds federated in Slices can be found on Slices Infrastructures overview.
To verify the current status of all testbeds federated within Slices, you can use the Federation Monitor.
For more information about the usage of each testbed, we refer to the specific documentation pages of each testbed:
- imec Virtual Wall (cloud, compute and networking testbed) documentation
- imec GPULabl (GPU, machine learning and AI testbed) documentation
- imec w-iLab.t (wireless and IoT testbed) documentation
- imec CityLab (wireless city testbed) documentation
- imec Portable wireless testbed documentation
- GRID’5000 (cloud, compute and networking testbed) documentation
- NITOS (wireless and IoT testbed) documentation
Testbed Owner Documentation¶
We have three ways of adding your testbed to the Slices Research Infrastructure:
- Light federation: access to the testbed’s resources is realized by exposing a Web-based GUI or Web-based API, with authentication through OAuth (offered by the Slices federation). This option does not allow full control over the individual testbed resources, but ensures unified access to experimenters. We support the OpenID Connect layer on top of the OAuth protocol and this link gives an idea of the metadata to be supported for the integration.
- Advanced federation: this is typically used for testbed resources which are accessible through ssh (including e.g. a testbed gateway or jumphost that is accessible through ssh). The testbed is fully integrated in the federation so that experimenters can interact with their experiment during all stages of the experiment’s life cycle (resource selection, instantiation, control, monitoring, etc.). This option requires the implementation of the Federation AM API (Aggregate Manager Application Programming Interface) on top of your testbed. You can find some possible ways to support the AM API . The GCF option is probably the best candidate if your testbed does not yet support the AM API.
- Associated testbed: there is no technical integration, but the testbed is just mentioned in the Slices Research Infrastructure overview. This is not further discussed here.
When you want to join Slices with your testbed, you can start with the following webinar (and accompanying slides): Fed4FIRE WP2: info for new testbeds.
Advanced federation: advanced topics¶
Useful links for advanced federation¶
Other useful links for AM developers:
- Almost all AM servers use the Geni AM API version 3.
- There is also a more generic AM API, the Federation AM API which has some extensions of the GENI AM API version 3, however, it is not completely finished, but the documentation is useful also for the Geni AM API v3. The API documentation is built from the github repo where you can discuss or change the API.
- Documentation on the Slice Authority and Member Authority APIs.
- More documentation on RSpec including info on the Fed4Fire RSpec extension for SSH Proxy.
- Use the Federation Monitor to monitor your testbeds status once the integration has been done
For more info, contact us at firstname.lastname@example.org