Upgrade, rollback, or uninstall BDS
Learn how to upgrade, rollback, or uninstall Billing Data Service (BDS).
Before upgrading, ensure that you have a current backup of configuration files for configmaps.
To upgrade to a new release of BDS, deploy the new release. BDS provides a tool to automatically migrate configuration settings to the new release. If the new release introduces new parameters, or has changes to existing parameters, BDS prompts you to populate them.
This section describes how to use the BDS migration tool to patch your configuration file in preparation for upgrading BDS.
Prerequisites: Ensure that the cfg_file parameter in gvars.py contains the correct path to the configuration file to be patched:
docker run -e ACTION=config -u genesys -t -v $(pwd)/etc:/genesys/etc -i pureengage-docker-production.jfrog.io/cloudbilling/scripts:latest
- Prepare environment:
. /home/genesys/.bash_profile export BDS_OPERATING_MODE=MULTICLOUD_PE
- Run configuration wizard:
python3 brsctl.py migrate Starting configuration migration config.py:init: Trying to read configuration from /genesys/brs/config.json 2021-04-28 11:54:50,290 DEBUG MainThread config.py:init: Read configuration from /genesys/brs/config.json Found configuration 100.0.000.0001, BDS 10.0.000.01. Searching for required migration patches... Patches to be applied: 0.0.0.0 to 100.0.000.0002, 100.0.000.0002 to 100.0.000.0003 Proceed? [y/N]: y Current configuration backup file '/genesys/brs/config.json.100.0.000.0001.backup' and gvars '/genesys/brs/gvars.py.100.0.000.0001.backup' are created Applying patch 0.0.0.0 to 100.0.000.0002 ... ------> OK Applying patch 100.0.000.0002 to 100.0.000.0003 ... ------> OK Migration process completed successfully. The configuration has been upgraded to 100.0.000.03
- Refresh the configmap as described in Provision BDS: Create configmap.
To roll back BDS to an earlier release, run the deployment process for the desired release. To roll back the configuration, use the backup files you created before upgrade.
To uninstall, execute the command helm -n <namespace> uninstall <bds-deploy-name>.