|
|
|
|
|
|
|
|
| Re: Existing Templates [message #726 is a reply to message #646] |
Sat, 07 January 2006 16:15   |
AndyS
Messages: 3
Registered: January 2006
|
Junior Member |
|
|
| Quote: |
Can you tell which ones have you tried, and why you found OpenVZ better than those?
|
Sure. I've tested most that i've come across, since the early days of FreeVSD, including Vserver, FreeVPS and so forth.
The main problem with all systems is **minor bugs** - However, if your trying to setup a professional hosting business, these bugs are more like major ones.
I find OpenVZ Much better as its quick to install and setup. I had it installed on a sandbox, 2 templates installed and 5 VPS's up and running in just over an hour.
It appears all VPS report correct stats. e.g, quotas, memory allocaton etc. This was a major problem using VServer.
VPS's remained up and running 2 days after booting them. Luckly their is the --onboot command, but this has not been needed so far. unlike vserver where the --onboot didn't work and i needed to manually boot 2 our of 3 servers manually on a daily bases
Installation of Webmin and Usermin works 100% - Using Vserver and others e.g FreeVPS this was hell to run.
I even got CPanel installed (i admit, i could not test it as i dont have a licnece, but it installed with minimal errors)
Ones that i've tested since the early days are FreeVPS, OpenVPS, FreeVSD, VServer, UML, Xen to name a few. All have errors from speed through to incorrect stats.
Im not yet up and running with a vps business yet, because of the above errors. Although with OpenVZ this could be possable sometime this year.
One downfall which i was hoping to see in OpenVZ is name-based servers instead of just IP Based. Only because when i start offering VPS i want to offer a 1 week trial. As you can guess, doing so people are going to sign up left right and center, costing me an arm and a leg buying new IP Addys.
|
|
|
|
|
|
| Re: Existing Templates [message #730 is a reply to message #646] |
Sun, 08 January 2006 05:39 |
phpfreak
Messages: 47
Registered: January 2006
|
Member |
|
|
Here's how I found out how to create some easily customized templates.
1.) create a temporary ve and start it up:
vzctl create 1000 --ostemplate centos-4-i386-default
vzctl start 1000
vzctl enter 1000
(now type: su -)
2.) Now that you have your VE created, go ahead and make all of your customizations. Install whatever you want, custom compile anything, tweak out the various things you like, install custom firewall scripts etc. Then exit out.
exit
exit
3.) Shut down the VE
vzctl stop 1000
4.) Now, cd into the vz private directory on the host:
cd /vz/private/1000
5.) Next, tarball the root of the VE:
tar czpf /vz/template/cache/centos-4-i386-mycoolvz.tar.gz *
Now your template is ready to go. You can create a new copy of this VE anytime you want. Don't worry about the hostname, IP's or root passwords because you can reset those when you create a copy of your VE later on.
Here's a tip for you though, something I think works. If you don't name the template tarball such as 'centos-4-i386-xxx' and just name it 'myvz.tar.gz' when you create the VE you'll get a message that it could not find the distro type or something to that effect. That means that it won't use the template inside the centos directory to run the install-pre and install-post items and it wont obey the package lists in the spec files. In other words, it's an easy way to avoid having anything reinstalled on your VE that you uninstalled in your custom setup, when you go to recreate it.
Hope that info helps. I may be smoking crack, but it works well for me 
Eric Rosebrock
http://www.serverpowered.com
http://www.hybodus.com
http://www.linuxforum.com
http://www.phpfreaks.com
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Existing Templates [message #748 is a reply to message #735] |
Mon, 09 January 2006 07:21 |
|
|
| vmvmvm wrote on Sun, 08 January 2006 09:17 |
1. are their special openvz files in the filesystem that should also be updated? It seems to work either way...
|
No. OpenVZ tries to be as much as a real system, so no special stuff is needed. Also, see below
| Quote: |
2. when openvz sets the ip, hostname, etc. is it running commands to do so? Does it just rely on the fact that most linux's will use /etc/resolv.conf for nameservers, etc.?
|
For doing these operations, vzctl relies on a set of scripts in /etc/sysconfig/vz-scripts/dists/scripts/, and a few configs in the /etc/sysconfig/vz-scripts/dists/. vzctl first gets the value of OSTEMPLATE variable from VPS config file, then reads the appropriate config file, then executes the proper script.
So, for this to work properly, OSTEMPLATE should be set in VPS config (and should be valid, e.g. start from the word 'gentoo' for gentoo-based VPS), and a config file and a set of scripts for this OSTEMPLATE should exist.
Kir Kolyshkin
|
|
|
|
|
|
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
(
