The Secret Diary of Han, Aged 0×29

We had so many issues to solve around getting things to work in the deployment environment, correcting errors, and verification, that we hardly got started on verifying the cycle 1 stories. Most were not even started yet. Some were done and rejected with some extra work. We’ll continue this on tuesday (monday is a holiday).

See comments in individual stories for some comments.

Micromuse installed some SSM’s and ASM’s today in decafe, for us to play with. The configuration tool is on backup01.

Event flow in Decafe now works end-to-end using the stub helpdesk. We solved a number of problems due to config files being overwritten during the auto deploy.

• Service correlator now does not cache Component state. It does cache dependency information, so that lookup is fast.However, it now is stateless with respect to component states. The old Correlator used a Dataset representation of components and dependencies.

  The new implementation reuses the ComponentCache that is in use in reporting.

• Added writeCount protocol, so that multiple highly available service correlatorscan process the same event without interference.
• Added NUnit test cases for all of the above. These are not added to Nant yet, in order not to brake the build on the buildmachine.These testcases create a new database, and assume the presence of SQL and a certain SA password.

All alerts in Netcool are stuck in status 2 (raised to Smart24). This means they never saw a ticket-opened or closed notification coming back into Netcool. I investigated a bit, and found that the SocketGatewayListener, which is a perl script that is listening for messages from Netcool’s socket gateway, is not receiving any messages. The listener itself is working fine, since I can telnet into it and send a message manually. However, the socket gateway appears to be working OK too. I can see in its log that it is picking up alerts and sending them (internally) to its writer.

This is a mystery to me. Perhaps somebody can shed some light on this

The CVS sourceforge problems is fixed. The tracker / commit log integration has been reactivated.

When you commit in CVS, you will see a “tracker:” text. If you enter the number of the story you are working on here, links will be created automatically from the story to the checked-in code in Sourceforge

This changes the CVS config, so you need to check-out anew in a virgin directory. I sent an e-mail on this this afternoon. Unfortunately it didn’t get delivered due to a problem wiht our Exchange server. I resent the message tonight.

• Database creation / deletion scripts for Service correlator test cases
• Created database read test cases for Service Correlator.
• Partly implemented new Service correlator cache until read testcase succeeded
• Fixed Exchange name lookup problem (by rebooting!)

Sourceforge lets you move tracker items around. I took advantage of this to move the user stories for the current cycle from the Feature Requests tracker to a new tracker I created called “Cycle 1 user stories. This tracker now contains all stories to be implemented in this cycle.

Similarly, I will create a new tracker for the next cycle, and will move stories to be implemented in this cycle to it. Feature requests will serve as a repository for stories, and new stories will initially be added here, until they are scheduled for a cycle.

I moved all userstories from the Excel spreadsheet into Sourceforge. Sourceforge has the concept of “trackers”. The user stories are being treated as “feature requests”. You’ll see 101 user stories there, 99 open and 2 closed. Please use sourceforge from now on instead of the spreadsheet

Most story id numbers are identical to the ones in the spreadsheet, but there are some differences:

• 6 11
• 34 35
• 53 -> 59
• 54-59 -> (-1)
• 91 – 99 -> (-1)

Some of the category names have changed as well. Here are the new categories (old ones in brackets:

• Accessibility
• Customer Portal
• Event Collection (was: polling)
• Event Correlation (was: Micromuse)
• High Availability
• Provisioning (was: Dependency viewer)
• Scalability
• Security
• Management
• Ticketing (was: Siebel)
  Each user story has a “projected hours” field, that I filled out for some, but not all stories. Please check this for your stories and fill it out where necessary.Stories can be associated with tasks, which can then be used to fill out more details, and are linked to the project management side of sourceforge. Unfortunately, only one task per tracker is allowed. We’ll add tasks to all stories that are planned for a cycle. Please add tasks for each story that you are responsible for, for the current cycle.

  Once the CVS problem with sourceforge is fixed, we can create links between check-ins and user stories as well, by adding the user story number in the CVS commit log message

We have only 10 sourceforge accounts for now. More are on the way. However, since all 9 developers are using CVS, I decided to use 9 accounts for this. The one account left is, for now, to be used by everybody else.

BTW, we need to start using CVS for all Micromuse configurations and scripts soon