Page 2 of 2

Re: Virtual Machine Upgrade Path

Posted: Thu Apr 14, 2016 2:56 pm
by tmcdonald
In my opinion, if you need a truly offline install then you should follow the instructions on http://repo.nagios.com/ and not use the pre-built VM, which was built in an online environment. Trying to use a pre-built VM to upgrade offline is not going to work the greatest, and is not something we have really officially tested/documented.

Re: Virtual Machine Upgrade Path

Posted: Tue Apr 19, 2016 8:20 am
by sm00thindian
Perhaps it's something you should think about... the purpose of a VM is that the server is "ready", that shouldn't mean your current customers shouldn't benefit from that convenience.

Re: Virtual Machine Upgrade Path

Posted: Tue Apr 19, 2016 10:04 am
by hsmith
We offer a solution for source installs, offline installs, and drop in place installations. I believe @ssax provided a decent solution in his post. A lot of environments that need to deny their server internet access will have repos available that can be accessed without touching the internet.

If you have any suggestions, please feel free to post them here, and we can forward the information on.

Re: Virtual Machine Upgrade Path

Posted: Tue Apr 26, 2016 8:14 am
by sm00thindian
From a support perspective here is the issue. CentOS is a publicly maintained Operating System. If packages were corrupted or intentionally changed to facilitate the intentions of a malicious actor there is no recourse. For a large, high dollar, highly secure environment (3 letter gov and the like) this makes Nagios less desirable. By providing a VM and a path to upgrade between VM versions Nagios would benefit.

Re: Virtual Machine Upgrade Path

Posted: Tue Apr 26, 2016 8:20 am
by eloyd
Use RHEL instead of CentOS if you must have a private, secure, no-Internet install. It's unfortunate, but it's the "Way of Things." You can then host a private RHEL repo for fixes that you get from your RHEL distribution channels.

Re: Virtual Machine Upgrade Path

Posted: Tue Apr 26, 2016 9:23 am
by hsmith
Thanks Eric, that's completely accurate. The solution is to host your own offline repository if the ones that CentOS use cannot be trusted.