H2O-3 OSS is designed for self-managed production and therefore places every operational responsibility on your internal teams:
SLAs, incident response, and remediation timelines
Commercial CVE patching & long-term support
Model lineage and audit evidence
Supportability documentation for auditors and regulators
Audit-supporting capabilities (SOC 2, ISO 27001, ISO 42001)
H2O-3 Secure is the commercially supported upgrade for enterprises running audit-sensitive AI/ML in production. Keep everything you have: same code, APIs and pipelines run unchanged.
2. Install dependencies (prepending with `sudo` if needed):
pip install requests
pip install tabulate
Optional: install `matplotlib` (required for plotting in Python):
pip install matplotlib
By default, this setup is open. If you want to secure your installation, follow the Security Guidelines.
At the command line, copy and paste these commands one line at a time:
# The following command removes the H2O module for Python.
pip uninstall h2o
# Next, use pip to install this version of the H2O Python module.
pip install /Python/h2o-3.46.0.11-py2.py3-none-any.whl
Conda Installation
Available at https://anaconda.org/h2oai/h2o/
To install this package with conda run:
conda install -c h2oai h2o
Use H2O directly from R
By default, this setup is open. If you want to secure your installation, follow the Security Guidelines.
Copy and paste these commands into R one line at a time:
# The following two commands remove any previously installed H2O packages for R.
if ("package:h2o" %in% search()) { detach("package:h2o", unload=TRUE) }
if ("h2o" %in% rownames(installed.packages())) { remove.packages("h2o") }
# Next, we download packages that H2O depends on.
pkgs <- c("RCurl","jsonlite")
for (pkg in pkgs) {
if (! (pkg %in% rownames(installed.packages()))) { install.packages(pkg) }
}
# Now we download, install and initialize the H2O package for R.
install.packages("h2o", type="source", repos="/R")
# Finally, let's load H2O and start up an H2O cluster
library(h2o)
h2o.init()
Run H2O on Hadoop in just 3 steps
NOW AVAILABLE: H2O-3 Secure FOR PRODUCTION AI/ML
H2O-3 OSS is designed for self-managed production and therefore places every operational responsibility on your internal teams:
SLAs, incident response, and remediation timelines
Commercial CVE patching & long-term support
Model lineage and audit evidence
Supportability documentation for auditors and regulators
Audit-supporting capabilities (SOC 2, ISO 27001, ISO 42001)
H2O-3 Secure is the commercially supported upgrade for enterprises running audit-sensitive AI/ML in production. Keep everything you have: same code, APIs and pipelines run unchanged.
1. Download H2O for your version of Hadoop. This is a zip file that contains everything you need to get started.
2. Unpack the zip file and launch a 6g instance of H2O:
unzip h2o-3.46.0.11-*.zip
cd h2o-3.46.0.11-*
hadoop jar h2odriver.jar -nodes 1 -mapperXmx 6g
3. Point your browser to H2O (see "Open H2O Flow in your web browser" in the output below):
Determining driver host interface for mapper->driver callback...
[Possible callback IP address: 172.16.2.181]
[Possible callback IP address: 127.0.0.1]
...
Waiting for H2O cluster to come up...
H2O node 172.16.2.188:54321 requested flatfile
Sending flatfiles to nodes...
[Sending flatfile to node 172.16.2.188:54321]
H2O node 172.16.2.188:54321 reports H2O cluster size 1
H2O cluster (1 nodes) is up
(Note: Use the -disown option to exit the driver after cluster formation)
Open H2O Flow in your web browser: http://172.16.2.188:54321
(Press Ctrl-C to kill the cluster)
Blocking until the H2O cluster shuts down...
H2O-3 OSS is designed for self-managed production and therefore places every operational responsibility on your internal teams:
SLAs, incident response, and remediation timelines
Commercial CVE patching & long-term support
Model lineage and audit evidence
Supportability documentation for auditors and regulators
Audit-supporting capabilities (SOC 2, ISO 27001, ISO 42001)
H2O-3 Secure is the commercially supported upgrade for enterprises running audit-sensitive AI/ML in production. Keep everything you have: same code, APIs and pipelines run unchanged.
Helm can be used to deploy H2O into a kubernetes cluster. Helm requires the KUBECONFIG environment variable to be set up properly, or stating the kubeconfig destination explicitly. Please refer to Helm's documentation
for further information.
There are various settings and modifications available. To inspect the configuration options available, use the "helm inspect values h2o/h2o --version 3.46.0.11" command.
Setup H2O on Kubernetes with kubectl
1. Set-up kubernetes cluster and kubectl.
2. (Optional) Adjust the 'default' namespace in the following YAML, if required.
H2O_KUBERNETES_SERVICE_DNS - [MANDATORY] Crucial for the clustering to work. The format usually follows the {service-name}.{project-name}.svc.cluster.local pattern. This setting enables H2O node discovery via DNS. It must be modified to match the name of the headless service created. Also, pay attention to the rest of the address to match the specifics of your Kubernetes implementation.
H2O_NODE_LOOKUP_TIMEOUT - [OPTIONAL] Node lookup constraint. Time before the node lookup is ended.
H2O_NODE_EXPECTED_COUNT - [OPTIONAL] Node lookup constraint. Expected number of H2O pods to be discovered.
H2O_KUBERNETES_API_PORT - [OPTIONAL] Port for Kubernetes API checks and probes to listen on. Defaults to 8080.
3. Issue "kubectl apply -f filename.yaml" to deploy H2O into Kubernetes.
4. (Optional) Adjust the YAML file to spawn more nodes or allocate more resources for the H2O cluster.
A lightweight assembly jar with minimum dependencies