From: Grant <emailgrant@gmail.com>
To: Gentoo mailing list <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] {OT} Need a new server
Date: Fri, 13 Sep 2013 15:14:05 -0700 [thread overview]
Message-ID: <CAN0CFw0ZKPiR__bbdmqX4SG1gOObpPqu74eDP6ct4XQq2t=-Eg@mail.gmail.com> (raw)
In-Reply-To: <52338A8E.1010708@thegeezer.net>
>> It's time to switch hosts. I'm looking at the following:
>>
>> Dual Xeon E5-2690
>> 32GB RAM
>> 4x SSD RAID10
> nice
>> Can I count on this system to keep running if I lose an SSD?
> if a built in raid controller, yes. one thing you might want to check is
> linux tools for management -- you wouldn't want to reboot just go to go
> into the raid tools and check if it requires a rebuild, and you want to
> be able to schedule regular scrubs and maybe get a report.
> you might also like to consider OOB management such as IPMI, dell and HP
> do very lovely web based control panels that are independent of your
> main o/s allowing you to get alerts when bad things happen, and
> crucially watch reboot process from remote locations.
Good idea, I will look into IPMI.
>> Is a 100M uplink enough if this is my only system on the LAN?
> gigabit NICs are pretty cheap i'd be surprised if any new machine didn't
> have gigabit. i would suggest if you ever want to transfer data over
> 10GB across the network you should request gigabit
I should be OK with 100M. I shouldn't be copying anything across the LAN.
>> Any opinions on Soft Layer?
>>
>> - Grant
> are you putting this server in colocation at softlayer? if so OOB is a
> requirement, and gigabit is not
I decided against colocation because I don't want to be responsible
for fixing hardware problems. It would be a hosted machine.
- Grant
next prev parent reply other threads:[~2013-09-13 22:14 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 20:00 [gentoo-user] {OT} Need a new server Grant
2013-09-13 20:39 ` Alan McKinnon
2013-09-13 21:39 ` Grant
2013-09-14 8:14 ` Alan McKinnon
2013-09-14 8:54 ` Grant
2013-09-14 9:02 ` Alan McKinnon
2013-09-14 9:14 ` Grant
2013-09-13 20:44 ` Michael Orlitzky
2013-09-13 21:47 ` Grant
2013-09-13 22:47 ` Peter Humphrey
2013-09-13 22:54 ` Daniel Frey
2013-09-14 8:50 ` Grant
2013-09-14 11:32 ` Tanstaafl
2013-09-15 11:15 ` Grant
2013-09-16 9:54 ` Tanstaafl
2013-09-14 14:37 ` Michael Orlitzky
2013-09-16 6:49 ` Grant
2013-09-16 13:10 ` Michael Orlitzky
2013-09-17 6:43 ` Grant
2013-09-17 12:30 ` Michael Orlitzky
2013-09-17 13:13 ` Grant
2013-09-17 16:46 ` Alan McKinnon
2013-09-13 23:17 ` Michael Orlitzky
2013-09-14 8:52 ` Grant
2013-09-14 11:35 ` Tanstaafl
2013-09-13 21:58 ` thegeezer
2013-09-13 22:14 ` Grant [this message]
2013-09-14 8:59 ` [gentoo-user] " Grant
2013-09-14 9:10 ` Alan McKinnon
2013-09-14 9:29 ` Grant
2013-09-14 11:07 ` Michael Hampicke
2013-09-15 11:07 ` Grant
2013-09-14 14:36 ` Alan McKinnon
2013-09-14 11:34 ` Tanstaafl
2013-09-14 14:42 ` Alan McKinnon
2013-09-14 11:04 ` thegeezer
2013-09-15 11:05 ` Grant
2013-09-14 11:18 ` [gentoo-user] " Tanstaafl
2013-09-15 11:10 ` Grant
2013-09-17 5:36 ` Pandu Poluan
2013-09-17 6:32 ` Grant
2013-09-17 9:24 ` Neil Bothwick
2013-09-17 10:01 ` Tanstaafl
2013-09-17 7:28 ` Grant
2013-09-17 7:37 ` Pandu Poluan
2013-09-17 9:49 ` Grant
2013-09-17 10:10 ` Alan McKinnon
2013-09-17 13:11 ` Grant
2013-09-17 16:49 ` Alan McKinnon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAN0CFw0ZKPiR__bbdmqX4SG1gOObpPqu74eDP6ct4XQq2t=-Eg@mail.gmail.com' \
--to=emailgrant@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox