Closed Bug 1369572 Opened 2 years ago Closed 9 months ago

[puppet] puppetify the new partner-repack-1

Categories

(Release Engineering :: Release Automation: Other, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: aki, Unassigned)

References

Details

We currently use the old partner-repack1 in scl3 for partner repacks and funnelcakes.  This is not under puppet and will not be moved to the new colos.

In bug 1361543, :dividehex set up a new partner-repack-1 in the new colo.  This is ready to be puppetized in this bug.

We probably need:
- cltbld acct
- git - already there
- hg
- both s3cfg files
- ~cltbld/partner-repacks dir with repo setup
- ~cltbld/funnelcake dir with repo setup

I have this on my todo list, but if anyone else is interested, please feel free :)

old:
Name:   partner-repack1.srv.releng.scl3.mozilla.com
Address: 10.26.48.41

new:
Name:   partner-repack-1.srv.releng.mdc1.mozilla.com
Address: 10.49.48.16
Blocks: 1366828
Priority: -- → P2
Partner repacks are now on taskcluster, and it's on our short term cleanup list to get an off-cycle partner repack story in taskcluster. Once that is complete, we can retire both partner-repack1.srv.releng.{mdc1,scl3}, though we may hang on to the scl3 one for a few cycles to make sure we don't still need it.
Depends on: 1457034

Aki, what is the status here?

Flags: needinfo?(aki)
  • off-cycle partner repacks are on taskcluster as of mid? last year.
  • partner-repack-1 {mdc1,mdc2} are tracked in bug 1500323, but we just took over those two boxes as our mac notarization testing grounds. (We were able to get mojave on partner-repack-1 mdc1 after the apple netblock was removed; thanks!)

We can close this bug. At some point in Q2? we may start retiring the signing server pools as well.

Status: NEW → RESOLVED
Closed: 9 months ago
Flags: needinfo?(aki)
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.