Support #64283
openSepia Lab Access Request
0%
Description
1) Do you just need VPN access or will you also be running teuthology jobs?
Both
2) Desired Username:
adamlyon
3) Alternate e-mail address(es) we can reach you at:
adam.el.jones@proton.me
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?
Neha Ojha
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 AAAAC3NzaC1lZDI1NTE5AAAAIFXRsu2yFksmvo90RrBaH9vbrhBr3i2CoxnGrhfSdbWn adam@Adams-MacBook-Pro
6) Paste your hashed VPN credentials between the pre
tags (Format: user@hostname 22CharacterSalt 65CharacterHashedPassword
)
adam@Adams-MacBook-Pro EmCZGapZk6W1GIYnizX5jw 965deebfe30ef74014dc74a050c6bf296cf5811c0afe0a2af6d2731c6454651f
Updated by adam kraitman 3 months ago
- Category set to User access
- Status changed from New to In Progress
- Assignee set to adam kraitman
Updated by adam kraitman 3 months ago
Hey Adam,
You should have access to the Sepia lab now. Please verify you're able to connect to the vpn and ssh adamlyon@teuthology.front.sepia.ceph.com 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.