Andromeda Service Catalog

Restricted functionality

This functionality can only be accessed when having one of the following roles:

• OWNER

Learn more about roles here.

The Service Catalog module lets admins maintain the list of available services and review access requests submitted for service usage.

This feature provides the editing interface for managing:

• Service catalog items such as platform services, tools, or resources users can request.
• Open access requests that need approval or rejection from the HPC-center team.

The feature is organized into two main working areas:

• Services — the catalog entries available to users.
• Requests — incoming service requests with project and person context.

Services

A service item represents a service available in the catalog.

Each item can contain:

• A Name
• A Description
• One or more Tags
• An Icon or Image
• Available actions
• Required permissions and permission explanations

How users work with services

Add a service

1. Click Add service.
2. Fill in the service details.
3. Add tags, icon, or image if needed.
4. Configure available actions and permissions.
5. Save the service.

Update a service

1. Open an existing service from the list.
2. Change the required fields.
3. Save the updated version.

Delete a service

1. Open the service.
2. Click Delete.
3. Confirm the action.

Deleting a service removes it from the catalog and should only be used when the item is no longer valid.

What the main service fields mean?

1. Name: the label shown to users in the catalog.
2. Description: explains what the service does and when it is used.
3. Tags: help group related services.
4. Icon / Image: provides a clear visual identifier for the service.
5. Available actions: actions that can be triggered for the service.
6. Required permissions: defines which access rights are needed before the service can be used.

Requests

Open requests represent service access requests submitted by users or projects.

Admins can review the request together with the related project and person details before deciding whether to approve or reject it.

How users work with requests

Review a request

1. Open the list of open requests.
2. Check the related project and person information.
3. Review the requested service details.
4. Approve or reject the request.

Approve a request

1. Click Approve on the relevant row.
2. Confirm the action prompted.
3. The request is processed and the catalog state is refreshed.

Reject a request

1. Click Reject on the relevant row.
2. Confirm the rejection.
3. The request is removed from the active list.

Common Usage Examples

Typical use cases include:

• Adding a new internal service to the catalog
• Updating an existing service description or permissions
• Uploading a new icon or image for branding
• Reviewing and approving a project request for service access

Error Conditions and Validation

Users may encounter the following validation or error situations:

• Data could not be loaded. The page may display an error if catalog data cannot be retrieved. In this case, the user can use Retry.
• Required service fields missing. A service cannot be saved without a Name and Description.
• Save or update failure. If the create or update action is rejected, the user sees an error message and can fix the input and retry.
• Delete failure. If a service deletion fails, the returned error message is displayed.
• Request approval or rejection failure. If the decision action fails, the user sees an error and can retry.