Closed
Bug 1454578
Opened 7 years ago
Closed 7 years ago
install an ssh server on taskcluster windows workers
Categories
(Infrastructure & Operations :: RelOps: General, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: grenade, Assigned: grenade)
Details
No description provided.
| Assignee | ||
Comment 1•7 years ago
|
||
testing on beta workers:
https://github.com/mozilla-releng/OpenCloudConfig/commit/ad9df9e7b507ad2e6541459f8c1641ef37e7a16e
| Assignee | ||
Comment 2•7 years ago
|
||
seems to be working well.
add your public key to a new line here to give yourself ssh access to workers:
https://github.com/mozilla-releng/OpenCloudConfig/blob/master/userdata/Configuration/ssh/authorized_keys
for win 10 and win 2012 the username to connect is Administrator. eg:
$ ssh -i ~/.ssh/id_rsa Administrator@<public_ip_of_worker>
for win 7 the username to connect is root. eg:
$ ssh -i ~/.ssh/id_rsa root@<public_ip_of_worker>
the current implementation uses the powershell shell on the remote instance. if you want bash, just type "bash" at the powershell prompt. it takes a while to load the bash shell, but if you are patient, it will eventually load.
| Assignee | ||
Comment 3•7 years ago
|
||
deployed to all windows worker types except l3 builders.
the aws security groups do not include ssh access for now so you need both a public key in authorized_keys (see comment 2, best to add this long before you need it as it will take hours before all workers have synced the authorized_keys file) and you need to add the ssh security group to the worker you wish to connect to (the sg can be added to a running instance and takes effect immediately).
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•