Automating Apigee edge installation - information needed

[navinrao]

We need to update our on-prem Apigee edge installation from 4.16.09 to 4.18.01, and we are trying to automate it using chef so that subsequent updates can be done easily.

The instructions on the Apigee website mention that we must follow an “Order of machine update” while performing the upgrade : https://docs.apigee.com/private-cloud/v4.18.01/update-apigee-edge-41609-41801#orderofmachineupdate

However, this means that for a 9 host clustered installation, there are about 20+ different steps which have to be done in a particular sequence on different nodes– along with using a ‘standby’ postgres node - which would be quite difficult to co-ordinate/implement in chef.

Would appreciate if anyone could tell me if we can just run the update utility
(/opt/apigee/apigee-setup/bin/update.sh -c component -f configFile)
on all the nodes at once, and also avoid using any ‘standby’ postgres node as well?

Thanks in advance for your help,
Navin

(P.S. - We will have a maintenance window to perform this action, so are not very concerned about losing any functionality or transaction data while this update is being performed.)

[dchiesa1 · Accepted solution]

No, you cannot just run update on all the nodes at once. You should follow the instructions. We've tested that approach, and that is what all customers are instructed to do.