I did a “service dhcpd stop” and a “service confluent restart”, and the SuperMicro did not receive any reply to the DHCP/PXE packets it was sending out. I then did a “service dhcpd start” and the “xcat/genesis” file was loaded.
The dhcpd.conf did have "gpxe.no-pxedhcp”, but removing it and restarting did not change any behaviour. I noticed that “http://IP:80/tftpboot/xcat/xnba/nets/172.17.8.0_21” is being referenced. Per “lsof -i udp”, the Confluent is listening on *:bootps, so I’m not sure why it is not answering. I had run a “nodedeploy MYHOST -n ubuntu-20.04.6-x86_64-default” earlier. $ nodeattrib MYHOST MYHOST: console.method: ipmi MYHOST: deployment.apiarmed: once MYHOST: deployment.pendingprofile: ubuntu-20.04.6-x86_64-default MYHOST: deployment.profile: MYHOST: deployment.stagedprofile: MYHOST: deployment.state: MYHOST: deployment.state_detail: MYHOST: groups: prox,ipmi,all,everything MYHOST: hardwaremanagement.manager: MYHOST-ipmi MYHOST: net.hwaddr: ac:1f:AA:BB:CC:DD MYHOST: net.ipv4_method: dhcp MYHOST: secret.hardwaremanagementpassword: ******** MYHOST: secret.hardwaremanagementuser: ******** > On Nov 7, 2023, at 13:40, Jarrod Johnson wrote: > > If dhcpd.conf is set to not send any 'filename', it's best. If you don't > need a dhcp server, then you can turn it off. There's also > > If you have a dhcp server with a dynamic range on it, then: > nodeattrib net.ipv4_method=firmwaredhcp > > If you have a dhcp server with static reservations, you could either have > dhcp continue, or disallow dhcp for the confluent node. > > If you have no dhcp server, then it should just do the right thing directly. > > If you want to use dhcp ongoing, then 'net.ipv4_method=dhcp', however you own > the IPAM sort of responsibility totally. > > If your dhcp has: > option gpxe.no-pxedhcp 1; > Please remove that to let confluent merge an offer with an uncoordinated dhcp > server. > > I need to do a deeper right up on the detail about dhcp interaction, how it > is now optional, and how it can coexist with an unmanaged dhcp server and > free the dhcp server from 'filename' > >> From: David Magda >> Sent: Tuesday, November 7, 2023 9:27 AM >> To: xCAT Users Mailing list >> Subject: Re: [xcat-user] [External] Re: xCAT-Confluent >> >> After running the first few commands, I have >> /tftpboot/confluent/x86_64/ipxe* and /var/lib/confluent/public/{os, >> distribution}/ubuntu* present, along with genesis-x86_64/. >> >> However the contents of the RHEL/CentOS /etc/dhcp/dhcpd.conf are such that >> “filename” is “xcat/xnba.*”, so that’s what gets loaded. >> >> Do I need to tweak the dhcpd.conf just for the test system I’m playing with, >> or should a completely new dhcpd.conf file be put in place for using >> Confluent? (Moving the current one out of the way, perhaps temporarily until >> I get an understanding of Confluent so I can revert to xCat if need-be.) >> >>> On Oct 26, 2023, at 11:33, Jarrod Johnson wrote: >>> >>> I will say that EL7 hasn't been tested and thus we haven't pushed updates >>> since 3.8.0, but 3.8.0 should be plenty. >>> >>> The confluent you have going is already enough to start examining OS >>> deployment profiles. If you would like to, you can use commands like >>> osdeploy initialize and osdeploy import and even imgutil build, and it >>> won't mess with xCAT. >>> >>> When you get to nodedeploy, that is the time when you have to start >>> planning around potential disruption as xCAT and confluent might fight over >>> who gets to deploy a system, and that can be confusing. We should document >>> formally how to mask a node from xCAT ('!*NOIP*' in mac table) to let one >>> kick the tires with a node... >>> >>> I can help look at a few people kicking tires, certainly seems worthy of >>> documentation or video example... >>>> From: David Magda >>>> Sent: Thursday, October 26, 2023 11:22 AM >>>> To: xCAT Users Mailing list >>>> Subject: [External] Re: [xcat-user] xCAT-Confluent >>>> >>>> Yes, there was perhaps auto-completion with regards Confluent/Confluence. >>>> I currently have a (legacy?) ‘joint’ xCAT-Confluent (3.6) installation on >>>> RHEL 7 that I inherited; if one wants to fully move from xCAT to >>>> Confluent, is there document on how to ‘extract’ oneself from xCAT? I >>>> don’t see anything that jumps out at: >>>> https://hpc.lenovo.com/users/ >>>> https://hpc.lenovo.com/users/documentation/ >>>> Should I simply abandon the previous installation and do a fresh install? >>>> While there is some documentation, the system leans towards being heavily >>>> vendor-used so people completely new to it have a steep learning curve >>>> (xCAT is/was also challenging to get into since it was fairly >>>> vendor-focused). >> […] >> _______________________________________________ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user
