Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Requesting access to test-linuxonecc-rhel72-s390x-1 #1291

Closed
apapirovski opened this issue May 30, 2018 · 8 comments
Closed

Requesting access to test-linuxonecc-rhel72-s390x-1 #1291

apapirovski opened this issue May 30, 2018 · 8 comments

Comments

@apapirovski
Copy link
Member

Hi there,

I would like to request access to one of the LinuxONE machines (test-packetnet-ubuntu1604-x64-1 or similar), so that I can debug nodejs/node#20907

Thanks and let me know what would be needed on my end. Also, my email is in the profile.

@refack
Copy link
Contributor

refack commented May 30, 2018

You probably mean one of https://ci.nodejs.org/label/rhel72-s390x/ (test-packetnet-ubuntu1604-x64-1 is just a jenkins workspace that triggers the actual work)

Anyway +1 from me

@refack refack changed the title Requesting access to test-packetnet-ubuntu1604-x64-1 Requesting access to test-linuxonecc-rhel72-s390x-1 May 30, 2018
@refack
Copy link
Contributor

refack commented May 30, 2018

FYI you can spin your own up, for free during a trial period - https://developer.ibm.com/linuxone/

@maclover7
Copy link
Contributor

LGTM

Would take care of this myself, but don't know how to... would be interested in learning how to do this from one of the infra admins

@apapirovski
Copy link
Member Author

@refack thanks for the correction!

@gdams
Copy link
Member

gdams commented May 30, 2018

@apapirovski I would agree with @refack! Try and spin up a machine on https://developer.ibm.com/linuxone/ first and if you still need access to one of the CI machines then let us know

@Trott
Copy link
Member

Trott commented May 31, 2018

+1

Would take care of this myself, but don't know how to...

@maclover7 I pretty sure I know how to grant access (grab the user's public keys, in this case from https://github.com/apapirovski.keys, and put them in the .ssh/authorized_keys file for the user that we log in as via SSH on the machine), but the part I don't know is where to document that change so that we remember to undo it. Maybe we just leave this issue open and remove the keys when the issue is closed? Not sure what we've done in the past.

@refack
Copy link
Contributor

refack commented May 31, 2018

Maybe we just leave this issue open and remove the keys when the issue is closed?

Yep. Also move the ticket along in https://github.com/nodejs/build/projects/2#card-10173847

@apapirovski can you send me your public ssh key?

@refack refack self-assigned this May 31, 2018
@apapirovski
Copy link
Member Author

@Trott, @addaleax and I are handling this at the summit. Thanks for the help!

@Trott Trott closed this as completed May 31, 2018
@refack refack removed their assignment May 31, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants