Proxmox 2.2 has some updates which have been pushed to the stable repository. There is no new functionality added with these updates, they are just bug fixes.
Reading the forum, there looks to be an issue with this update if you have turned off being able to login to SSH with passwords and enabled keys on your Proxmox host. It looks like the keys are removed and you will need to login to the local shell to re-create the keys. Updating a standard cluster works fine.
Before updating, make sure all your VM’s have been stopped. Run the below commands on each server in your cluster.
apt-get update
apt-get dist-upgrade
Restart all Proxmox servers to complete the installation.
For more information, visit the forum post on Proxmox.com.
Since the 2.6.18-028stable021 kernel, it has been possible to set the I/O priority of an OpenVZ container. It is not currently possible to set any I/O limits for containers, only the priority. If you require I/O limits you should use KVM.
The higher the priority is for a container, the more time the container will have for using disks. You can choose between 0 – 7 inclusive, the default value is 4. The higher the value you use, the more I/O time your container will receive. Remember, as this is a priority system each container setting is relative to another. For example, if you set all your containers to priority 7, they will still receive the same amount of I/O time each.
To set the I/O priority of an OpenZV container, login to the host using the console and use the below command.
vzctl set [VM ID] --ioprio [Priority] --save
Replace [VM ID] with the ID of the container you would like to modify, and replace [Priority] with the priority value to use between 0 and 7. The below example sets the priority of container 200 to 7.
vzctl set 200 --ioprio 7 --save
You can also edit the config file directly. In Proxmox this is saved in /etc/pve/openvz/[VMID].conf
Add, or change the existing entry in the conf file to: IOPRIO=”[Priority]”
You will need to reboot the container for the changes to take effect.
OpenSearchServer is an open source website crawler and query engine to provide advanced search capabilities to your website.
Onced you have installed OpenSearchServer you simply add an index, specify a URL to begin crawling and you website will be indexed and available to search.
WordPress has a pluginwhich integrates OpenSearchServer and replaces the existing search box to serve search queries directly to your OpenSearchServer instance. The pluginsite is available here.
Configure OpenSearchServer Search plugin
Login to your WordPress admin site and click Add New under Plugins. Search for opensearchserver and click Install Now.
Once you have the plugin installed, click Activate to enable the plugin.
You will then need to configure the OpenSearchServer plugin. The configuration page is under Plugins, then OpenSearchServer. Under Instance settings fill in your OpenSearchServer details.
: is the URL which points to your OpenSearchServer installation. Example: http://search.jamescoyle.net:8080/
: The index name you created on your OpenSearchServer to hold the search database for your WordPress site.
: Authentication username for your OpenSearchServer.
: Authentication API key for your OpenSearchServer.
Click Update Settings once you have entered the details.
For better search results, I would recommend using the following code under :
title:($$)^10 OR title:("$$")^10 OR
titleExact:($$)^10 OR titleExact:("$$")^10 OR
titlePhonetic:($$)^10 OR titlePhonetic:("$$")^10 OR
url:($$)^5 OR url:("$$")^5 OR
urlSplit:($$)^5 OR urlSplit:("$$")^5 OR
urlExact:($$)^5 OR urlExact:("$$")^5 OR
urlPhonetic:($$)^5 OR urlPhonetic:("$$")^5 OR
content:($$) OR content:("$$") OR
contentExact:($$) OR contentExact:("$$") OR
contentPhonetic:($$) OR contentPhonetic:("$$")
Click Update Options once you have finished.
Your Search box is replaced as soon as you activate the OpenSearchServer plugin. You will need to make sure your Search box is available on your site.
Your search queries will now be served from your local search server!
Proxmox can be installed on very little disk space. I tested Proxmox version 2.2 and installed it on a 10GB hard disk and Proxmox installed without an issue. On an earlier test, a 2GB hard disk was not sufficient and the installer showed an error.
The official webpage for Proxmox hardware requirements does not state a required or recommended size. I would suggest that more is better because each VM or OpenVZ container will be stored on your hard disk. If you have multiple hard disks, you should always put your OpenVZ containers and virtual disks on the fastest one. A common setup with just two disks is detailed below.
Disk A
Proxmox install
ISO images
OpenVZ templates
Backups
Disk B
OpenVZ containers
Virtual disks
This setup should reduce the time it takes to backup and create your OpenVZ containers and virtual machines as the reads and writes are on different disks. In addition it keeps your backups on a separate disk to the OpenVZ containers and virtual disks so if one disk fails, you will still have a copy.
For a test setup, two 250GB disks would be ample and enable you to try Proxmox and create multiple guests. For a production setup, the size of the disks would depend on the work load and volume of guests required. One thing is for sure though, faster is better. With SSD disks you will get the best performance with near zero seek time however they cost the most per gigabyte. For mechanical drives, use 15k rpm disks in a raid 0, or raid 10 for best speed and redundancy.
A new release of OpenSearchServer is available for download.
OpenSearchServer is a Java open source search engine and crawler based on Lucene and Tomcat. The crawler can index database tables, filesystems or crawl webpages from the internet or local network.
Proxmox 2.2 has some updates which have been pushed to the stable repository. There is no new functionality added with these updates, they are just bug fixes.
Since the 2.6.18-028stable021 kernel, it has been possible to set the I/O priority of an OpenVZ container. It is not currently possible to set any I/O limits for containers, only the priority. If you require I/O limits you should use KVM.
