Murphy's Law
So last week I was charged with the task of ensuring that the Training Room would be configured when a representative from Green Hills Software (www.ghs.com) came on-site to teach Integrity/Multi. I had to...
1. Make sure developers could run Multi from the training room
2. Make sure enough licenses were installed
My Preparation:
I had a license file generated last week for 50% more than the number of people who were in the class. I had tested a configuration which called for setting up a Remote Connection with a server which had the GHS software installed and configured. I judged that the remote server was powerful enough to handle the load of ~10 remote Gnome-supported connections + GHS over the network. The processor is a dual Xeon - so it stood to reason the it would have the power.
What Went Wrong:
I did not correctly install the training licenses. Even though the software gave me a "Success" message, it didn't write the new license file because the old one was still running a process and had a lock on certain files that needed to be modified.
I did not know that the Training Room computers were networked WIRELESSLY. Yeah... that slowed things quite a bit. No Remote Connection.
First Attempt to Solve Things:
Figured out how to correctly install the training licenses. Passed around CDs so people could individually install local copies of Integrity/Multi.
What went Wrong Next:
The license GHS gave me last week was for an x86 processor target while we were compiling for a target Simulated PPC board.
Second Attempt:
After a series of telephone calls to our support rep in Virginia and waiting for the license guys in Santa Barbara to arrive in their offices (by this time it was after lunch on the east coast - halfway through the first day of training), we finally had a viable system.
So, it is like the man said... Things will go wrong at the most critical times. Issues occur in bunches. Problems wait until large groups of users depend on their systems before occurring.
Good 'ole Murphy!
So last week I was charged with the task of ensuring that the Training Room would be configured when a representative from Green Hills Software (www.ghs.com) came on-site to teach Integrity/Multi. I had to...
1. Make sure developers could run Multi from the training room
2. Make sure enough licenses were installed
My Preparation:
I had a license file generated last week for 50% more than the number of people who were in the class. I had tested a configuration which called for setting up a Remote Connection with a server which had the GHS software installed and configured. I judged that the remote server was powerful enough to handle the load of ~10 remote Gnome-supported connections + GHS over the network. The processor is a dual Xeon - so it stood to reason the it would have the power.
What Went Wrong:
I did not correctly install the training licenses. Even though the software gave me a "Success" message, it didn't write the new license file because the old one was still running a process and had a lock on certain files that needed to be modified.
I did not know that the Training Room computers were networked WIRELESSLY. Yeah... that slowed things quite a bit. No Remote Connection.
First Attempt to Solve Things:
Figured out how to correctly install the training licenses. Passed around CDs so people could individually install local copies of Integrity/Multi.
What went Wrong Next:
The license GHS gave me last week was for an x86 processor target while we were compiling for a target Simulated PPC board.
Second Attempt:
After a series of telephone calls to our support rep in Virginia and waiting for the license guys in Santa Barbara to arrive in their offices (by this time it was after lunch on the east coast - halfway through the first day of training), we finally had a viable system.
So, it is like the man said... Things will go wrong at the most critical times. Issues occur in bunches. Problems wait until large groups of users depend on their systems before occurring.
Good 'ole Murphy!
0 Comments:
Post a Comment
<< Home