Data Center
What Reg readers are planning for their datacentre
When 481 Reg Readers were asked to rate their IT delivery capability in terms of responsiveness, service level management, cost control and business alignment, only a quarter claimed a good level of performance across all areas. Furthermore, a wholesale move to the public cloud was not felt to be the answer. This puts the …
clouds and media
I was planning a cloud storage system to handle all my media and hot link to the media so I would only have to store the index of the links and not the media. That said apparently TVshack did that and did not work well. Clouds for you heh
Linux
1) Get rid of vestiges of Windows. Now Samba 4 is out, which has AD support, this is even easier.
2) Save a packet on licences, licence management,antivirus, extra tin to run the bloatware (15% price increase this year on CAL's alone)
3) Run Linux natively and Linux VMs
4) No rebooting, no virus menace, fast, robust systems. Low TCO.
5) Profit
Re: Linux
SAMBA 4 hasn't been out nearly long enough for any kind of reliability evaluation.
Yes, standardising on a single platform for virtualisation is a good idea
No rebooting? Do me a favour.
Re: Linux
"Run Linux natively and Linux VMs"
Yes, but which distro and which distro?
Re: Linux...4) No rebooting, no virus menace, fast, robust systems. Low TCO.
Uhhhh!! Then, why did I get a message to close my work and reboot after the last kernel install???
Now, don't get me wrong, this post is coming from a Linux box, but, please don't say NO rebooting. It isn't completely accurate.
Re: Linux...4) No rebooting, no virus menace, fast, robust systems. Low TCO.
OK Pedants :-)
There are some geeks that keep linux up to date without ever rebooting but yes, in reality, there will be a pragmatic reboot now and then, but it's not uncommon for linux servers to run without a reboot for hundreds of days.
Re: Linux...4) No rebooting, no virus menace, fast, robust systems. Low TCO.
@Eadon - If you weren't so pedantic about other OSes it would be fair to not be pedantic here.
Anyway, a Modern Windows server only needs to be rebooted rarely, updates aside.
The thing is that with any OS on micro or mini computers, if you need big uptime, which isn't affected by hardware problems or reboots, you'll cluster it, at which point it doesn't really matter if you need to reboot every so-often. You certainly wouldn't update your software on a live system, when you can remove a cluster node, update and re-introduce the node.
The tactic considered to be most useful is the creation of a modest beachhead
well duh.
then they can use the bucket and spade approach to streamline their sandcastle workflow.
now pay me some money for this insight
