Project

General

Profile

Actions

Support #72332

closed

Sepia Lab Access Request

Added by Sungjoon Koh 9 months ago. Updated 8 months ago.

Status:
Resolved
Priority:
Normal
Category:
-
Target version:
-
% Done:

0%

Reviewed:
Affected Versions:
Pull request ID:
Tags (freeform):
Merge Commit:
Fixed In:
Released In:
Upkeep Timestamp:

Description

Whether you are only requesting access to schedule jobs (and view their results), or also to run jobs manually. The latter is more restricted in that it is usually only granted to core developers.
- Schedule jobs

The username you would like to use. This should probably just be the first part of your email address, but exceptions are possible.
- sungjoon_koh

Alternate e-mail addresses (other than the one you used to create your Tracker account.
-

Existing contributions to Ceph
- https://github.com/ceph/ceph/pull/64428
- https://github.com/ceph/ceph/pull/60019

A public SSH key. You may already have this (cat ~/.ssh/id_rsa.pub). If necessary, you can create a new one on the machine you will be connecting from with:
ssh-keygen t rsa
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQCiZhnTutVosuAbmYueKyyccGN8W4SZ2331HSa8q/BO1QEiOTeoEK6Kbm+hyi3vVxTZ8DRA2c/MlWyp2PWASwAyUcxTKnxerkbb8RV2Xz64qvOJRhXXnSlepjMlXDbIaJRszmEaCvf+djiNpFooR+wNFemYwjWz6tj05dRjsuR/TEoF2ATSVDdE33Vbd5QwJTG323cCigbgMFsun0gEAnY55HxwLkjfmipKa+ytHNRYhfACutKgclkxLDBF3IsML1RCSdLgqwahy1th86XuZNj6KzXtPI16XHY7pXMC7FY8Ojnlh4tSJEXcAU457DkIhjCgCqEKdSKSR+dfcaRFoD9XcBo9+D75vi+Wd0f1wxX+bqFgBkFDAHJRhnFGnS7KvWGp+0YXTAOZ+HNcwptiE5/cvdg+ED/SgVhAtErORc5bNRt332Y4HqZngdROWR06ogNTmgNFEAPElmOvP8/Wyx/7i1MkgHR3tAkg1AEMq+LmDmHdoqeIZc/u2vRugW/xEOs=

Actions #1

Updated by Sungjoon Koh 8 months ago

Paste your hashed VPN credentials between the pre tags (Format: user@hostname 22CharacterSalt 65CharacterHashedPassword)
- sungjoon_koh@linux-vm 6TQ0W+C9UY4hHJ4uZCwXQA efd2af621ccbc8c102d160fa1fa606896715b91b126f5e988aff9872f5249ce9

Actions #2

Updated by Sungjoon Koh 8 months ago

@Fernando Alcocer I've added the VPN hash credentials in the comments.
I couldn't assign the ticket due to permission issues, so I've mentioned in the comments instead.
I would appreciate it if you could confirm this.
If you need any additional information, please let me know.
Thank you!

Actions #3

Updated by Fernando Alcocer 8 months ago

  • Status changed from New to In Progress
  • Assignee set to Fernando Alcocer
Actions #4

Updated by Fernando Alcocer 8 months ago

Hey Sungjoon,

You should have access to the Sepia lab now. Please verify you're able to connect to the vpn and ssh 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.

Actions #5

Updated by Sungjoon Koh 8 months ago

Fernando Alcocer wrote in #note-4:

Hey Sungjoon,

You should have access to the Sepia lab now. Please verify you're able to connect to the vpn and ssh 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.

Thank you so much for your support!

Actions #6

Updated by Fernando Alcocer 8 months ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF