Support #55535: Sepia Lab Access Request - sepia - Ceph

Actions

Copy link

Support #55535

closed

Sepia Lab Access Request

Added by Tim Serong almost 2 years ago. Updated almost 2 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

adam kraitman

Category:

User access

Target version:

% Done:

Tags:

Reviewed:

Affected Versions:

Description

1) Do you just need VPN access or will you also be running teuthology jobs?

Both

2) Desired Username:

tserong

3) Alternate e-mail address(es) we can reach you at:

tserong@suse.com

4) If you don't already have an established history of code contributions to Ceph, is there an existing community or core developer you've worked with who has reviewed your work and can vouch for your access request?

If you answered "No" to # 4, please answer the following (paste directly below the question to keep indentation):

4a) Paste a link to a Blueprint or planning doc of yours that was reviewed at a Ceph Developer Monthly.

4b) Paste a link to an accepted pull request for a major patch or feature.

4c) If applicable, include a link to the current project (planning doc, dev branch, or pull request) that you are looking to test.

5) Paste your SSH public key(s) between the pre tags

ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAs6Qm1chlR0DVvDfkjqm7t+mjmXS/AkMBblcruV1qFTOYi4zkryJiqIUe/41gmDlMi4Nqa7dzgAoS/OPMCIXFE+XxyuhggvAa87YxDZCkE5XjZ54jbbSdRYn/xa/S3yLLAXhd2J8hfcBj2qmmosV/iT0pWQm5lXD7fQBqLiSt/5DyLzOFVL45oDYy2mN2u5VWBWrKXMPzCF2HQQWv4gISLBY1gF6WozNDChOrmujK6buMjdA29IbrjTZ1YykngeK8fCAxPTaXWdDxbY5fxPF1dw6xAWz3dvtre2OIcm1Z5Au9yuiMCecA5nb+OxFho8zOhwv1+bQmqpcM4kfjWYb33Q== tserong@suse.com

6) Paste your hashed VPN credentials between the pre tags (Format: user@hostname 22CharacterSalt 65CharacterHashedPassword)

tserong@thor VhPmkUKJdgNE/RJBN0nZvA 11671c34eb25c5fdff7f0002de197c1e72922a0e2122901d062a6d3ed758a9cf

Actions

Copy link

Updated by adam kraitman almost 2 years ago

Category set to User access
Status changed from New to In Progress
Assignee set to adam kraitman

Actions

Copy link

Updated by adam kraitman almost 2 years ago

Hey Tim, is there an existing community or core developer you've worked with who has reviewed your work and can vouch for your access request?

Actions

Copy link

Updated by Tim Serong almost 2 years ago

Category deleted (~~User access~~)
Assignee changed from adam kraitman to Yehuda Sadeh

adam kraitman wrote:

Hey Tim, is there an existing community or core developer you've worked with who has reviewed your work and can vouch for your access request?

Hey Adam, I've actually been around for a while, although I'm fairly quiet these days :-) The most recent reviews of my work are from Kefu and Ilya (see https://github.com/ceph/ceph/pull/45845 which is what I was going to test, although Ilya's since beaten me to that one).

Actions

Copy link

Updated by Tim Serong almost 2 years ago

Category set to User access
Assignee changed from Yehuda Sadeh to adam kraitman

OK, I did not mean to reassign that or mess up the category.

Actions

Copy link

Updated by adam kraitman almost 2 years ago

I am adding your user to the lab I will update once I finish

Actions

Copy link

Updated by adam kraitman almost 2 years ago

Hey Tim,

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

Actions

Copy link

Updated by Tim Serong almost 2 years ago

Hi Adam,

Thank you for that. I can connect to the openvpn OK, but can't seem to ssh to teuthology.front.sepia.ceph.com. I'm seeing the following:

> ssh tserong@teuthology.front.sepia.ceph.com
ssh: connect to host teuthology.front.sepia.ceph.com port 22: No route to host

> ping teuthology.front.sepia.ceph.com
PING teuthology.front.sepia.ceph.com (172.21.0.51) 56(84) bytes of data.
From 172.21.0.100 (172.21.0.100) icmp_seq=1 Destination Host Unreachable
From 172.21.0.100 (172.21.0.100) icmp_seq=2 Destination Host Unreachable
From 172.21.0.100 (172.21.0.100) icmp_seq=3 Destination Host Unreachable
From 172.21.0.100 (172.21.0.100) icmp_seq=4 Destination Host Unreachable
^C
--- teuthology.front.sepia.ceph.com ping statistics ---
6 packets transmitted, 0 received, +4 errors, 100% packet loss, time 5043ms

> /usr/sbin/traceroute teuthology.front.sepia.ceph.com
traceroute to teuthology.front.sepia.ceph.com (172.21.0.51), 30 hops max, 60 byte packets
 1  172.21.48.1 (172.21.48.1)  316.623 ms  326.574 ms  326.599 ms
 2  172.21.0.100 (172.21.0.100)  3331.015 ms !H  3331.216 ms !H  3331.260 ms !H

> ping 172.21.0.100
PING 172.21.0.100 (172.21.0.100) 56(84) bytes of data.
64 bytes from 172.21.0.100: icmp_seq=1 ttl=64 time=295 ms
64 bytes from 172.21.0.100: icmp_seq=2 ttl=64 time=315 ms
^C
--- 172.21.0.100 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 294.953/304.764/314.575/9.811 ms

So it looks like I can get as far as 172.21.0.100 (whatever that is), but can't get through(?) it to teuthology.front.sepia.ceph.com (172.21.0.51). Have you seen anything like this before?

Thanks

Actions

Copy link