Editing
Getting high with lenny
(section)
From Linix VServer
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== Getting High with Lenny == The aim here is to set up some high available services on Debian Lenny (at this moment October 1st still due to be released) There is a lot of buzz going on for a while now about virtualisation and High Availability and while Vserver is very well capable for this job the number of documented examples compared to some other virtualisation techniques are a little lacking so i thought i'd do my share. I prefer to use Vserver for the "virtualisation" because of its configurability, shared memory and cpu resources and basically the raw speed. DRBD8 and Heartbeat should take care of the availability magic in case a machine shuts down unexpectedly. In my experience it takes a few seconds to have several Vservers fail over to another machine with this setup. The main attempt here is to give a single working example without going to much in to the details of every option, the scenario is relatively simple but different variations can be made. For this set up we will have <blockquote> *2 machines <br> *both machines have 1 single large DRBD partition <br> *primary/seconday there is always 1 machine active and 1 on standby <br> *1 LVM partition per Vserver on top of the DRBD partition, for quota support from within the guest and LVM snapshots *the Vservers /etc/vserver and /var/lib/vservers directories will be placed on the DRBD partition. <br> </blockquote> In case the main machine that runs the Vservers goes down, the synchronized second machine should take over and automatically start the Vservers. Basically this is an on-line RAID solution that can keep your services running in case of hardware failure, it is NOT a back-up replacement. The cost for this setup is that you always have 1 idle machine standby, this cost can be justified by the fact that Linux-Vserver enables you to make full use of the 1 machine that is running, you also could consider to run this on a little less expensive (reliable) hardware. Also note that i will be using R1 style configuration for heartbeat, R1 style can be considered to be depreciated when using Heartbeat2 but i could not get my head around the R2 xml configuration, so if you want R2 you might want to have a look here. [[Fail-over]]) The partitioning looks as follows <code> c0d0p1 Boot Primary Linux ext3 10001.95 c0d0p5 Logical Linux swap / Solaris 1003.49 c0d0p6 Logical Linux 280325.77 </code> <blockquote> '''machine1''' will use the following names. <br> *hostname = node1 <br> *IP number = 192.168.1.100<br> *is primary for r0 on disk c0d0p6 <br> *physical volume on r0 is /dev/drbd0 <br> *volume group on /dev/drbd0 is called drbdvg0 <br> </blockquote> <blockquote> '''machine2''' will use the following names. <br> *hostname = node2 <br> *IP number = 192.168.1.200 <br> *is secondary for r0 on disk c0d0p6 <br> The Volume Group and the Physical Volume will be identical on node2 if this one becomes the primary for r0. </blockquote>
Summary:
Please note that all contributions to Linix VServer may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Linix VServer:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Navigation menu
Page actions
Page
Discussion
Read
Edit
History
Page actions
Page
Discussion
More
Tools
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
About
Overview
Paper
News
Developers
Donations
Search
Getting Started
Downloads
FAQs
Documentation
Support
Participate
How to participate
Report a Bug
Communicate
Teams/Projects
Hall of Fame
Resources
Archives
Recent Wiki Changes
Pastebin
Related Projects
VServer Hosting
Happy VServer Users
Tools
What links here
Related changes
Special pages
Page information