[Vserver] How to build first vserver ?
Hi, I've been surfing a bit around in search of a guide on how to set up/build the first vserver - but haven't been able to locate one... My base vserver is up and running (with the vserver kernel) - the problem is creating a virtual server... I'm running WhiteBox Enterprise Linux 4 (a RHEL clone), but have difficulties figuring out how to create the distribution stuff - and where does it pick the RPM packages from ?? Any hints, links, instructions etc are appreciated ... /Brian ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] How to build first vserver ?
[EMAIL PROTECTED] (Brian Ipsen) writes:
My base vserver is up and running (with the vserver kernel) - the problem
is creating a virtual server... I'm running WhiteBox Enterprise Linux 4 (a
RHEL clone), but have difficulties figuring out how to create the
distribution stuff - and where does it pick the RPM packages from ??
Any hints, links, instructions etc are appreciated ...
I recommend to:
1. choose the best-fitting distribution from
/usr/lib/util-vserver/distributions; in your case, this is
probably fc4.
2. copy the files from there into a suitable directory under
/etc/vservers/.distributions/ :
| # cp -a /usr/lib/util-vserver/distributions/fc4 \
/etc/vservers/.distributions/wbel4
This directory ('wbel4') will be used later at the '-d' option
of the 'vserver ... build' command
3. adjust the initpre/initpost symlinks
4. depending on your installation method, you need to:
- create a sources.list for apt in the apt/ subdirectory, or
- adjust the yum repositories in the yum.repos.d/ subdir, or
- add/change files in the rpmlist.d/ subdir
When WhiteBox Enterprise Linux is like RHEL, you should now be
able to create new vservers with
| # vserver ... build -m yum ... -- -d wbel4
out-of-the-box (although it is strongly recommended to patch
yum).
Enrico
pgpuT9axiHWXz.pgp
Description: PGP signature
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
RE: [Vserver] How to build first vserver ?
Hi,
My base vserver is up and running (with the vserver
kernel) - the problem is creating a virtual server...
I'm running WhiteBox Enterprise Linux 4 (a RHEL clone),
but have difficulties figuring out how to create the
distribution stuff - and where does it pick the RPM
packages from ??
Any hints, links, instructions etc are appreciated ...
I recommend to:
1. choose the best-fitting distribution from
/usr/lib/util-vserver/distributions; in your case, this is
probably fc4.
2. copy the files from there into a suitable directory under
/etc/vservers/.distributions/ :
| # cp -a /usr/lib/util-vserver/distributions/fc4 \
/etc/vservers/.distributions/wbel4
This directory ('wbel4') will be used later at the '-d' option
of the 'vserver ... build' command
3. adjust the initpre/initpost symlinks
4. depending on your installation method, you need to:
- create a sources.list for apt in the apt/ subdirectory, or
- adjust the yum repositories in the yum.repos.d/ subdir, or
- add/change files in the rpmlist.d/ subdir
Okay, I guess I need to set up an apt or yum repository myself, since I'm
not aware of any public ones (WBEL uses the up2date command). - Next step is
to locate apt-get or yum, that will run on WBEL4..
When WhiteBox Enterprise Linux is like RHEL, you should now
be able to create new vservers with
| # vserver ... build -m yum ... -- -d wbel4
out-of-the-box (although it is strongly recommended to patch yum).
Okay - I'll try to see if I can get something up and running ... Otherwise
I'll be back for more info ;-)
Regards,
/Brian
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] FC4 Guest
On Tue, 19 Jul 2005, Darryl Ross wrote: Then it's a case of cleaning up the initscripts so they don't do anything with hardware and stopping programs that aren't needed (kudzu, ntpd, etc etc) inside a guest. BTW - OpenVPS does all that for FC4 (you'll need the latest snapshots for FC4 though). Grisha ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] Re: About v2.0
Le mardi 19 Juillet 2005 07:33, Herbert Poetzl a écrit : it will take a few more days (maybe a fortnight) until we are convinced that it is _final_ and 2.0 will then be release (of course, shortly after that release, a lot of bugs/issues will be discovered, when the folks waiting for a stable release start using it, instead of testing the release candidates :) (Lol.) I'd like to help by testing the last rc (At home, it's holiday time here). But the problem is that apart from creating a vserver, starting it and applause, I don't really know what can be done to _really_ test it... Is there a check-list somewhere ? Some specific torture tests you'd like to be run ? Would it be interresting to create a torture documentation on the wiki ? -- Brigandage et truandage politique sont les deux gamelles de la France. SIM pgp8jocf9E94N.pgp Description: PGP signature ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
RE: [Vserver] How to build first vserver ?
When WhiteBox Enterprise Linux is like RHEL, you should now be able to create new vservers with | # vserver ... build -m yum ... -- -d wbel4 out-of-the-box (although it is strongly recommended to patch yum). Okay - I'll try to see if I can get something up and running ... Otherwise I'll be back for more info ;-) I may be wrong, but I think that WBEL uses Yum as the backend to up2date. Up2date by default is hardwired to RH servers, so they changed it to work the same but use yum instead. I might be mixing this up with one of the other RHEL clones, so forgive me if I'm off on this. ... Ah, just confirmed: http://www.whiteboxlinux.org/faq.html WBEL does use yum, which means I'm not crazy. -- Matthew Nuzum [EMAIL PROTECTED] www.followers.net - Makers of Elite Content Management System View samples of Elite CMS in action by visiting http://www.followers.net/portfolio/ ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Re: About v2.0
On Tue, Jul 19, 2005 at 07:32:17PM +0200, Nicolas Costes wrote: Le mardi 19 Juillet 2005 07:33, Herbert Poetzl a écrit : it will take a few more days (maybe a fortnight) until we are convinced that it is _final_ and 2.0 will then be release (of course, shortly after that release, a lot of bugs/issues will be discovered, when the folks waiting for a stable release start using it, instead of testing the release candidates :) (Lol.) I'd like to help by testing the last rc (At home, it's holiday time here). But the problem is that apart from creating a vserver, starting it and applause, I don't really know what can be done to _really_ test it... basically everybody has a slightly different setup and different usage for linux-vserver so 'just' testing it already provides valuable information, especially if something doesn't work as expected ... (although we always prefer reports stating It just works great!) Is there a check-list somewhere ? basically the 'feature' list on the Release FAQ page (http://linux-vserver.org/Release+FAQ) gives a good idea what could/should be tested ... of course, previous issues/incidents or security in general might be a good idea to test too (you can't really overdo it here :) Some specific torture tests you'd like to be run ? benchmarks, stress tests (inside and outside a guest) special conformance tests (like for example the LTP) but the important part is to classify the results and feed back the 'distilled' information of interest to the developers (or make some fancy marketing paper like the one showing that Xen really rocks :) Would it be interresting to create a torture documentation on the wiki ? of course, and even better would be to create some kind of linux-vserver test project (for performance and regression testing), that would definitely improve linux-vserver in the long run ... btw, I already started some regression testsing with the testme.sh and testfs.sh scripts (which focus on general functionality and xid/xattr tests) very important (but until now not really covered) areas would IMHO be: - limits and accounting - process and resource isolation - virtualization - scheduler testing best, Herbert -- Brigandage et truandage politique sont les deux gamelles de la France. SIM ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
