>> >> - Stateless booting wreaks havoc with Satellite registration. > > Ouch. Did you try doing it in an xCAT postscript (I did not address the stateless registration case yet but I would start here) ?
The problem really is more Satellite-side. Every time you reboot a stateless system, Satellite sees it as a brand-new system, and, depending on your Satellite configuration, either creates a duplicate, errors out, or simply overwrites the same registration (in the last case, you of course wouldn't notice). The issue was particularly noticeable in RedHat Insights, where I ended up with dozens of copies for the same actual node. _______________________________________________________________________ Kevin Keane | Systems Architect | University of San Diego ITS | kke...@sandiego.edu *Pronouns: he/him/his*Maher Hall, 162 |5998 Alcalá Park | San Diego, CA 92110-2492 | 619.260.6859 | Text: 760-721-8339 *REMEMBER! **No one from IT at USD will ever ask to confirm or supply your password*. These messages are an attempt to steal your username and password. Please do not reply to, click the links within, or open the attachments of these messages. Delete them! On Mon, Nov 8, 2021 at 8:38 AM THomas HUMMEL <thomas.hum...@pasteur.fr> wrote: > On 11/8/21 17:06, Kevin Keane wrote: > > Seems like your use case is very similar to ours - we also have an HPC. > > But I abandoned stateless compute nodes, and we don't need discovery. > > Several reasons: > > > > - Stateless booting wreaks havoc with Satellite registration. > > Ouch. Did you try doing it in an xCAT postscript (I did not address the > stateless registration case yet but I would start here) ? > > > - Applying updates to stateless images is difficult, while it's trivial > > using Satellite. Of course, YMMV on this. > > - Stateful installation makes (slightly) more memory available on the > > compute nodes. > > - We rarely add nodes, so discovery isn't important. We simply use an > > Ansible list with MAC address, IP address and name. We maintain it > > manually, but it could also be scripted from DHCP logs or the like. > > I see. > > > My process takes longer than yours, because it involves an Ansible run. > > I also must run a playbook on the image before packing it or after the > xCAT stateful install. > > In any case I always have the simple option of installing against the > DVD.ISO via xCAT as I did with CentOS and register later (which is > indeed kind of a waste when all the needed repos are in Satellite). > > Thanks for your help. > > -- > Thomas HUMMEL > > > _______________________________________________ > xCAT-user mailing list > xCAT-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xcat-user >
_______________________________________________ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user
