Profile Catalog Management

Overview¶

The Profile Catalog provides a centralized mechanism for managing and distributing environment templates and profiles. It supports two key personas:

Partners (CSPs): Can customize and share profiles with their tenant organizations by managing artifacts in the Profile Catalog using the Ops Console.
Enterprise Organizations: Can clone templates and profiles from the Profile Catalog into local projects for customization and reuse across internal projects.

This guide outlines the steps for both CSPs and enterprise admins to effectively use the Profile Catalog while maintaining governance through read-only system-defined baselines.

Profile Catalog for CSP/Tenant Organizations¶

Step 1: Profile Catalog Population¶

Rafay loads system templates and profiles into the default-catalog project within the default Org of the partner. These are read-only artifacts.

Step 2: Select the `system-catalog` Project During Cloning¶

To expose customized profiles to tenant orgs, the partner must ensure that the cloned profile resides in the system-catalog project.

Follow these steps: 1. Navigate to PaaS Studio → Profile Catalogs from the left-hand menu. 2. Browse and identify the required profile catalog (e.g., a service or compute profile). In the example below, a service profile is selected. 3. Select Get Started on the desired profile card. 4. In the Get Started dialog: * Provide a Name for the catalog. * Choose Select Existing Project. * From the Select Project dropdown, choose system-catalog. This ensures that the profile is placed in the correct project for sharing with tenant organizations. * Enable the Is Customizable option when the profile must allow tenant administrators to override specific input variables. This option is used when tenant organizations require controlled customization of shared profiles. Only the variables marked as Allow Override by the partner administrator can be modified by tenants, while all other variables remain fixed. 5. Click Continue to proceed. 6. Make the required configuration changes to the cloned profile (e.g., environment templates, variables, or schedule settings) and click Save Changes to finalize the profile in the system-catalog project.

Partners can expose customized profiles to their tenant organizations via the Ops Console.

Note: These profiles must reside in the system-catalog project to be shareable with tenants.

In the Service Profiles section, locate the desired profile and use the Share icon under the Actions column to configure sharing.

Step 4: Profiles in Tenant Org’s Profile Catalogs¶

Exposed profiles will be shown in the Profile Catalogs of the tenant organizations.

Note: This profile is read-only for tenant orgs.

PaaS admins in tenant orgs cannot modify or clone these profiles. They can only share them with other projects within their organization.

Clone Option for Customizable Profiles¶

If the Is Customizable option is enabled for a profile in Step 2, a clone icon appears on the profile card in tenant organizations. This allows tenant administrators to clone and customize the profile based on the variables marked as Allow Override by the partner administrator.

Selecting the clone icon on a customizable profile opens the Customize Compute Profile dialog. This dialog allows tenant administrators to create a customized version of the shared profile within their organization.

The following fields are available: * Name: Specifies the name for the customized profile. * Display Name (optional): Provides a user-friendly label for the profile. * Description (optional): Describes the purpose or variations of the customized profile. * Target Project: Indicates where the customized profile will be created within the tenant organization.

After saving the customization, the tenant administrator can modify only the variables designated as Allow Override by the partner administrator.

The Override option can be enabled for individual variables or for all variables using Allow Override For All. Only variables marked as overridable are available for customization when creating instances based on the tenant’s customized profile.

After the customization is saved, the cloned profile appears in the tenant organization’s profile list with a “Customized Profile” label. This label indicates that the profile is derived from a partner-provided profile and includes tenant-specific overrides.

If the profile is not marked as customizable in Step 2, the clone icon is not displayed, and customization is not available in tenant organizations.

Profile Catalog for Enterprise Organizations¶

Rafay provides system templates and profiles to enterprise organizations in a centralized, read-only location called the Profile Catalogs. These serve as baseline templates that can be used across the organization.

Step 1: Default Catalog¶

Rafay loads system environment templates and profiles into the Profile Catalogs. These are read-only and cannot be modified directly.

Step 2: Cloning for Customization¶

Admins of the default organization can customize system templates or profiles by cloning them into a project they have access to.

Navigate to PaaS Studio → Profile Catalogs.
Locate the required system profile (e.g., Jupyter Notebook) and click Get Started.
In the Get Started window:
- Provide a Name for the new catalog (e.g., jupyter-catalog).
- Select the Project Type (choose “Select Existing Project” or “Create Project” as needed).
- Select the target Project where the profile should be cloned (e.g., notebook-profile).
Click Continue to complete the cloning process.
Make the required modifications (e.g., update configurations, variables, or schedules) in the selected project and click Save Changes

The environment template must be shared with the target profile before cloning.

Once customized, admins can share the modified templates or profiles with other projects in the same organization. This enables consistent and reusable configurations across multiple teams or workspaces.

Note: Admins of Default Org have full control over cloned artifacts. However, the originals in Profile Catalog remain immutable and serve as a reliable source of system-defined baselines.