For AI agents: the complete documentation index is available at https://docs.us.ovhcloud.com/en/llms.txt, the full documentation bundle is available at https://docs.us.ovhcloud.com/en/llms-full.txt, and this page is available as Markdown at https://docs.us.ovhcloud.com/en/public-cloud/managed-private-registry/responsibility-sharing.md.
  • English

Managed Private Registry - Responsibility sharing

View as Markdown

Managed Private Registries allow you to focus on using Harbor to host, share, and manage your cloud-native artifacts while OVHcloud takes care of the required software and hardware maintenance in operational conditions.

The RACI below details shared responsibilities between OVHcloud and the customer for Public Cloud Managed Private Registry services. This shared model can help relieve the customer’s operational burden.

 

RACI definition

Roles
R: Is responsible for carrying out the process
A: Is accountable for the successful completion of the process
C: Is consulted during the process
I: Is information of the results of the process

For your information, a Service is considered a Cloud Databases service, such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, Cassandra, or M3 cluster.

 

1. Before subscription

1.1. Specify service as needed

ActivityCustomerOVHcloud
Learn about the capabilities and limitations of the Services detailed in the OVHcloud documentationRACI
Use a container or orchestrator toolRAI
Create a Public Cloud projectRAI
Choose the service locationRAI
Choose the plan range (model: S, M, or L) based on business needsRAI

 

2. Service availability

2.1. Install service

ActivityCustomerOVHcloud
Produce, route, deliver, and maintain underlying software, physical machines, and hosting buildings RA
Buy and hold licenses and usage rights for software provided by OVHcloud (Harbor, Trivy, etc.) RA

 

2.2. Reversibility model

ActivityCustomerOVHcloud
Import images using any Docker images or chart helm within OCI formatRA 

 

2.3. Customer Information System setup

ActivityCustomerOVHcloud
Deploy workloads using imagesRA 
Modify templates, helm charts, dockerfile, URLs for images' names, image dockers, etc.RA 

 

3. Service usage

3.1. Operations

3.1.1 Daily operations
ActivityCustomerOVHcloud
Leverage adequate compute and storage to deliver the service within the plan limits RA
Decide to upgrade the plan of existing service following business needsRAI
Define and implement an image policy (use of official and trusted public images Registry, updates, vulnerability scoring, etc.)RAI
Implement a backup policy for Registry imagesRAI
 
3.1.2 Access management
ActivityCustomerOVHcloud
Manage access to the OVHcloud Control PanelRAI
Manage access to management interfaces specific to the Service (Harbor UI, API, Docker command line, etc.)RAI
Manage OVHcloud teams' physical access to infrastructures RA
Manage OVHcloud teams' logical access to infrastructures RA
 
3.1.3 Monitoring
ActivityCustomerOVHcloud
Monitor the proper functioning of physical devices (utilities) in support of the registry service RA
Monitor the proper functioning of virtual devices (utilities) in support of the registry serviceIRA
Process and pay for alarms from managed devices in the Private Registry infrastructureIRA
Maintain and monitor logs generated by the Private Registry service on the management infrastructure RA
Keep logs of the Private Registry service provided in Harbor UI or by using APIRA 
 
3.1.4 Storage
ActivityCustomerOVHcloud
Manage content hosted on the Private Registry serviceRAI
Manage data continuity and sustainabilityRA 
Perform storage and device maintenance RA
 
3.1.5 Connectivity
ActivityCustomerOVHcloud
Operate automatic network management systems (architecture, implementation, software, and hardware maintenance for deployed public and private networks)IRA
Provide and maintain a domain name on the serviceIRA
 
3.1.6 Management
ActivityCustomerOVHcloud
Provide inventory of the service usedIRA
Manage risks on managed components of the Private Registry service RA
Maintain the service in operational and security conditions RA
Plan vulnerability scans on used images (in case of subscription to M or L plan or with the client's proper tool)RAI
Manage alerts raise by vulnerability scans on imagesRA 
 
3.1.7 Business continuity
ActivityCustomerOVHcloud
Manage automatic systems and availability for the managed Platform serviceIRA
Maintain a business continuity and disaster recovery plan on the Registry imagesRAI

 

3.2. Event management

3.2.1 Incidents
ActivityCustomerOVHcloud
Notify incidents within the service RegistryRAI
Intervene with Public Cloud Private Registry managed elementsIRA
 
3.2.2 Changes
ActivityCustomerOVHcloud
Comply with the service Lifecycle PolicyRA 
Deploy patches, update software and information systems hosted in Public Cloud Private RegistryIRA
Deploy patches, update, and configure the information system using the Public Cloud Private RegistryRA 
Perform preventative interventions on managed elements of the Public Cloud Private RegistryIRA

 

4. Reverting

4.1. Reversibility model

ActivityCustomerOVHcloud
Schedule reversibility operationsRAI
Choose fallback infrastructuresRA 
Use Docker to transfer image by image or to replicate images by using Harbor registryRA 

 

4.2. Data recovery

ActivityCustomerOVHcloud
Manage reversibility operationsRAI
Migrate/transfer dataRA 

 

5. End of service

5.1. Destroying configurations

ActivityCustomerOVHcloud
Delete the Private Registry service configurations (using API or user interface)RAI

 

5.2. Data destruction

ActivityCustomerOVHcloud
Destroy DB image registry service RA
Destry project information RA

 

Go further

Browse all the Managed Private Registry (MPR) guides.

Browse the rest of the OVHcloud US documentation for guides on our other products and services.

Learn more about Managed Private Registry on the OVHcloud US website.