Description of problem: After deploying hosted engine via cli (hosted-engine --deploy) having the web address of your appliance printed on the screen would add to the UX. How reproducible: Steps to Reproduce: 1. run a successful deployment by hosted-engine --deploy Actual results: No IP/FQDN printed on screen. Expected results: Web address printed on screen after successful deployment. Additional info: N/A
Which UX? You've deployed via CLI?
(In reply to Yaniv Kaul from comment #1) > Which UX? You've deployed via CLI? Maybe I have my acronym wrong. but I was going on the impression that UX = user experience. If that is not the case then I can change it to whatever is a better fit. This RFE would be just to print the IP/FQDN of the appliance in a summary like printout when the user successfully deploys hosted engine.
FQDN of the hosted engine VM is one of the required inputs. What's the gain in printing an information which should be known prior to Hosted Engine deployment?
Yes it is but I believe that it would help the user experience to have the it printed. I know it sounds like a redundancy over a convenience but it would make the next step of going to the FQDN/IP seamless. Something along the lines of "Deployment Successful. You can now continue to [FQDN/IP] to finish setting up your environment." Instead of having to go to wherever you wrote down your FQDN/IP it's simply right there for you. It gives the whole process a little more polish.
Beside what Sandro pointed out on comment 3, at the CLI deployment there is a summary with all the configuration details (for the user to confirm), including the engine FQDN. In addition, this information can be found on the answerfile, which it's path printed out at the end of the deployment. So if the user has forgot the engine FQDN he has many places to find it pretty easily.