Date: Thu, 28 Mar 2024 15:20:54 +0000 (UTC) Message-ID: <572881583.1110.1711639254128@759870d846b0> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1109_1159351662.1711639254122" ------=_Part_1109_1159351662.1711639254122 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The UNH-IOL hosts 38 HPE proliant x86 servers and 14 Gigabyte Cavium aar= ch64 servers. These machines are made freely available to the OPNFV develop= er community to develop, test, and improve the OPNFV platform.
You can access the web dashboard, where you can reserve a machine for yo= ur team, here: https://labs.lfnetworking.org/
Each x86 HPE server has:
We are in the process of upgrading the x86 based machines in accordance = with the needs of CNTT. As upgrades are completed, the specs of the x86 mac= hines will be:
Each arm cavium server has:
See the Lab as a Service 2.0 page= for up to date usage information.
To connect to the UNH-IOL openpvn server, you must download the file att= ached below. You also need to have an openpvn client installed on your mach= ine (most linux distributions ship with this by default).
Once you have the file, you may initiate the vpn connection. For example= , on a Linux client:
$ sudo = openvpn /path/to/laas_opnfv.ovpn
The VPN client will prompt you for a username and password. Your credent= ials will be in the email you received when booking your pod.
You may want to add our DNS server to your vpn client machine so that yo= u can resolve the hostname of your reserved server. Note that this = is not necessary.
The DNS server is reachable at 10.64.0.1. Please be careful when modifyi= ng your own network settings.
On a Linux client:
$ sudo = mv /etc/resolv.conf /etc/resolv.conf.bak $ sudo echo "nameserver 10.64.0.1" > /etc/resolv.conf
And then, after you are done on the vpn and want to restore your origina= l network settings:
$ sudo = mv /etc/resolv.conf.bak /etc/resolv.conf
Again, this is not a necessary step and it is recommended that you do no= t do this if you don't know what you are doing. It is possible to reach eac= h server by its ip address rather than its hostname.
See the Lab as a Service 2.0 page= for up to date usage information.
Every machine in LaaS has an IPMI port that you can use to control and m= onitor the power state of your server.
Your IPMI ip address and access account will be emailed to you when you = book a resource.
To use IPMI to control your server, use the Linux utility 'ipmitool'.
Sample usage:
$ ipmit= ool -I lanplus -L OPERATOR -U OPNFV -P <ipmi_password> -H <ipmi_ad= dress> chassis power status # gives you the current power status $ ipmitool -I lanplus -L OPERATOR -U OPNFV -P <ipmi_password> -H <= ipmi_address> chassis power <on/off/cycle> # turns your server o= n or off or reboots $ man ipmitool # for more information
Please first make sure that you can reach our vpn server, eg
$ ping = opnfv-vpn.iol.unh.edu
If you can ping the vpn server, but cannot establish a vpn connection, a= firewall is likely to be the culprit. Please verify that there is not a fi= rewall on your network that will block the vpn connection.
If something happens to your server, such as the networking getting misc= onfigured, the dashboard allows a way for you to reset your machine.
This will reinstall the operating system of your machine. This should fi= x any issues, but will also erase anything you had running or stored on the= machine.
If you have any more questions or issues, you may contact the IOL OPNFV = team at nfv-lab@iol.unh.edu. Please note that we will be happy = to assist with any problems related to the lab, but do not provide technica= l support for installing and maintaining OPNFV scenarios. The OPNFV install= er teams are very capable and willing to help you in that respect.
The Lab as a Se= rvice (LaaS) Acceptable Usage Policy (AUP) defines what is acceptable and n= ot acceptable in the LaaS community labs. These lab environments are sponso= red by the Linux Foundation, hosted by the UNH-IOL (https://www.iol.unh.edu) and made available to OPNFV community members f= or purposes of developing OPNFV features, testing deployments and deliverin= g releases.
LaaS resources = are controlled and scheduled through the Ph= aros LaaS Dashboard This system provides all user access, displays status of= available resources, and allows the scheduling of resources. Users m= ay not schedule resources in excess of what the dashboard permits.= p>
All dashboard u= sers must have approved Linux Foundation / controlled credentials. Co= ntrol / approval / granting of those credentials is outside the scope of th= is policy.
Hardware resour= ces are only to be used for their assigned purpose. Lab users should be con= tributors to an approved OPNFV project and be working on tasks that are for= planned project deliverables.
The maximum len= gth of time a user may book a resource is defined to be three weeks plus a = maximum of two additional extensions, each one week in length.
= li>Users may not "= host" or "assign" hardware resources to other projects or individuals witho= ut the approval of the UNH-IOL or Linux Foundation.
Hardware resour= ces that are not being actively used may be reallocated to another project = or user.
No data, softwa= re, or intellectual property that is not freely available to the community = may be downloaded or stored in/on the LaaS resource.
Users are respo= nsible for obtaining, monitoring and renewing any software licences require= d. No software may be downloaded or used in the lab without required licenc= es.
The UNH-IOL and= Linux Foundation reserve the right to audit software and lab usage without= notice and remove access of users who are not following this AUP.= p>
VPN Access
Users access to= LaaS resources is provided through an openvpn connection.
The IOL provide= s VPN access to the LaaS resources on a per-booking basis. Users may not sh= are their VPN credentials with others. Sharing of VPN credentials will resu= lt in permanent loss of access to the LaaS resources.
VPN access is c= reated automatically on the start date of a booked resource and terminated = automatically at the conclusion of the booking.
Network Bandwid= th
Available bandw= idth is limited and shared across all lab users.
Downloading exc= essively large files can interfere with other users therefore as a courtesy= the lab admin should be informed if users intend to download very large fi= les or consume substantial bandwidth for any duration.
Remote Console = Access
Access to the r= emote console access and ipmi power management will be given out on a per-b= ooking basis.
Causing or inte= nding to cause any damage or configuration change to the BIOS of the hosted= machines will result in permanent loss of access to the LaaS resources.
Console and pow= er management rights may be changed or removed at the Linux Foundation or U= NH-IOL=E2=80=99s discretion.
Support<= /p>
Support is prov= ided during normal business hours (assuming the USA East Coast time zone.)&= nbsp; Support outside of those hours is provided on a best effort basis onl= y.
Support request= s might take up to 24 business hours to be completed, depending on the requ= est.
For support, pl= ease contact nfv-lab@iol.unh.edu= .
<= /li>Any violation o= f this Acceptable Usage Policy may result in loss of VPN access and u= sage of the LaaS resources.
For more information about the UNH-IOL and it's participation in the OPN= FV projects, please visit our website here: https://www.iol.unh.edu/testing/open-networking/opnfv