Just a Heads Up no host plays on there clients server or chooses who's a Admin and stuff.Host try to make a living on this and unless you can come up with better ideas I can't help you....
As have we, there are a few providers on here who provide a great service. We have hosted dedicated servers since 2008 before that we hosted servers for large gaming communities. Our parent company provides dedicated servers in multiple locations, more than most providers you would find on a place like WHT.
However our prices are not bottom of the barrel, we have prices which are on the lower side of the average for other providers who provide a service level as us.
While that dedicated will be okay from the budget point, don't forget that (if it's at the place I'm thinking it is), it doesn't come with any support, whatsoever, and any additional IP addresses or SSD drives will cost you extra one way or the other. The main thing being, from the looks of it, you aren't a sysadmin, as such having a completely "no support here" dedicated will cause you nothing but grief since you'll have to pay someone to help you fix or install whatever it is you want.
Just for s and giggles, here's the procedure I have for firing up a new hardware node (and I still haven't automated that part...):
1) order your dedicated with a blank harddrive and a rescue system only
2) install Centos 6 from scratch
- if hardware raid: partition drives
- if software raid: set up software raid, and LVM, and then partition drives
- mkfs all the drives
- install a Centos 6 image
3) configure machine:
- sysctl settings
- network settings
- syslogging to central loghost
- monitoring agent
- install perl and half of CPAN
- install the Blockstackers secret sauce™
4) install OpenVZ
5) configure OpenVZ
6) synch up all OpenVZ templates and VE sample configs from the master repository
7) test to see if the secret sauce™ is being saucey or not (read: does it work as intended)
8) run a test involving repeated creation and destruction of containers to see if the other bit of the
secret sauce is keeping track of everything the way it should
9) clean up the temporary stuff, polish it up some, and tell the big master control panel a new node is
available.
And that's simplified. It takes me a little bit under 4 hours to do, and I'm pretty damn good at this stuff.
As to how many Minecraft servers you can run on any given box, that starts off simple. Each player slot will use 100Mb. Given that, a server allocated 512Mb (the java process, that is) will host 5 players, maybe a few more if the world is small. A server with 16Gb of memory can theoretically run 32 servers each allocated 512Mb.
Now add in OpenVZ, so you have a little bit of overhead; this means that an OpenVZ container needs to be allocated the OS overhead, plus a small buffer, plus the allocation for the Minecraft server. So if you want to allocate 512Mb to the Minecraft server, you're best off allocating 768Mb to the OpenVZ container, unless you rolled your own OpenVZ template and you have a truly minimal OS going.
Now do the math. 16Gb divided by 768Mb is 21 OpenVZ containers, give or take. Unfortunately, you still can't run 21 servers because you'll max out every CPU core eventually, before you hit 21 servers.
And this is if you stuff a machine as full as it can get, which borders very close on overselling. Ideally you want to use only 80% capacity, and whether this means memory or CPU doesn't matter; hitting 80% memory means having 15 servers running, hitting 80% CPU, well, you'll just have to see how many are or are not running since there's no "fixed" way of determining that.
/end random junk
Also Should I get Multicraft or SpaceBukkit. Also If you can show me some of this that would be great but not like right away so yeah just maybe it was just a idea so yeah
Reselling requires you to have a dedicated server which start at about $75.00/mo so it will NOT fit your budget. I suggest raising your budget, or you will never get a company.
Wait me or him But He's not wanting a dedicated server he's wanting a reseller package
While that dedicated will be okay from the budget point, don't forget that (if it's at the place I'm thinking it is), it doesn't come with any support, whatsoever, and any additional IP addresses or SSD drives will cost you extra one way or the other. The main thing being, from the looks of it, you aren't a sysadmin, as such having a completely "no support here" dedicated will cause you nothing but grief since you'll have to pay someone to help you fix or install whatever it is you want.
Just for s and giggles, here's the procedure I have for firing up a new hardware node (and I still haven't automated that part...):
1) order your dedicated with a blank harddrive and a rescue system only
2) install Centos 6 from scratch
- if hardware raid: partition drives
- if software raid: set up software raid, and LVM, and then partition drives
- mkfs all the drives
- install a Centos 6 image
3) configure machine:
- sysctl settings
- network settings
- syslogging to central loghost
- monitoring agent
- install perl and half of CPAN
- install the Blockstackers secret sauce™
4) install OpenVZ
5) configure OpenVZ
6) synch up all OpenVZ templates and VE sample configs from the master repository
7) test to see if the secret sauce™ is being saucey or not (read: does it work as intended)
8) run a test involving repeated creation and destruction of containers to see if the other bit of the
secret sauce is keeping track of everything the way it should
9) clean up the temporary stuff, polish it up some, and tell the big master control panel a new node is
available.
And that's simplified. It takes me a little bit under 4 hours to do, and I'm pretty damn good at this stuff.
As to how many Minecraft servers you can run on any given box, that starts off simple. Each player slot will use 100Mb. Given that, a server allocated 512Mb (the java process, that is) will host 5 players, maybe a few more if the world is small. A server with 16Gb of memory can theoretically run 32 servers each allocated 512Mb.
Now add in OpenVZ, so you have a little bit of overhead; this means that an OpenVZ container needs to be allocated the OS overhead, plus a small buffer, plus the allocation for the Minecraft server. So if you want to allocate 512Mb to the Minecraft server, you're best off allocating 768Mb to the OpenVZ container, unless you rolled your own OpenVZ template and you have a truly minimal OS going.
Now do the math. 16Gb divided by 768Mb is 21 OpenVZ containers, give or take. Unfortunately, you still can't run 21 servers because you'll max out every CPU core eventually, before you hit 21 servers.
And this is if you stuff a machine as full as it can get, which borders very close on overselling. Ideally you want to use only 80% capacity, and whether this means memory or CPU doesn't matter; hitting 80% memory means having 15 servers running, hitting 80% CPU, well, you'll just have to see how many are or are not running since there's no "fixed" way of determining that.
/end random junk
Some of this stuff I don't even know what they are like the Blockstackers Secret Sauce By the way LOL. But if you could help in any other way Please.And for the Setup Thanks!
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0