Infrastructure » sepia

Hey Yingxin Cheng,

You should have access to the Sepia lab now. Please verify you're able to connect to the vpn and ssh yingxin@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.

Thanks! I'm still trying to find out a way to access the VPN behind proxy.

According to the OpenVPN documentation, there are two ways to connect through a proxy: http-proxy and socks-proxy.

It seems wrong to use http-proxy because it requires proto tcp, but the VPN server only supports udp from the error log:

• without proxy, baseline:
  

  SIGUSR1[soft,tls-error] received, process restarting
  TCP/UDP: Preserving recently used remote address: [AF_INET]8.43.84.129:1194
  UDP link local: (not bound)
  UDP link remote: [AF_INET]8.43.84.129:1194
  TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
  TLS Error: TLS handshake failed
  

• with http-proxy:
  

  SIGUSR1[soft,tls-error] received, process restarting
  TCP/UDP: Preserving recently used remote address: [AF_INET] <http-proxy>
  Attempting to establish TCP connection with [AF_INET] <http-proxy> [nonblock]
  TCP connection established with [AF_INET] <http-proxy>
  Send to HTTP proxy: 'CONNECT vpn.sepia.ceph.com:1194 HTTP/1.0'
  Send to HTTP proxy: 'Host: vpn.sepia.ceph.com'
  HTTP proxy returned: 'HTTP/1.1 503 Service Unavailable'
  HTTP proxy returned bad status
  

I’m also not able to use socks-proxy with the following error logs.

• with socks-proxy:
  

  SIGUSR1[soft,tls-error] received, process restarting
  TCP/UDP: Preserving recently used remote address: [AF_INET] <socks-proxy>
  Attempting to establish TCP connection with [AF_INET] <socks-proxy> [nonblock]
  TCP connection established with [AF_INET] <socks-proxy>
  UDP link local: (not bound)
  UDP link remote: [AF_INET]8.43.84.129:1194
  TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
  TLS Error: TLS handshake failed
  

Both proxies are working properly because “telnet 8.43.84.129 1194” is successful with tcp. But “nmap -sU -p 1194 8.43.84.129” is always failed with udp.

You must use a proxy? maybe let's configure it without a proxy first and later you can add a proxy

Thanks Adam, I've got the access to the sepia lab.