Internal documentation only

This page has been marked as draft.

Cloud Upgrade Patches

Related to Copied

A script is used for cloud system upgrades whenever a customer requests custom additions. This will help reapply previously requested custom additions after each upgrade.

Problem Copied

Custom configurations disappear whenever there is an upgrade. These files include but not limited to:

• Monitoring Scripts
• Host Icons

Possible cause(s) Copied

• Cloud Upgrade

Possible solution(s) Copied

• Look for any ticket evidence for customer requests to include custom configurations permanently even after upgrades
• Once confirmed, support engineer shall modify Post Upgrade Script located in root directory for every cloud customer to retain requested custom configurations

~] vim /root/post_upgrade_patches

• Include comments in the script to reference custom additions from Jira or Ticket number.

i.e.
## Workaround for ... - OP-XXXX
## Add Custom ... - ticket XXXXX

• Use echo to print what step is executed before the actual script to run

i.e.
echo "Updating . . ."
echo "Adding Custom . . ."

• If the script references a file, the actual file must be placed in root directory

i.e.
~] mkdir logos
~]# ls -la /root
drwxr-x--- 2 root root 52 Apr 2 06:43 logos

• Apply Changes MUST NOT be included in the script as it should be done manually by the upgrader as part of the post upgrade process

Related article(s) Copied

• Opsview Cloud Documentation: ITRS Opsview Cloud