| Item |
Section |
Comment |
Response |
| KS1 |
Rolling upgrade |
Rolling upgrade choreography need to be mentioned somewhere. I assume best page to cover that is Rolling Upgrade page |
We are not sure who will be the overall owner yet. Right now, we will just refer to the v2.1 doc for the overall choreography. |
| KS2 |
Rolling upgrade |
With multiple versions of application supported, there is no need for rolling upgrade for applications. It is only needed for instance/system upgrade. Right? |
No, it's still needed. The application versioning we have for this release is just the basic application versioning where only one version of the application will be enabled at one time in the runtime. So switching between versions will still cause loss of the service for that period of time. In the future, when we have the runtime versioning (where more than one versions could be enabled at the same time in the runtime), it can probably replace the current application rolling upgrade. KSHITIZ - Will load-balancer be involved in application upgrade? I mean will application be disabled by setting lb-enabled attribute to false, then when upgrade is complete setting it back to true. |
| KS3 |
Versioning |
What will happen during period when a new version of application is enabled? During this period, will requests for that application be blocked or some error response is send back? Does LB need to play any role during this period? |
We might try to do something in the grizzly layer to block/queue the request till the upgrade is finished, but not sure if it can be accomplished in this release. |
