Description of problem: We need to specify a portion for PXE_SSH in overcloud integration via command line Version-Release number of selected component (if applicable):RHOS 10 Actual results: Not available in Page 5, portion 5.1 Expected results: Note The UI also allows for registration of nodes from a KVM host using the pxe_ssh driver. Note that this option is available for testing and evaluation purposes only. It is not recommended for Red Hat OpenStack Platform enterprise environments. For more information, see Section B.6, “SSH and Virsh”.
Closing this BZ as the pxe_ssh driver is only for evaluation purposes as per the note. Customers should not be using pxe_ssh in enterprise setups.
Of course we should not use pxe_ssh driver for enterprise setups, but for evaluation & testing purpose we need the pxe_ssh driver to be present. Please, do accept this and add it as comment for the CLI portion. Note: It is already part of the Web UI portion, so it is also required to be part of CLI portion.
Hi Nikhil, As mentioned in the text, the Appendix in the doc covers the parameters for pxe_ssh: https://access.redhat.com/documentation/en/red-hat-openstack-platform/10/single/director-installation-and-usage/#sect-SSH_and_Virsh This should be sufficient for the CLI documentation. I'm not sure what you are expecting beyond this. Can you please clarify?
Hi Dan, If you go via the official Documentation we donot have any such Details present in CLI Section, but if you look specifically in point 6.4 in Director Installation via WEB UI we do have a NOTE specifying the Same. Why cant we have a similar NOTE in CLI As well, It would make CLI Procedure quite more Simpler.
Hi Nikhil, There's similar a note that is a little more general in the CLI section that says the following: = NOTE = For more supported power management types and their options, see Appendix B, Power Management Drivers. https://access.redhat.com/documentation/en/red-hat-openstack-platform/10/single/director-installation-and-usage/#sect-Registering_Nodes_for_the_Overcloud This reason this note is more general is because the CLI supports other drivers beyond IPMI and libvirt+SSH.
Closing due to non-response to Dan's query (1year +).