Currently we cannot migrate current RHEL 6.9 and Apigee 4.19.01 to Apigee 4.19.06 running in migrated RHEL 7.7 (using a migration/Zero downtime step process as indicated in the link).
We have new separate set up for RHEL 7.7 with Apigee 4.19.06 ( Future Set up) and Current set up VM/Hardware for RHEL 6.9and Apigee 4.19.01 (currently running), once Future set up is ready we will have to route our traffic from Apigee 4.19.01 running on RHEL 6.9 to Apigee 4.19.06 running on RHEL 7.7
Post setup and testing of Apigee 4.19.06 running in RHEL 7.7 (Future State), will not have the Token.Cache,Encrypted information of Apigee 4.19.01 running on RHEL 6.9.
In such cases to sync up, we will have to plan Cassendra ring join from Apigee 4.19.01 running in RHEL 6.9 with Cassendra ring of Apigee 4.19.06 running in RHEL 7..
This should take care of encrypted KVM, Cache and Token to sync up with Future State Cassendra (ie Apigee 4.19.06), and plan to Decompression/remove Apigee 4.19.01 running on RHEL 6.9,
Q1: Would like to know, did we face any any issues ? any surprises ? with such Cassendra ring formation of different Apigee versions (ie Apigee 4.19.01 Three CS and Apigee 4.19.06 Three CS)
Q2: Apugee and how much time this Caseendra ring should be active between 4.19.01 running on RHEL 6.9 with Cassendra ring 4.19.06 running in RHEL 7.7 ? any known guidelines ..
As per Apigee doc indicates following
*****************
Which components must you update
You must update all Edge components. Edge does not support a setup that contains components from multiple versions.
*************
Q: But connecting Cassendra ring between 4.19.01 running in RHEL 6.9 with Cassendra ring 4.19.06 running in RHEL 7.7. To sync up the KVM/Cache and Token, we don't have options, other than joining two CS of different versions.
LinkedIn
Twitter
