Support #65633
openSepia Lab Access Request
0%
Description
Hi Team,
I am from ceph qe team and Requesting sepia lab access for the first time. Please do the needful.
Details:
nehagangadhar:.ssh$ cat id_rsa.pub
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDMvdHKEekShMn2ylsbeABewdmsuQ7mQToz8xq+pS3yEyqZNduKHTv/ryf3b7oYmECTk5f9sjuxIdUuvS5Ss6AFWiWwSQIM+VddoAsC/DtAE+OPDcvPq1F1cnOzPcUv++Of6EBSCrfkSvyqe4JGLmuAM/unVmtOVkUQee3BDgR8GmBcqOnfcHA6KgDchX0tFHHUFma3BRSuU7tbETyvXTs6jPgJnuZe/MEvPDLDZQMzGyVLMpWWPSWK4j9c3wGyPhyPm7BatJh1WcpjhWmKnjoAHiBnO1zXpZGXoG+yrb2jfseGDcGy1OxuiDREEdjc0RV5RXCYRr+x2VeXKXgwo4IaPXXyIK+azfOqYu+c8ugbYOioHQoe8sFX3sR3R0oYRafQ5daO8hL3tve6YKuZ4KEu0RnUPeAmoqjb7tUk6KfBLA5fkf+dQvMy7J5vCfBtV7uie7Vd8pI7ZrEMgMKmY0o55XBy/z4zy3YDDnwUJ0cwe+0K/E5nOmFDjsZ5zMGScNU= nehagangadhar@li-47ecb14c-316b-11b2-a85c-978842ca43ab.ibm.com
VPN password:
nehagangadhar:openvpn$ sudo ./sepia/new-client ngangadh@thinkpad
!!!!! DO NOT RUN THIS SCRIPT MORE THAN ONCE !!!!!
Please paste the following line in your Sepia Lab Access Request tracker ticket:
ngangadh@thinkpad dm/7cXQh+oSsqcjlmDGWnA 0cf599d0a5416763a3b8af9b80836e811dcff5a9506c4cbd934c7fe4902e860e
Thanks,
Neha
Updated by adam kraitman 18 days ago
Hey Neha,
You should have access to the Sepia lab now. Please verify you're able to connect to the vpn and ssh nehagangadhar@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 adam kraitman 18 days ago
- Status changed from New to In Progress
- Assignee set to adam kraitman