6,535
edits
Changes
→Organization of This Guide: remove "Managing Templates"
<noinclude>{{UG/Header}}</noinclude>
== About This Guide ==
This guide is meant to provide comprehensive information on OpenVZ — high-end server virtualization software for Linux-based computers. The issues discussed in this guide cover the necessary theoretical conceptions as well as practical aspects of working with OpenVZ. The guide will familiarize you with the way to create and administer ''containers'' (sometimes also called ''Virtual Environments'', or ''VEs'') on OpenVZ-based Hardware Nodes and to employ the command line interface for performing various tasks.
== Who Should Read This Guide ==
Chapter 4, [[../Operations on Virtual Private Servers/]], covers those operations that you may perform on a container as on a single entity: creating and deleting Virtual Private Servers, starting and stopping them, etc.
Chapter 5, [[../Managing Templates/]], shows you the way to handle OpenVZ templates properly – create and install templates and template updates on the Hardware Node, add them to and remove from containers, etc. Chapter 6, [[../Managing Resources/]], zeroes in on configuring and monitoring the resource control parameters for different containers. These parameters comprise disk quotas, disk I/O, CPU and system resources. Common ways of optimizing your containers configurations are suggested at the end of the chapter.
Chapter 76, [[../Advanced Tasks/]], enumerates those tasks that are intended for advanced system administrators who would like to obtain deeper knowledge about OpenVZ capabilities.
Chapter 87, [[../Troubleshooting/]], suggests ways to resolve common inconveniences should they occur during your work with the OpenVZ software.
Chapter 98, [[../Reference/]], is a complete reference on all OpenVZ configuration files and Hardware Node command-line utilities. You should read this chapter if you do not understand a file format or looking for an explanation of a particular configuration option, if you need help for a particular command or looking for a command to perform a certain task.
== Documentation Conventions ==
!| Formatting convention || Type of information || Example
|-
| '''Bold'''| Items you must select, such as menu options, command buttons, or items in a list.| Go to the '''QoS''' tab.|-| ''Italics''
| Used to emphasize the importance of a point or to introduce a term.
| Such servers are called ''Hardware Nodes''.
|-
|
<code>Monospace</code>
| The names of commands, files, and directories.
| Use <code>vzctl start</code> to start a Container.
|-
|
Preformatted
| On-screen computer output in your command-line sessions.
|
Saved parameters for CT 101
|-
|
'''Preformatted bold'''
| What you type, as contrasted with on-screen computer output.
|
'''rpm -q quota'''
|}
The root path usually includes the /bin, /sbin, /usr/bin and /usr/sbin directories, so the steps in this book show the commands in these directories without absolute path names. Steps that use commands in other, less common, directories show the absolute paths in the examples.
== Getting Help ==
In addition to this guide, there are a number of other resources available for OpenVZ which can help you use it more effectively. These resources include:
* [[User beancounters]] manual provides in-depth knowledge of UBC functioning and configuration.
* OpenVZ Wiki (http://wiki.openvz.org/) serves as a primary place to collect and share OpenVZ information.
* OpenVZ users [[mailing list]] is where users exchange questions and ideas.
* http://forum.openvz.org/ is OpenVZ support and discussion forum.
== Feedback ==
Please submit a report by e-mail to userdocs@openvz.org.
<noinclude>{{UG/Footer}}</noinclude>
