Table of Contents

VPN Access

Requesting Access

To request access to the Sepia lab,

  1. Generate login credentials by following directions under VPN Client Access below.
  2. File a ticket.
  3. Copy and paste the questions below into your ticket
1) Do you just need VPN access or will you also be running teuthology jobs?

2) Desired Username:

3) Alternate e-mail address(es) we can reach you at:
   (Other than the one used to create your tracker/Redmine account.  Optional.)

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?

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: <pre></pre>

6) Paste your Wireguard public key between the pre tags <pre></pre>

VPN Client Access

See Wireguard Access

A Note About DNS

Due to complexities around adding nameservers to various Linux distro VPN clients, our OpenVPN server does not use the dhcp-option DNS option.

Instead, we serve our private DNS records publicly. Your machine should be able to resolve hostnames under the sepia.ceph.com subdomain automatically.

If you're using dnsmasq, you can add server=/sepia.ceph.com/172.21.0.1 to /etc/dnsmasq.conf.