The New Jobs Drawer in Ops Center 2.5
By user12601629 on Jul 26, 2009
Because Ops Center is designed to manage thousands of servers, we designed it differently than other, more traditional management systems. In particular, the core of the Ops Center Controller is a giant job queuing systems. Almost no actions in Ops Center are synchronous. When the user requests an action, a job is created and queued for execution. Then the job is picked up by a Proxy for execution against a group of managed Servers or OSs. Because this is all asynchronous, jobs can be queued against thousands of systems and executed in an orderly manner -- without blocking the user interface until they complete.
However, with all these jobs starting and completing on different schedules, it requires that Ops Center do a really good job of explaining to the user the state of the world. What jobs are processing? What has completed? Did anything fail? Thus, in Ops Center 2.5, we've redesigned the user experience for accessing the job manager status to be even easier. In version 2.0 and 2.1, there was a section in the left-nav that took you to a dedicated screen to access job info. Now it's available all the time.
Take a look at the screenshot below. At the bottom-left corner of the screen is the word "Jobs" followed by a set of icons and numbers. This shows you the current status of the job manager at a glance, all the time. Each of those numbers tells you how many jobs are in different states. How many have completed, are processing or have failed, etc.
Beyond that, each of those icons is a button (with a rollover tooltip to remind you the exact meaning of the icon) that allows you to access the Jobs Drawer. Let's start by clicking on the icon with the Yellow Arrow. This opens the Job Drawer and shows us all the jobs in the system.
Next, we might want to just focus in on the jobs that failed, so we click on the Red Stop Sign. That filters the jobs to only show ones with Failed status. The screen below shows that this looks like.
Now, of course, when you see you have two failed jobs you'll want to find out why. You can double click any of the jobs in the list and bring up the details of that job (example below).
The job details shows you each step in the job (many jobs have multiple components) and shows you the specific target(s) that may have failed (jobs can be directed and multiple hosts and may success against some and fail on others). This then gives you the info you need to investigate the failure, determine the problem and then, if you so choose, rerun the job against failed targets with just the click of a button.