Re: best practice WRT use of "provision.pl requisition import ..."

Thanks David I appreciate the detailed response. The question was answered and I was able to get everything working without having to adopt PRIS at the moment, but I will definitely keep this in mind. There was nothing broken in provision.pl and hope I did not infer that.

So at this point as an OpenNMS consumer (and it is providing a powerful role) my biggest concern is not being able to update beyond 19.1.0 for the reason I mentioned earlier in the thread WRT the Advanced Alarm Search functionality changing behavior. I sure hope that the enhancement request which will ostensibly bring back the 19.1 search ability (plus a lot more as I understand) is something that can get some attention soon.

Thanks again for a wonderful tool.
Paul





-----Original Message-----
From: David Hustace [mailto:[email protected]] 
Sent: Tuesday, February 20, 2018 10:41 AM
To: DiscussionList List <[email protected]>
Subject: Re: [opennms-discuss] best practice WRT use of "provision.pl requisition import ..."



> On Feb 20, 2018, at 09:39, Hernandez, Paul <[email protected]> wrote:
> 
> Well sadly not looking for a rip and replace solution at this time but yes will certainly look at it.

I understand, however, because we have such a small development community, we chose to only provide updates tp the current major release while we are working on the new features for the next major release.  Unfortunately, that makes it difficult when answering questions and providing solutions about previous releases for even if you get beyond a non-bug related issue, how tenable is that going to be when there are so many bugs and security fixes in the current releases.


> Our script is also an updater which compares current inventory against what is in onms and adjusts with add/deletes/replace. Lots of control and we like that.

I understand the use case and I believe that was the reason for PRIS.  I'm not sure that the current PRIS release wouldn't work with your version but here we are back to the version question and I can just assume you've already investigated that.  Though, I can't really imaging that it wouldn't work for I don't think we've change the document spec such that it would break the integration.  I'm just giving you my best practices advice without helping debug you current script... though, I know that's what you'd prefer.  Perhaps someone with better scripting skills will try.


> So I guess there is no answer to the OP’s original question beyond rip and replace?

There probably is an answer.  If I get more time, I'll look deeper.  Hopefully someone else will chime in, here.


David


David Hustace
The OpenNMS Group, Inc.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

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