About MATRIXX Installation and Upgrade
MATRIXX Installation and Upgrade describes the tasks required to install MATRIXX components as containers using Kubernetes and Helm.
Intended Audience
This information is intended for anyone who will install and configure containerized MATRIXX components.
Before following the procedures in this guide, see MATRIXX Architecture for an introduction to the system architecture, and information about MATRIXX Engine high availability and disaster recovery configurations. For information about installing and configuring the MATRIXX web applications (My MATRIXX and MATRIXX Backoffice Customer Tool), see MATRIXX Web App Administration.
For information about installing and administering 5G event streaming microservices, see MATRIXX 5G Event Streaming.
About MATRIXX Upgrades
The upgrade process tasks depend on the type of upgrade you are performing.
MATRIXX Upgrade Changes summarizes possible upgrade changes by MATRIXX release type for MATRIXX Data Container (MDC) schema changes, pricing compiles, online database upgrades, backward-compatibility, and checkpoint compatibility.
Release Type | MDC Schema Changes | Pricing Compile Required | Online Database Upgrade | Backward- Compatibility Guaranteed | Checkpoint Compatibility Guaranteed |
---|---|---|---|---|---|
Architectural | yes | yes | yes | no | no |
Functional | yes | yes | yes | no | no |
Maintenance | incremental | no | no | yes | yes |
For API changes, see the Application Integration new features and Interface Changes in MATRIXX Release Notes.
Upgrade Paths
For information about MATRIXX upgrade scenarios tested and supported for this release, see the discussion about upgrade paths in MATRIXX Release Notes.
Upgrading Without Processing Interruptions
Upgrades that include schema changes to the MATRIXX Engine are performed online, that is, while the MATRIXX Engine continues to process network traffic.
You do this by upgrading an engine while the rest of the engine chain continues to process network data and queue real-time transactions. The database schema and APIs are upgraded by the standby engine while the active engine processes network data normally. You then make the upgraded standby engine active and upgrade the other engines in the chain. Because MDC traffic is always backward-compatible, this process is invisible to the applications communicating with MATRIXX Engine.
About the MATRIXX Schema Versions
An engine with an older system schema version does not start if an active engine with a higher version is already running. The MATRIXX schema version is an unsigned 16-bit number that represents a snapshot in time of a specific collection of MDCs. There are two schema versions, one for base MDCs and one for service provider custom MDCs. These schema versions are incremented each time one or more MDCs have changed. The MDC header also has a schema version for the MDC fields. One schema version has the highest schema version of any MATRIXX field in the MDC, and the other stores the highest schema version of any Service Provider field in the MDC.
Documentation Conventions
Bold | Identifies items whose names are predefined by the system, such as user interface controls. |
Italics | Identifies variables that are parameters whose actual names or values are to be supplied by the user. |
Monospace | Identifies file names and directories, data value examples, code examples, blocks of code, references to code snippets inline, system messages, and commands supplied by the user. |
Dash (-) | A dash (-) in a property table cell indicates the property in that row does not have a default value. |
Documentation Feedback
MATRIXX Software strives to provide concise, complete, and accurate product documentation and welcomes all feedback. If you have any comments, corrections, or suggestions for improvement, send them to [email protected].
Support
- Discovery and sizing services.
- Installation and configuration services.
- Data migration and update services for pricing and subscribers.
For more information about MATRIXX services, contact us.