New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
You can run it on as little as 8GB of RAM but as with any other kind of server, the fewer the resources the fewer the machines you can host.
CentOS 5/6 doesn't use a whole lot of RAM.
implys you need 8gb ram
8GB? I thought it would be much lower
like around 2-4
I don't believe he is looking to host VMs on the master, just the SolusVM master that communicates with the slaves.
If you don't plan to have any VM on your solus master and only want to use it as a controller, you could get away with using 1gb of ram and 20gb of disk space. It depends on how many OS templates you have.
^ that
Yeah thats what I thought, I was thinking of getting a DDoS protected XEN or KVM VPS for this
512mb with 10gb of space would be fine on xen. just create dummy files for templates with zero size to save space on solusvm master.
The specs needed really depends on how busy your database is. For our master we have a dedicated box for it with no VMs, on an E3-1230 with 2x drives in HW RAID1 and 16GB of RAM. It's already overkill for our needs but as our database is quite busy at times so we want to leave a little wiggle room, and this master box will suit us for a while as it leaves lots of room for future growth.
1GB RAM is safe.
I I use a DigitalOcean SSD VPS with 1GB RAM and 20GB of disk. It's more than enough!
I have a 1GB Box with BuyVM
Mine is a simple 1Gb box at Hostigation.
Most likely going with a 1gb BuyVM for this
Are you all saying that your SolusVM master is in a different datacenter/provider than the servers from which you are provisioning from?
Maybe a different DC isn't that weird if latency isn't a big deal, and I suppose it has to happen for those who have multiple locations...but on a VPS provided by another company...?
If you have no plans to store the OS images on the master, it'd take very little space, and it'd run nicely with 256MB of RAM. However to be safe, just make sure you can upgrade the plan along the way.
What's wrong with you all, we use 256MB openvz and usage never goes above half.
"Hey guys, we'll try be the edgy little cunts we are and run SolusVM with 64MB RAM! Oh boy, I can't fucking wait for something to blow up and we're screwed!"
Seriously? Re-think your business.
@GetKVM_Ash yup 256MB is what we run our solus on, planning to move all the internal stuff on to a box soon.
Had too many disasters with VPS Providers.(Last time sandy took out our master, without a recent backup and it had to be rebuilt).
@murky who are you referring too?
Backup backup backup
@ShardHost FTP Backups are put on a shared account, which I completely forgot that HostGator issued me a new IP Address, and when the time come and I checked the directory. Oh shii..!
You need more at times, e.g. when adding a tonne of IPv6
I've never had any problems adding ipv6 pools
We run our Solus master on a 1GB VPS, but it never uses more than 256MB usually.
Exactly the same, openvz 256mb ram. Does its job.
Our Master is currently consuming around 2GB of RAM on a KVM box (around 10-12 slaves are connected to it). All our internal stuff are hosted on Dual quad xeon with 16 gigs of RAM.
This.
Realistically, SolusVM can run on as little as 256 mb of ram. Size reducing MySQL config + replacing the current httpd with nginx (they have a script on their wiki), it really doesn't need much. Just PHP.
If you get more than 20 gb of templates, you should look into ways to reduce your impact. I'm working on switching our KVM infrastructure from ISO's to PXE boot... for OpenVZ and Xen you can have an init script that pulls the bulk of everything on first boot.
We using a 4 VMs in an Raid10 GlusterFS setup to provide a ha environment for our templates and isos. We don´t host any templates on the solusvm master. So we need only two VMs with 20GB space and 512MB RAM. Both VMs are hosted on a DRBD nodes to provide a fail-over mechanism.
512MB Gigenet Cloud works ace, creating empty files for templates/isos so only use few gb disk space on master.