Difference between revisions of "Template: PEUpgradeBoilerplate"

From Genesys Documentation
Jump to: navigation, search
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
 
<onlyinclude>{{#switch:{{NAMESPACENUMBER}}|620=<font color=green>|#default=}}{{#switch:{{{BoilerplateSection|}}}<!--Boilerplate text for the intro on the PE Upgrade topic.-->
 
<onlyinclude>{{#switch:{{NAMESPACENUMBER}}|620=<font color=green>|#default=}}{{#switch:{{{BoilerplateSection|}}}<!--Boilerplate text for the intro on the PE Upgrade topic.-->
|UpgradeIntro={{NoteFormat|The instructions on this page assume you have deployed the services in service-specific namespaces or OpenShift projects. If you are using a single namespace for all private edition services, replace the namespace element in the commands on this page with the name of your single namespace or project.}}
+
|UpgradeIntro={{NoteFormat|The instructions on this page assume you have deployed the services in service-specific namespaces. If you are using a single namespace for all private edition services, replace the namespace element in the commands on this page with the name of your single namespace or project.}}
 
==Supported upgrade strategies==
 
==Supported upgrade strategies==
 
{{#sub:{{MINTYDOCSMANUAL}}|0|-22}} supports the following upgrade strategies:
 
{{#sub:{{MINTYDOCSMANUAL}}|0|-22}} supports the following upgrade strategies:
Line 32: Line 32:
 
==Timing==
 
==Timing==
 
A regular upgrade schedule is necessary to fit within the Genesys policy of supporting N-2 releases, but a particular release might warrant an earlier upgrade (for example, because of a critical security fix).
 
A regular upgrade schedule is necessary to fit within the Genesys policy of supporting N-2 releases, but a particular release might warrant an earlier upgrade (for example, because of a critical security fix).
 +
 +
If the service you are upgrading requires a later version of any third-party services, upgrade the third-party service(s) before you upgrade the private edition service. For the latest supported versions of third-party services, see the {{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide|topic=Prerequisites}} page in the suite-level guide.
 
===Scheduling considerations===
 
===Scheduling considerations===
Genesys recommends that you upgrade the services methodically and sequentially: Complete the upgrade for one service and verify that it upgraded successfully before proceeding to upgrade the next service. If necessary, roll back the upgrade and verify successful rollback. <!--End of Timing section -->
+
Genesys recommends that you upgrade the services methodically and sequentially: Complete the upgrade for one service and verify that it upgraded successfully before proceeding to upgrade the next service. If necessary, roll back the upgrade and verify successful rollback.
 +
 
 +
{{#switch:{{NAMESPACENUMBER}}|620=
 +
{{Editgrn_open}}<font color=red>In addition to providing info on any specific scheduling considerations for your service, please also include information on any specific needs for upgrading the 3rd party services that your service uses.</font>{{Editgrn_close}}
 +
|#default=
 +
}}
 +
<!--End of Timing section -->
 
|Monitoring=<nowiki/>
 
|Monitoring=<nowiki/>
 
==Monitoring==
 
==Monitoring==

Latest revision as of 12:30, February 20, 2023

Retrieved from "https://all.docs.genesys.com/Template:PEUpgradeBoilerplate (2025-07-25 02:34:22)"