Upgrade67 Landing Page

Wireframe

Landing Page - Preliminary Checks

High Definition Mockup

Annotations

#	Component	Description
1	Preliminary Check Section	Contains information, a status list of the preliminary checks, and a "Check" button. This section should "float left".
1.1	Preliminary Check Item	Name of the Preliminary Check and it status.
1.2	Check Button	Enabled by default, on mouseOver show the hover state and once the user clicks this button, it will be disabled and a spinner will be displayed if the action takes more than 2 seconds. This button will be re-enabled if any preliminary check failed.
2	Upgrade Mode Section	Contains generic information, and, once all checks have passed upgrade mode specific information. In case of normal mode, the "proceed in normal mode" button is shown and enabled once the checks have passed. In case of non-disruptive mode only information is shown. This section should "float left".
2.1	Proceed in Normal Mode Button	This button is just for confirmation. Once clicked the "Begin Upgrade" button will be enabled.
3	Begin Upgrade Section	Contains information the "Begin Upgrade" button as well as information about it. This section should "float left".
3.1	Begin Upgrade Button	This button will be enabled when the preliminary checks all return success, and in case of normal mode, the "proceed in normal mode" button has been clicked. On mouseOver show the hover state. When clicked, the Backup Administration Server page will be displayed.

Business Rules

1. Upgrade process flow can only be accessed by the Crowbar Administrator.
2. Crowbar Administrator must successfully run preliminary checks.
3. Preliminary checks for the Upgrade flow consist of:
4. All maintenance updates available have been successfully installed.
5. Crowbar sanity network checks (6 different network checks)
6. If High Availability module is available, its health check pass
7. There is a free node as large as the largest running node
8. "Check" button is enabled by default.
9. "Check" button is enabled but set to a secondary button when all preliminary checks are successful and the Upgrade Mode section is enabled.
10. Depending upon the determined upgrade mode the one of two things happens
11. Normal Mode: information about normal mode and a "proceed with in normal mode" button is displayed when all checks succeed
12. Non-Disruptive Mode: information about non-disruptive mode is shown and "Begin Upgrade" section and button is enabled when all checks succeed.
13. "Begin Upgrade" button changes the status of the nodes to "upgrade".
14. When clicked, "Begin Upgrade" button redirects the user to Backup the Administration Server page.
15. In case of preliminary checks failure, the Crowbar Administrator is notified.
16. In case of preliminary checks failure, the Crowbar Administrator is able to trigger a new check.
17. In case of failure when setting the upgrade node-state button:
18. The upgrade nodes-state is reverted.
19. The user is notified.
20. The Crowbar Administrator remains on the current Landing page.
21. The current repository information will be retrieved and stored in case of cancelling upgrade.

Test Cases

TC.UPGRADE.LANDING.01

1. Given I am Crowbar Administrator
2. And I have a SUSE OpenStack Cloud 6
3. And I have all maintenance updates installed
4. And I have a healthy High Availability module
5. And I have a healthy network on Crowbar
6. And I have a free node as large as the largest running node
7. And I navigate to the Upgrade Flow
8. And I see Begin Upgrade button disabled
9. When I click on Run Checks button
10. Then I will not see error messages
11. And I will see Begin Upgrade button enabled

TC.UPGRADE.LANDING.02

TC.UPGRADE.LANDING.03

User Stories

• (A list of Trello cards to track the implementation of this page)