...
- EVC implements support for v2, and supports both v1 and v2 APIs in version 3.1.
- EVC is upgraded to 3.1. At this point, both v1 and v2 APIs are supported by EVC, so existing EVE instances with 3.0 or below will continue to work with v1.
- EVE software adds support to switch to v2 APIs, with default choice as v1, in version 3.1.
- Some of the EVE instances are upgraded to 3.1, and configured to use v2 API. They will work too, since EVC supports v1 and v2 at this point. Any EVE-EVC integration issues can be debugged and fixed at this point.
- All the devices are upgraded to 3.1, and switched to v2 API
- EVC stops supporting v1 from 3.2
- EVC is upgraded to 3.2. This should not be a problem since all the devices are moved to v2 at this point
- EVE stops supporting v1, and makes v2 as the only supported API version, in 3.2
- EVE instances are upgraded to 3.2.
- After this point, any EVE instance trying to go back to a version 3.1 are or below(which use v1 API), will see failure, and come back to the current version. This is because the older version will try to talk v1 to EVC, which is discontinued, and hence EVE will timeout, declare the old image toxic and fallback to current version.
...