Support #62416


Sepia Lab Access Request

Added by Vallari Agrawal 9 months ago. Updated 8 months ago.

In Progress
User access
Target version:
% Done:


Affected Versions:


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

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?
I have history of code contributions to 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 AAAAB3NzaC1yc2EAAAADAQABAAACAQCn0DXBoHzMzFYTgo8XVGQz2GDRHBa1e63gwH5LOIFjGQFUGUTxxOxlEU/tsHP/MgmJrRZV/4A5VPf6qlCVwhLBXTekfRC+zOF1+C4uEUhhwXsU4Ame0UH6s1VkzbwH3wyxh3lOOoOqSASEkPJAaYIskj1KYbbw5zdz9p5mMSrlvRP9X59oaXdn4Ir0QU7f9cfxUBZcDdKVI26+PHVEIf8WMSEih2RUTotGgRMG705lfzTC51yeFvlcJYKjlBO7x4NJqf/AmiUEBY+2qP1aZApyRevBqfTzWmVcLWfh/BR0pXZSbJA+ce5yW3lvhhXFGZIDg7VZv7llu+CJ1QZM7nOL5ihjmTKZeRCTZhvtTRASw6M5O1BY4SnFS3scL+wB1t6UWmQD1rj4T99L3QsUx7Jm0GhSr8ymLKOv//YB53wfU8eRaUh5WM/NZI09emYM1/FGCyi94XCuvJRjVo7KMe/bThq+okQXYxjPJQMpBfs+PCFiD5vTMkWbsPMq9ZGyWnM3XTm/ciVrvdQAyLG0djS9PAL3QAqgA2hPOWJtQSsQyr1OH11CFnyiW3CiRkILT5BCf+l9cHOjG8rLZK15MD1wg73Touv6NtsZw/KS21TJKNGk802Bq6+57keEYSVniAowZ+zk8Kq+4DsO+ZyraSHT/P2yHU/Aixo/9TYEt181LQ== vallari@Vallaris-MacBook-Pro.local

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

vallariag@ibmmac UnflP9qfF8xHeU76uB7zhw bba7e4a5823b912df371a13c10c64d86a47aae8d5c7161ea31b63e99c734c29d

Actions #1

Updated by adam kraitman 8 months ago

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

Updated by adam kraitman 8 months ago

Hey Vallari, Are these new/additional or replacement credentials?

Actions #3

Updated by Vallari Agrawal 8 months ago

Hey Adam, these are additional credentials. I would prefer if I can have Sepia access on both machines - old one (fedora) and this one (MacOS).

Actions #4

Updated by adam kraitman 8 months ago

Hey Vallari,

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.


Actions #5

Updated by Vallari Agrawal 8 months ago

Hey Adam,

Sepia VPN is up and connected on my new machine. And I'm able to ssh into from my new machine using my old private key matching the public key mentioned in ticket
But I'm not able to ssh using my private key corresponding to the public key mentioned in this ticket. Just wanted to ask if this is expected behaviour.

Actions #6

Updated by adam kraitman 8 months ago

Please try now the key was missing in teuthology for some reason

Actions #7

Updated by Vallari Agrawal 8 months ago

I'm able to ssh into teuthology using the new key as well. Thank you!


Also available in: Atom PDF