CCE.Storage.OBS
Element Description
The CCE.Storage.OBS element corresponds to object storage volumes in the CCE storage management function. This type of resources must be used together with CCE clusters.
Element Properties
Property |
Mandatory |
Descripiton |
---|---|---|
k8sManifest |
No |
K8s-native manifest object of the OBS, which can be used to replace other configuration items in OBS resource creation Type: dict Value Constraint: The value must meet the Kubernetes specifications. Suggestion: For details, see the sample or CCE documentation. |
name |
No |
PVC name Type: string Value Description: Customize the value. Value Constraint: Each PVC name must be unique in a namespace. The value must contain 1 to 24 characters and meet regular expression (^$)|(^[a-z]([-a-z0-9]*[a-z0-9])?$). Suggestion: Customize the value. |
clusterId |
No |
ID of the cluster to which the resource belongs Type: Cloud.CCE.Cluster.Id Value Description: ID of an existing or new container cluster. Value Constraint: The value must satisfy the UUID rule and contain a maximum of 64 characters. Suggestion: 1. Enter the cluster ID. Specifically, log in to the CCE console, and choose Resource Management > Clusters. Click the target cluster, and you can then obtain its cluster ID. 2. Connect to the cluster object and use the get_reference function to obtain the cluster ID. 3. Leave it blank, and specify the ID on the AOS console when creating a stack. |
namespace |
No |
Namespace to which the resource belongs Type: string Value Description: It must be a valid namespace in the cluster, for example, default. Value Constraint: The value must start with a letter. Only lowercase letters, digits, and hyphens (-) are allowed. Suggestion: Customize the value based on the existing cluster or the cluster to be created. |
volumeId |
No |
Cloud storage volume ID when you import a volume Type: string Value Description: Customize the value. Value Constraint: The value must satisfy the UUID rule and contain a maximum of 64 characters. Suggestion: None |
deleteVolume |
No |
Whether to delete the cloud storage when you import a volume and delete a PVC Type: boolean Default: False Value Constraint: The options are true and false. Suggestion: None |
Relationships Between Elements
Description |
Target |
---|---|
Dependency |
|
Dependency |
|
Dependency |
|
Dependency |
|
Dependency |
|
Dependency |
|
Dependency |
|
Inclusion |
Return Value
Property |
Type |
Description |
---|---|---|
clusterId |
string |
ID of the cluster which is associated with the OBS file system |
refID |
string |
UID of the OBS file system |
refName |
string |
Name of the OBS file system |
Blueprint Example
Example 1:
tosca_definitions_version: cloud_tosca_version_1_0 inputs: storage-name: default: my-evc-storage node_templates: my-storage: type: Cloud.CCE.Storage.OBS properties: name: {get_input: storage-name}
Example 2: Custom K8s Manifest for Orchestration
- For clusters of version 1.13 or earlier, the example configuration of the YAML file is as follows:
tosca_definitions_version: cloud_tosca_version_1_0 node_templates: my-storage: type: Cloud.CCE.Storage.OBS properties: apiVersion: v1 kind: PersistentVolumeClaim metadata: annotations: volume.beta.kubernetes.io/storage-class: obs-standard volume.beta.kubernetes.io/storage-provisioner: flexvolume.com/obs name: cce-obs-k7yhr36u-iuu9 namespace: default spec: accessModes: - ReadWriteMany resources: requests: storage: 10Gi
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot