Upgrade checklist: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
Dcunningham (talk | contribs) mNo edit summary |
Dcunningham (talk | contribs) No edit summary |
||
| Line 4: | Line 4: | ||
* Will one of your engineers be available during the upgrade in case of problems, and afterwards to test Enswitch is working? |
* Will one of your engineers be available during the upgrade in case of problems, and afterwards to test Enswitch is working? |
||
* Can any CDRs be deleted in advance to speed up the upgrade process? |
* Can any CDRs be deleted in advance to speed up the upgrade process? |
||
* Is a database backup configured to run in advance of the upgrade? It may also be necessary to temporarily disable Enswitch cron processes from running during the upgrade. |
|||
For the upgrade engineer: |
For the upgrade engineer: |
||
Latest revision as of 00:03, 22 October 2016
For the Enswitch owner:
- Have you reviewed all the Enswitch functional changes and planned for each of them?
- Is the Linux distribution package manager working on all servers? Please test it in advance.
- Will one of your engineers be available during the upgrade in case of problems, and afterwards to test Enswitch is working?
- Can any CDRs be deleted in advance to speed up the upgrade process?
- Is a database backup configured to run in advance of the upgrade? It may also be necessary to temporarily disable Enswitch cron processes from running during the upgrade.
For the upgrade engineer:
- Is firewall, ssh, and sudo access working on all servers?