r11536tor11537upgradeoverviewmop.j2

markdown_main templates/upgrade_main/r11536tor11537upgradeoverviewmop.j2

Back to Dashboard
Jinja2 Template 148 lines
<!---
Copyright (c) Microsoft Corporation. All rights reserved.
Highly Confidential Material
-->

|**Metadata**|**Description**  |
|--|--|
|Doc Title|  MVM v3: Release {{ DOWNLEVEL_MVM_VERSION | default('<DOWNLEVEL_MVM_VERSION>') }} to Release {{ UPLEVEL_MVM_VERSION | default('<UPLEVEL_MVM_VERSION>') }} Upgrade Overview|
|Navigation|[WIKI Home Page](https://dev.azure.com/mvmprodeus2/MVM/_wiki/wikis/documentation/1/documents-home#)|
|Tracking| Document Number: VPE-5512-000|
|Author| Graeme Thomson (gt163y) |
| Agreement Number | 24252.S.005 |


**Notices**

Copyright &copy; 2025 Metaswitch Networks.  All rights reserved.

This manual is Confidential Information of Metaswitch Networks subject to the confidentiality terms
of the Agreement 01019223 as amended between AT&amp;T and Metaswitch Networks.

It is issued on the understanding that no part of the product code or documentation (including this manual)
will be copied or distributed without prior agreement in writing from Metaswitch Networks and Microsoft.

Metaswitch Networks and Microsoft reserve the right to, without notice, modify or revise all or part of
this document and/or change product features or specifications and shall not be responsible for any
loss, cost, or damage, including consequential damage, caused by reliance on these materials.

Metaswitch and the Metaswitch logo are trademarks of Metaswitch Networks. Other brands and
products referenced herein are the trademarks or registered trademarks of their respective holders.

Product(s) and features documented in this manual handle various forms of data relating to your
users. You must comply with all laws and regulations applicable to your deployment, management,
and use of said product(s), and you should take all appropriate technical and organizational
measures to ensure you are handling this data appropriately according to any local legal and
regulatory obligations.

You are responsible for determining whether said product(s) or feature(s) is/are appropriate for
storage and processing of information subject to any specific law or regulation and for using said
product(s) or feature(s) in a manner consistent with your own legal and regulatory obligations. You
are also responsible for responding to any request from a third party regarding your use of said
product(s), such as a request to take down content under the U.S. Digital Millennium Copyright Act
or other applicable laws.


Metaswitch Networks
399 Main Street
Los Altos
CA 94022
<http://www.metaswitch.com>


***
***Table of Contents***
[[_TOC_]]


# Document History

| **Issue** | **Issue Date** | **Author(s)** | **Identification** **of** **Changes** |
|-|-|-|-|
| 1 | 09/30/2025 | gt163y | Initial version |


# 1. Introduction

This document serves as an overall guide to the set of MOPs required to upgrade an
existing MVM deployment of MVM on Azure (also known as MVM v3) from Release **`{{ DOWNLEVEL_MVM_VERSION | default('<DOWNLEVEL_MVM_VERSION>') }}`** to Release **`{{ UPLEVEL_MVM_VERSION | default('<UPLEVEL_MVM_VERSION>') }}`**.

It includes a list of MOPs to run, in order. Use this as a reference to know when to run each of the individual MOPs included.

# 2. List of MOPs

The following MOPs must be followed to upgrade the deployment from Release **`{{ DOWNLEVEL_MVM_VERSION | default('<DOWNLEVEL_MVM_VERSION>') }}`** to Release **`{{ UPLEVEL_MVM_VERSION | default('<UPLEVEL_MVM_VERSION>') }}`**.

>Note that the MOPs ***must*** be run in the order listed.

## 2.1 Upgrade resources on all regions in the deployment

***
These MOPs ***must*** be run on all regions before proceeding with the subsequent steps
***


**Upload new release artifacts** [*R1153UploadArtifacts*](r1153uploadartifacts.md)


## 2.3  Upgrade the region specific resources

***
***The first region to be upgraded must be the deployment region***
***






**Prepare the up-level config repository** [*R1153upgradeConfiguration*](r1153upgradeconfiguration.md)

- The value to use for **DOWNLEVEL_MVM_VERSION** is `{{ DOWNLEVEL_MVM_VERSION | default('<DOWNLEVEL_MVM_VERSION>') }}`.

- The value to use for **UPLEVEL_MVM_VERSION** is `{{ UPLEVEL_MVM_VERSION | default('<UPLEVEL_MVM_VERSION>') }}`.

- No new variables have been introduced in this release.


- No existing variables have been retired in this release.



- No existing variables need to be updated.



- No configuration needs to be specified in the file perimeta-config. Ensure that it is set to:
  ```
  # Copyright (c) Microsoft Corporation. All rights reserved.
  # Highly Confidential Material
  #
  # WARNING: Modifications to this file may cause your deployment to break.
  #
  # Changes should not be made without consulting your Support representative, and must
  # be done by following the process for updating a Service Instance by replacement.
  ```


- There are no new secrets introduced in this release.







**Upgrade CCM SIs** [*R1153UpgradeCCM*](r1153upgradeccm.md)


**Upgrade CMM SIs** [*R1153UpgradeCMM*](r1153upgradecmm.md)



**Upgrade the CLI tools** [*R1153UpgradeCLITools*](r1153upgradeclitools.md)