| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
| Created: | Wed Nov 13 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4455 |
| Total number of notes: | 16761 |
Hi,
This is going to seem like a very ignorant question. Here goes anyway.
Is there any way that the HUBwatch / DECagent code could be developed
in a slightly more modular fashion.
The reason I ask this is that new hardware modules do not seem to keep
in step with new versions of the software. I was thinking that a
possible solution to this may be that you have a base version of the
software (say v2.0) and if a new hardware module is released and no
new version of the software (i.e. including bug fixes and new features)
is planned for some time after then the customer could contact digital
and we could pop out and load (via a tape or a P.C.) the specific code
for that module.
Would that be possible in the future?
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 264.1 | No- 4 month release cycle | EMDS::SEAVER | Bill Seaver, HUBwatch Mktg | Mon Jun 14 1993 02:22 | 14 |
Nothing ignorant about that question. It causes us to tear our hari
out regurlarly. So far our solution is:
most new modules will have integral SNMP agents, thus the DECagent does
not need to be upgraded. Also newer versions of the agent will use
SLIP and HUBwatch for out of band so we do not have to maintain another
set of software to draw pictures.
All DEChub releases will happen on a 4 month schedule and hopefully the
HUBwatch software will match the hardware being released. Issuing
patches between that schedule would be difficult to impossible since
system test takes significant time. We may issue ports of HUBwatch to
different platforms when they are ready tho.
| |||||