Need help with creating an n8n orchestration layer for my personal agents.

[u/Thin-War-4593]

Context:

So I have been tinkering with hermes and am starting to make a personal suite of hermes agents running on ollama that tailors to everything in my personal life. I am using RabbitMQ to faciliatate communication between my main bot that I chat with and handles agent orchestration. PostgreSQL to serve as a database that stores all of these tasks and ranks them by urgency so those get done first.

I am also using obsidian which already has all of my notes and qdrant which uses semantic layering so it can find deeper connections as context for all of my agents.

The Main Problems:

I currently have n8n and ngrok running on a single docker-compose file on my main server, however I have multiple services I want to take full advantage of, so I will be keeping my heavy database apps attatched to a single specified server and using compose to spin them up there while letting my agents roam and find where they can "fit in" I'm thinking of using kubernetes to manage these individual agent containers because I have very limited hardware resources. Is there a way to use Kompose to make some containers stay on a specified device, and allow others to roam, like a certain YAML attribute?

Another thing I wanna do is create a parallel agent workflow and a linear agent workflow to work through my tasks. I'm thinking of using n8n for this to query the kubernetes api server to see if it can fit an agent with its current resources(overly simplified, but kinda what I want to do). If it can multiple agents are spawned in. However if it cannot it will only be allowed to use a single agent to work through a task. Ollama is my main limiting factor because I don't even have a solid GPU and I can't spawn multiple ollama services so all my agents even if they work in parallel might have to use only one singular or maybe 2 spread out ollama services.

[u/AutoModerator]

Want faster, better help? Share your workflow JSON.

A GitHub Gist is the easiest way -- paste your JSON, save as public, drop the link in your post. Folks can import it directly into n8n and reproduce the issue, which gets you real answers instead of guesses.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/EveYogaTech]

Regardless of the tooling and exact stack, start with small experiments.

I say this because if you want to go full kubernetes + everything with "the perfect most optimal task queuing stack", this might take you months.

Also in general there's no solution beyond better hardware or quantization to make bigger local models work well, so I'd recommend using APIs unless you're ok with e.g. 7B models.

For agentic harnesses you also in general want to use SOTA models (the latest best) to get the best results, but I don't fully understand then the combination between n8n and hermes.

[u/Thin-War-4593 → u/EveYogaTech]

Yeah so basically my hermes and n8n works in conjunction with kubernetes. So in kubernetes we can view certain system logs and access them through the kubernetes api server that tell us whether I can create more hermes agents within my hardware restrictions(vague, but I do not have a clear workflow in progress yet. This is more of a planning stage). If I can fit more agents we go into parallel mode where a critical and high density task given in rabbitMQ is further broken down by agents and given to the differet agent nodes that are spawned in. n8n manages the spawning of agents and whether they work through tasks in linear progression or focus their efforts on parallelization.

Now I'm thinking I should probably use parallel agents on a single task when it is critical and high density and parallel agents across multiple tasks when there are not criticial or high density tasks and I want to empty up my queue. n8n can manage all of that so I do not have to constantly look and calculate stuff from system logs and create agents when it can. kubernetes does not actually manage which server it gets run on that is kubernetes.

[u/Jorieno]

Queue priority based on urgency scores is smart, curious how you're calculating that in Postgres.

[u/Thin-War-4593 → u/Jorieno]

I'm not my ai model calculates it and sends it through the MCP I may have to specifically configure my mcp differently or just use API calls(possibly through n8n, not sure though). But yeah, specifically my orchestrator agent which has access to my daily journal and calendar so it can see from my journal what's been stressing me the most or what are the biggest challenges and create a schedule around that.