If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

write opsi package to deploy sshd on windows build machines

RESOLVED FIXED

Status

Release Engineering
General
P5
normal
RESOLVED FIXED
9 years ago
4 years ago

People

(Reporter: catlee, Assigned: salbiz)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [oldbugs][opsi])

Attachments

(1 attachment, 2 obsolete attachments)

(Reporter)

Description

9 years ago
We should figure out a way to get sshd working on our windows build slaves.  It would make updating the slaves soooo much easier.
I have filed pretty much the same bug for all the talos boxes. :)

Just like it, this goes in Future for now - though it would be awesome all around.
Component: Release Engineering → Release Engineering: Future

Updated

9 years ago
OS: Linux → Windows Server 2003
As we are rolling OPSI into production for build/unittest machines, do we still need this bug at all?

Comment 3

8 years ago
(In reply to comment #2)
> As we are rolling OPSI into production for build/unittest machines, do we still
> need this bug at all?

I would argue yes. Mundane tasks like cleaning up build dirs in advance of releases would be made much easier on Windows by not having to RDP in. This isn't something OPSI can handle AIUI.

Suffering through windows build dir cleanup on slaves for 3.5.4 right now. :(
(In reply to comment #3)
> (In reply to comment #2)
> > As we are rolling OPSI into production for build/unittest machines, do we still
> > need this bug at all?
> 
> I would argue yes. Mundane tasks like cleaning up build dirs in advance of
> releases would be made much easier on Windows by not having to RDP in. This
> isn't something OPSI can handle AIUI.

Correct, opsi/puppet and release automation do not handle this currently. 

I'd suggest that having this cleanup be part of release automation (bug#508403 is the real cure. If bug#508403 was fixed, would we still want to install sshd on the win32 slaves?



> Suffering through windows build dir cleanup on slaves for 3.5.4 right now. :(
Urgh - sorry.

Comment 5

8 years ago
Mass move of bugs from Release Engineering:Future -> Release Engineering. See
http://coop.deadsquid.com/2010/02/kiss-the-future-goodbye/ for more details.
Component: Release Engineering: Future → Release Engineering
Priority: -- → P3

Updated

8 years ago
Whiteboard: [buildslaves][opsi]
(Reporter)

Updated

8 years ago
Priority: P3 → P5
Assignee: nobody → bhearsum
Whiteboard: [buildslaves][opsi] → [triage][oldbugs]
Whiteboard: [triage][oldbugs] → [triage][oldbugs][buildslaves][opsi]
Morphing summary. 

1) This is about writing an opsi package to deploy sshd onto windows 2003 build machines

2) This is for build machines only, explicitly not test machines.
Summary: sshd on windows → write opsi package to deploy sshd on windows build machines
Whiteboard: [triage][oldbugs][buildslaves][opsi] → [triage][oldbugs]

Updated

7 years ago
Whiteboard: [triage][oldbugs] → [oldbugs][opsi]
(Assignee)

Comment 7

7 years ago
using kpyM sshd package with license key from bug 497487
Assignee: bhearsum → salbiz
(Assignee)

Comment 8

7 years ago
Created attachment 479436 [details] [diff] [review]
[untested]add_sshd_opsi

Had to use autoit package to install via graphical installer. Tested autoit script, but need root staging-opsi powers to test properly through staging-opsi. In addition the license key from https://wiki.mozilla.org/ReferencePlatforms/Win64#SSH seems to be invalid when tested with the latest installer.
Attachment #479436 - Flags: feedback?(catlee)
Attachment #479436 - Flags: feedback?(bhearsum)
(Reporter)

Comment 9

7 years ago
Comment on attachment 479436 [details] [diff] [review]
[untested]add_sshd_opsi

Need to figure out how to deploy the license key too.
Attachment #479436 - Flags: feedback?(catlee) → feedback+
Comment on attachment 479436 [details] [diff] [review]
[untested]add_sshd_opsi

r+ assuming this tests fine in staging
Attachment #479436 - Flags: review+
Attachment #479436 - Flags: feedback?(bhearsum)
Attachment #479436 - Flags: feedback+
(Assignee)

Comment 11

7 years ago
Created attachment 480929 [details] [diff] [review]
[tested]patch_opsi_package

After thorough testing, I've made a few changes that get rid of the nag screen, and also added an auto-it based uninstall script.
Attachment #479436 - Attachment is obsolete: true
(Assignee)

Updated

7 years ago
Attachment #480929 - Flags: review?(rail)
(Assignee)

Comment 12

7 years ago
Created attachment 480942 [details] [diff] [review]
[tested]patch_opsi_package

Added a section to remove the firewall exception on uninstall
Attachment #480929 - Attachment is obsolete: true
Attachment #480942 - Flags: review?(rail)
Attachment #480929 - Flags: review?(rail)
Comment on attachment 480942 [details] [diff] [review]
[tested]patch_opsi_package

Looks good.
Attachment #480942 - Flags: review?(rail) → review+
(Assignee)

Updated

7 years ago
Attachment #480942 - Flags: checked-in?
Probably best to do this in a reconfig window. At the very least, needs-reconfig? will make sure this lands soon.
Flags: needs-reconfig?
Comment on attachment 480942 [details] [diff] [review]
[tested]patch_opsi_package

changeset:   66:49061b7f307d
Attachment #480942 - Flags: checked-in? → checked-in+
Flags: needs-reconfig? → needs-reconfig+
Landed the "binaries" too:
RCS file: /mofo/opsi-binaries/kpyM-sshd/kts.ini,v
done
Checking in kts.ini;
/mofo/opsi-binaries/kpyM-sshd/kts.ini,v  <--  kts.ini
initial revision: 1.1
done
RCS file: /mofo/opsi-binaries/kpyM-sshd/kts118.exe,v
done
Checking in kts118.exe;
/mofo/opsi-binaries/kpyM-sshd/kts118.exe,v  <--  kts118.exe
initial revision: 1.1
done
Set to deploy on all win32 build machines:
mw32-ix-slave*
try-w32-slave*
w32-ix-slave*
win32-slave*
(In reply to comment #17)
> Set to deploy on all win32 build machines:
> mw32-ix-slave*
> try-w32-slave*
> w32-ix-slave*
> win32-slave*

Awesome! Thanks!
Haven't seen any fallout here, a few random tests confirm that this is deployed.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.