Closed
Bug 997785
Opened 12 years ago
Closed 12 years ago
Reconfigure of irc1.dmz.phx1.mozilla.com and migration to new ESX Cluster
Categories
(Infrastructure & Operations :: Virtualization, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: cknowles, Assigned: cknowles)
Details
We're moving all VM's out of the old HP based VC, and into the new UCS based VC.
All VMs successfully made this transition, with the exception of irc1.dmz.phx1.mozilla.com, which due to some configuration oddities needs to have its network redone in vmware. This will result in a few seconds of network disconnect, which will likely cause IRC interruptions.
We're aiming to start this work at 7AM Eastern on Friday 4/18/2014 - as promptly as possible.
| Assignee | ||
Updated•12 years ago
|
Assignee: server-ops-virtualization → cknowles
Group: infra
Updated•12 years ago
|
Group: infra
| Assignee | ||
Comment 1•12 years ago
|
||
Alright, that went better than anyone expected.
irc1.dmz.phx1.mozilla.com is now using eth1 instead of eth0, and has been migrated to the new cluster.
As stated elsewhere, there was no noticeable impact, irc seems to have weathered the process very well.
Here's the process we followed -
* backup ifcfg-eth0
* copy ifcfg-eth0 -> ifcfg-eth1 - changing the device to eth1, and getting ready to change the mac address.
* remove ifcfg-eth0
* Add a new network card to the VM in the same vlan, noting the MAC
* update dhcp with that MAC for irc1's IP.
* updating ifcfg-eth1 with the new mac address
* Wait for DHCP to notice the change.
* service network restart
* ifconfig eth0 down.
* Huh. That worked.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Infrastructure & Operations
You need to log in
before you can comment on or make changes to this bug.
Description
•