#minimal harvest installation

1 messages · Page 1 of 1 (latest)

proud schooner
#

we have prometheus and graphana installed, how can we integrate harvest installation with our existing installations,,,?

#

I've installed harvest on a host from rpm, what's next?

compact pond
proud schooner
#

Hi @compact pond
Thanks, I went through the docs and I've managed to get it up and running - contenerized harvest and external prometheus/graphana. Not sure if I shouldn't be running harvest as a service on linux though.
ps . Verify Dashboards in Grafana should have number 11 😉

compact pond
proud schooner
#

@compact pond I've been playing with podman images for harvest and cut down to only to pollers as we have external graphana and prometheus installations, but I've not found on harvest documentation how to run podman containeres permanent, so I figured out that harvest.service can be run with docker compose

[Unit]
Description=NetApp Harvest Service
After=network-online.target

[Service]
User=root
Restart=on-failure
ExecStart=/usr/local/bin/docker-compose -f /path/to/harvest-compose.yml up -d --remove-orphans

[Install]
WantedBy=multi-user.target

what do you think about this solution, it generally works
ps I've tried to create services for containers with podman generate but this didn't work out

compact pond
#

hi @proud schooner I've not followed podman super closely, but I think they moved to quadlets for this type of functionality

#

I think podman generate systemd is deprecated so maybe it will still work

#

In terms of what I would recommend, it really depends on what you're wanting to achieve. The reason Harvest has a bin/harvest generate docker command is a convenience to make your harvest.yml file a single source of truth. The idea is you can add/remove pollers there, and then run generate to create a compose file. That compose file can be converted to k8 resources, quadlets or whatever. Some folks prefer to edit their compose by hand and copy/paste one of the exiting poller blocks as needed

proud schooner
#

Yes, podman generate warns about that it is deprecated. I'm using entrypoint "bin/harvest" to create harvest-compose.yaml, what I meant that Podman containers are ephemeral and do not restart automatically upon system reboot, and this is what I wanted to achieve what the above service does. Cheers

compact pond
compact pond
#

@proud schooner have you had a chance to try the above yet?