Adding newrelic to old BOA and upgrading it somewhat smooth to latest stable

[Pls]

We have outdated BOA-2.2.3, which is just begging for upgrade. Wanted to add newrelic monitoring and got some confusion as to what is the proper procedure for that.

Basically, I'm not sure if we first need to do "barracuda up-legacy" (and same legacy upgrade for octopus) to 2.2.9 and just have newrelic key in /root/.barracuda.cnf. Or maby it's just enough to add newrelic key in /root/.barracuda.cnf and run "barracuda up-legacy system"?

Another idea - maby temporary its completely ok to just configure newrelic agent manually? Further BOA upgrades (when all caveats will be sorted out) will just owerwrite those changes (not sure if i'm right here). That would maby temporary solve our needs for newrelic, but is it good idea?

Now regarding ancient BOA-2.2.3 - what's the best process of going up to 2.3.5 stable? Read caveats from release notes till 2.2.9 and run "barracuda up-legacy" (along with similar commands for octopus instance). Then continue writing down all the caveats till 2.3.5 and execute "barracuda up-stable"?

[omega8cc]

To add New Relic only:

1. Add the key to /root/.barracuda.cnf
2. Run 'barracuda up-legacy system'

To prepare for stable:

1. Run 'barracuda up-legacy'
2. Run 'octopus up-legacy all both'

If everything works fine after some testing:

1. Run 'barracuda up-stable'
2. Run 'octopus up-stable all both'

There should be no issues besides little downtime during 'barracuda up-stable', unless you have some non-standard vhosts with legacy listen directives etc, so read about all caveats for 2.3.0+ first, make notes, so you will be prepared to fix problems if they will happen. But don't panic early, see what happens once upgrade is complete and cron had run for 2-3 minutes, try reload (not restart) nginx etc.=

[Pls]

Thanks for your fast awesomeness, I'm really impressed.

Just to clarify - 'barracuda up-legacy system' will not add anything specific only to BOA-2.2.9? How it differs from 'barracuda up-stable system', if it's just upgrading system packages? Better to be safe and clear, than sorry and down..

Still, thank you for all your guidance, I love your passion at doing things.

[omega8cc]

The 'system' upgrade/mode is NOT just about packages! It is about BOA configurations, agents, Aegir dependencies etc.

The difference between legacy and stable is huge, at least at the moment, so you can't just upgrade the system part only anyway.

It is explained at the top of docs/UPGRADE.txt, I think.

The 'barracuda up-legacy system' will simply upgrade system to latest 2.2.x version available, which is 2.2.9, but will not upgrade Aegir Master Instance. If you will add New Relic key first, it will install New Relic, but it the old mode, of course, just globally.

The 'barracuda up-legacy' will upgrade both the system and Aegir Master Instance (it will ask, and you should say Y/y or just hit Enter).

Only then you should run 'octopus up-legacy all both' to have everything upgraded and running on the max legacy version available: 2.2.9

Once it runs fine, you are ready to consider the upgrade to stable, which needs some preparation, but mainly it just needs that you read and understand caveats and how-tos/hints explained in the release notes for 2.3.0+

I hope this helps!=

[Pls]

Yep, clear as fresh air. Thank you very much!

[omega8cc]

We should add this extended information on upgrade procedures to our docs by default.