Infrastructure » sepia

Hey Dhairya Parmar,

You should have access to the Sepia lab now. Please verify you're able to connect to the vpn and ssh dparmar@teuthology.front.sepia.ceph.com using the private key matching the pubkey you provided.

Be sure to check out the following links for final workstation setup steps:
https://wiki.sepia.ceph.com/doku.php?id=vpnaccess#vpn_client_access
https://wiki.sepia.ceph.com/doku.php?id=testnodeaccess#ssh_config

Most developers choose to schedule runs from the shared teuthology VM. For information on that, see http://docs.ceph.com/teuthology/docs/intro_testers.html

If you plan on scheduling tests, one of the options you'll need to set with teuthology-suite is -p, --priority. Please refrain from using a priority lower than 101 (lower number = higher priority). When a high priority is used, it locks up too many testnodes at once and prevents other developers from testing changes.

Thanks.

adam kraitman wrote:

Hey Dhairya Parmar,

You should have access to the Sepia lab now. Please verify you're able to connect to the vpn and ssh dparmar@teuthology.front.sepia.ceph.com using the private key matching the pubkey you provided.

Be sure to check out the following links for final workstation setup steps:
https://wiki.sepia.ceph.com/doku.php?id=vpnaccess#vpn_client_access
https://wiki.sepia.ceph.com/doku.php?id=testnodeaccess#ssh_config

Most developers choose to schedule runs from the shared teuthology VM. For information on that, see http://docs.ceph.com/teuthology/docs/intro_testers.html

If you plan on scheduling tests, one of the options you'll need to set with teuthology-suite is -p, --priority. Please refrain from using a priority lower than 101 (lower number = higher priority). When a high priority is used, it locks up too many testnodes at once and prevents other developers from testing changes.

Thanks.

Hi Adam,

I was following https://wiki.sepia.ceph.com/doku.php?id=vpnaccess#vpn_client_access in order to start the openvpn service, seems like upon `sudo systemctl restart openvpn-client@sepia`, it's failing and the status says that it cannot find sepia.conf -> `/usr/sbin/openvpn --suppress-timestamps --nobind --config sepia.conf`, and i can see that there is no config file `sepia.conf` at /usr/sbin/openvpn. Could you please help bring some light on it. Below you can find the log:

[dparmar@fedora sepia]$ sudo systemctl restart openvpn-client@sepia
Job for openvpn-client@sepia.service failed because the control process exited with error code.
See "systemctl status openvpn-client@sepia.service" and "journalctl -xeu openvpn-client@sepia.service" for details.
[dparmar@fedora sepia]$ sudo systemctl status openvpn-client@sepia
× openvpn-client@sepia.service - OpenVPN tunnel for sepia
Loaded: loaded (/usr/lib/systemd/system/openvpn-client@.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2022-03-31 15:37:02 IST; 1s ago
Docs: man:openvpn(8)
https://community.openvpn.net/openvpn/wiki/Openvpn24ManPage
https://community.openvpn.net/openvpn/wiki/HOWTO
Process: 206866 ExecStart=/usr/sbin/openvpn --suppress-timestamps --nobind --config sepia.conf (code=exited, status=1/FAILURE)
Main PID: 206866 (code=exited, status=1/FAILURE)
CPU: 12ms

Mar 31 15:37:02 fedora systemd¹: Starting OpenVPN tunnel for sepia...
Mar 31 15:37:02 fedora openvpn²⁰⁶⁸⁶⁶: Options error: In [CMD-LINE]:1: Error opening configuration file: sepia.conf
Mar 31 15:37:02 fedora openvpn²⁰⁶⁸⁶⁶: Use --help for more information.
Mar 31 15:37:02 fedora systemd¹: openvpn-client@sepia.service: Main process exited, code=exited, status=1/FAILURE
Mar 31 15:37:02 fedora systemd¹: openvpn-client@sepia.service: Failed with result 'exit-code'.
Mar 31 15:37:02 fedora systemd¹: Failed to start OpenVPN tunnel for sepia.
[dparmar@fedora sepia]$ cat /usr/sbin/openvpn
ca.crt client.conf new-client secret tlsauth

Solved over gchat this is the new vpn cred
dparmar@thinkpad r8pTNS583rP4483MZ9Z69w c452859abbc87e8aad042cf0293d1b3e18090d147319722a1e29a9716e13aa88