Implement deploy

[sameehj]

Deploy was planned and is mentioned in the Tutorial but hasn't been added as a tool and we need to add it.

This issue is for tracking it.

[Ekleen123]

Hi @sameehj, I’m beginner interested in working on this deploy tool. Could you please provide more details or point me to the tutorial you mentioned? I want to understand what exactly the deploy tool should do. Thanks!

[sameehj]

Implemented, renamed and plit to load_program and attach_program. currently still trying to make it work

[sameehj]

Hi @sameehj, I’m beginner interested in working on this deploy tool. Could you please provide more details or point me to the tutorial you mentioned? I want to understand what exactly the deploy tool should do. Thanks!

Wooh! @Ekleen123 somehow I missed your comment. Would love to get you started on the project.

[sameehj]

Currently I changed the tools a bit, check the latest README.md and docs/schema.json for the latest tools shcema. I tried to define the tools in such way that they will be minimal with maximum Flexibility.

Thus mimicking the kernel API with the tools and thus split deploy into load_program and attach_program

We need to make sure the tools are working in all scenarios

for example the load_program can load url of .c ebpf kernel file or .o in base64 maybe also asm? not sure but this level of flexibility I believe is gonna make the usability great. Ofcourse this can also make it overwhelming maybe, but giving many ways to get it right for the llm, will make it's chance of successful execution high.

so you can go ahead and test the load_program and attach_program

ALSO I have opened new tickets for supporting the mcp-resources and mcp-prompts which we don't support yet but are part of the standard and part of mcp-go.