Sepia Lab Access Request
1) Do you just need VPN access or will you also be running teuthology jobs?
Both. I need access to analyze teuthology fails, as well as the ability to relaunch jobs.
2) Desired Username:
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?
ceph community? I have been talking to Neha, Laura Flores, Adam Kupczyk. At IBM, you can contact my manager, Sameh Asaad <firstname.lastname@example.org>.
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
6) Paste your hashed VPN credentials between the
pre tags (Format:
user@hostname 22CharacterSalt 65CharacterHashedPassword)
email@example.com 1swhxve5X+6Bg1QYOHalGQ 3a79d8369ba6c5c837488939060d327a99c6f328a5fa6332ec3b1eecad0f8c70
#2 Updated by adam kraitman 3 months ago
Hey Martin Ohmacht,
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 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.