Categories:
Hot swapping in Aura
Description of Aura processes that can be executed without service outage
Introduction
The objective of the current documents is to describe the available actions that can be carried out over Aura through hot swapping processes, that is, without interrupting its operation. These actions include the update, insertion or removal of specific components or resources. The modifications resulting from these processes can be available immediately without the need to wait for the deployment of a subsequent Aura Platform release.
Despite the previous definition, performing a specific hot swapping process within a component can impact other components. In such cases, it becomes necessary to either restart the affected component or carry out a particular action to mitigate any potential issues or conflicts.
Available hot swapping processes and associated impact
The following table illustrates the available hot swapping processes against key Aura components, the impact of the process over each of them and the consequent actions that must be executed afterwards.
Each hot swapping process in the table is fully described in the document Hot swapping processes.
|——-|————-|———————-|————|———-|———-|————-|————|————————-|——————|———————|——————|———|————————|
| 1. Update locales | Restart | Restart | Restart | aura-configuration-updater
Make-up | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
| 2. Update NLP packages | N/A | N/A | N/A | N/A | Restart | NO1 | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
| 3. Modify TV use cases (User helper) | N/A | N/A | N/A | N/A | N/A | Restart | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
| 4. Channels handling | Restart | Restart | Reload | Make-up | Restart | Restart | Restart | NO2 | Reload| Restart | Restart | N/A |
| 5. Skills handling | N/A | N/A | Reload | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
| 6. Applications handling | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | Reload | N/A | N/A | N/A | N/A |
| 7. Add new local dialogs in aura-bot | N/A | N/A | N/A | DeployLocal | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
| 8. Update libraries and dialogs configuration | N/A | N/A | N/A | aura-configuration-updater | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
| 9. Add static resources in a uc | N/A | N/A | N/A | aura-configuration-updater | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
| 10. Review indexes definitions | N/A | N/A | Make-up | Make-up | N/A | N/A | Make-up | Make-up | N/A | N/A | Make-up | Force | Make-up |
Legend
- N/A: The change does not apply to the component
- NO: The change does not apply to the component, unless a condition is met
- Restart: the component will be restarted automatically by the config-watcher. The restart is executed pod by pod, with no impact to final users
- Reload: the component is not restarted, but its configuration will be reloaded automatically by the config-watcher.
- aura-configuration-updater: The hot swapping process must be executed using aura-configuration-updater.
- Make-up: the make-up of the component is executed during the deploy phase: both with
deploy-coreanddeploy-local. Take into account that aura-configuration-updater is included into thedeploy_localprocess - DeployLocal: the component is automatically restarted after the execution of its make-up
- Force: a restart of the component must be executed manually
Notes