Support #58277
openSepia Lab Access Request
0%
Description
1) Do you just need VPN access or will you also be running teuthology jobs? Running teuthology jobs
2) Desired Username: bcs-ceph
3) Alternate e-mail address(es) we can reach you at: jzhu116@bloomberg.net, oozmen@bloomberg.net
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? Yes (Adam Emerson/Casey Bodley)
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 AAAAB3NzaC1yc2EAAAADAQABAAABgQCybh4on/Al9aQnCYorI24foL4j+5qIjU5390cqo02FJLGCYqeLPwkm0Rbfs4UjNLs2Vk+CQL8OLqjWhxtgIRK671qxAscpwpZgGDW2XYrEjp/aUM66D9mguFFVl0DIWd2Fe7YYsccOqI91vEvnOV84TKe1Zc+XB7r1rfUzYu7SSOo1YbFx0gpxkdel1mpAyCqMYevDrd8RMBWO+Sb7hdeKBgMXxZiXDG2zck7OqLT3OzgBbY/kfG3917ZYqlNDuuRm46niI8e/xDbAw+wVr0amw3Aco60ZBioPf0j+pDRt/013yJuTsz3BVs64p4MCllhbA3cygqsQnkBoKWWj822XZSUNcfbWzPOVfimU9cqwSh8PC/8tr2iBbemboxSH5WILnzTuRa/Xgn9nhYZscWqoYAcGdjlGLX+t8+TueCkdLbNIhGfBmNN/5l2wcCefWFqNMpYqExXygIaPEGMf6eGoS2Q2I2Je5L4OYC07WmcXas3spEjCk50ZdQcPElm9OLU= kchheda3@dev-10-74-3-243
6) Paste your hashed VPN credentials between the pre tags (Format: user@hostname 22CharacterSalt 65CharacterHashedPassword)
bcs-ceph@bcc eAQD+fjNB4qzQejR5zbWKw 97ab71135769d6caa1137da63efca09c3839b066f15f8b5204c6966ce9edbe07
Updated by Casey Bodley over 1 year ago
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? Yes (Adam Emerson/Casey Bodley)
consider this vouched! thanks
Updated by adam kraitman over 1 year ago
- Category set to User access
- Status changed from New to In Progress
Updated by adam kraitman over 1 year ago
Hey Krunal Chheda,
You should have access to the Sepia lab now. Please verify you're able to connect to the vpn and ssh bcs-ceph@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 Krunal Chheda over 1 year ago
Thanks Adam.
We were able to connect to vpn and able to ssh to test nodes.
Updated by Krunal Chheda over 1 year ago
Hi Adam,
As per the steps mentioned here , to run the tests in the lab, we need to create a branch in the ceph/ceph-ci repo, but we are getting PERMISSION DENIED when trying to push the new branch upstream?
do we need any additional permissions/approvals while pushing a branch to ceph/ceph-ci ?
We tried forking the repo and creating new branch, but in that workflow the Jennkins pipeline doesn't trigger ? Is there any other way to trigger the test suite?
Updated by adam kraitman about 1 year ago
Hey Krunal Chheda i see that you have access to ceph-ci