Closed Bug 1563357 Opened 5 years ago Closed 5 years ago

Allocate and move 4 additional mac minis for deploystudio to new tier3 vlan

Categories

(Infrastructure & Operations :: RelOps: Posix OS, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dividehex, Unassigned)

References

Details

We need to allocate 4 minis to be used as deploystudio (active/standby) hosts in both mdc1 and mdc2.

We will re-purpose existing t-yosemite-r7 hosts from the test.releng.mdc[1,2] networks. Before moving them, we will need to upgrade them in place to MacOS 10.13 High Sierra.

New hostnames:
t-yosemite-r7-242.test.releng.mdc1.mozilla.com -> install1.tier3.releng.mdc1.mozilla.com
t-yosemite-r7-243.test.releng.mdc1.mozilla.com -> install2.tier3.releng.mdc1.mozilla.com
t-yosemite-r7-022.test.releng.mdc2.mozilla.com -> install3.tier3.releng.mdc2.mozilla.com
t-yosemite-r7-023.test.releng.mdc2.mozilla.com -> install4.tier3.releng.mdc2.mozilla.com

Instead of upgrading in place, I'm going to (attempt to) re-image these hosts with a fresh 10.13.6 image generated from autodmg. It will be cleaner and faster than the upgrade in place.

10.13 apfs image has been created using AutoDMG and has been uploaded to both install2 hosts in mdc1 and mdc2
/Deploy/Masters/APFS/osx_updated_190605-10.13.6-17G65.apfs.dmg

Summary: Allocate and move 2 additional mac minis for deploystudio to new tier3 vlan → Allocate and move 4 additional mac minis for deploystudio to new tier3 vlan
Depends on: 1568299

I created a new ds workflow and group for deploying high sierra 10.13.6 on both mdc1 and mdc2 deploystudio servers in order to provision these with high sierra. Then:

  • reimaged hosts to 10.13.6
  • disabled powermanagement via systemsetup
  • created dsadmin user
  • changed host name in inventory and infoblox

This is now blocked on netops changing the vlan ports to 260 for all 4 minis.

Previous IPs have been reclaimed in infoblox

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.