Live Linux Training

Live OpenVZ Administration
Purchase Now for $495.95
Why Choose OpenVZ? (taken from the OpenVZ.com website)
20 % of each Class Sold will go back to support the OpenVZ project. 1. OS Virtualization
From the point of view of applications and Virtual Environment users, each VE is an independent system. This independency is provided by a virtualization layer in the kernel of the host OS. Note that only a negligible part of the CPU resources is spent on virtualization (around 1-2%).
2. Network virtualization
The OpenVZ network virtualization layer is designed to isolate VEs from each other and from the physical network
3. Resource Management
OpenVZ resource management controls the amount of resources available for Virtual Environments. The controlled resources include such parameters as CPU power, disk space, a set of memory-related parameters, etc.
4. Two-Level Disk Quota
Host system (OpenVZ) owner (root) can set up a per-VE disk quotas, in terms of disk blocks and i-nodes (roughly number of files). This is the first level of disk quota. In addition to that, a VE owner (root) can use usual quota tools inside own VE to set standard UNIX per-user and per-group disk quotas. 5. Fair CPU scheduler
CPU scheduler in OpenVZ is a two-level implementation of fair-share scheduling strategy.
6. User Beancounters
User beancounters is a set of per-VE counters, limits, and guarantees. There is a set of about 20 parameters which are carefully chosen to cover all the aspects of VE operation, so no single VE can abuse any resource which is limited for the whole node and thus do harm to another VEs.
How the Course is Run
1. Self-Paced Individual Training
The self-paced style allows you to work on your own schedule and set up instructor training when it works for you. The student studies the material and then view the live examples from the instructor. Students will be provided a 200 page manual for the class. This manual provides theory as well as practical step by step application.
2. Instructor Led Live Class
The student will have 4 live sessions with the instructor in the two week period. The instructor will demonstrate the projects and solutions for troubleshooting so the student has the opportunity to view the process as well as read about the process before they perform the projects. During this time will have 24/7 contact with the instructor via email and will be able to setup a telephone conference any time they need help.
3. Instructor Monitored Project Completion
The course requires the student to complete a number of projects on a live server to gain experience working with virtual servers. These projects are done under the instructors supervision.
Projects
Each project is designed to develop skills in managing a server with many virtual servers.
Project# 1: Installation
Installation of the necessary programs will be covered and tips on configuration settings.
Project #2: Manage the Node Firewall
The hardware node is the server that hosts the virtual servers. It is critical that the firewall be set up correctly to prevent any intrusion attempts as the hardware node controls all of the virtual servers. This project will go into detail on how to set the firewall up so that it will not only protect the hardware node but the virtual servers as well.
Project #3: Manage the Node Security
Managing services, tcp_wrappers, user accounts, locking down the server so that it is as secure as possible is covered in this project.
Project #4: Create a Virtual Server
Step by step students are taken through the process of building virtual servers. This process includes selecting a template and using that template to build a working server in less than 5 minutes!
Project #5: Install Programs on the VPs
Once the server is created users will want to install server applications or services so the servers are useful for the organization.
Project #7: Manage the Resources on the VPs
Each virtual serve can be managed individually, so that the total hardware node resources may be divided any way that you want to configure it. This project will help the student manage those resources.
Project #8: Clone the VPs
Students will learn how to clone a virtual server as a backup or to create a new virtual server.
Project #9: Troubleshooting Resources on the VPs
Troubleshooting usually involves readjusting the resources for a virtual server. This project will help students recognize problems and then solve the resource issues.
Project #10: Managing Templates
Determining which templates to use and how to set templates up will be the subject of this project.
Project #11: Connecting to a Serial Interface
Virtual servers can be set up to use serial devices for connecting to a router for example. This project will show students how to designate serial connections for the virtual server.
Project #12: Using Multiple Network Cards
Separate network cards may be used to connect to any number of networks from different virtual servers on the same hardware node. This project helps students set up those separate network connections.
The information below is taken from the OpenVZ.com website. It provides you with a basic understanding of some the powerful features of OpenVZ.
The architecture of OpenVZ VEs is different from the traditional virtual machines architecture because it always runs the same OS kernel as the host system (while still allowing multiple Linux distributions in individual VEs). This single-kernel implementation technology enables running Virtual Environments with a near-zero overhead. Thus, OpenVZ offer an order of magnitude higher efficiency and manageability than traditional virtualization technologies.
OS Virtualization
From the point of view of applications and Virtual Environment users, each VE is an independent system. This independency is provided by a virtualization layer in the kernel of the host OS. Note that only a negligible part of the CPU resources is spent on virtualization (around 1-2%). The main features of the virtualization layer implemented in OpenVZ are the following:
* A VE looks and behaves like a regular Linux system. It has standard startup scripts; software from vendors can run inside a VE without OpenVZ-specific modifications or adjustment; * A user can change any configuration file and install additional software; * Virtual Environments are completely isolated from each other (file system, processes, Inter Process Communication (IPC), sysctl variables); * Processes belonging to a VE are scheduled for execution on all available CPUs. Consequently, VEs are not bound to only one CPU and can use all available CPU power.
Network virtualization
The OpenVZ network virtualization layer is designed to isolate VEs from each other and from the physical network: * Each VE has its own IP address; multiple IP addresses per VE are allowed; * Network traffic of a VE is isolated from the other VEs. In other words, Virtual Environments are protected from each other in the way that makes traffic snooping impossible; * Firewalling may be used inside a VE (the user can create rules limiting access to some services using the canonical iptables tool inside the VE). In other words, it is possible to set up firewall rules from inside a VE; * Routing table manipulations and advanced routing features are supported for individual VEs. For example, setting different maximum transmission units (MTUs) for different destinations, specifying different source addresses for different destinations, and so on.
Resource Management
OpenVZ resource management controls the amount of resources available for Virtual Environments. The controlled resources include such parameters as CPU power, disk space, a set of memory-related parameters, etc. Resource management allows OpenVZ to: * Effectively share available Hardware Node resources among VEs * Guarantee Quality-of-Service (QoS) * Provide performance and resource isolation and protect from denial-of-service attacks * Collect usage information for system health monitoring Resource management is much more important for OpenVZ than for a standalone computer since computer resource utilization in a OpenVZ-based system is considerably higher than that in a typical system. As all the VEs are using the same kernel, resource management is of paramount importance. Really, each VE should stay within its boundaries and not affect other VEs in any way and this is what resource management does. OpenVZ resource management consists of three components: two-level disk quota, fair CPU scheduler, and user beancounters. Please note that all those resources can be changed during VE runtime, there is no need to reboot. Say, if you want to give your VE less memory, you just change the appropriate parameters on the fly. This is either very hard to do or not possible at all with other virtualization approaches such as VM or hypervisor.
Two-Level Disk Quota
Host system (OpenVZ) owner (root) can set up a per-VE disk quotas, in terms of disk blocks and i-nodes (roughly number of files). This is the first level of disk quota. In addition to that, a VE owner (root) can use usual quota tools inside own VE to set standard UNIX per-user and per-group disk quotas.

Live Virtual Ubuntu 9.04 Server Training Each student receives a 1100 pages of lay flat 8" x 11" manuals. Each course is 8 weeks long and during that time students will have a live server to work on. Students will have one-on-one classes with an instructor on a weekly basis to ask questions and see demonstrations. Each student also receives a CD with over 100 Flash movies.

Live Virtual CentOS 5.3 Server Training Each student receives a 1100 pages of lay flat 8" x 11" manuals. Each course is 8 weeks long and during that time students will have a live server to work on. Students will have one-on-one classes with an instructor on a weekly basis to ask questions and see demonstrations. Each student also receives a CD with over 65 Flash movies.

Live Virtual Postfix Mail Server Training The course is designed to provide the information needed to set up a Postfix Mail Server, labs that can be performed on a practice server, flash movies that demonstrate configuration of Postfix, live virtual classroom sessions with an instructor and each student is provided a practice server. The Postfix Mail Server course is 8 weeks long, performed one-on-one for each student so that it can be taken at any time.