This commit adds the missing closing bracket to the ai-frontend.nomad job definition. The file was incomplete without this bracket, which is necessary for the proper structure of the Nomad job configuration. This change ensures the job definition is correctly formatted and will be parsed properly by the Nomad service.
Adds a new `lobechat` group and task to the `ai-frontend.nomad` job file.
This change introduces the LobeChat AI frontend application, running in a Podman container, alongside the existing OpenWebUI service. It's configured to connect to an Ollama instance via Consul service discovery.
The new `lobechat` service is registered in Consul but does not include Traefik tags, meaning it's not immediately exposed via the Traefik ingress controller. It's constrained to run on the `hp1-home` host.
The `ollama` service in the `ai-backend` Nomad job has been updated to use `address_mode = "host"`. This ensures the service is registered with the host's IP address in Consul, allowing external proxies like Traefik to correctly route traffic. This change resolves potential connectivity issues by making the service directly accessible via the host network.
Adds the `traefik.enable=true` tag to the `ollama` service definition within the `ai-backend` Nomad job.
This enables Traefik to automatically discover and route incoming requests to the Ollama service, making it accessible through the Traefik ingress.
The `OLLAMA_HOST` environment variable in the `ai-backend` Nomad job has been updated from `0.0.0.0` to `0.0.0.0:11434`.
This change ensures OLLAMA explicitly binds to the correct address and port, preventing potential connectivity issues or misconfigurations where the port might be omitted or incorrectly inferred.
Removed the `lobechat` group and its associated configuration from `stacks/ai/ai-frontend.nomad` as this application is no longer required.
Updated the `OLLAMA_BASE_URL` for the `ai-frontend` (OpenWebUI) task to use the concise `ollama` service name (`http://ollama:11434`). This leverages Nomad's built-in service discovery more efficiently, simplifying the URL from `http://ollama.service.consul:11434`.
Additionally, the `memory` allocation for the `ai-frontend` task was increased from `1024` to `4000` to provide more stable resources for the OpenWebUI application.
Moves DNS server and search domain configuration from task `config` blocks to the job/group `network` blocks for `ai-frontend` (OpenWebUI) and `lobechat`.
This refactoring centralizes DNS settings for all tasks within a Nomad job or group, ensuring consistent DNS resolution and aligning with recommended Nomad configuration patterns.
Corrected the LobeChat service health check path from `/api/health` to `/` as the root endpoint is the correct health indicator. This resolves an issue where the service was not being properly marked as healthy by Nomad.
Additionally, this commit refactors comments across both `ai-frontend` (OpenWebUI) and `lobechat` jobs within the `ai-frontend.nomad` file. Redundant or outdated comments regarding DNS "reverts," version pinning, and security notes have been removed or simplified to improve readability and reflect the stable state of the configurations. The Consul DNS configuration is now consistently marked as a "DNS Fix" rather than a temporary solution.
This commit addresses service discovery issues by explicitly configuring Consul DNS for the `openwebui` and `lobechat` tasks within the `ai-frontend` job.
Previously, services were unable to reliably resolve `ollama.service.consul`. This is resolved by:
* Setting `dns_servers` to the Consul server IP (`192.168.1.133`).
* Setting `dns_search` to `service.consul`.
* Reverting `OLLAMA_BASE_URL` and `OLLAMA_PROXY_URL` environment variables to use `ollama.service.consul` as intended.
* The `lobechat` task's image is now pinned to `v1.143.0` for improved stability.
* Removed outdated comments regarding host pinning.
Updates the hostname constraint in the `ai-frontend` Nomad job from `hp-mini-1` to `hp1-home` for both `openwebui` and `lobechat` tasks. This correction ensures the services are pinned to the accurate target host.
Removed outdated `FIXED:` comments for cleanup.
* Reformatted the `resources` block for the `openwebui` group to a multi-line format to resolve an illegal semicolon syntax issue.
* Added explicit comments to both `openwebui` and `lobechat` groups to clarify the host pinning constraint.
* Streamlined comments in the `lobechat` group's `resources` block to concisely state the memory allocation, removing outdated "fix" comments and adding a current "FIXED" comment.
These changes enhance the readability, maintainability, and correctness of the Nomad job definition.
This commit addresses several issues and updates in the `ai-frontend.nomad` job configuration:
- **LobeChat OOM Fix**: Increased `lobechat` service memory allocation from 512MB to 1024MB to prevent out-of-memory crashes and improve stability.
- **Node Constraint Update**: Updated the `attr.unique.hostname` constraint for both `openwebui` and `lobechat` groups from `hp1-home` to `hp-mini-1` to reflect the correct node hostname.
- **Static Port Assignment**: Explicitly added `static` port definitions for `http` in both `openwebui` (8080) and `lobechat` (3210) services to ensure consistent port binding.
- **Minor Housekeeping**: Cleaned up comments and formatted resource blocks for better readability.
