.svg?alt=media&token=f31f417e-1743-4ed1-8244-f1ad9a4fd041)
Hydra CLI
Last updated
Was this helpful?
Last updated
Was this helpful?
Hydra CLI is a powerful command line utility designed to manage local development Docker clusters in the Euclid Development Environment. With Hydra CLI, developers can easily create, configure, and manage Constellation Network development clusters for metagraph development.
Hydra CLI is a free and open-source tool that can be easily installed on any operating system that supports bash. Hydra is currently distributed as a part of the and can be found in the scripts directory.
Argc
Copy
Or you can install the directly.
Docker
Ansible is a configuration tool for configuring and deploying to remote hosts
you can check how to install Ansible
jq is a lightweight and flexible command-line JSON processor. It allows you to manipulate JSON data easily, making it ideal for tasks like querying, filtering, and transforming JSON documents.
yq is a powerful command-line YAML processor and parser, similar to jq but for YAML data. It allows you to query, filter, and manipulate YAML documents easily from the command line, making it a handy tool for tasks such as extracting specific data, updating YAML files, and formatting output.
Run the install command which accomplishes two things:
Creates templated currency starter projects for L0 and L1 Currency apps in the source/ directory.
Removes the project's git configuration so that you're free to check your changes into your own repo. Further infrastructure upgrades can be handled through Hydra.
You can import a metagraph template from custom examples by using the following command:
Create a Github personal access token. This token is necessary for building Tessellation from source.
Edit the euclid.json file with your token. You can leave the other variables as default for now.
Build using the Hydra CLI. This will build a minimal development environment for your project using Docker.
The primary purpose of Hydra is to manage local deployment and configuration of development clusters for developing metagraph projects. Running all the necessary network clusters for development can be quite complex to do from scratch, so Hydra aims to simplify that process.
Hydra uses Docker to launch minimal development clusters for the following supported networks:
Global L0
Currency L0
Currency L1
DAG L1
It also includes a pair of monitoring containers supporting:
Prometheus
Grafana
Build the default clusters (Global L0, Currency L0, Currency L1, Monitoring)
To include the DAG L1 network, you can add dag-l1 to the layers field on euclid.json. This option is disabled by default because it is not strictly necessary for metagraph development.
Built containers can be destroyed with the destroy command
Run your built clusters with the start-genesis and start-rollback commands.
Stop running containers with the stop command.
Check the status of all running containers.
Configuring, deploying, and starting remote node instances is supported through Ansible playbooks. The default settings deploy to three node instances via SSH which host all layers of your metagraph project (gL0, mL0, cL1, dL1). Two hydra methods are available to help with the deployment process: hydra remote-deploy and hydra remote-start. Prior to running these methods, remote host information must be configured in infra/ansible/remote/hosts.ansible.yml.
If your file contains a password, you will be prompted to enter it to proceed with remote operations.
To run your metagraph remotely, you'll need remote server instances - 3 instances for the default configuration. These hosts should be running either ubuntu-20.04 or ubuntu-22.04. It's recommended that each host meets the following minimum requirements:
16GB of RAM
8vCPU
160GB of storage
You can choose your preferred platform for hosting your instances, such as AWS or DigitalOcean. After creating your hosts, you'll need to provide the following information in the hosts.ansible.yml file:
Host IP
Host user
Host SSH key (optional if your default SSH token already has access to the remote host)
P12 files contain the public/private key pair identifying each node (peerID) and should be located in the source/p12-files directory by default. The file-name, key-alias, and password should be specified in the euclid.json file under the p12_files section. By default, Euclid comes with three example files: token-key.p12, token-key-1.p12, and token-key-2.p12. NOTE: Before deploying, be sure to replace these example files with your own, as these files are public and their credentials are shared.
NOTE: If deploying to MainNet, ensure that your peerIDs are registered and present on the metagraph seedlist. Otherwise, the metagraph startup will fail because the network will reject the snapshots.
Currently, there are two networks available for running your metagraph: IntegrationNet, and MainNet. You need to specify the network on which your metagraph will run in the euclid.json file under deploy -> network -> name.
NOTE: Your GL0 node must be up and running before deploying your metagraph. You can use the same host to run all four layers: gl0, ml0, cl1, and dl1.
This method configures remote instances with all the necessary dependencies to run a metagraph, including Java, Scala, and required build tools. The Ansible playbook used for this process can be found and edited in infra/ansible/playbooks/deploy.ansible.yml. It also creates all required directories on the remote hosts, and creates or updates metagraph files to match your local Euclid environment. Specifically, it creates the following directories:
code/global-l0
code/metagraph-l0
code/currency-l1
code/data-l1
Each directory will be created with cl-keytool.jar, cl-wallet.jar, and a P12 file for the instance. Additionally, they contain the following:
In code/metagraph-l0:
metagraph-l0.jar // The executable for the mL0 layer
genesis.csv // The initial token balance allocations
genesis.snapshot // The genesis snapshot created locally
genesis.address // The metagraph address created in the genesis snapshot
In code/currency-l1:
currency-l1.jar // The executable for the cL1 layer
In code/data-l1:
data-l1.jar // The executable for the dL1 layer
This method initiates the remote startup of your metagraph in one of the available networks: integrationnet or mainnet. The network should be set in euclid.json under deploy -> network
To begin the remote startup of the metagraph, we utilize the parameters configured in euclid.json (network, gl0_node -> ip, gl0_node -> id, gl0_node -> public_port, ansible -> hosts, and ansible -> playbooks -> start). The startup process unfolds as follows:
Termination of any processes currently running on the metagraph ports, which by default are 7000 for ml0, 8000 for cl1, and 9000 for dl1 (you can change on hosts.ansible.yml).
Relocation of any existing logs to a folder named archived-logs, residing within each layer directory: metagraph-l0, currency-l1, and data-l1.
Initiation of the metagraph-l0 layer, with node-1 designated as the genesis node.
Initial startup as genesis, transitioning to rollback for subsequent executions. To force a genesis startup, utilize the --force_genesis flag with the hydra remote-start command. This will move the current data directory to a folder named archived-data and restart the metagraph from the first snapshot.
Detection of missing files required for layer execution, such as :your_file.p12 and metagraph-l0.jar, triggering an error and halting execution.
Following the initiation of metagraph-l0, the l1 layers, namely currency-l1 and data-l1, are started. These layers only started if present in your project.
After the script completes execution, you can verify if your metagraph is generating snapshots by checking the block explorer of the selected network:
You can verify if the cluster was successfully built by accessing the following URL:
http://{your_host_ip}:{your_layer_port}/cluster/info
Replace:
{your_host_ip}: Provide your host's IP address.
{your_layer_port}: Enter the public port you assigned to each layer.
Each layer directory on every node contains a folder named logs. You can monitor and track your metagraph logs by running:
tail -f logs/app.log
NOTE: Don't forget to add your hosts' information, such as host, user, and SSH key file, to your infra/ansible/remote/hosts.ansible.yml file.
This method will return the status of your remote hosts. You should see the following:
you can check how to install jq
you can check how to install yq
By default, we use the repository. You should provide the template name when running this command. To list the templates available to install, type:
See for details on how to create your token. The token only needs the read:packages permission.
See for an overview of the role each cluster plays in the Hypergraph.
By default, we use the default directory for the SSH file, which is ~/.ssh/id_rsa. However, you can change it to your preferred SSH file directory. You can find instructions on how to generate your SSH file .
Ansible functions more effectively with .pem key files. If you possess a .ppk key file, you can utilize to convert it to .pem.
The deploy script does not deploy the gl0 node. It's recommended to use nodectl to build your gl0 node. Information on installing nodectl can be found . Nodectl helps manage gl0 nodes by providing tools such as auto-upgrade and auto-restart which keep the node online in the case of a disconnection or network upgrade. Using these features is highly recommended for the stability of your metagraph.
Integrationnet:
Mainnet: