6.8. Monitoring Progress of the Deployment

There are several methods to monitor the progress of your deployment. This section gives a high level overview of each of these methods.

Progress Bar

The Progress Bar on the deployment screen provides an overall indicator of the deployment progress, including the percentage of completion for the different node types deployed.

Tasks

The Tasks page displays a list of details about current tasks being run by the installer. You can access the Tasks page at any time from anywhere in the user interface by clicking MonitorTasks. You can also access the task for your deployment by clicking Show more details under the progress bar.
The Tasks page is useful for indentifying specific progress on your deployment including any errors that have stopped your deployment.

Dynflow Console

The Dynflow Console shows the subtasks for a particular task and the progress on each. This can include subtasks such as building the host's operating system, or deployment and configuration of the OpenStack environment. Access the Dynflow Console from any Tasks page.

Reports

The Reports page displays a list of reports of Puppet runs executed on the hosts that the installer manages. You can access this page at any time from anywhere in the user interface by clicking MonitorReports. You can also view all reports for a specific host by navigating to HostsAll Hosts[Hostname]Reports.
The Reports page

Figure 6.13. The Reports page

The reports table displays a list of the number of actions performed on individual hosts during a report interval. The time at which a report was collected is displayed in the Last report column, and actions are divided into a number of categories as outlined below:
  • Applied: The number of changes that were applied to resources on the host, such as files, directories, or user accounts.
  • Restarted: The number of resources, such as services, that were restarted.
  • Failed: The number of actions that were executed but did not complete successfully.
  • Restart Failures: The number of resources, such as services, that were scheduled to restart but did not restart successfully.
  • Skipped: The number of actions that were scheduled, but were skipped due to a problem scheduling the Puppet run.
  • Pending: The number of actions that were scheduled to be applied, but had not yet been performed at the time the report was collected.