Project

General

Profile

Support #52924

Sepia Lab Access Request

Added by Prashant D 3 months ago. Updated 13 days ago.

Status:
Resolved
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?
Both

2) Desired Username:
prashant

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?
I am working with RADOS team now and have been contributing to upstream Ceph.

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 AAAAB3NzaC1yc2EAAAADAQABAAABAQCoeyVaMjhcGrWQB+4Rq+SSIi8+OY/kx2s1vofiGt1gu3RNtFmG0Df1VITJJ32dbzaW7kTNxaRvhldNd/n7yEMssG+Wg+a5WKvSudlbVMmscbSXdFuVbcCW1jNrTGCYrxL7Sn5e7NQEQfAsCbfXwTcYBw33NdBVovC+gs2V3sZGvX3Y0akZONNuVg1mhu0L4m1/5IegJh005KeilwetHA2A5Dr10RG6oyIgT7t4z5gZXsrOiG3UQBXaekILYV9jxMWoFXGkVLc8TpL9SUAdxE3Owc0u1XiPqYYlEN+zDvE0554Zj8Oc2ZO6HRXCZXQFvzXeCD12YswcOfkIDmJRF7GT prashant@mauli

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

prashant@mauli USJcesLtEC1JyDZ7oZ81Rg dd963bbe895d1d1abde3e09b4c08d105249a22d9f7ade1c648b30ffbb04c4047

History

#1 Updated by Prashant D 3 months ago

@David and Adam,

I am having trouble with my VPN client setup on VMs (old ticket https://tracker.ceph.com/issues/48160). I am now trying to setup on my laptop.

#2 Updated by adam kraitman 3 months ago

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

#3 Updated by adam kraitman 3 months ago

Hey Prashant your username in the sepia gateway is "pdhange" we don't recommend changing the username
Please regenerate the vpn credentials using this username and paste it here

#4 Updated by Prashant D 3 months ago

Hey Adam. Thank you for looking into it.

I have cleaned up the sepia directory along with sepia.conf file and re-generated client credentials.

client credentials :

pdhange@mauli hqKEk1OuI2Wmi1CAcJk5CQ f49d854572b5efe9514b4d741e336adb3534d00b22b0a505142d82eccc2f7535

Can you also add below additional SSH public key for pdhange ?

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDCG54YhVGirRaEQtpNyBkXT+/HgJzOIY7Y2zmeoYYRr3mosa599Ns3KsFJXpiTOrkM2CbpxlfTkZGewZ40eK8dBLYpAKspOwN19ZcfaKsRA7Dhluhoc2goBhwFrcWhrNC8vOwwrwXgzSxwpfGoNfkcboOnhBwobiiM4qyHd4sUJwtuSFScAqHFa14S+Yxg17loFaPt5GyaSocgasYPVDzTpFLEdWwa542/mUr9hDovk8R7MCOZlztml0QMJ1OCKunfufbvR35AcFY4VmeW0jpQw6HjUq658sITgHEEITY+aMbhAHckzG47mQzF3JPPkv4D5SwERAKKfAIJlnr3Hghl pdhange@mauli

#5 Updated by adam kraitman 3 months ago

Prashant D wrote:

Hey Adam. Thank you for looking into it.

I have cleaned up the sepia directory along with sepia.conf file and re-generated client credentials.

client credentials :
pdhange@mauli hqKEk1OuI2Wmi1CAcJk5CQ f49d854572b5efe9514b4d741e336adb3534d00b22b0a505142d82eccc2f7535

Can you also add below additional SSH public key for pdhange ?
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDCG54YhVGirRaEQtpNyBkXT+/HgJzOIY7Y2zmeoYYRr3mosa599Ns3KsFJXpiTOrkM2CbpxlfTkZGewZ40eK8dBLYpAKspOwN19ZcfaKsRA7Dhluhoc2goBhwFrcWhrNC8vOwwrwXgzSxwpfGoNfkcboOnhBwobiiM4qyHd4sUJwtuSFScAqHFa14S+Yxg17loFaPt5GyaSocgasYPVDzTpFLEdWwa542/mUr9hDovk8R7MCOZlztml0QMJ1OCKunfufbvR35AcFY4VmeW0jpQw6HjUq658sITgHEEITY+aMbhAHckzG47mQzF3JPPkv4D5SwERAKKfAIJlnr3Hghl pdhange@mauli

Hey Prashant, I am not sure I understood, Are these new/additional or replacement credentials ?

#6 Updated by Prashant D 3 months ago

Hi Adam,

adam kraitman wrote:

Prashant D wrote:

Hey Adam. Thank you for looking into it.

I have cleaned up the sepia directory along with sepia.conf file and re-generated client credentials.

client credentials :
pdhange@mauli hqKEk1OuI2Wmi1CAcJk5CQ f49d854572b5efe9514b4d741e336adb3534d00b22b0a505142d82eccc2f7535

Above are the replacement VPN credentials as we donot allow changing username. On sepia gateway, my username is registered as "pdhange" hence re-generated client VPN credentials with "pdhange" username.

Can you also add below additional SSH public key for pdhange ?
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDCG54YhVGirRaEQtpNyBkXT+/HgJzOIY7Y2zmeoYYRr3mosa599Ns3KsFJXpiTOrkM2CbpxlfTkZGewZ40eK8dBLYpAKspOwN19ZcfaKsRA7Dhluhoc2goBhwFrcWhrNC8vOwwrwXgzSxwpfGoNfkcboOnhBwobiiM4qyHd4sUJwtuSFScAqHFa14S+Yxg17loFaPt5GyaSocgasYPVDzTpFLEdWwa542/mUr9hDovk8R7MCOZlztml0QMJ1OCKunfufbvR35AcFY4VmeW0jpQw6HjUq658sITgHEEITY+aMbhAHckzG47mQzF3JPPkv4D5SwERAKKfAIJlnr3Hghl pdhange@mauli

Hey Prashant, I am not sure I understood, Are these new/additional or replacement credentials ?

You donot need to add new public SSH keys for username "pdhange" if SSH public key for prashant user (mentioned in comment#0) can be used for accessing sepia nodes.

#7 Updated by adam kraitman 3 months ago

Hey Prashant,

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.

#8 Updated by Prashant D 3 months ago

Thanks Adam. I am able to access sepia lab now.

#9 Updated by adam kraitman 13 days ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF