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”.
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.
Please comment at-will. Propose an alternative direction, if you like.
Thanks,
Lee