Re: Upgrading from CentOS 5.5 & OpenNMS 1.8.10

Les - Thanks for the input! Yes, this is the way "I" would like to go....

Anybody still running CentOS 5.5? What version of ONMS are you using?
We are considering staying with current OS and using the latest ONMS 
release that will work on this OS (for now).

Sincerely,
Dan

On 8/15/14, 11:40 AM, Les Mikesell wrote:
> On Fri, Aug 15, 2014 at 12:02 PM, Dan Lacey <[email protected]> wrote:
>> I will be upgrading an opennms server.
>> Currently it is running CentOS 5.5 (Final) and OpenNMS 1.8.10. (Just a
>> bit long in the tooth...)
>> I am looking for the path of least resistance...
>>
>> I am wondering if the latest stable release will run well on that
>> version of CentOS.
>> Can anybody give me some feedback on the best approach?
>>
>> 1. Just upgrade ONMS and Java on the current system (will this even work?)
>>       Will this require many other components to be upgraded
>> independently of the OS? (e.g. Postgres)
>> 2. Dump the DB, upgrade the OS and ONMS, put the DB back and see what
>> happens.
>>       Any suggestions as to whether CentOS 6 or 7 is best at this time?
>> 3. Start completely from scratch.
>>       Again, CentOS 6 or 7?
> Unless you have a lot of custom changes to preserve of have to keep
> old history, I'd recommend starting from scratch using CentOS7 and and
> Opennms 1.12.9 which has support for systemd.   A lot of things have
> changed and this also lets you modify your rrd layout (storebygroup,
> jrobin vs rrdtool, etc.).   The stock postgres/openjdk 1.7 work fine
> but I think installing opennms via yum will still pull in a different
> 1.6 jdk that you can ignore.  You may want to come up with a way to
> use provisioning to manage the nodes.
>
> If you do try to upgrade, you'll probably need to go to a 1.10 version
> first, following:
> http://www.opennms.org/wiki/Upgrade_Guide:_1.8_to_1.10
> and then
> http://www.opennms.org/wiki/Upgrade_Guide:_1.10_to_1.12
>
> If you have some old changes to merge into the new setup, a fairly
> painless approach is to save your old opennms/etc directory somewhere
> and compare it to the new one after a fresh install.  If you aren't
> already using some version control tool for this, the gui 'meld' tool
> will do either a file or directory comparison showing color-coded
> changes and point/click merges so you can copy your changes into the
> new configs.
>
> There is also a tool to help with conversion to provisioning:
> http://www.opennms.org/wiki/Migrate_from_Capsd_and_Discovery_to_Provisiond
> although I think that might be slightly out of date and for a small
> number of nodes it might not be worth the trouble.  If you are mostly
> starting from scratch you could just do the part that generates the
> provisioning requisition to use in the new system and ignore the part
> about updating the existing database to keep the node numbering.
>


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

opennms-install mailing list

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