Confluent information can be found at hpc.lenovo.com. As for integrating w/ xCAT. At a minimum, Confluent can replace the console server. Info on doing that is here:
https://hpc.lenovo.com/users/documentation/configconfluent_xcat.html Once makeconfluentcfg is run, you can use confluent to replace most all xCAT management tools (“r” commands) that don’t involve node provisioning. Beyond node management, Confluent can discover and configure BMCs w/o power-up. In order for this to work, you would define the BMC switchport info rather than the node boot interface info. Finally, Confluent adds a web interface. Info on that can be found here under “Enabling the Web UI”: https://hpc.lenovo.com/users/documentation/installconfluent_rhel.html Regards, Christian Caruthers Lenovo Professional Services Mobile: 757-289-9872 From: Imam Toufique <techie...@gmail.com> Sent: Saturday, May 15, 2021 00:25 To: xCAT Users Mailing list <xcat-user@lists.sourceforge.net> Subject: Re: [xcat-user] [External] ability to integrate with Ansible (Coming soon) Where do I find documentation on confluent and how does it integrate with xcat ? thanks On Fri, May 14, 2021 at 10:36 AM Jarrod Johnson <jjohns...@lenovo.com<mailto:jjohns...@lenovo.com>> wrote: Note I can't speak to xcat-invenntory, but the upcoming confluent release has some definition of ansible integration. In confluent 3.2, a deployment profile can have scripts executed directly on nodes (basically the same as postscripts): /var/lib/confluent/public/os/<profilename>/scripts/firstboot.d /var/lib/confluent/public/os/<profilename>/scripts/post.d Additionally, playbooks may be remotely triggered at points of the deployment: /var/lib/confluent/public/os/<profilename>/ansible/firstboot.d /var/lib/confluent/public/os/<profilename>/ansible/post.d The 'hosts' field will be specifically whatever node that enters that phase. The play will be executed as the confluent user on the deployment server, targeting the deploying server (with a separate automation user key that you must opt into, since confluent isn't allowed to read user's private keys). Also, if pertinent, the corresponding release of confluent genesis has enough python to be targeted by ansible plays. It has 'onboot' scripts and ansible plays supported. However, it's far more optional in confluent (emphasis on standby power discovery, PXE discovery if needed can be done during the PXE attempt, and the 'configbmc' script if needed should also work as 'pre.d' script for an installing system, to roll most genesis actions into the OS installers instead of requiring genesis to boot first. That is a specific interpretation of 'ansible support' and I welcome more requests (e.g. for confluent to provide facts and/or a module to use something in lieu of cmdline. ________________________________ From: James Goebel <jkgoe...@bu.edu<mailto:jkgoe...@bu.edu>> Sent: Friday, May 14, 2021 11:58 AM To: xcat-user@lists.sourceforge.net<mailto:xcat-user@lists.sourceforge.net> <xcat-user@lists.sourceforge.net<mailto:xcat-user@lists.sourceforge.net>> Subject: [External] [xcat-user] ability to integrate with Ansible (Coming soon) On the xcat-inventory github page there is the suggestion that Ansible integration is planned. Has there been any progress on this? https://github.com/xcat2/xcat-inventory _______________________________________________ xCAT-user mailing list xCAT-user@lists.sourceforge.net<mailto:xCAT-user@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/xcat-user -- Regards, Imam Toufique 213-700-5485
_______________________________________________ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user
