Re: Relocation and renaming of meshmodels

[marcus ringblom]

All,

Both first and second parts of this work are complete. Here is a link to the issue epic and details of the changes - https://github.com/meshery/meshery/issues/17904#issuecomment-5009983900

Regards,

Marcus

On Jul 17, 2026, at 10:25 PM, marcus ringblom <marcus....@gmail.com> wrote:

All,

I'm picking up the second half of this outstanding work now. Please expect a new "registry" construct in https://schemas.meshery.io, and a release of meshery/schemas, meshery/meshkit, layer5io/sistent, meshery/meshery (and meshery-extensions).

- Marcus

On Friday, June 26, 2026 at 11:55:09 PM UTC-5 mia.gre...@gmail.com wrote:

I'm following through on this meshmodels-good-riddance request. The first step of directory renaming and relocating from server/meshmodel to the repo root as models/ is completed as of this PR - https://github.com/meshery/meshery/pull/20312.

This change has been coordinated in the following repos:

- meshery/meshery

- meshery/schemas

Warm regards,

Mia

On Saturday, March 14, 2026 at 1:17:43 AM UTC-5 Mia Grenell wrote:

This has my +1. I see that Yi opened an issue to track this as well - https://github.com/meshery/meshery/issues/17904

Mia

On Tuesday, January 20, 2026 at 7:27:45 PM UTC-6 lee.c...@layer5.io wrote:

All,

I have added this to tomorrow's meeting agenda. Please review and comment at-will.

Regards,

Lee

On Sunday, January 18, 2026 at 3:28:37 PM UTC-6 Lee Calcote wrote:

All,

The source of truth for Meshery’s models is the Meshery Integration spreadsheet. Nightly, the contents of this sheet are downloaded and published to a handful of repositories. Within those repositories, these contents are placed in a specific directory. Each of those directories carries the name “meshmodels”. 

Proposal One: Rename and relocate "meshmodels" directory

While Meshery as a project does and has been known to use portmanteaus in it's naming of components, as time has gone on, the canonical reference to Meshery Models is just as “Models” not “MeshModels”. I propose that this directory be moved to a new directory in the root of the meshery/meshery repo at `/registry`. 

Proposal Two: Rename `meshmodel` API endpoints (routes) to `registry`

The collection of APIs under `/api/meshmodel` refer to Meshery’s internal “capabilities registry" in which models, components, relationships, connections, credentials, policies, and in the future, workflows (for actions other than “deploy” and “undeploy”), profiles (for both performance testing and monitoring) are registered into service. They can be used in designs, views, tests, policies, and in the future, workflows. The registry is where models are imported and cataloged, not meshmodels.

So, instead of /api/meshmodels, the routes will be /api/registry.

Relevant Renaming: meshes.proto

As you consider this, please be aware of related work, previously agreed and initiated, work in the renaming of the meshes protobuf definition that Meshery uses for gRPC communication between Meshery Server and its Adapters, which is currently called “meshes.proto”. Meshery Adapters capabilities have progressed well beyond that of managing service meshes. Adapters include the ability to manage any type of structure as well as perform advanced performance management of that into structure.

- https://github.com/meshery/meshery/issues/14226

- https://github.com/meshery/meshery/issues/9969

- https://github.com/meshery/meshery/issues/9968

Please comment at-will. Propose an alternative direction, if you like. 

Thanks,

Lee