[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opennms-install
Subject:    Re: [opennms-install] Upgrading from CentOS 5.5 & OpenNMS 1.8.10
From:       Marc Ritorto <mritorto () gmail ! com>
Date:       2014-08-15 19:30:02
Message-ID: CAKFdbWgekrSDCavGGRdSn5wKh7pHYAHZQH9ej1GEuQPJSvST4A () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


The up grade is a pain i had to use support

Thanks

Marc
On Aug 15, 2014 1:03 PM, "Dan Lacey" <daniel.p.lacey@gmail.com> wrote:

> Hi All,
>
> 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?
>
> Thanks!!!
> Dan
>
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> 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
>

[Attachment #5 (text/html)]

<p dir="ltr">The up grade is a pain i had to use support</p>
<p dir="ltr">Thanks</p>
<p dir="ltr">Marc</p>
<div class="gmail_quote">On Aug 15, 2014 1:03 PM, &quot;Dan Lacey&quot; &lt;<a \
href="mailto:daniel.p.lacey@gmail.com">daniel.p.lacey@gmail.com</a>&gt; wrote:<br \
type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> Hi All,<br>
<br>
I will be upgrading an opennms server.<br>
Currently it is running CentOS 5.5 (Final) and OpenNMS 1.8.10. (Just a<br>
bit long in the tooth...)<br>
I am looking for the path of least resistance...<br>
<br>
I am wondering if the latest stable release will run well on that<br>
version of CentOS.<br>
Can anybody give me some feedback on the best approach?<br>
<br>
1. Just upgrade ONMS and Java on the current system (will this even work?)<br>
        Will this require many other components to be upgraded<br>
independently of the OS? (e.g. Postgres)<br>
2. Dump the DB, upgrade the OS and ONMS, put the DB back and see what<br>
happens.<br>
        Any suggestions as to whether CentOS 6 or 7 is best at this time?<br>
3. Start completely from scratch.<br>
        Again, CentOS 6 or 7?<br>
<br>
Thanks!!!<br>
Dan<br>
<br>
<br>
<br>
------------------------------------------------------------------------------<br>
_______________________________________________<br>
Please read the OpenNMS Mailing List FAQ:<br>
<a href="http://www.opennms.org/index.php/Mailing_List_FAQ" \
target="_blank">http://www.opennms.org/index.php/Mailing_List_FAQ</a><br> <br>
opennms-install mailing list<br>
<br>
To *unsubscribe* or change your subscription options, see the bottom of this \
page:<br> <a href="https://lists.sourceforge.net/lists/listinfo/opennms-install" \
target="_blank">https://lists.sourceforge.net/lists/listinfo/opennms-install</a><br> \
</blockquote></div>



------------------------------------------------------------------------------


_______________________________________________
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

[prev in list] [next in list] [prev in thread] [next in thread]