Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

History nodeset success-fail info

#133

Jobs and ad-hoc commands are executed across a nodeset. This information should be stored as a success-fail record (like a win-loss stat). The presentation should not emphasize a FAIL result but rather a "completion" level. So imagine a command or Job was run across 10 nodes on on three nodes the command failed the record would be "7 / 3" (text formatting not important).

Graphical visualization might incorporate a barchart (ascii or html): [####### ]

A mouse over might also read that data and render other calculations like:

  • average

  • ratio

  • total

Reported by Alex-SF · December 16th, 2010 @ 10:05 AM

State: resolved
Milestone: Rundeck 1.1
Assigned to: nobody

Activity

  1. Deleted User
    Deleted User

    December 16th, 2010 @ 10:06 AM

  2. Alex-SF
    Alex-SF
    • Milestone changed from Rundeck 1.0 to Rundeck 1.1
    • Milestone order changed from 36 to 0

    December 16th, 2010 @ 10:09 AM

  3. Alex-SF
    Alex-SF
    • Tag set to ux

    December 17th, 2010 @ 08:42 AM

  4. Alex-SF
    Alex-SF
    • Tag changed from ux to history, ux

    December 17th, 2010 @ 09:58 AM

  5. Alex-SF
    Alex-SF
    • Milestone changed from Rundeck 1.1 to Rundeck 1.2
    • Milestone order changed from 21 to 0

    January 13th, 2011 @ 07:48 AM

  6. Alex-SF
    Alex-SF
    • State changed from new to resolved
    • Milestone changed from Rundeck 1.2 to Rundeck 1.1
    • Milestone order changed from 10 to 0

    January 14th, 2011 @ 07:32 AM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.