[opennms-devel] event/alarm 3gpp model implementation

Hello all,
we'd like to submit to your attention what we're going to implement starting from OpenNMS 1.6.1 version.
We have talked with Davide Hustace about this work and he suggest us to write to this developer list
describing the work.
We need to work starting from version 1.6.1 because we have a short time delivery request,
so we prefer to work on a recognized stable release. (or 1.6.2 last released)
 
I attach 2 class diagram to explain first steps we have thought so to realize a 3gpp event/alarm model.
 
Class_Diagram_3gpp_datamodel.jpg
----------------------------------------------------------------
describe an astract of actual OnmsEvent and OnmsAlarm class and some relations of these entities.
Present the extention of the above with the declaration on all needed new attributes.
For the 2 new classes is presented a box with some notes. A little description of the specific attribute,
and a description for all derived attributes (meaning attributes already present into parent class, simply defined different accessor methods)
 
Class_Diagram_3gpp_datamodel-dao.jpg
--------------------------------------------------------------------
describe new classes needed to implements dao objects, with related changes into spring configuration.
We're thinking to extends JdbcEventWriter and JdbcAlarmWriter so to save OnmsEvent3gpp and OnmsAlarm3gpp specific attributes,
with a little modification of parent classes (Jdbc*Writer) so to be able to populate PreparedStatement
with all OnmsEvent|OnmsAlarm attributes but being able to control if the PreparedStatement should be executed
or just populated.
With David we have talked about a possible 3gppAlarmPersister to be used by Alarmd (alternatively to the actual AlarmPersisterImpl),
but this approach is not in 1.6.1 so we are not able to follow it by now.
 
With the proposed approach all jsp and all other classes presents in OpenNMS will continue to work
because OnmsEvent3gpp and OnmsAlarm3gpp are extentions classes.
 
Our idea is that one could start or with default event/alarm model, or with the 3gpp model.
So we need to define a customization of database schema creation (referring to create.sql),
for example an 'update_schema_3gpp.sql' to be invoked at the end of OpenNMS installation process
and before start working with it.
 
What do you think about this? Do you see any contraindication ?
Thanks for any reply.
Andrea C.

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword

_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-devel mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel