On Thu, Feb 22, 2007 at 11:29:13PM +0800, Tim Post wrote:
> On Thu, 2007-02-22 at 20:30 +0530, Ligesh wrote:
> > On Thu, Feb 22, 2007 at 02:54:46PM +0100, Henning Sprang wrote:
> > > Not enough doc reading about Xen and it's architecture, and the config
> > > parameters :)
> > >
> Xen (open source) is a set of very powerful tools that need somewhat
> skilled hands to use them. I think if the project shifted focus such as
> you suggest, it would lose some of its support and community.
Hey, I had said: "It is not part of xen the hypervisor, but xen as a platform".
For instance, xenEnterprise. Or any good management tool built on Xen should
provide the means to do a little more than mere create/delete. Your solution is
actually nice. The problem with your templated osimages is that the scripts
can be run only once. ONce you have setup the domU, then the placeholder
variables all disappear and then a _reconfiguration_ is not possible. Other
than that, the idea is quite innovative.
A better idea would be create template files separately:
So a generic script can scan '/etc' for all files ending with xentemplate then
configure the values and save them without the suffix.
for i in `find -name '*.xentemplate' /mount/domU/etc/` ; do
sed 's/$IPADDRESS/184.108.40.206/g' < $i > `basename $i .xentempate`
sed 's/$HOSTNAME/host.domain.com/g' < $i > `basename $i .xentempate`
This is actually a wonderful idea. That way, the script remains generic, and
each distro can prepare itself Xen with the proper template files.
Xen-users mailing list