Hello, thanks for your answer. On 10/22/24 4:18 PM, Jarrod Johnson via xCAT-user wrote:
But for non-Lenovo, you would do it roughly xCAT style, with 'pxe-client' and maybe a genesis image using configbmc (or another profile). One difference is you don't need a dynamic range in Confluent, as it does discovery against the DHCPDISCOVER packet rather than needing linux first.
The BMC discovery mechanism seems cool but I don't think I really understand how it works :
a) So the BMC config is made out of band ? This would imply 2 DHCP servers if 1 vlan for data and 1 for BMC ?
b) how can no dynamic range work without ending up either BMC ip address being "random" (i.e 2 discover would not necessary end up the same BMC having the same ip address) or exposing to ip address conflict risk (one BMC get set up its final ip address while it is used by another one still being discovered) ?
[root@r3u20 ~]# nodediscover list -t pxe-client -f node,uuid,type,switch,port -o node Node| UUID| Type| Switch| Port ------|-------------------------------------|-----------|-------|------ r3u21| 11137727-3f6e-11ed-9dcc-92feca966289| pxe-client| r3c1| swp34 r3u22| cfeaac8f-341f-11ed-a12e-ca86724e9d51| pxe-client| r3c1| swp2 r3u23| 57ab573c-327b-11ed-92ce-bf13e73b0f63| pxe-client| r3c1| swp3 r3u24| 40146251-4bb5-11ed-95a4-adc935918367| pxe-client| r3c1| swp5
The above command implies BMC is already configured (in order to pxe boot the node), correct ?
So image based (genesis like) discovery is ready to be used or do we have to self generate our own genesis-like image ?
Like most stop at 'power on/off, *maybe* setboot, but nodeconsole, nodeconfig, nodeinventory, etc are frequently out of scope for non-xCAT, non-confluent OS deployment tools.
Well minimal config has to be supported just in order to customize the image to the particular node (like "statifying" network setting and hostname at the very minimal)
Note also that confluent profiles have 'ansible/post.d' as well as 'scripts/post.d', opening up the possibility of triggering ansible plays on the deployer rather than scripts on the node if desired.
You mean running ansible from the inside at boot or from the management node ? In a pull mode ?
In short, if you ignore the new BMC-driven discovery you end up with xCAT as mostly a subset of confluent functions (excepting non-deployment DHCP configuration, and ISC DNS, though that could be addressed if desired, and perhaps extended to more use cases). So we have BMC-driven, PXE-driven, and manual operation all as options, just have to be very careful and clear which one matches the right audience.
Do image use initialramfs (if yes, dracut type ?) ? I have to actually play with confluent to go further in my questions. Thanks for your help -- Thomas HUMMEL HPC Group Institut PASTEUR Paris, FRANCE _______________________________________________ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user
