Moving a Model Deployment Between Compartments
Move a Data Science model deployment to a different compartment.
For example, you might want to move a model deployment to promote it from a development compartment to production compartment, or to change the visibility of the model.
A notification is displayed indicating that the model deployment resource is moved to the new compartment successfully. You might notice the status change to Moving. After the move is completed successfully, the status changes back to Active. Use the oci data-science model-deployment change-compartment command and required parameters to change the compartment:
oci data-science model-deployment change-compartment --compartment-id
<compartment-id>
.-c [<text>] --model-deployment-id [<text>] .. [OPTIONS]For a complete list of flags and variable options for CLI commands, see the CLI Command Reference.
Use the ChangeModelDeploymentCompartment operation to change the compartment for the model deployment.
Impact of the Change Compartment Operation
From the public metrics' perspective, the change compartment opreation has no functional
changes. When the deployment is moved to a different compartment, the metrics are moved to the
newer compartment, too. So if you have alarms defined based on these metrics such as
CPUUtilization
, update the alarms with the new compartment. This update can
be made after the change.
Regarding OCI Logging, the logs might reside in a compartment different than the model deployment resource compartment. So, as long as the log groups' compartment is unchanged, no changes are required.
If policies are associated with a subcompartment, update the policies for CRUD and predict call operations if those policies are to continue making a successful call. Make the policy update to reflect the new compartment. For more information on policies, see Manage Model Deployment Policies.