Hive-CLI

Hive-CLI is a command-line interface for managing and deploying the Hive agent and experiments on Kubernetes and other platforms.

     ███          █████   █████  ███
    ░░░███       ░░███   ░░███  ░░░
      ░░░███      ░███    ░███  ████  █████ █████  ██████
        ░░░███    ░███████████ ░░███ ░░███ ░░███  ███░░███
         ███░     ░███░░░░░███  ░███  ░███  ░███ ░███████
       ███░       ░███    ░███  ░███  ░░███ ███  ░███░░░
     ███░         █████   █████ █████  ░░█████   ░░██████
    ░░░          ░░░░░   ░░░░░ ░░░░░    ░░░░░     ░░░░░░

Installation

Pre-requisites

• Python 3.8 or higher
• docker for image building.
• gcloud CLI via brew install gcloud for authentication.

Notes:

• Make sure to enable the ✅ Use containerd for pulling and storing images option in Docker Desktop settings, which is required for multi-arch image support.

Install via pip

pip install hiverge-cli==0.2.2

Install from source

source start.sh

How to run

Note: Hive-CLI reads the configuration from a yaml file, by default it will look for the ~/.hive/sandbox-config.yaml. You can also specify a different configuration file using the -f option. Refer to the config.yaml for examples.

Below we assume that you have a ~/.hive/sandbox-config.yaml file.

Edit the experiment

Edit command will open the configuration file in your default editor (e.g., vim, nano, etc.) for you to modify the experiment configuration. You can also specify a different editor using the EDITOR environment variable, by default it will use vim.

hive edit config

Create an experiment

hive create exp my-experiment

Note: This will build a Docker image for the experiment and push it to the container registry which may take some time, based on the Dockerfile and network speed. You can enable the Debug mode in the configuration file to see more detailed logs.

List experiments

hive show exps

Visit Dashboard

hive dashboard

Delete an experiment

hive delete exp my-experiment

More

See hive -h for more details.

Development

Debugging

Change the log_level in the configuration file to DEBUG to see more detailed logs.