The nginx Web server and reverse proxy server has already posted impressive numbers in the Web server market as a small open source project. Now the project's creator, Igor Sysoev, is taking a run at turning nginx into a company. Will nginx shake things up?
Comments (0)
SeaMicro says it has packed more Intel Atom processors into a new device it claims is the most power-efficient x86 server on the market. The SM10000-64HD has 384 N570 chips, 1.5 terabytes of DDR3 memory, up to 64 SATA hard disks or solid state drives, and from eight to 64 gigabit Ethernet ports, the company says....
Comments (0)Continuous integration (CI) is a software engineering practice that aims to minimize software development time while applying rigorous quality control from the beginning and at every step of the process. If you’re ready to jump on the CI bandwagon, turn to Jenkins CI.
Continuous integration (CI) is a software engineering practice that aims to minimize software development time while applying rigorous quality control from the beginning and at every step of the process. If you’re ready to jump on the CI bandwagon, turn to Jenkins CI.
The need for faster and better software development methods is nothing new. What’s changed lately is the fact that it’s almost impossible to stay competitive if you don’t use the best new tools. Factors such as globalization, outsourcing, and crowdsourcing have increased the time pressure on software development teams, while adding to the likelihood that team members cannot meet regularly to debug and test their code.
This tutorial explains the installation of a Samba fileserver on OpenSUSE 11.4 and how to configure it to share files over the SMB protocol as well as how to add users. Samba is configured as a standalone server, not as a domain controller. In the resulting setup, every user has his own home directory accessible via the SMB protocol and all users have a shared directory with read-/write access.
New release sees a major boost in handling small objects at over 200,000 requests per second in benchmarks. Traffic Server also builds on Mac OS X, Solaris and FreeBSD now...
New release sees a major boost in handling small objects at over 200,000 requests per second in benchmarks. Traffic Server also builds on Mac OS X, Solaris and FreeBSD now
Officials with Calxeda, the startup that's building ARM-based chips for low-power data center servers, announced a & Trailblazer& program designed to create an ecosystem around its technology. But, while Calxeda touted support from Ubuntu Linux sponsor Canonical, among other companies, there's been no hint from Microsoft that it will create...
Officials with Calxeda, the startup that's building ARM-based chips for low-power data center servers, announced a & Trailblazer& program designed to create an ecosystem around its technology. But, while Calxeda touted support from Ubuntu Linux sponsor Canonical, among other companies, there's been no hint from Microsoft that it will create a server edition of its ARM-based & Windows 8.& ...
The VPN is very often critical to working within a company. With working from home being such a popular draw to many industries, it is still necessary to be able to access company folders and hardware that exists within the LAN. When outside of that LAN, one of the best ways to gain that access is with the help of a VPN. Many VPN solutions are costly, and/or challenging to set up and manage. Fortunately, for the open source/Linux community, there is a solution that is actually quite simple to set up, configure, and manage. OpenVPN is that solution and here you will learn how to set up the server end of that system.
The VPN is very often critical to working within a company. With working from home being such a popular draw to many industries, it is still necessary to be able to access company folders and hardware that exists within the LAN. When outside of that LAN, one of the best ways to gain that access is with the help of a VPN. Many VPN solutions are costly, and/or challenging to set up and manage. Fortunately, for the open source/Linux community, there is a solution that is actually quite simple to set up, configure, and manage. OpenVPN is that solution and here you will learn how to set up the server end of that system.
I will be setting OpenVPN up on a Ubuntu 11.04, using Public Key Infrastructure with a bridged Ethernet interface. This setup allows for the quickest route to getting OpenVPN up and running, while maintaining a modicum of security.
The first step (outside of having the operating system installed) is to install the necessary packages. Since I will installing on Ubunutu, the installation is fairly straightforward:
Open up a terminal window.Run sudo apt-get install openvpn to install the OpenVPN package.Type the sudo password and hit Enter.Accept any dependencies.There is only one package left to install — the package that allows the enabling of bridged networking. Setting up the bridge is simple, once you know how. But before the interface can be configured to handle bridged networking, a single package must be installed. Do the following:
Install the necessary package with the command sudo apt-get install bridge-utils.Edit the /etc/network/interfaces file to reflect the necessary changes (see below).Restart networking with the command sudo /etc/init.d/networking restart .Open up the /etc/network/interfaces file and make the necessary that apply to your networking interface, based on the sample below:
auto loiface lo inet loopbackauto br0iface br0 inet static address 192.168.100.10 network 192.168.100.0 netmask 255.255.255.0 broadcast 192.168.100.255 gateway 192.168.100.1 bridge_ports eth0 bridge_fd 9 bridge_hello 2 bridge_maxage 12 bridge_stp offMake sure to configure the bridge section (shown above) to match the correct information for your network. Save that file and restart networking. Now it's time to start configuring the VPN server.
The OpenVPN server will rely on certificate authority for security. Those certificates must first be created and then placed in the proper directories. To do this, follow these steps:
Create a new directory with the command sudo mkdir /etc/openvpn/easy-rsa/.Copy the necessary files with the command sudo cp -r /usr/share/doc/openvpn/examples/easy-rsa/2.0/* /etc/openvpn/easy-rsa/.Change the ownership of the newly copied directory with the command sudo chown -R $USER /etc/openvpn/easy-rsa/.Edit the file /etc/openvpn/easy-rsa/vars and change the variables listed below.The variables to edit are:
export KEY_COUNTRY="US"export KEY_PROVINCE="KY"export KEY_CITY="Louisville"export KEY_ORG="Monkeypantz"export KEY_EMAIL=" This e-mail address is being protected from spambots. You need JavaScript enabled to view it "Once the file has been edited and saved, we'll run several commands must be entered in order to create the certificates:
cd /etc/openvpn/easy-rsa/source vars./clean-all./build-dh./pkitool --initca./pkitool --server servercd keyssudo openvpn --genkey --secret ta.keysudo cp server.crt server.key ca.crt dh1024.pem ta.key /etc/openvpn/The clients will need to have certificates in order to authenticate to the server. To create these certificates, do the following:
cd /etc/openvpn/easy-rsa/source vars./pkitool hostnameHere the hostname is the actual hostname of the machine that will be connecting to the VPN.
Now, certificates will have to be created for each host needing to connecting to the VPN. Once the certificates have been created, they will need to be copied to the respective clients. The files that must be copied are:
/etc/openvpn/ca.crt/etc/openvpn/ta.key/etc/openvpn/easy-rsa/keys/hostname.crt (Where hostname is the hostname of the client)./etc/openvpn/easy-rsa/keys/hostname.key (Where hostname is the hostname of the client).Copy the above using a secure method, making sure they are copied to the /etc/openvpn directory.
It is time to configure the actual VPN server. The first step is to copy a sample configuration file to work with. This is done with the command sudo cp /usr/share/doc/openvpn/examples/sample-config-files/server.conf.gz /etc/openvpn/. Now decompress the server.conf.gz file with the command sudo gzip -d /etc/openvpn/server.conf.gz. The configuration options to edit are in this file. Open server.conf up in a text editor (with administrative privileges) and edit the following options:
local 192.168.100.10dev tap0up "/etc/openvpn/up.sh br0"down "/etc/openvpn/down.sh br0"server-bridge 192.168.100.101 255.255.255.0 192.168.100.105 192.168.100.200push "route 192.168.100.1 255.255.255.0"push "dhcp-option DNS 192.168.100.201"push "dhcp-option DOMAIN example.com"tls-auth ta.key 0 # This file is secretuser nobodygroup nogroupIf you're unsure of any of the options, here:
The local address is the IP address of the bridged interface.The server-bridge is needed in the case of a bridged interface.The server will push out the IP address range of 192.168.100.105-200 to clients.The push directives are options sent to clients.Before the VPN is started (or restarted) a couple of scripts will be necessary to add the tap interface to the bridge (If bridged networking is not being used, these scripts are not necessary.) These scripts will then be used by the executable for OpenVPN. The scripts are /etc/openvpn/up.sh and /etc/openvpn/down.sh.
#!/bin/sh#This is /etc/openvpn/up.shBR=$1DEV=$2MTU=$3/sbin/ifconfig $DEV mtu $MTU promisc up/usr/sbin/brctl addif $BR $DEV#!/bin/sh#This is/etc/openvpn/down.shBR=$1DEV=$2/usr/sbin/brctl delif $BR $DEV/sbin/ifconfig $DEV downBoth of the scripts will need to be executable, which is done with the chmod command:
sudo chmod 755 /etc/openvpn/down.shsudo chmod 755 /etc/openvpn/up.shFinally, restart OpenVPN with the command sudo /etc/init.d/openvpn restart. The VPN server is now ready to accept connections from clients (the topic of my next tutorial.)
One thing that is a must for a VPN is that the machine hosting the VPN has to be accessible to the outside world — assuming users are coming in from the outside world. This can be done by either giving the server an external IP address or by routing traffic from the outside in with NAT rules (which can be accomplished in various ways). It will also be critical to employ best security practices (especially if the server has an external IP address) to prevent any unwanted traffic or users from getting into the server.
With a few weeks having passed since UDS Budapest where a lot of details concerning Ubuntu 11.10 "Oneiric Oncelot" were figured out and debated, and the features definition freeze now in effect, Canonical has announced the five core areas they'll be working on in this development cycle as it pertains to the Ubuntu Server release...
This guide explains how you can run virtual machines with VirtualBox 4.0 on a headless Ubuntu 11.04 server. Normally you use the VirtualBox GUI to manage your virtual machines, but a server does not have a desktop environment. Fortunately, VirtualBox comes with a tool called VBoxHeadless that allows you to connect to the virtual machines over a remote desktop connection, so there's no need for the VirtualBox GUI.
I do not issue any guarantee that this will work for you!
I have tested this on an Ubuntu 11.04 server (host system) with the IP address 192.168.0.100 where I'm logged in as a normal user (user name administrator in this example) instead of as root.
To install VirtualBox 4.0 on our Ubuntu 11.04 server, we open /etc/apt/sources.list...
sudo vi /etc/apt/sources.list... and add the following line to it:
[...]deb http://download.virtualbox.org/virtualbox/debian natty contribThen we download the VirtualBox public key...
wget -q http://download.virtualbox.org/virtualbox/debian/oracle_vbox.asc -O- | sudo apt-key add -... and update our package database:
sudo apt-get updateAfterwards, we install VirtualBox 4.0 as follows:
sudo apt-get install linux-headers-$(uname -r) build-essential virtualbox-4.0 dkms(The dkms package ensures that the VirtualBox host kernel modules are properly updated if the Linux kernel version changes.)
Starting with version 4.0, VirtualBox has introduced so called "extension packs" and has outsourced some functionality like remote desktop connection support (VRDP) that was part of VirtualBox packages before version 4.0 into these extension packs. Because we need remote desktop connections to control our virtual machines, we need to install the appropriate extension pack now. Go to http://www.virtualbox.org/wiki/Downloads, and you will find a link to the following extension pack:
VirtualBox 4.0.6 Oracle VM VirtualBox Extension PackDownload and install the extension pack as follows:
cd /tmp(Make sure you grab the latest version from the VirtualBox web site.)
(Make sure you run the last command with sudo - sudo VBoxManage extpack install ... - because otherwise you will get an error like this:
administrator@server1:/tmp$ VBoxManage extpack install Oracle_VM_VirtualBox_Extension_Pack-4.0.6-71344.vbox-extpack)
Now we must add the user that will run VirtualBox (administrator in this example) to the vboxusers group:
sudo adduser administrator vboxusersVirtualBox is now installed and ready to be used.
To create a VM on the command line, we can use the VBoxManage command. See
VBoxManage --helpfor a list of available switches and (highly recommended!) take a look at http://www.virtualbox.org/manual/ch08.html.
I will now create an Ubuntu 11.04 Server VM with 512MB memory and a 10GB hard drive from the Ubuntu 11.04 Server iso image (which I have stored in /home/ubuntu-11.04-server-amd64.iso):
VBoxManage createvm --name "Ubuntu 11.04 Server" --registerLet's assume you have a VM called examplevm that you want to reuse on this host. On the old host, you should have a directory Machines/examplevm in the VirtualBox directory; Machines/examplevm should contain the examplevm.xml file. Copy the examplevm directory (including the examplevm.xml file) to your new Machines directory (if your user name is administrator, this is /home/administrator/.VirtualBox/Machines - the result should be /home/administrator/.VirtualBox/Machines/examplevm/examplevm.xml).
In addition to that copy the examplevm.vdi file from the old VDI directory to the new one (e.g. /home/administrator/.VirtualBox/VDI/examplevm.vdi).
Afterwards, you must register the imported VM:
VBoxManage registervm Machines/examplevm/examplevm.xmlRegardless of if you create a new VM or import an old one, you can start it with the command:
VBoxHeadless --startvm "Ubuntu 11.04 Server"(Replace Ubuntu 11.04 Server with the name of your VM.)
VBoxHeadless will start the VM and a VRDP (VirtualBox Remote Desktop Protocol) server which allows you to see the VM's output remotely on another machine.
To stop a VM, run
VBoxManage controlvm "Ubuntu 11.04 Server" poweroffTo pause a VM, run
VBoxManage controlvm "Ubuntu 11.04 Server" pauseTo reset a VM, run
VBoxManage controlvm "Ubuntu 11.04 Server" resetTo learn more about VBoxHeadless, take a look at
VBoxHeadless --helpand at http://www.virtualbox.org/manual/ch07.html#vboxheadless.
VBoxHeadless - Running Virtual Machines With VirtualBox 4.0 On A Headless Ubuntu 11.04 Server - Page 2This tutorial explains the installation of a Samba fileserver on Fedora 14 and how to configure it to share files over the SMB protocol as well as how to add users. Samba is configured as a standalone server, not as a domain controller. In the resulting setup, every user has his own home directory accessible via the SMB protocol and all users have a shared directory with read-/write access.
I do not issue any guarantee that this will work for you!
I'm using a Fedora 14 system here with the hostname server1.example.com and the IP address 192.168.0.100.
Please make sure that SELinux is disabled as shown in chapter 5 of this tutorial: The Perfect Server - Fedora 14 x86_64 [ISPConfig 2] - Page 3
Connect to your server on the shell and install the Samba packages:
yum install cups-libs samba samba-commonEdit the smb.conf file:
vi /etc/samba/smb.confMake sure you see the following lines in the [global] section:
[...]# ----------------------- Standalone Server Options ------------------------## security = the mode Samba runs in. This can be set to user, share# (deprecated), or server (deprecated).## passdb backend = the backend used to store user information in. New# installations should use either tdbsam or ldapsam. No additional configuration# is required for tdbsam. The "smbpasswd" utility is available for backwards# compatibility.# security = user passdb backend = tdbsam[...]This enables Linux system users to log in to the Samba server.
Then create the system startup links for Samba and start it:
chkconfig --levels 235 smb onNow I will add a share that is accessible by all users.
Create the directory for sharing the files and change the group to the users group:
mkdir -p /home/shares/allusersAt the end of the file /etc/samba/smb.conf add the following lines:
vi /etc/samba/smb.confIf you want all users to be able to read and write to their home directories via Samba, add the following lines to /etc/samba/smb.conf (make sure you comment out or remove the other [homes] section in the smb.conf file!):
[...][homes] comment = Home Directories browseable = no valid users = %S writable = yes create mask = 0700 directory mask = 0700Now we restart Samba:
/etc/init.d/smb restartIn this example, I will add a user named tom. You can add as many users as you need in the same way, just replace the username tom with the desired username in the commands.
useradd tom -m -G usersSet a password for tom in the Linux system user database. If the user tom should not be able to log into the Linux system, skip this step.
passwd tom-> Enter the password for the new user.
Now add the user to the Samba user database:
smbpasswd -a tom-> Enter the password for the new user.
Now you should be able to log in from your Windows workstation with the file explorer (address is \\192.168.0.100 or \\192.168.0.100\tom for tom's home directory) using the username tom and the chosen password and store files on the Linux server either in tom's home directory or in the public shared directory.
This article describes how you can upgrade your Fedora 14 system to Fedora 15. The upgrade procedure works for both desktop and server installations.
I do not issue any guarantee that this will work for you!
The commands in this article must be executed with root privileges. Open a terminal (on a Fedora 14 desktop, go to Applications > System Tools > Terminal) and log in as root, or if you log in with a regular user, type
suto become root.
Please make sure that the system that you want to upgrade has more than 600 MB of RAM - otherwise the system might hang when it tries to reboot with the following message (leaving you with an unusable system):
Trying to unpack rootfs image as initramfs...First we must upgrade the rpm package:
yum update rpmThen we install the latest updates:
yum -y updateNext we clean the yum cache:
yum clean allIf you notice that a new kernel got installed during yum -y update, you should reboot the system now:
reboot(After the reboot, log in as root again, either directly or with the help of
su)
Now we come to the upgrade process. We can do this with preupgrade (preupgrade will also take care of your RPMFusion packages).
Install preupgrade...
yum install preupgrade... and call it like this:
preupgradeThe preupgrade wizard will then start on your desktop. Select Fedora 15 (Lovelock). Afterwards the system is being prepared for the upgrade.
At the end, click on the Reboot Now button.
During the reboot, the upgrade is being performed. This can take quite a long time, so please be patient.
Afterwards, you can log into your new Fedora 15 desktop.
First we must upgrade the rpm package:
yum update rpmThen we install the latest updates:
yum -y updateNext we clean the yum cache:
yum clean allIf you notice that a new kernel got installed during yum -y update, you should reboot the system now:
reboot(After the reboot, log in as root again, either directly or with the help of
su)
Now we come to the upgrade process. We can do this with preupgrade.
Install preupgrade...
yum install preupgrade... and call it like this:
preupgrade-cliIt will show you a list of releases that you can upgrade to. If all goes well, it should show something like Fedora 15 (Lovelock) in the list:
[root@server1 ~]# preupgrade-cliTo upgrade, append the release string to the preupgrade-cli command:
preupgrade-cli "Fedora 15 (Lovelock)"Preupgrade will also take care of your RPMFusion packages, so all you have to do after preupgrade has finished is to reboot:
rebootDuring the reboot, the upgrade is being performed. This can take quite a long time, so please be patient. Afterwards, you can log into your new Fedora 15 server.
Apple's Jeremy Huddleston has just released X.Org Server 1.10.2. This second point release was set to be released yesterday, but then there was fear of a regression causing a delay (turns out it's no longer reproducible), so now we have a holiday weekend release of xorg-server 1.10.2...
Version 1.0
Author: Falko Timme 
Follow me on Twitter
Last edited 04/28/2011
The new Ubuntu 11.04 (Natty Narwhal) has just been released. This guide shows how you can upgrade your Ubuntu 10.10 desktop and server installations to Ubuntu 11.04.
This document comes without warranty of any kind! I do not issue any guarantee that this will work for you!
Start the Update Manager (System > Administration > Update Manager):
The Update Manager should show that a new distribution release (11.04) is available. Click on the Upgrade button to start the distribution upgrade:
A window with the release notes for 11.04 comes up. Click on Upgrade again:
The upgrade tool is now being downloaded. Afterwards, type in your password:
The upgrade is being prepared:
Click on Start Upgrade to finally begin with the upgrade process:
The upgrade packages are now being downloaded...
... and installed. This can take some time, so please be patient.
At the end of the upgrade process, you should remove obsolete packages:
The system needs to be rebooted to complete the upgrade, therefore click on Restart Now:
When you log in, Ubuntu 11.04 will by default start the new Unity desktop which requires that your hardware supports 3D acceleration. If it doesn't, you can choose the Ubuntu Classic desktop at the login screen instead:
After the reboot, you can use your new Ubuntu 11.04 desktop (because I used a virtual machine for this tutorial, the system has no 3D support, that's why you see the Ubuntu Classic desktop in the screenshot below):
ow To Upgrade Ubuntu 10.10 (Maverick Meerkat) To 11.04 (Natty Narwhal) (Desktop & Server) - Page 2
Anthony Nordquist has announced the release of SalineOS 1.4, a Debian-based desktop distribution with Xfce, and SalineOS 1.0 "Personal Server" edition, a Debian-based distribution for home servers: "SalineOS Personal Server edition 1.0 is now available. The Personal Server edition is designed to make setting up small personal home....
A new version of Superb Mini Server (SMS), a Slackware-based distribution for servers, was announced earlier today: "Superb Mini Server version 1.6.0 released. SMS 1.6.0 is based on Slackware Linux 13.37 and ships with Linux kernel 2.6.37.6 to honor our compatibility with the new Slackware release; the 2.6.38.4....
Read more at DistroWatch
This guide explains how you can install and use KVM for creating and running virtual machines on an OpenSUSE 11.4 server. I will show how to create image-based virtual machines and also virtual machines that use a logical volume (LVM). KVM is short for Kernel-based Virtual Machine and makes use of hardware virtualization, i.e., you need a CPU that supports hardware virtualization, e.g. Intel VT or AMD-V.
I do not issue any guarantee that this will work for you!
I'm using an OpenSUSE 11.4 server with the hostname server1.example.com and the IP address 192.168.0.100 here as my KVM host.
We also need a desktop system where we install virt-manager so that we can connect to the graphical console of the virtual machines that we install. I'm using an OpenSUSE 11.4 desktop here.
OpenSUSE 11.4 KVM Host:First check if your CPU supports hardware virtualization - if this is the case, the command
egrep '(vmx|svm)' --color=always /proc/cpuinfoshould display something, e.g. like this:
server1:~ # egrep '(vmx|svm)' --color=always /proc/cpuinfoIf nothing is displayed, then your processor doesn't support hardware virtualization, and you must stop here.
One of the dependencies that gets installed when we install KVM is Python 2.7, but Python 2.7 conflicts with the package patterns-openSUSE-minimal_base. Therefore we must uninstall that package first. To do so, start YaST:
yast2In YaST, go to Software > Software Management:
Type patterns-openSUSE-minimal_base in the Search field and press ENTER. The package should be listed as installed (i) in the main window. Mark the package and press the ENTER key until there's a minus (-) sign in front of the package (the minus stands for uninstall), then hit [Accept]:
As a replacment for the package, some other packages need to be installed. Accept the selection by hitting [OK]:
Leave YaST afterwards.
To install KVM and virtinst (a tool to create virtual machines), we run
yast2 -i kvm libvirt libvirt-python qemu virt-managerThen create the system startup links for libvirtd...
chkconfig --add libvirtd... and start the libvirt daemon:
/etc/init.d/libvirtd startTo check if KVM has successfully been installed, run
virsh -c qemu:///system listIt should display something like this:
server1:~ # virsh -c qemu:///system listserver1:~ #
If it displays an error instead, then something went wrong.
Next we need to set up a network bridge on our server so that our virtual machines can be accessed from other hosts as if they were physical systems in the network.
To do this, we install the package bridge-utils...
yast2 -i bridge-utils... and configure a bridge.
To configure the bridge, create the file /etc/sysconfig/network/ifcfg-br0 as follows (make sure you use the IPADDR setting from the /etc/sysconfig/network/ifcfg-eth0 file):
vi /etc/sysconfig/network/ifcfg-br0(If you get the message You do not have a valid vim binary package installed. Please install either "vim", "vim-enhanced" or "gvim"., please run
yast2 -i vimto install vi and try again. )
Modify /etc/sysconfig/network/ifcfg-eth0 as follows (set IPADDR to 0.0.0.0 and change STARTMODE to hotplug):
vi /etc/sysconfig/network/ifcfg-eth0Then restart the network:
/etc/init.d/network restartAfterwards, run
ifconfigIt should now show the network bridge (br0):
server1:~ # ifconfigeth0 Link encap:Ethernet HWaddr 00:1E:90:F3:F0:02
inet6 addr: fe80::21e:90ff:fef3:f002/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:58 errors:0 dropped:0 overruns:0 frame:0
TX packets:65 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5995 (5.8 Kb) TX bytes:7381 (7.2 Kb)
Interrupt:41 Base address:0xe000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:100 (100.0 b) TX bytes:100 (100.0 b)
server1:~ #
OpenSUSE 11.4 Desktop:We need a means of connecting to the graphical console of our guests - we can use virt-manager for this. I'm assuming that you're using an OpenSUSE 11.4 desktop.
Become root...
su... and run...
yast2 -i virt-manager libvirt... to install virt-manager.
(If you're using an Ubuntu 10.10 desktop, you can install virt-manager as follows:
sudo aptitude install virt-manager)
OpenSUSE 11.4 KVM Host:
Now let's go back to our OpenSUSE 11.4 KVM host.
Take a look at
virt-install --helpto learn how to use it.
We will create our image-based virtual machines in the directory /var/lib/libvirt/images/ which was created automatically when we installed KVM in chapter two.
To create a Debian Squeeze guest (in bridging mode) with the name vm10, 512MB of RAM, two virtual CPUs, and the disk image /var/lib/libvirt/images/vm10.img (with a size of 12GB), insert the Debian Squeeze Netinstall CD into the CD drive and run
virt-install --connect qemu:///system -n vm10 -r 512 --vcpus=2 --disk path=/var/lib/libvirt/images/vm10.img,size=12 -c /dev/cdrom --vnc --noautoconsole --os-type linux --os-variant debiansqueeze --accelerate --network=bridge:br0 --hvmOf course, you can also create an ISO image of the Debian Squeeze Netinstall CD (please create it in the /var/lib/libvirt/images/ directory because later on I will show how to create virtual machines through virt-manager from your OpenSUSE 11.4 desktop, and virt-manager will look for ISO images in the /var/lib/libvirt/images/ directory)...
dd if=/dev/cdrom of=/var/lib/libvirt/images/debian-6.0.0-amd64-netinst.iso... and use the ISO image in the virt-install command:
virt-install --connect qemu:///system -n vm10 -r 512 --vcpus=2 --disk path=/var/lib/libvirt/images/vm10.img,size=12 -c /var/lib/libvirt/images/debian-6.0.0-amd64-netinst.iso --vnc --noautoconsole --os-type linux --os-variant debiansqueeze --accelerate --network=bridge:br0 --hvmThe output is as follows:
server1:~ # virt-install --connect qemu:///system -n vm10 -r 512 --vcpus=2 --disk path=/var/lib/libvirt/images/vm10.img,size=12 -c /var/lib/libvirt/images/debian-6.0.0-amd64-netinst.iso --vnc --noautoconsole --os-type linux --os-variant debiansqueeze --accelerate --network=bridge:br0 --hvmStarting install...
Allocating 'vm10.img' 100% |=========================| 12 GB 00:00
Creating domain... 0 B 00:00
Domain installation still in progress. You can reconnect to
the console to complete the installation process.
server1:~ #
This tutorial shows how to set up a CentOS 5.6 server (x86_64) that offers all services needed by ISPs and web hosters: Apache web server (SSL-capable), Postfix mail server with SMTP-AUTH and TLS, BIND DNS server, Proftpd FTP server, MySQL server, Dovecot POP3/IMAP, Quota, Firewall, etc. This tutorial is written for the 64-bit version of CentOS 5.6, but should apply to the 32-bit version with very little modifications as well. In the end you should have a system that works reliably, and if you like you can install the free webhosting control panel ISPConfig 2 (i.e., ISPConfig runs on it out of the box).
I will use the following software:
Web Server: Apache 2.2 with PHP 5.1.6 Database Server: MySQL 5.0 Mail Server: PostfixDNS Server: BIND9 (chrooted) FTP Server: ProftpdPOP3/IMAP server: DovecotWebalizer for web site statisticsPlease note that this setup does not work for ISPConfig 3! It is valid for ISPConfig 2 only!
I want to say first that this is not the only way of setting up such a system. There are many ways of achieving this goal but this is the way I take. I do not issue any guarantee that this will work for you!
To install such a system you will need the following:
In this tutorial I use the hostname server1.example.com with the IP address 192.168.0.100 and the gateway 192.168.0.1. These settings might differ for you, so you have to replace them where appropriate.
Boot from your first CentOS 5.6 CD (CD 1) or the first CentOS 5.6 DVD. Press
It can take a long time to test the installation media so we skip this test here:
The welcome screen of the CentOS installer appears. Click on Next:
Choose your language next:
Select your keyboard layout:
I'm installing CentOS 5.6 on a fresh system, so I answer Yes to the question Would you like to initialize this drive, erasing ALL DATA?
Now we must select a partitioning scheme for our installation. For simplicity's sake I select Remove linux partitions on selected drives and create default layout. This will result in a small /boot and a large / partition as well as a swap partition. Of course, you're free to partition your hard drive however you like it. Then I hit Next:
Answer the following question (Are you sure you want to do this?) with Yes:
On to the network settings. The default setting here is to configure the network interfaces with DHCP, but we are installing a server, so static IP addresses are not a bad idea... Click on the Edit button at the top right.
In the window that pops up uncheck Dynamic IP configuration (DHCP) and Enable IPv6 support and give your network card a static IP address (in this tutorial I'm using the IP address 192.168.0.100 for demonstration purposes) and a suitable netmask (e.g. 255.255.255.0; if you are not sure about the right values, http://www.subnetmask.info might help you):
Set the hostname manually, e.g. server1.example.com, and enter a gateway (e.g. 192.168.0.1) and up to two DNS servers (e.g. 8.8.8.8 and 145.253.2.75):
Choose your time zone Give root a password:
The Perfect Server - CentOS 5.6 x86_64 [ISPConfig 2] - Page 2
