For AI agents: the complete documentation index is available at https://docs.ovhcloud.com/de/llms.txt, the full documentation bundle is available at https://docs.ovhcloud.com/de/llms-full.txt, and this page is available as Markdown at https://docs.ovhcloud.com/de/guides/hosted-private-cloud/opcp/cloudstore-getting-started.md.
Zum Inhalt springen

Getting started with Cloud Store

Als Markdown ansehen

Find out what Cloud Store is, its two consoles and its key concepts — Organizations, Service Deployments, Host Pools and Enabled Services

Warning

Alpha version — This guide documents the alpha version of Cloud Store. Features, interfaces and procedures will change until general availability (GA), and this guide will be updated along with them.

Objective

This guide introduces Cloud Store, its two consoles and the concepts you need before you start using it.

Cloud Store is the management platform of On-Prem Cloud Platform (OPCP). It runs on top of OPCP Core and the OPCP hardware, and lets you deploy cloud services on your bare-metal hosts and make them available to the companies, departments or teams that use them.

Requirements

  • An OPCP platform with Cloud Store, delivered by OVHcloud.
  • The URL of the OPCP Admin Console and your login credentials, provided during service delivery.

Instructions

The two Cloud Store consoles

Cloud Store has two interfaces, one per audience:

ConsoleForPurpose
OPCP Admin ConsoleIT AdminsCreate Organizations, deploy services from the Service Catalog and enable them for Organizations.
OPCP Cloud ConsoleOrganization Admins and Organization UsersUse the services enabled for the Organization and create Cloud Resources, such as virtual machines, volumes or buckets.

Both consoles are available in French and English.

Each console has its own guide:

Roles

RoleConsoleResponsibilities
IT AdminOPCP Admin ConsoleCreates Organizations, deploys services and enables them for Organizations.
Organization AdminOPCP Cloud ConsoleCreated with the Organization. Manages the users of the Organization.
Organization UserOPCP Cloud ConsoleUses the services enabled for the Organization and creates Cloud Resources.

Key concepts

Organization

An Organization is the environment in which a group of users consumes the services enabled for it. It usually represents a company, a department or a team. What separates Organizations is described in Isolation between Organizations.

Service Catalog and Service Deployments

The Service Catalog lists the services available on your platform, for example Compute and Block Storage or Object Storage. From the catalogue, the IT Admin deploys a chosen version of a service onto the infrastructure. The result is a Service Deployment. All Service Deployments are collected in the OPCP Admin Console, under Management > Deployments.

Host Pools

When deploying a service, the IT Admin allocates bare-metal hosts to Host Pools. A Host Pool groups hosts by their characteristics, for example compute or storage hosts. Each service states the Host Pools it needs.

To increase the capacity of a service, add hosts to the corresponding Host Pool.

Enabled Services

An Enabled Service is a Service Deployment enabled for one Organization. It makes the service visible in that Organization's OPCP Cloud Console. Depending on the service, its hosts are shared by several Organizations or dedicated to a single one: services that cannot be shared get a dedicated Host Pool for each Organization.

Isolation between Organizations

Organizations are isolated from each other at two levels:

  • Identity: each Organization has its own Keycloak realm, which holds its users, roles and groups.
  • Cloud Resources: each service separates the Cloud Resources of the Organizations it is enabled for. For example, Compute and Block Storage holds the resources of each Organization in its own OpenStack Keystone projects.

Typical journeys

  1. Service deployment: the IT Admin logs in to the OPCP Admin Console, opens the Service Catalog, selects a service and deploys it. They choose a version, allocate the Host Pools and configure the service.
  2. Organization creation: the IT Admin opens Organizations, creates an Organization for the customer and defines its Organization Admin (email, first name, last name).
  3. Service enablement: the IT Admin enables the Service Deployment for the Organization, from the Service Deployment page or from the Organization page.
  4. Cloud Console usage: the Organization Admin logs in to the OPCP Cloud Console and manages the users of the Organization. Organization Users open the Enabled Services and create Cloud Resources.

Authentication and Security Zones

The platform separates authentication into two Security Zones, each backed by its own Keycloak instances:

Security ZoneKeycloak instanceUsersPurpose
Admin Security ZoneOPCP Core KeycloakDC operators, Super adminsInfrastructure-level identity
Admin Security ZoneOPCP Admin Console KeycloakIT Admins, Service PackagersPlatform management
Public Security ZoneOne Keycloak realm per OrganizationOrganization Admins, Organization UsersOPCP Cloud Console and Enabled Services
  • Within the Admin Security Zone, the OPCP Admin Console Keycloak is federated with the OPCP Core Keycloak: rights granted on OpenStack projects in OPCP Core are carried through to the OPCP Admin Console.
  • The Public Security Zone relies on an independent Keycloak instance managed by the OPCP Admin Console API. It is not federated with the Admin Security Zone, and each Organization's realm is isolated from the others.

Go further

OPCP Admin Console

OPCP Cloud Console

For training or technical assistance implementing our solutions, contact your sales representative or visit our Professional Services page to request a quote and have your project analysed by our experts.

Join our community of users.

War diese Seite hilfreich?