Xen-tools and FAI softupdates: Difference between revisions
(first version) |
m (+ category) |
||
(2 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
== FAI dirinstall with xen-tools == | |||
from xen-tools, you can start fai dirinstall as a role script. | |||
Therefore, the debootstrap has to be disabled with the install=0 option of xen-tools, and the machine needs to use the role "fai-install". The role script looks like this: | |||
<pre> | |||
#!/bin/sh | |||
TARGET=$1 | |||
CMD="fai -N -v -u ${hostname} dirinstall $TARGET" | |||
echo running $CMD | |||
$CMD | |||
</pre> | |||
== FAI softupdates after xen-tools installation == | |||
For now, only my xen-tools config, [[Image:Etc xen-tools.tar.gz|here]] | |||
Basically, I run fai softupdates in the chroot, after xen-tools has created the basic system. That way I can use the FAI class system to get more sophisticated possibilities of sharing configuration for multiple different systems, which are party similar and partly quite different. | |||
I run xen-tools with the command | I run xen-tools with the command | ||
Line 9: | Line 25: | ||
to get a FAI Server installed, the FAI configspace is located in the xen-tools skel directory. | to get a FAI Server installed, the FAI configspace is located in the xen-tools skel directory. | ||
Sure, some further knowledge of FAI is necessary to understand all that... | Sure, some further knowledge of FAI is necessary to understand all that... | ||
[[Category:Howto]] |
Latest revision as of 07:54, 4 October 2010
FAI dirinstall with xen-tools
from xen-tools, you can start fai dirinstall as a role script. Therefore, the debootstrap has to be disabled with the install=0 option of xen-tools, and the machine needs to use the role "fai-install". The role script looks like this:
#!/bin/sh TARGET=$1 CMD="fai -N -v -u ${hostname} dirinstall $TARGET" echo running $CMD $CMD
FAI softupdates after xen-tools installation
For now, only my xen-tools config, File:Etc xen-tools.tar.gz
Basically, I run fai softupdates in the chroot, after xen-tools has created the basic system. That way I can use the FAI class system to get more sophisticated possibilities of sharing configuration for multiple different systems, which are party similar and partly quite different.
I run xen-tools with the command
mac=00:16:3E:3C:02:40 xen-create-image --ide --size=2Gb --copy=/dev/null --hostname faiserver --template=/etc/xen-tools/paravirtual.tmpl
to get a FAI Server installed, the FAI configspace is located in the xen-tools skel directory. Sure, some further knowledge of FAI is necessary to understand all that...