Catalog Details
CATEGORY
deploymentCREATED BY
UPDATED AT
January 06, 2025VERSION
0.0.1
What this pattern does:
This infrastructure design defines two services within a system: 1. **Customer Service**: - Type: Customer - Version: 0.0.50 - Model: Jira Service Desk Operator - Attributes: This service is configured with specific settings, including an email address, legacy customer mode, and a name. It is categorized as a tool within the system.2. **Notebook Service**: - Type: Notebook - Version: 1.6.1 - Model: Kubeflow - Attributes: This service is categorized as a machine learning tool. It has metadata related to its source URI and appearance. These services are components within a larger system or design, each serving a distinct purpose. The Customer Service is associated with customer-related operations, while the Notebook Service is related to machine learning tasks.
Caveats and Consideration:
Make sure to use correct credentials for Jira service operator
Compatibility:
Recent Discussions with "meshery" Tag
- Jun 22 | Newcomers call experience and Star Meshery
- Dec 31 | 404 page not found
- Dec 30 | Seeking Help with Playground Features for Complex Designs
- Dec 04 | Link Meshery Integrations and Github workflow or local code
- Nov 25 | Issue: Unable to Run make server-local in Meshery Cloud Setup Due to Soda CLI Dependency
- Nov 28 | Issue on Setting Up Meshery Using Docker
- Nov 22 | Meshery CI Maintainer: Sangram Rath
- Nov 25 | T.roles_names is undefined ( permission path is not provided )
- Nov 20 | Meshery Development Meeting | Nov 20th 2024
- Nov 10 | Error in "make server" and "make ui-server"