Re: [opennms-devel] Refactoring AssetRecord?

I'll start working on that, in my spare time.

It seems the largest challenges is how to deal with the importer/exporter as
well as the upgrades.  In other words, how do we create a simple template to
parse the vendor information into a single table?

The easiest way for the developer (but a PITA for the user) would be to
create a single vendor for each asset being converted/imported.  Then expect
the user to map them to a single Vendor ID, and remove the duplicate vendor
data.

If this was a graphical installer/importer, we could ask the user to map
them during the upgrade/import.  Not sure how to do it in the current setup.

First, I'll just do the refactoring.  Then, I guess we'll go over the next
step of putting into production scripts.

Going through how onms does it's DAO, Entity, and Servlets.  No doubt will
have questions.

Thanks!

Aaron


On Jan 28, 2008 3:32 PM, Matt Brozowski <[email protected]> wrote:

>
> On Jan 28, 2008, at 11:52 AM, Aaron Paxson wrote:
>
> > All,
> >
> > I would like to start refactoring
> > org.opennms.netmgt.model.OnmsAssetRecord to normalize some of the
> > data.  Specifically, I would like to bring Vendor information into
> > it's own class/table.
> >
> > For example, I have LOTS of Cisco equipment, but the TAC number and
> > maintenance contract pretty much stays the same.  Why can't I just
> > choose this for each node I have that is relevant, rather than
> > typing this in each time?
> >
> > Also, I'd also like to map multiple vendors to a specific node
> > asset.  This is because a node can have multiple vendors (hardware
> > support and software support could be different, as well as provider
> > support).
> >
> > I feel it would be administratively easier to add/remove vendors
> > separately from Assets, and just map the vendors to the assets as
> > needed.
> >
> > What is everyone's thoughts?
> >
> > I'm familiar with Hibernate, and understand the OnmsAssetRecord
> > class, but am not sure the implications of this change.  Obviously,
> > the webUI will also need to reflect it, as well as, creating a new
> > table in the upgrade/install script.
> >
> > Basically, before I start spending hours on learning the layout, I'd
> > like to know what everyone thinks.  If it's not worth it, can
> > someone give me a better idea?
>
>
> I think this is fine... Some of the trick will be making sure the
> installer can properly upgrade an existing database to the modified
> version that you define.  I'm all for the change though so...
>
> Give to me! You're not giving it to me fast enough!
>
> Matt
>
> ___________________________________________________________________________
> Matt Brozowski, OpenNMS Maintainer Main: +1 919 812 4984
> The OpenNMS Group, Inc. Fax: +1 503 961 7746
> Email: [email protected] URL: http://www.opennms.com
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> 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
>



-- 
Aaron J. Paxson
---------
[email protected]
http://aaron.thepaxson5.org

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

_______________________________________________
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