Project

General

Profile

Actions
Copy link

Support #40172

closed

Sepia Lab Access Request

Added by Anonymous almost 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
David Galloway
Category:
User access
Target version:
-
% Done:

0%

Tags:
Reviewed:
Affected Versions:

Description

1) Do you just need VPN access or will you also be running teuthology jobs?
I might be using teuthology in future, but as of now I don't.

2) Desired Username:
ideepika

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?
Yes, I am interning with Ceph and working with Josh Durgin, Neha Ojha and Ali Maredia as my mentors.

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

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDEJa/U9zUfZ7YFl0kwU7Mx3rHPn2O4sdh1J3XBUgoVdrJ4Qnh7i+QhN+fw0eaBWQE2GIsGEX6YWAL5xJ7EuYZyas8OVLNdP9cJIr79M51d8dG/ywqBpgcFnx7qhCSua3sKmP6GCTWGD9Y0eWL2Z6y9t3amb8dPXviMNqKGDz/DaDtp5bPaoG8mDHQ9QeADYYk3tx6V7+phIBXrI2GKt0BBlJeuZysiUI/XWO46JdMyHvCzvzcdquD446aoWS44waDGj501sgnHVQ7gwf4P1+vFOSEHzkWhbenpJmmTA26f4dim+Jo5JpBW/Ma5mMBvORFhH/Kt+S9P9sPCiF1shWc3 d@d

6) Paste your hashed VPN credentials between the pre tags (Format: user@hostname 22CharacterSalt 65CharacterHashedPassword)

d@d 6gyFcf8FvefhkfJp9+xjQA 56fc4f30b76c2ce4f5cf5a3d89301a0c6ca515f5040a7b86021598da9e998b92

Actions
Copy link
 #1

Updated by David Galloway almost 5 years ago

  • Status changed from New to 4
  • Assignee set to David Galloway

Hi Deepika,

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

Thanks.

Actions
Copy link
 #2

Updated by Anonymous almost 5 years ago

David Galloway wrote:

Hi Deepika,

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

Thanks.

Hey David,
Thanks for processing my request. Although my authentication is
failing in setting up VPN.
Here's a debug log, can you point me in the right direction? I have
tried everything I can think of.

https://paste.fedoraproject.org/paste/gF7Km~Ep4QIeDsgkI0RmnQ

Actions
Copy link
 #3

Updated by David Galloway almost 5 years ago

Did you re-run the new-client script by chance? The error I see on the server is basically 'wrong password.'

The new-client script can only be run once. If you run it again, the output will be different and I'll need to update the credentials on my side.

If you did run it and still have the output, please paste it here. If you're not sure, run the script again and paste the output and I'll update.

Actions
Copy link
 #4

Updated by Anonymous almost 5 years ago

Maybe I didn't copy correct. Thanks, for helping.
Here's a regenerated hash.

`
deepika@asus hHsL1xugca0LzY52gKqfqQ 312e0f2680f72d9459c707fcd0ccfb777617f00017f0511839e9b7e3167d590f

`
Sorry for the inconvenience.

Actions
Copy link
 #5

Updated by Anonymous almost 5 years ago

http://tracker.ceph.com/issues/15986

Hey David,
I am having the same issue, I can authenticate and log can track Initialization Sequence Completed, yet I can't ssh to remote system. I am using this command

ssh -vv -i /home/d/.ssh/id_rsa deepika@senta04.front.sepia.ceph.com

which outputs:

OpenSSH_7.8p1, OpenSSL 1.1.0i-fips 14 Aug 2018
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Reading configuration data /etc/ssh/ssh_config.d/05-redhat.conf
debug1: Reading configuration data /etc/crypto-policies/back-ends/openssh.config
debug1: /etc/ssh/ssh_config.d/05-redhat.conf line 8: Applying options for *
debug2: resolving "senta04.front.sepia.ceph.com" port 22
debug2: ssh_connect_direct
debug1: Connecting to senta04.front.sepia.ceph.com [172.21.9.34] port 22.
debug1: connect to address 172.21.9.34 port 22: Connection timed out
ssh: connect to host senta04.front.sepia.ceph.com port 22: Connection timed out

Also added the `172.21.0.51` to resolv.conf file. Nothing helped.

Actions
Copy link
 #6

Updated by David Galloway over 4 years ago

  • Status changed from 4 to Closed
Actions
Copy link

Also available in: Atom PDF