How to Update Models
Our product in the Full API version is delivered in two ways:
via Helm charts,
via Docker Compose.
For Instant API, models are not updated. Instead, a new Instant API image is released and delivered.
Kubernetes installations (delivery via Helm charts)
Support engineers notify the client of a new model version through the relevant communication channel.
The client confirms they are ready to update the model version and specifies a suitable time for the work. The client coordinates with their information security team and management on their own.
An engineer prepares the update for the corresponding client environment (DEV or PROD) via the
Oz-Bio-Adminservice.
Our oz-k8s-bio-updater service on the client side polls our https://bio-admin.infra.ozforensics.com service on its own. For this, the client must allow access to the following resources:
https://*.infra.ozforensics.ai/https://*.infra.ozforensics.comhttps://*.s3.amazonaws.com/https://*.s3-accelerate.amazonaws.com/
If the oz-k8s-bio-updater service detects an update, it downloads and unpacks the full set of models to its PVC. The client can monitor this process via the oz-k8s-bio-updater StatefulSet log.
The update takes effect only after all oz-k8s-bio pods are restarted manually. For example, via kubectl:
kubectl -n oz-namespace rollout restart deployment oz-k8s-bioor via the ArgoCD GitOps tool:
To check that the update was successful, run curl on any oz-k8s-bio pod of the Kubernetes cluster:
Example response showing the inquisitor_c model and its current version:

The update is considered successful only after the client confirms that the model version has been updated.
Docker installations (delivery via Docker Compose)
Support engineers notify the client of a new model version through the relevant communication channel.
The client confirms they are ready to update the model version and specifies a suitable time for the work. The client coordinates with their information security team and management on their own.
An engineer prepares the update for the corresponding client environment (DEV or PROD) via the Oz-Bio-Admin service.
The oz-bio-updater container on the client side checks our https://bio-admin.infra.ozforensics.com service for new model updates on its own. For this, the client must allow access to the following resources:
https://*.infra.ozforensics.ai/https://*.infra.ozforensics.comhttps://*.s3.amazonaws.com/https://*.s3-accelerate.amazonaws.com/
If the oz-bio-updater container detects an update, it downloads and unpacks the full set of models. The client can monitor this process via the container log.
Example command:
To apply the update, take the oz-bio containers out of load balancing one by one manually and restart them. Example command for an installation without a load balancer:
You can monitor the container restart via its log.
To check the current model version, run curl inside the oz-bio container:
Example of a successful response:

The update is considered successful only after the client confirms that the model version has been updated.
Last updated
Was this helpful?
