Support #42212

Sepia Lab Access Request

Added by rakesh manohar 10 months ago. Updated 10 months ago.

User access
Target version:
% Done:


Affected Versions:


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

2) Desired Username:

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

rakesh@fedora Rupc3dkcIu4knrqd0It3JQ b1dc5f41a65c2403790b0048e1488b0e5ae40c7d5a3a284cd25b64640d20e587

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

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDEOigBGMeElb3uHXX36HxLtPJMG+iG/6D7NDFCVR6AyYsmimBQb6SlSIR6SaFULb6HT/IFVk0Jf/z0HoipAP7Xu+wvP/J6LFoMdguxylh1ov8raqxQJrGLl9n64EI+qWINwEM0MKMUnDQ3tmMKBl78LKQVQTYBx1+9cXsT6DE1yhgmV79XIvOOb+v53agSi/kLJF2i9K04kpi1OejXg95Ub2eLMY69Jm8PnLy1Jq8DhC8pz7nrfzbKtOC7HbytTAO1XTlb90lVhqC/1yTMAUc/rpJwoSEHc2epGeZWdMsJhqhX2EqMwcV53M3qcFSGreGNJ/Ncd4/JHxz7q0IU411t rakesh@localhost.localdomain


#1 Updated by rakesh manohar 10 months ago

hi please ignore the above keys, use below.

ssh-public key:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDEOigBGMeElb3uHXX36HxLtPJMG+iG/6D7NDFCVR6AyYsmimBQb6SlSIR6SaFULb6HT/IFVk0Jf/z0HoipAP7Xu+wvP/J6LFoMdguxylh1ov8raqxQJrGLl9n64EI+qWINwEM0MKMUnDQ3tmMKBl78LKQVQTYBx1+9cXsT6DE1yhgmV79XIvOOb+v53agSi/kLJF2i9K04kpi1OejXg95Ub2eLMY69Jm8PnLy1Jq8DhC8pz7nrfzbKtOC7HbytTAO1XTlb90lVhqC/1yTMAUc/rpJwoSEHc2epGeZWdMsJhqhX2EqMwcV53M3qcFSGreGNJ/Ncd4/JHxz7q0IU411t

hashed VPN credentials
rakesh@fedora Rupc3dkcIu4knrqd0It3JQ b1dc5f41a65c2403790b0048e1488b0e5ae40c7d5a3a284cd25b64640d20e587

#2 Updated by David Galloway 10 months ago

  • Assignee set to adam kraitman

The SSH key is the same we already have so we can just add the VPN creds to ceph-sepia-secrets and push.

#3 Updated by David Galloway 10 months ago

  • Status changed from New to 4
  • Assignee changed from adam kraitman to David Galloway

Hi Rakesh,

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:

Most developers choose to schedule runs from the shared teuthology VM. For information on that, see

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.


#4 Updated by rakesh manohar 10 months ago

Hi David,

my machine crashed, I was able to get the ssh key backup but not the client credentials.
Here is my new VPN client key, can you remove the old one add this, please.



#5 Updated by David Galloway 10 months ago

  • Status changed from 4 to Resolved

Rakesh and I worked this out over Hangouts.

Also available in: Atom PDF