LMG Server Closet / Infrastructure Build / Suggestion
On 9/23/2016 at 4:39 PM, Mark77 said:I don't think putting the gateway router on the same physical hardware (ie: virtualized) as the actual enterprise applications server is a good idea. If you're on the phone to the ISP, and you have to make a change because something isn't working, the last thing you want to be doing is fighting with the virtualizer, especially if there's any question of whether the virtualizer is at fault. A standalone pfsense box is relatively simple to troubleshoot and connect/disconnect. And the cost of the hardware and electricity for such a machine is negligible.
Hey Mark,
Typically when diagnosing issues, for myself I exhaust all possible diagnoses before calling a support line. Most support lines don't know much anyways. Furthermore I would never even mention it was virtualized hardware. OMG that would just be an excuse for them to blame it on something that doesn't involve them as the source of the problem. As far as the stability if Hypervisors goes, in my experience they are pretty good. I myself have never had problems outside of nailing down the initial configuration. A nice feature of virtualization is that you can just restart the guest to fix a virtualization issue in the (in my experience) unlikely event one should occur.
QuoteLikewise, that big machine you propose, its basically concentrating all one's eggs in one basket. If it goes down, a company basically has to shut their doors until its back up and running and can be fixed. The 'cost' of idle capacity is largely that of the amortized capital cost of hardware, as electricity scaling is actually very good these days (ie: a lightly loaded machine uses very little of it!). And with the cost of hardware these days, its trivial and negligible.
Distributed systems like this actually offer redundancy in that anyone system could go down and everything would continue to run without issue. Now in the configuration I outline there are a couple caveats. 1. The cluster servers that form the RADIZ could suffer only the loss of one system. Once that system came back up, the RAIDZ would need to catch that iSCSI device back up with storage changes. 2. The Main Head server does not have a redundant replacement. So in that you are correct, But there is no redundancy in a single router system either. Also the RAIDZ would be rediscoverable once the system was repaired.
So, example should the transcoding system go down in the existing setup, then that needs to be repaired before transcoding can continue. In my setup, the transcoding system is spawned on demand on what ever system is available. Systems could go down and the transcoding system would just spawn on another device that is up.
QuoteIf they were a much larger business, had a dozen or a few hundred servers and could have their system structured for a few spare ones ready to back-up, then sure, the sort of fancy-ness you propose certainly can help reduce costs and improve uptime. But I'd say for an outfit like LMG, the chief concern should be actually keeping their IT simple enough that they can focus most of their efforts on generating revenue-creating content. This means going with systems they have expertise in (Linus freely and readily admits he knows little about Linux, which is perfectly okay if he/they can accomplish what they need to accomplish in Windows).
I think LMG is plenty large enough. I have actually seen many smaller businesses using similar infrastructures. They like the flexible virtual development environments they can create on demand.
I hope this seen as just a follow up response and my general disagreement with your stance. You could be right in the end.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now