re: [vserver] vserver update script

About this list Date view Thread view Subject view Author view Attachment view

From: Jacques Gelinas (jack_at_solucorp.qc.ca)
Date: Fri Jun 28 2002 - 07:58:19 EDT


On Thu, 27 Jun 2002 11:13:20 -0500, Vlad wrote
>
> I recall someone saying something about vserver (redhat) update scripts
> that would update all the files on the vserver (or create a vserver)
> directly from redhat cd's. Does anybody still maintain this and
> furthermore, has anybody used it at all to make upgrades to their systems?
> I have both types of vservers (with links to the root server and separate
> fs copies) so I am wondering if anybody has encountered any problems
> before I go ahead and start destroying stuff.

The script to install directly from a CD is in /usr/lib/vserver. Currently
there is one to install from a rh7.2 CD.

I will release a new version with support for 7.3. Further, the newvserver
utility will offer the ability to install from a CD directly in the menu and
will use these script directly (note this stuff is already done, just not released
yet).

For the upgrade part, no script are available yet. Performing the upgrade generally
involve the following steps

-Doing rework in distribution dependant configuration file, as needed. In
 general, this does not affect a vserver since this stuff applies to
 low level configuration.

-Handling deprecated packages. For example, a package foo may evolve in
 two packages: foo-client and foo-server. RPM can't handle this kind of relation
 (the package has a new name). So in that case, the offending package must
 be removed and then the upgrade performed.

-Computing the new dependencies and potentially adding new packages
 to solve it.

I have written a module to handle that and I am testing it here. The cool thing
about vservers is that you can test your upgrade over and over without rebooting
or loosing anything. You simply do

-create a new test vserver out of a production one: 1 minute
-assign a new IP to it
-perform the upgrade
-test it
-erase it and try again.

In general, the original production vserver should just stay there in case the upgrade
has some hidden side effect. You archive it and delete it few week later.

---------------------------------------------------------
Jacques Gelinas <jack_at_solucorp.qc.ca>
vserver: run general purpose virtual servers on one box, full speed!
http://www.solucorp.qc.ca/miscprj/s_context.hc


About this list Date view Thread view Subject view Author view Attachment view

This archive was generated by hypermail 2.1.4 : Mon Aug 19 2002 - 12:01:01 EDT