Skip to main content
Version: v1.3.0

Deploy a model to H2O MLOps (through the H2O Hydrogen Torch UI)

Overview​

After building an H2O Hydrogen Torch model, you can deploy it to H2O MLOps utilizing the H2O Hydrogen Torch user interface (UI).

note

With a model's H2O MLOps pipeline, you can deploy a built model to H2O MLOps. To learn more, see Download an experiment's H2O MLOps pipeline

Instructions​

Deploy a model​

To deploy a built model (experiment) to H2O MLOps utilizing the H2O Hydrogen Torch UI, consider the following instructions:

  1. In the H2O Hydrogen Torch navigation menu, click View experiments.
  2. Click the name of the experiment (model) you want to depoy to H2O MLOps.
  3. Click the Deployments tab.
  4. In the Project box, select or enter an H2O MLOps project.
    note
    • If a project does not exist in H2O MLOps, H2O Hydrogen Torch creates a new project named HT, which can be utilized.
    • You can enter a non-existing project name that creates a new project to deploy the model.
  5. In the Environment list, select an environment to deploy the built model.
  6. (Optional) Click the GPU deployment toggle.
  7. In the Runtime list, select a runtime to deploy the built model.
  8. Click Deploy.
note

After the deployed model achieves a HEALTHY status (the deployment is alive and healthy), you can view certain deployment pieces of information (for example, Endpoint URL). To view the deployed model's details, consider the following instructions:

  1. In the List of deployments table (card), select the deployed model you want to view its deployment details.
note
  • To learn about the different deployment states a model can be in, see States.
  • To learn about the available deployment details of a deployed model, see Deployment details.

H2O MLOps: Deployment settings​

H2O Hydrogen Torch offers several H2O MLOps deployment settings to deploy an H2O Hydrogen Torch model to H2O MLOps quickly. Available settings are described below.

Project​

Defines the H2O MLOps project to deploy (store) the built H2O Hydrogen Torch model. To learn more about H2O MLOps projects, see Understand projects in H2O MLOps.

GPU deployment​

Determines whether to deploy the built model on GPUs.

note

CPU deployments are often sufficient and less demanding on resources.

Environment​

Defines the target deployment environment H2O MLOps utilizes to deploy the built H2O Hydrogen Torch model. To learn more about H2O MLOps deployments, see Understand deployments in H2O MLOps.

Runtime​

Defines the runtime H2O MLOps utilizes to deploy the built H2O Hydrogen Torch model. To learn more about supported runtimes, see Runtime names mapping.

note

Runtimes supporting H2O Hydrogen Torch models follow the following naming convention: python-scorer_hydrogen_torch-*. For example, python-scorer_hydrogen_torch_gpu_38_130, 38 refers to Python 3.8, while 130 refers to v1.3.0 (the version of H2O Hydrogen Torch). Accordingly, H2O Hydrogen Torch models are version dependent when deploying to H2O MOLops; in other words, a built model in H2O Hydrogen Torch v1.3.0 requires a runtime ending in _130 (for example, python-scorer_hydrogen_torch_gpu_38_130).

Requests/Limits​

Defines the amount of resources H2O MLOps utilizes for the deployment.

  • Requests: Resource requests determine the amount of resources the deployment asks Kubernetes to provide. For example, if a replica requests 256Mi of memory, Kubernetes schedules the deployment on any node with enough memory to satisfy the stated requirement.
  • Limits: Resource limits determine the maximum available resources for deployment. If a deployment exceeds a limit on the amount of memory allocated, the deployment is restarted. Note that the deployment does not restart if it exceeds a CPU limit.
note
  • To add additional fields for any existing custom resources that an admin has set up in your Kubernetes cluster, consider the following instructions:
    1. Click Add row.
  • The resource requests and limits fields must be defined using the quantity suffixes used in Kubernetes. The default values for Memory and CPU requests are 256Mi and 100m, respectively. For more information, see Resource units in Kubernetes.
  • By default, resources are not limited.
  • When specifying custom resources, the pod cannot be scheduled if Kubernetes cannot satisfy the stated custom value(s).
  • For more information on resource requests and limits in Kubernetes, see Resource Management for Pods and Containers.

Access all H2O MLOps deployment settings​

By default, H2O Hydrogen Torch only displays specific H2O MLOps deployment settings (for example, Project, Environment, GPU deployment, etc.).

You can access other H2O MLOps deployment settings (for example, deployment limits). To access other (non-default) H2O MLOps deployment settings, consider the following instructions:

  1. In H2O Hydrogen Torch navigation menu, click Settings
  2. Click the Allow custom MLOps limits toggle.
  3. Click Save settings persistently.
Feedback