replace all remaining uses of cobbler/cobbler2 with pxe, delete cobbler/cobbler2

RESOLVED FIXED

Status

RESOLVED FIXED
6 years ago
4 years ago

People

(Reporter: dustin, Assigned: afernandez)

Tracking

Details

Cobbler's still in use on admin1a/b.private.mtv1.mozilla.com and admin1a/b.private.pek1.mozilla.com.  It's commented out for admin1a.private.tor1.mozilla.com.

I'm particularly keen on having 'pxe' active in mtv1, since I'm occasionally called on to install puppetagain things there, but it really should be used everywhere, and the old cobbler modules deleted (it's version control - svn rm isn't forever!!)

Updated

6 years ago
Assignee: server-ops → afernandez
bug 836548 for mtv1
Depends on: 836548
(Assignee)

Comment 2

6 years ago
All cobbler instances (really just admin1{a,b}.private.pek1.mozilla.com) replaced with pxe module (r57780). Waiting for svn to catch up and then will verify that everything is working.

I did not add the pxe module to office hosts as currently not needed but can/will be added as needed.

Comment 3

6 years ago
(In reply to Adrian Fernandez [:Aj] from comment #2) 
> I did not add the pxe module to office hosts as currently not needed but
> can/will be added as needed.

I believe mtv1 is the only office that uses pxe / cobbler so as long as its applied there then its ok
(Assignee)

Comment 4

6 years ago
Yeup, dustin enabled it on Bug 836548 and verified it worked for him.

I have verified that it works in pek1 by using a esx VM, however, downloading the needed packages from mrepo takes a fairly long time.

Not sure if we want a local mrepo in pek1 (not sure if needed and/or if worth the storage).
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
(Assignee)

Comment 5

6 years ago
Forgot to add, cobbler and cobbler2 modules removed from svn (r57918).

Comment 6

6 years ago
(In reply to Adrian Fernandez [:Aj] from comment #4)
> Yeup, dustin enabled it on Bug 836548 and verified it worked for him.
> 
> I have verified that it works in pek1 by using a esx VM, however,
> downloading the needed packages from mrepo takes a fairly long time.
> 
> Not sure if we want a local mrepo in pek1 (not sure if needed and/or if
> worth the storage).

I think this was discussed before in the past and the decision was it was not worth getting an mrepo server up there for the amount of hardware we have there.
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.