Managed Private Registry - Responsibility model

Shared responsibilities between OVHcloud and the customer

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 in charge of carrying out the process
A: Accountable for the successful completion of the process
C: Is consulted during the process
I: Is informed of the results of the process

For your information, a Service is considered a Public Cloud Managed Private Registry service, that is a Harbor registry instance hosting your container images and Helm charts.

1. Before subscription

1.1. Specify service as needed

Activity	Customer	OVHcloud
Learn about the capabilities and limitations of the Services detailed in the OVHcloud documentation	RA	CI
Use a container or orchestrator tool	RA	I
Create a Public Cloud project	RA	I
Choose the service location	RA	I
Choose the range plan following business needs (Model : S , M or L)	RA	I

2. Service availability

2.1. Install service

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

2.2. Reversibility model

Activity	Customer	OVHcloud
Import images using any Docker images or chart helm within OCI format	RA

2.3. Customer Information System setup

Activity	Customer	OVHcloud
Deploy workloads using their images	RA
Modify templates, helm charts, dockerfile, urls for images' names, Docker images, etc .	RA

3. Service usage

3.1. Operations

3.1.1. Daily operations

Activity	Customer	OVHcloud
Leverage adequate compute and storage to deliver the service within the plan limits		RA
Decide to upgrade plan of the existing service following business needs	RA	I
Define and implement an image policy (use of official and trusted public images Registry, updates, vulnerability scoring, etc.)	RA	I
Implement a backup policy for Registry images	RA	I

3.1.2. Access management

Activity	Customer	OVHcloud
Manage access to the OVHcloud Control Panel	RA	I
Manage access to management interfaces specific to the Service (Harbor UI, API, Docker command line, etc.)	RA	I
Manage OVHcloud teams’ physical access to infrastructures		RA
Manage OVHcloud teams’ logical access to infrastructures		RA

3.1.3. Monitoring

Activity	Customer	OVHcloud
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 service	I	RA
Process and pay for alarms from managed devices in the Private Registry infrastructure	I	RA
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 API	RA

3.1.4. Storage

Activity	Customer	OVHcloud
Manage content hosted on the Private Registry service	RA	I
Manage data continuity and sustainability	RA
Perform storage and device maintenance		RA

3.1.5. Connectivity

Activity	Customer	OVHcloud
Operate automatic network management systems (architecture, implementation, software and hardware maintenance for deployed public and private networks)	I	RA
Provide and maintain a domain name on the service	I	RA

3.1.6. Management

Activity	Customer	OVHcloud
Provide inventory of the service used	I	RA
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)	RA	I
Manage alerts raised by vulnerability scans on images	RA

3.1.7. Business continuity

Activity	Customer	OVHcloud
Manage automatic management systems and availability for the managed Platform service	I	RA
Maintain a business continuity and disaster recovery plan on the Registry images	RA	I

3.2. Event management

3.2.1. Incidents

Activity	Customer	OVHcloud
Notify incidents within the service Registry	RA	I
Intervene with Public Cloud Private Registry managed elements	I	RA

3.2.2. Changes

Activity	Customer	OVHcloud
Comply with the service Lifecycle Policy	RA
Deploy patches, update software and information systems hosted in Public Cloud Private Registry	I	RA
Deploy patches, update and configure the information system using Public Cloud Private Registry	RA
Perform preventive interventions on managed elements of the Public Cloud Private Registry	I	AR

4. Reverting

4.1. Reversibility model

Activity	Customer	OVHcloud
Schedule reversibility operations	RA	I
Choose fallback infrastructures	RA
Use Docker to transfer image by image or to replicate images by using Harbor registry	RA

4.2. Data recovery

Activity	Customer	OVHcloud
Manage reversibility operations	RA	I
Migrate/transfer data	RA

5. End of service

5.1. Destroying configurations

Activity	Customer	OVHcloud
Delete the Private Registry service configurations (using API or user interface )	RA	I

5.2. Data destruction

Activity	Customer	OVHcloud
Destroy DB image registry service		RA
Destroy project information		RA

Go further

Visit our dedicated Discord channel: https://discord.gg/ovhcloud. Ask questions, provide feedback and interact directly with the team that builds our private registry services.

Join our community of users.

¿Le ha resultado útil esta página?