Sepia Lab Access Request
1) Do you just need VPN access or will you also be running teuthology jobs?
I will be running teuthology jobs.
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 contributed to Ceph as shown by
git -C ceph log --author dachary
and I joined the ceph stable release team today https://email@example.com/thread/NQVWKVSJPQWHTJRBLEXD2C3G7TTBEL5G/, reason why I would like to get access to the lab.
5) Paste your SSH public key(s) between the
6) Paste your hashed VPN credentials between the
pre tags (Format:
user@hostname 22CharacterSalt 65CharacterHashedPassword)
loic@tulipe 1NGxatlPDW6m9FLwzG2Gng cc19cfe2d2101909e9e0ae6b207d7e8dccafd8ec1f4594bdd006dda6b67a80b5
#7 Updated by David Galloway 4 months ago
Try to connect and SSH to teuthology.front.sepia.ceph.com now. Pasting my usual clipping below in case you need it.
You should have access to the Sepia lab now. Please verify you're able to connect to the vpn and
ssh firstname.lastname@example.org 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 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
-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.