Support #51865
closedSepia Lab Access Request
0%
Description
1) Do you just need VPN access or will you also be running teuthology jobs?
Also running teuthology jobs.
2) Desired Username:
matan
3) Alternate e-mail address(es) we can reach you at:
matan.brz@gmail.com
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'm a Gsoc2021 student working with Yuval Lifshitz as my mentor
https://summerofcode.withgoogle.com/projects/#4847082420043776
https://github.com/ceph/ceph/pull/41927
https://github.com/ceph/ceph/pull/42102
https://github.com/ceph/ceph/pull/42169
- I have lost access to my previous Request (https://tracker.ceph.com/issues/51160)
5) Paste your SSH public key(s) between the pre tags
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIKjxTgyhL1yFriyNvvuhUc6SE8+6f6lT6FTF8cZL9uiz matan.brz@gmail.com
6) Paste your hashed VPN credentials between the pre tags (Format: user@hostname 22CharacterSalt 65CharacterHashedPassword)
matan@main-win vEAxj3ZM9DjxBi/jfjc+jQ 9c30b8fcef9bdc804090947a92e1e60cc21d3f280f261bc3f4cecac64541dc6e
Updated by adam kraitman over 2 years ago
- Category set to User access
- Status changed from New to In Progress
- Assignee set to adam kraitman
Updated by adam kraitman over 2 years ago
Hey Matan,
You should have access to the Sepia lab now. Please verify you're able to connect to the vpn and ssh matan@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.
Updated by Matan Breizman over 2 years ago
adam kraitman wrote:
Hey Matan,
You should have access to the Sepia lab now. Please verify you're able to connect to the vpn and ssh matan@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_configMost 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.
Thank you!
May I have access to folio03.front.sepia.ceph.com for development purposes?
Updated by adam kraitman over 2 years ago
Yes I added your user to folio03.front.sepia.ceph.com
Updated by adam kraitman over 2 years ago
- Status changed from In Progress to Resolved