Skip to content

Portfolios

Curated service catalogs that bundle artifacts from across the platform -- similar to AWS Service Catalog.

Overview

Portfolios are curated collections of artifacts that span both the MetaCloud and Cloud Operations layers. A portfolio packages formations, images, cloud keys, storages, perspectives, views, IAM users, and other platform artifacts into a single shareable unit.

Think of portfolios as service catalogs: an administrator curates a set of approved resources, shares the portfolio with a team or organization, and members can browse, clone, and deploy from it. This is similar to how AWS Service Catalog works, but across all supported clouds and spanning both infrastructure and governance artifacts.

What Portfolios Can Contain

Layer Artifact Types
MetaCloud Formations, images, cloud keys, key pairs, storages, container images, container repositories, Kubernetes clusters, IP addresses, domains, SSL certificates, startup scripts
Cloud Operations IAM users, cloud accounts, perspectives, views
Platform Any shareable RosettaHub artifact

Use Cases

Use Case Description
Institutional service catalog IT curates approved formations, images, and cloud accounts for self-service deployment across the organization
Course materials Educator packages lab formations, images, perspectives, and pre-configured views for a class
Research reproducibility Researcher bundles all artifacts (formations, datasets, images, keys) needed to reproduce an experiment
Onboarding kits Assemble everything a new team member needs -- formations, perspectives, views, and cloud keys -- in one place
Managed environments Package a complete governed environment: formation + cloud account + compliance perspective

Portfolio Roles

Each portfolio has its own role-based access control:

Role Description
rhp-portfolio-{id} Portfolio member -- can view and deploy from the portfolio
rhpsu-portfolio-{id} Portfolio superuser -- elevated access within the portfolio
rhpadmin-portfolio-{id} Portfolio administrator -- full control over portfolio contents and membership

Actions

Action Description
Create Portfolio Create a new portfolio
Add To Portfolio Add artifacts from any layer to the portfolio
Remove From Portfolio Remove artifacts from the portfolio
Browse View portfolio contents
Share Grant access to users, groups, or organizations
Publish List on the Marketplace
Clone Copy a shared or public portfolio to customize it
Customize Update label and metadata
Delete Remove the portfolio

Sharing and Publishing

Portfolios support the same sharing model as other RosettaHub artifacts:

  • Share with individuals -- grant access to specific users
  • Share with groups or organizations -- make the portfolio available to a team or department
  • Publish to the Marketplace -- share the portfolio with user "hub", then publish it for discovery by all users

When someone receives a shared portfolio, they can browse its contents and clone individual artifacts into their own workspace.

Portfolios vs Formations

Aspect Formation Portfolio
What it is A single infrastructure template A collection of multiple artifacts across layers
Contains Cloud keys, images, scripts, IaC Formations, images, keys, perspectives, views, IAM users, and more
Action Launch to create a session Browse and clone individual items
Scope MetaCloud only MetaCloud + Cloud Operations