On 03/11/2020 03:09, Casandra H Qiu wrote:
Have you check this link:
Hello, thanks for your answer. Yes I did read it.
after "rinstall" command , you can run command "xcatprobe osdeploy -n
<nodename>" to probe operating system provision process.
The output will show from begin of provision process until end of node
installation completion. set attribute "xcatdebugmode=1" on the site
table will show more of debug information.
I'll try this
when you deploy the VM template, How did u change the network setting?
The template has an NetworkManager auto (dhcp) profile but the node xCAT
object has been created beforehand with the correct MAC address (of the
VM instanciated from the template). Then a role in the ansible playbook
which is run to further configure the VM runs updatenode -P <node>
"confignetwork -s" to "statify" the (already correct) ip address.
I
think /opt/xcat/xcatinfo just capture some information for the CN. Don't
think will use them during the provision.
I'll check all of this. Can you tell me what /xcatpost/mypostscript.post
is ? Is just for the REBOOT/postbootscripts case ?
Basically, what I want to know is this :
all those generated or patched scripts on the CN hold some node's info
(node's name, ...) : what is the source of this info (local or from the
node object definition on the MN ?) and in what file can it be safely
removed (in order not to have the template info which will be incorrect
on the VM) ?
Thanks for your help
--
Thomas HUMMEL
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
