OpenCHAMI Quickstart Guide

For the most up-to-date instructions on deploying OpenCHAMI, follow the OpenCHAMI Tutorial. It provides step-by-step guidance for setting up OpenCHAMI in a controlled environment using Podman Quadlets.

Happy HPC!

Start OpenCHAMI Services#

The OpenCHAMI Tutorial provides the most current and detailed instructions for deploying OpenCHAMI. Follow the tutorial to set up your environment and start the services using Podman Quadlets and the Release RPM.

Dependencies and Assumptions#

The OpenCHAMI Tutorial uses Podman Quadlets for container management and is tested on Rocky Linux 9 with x86 processors.

For Docker Compose deployments (legacy), the OpenCHAMI services are containerized and tested running under docker compose. See the deployment-recipes repository for details (not recommended for new users).

Assumptions#

See the OpenCHAMI Tutorial for current system requirements and assumptions.

Dependencies#

See the OpenCHAMI Tutorial for current dependencies and installation instructions.

What’s next#

Now that you know where to find the current OpenCHAMI deployment instructions, explore the tutorial and related guides.

Helpful references#

For Docker Compose deployments (legacy), this quickstart uses docker compose to start up services and define dependencies. If you have a basic understanding of Docker, you should be able to work with the included services. Some handy items to remember for when you are exploring the deployment are below.

• docker volume list This lists all the volumes. If they exist, the project will try to reuse them. That might not be what you want.
• docker network list ditto for networks.
• docker ps -a the -a shows you containers that aren’t running. We have several containers that are designed to do their thing and then exit.
• docker logs <container-id> allows you to check the logs of containers even after they have exited
• docker compose ... down --volumes will not only bring down all the services, but also delete the volumes
• docker compose -f <file.yml> -f <file.yml> restart <service-name> will restart one of the services in the specified compose file(s) without restarting everything. This is particularly useful when changing configuration files.