Project

General

Profile

Bug #58630

Sepia Lab Access Request

Added by Prashant D about 1 year ago. Updated about 1 year ago.

Status:
Fix Under Review
Priority:
Normal
Assignee:
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):

Description

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

2) Desired Username:
pdhange

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?

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 AAAAB3NzaC1yc2EAAAADAQABAAABgQDLGd4FKMA9fW9Jrz4DiMJvDFLcbXO2dV+pY5hZSM34hcGzNwYd9kijoRo/y4H/2GoVelEb8pI6eWW6lp4uYFEpZGf53pqk41w+a1t6kbn7kyX2eboMlsx5A+I97CtDxLn6qGiaMfOab+yWnu2TP0i40EJ6GGVUDDaRwNs0rGHtXVvg58jFEGdDojzuxixu/+YPIfUMTynL10XtOgBVXxMeHFmfsw7Z+YRuukhuj0nhALiaEdL5f14do7KKEPzBDYZQJCzBfLKCX1xmxakjF9J7wNVUAF5pQlJvN8aOlC/gBs4QsW0G4kbZ9Po1Ip4NujR4Rq0hqBZ7R84w7bJMCKnk9u2RchAf6ZdkkoFTWbsxLRsTAupbMND319QVejd5XSJY93FXn1PY041wCp/HT/Z/ihAYv4D3h4MUNuWTsQXOWbrs8xwcG6PHXKlPuZh+5ofBx6E6SON3gV3u8zI+I16PWBmUV4PnXIU8rNmAsEQT1Y8lqALjM3FBg1CZLfwm+x0= prashant@shesha

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

pdhange@shesha 5kgV9m4hyYIY7mXatRrlWA f44687b474d9f7096c0ab6829229ad49e130e4616fd65d46c3e1d882cd991a6d

History

#1 Updated by Prashant D about 1 year ago

Hi Adam,

These are my replacement VPN credentials as I need to move sepia VPN client to VM.

#2 Updated by Prashant D about 1 year ago

  • Status changed from New to Fix Under Review
  • Assignee set to adam kraitman

#3 Updated by adam kraitman about 1 year ago

Hey Prashant Dhange,

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.

Also available in: Atom PDF