The UNH-IOL currently hosts the Akraino Shared Community Lab. The Community Lab provide resources to the Akraino and LF Edge development communities, through the support of the Linux Foundation and donation from participants. The lab was initially founded in April 2019, and is working to add additional resources. These pages, hardware lists, and documentation will be updated as resources become available.
Access to the lab and its resources is controlled through an OpenVPN connection. Each user needs an account, currently created and maintained by the lab host (see below). Once connected to the VPN, users will have access to the pods and networking equipment in the community lab. Each pod has a primary and secondary contact for the pod, who is responsible for the oversight and sharing of the pod resources. Please do not make changes to a pod without coordinating with the pod contacts.
Each pod consists of 1 or more servers and networking fabrics (one or more switches). A pod is intended to be a self contained unit, where the pod user is able to make changes to the networking configuration or enable SDN control of the network / switch.
The community lab project is part of the CI, Blueprint Validation Lab TSC Subcommittee. To request resources within the lab for your plugfest, please complete the Lab Topology Template for BluePrints and submit it to the Subcommittee for review.
Lab documentation is being moved over to the LF Edge Wiki, as lab operation and oversight is assumed by the LF Edge TAC and the lab subcommittee
Host & Pod Access
This will be slightly different for each pod, but each pod will have an IPMI/LOM connection available. This connection will be reachable through the VPN and from the public network of the pod, and can be used to control the automated install or deployment onto the pod, depending on the desired blueprint. Each pod has its own documentation page in this wiki space.
|ThunderX2 Pod #1
|ThunderX2 Pod #2
|Intel Pod 1
|Intel Pod 2
|Intel Pod 3
|Intel Pod 4
|Ampere Pod 1
|Ampere Pod 2
Acceptable Usage Policy
Acceptable Usage Policy, v2.0 - Approved January 30, 2020