Introduction
Refers to create a shared service on the platform, and specify its name, resource pool, IP address, domain name, and other information. Tenant VPCs then can access the corresponding shared service (Example: Application center, security center) through the configuration.
Constraints and Restrictions
• Predefined services (Example: Kubernetes Engine, Block Storage Service - Block Storage) cannot be created on the platform. Only shared services customized by users can be created.
• If the resource pool is specified, the resource pool version must be SCP 5.8.8 or later. Otherwise, creation will fail.
• The IP address for a shared service must be a private IP address and cannot conflict with the IP ranges of existing networks (Example: Tenant VPCs, networks of other shared services).
• The domain name must comply with DNS naming conventions and must be resolvable within the tenant environment.
Prerequisites
• You have logged in to SCP using the super admin account.
• The IP address and domain name for the shared service must already be planned to ensure no conflict with existing networks.
• If the resource pool is specified, the resource pool version must be SCP 5.8.8 or later.
Precautions
• The shared service gateway must be configured for the resource pool before creation. Otherwise, the shared service will be unable to communicate with tenant VPCs.
• If the Activate this service for tenants option is checked, the service will be automatically activated for new tenants associated with the resource pool. Make sure that the service is available for all tenants.
• The selected protocol must match the actual communication protocol of the shared service. If uncertain, you can select All for Protocol.
Steps
Step 1.Log in to SCP and go to the Shared Service Network > Shared Services page.
Step 2.Click New at the top of the page, and the Create Shared Service pop-up window appears.
Step 3.Configure the following fields:
| Field |
Description |
Operation Suggestion |
| Name |
A custom name for the shared service, used to identify the service type. |
The format is Service Type – Purpose. Example: Application Center - sss. |
| Description |
Optional. Supplement information about the purpose or details of the shared service. |
Example: Shared service providing best practices for app deployment. |
| Resource Pool |
Select the resource pools associated with the shared service. Selecting all resource pools makes the service available to all pools. If the resource pools are specified, the service will be available only to the specified pools. |
If the service is only available to tenants of specific resource pools, select Specified for Resource Pool and select the target resource pools (Example: Hygon Cluster (c86)). |
| IP Address |
The IP address of the shared service. It must be a private IP address and not conflict with existing networks. |
Enter the planned IP address (Example: 100.1.1.200). |
| Domain Name |
The domain name of the shared service. It must match the DNS conventions. |
Enter a domain name that is resolvable (Example: appcenter.local.cloud.scp). |
| Protocol |
The communication protocol for the shared service. Selecting all protocols indicates that all protocols are supported. |
If the service uses only HTTP/HTTPS protocol, select the corresponding protocol. Otherwise, select all protocols. |
| Advanced - Activate this service for tenants |
If selected, the shared service will be automatically activated for new tenants associated with the resource pool. |
Check this option if the service is a general basic service. Do not check the option if it is a specific business service. |
Step 4.After the configuration is complete, click OK to finish the shared service creation. You can view the new shared service on the Shared Services page.
{{ $t('index.defaultHeader.chromeBrowserTip') }}