dm-bugzilla-api02 (might be aka api-dev, bugzilla-api01, dm-bugzilla-api02) is api-dev.bugzilla.mozilla.org which, despite its name, is effectively production infra, relied upon by pretty much everything which programmatically interfaces with Bugzilla. It needs to move to SCL3. 06:25:02 up 501 days, 6:08, 1 user, load average: 0.02, 0.07, 0.12 ^---- shame... justdave says: "We could probably clone this (rather than moving it) to SCL3 and then point the domain at it after it's up and running in SCL3." This would still require downtime for the cloning process, but not nearly as much. The current disk space used on the VM _without_ any of the BzAPI log files in /tmp is: 3.5GB. Those log files would need deleting before we cloned. We should estimate the downtime and, if it's going to be more than a few minutes we should schedule and announce it. But surely it can't take long to clone a 3.5GB file? Gerv

Can this move before there's a bugzilla instance in scl3? (bug 726710)

BzAPI benefits performance-wise from being close to and having a high-BW link to Bugzilla, so ideally the production instance of BzAPI would be almost always co-located with Bugzilla. Not sure how often that's true these days! Having said that, BzAPI addresses Bugzilla simply by its domain name, and so could be half way round the world and would still function just as well, with the possible exception of performance. Gerv

Well, this got moved, accidentally, and to the wrong VLAN, in bug 743916.