Create Blog “llm-agentic-tool-mesh-orchestrating-agentic-tools-for-the-next-revolution” #2879
Conversation
…e-next-revolution”
…e-next-revolution”
…e-next-revolution”
…e-next-revolution”
✅ Deploy Preview for hpe-dev-portal ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
…e-next-revolution”
There was a problem hiding this comment.
Hi Antonio,
Thank you so much for your new contribution!!
This is again a great blog post.
Just added some "cosmetic" suggestions for you to consider if you think they make sense for you.
Dale will go through the editorial review when time permits.
Thanks again!
Denis
content/blog/llm-agentic-tool-mesh-orchestrating-agentic-tools-for-the-next-revolution.md
Outdated
Show resolved
Hide resolved
content/blog/llm-agentic-tool-mesh-orchestrating-agentic-tools-for-the-next-revolution.md
Outdated
Show resolved
Hide resolved
content/blog/llm-agentic-tool-mesh-orchestrating-agentic-tools-for-the-next-revolution.md
Outdated
Show resolved
Hide resolved
content/blog/llm-agentic-tool-mesh-orchestrating-agentic-tools-for-the-next-revolution.md
Outdated
Show resolved
Hide resolved
content/blog/llm-agentic-tool-mesh-orchestrating-agentic-tools-for-the-next-revolution.md
Outdated
Show resolved
Hide resolved
content/blog/llm-agentic-tool-mesh-orchestrating-agentic-tools-for-the-next-revolution.md
Outdated
Show resolved
Hide resolved
content/blog/llm-agentic-tool-mesh-orchestrating-agentic-tools-for-the-next-revolution.md
Outdated
Show resolved
Hide resolved
content/blog/llm-agentic-tool-mesh-orchestrating-agentic-tools-for-the-next-revolution.md
Show resolved
Hide resolved
content/blog/llm-agentic-tool-mesh-orchestrating-agentic-tools-for-the-next-revolution.md
Show resolved
Hide resolved
…e-next-revolution”
|
Thanks Denis, I've just updated the blog post following your suggestion |
| @@ -0,0 +1,193 @@ | |||
| --- | |||
| title: "LLM Agentic Tool Mesh: Orchestrating agentic tools for the next revolution" | |||
There was a problem hiding this comment.
Hi, Antonio,
I was wondering if maybe you could change "next" to "AI" revolution. Is it too late to do that?
| } | ||
| </style> | ||
|
|
||
| In our previous blog posts, we delved into the [Chat Service](https://developer.hpe.com/blog/ll-mesh-exploring-chat-service-and-factory-design-pattern/), [Agent Service](https://developer.hpe.com/blog/llm-agentic-tool-mesh-harnessing-agent-services-and-multi-agent-ai-for-next-level-gen-ai/), and [RAG Service](https://developer.hpe.com/blog/llm-agentic-tool-mesh-empowering-gen-ai-with-retrieval-augmented-generation-rag/) of [LLM Agentic Tool Mesh open source project](https://github.com/HewlettPackard/llmesh). Today, we'll explore the System Services of LLM Agentic Tool Mesh that are essential for managing and orchestrating the mesh of agentic tools. |
There was a problem hiding this comment.
Change: System Services of LLM Agentic Tool Mesh that are essential
To: System Services of LLM Agentic Tool Mesh**, which** are essential
Also, I was going to assume throughout this blog post that "System Services" is the formal name, just like "Chat Service", "Agent Service", "RAG Service", etc.
However, as I read a little further down, I see that the term "System Services" really refers more to a set of services that have their own names: Tool Client Service and Tool Server Service.
Given that, I would recommend (unless you feel strongly otherwise) that you refer to "System Services" as "system services" throughout this blog post (title and everything). In doing so, you would indicate that there are a set of services under that umbrella and the reference would be grammatically correct and Brand compliant.
|
|
||
| In our previous blog posts, we delved into the [Chat Service](https://developer.hpe.com/blog/ll-mesh-exploring-chat-service-and-factory-design-pattern/), [Agent Service](https://developer.hpe.com/blog/llm-agentic-tool-mesh-harnessing-agent-services-and-multi-agent-ai-for-next-level-gen-ai/), and [RAG Service](https://developer.hpe.com/blog/llm-agentic-tool-mesh-empowering-gen-ai-with-retrieval-augmented-generation-rag/) of [LLM Agentic Tool Mesh open source project](https://github.com/HewlettPackard/llmesh). Today, we'll explore the System Services of LLM Agentic Tool Mesh that are essential for managing and orchestrating the mesh of agentic tools. | ||
|
|
||
| We'll provide insights into these services, showcase an example of a Mesh available in the repository, discuss federated governance, and share our vision for the future evolution of the LLM Agentic Tool Mesh project. |
There was a problem hiding this comment.
I just noticed that, in your previous blog post, I didn't call you out on this, but I did in some of your earlier blog posts.
Please try to avoid the "Royal We" and say something like "In my previous blog posts, I dove into", "Today, I'll explore the", "I'll provide insights into", etc.
|
|
||
|  | ||
|
|
||
| # Understanding the System Services |
There was a problem hiding this comment.
Per my comment at the top, since we are talking about a set of system services, which is a more general term and not the specific "name" of a product or offering, I would change this to sentence case: Understanding the system services
Unless your group has specifically "named" this as such, but honestly, if you did, it would create more confusion.
|
|
||
| # Understanding the System Services | ||
|
|
||
| The System Services in LLM Agentic Tool Mesh are crucial for the seamless operation and orchestration of agentic tools and web applications. These services ensure consistency, ease of use, and flexibility across the platform. They include: |
There was a problem hiding this comment.
Recommend:
"The system services in LLM Agentic Too Mesh are..."
| **Development panel**: | ||
|
|
||
| * Implemented features: This panel has been partially tackled with the backpanel web app example, which allows users to runtime modify the basic copywriter agentic tool and the RAG tool. | ||
| * Future goals: Add more system services to support development, including real-time LLM tuning and configuration. |
There was a problem hiding this comment.
Similarly, change this to:
Future goals: We aim to add more system services to...
| * Implemented features: This panel has been partially tackled with the backpanel web app example, which allows users to runtime modify the basic copywriter agentic tool and the RAG tool. | ||
| * Future goals: Add more system services to support development, including real-time LLM tuning and configuration. | ||
|
|
||
| **Deployment panel (future)**: |
There was a problem hiding this comment.
You might want to add a sentence above this, similar to the one stated before the two previous panels (Currently, the platform...).
This one could say something like:
In the future, we hope to be able to offer a deployment panel and an experiment panel.
And then get into the subheaders with their bullets.
| **Deployment panel (future)**: | ||
|
|
||
| * Purpose: This panel will focus on deploying the LLM Agentic Tool Mesh tools seamlessly across one or more clusters, enabling large-scale and distributed deployments. | ||
| * Planned features: Tools for monitoring deployed tools, orchestrating distributed systems, and managing deployment pipelines. |
There was a problem hiding this comment.
make it a sentence after the colon:
We hope to offer tools for monitoring...
Whatever you do, be careful to not use language like "We will", "We guarantee", etc. Plans always change and you have to be careful what you "promise" publically.
|
|
||
| **Experiment Panel (Future)**: | ||
|
|
||
| * Purpose: Designed for tracking and managing experiments to optimize LLM tool performance and suitability. |
There was a problem hiding this comment.
Now it's the first bullet that needs to be made into a sentence :-)
This panel will be designed to track and manage experiments to...
|
|
||
| # Our mission ahead | ||
|
|
||
| As LLM Agentic Tool Mesh evolves, we aim to continue enhancing the platform by enriching existing services, especially in the user panel, and expanding the development panel with more robust system services. The addition of the deployment panel and experiment panel will complete the platform's vision, enabling a fully integrated lifecycle from development to deployment and optimization. |
There was a problem hiding this comment.
The use of "we" in both this paragraph and the one below is entirely appropriate. It's not the "Royal We"... you're merely talking about your group, so no change is required here.
Automatically generated by Netlify CMS