vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/swr/umn/swr_03_0001.html
Dong, Qiu Jian 38e4c01e6c SWR UMN: Permission description is added 
Reviewed-by: Eotvos, Oliver <oliver.eotvos@t-systems.com>
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-authored-by: Dong, Qiu Jian <qiujiandong1@huawei.com>
Co-committed-by: Dong, Qiu Jian <qiujiandong1@huawei.com>
2024-06-18 06:49:13 +00:00

3.0 KiB
Raw Blame History

Introduction

SoftWare Repository for Container (SWR) allows you to easily manage the full lifecycle of container images and facilitates secure deployment of images for your applications.

SWR can either work with CCE or be used as an independent container image repository.

Figure 1 How SWR works

Features

  • Full lifecycle management of images

    SWR manages the whole lifecycle of your container images, including push, pull, and deletion.

  • Private image repository and access control

    Private image repository and fine-grained permission management allow you to grant different access permissions, namely, read, write, and edit, to different users.

  • Large scale image distribution acceleration

    SWR uses the image pull acceleration technology to ensure faster image pull for CCE clusters in high concurrency scenarios.

Accessing SWR

The cloud platform provides a web-based management console and HTTPS-based APIs through which you can access the SWR service.

  • Using APIs

    If you want to integrate SWR into a third-party system for secondary development, use APIs to access SWR. For details, see SWR API Reference.

  • Using the management console

    Use this mode if you do not want to integrate SWR into a third-party system.

Parent topic: Service Overview