1. In Progress:

Issue/Feature Description Status Feature: Statistics "Time-Table" Allow a user to look at the stats associated with only the last hour, or day, etc... Progress: Started simple, a "day" and "hour" summary item... avoids needing a full "history" mechanism, for now.(4/8) Issues Being Worked on: Designing history database mechanism to allow efficient storage of all job info for the last couple of days. Feature: Peer Node List Control Allow a user to delete a peer node from the peer node list. Related, allow a user to reset the statistics for a peer node. Progress: Created a "clear stats" method for the peer node object(4/9) Issues Being Worked on: Building mouse listener to allow "context-menus" for the table Feature: Terminology Ensure all the statistics are labled with intuitive names that don't confuse the heck out everyone. :) Status: In Discussion for resolution Progress: More discussions. This has revived a possible change in peer node messaging format, moving to XML with well defined statistics tags. Yay!(3/28) Took some votes, changed a few lables... more to do v.0.6.6(3/29) Issues Being Worked on: Lots of discussion going on on ChessBrain.net to dtermine correct terms to be used from here on out for statistics.

2. In The Hopper:

Issue/Feature Description Status Feature: Time-based Trend Graphs Show a graph displaying metrics over defined time intervals. The chosen metrics and time interval will eventually be configurable. Example: A line-graph that shows the number of jobs accepted by each peer node, every 10 mins for the last day. A line for Total Jobs (for all peer nodes) could also be included. Progress: This builds on top of the work being done to add a "history" mechanism(4/1) Issues Being Worked on: Currently working on defining an efficient way to store job information for a specified amount of time (such as a day) without using actual archived Job objects, which is not efficient use of memory. What is a reasonable maximum amount of total time to graph? What's useful? E.g. A day? an hour? a week? (I'll probably start with one day.) Feature: CB-MOC Documentation Create and add CB-MOC documentation and add it to this site, and eventually to a help function to CB-MOC. Progress: Started this page... :) (3/29) Issues Being Worked on: Making time. Pending Issue: Accept New Message Format The prediction is that the peer node monitors will change it's messge format to include many XML tags with lots of great information. CB-MOC will be changed to take advantage of this. Progress: More discussions regarding the tags etc, on the ChessBrain bbs.(3/29) Issues Being Worked on: Pending finalizatin of XML tags for peer node messages.

3. On the Drawing Board:

Feature Description Priority Consideration Full Peer Node Statistics Dialog By double clicking a row in the peer node table, a window will pop-up providing full statistical analysis of that peer node, including many stats that we don't have room for in the table. (For Example: Average jobs per hour (minute?), peer node graphs, etc.) In my opinion, this should be considered as a basic functionality, but there are a few other things that will be more urgent than this. I'm guessing this will come somewhere in v.0.8.x. Feel free to help me place the priority of this if you have an opinion. "Log to file" option. This important feature allows users to log information recieved from peer nodes to a file. While the first implementation of this will first only log the raw messages from the peer nodes, options will later be added to log to XML, or other useful logs. The basic functionality of this feature is considered a necessary feature, and will therefore receive a high priority. Currently slated to be included somewhere in v.0.7.x. Exporting Statistics Allow the user to export current statistics to a file. Formats will probably include XML, basic HTML, and possibly a CSV format if requested enough. :) While not considered to be within the scope of this initial feature, some basic HTML templating capability would be nice, along with a scheduled "publishing" feature to allow to incorporate regular updates on a team web site, etc. The basic functionality of this feature is considered a necessary feature, and will therefore receive a high priority. The extra features will probably get pushed farther down the pile for awhile. Guessing this will be included in small incremental pieces around v.0.9.x Security: Peer Node ACL's Allow the operator to define the IP addresses of the peer nodes from whom the CB-MOC shoud accept connections. This is important to people who want to accept connections from peer nodes that are not on their local area network, and possibly from the internet. This will help avoid the possibilty of someone messing with your stats by sending bogus information. (Such as with the peernode_dummy program included with CB-MOC for testing purposes.) Medium Priority. It seems users are crying out for other things louder than this one. However, since I'm a network / application security specialist by career, I see a big need for this if I'm going to continue to use my own program. :) So, this will not be low on the TO-DO list. Hopefully this will be included somewhere in v. 0.8.x. More Coming ... ...

1. Completed:

Issue/Feature Description Status Feature: Basic Time Stamp Column Add Color Highlighting, signifying peer node activity / idle time Status: Functional- COMPLETED Progress: Building a "Master"table cell renderer (which will replace the number and date cell renderers) to enable row-based highlighting(4/6) Completed cell rederer and it now supports all data types with specific formatting by column as well(4/8) Completed"aging" process with shades of reds and blues(4/8) Completed, v 0.6.9 (4/8) Feature: Basic Time Stamp Column Add time column peer node table, showing the time the last job was submitted for a particular peer node. Status: Functional- COMPLETED Progress: Added timestamp: property to CbJob bean, table column (3/27) New table cell renderer to allow customized formatting of timestamp (condensed format) (3/28) Added new sorting code to make sure timestamp sorting occurs based on actual date/time value and not based on alphabetic order of the text in the cell. (3/28) Completed, v 0.6.3 (3/30) Feature: "Delta/Idle" Time Column Implement a column in the table that shows the seconds since last job was recived from a peer node. Status: Functional - COMPLETED Progress: Finishing some architecture modifications to allow me to support an update timer thread...(3/29) Completed v.0.6.6(3/30) Feature: "Real-Time" Column Sorting If a user has selected that the peer-node table should be sorted by a particular column, the rows will continue to sort themselves as the table data is updated. Note that this functionality will eventually be optional. Status: Functional - COMPLETED Progress: Have added some code to support a "table data model listener" to allow notification of updated data in the table. (3/27-29) Fully functional, however, I'm sure I'll need to optimize things later... Completed! v.0.6.7(3/30)