Down the rabbit hole
Aug. 17th, 2010 09:01 pmI love cleaning up other people's messes...take this project to provide a client with some redundancy:
Fuck you and the horse you rode in on.
- Hyper-V
- software iSCSI through Windows Storage Server and MPIO
- MS-SQL Enterprise Edition
- Windows Server Failover Clustering
- Data Protection Manager with storage provided by Iron Mountain
- How the hell do you plan on gracefully resolving the circle of dependencies created by having the domain controller running as a VM on one of the WSFC clusters? (Seriously - DC on VM using shared iSCSI storage with failover means DC relies on HyperV which relies on iSCSI which relies on MPIO, the last three of which rely on various bits of WSFC, which all fucking relies on the goddamned domain controllers.)
- What is the deal with trying to give clients brand new, untested, un-labbed software? (you never asked for a single trial account for any off-site storage services, did you?)
- Did it ever occur to you that it MIGHT be important to mention the fact that every single piece of this project requires Enterprise edition everything? OR did you just not bother finding out? At least you managed to get Server 2k8 Enterprise mentioned ONCE, somewhere in the middle of that stack of paperwork.
- What in the everloving fuck were you thinking telling our client we could do this for less than $20k when the licensing/hardware costs alone are almost that much? For that matter, what the fuck gave you the idea that your job description includes sales of any sort?
Fuck you and the horse you rode in on.
no subject
Date: 2010-08-18 04:21 am (UTC)Using a VM as a secondary DC, that's OK. Using a DC running in a VM as the FSMO, HELLS NO.
Of the 8 DCs we have at work, two are being cycled out as soon as we move some niggling dependant services from them, two are still physical boxes as they replaced the two being cycled out, and the rest are all VMs. The FSMO? one of the physical boxes.
And this is the reason why no one respects MS certs. *shakes head sadly*
no subject
Date: 2010-08-18 07:30 am (UTC)From LJ Support: If you are using a style from the old (S1) style system, your journal may be displaying incorrectly. Developers will have this fixed in a future release. In the meantime, refreshing the page may help, or you may wish to temporarily switch your style to one on the current system (S2).
Wrong post.no subject
Date: 2010-08-18 10:43 am (UTC)no subject
Date: 2010-08-19 04:19 pm (UTC)no subject
Date: 2010-08-25 01:37 am (UTC)