Project

General

Profile

Support #58437

Sepia Lab Access Request

Added by Pritha Srivastava about 1 year ago. Updated about 1 year ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
User access
Target version:
-
% Done:

0%

Tags:
Reviewed:
Affected Versions:

Description

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

I need VPN access and I will also be running teuthology jobs.

2) Desired Username:

prsrivas

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

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?

Matt Benjamin ()

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-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIJVFEYxlkN3FfEHN1LaTtTA/poYfzPNUlgFzXxlPkhNi prsrivas@redhat.com

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

prsrivas@fedora bWs83lQxql6KTc5km4vUeQ 50ad9843c3193166f0dc44ee7de8e4c85092710e38b10893045cd95339943832

History

#1 Updated by adam kraitman about 1 year ago

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

Hey Pritha Srivastava Are these new/additional or replacement credentials?

#2 Updated by Pritha Srivastava about 1 year ago

These are replacement credentials. The old one isn't needed as I had to regenerate the key.

#3 Updated by adam kraitman about 1 year ago

Hey Pritha Srivastava,

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

#4 Updated by Pritha Srivastava about 1 year ago

adam kraitman wrote:

Hey Pritha Srivastava,

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

Hi Adam,

I am unable to ping teuthology.front.sepia.com even though I am connected to the RH VPN. Also I had to re-instate openvpn profiles, because they disappeared for some reason. And this happened after creating this ticket, so do I need to generate new hashed VPN credentials?

Thanks,
Pritha

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.

#5 Updated by adam kraitman about 1 year ago

If you re-run the new-client script, It's unfortunately not idempotent so if you re-ran it and still have the output, we'll need the new string it printed. If you don't have the output, please re-run it again and send the new string.

#6 Updated by Pritha Srivastava about 1 year ago

prsrivas@fedora 13dmTf+3sbpan4iffbf1cw 65ea22c8ba7f49c3619ca9cf552a04400528b4114a53eafee715884cb3a04dea

#7 Updated by adam kraitman about 1 year ago

Hey please try now

#8 Updated by Pritha Srivastava about 1 year ago

I am unable to ssh, I see this error:

debug2: resolving "teuthology.front.sepia.ceph.com" port 22
debug3: resolve_host: lookup teuthology.front.sepia.ceph.com:22
debug3: ssh_connect_direct: entering
debug1: Connecting to teuthology.front.sepia.ceph.com [172.21.0.51] port 22.
debug3: set_sock_tos: set socket 3 IP_TOS 0x48
debug1: connect to address 172.21.0.51 port 22: Connection timed out
ssh: connect to host teuthology.front.sepia.ceph.com port 22: Connection timed out

#9 Updated by Pritha Srivastava about 1 year ago

able to ssh now, Thanks Adam!

Also available in: Atom PDF