Rubygem-Staypuft: need a better summary screen either on the dashboard or as a separate page - that shows in one page what the user has entered in the wizard.
Steps to reproduce:
1. install rhel-osp-installer.
2. Configure start any deployment.
3. Try to access the detail of that deployment while it's running.
No way to access the details of deployment while it's running/paused.
The details of the deployment or a summary should be available even when the deployment is running/paused. This will allow (in some cases) to resume the deployment after fixing some values.
I'd prefer a "quick summary" view as proposed here (either on dashboard or via link there) to opening up the wizard, since we're quite deliberately disabling the wizard when deploy starts.
Also, we don't want to see the full clickable wizard -- just a summary of relevant settings.
Related to this, the wizard itself is *not* disabled when a deployment is started -- only the *link* to the wizard -- so you can still get there via URL surgery -- but that's a separate bug and we shouldn't fix it until after the information is available via other means here.
Anything more that we need beyond what is currently in the wizard?
Jarda, in one of our previous builds we had a deployment summery page which I think would fit.
Arthur can you be a bit more specific which summary page you talk about here?
My question is - Do we want to allow user to pause deployment, change some parameters and resume the deployment again? What will be the expected behavior of back-end then?
Just my 2 cents:
While it's not required to change the parameters of the running deployment, there should be the option to see the type of the deployment and it's params (Tenant network type, Backend driver, selected interfaces, etc) without stopping the deployment.
If a customer has started the deployment and it got paused with errors. In order for him to include all the details for the deployment in a report (without writing down everything in advance) would be to stop the deployment and to revisit it. Perhaps there's an easy fix that would allow him to complete the deployment - so why stopping it.
(In reply to Jaromir Coufal from comment #6)
> Arthur can you be a bit more specific which summary page you talk about here?
> My question is - Do we want to allow user to pause deployment, change some
> parameters and resume the deployment again? What will be the expected
> behavior of back-end then?
As Sasha described on Comment#7, we need a static, read only summery of all the selected parameters, and all values the user selected throughout the wizard.
Closing list of bugs for RHEL OSP Installer since its support cycle has already ended . If there is some bug closed by mistake, feel free to re-open.
For new deployments, please, use RHOSP director (starting with version 7).
-- Jaromir Coufal
-- Sr. Product Manager
-- Red Hat OpenStack Platform