Core concepts（核心概念）¶
This page describes the core concepts that underpin Foundry DevOps and Foundry Marketplace. We recommend that you read this page before proceeding since Foundry DevOps and Marketplace use specialized terminology (such as "product").
Product¶
In Foundry DevOps, "products" are collections of Foundry resources that a product builder has made available to install. Builders can create new products in Foundry DevOps.
Example product types include:
- Ontology: An instance of the Foundry Ontology, whether a comprehensive standard industry ontology or an ontology fragment.
- Use Case: A use case can be as simple as a single Workshop application or could involve a combination of multiple Workshop applications, functions, and Carbon workspaces.
- Pipeline: Pipelines can range from a single data transformation all the way to a group of many transforms and data connections in sequence.
- Modeling: A containerized executable model encapsulating any functional logic, including machine learning, forecasting, optimization, physical models, and business rules.
Each product has outputs, or content, that are produced when the product is installed. Products may require that installers map inputs in order to produce output content.
Products are the atomic unit that users can browse and install via the Marketplace storefront.
Product version¶
Product builders create and publish new versions of products every time they want to adjust existing product content or add new product content. When installing, we typically recommend choosing the latest product version. When new product versions become available, installers can upgrade manually or opt to receive new versions automatically.
Store¶
Stores are collections of products; these products typically have a shared purpose. Product builders can publish new products to stores. Stores that appear on your Foundry instance may be local (for instance, produced by a builder within your organization who works on your Foundry instance) or remote (for example, the Foundry Store that is available to all Foundry users and maintained by Palantir).
Installation¶
An installation is created when an installer fulfills the required inputs (if any) for a product. Each product can be installed multiple times. Multiple installations are typically created when:
- A product is required for different user groups. For example, you might install a ticket management product across a variety of support teams, using their ticketing data as input.
- You need to create an installation for different development environments. For example, you might install a ticket management product into a pre-production space and ontology, and again into a production space and ontology, each with their own input data and environment-specific settings like release channels and upgrade windows.
中文翻译¶
核心概念¶
本页介绍支撑Foundry DevOps和Foundry Marketplace的核心概念。我们建议您在继续阅读前先浏览本页内容，因为Foundry DevOps和Marketplace使用了专业术语（例如"产品"）。
产品(Product)¶
在Foundry DevOps中，"产品"是指产品构建者(builder)已发布可供安装的Foundry资源集合。构建者可以在Foundry DevOps中创建新产品。
产品类型示例包括：
- 本体论(Ontology): Foundry本体论的一个实例，可以是全面的标准行业本体论，也可以是本体论片段。
- 用例(Use Case): 一个用例可以简单到单个Workshop应用，也可能涉及多个Workshop应用、函数(Functions)和Carbon工作区(Carbon workspaces)的组合。
- 管道(Pipeline): 管道可以涵盖从单一数据转换到按序排列的多个转换和数据连接组。
- 建模(Modeling): 一个容器化的可执行模型，封装了包括机器学习、预测、优化、物理模型和业务规则在内的任何功能逻辑。
每个产品都有安装时产生的输出(outputs)或内容(content)。产品可能要求安装者映射输入(inputs)才能产生输出内容。
产品是用户可以通过Marketplace商店界面浏览和安装的原子单元。
产品版本(Product version)¶
每当产品构建者想要调整现有产品内容或添加新产品内容时，他们会创建并发布新版本的产品。安装时，我们通常建议选择最新产品版本。当新版本可用时，安装者可以手动升级或选择自动接收新版本。
商店(Store)¶
商店是产品的集合；这些产品通常具有共同用途。产品构建者可以将新产品发布到商店。您Foundry实例上显示的商店可能是本地的（例如，由您组织内使用该Foundry实例的构建者创建），也可能是远程的（例如，所有Foundry用户均可使用并由Palantir维护的Foundry商店）。
安装(Installation)¶
当安装者(installer)满足产品的所需输入（如有）时，即会创建安装。每个产品可以安装多次。通常在以下情况下会创建多个安装：
- 不同用户组需要同一产品。例如，您可能为多个支持团队安装一个工单管理产品，并使用他们的工单数据作为输入。
- 您需要为不同开发环境创建安装。例如，您可能将工单管理产品安装到预生产空间(space)和本体论(ontology)中，再安装到生产空间和本体论中，每个安装都有各自的输入数据和特定于环境的设置，如发布渠道和升级窗口。