...
...
...
...
- Client versions stored in your Kiuwan On-Premises servers: these are the versions that your Kiuwan On-Premises server provides to be downloaded and installed on your CI systems, development computers, etc. This versions are those shown in the System Administration Console.
- Client versions installed in your company's laptops, CI systems, etc.: these are the versions that were installed after your first Kiuwan On-Premises installation or subsequent upgrades. Once you upgrade your installation client versions, your company's computers may have old versions of Kiuwan On-Premises clients. The following steps address how to upgrade these as well.
...
...
...
...
...
...
...
...
...
...
Step 3: check if you need to follow specific steps for your Kiuwan On-Premises version
Step 4: run the full upgrade
...
...
Specific upgrade notes
This section provides information that you may need to follow in case you are upgrading one of these specific versions (see Checking for updates section if you want to check which version is installed in your company):
Kiuwan On-Premises version | Specific upgrade process needed |
---|---|
2.8.1910.1 | YES |
Upgrading from Kiuwan On-Premises 2.8.1910.1
...
...
Due to changes in how Redis Cluster is created through the installation process, in order to keep your installation up to date with the latest infrastructure you will need to follow a different approach to perform a full upgrade from this version.
...
...
- [INSTALL_DIR_OLD]: where the old kiuwan-cluster version was untared.
- [INSTALL_DIR]: where the new kiuwan-cluster version has been untared.
Note that if you are using AWS elasticache service to run Redis Cluster services you can ignore this process and follow the standard upgrade process.
Step 1: stop kiuwan services
*stop-kiuwan.sh (version vieja)
Step 2: update your current configuration
*update.sh (version nueva)
Step 3: prune current containers
*uninstall.sh (version nueva)
Step 4: clean Redis cluster data
*Borrar los datos del redis antiguo (data-local/Redis/data/**).
Step 5: update Redis cluster node information
*Cambiar en el fichero globalConfig.properties las direcciones de los nodos de redis.
redis.cache.nodes=172.17.0.1:6379,172.17.0.1:6380,172.17.0.1:6381,172.17.0.1:6382,172.17.0.1:6383,172.17.0.1:6384
redis.store.nodes=172.17.0.1:6379,172.17.0.1:6380,172.17.0.1:6381,172.17.0.1:6382,172.17.0.1:6383,172.17.0.1:6384
Step 6: modify the current configuration if needed
---Si se quiere modificar alguna otra propiedad, este es el momento.
Step 7: install current version
*install.sh (version nueva)
...