Migration Guide 23.3 [Prep GEN]
Steps to a migration to victory from 23.2 to 23.3
To get the latest product versions, please use now the VidiNetLayer and proceed to update the system.
If you want to use the VPA - please see further information under VPA.
Please proceed with updating the system by using sudo ./prepared.sh playbook install-products.yml --tags=
.
ENV
AS
VC
Please note that vidispine-server-agent is now called vidicore-agent (This needs to be changed in the inventory)
CP
VF
Please note these changes for camunda.
By default the “old” workflow monitor will be used. If you want to change it towards the new workflow monitor, you can change it as describe here.
Update remaining products by using these tags: VS, MP, VE, ML.
VTR
If you have used one of the following events [chunkChanged, vidicoreItemCreated, chunkStatusChanged] please use the following VidiControl Migration 23.3 [Prep GEN]
Make sure to add additional values for the router ie:
- CODE
swp08router: devicesettings: "{\\\"RouterStatusCheckerIntervalInSeconds\\\":\\\"0\\\",\\\"RouterLevelsToSwitch\\\":\\\"0\\\",\\\"RouterMatrix\\\":1,\\\"RouterLevel\\\":0,\\\"RouterLevelToUse\\\":0,\\\"RouterDeviceId\\\":1,\\\"RouterDeviceName\\\":\\\"SWP08Router\\\",\\\"RouterUseExtendedMsgs\\\":true,\\\"RouterIpAdress\\\":\\\"10.231.17.220\\\",\\\"RouterPort\\\":\\\"2020\\\"}"
Update IDX and OBS after updating the products to 23.3
Updating OpenSearch to 2.7
On AWS OpenSearch is running as managed service so the service need to be migrated inside AWS.
Non managed service for OpenSearch - please refer to this.
PREPARED changes:
Kubernetes module
Please enable the kubernetes module in your prepared.cfg or do.
sudo ./prepared.sh config enable-module kubernetes
Version Layer
From 23.3 onwards, you can use a version layer that contains all release and approved product version. In order to implement it, please use the following changes in your layers.yml (layer in prepared):
layers:
versions:
origin: oci://buildserver:Buildserver2020@cr.vidinet.net/prepared/layers/vidinet-versions:23.3.0
VPA
VerticalPodAutoscaler is now part of PREPARED. You can find some internally or online to activate it for specific pods.
FluentD
FluentD is now handling datastream (https://opensearch.org/docs/latest/opensearch/data-streams/)
create new index pattern; manually or via update of default dashboard
change fluentd-target in wf-monitor configmap
check ttl of ds index
saved saved searches in fluentd-index won´t work anymore - need (manual) migration
OpenSearch changes
OS should be now updated to OS 2.7:
VidiFlow changes:
Camunda
Camunda is now part of CORE-SERVICES and not a standalone helm chart. Please refere to this documentation: VidiFlow Migration 23.3 [Prep GEN]
Example:
vidiflow-core-services:
helm_chart:
chart_values:
hull:
config:
general:
data:
installation:
config:
debug:
ignoreEntityRestCallErrors: true
retriesForEntityRestCall: 1
retriesForAuthServiceCall: 2
camunda:
hull:
objects:
deployment:
engine:
replicas: 2
VidiCore changes
VidispineServerAgent is now called VidicoreAgent so please consider this changes are required in you local inventory ie:
vidicore-agent:
helm_chart:
chart_values:
hull:
config:
specific:
components:
vidicore-agent:
custom:
transcoderMaxJobs: 20
objects:
statefulset:
vidicore-agent:
replicas: 2
pod:
containers:
vidicore-agent:
resources:
limits:
cpu: 4
memory: 12Gi
requests:
cpu: 4
memory: 12Gi