Forum OpenACS Q&A: Re: Gush: vservers as development/production environment

Collapse
16: Re: Gush: vservers as development/production environment (response to 1)
Posted by Carl Robert Blesius on 06/19/05 07:33 AM
I am finally taking the plunge and have a couple of initial questions about a Vserver setup. I have a ProLiant DL360 (as lound as a vacuum cleaner) on my dinning room table that I want to move to the server room asap (before my neighbors start to complain). It has U320 SCSI drives - RAID 1 (146.8GB mirrored) and 8GB RAM.

1. How much space do you typically give the vserver host OS?

2. Have any file system recommendations (e.g. ext3 vs. ReiserFS vs. XFS)? I am tending towards XFS (after doing some reading).

3. Any tips on partitioning? Documentation on the web tends to recommend a partition per vserver. Possibly relevant: I plan to separate the DB Server from the web server(s) and plan to keep CR files on the FS.

I am going to have a real system admin helping me set this up, but any preliminary vserver related input would be great (this is stuff I have to do before he can log on).

Thanks,
Carl

P.S. How easy is it to change the size of a Vserver guest OS?

Collapse
17: Re: Re: Gush: vservers as development/production environment (response to 16)
Posted by Carl Robert Blesius on 06/19/05 08:22 PM
Some feedback I got per email:

1. How much space do you typically give the vserver host OS?

--It's going to depend on what the host OS is running. Allow ample room for log files, but unless you plan to do anything substantive in the host, it doesn't need all that much.

2. Have any file system recommendations (e.g. ext3 vs. ReiserFS vs. XFS)? I am tending towards XFS (after doing some reading).

--There were problems at one point with vservers and JFS. Beyond that, no specific advice. I use ext3 since that's what is usually installed on the box when the datacenter turns it over.

3. Any tips on partitioning? Documentation on the web tends to recommend a partition per vserver. Possibly relevant: I plan to separate the DB Server from the web server(s) and plan to keep CR files on the FS.

--If you trust your users (or yourself, if these are all yours), don't. You get a lot more flexibility if you don't chop your space into little bits. If you feel partitioning is essential, you're going to have to work out what your space needs are going to be.