vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity

CCI UMN initial upload

Browse Source 
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>
This commit is contained in:
Dong, Qiu Jian 2024-10-24 12:19:17 +00:00 committed by zuul
parent e8e108284a
commit a9ef41723a
45 changed files with 2113 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

347
docs/cci/umn/ALL_META.TXT.json Normal file
View File

File diff suppressed because it is too large Load Diff

173
docs/cci/umn/CLASS.TXT.json Normal file
View File

File diff suppressed because it is too large Load Diff

3
docs/cci/umn/PARAMETERS.txt Normal file
View File

@ -0,0 +1,3 @@
version=""
language="en-us"
type=""

91
docs/cci/umn/cci_01_0001.html Normal file
View File

@ -0,0 +1,91 @@
<a name="cci_01_0001"></a><a name="cci_01_0001"></a>
<h1 class="topictitle1">Creating a Namespace</h1>
<div id="body1533802454806"><p id="cci_01_0001__p8060118">Namespaces are used to logically divide your resources into different groups, especially in scenarios where a large number of users from multiple teams work on different projects.</p>
<p id="cci_01_0001__p8838163242918">CCI provides general computing resources and allows you to create pods with CPU resources for general computing.</p>
<div class="note" id="cci_01_0001__note104738543614"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cci_01_0001__ul16488173333413"><li id="cci_01_0001__li1890044621416">One account can create a maximum of five namespaces in a region.</li><li id="cci_01_0001__li17472726134618">x86 images are supported.</li></ul>
</div></div>
<div class="section" id="cci_01_0001__section17189123157"><h4 class="sectiontitle">Relationship Between Namespaces and Networks</h4><p id="cci_01_0001__p113090420361">Each namespace requires a separate subnet, as shown in <a href="#cci_01_0001__fig119999112419">Figure 1</a>. When you create a namespace, you need to associate it with a VPC. A subnet will be created for the namespace in the VPC. Containers and other resources created in this namespace will run in the VPC and subnet you select.</p>
<p id="cci_01_0001__p588217147288">If you want to run resources of multiple services in the same VPC, you need to consider network planning, including subnet CIDR block division and IP address planning.</p>
<div class="fignone" id="cci_01_0001__fig119999112419"><a name="cci_01_0001__fig119999112419"></a><a name="fig119999112419"></a><span class="figcap"><b>Figure 1 </b>Relationship between namespaces and VPC subnets</span><br><span><img id="cci_01_0001__image1920811571216" src="en-us_image_0201693831.png"></span></div>
</div>
<div class="section" id="cci_01_0001__section5571151617513"><h4 class="sectiontitle">Application Scenarios</h4><p id="cci_01_0001__p1924341711518">Namespaces can implement partial environment isolation. If you have a large number of projects and personnel, you can create different namespaces based on project attributes, such as production, test, and development.</p>
</div>
<div class="section" id="cci_01_0001__section940418587214"><a name="cci_01_0001__section940418587214"></a><a name="section940418587214"></a><h4 class="sectiontitle">Creating a Namespace</h4><ol id="cci_01_0001__ol162711945486"><li id="cci_01_0001__li32713413484"><span>Log in to the CCI console. In the navigation pane on the left, choose <strong id="cci_01_0001__b7785123510359">Namespaces</strong>.</span></li><li id="cci_01_0001__li1476152610237"><span>On the <strong id="cci_01_0001__b11793203715322">Namespaces</strong> page, click <strong id="cci_01_0001__b4990144573211">Create Namespace</strong> in the upper right corner.</span></li><li id="cci_01_0001__li38097582234"><span>Enter a name for the namespace.</span><p><div class="note" id="cci_01_0001__note554162619484"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cci_01_0001__ul9719134717375"><li id="cci_01_0001__li9719114717371">The name of each namespace must be unique in CCI.</li><li id="cci_01_0001__li3719547193711">Enter 1 to 63 characters. Start and end with a lowercase letter or digit. Use only lowercase letters, digits, and hyphens (-).</li></ul>
</div></div>
</p></li><li id="cci_01_0001__li16865645389"><span>Configure the network plane.</span><p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cci_01_0001__table7168814201011" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Network plane settings</caption><thead align="left"><tr id="cci_01_0001__row1316816147103"><th align="left" class="cellrowborder" valign="top" width="24.18%" id="mcps1.3.6.2.4.2.1.2.3.1.1"><p id="cci_01_0001__p9168141418105">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="75.82%" id="mcps1.3.6.2.4.2.1.2.3.1.2"><p id="cci_01_0001__p18168131451020">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="cci_01_0001__row2142161092112"><td class="cellrowborder" valign="top" width="24.18%" headers="mcps1.3.6.2.4.2.1.2.3.1.1 "><p id="cci_01_0001__p414312101217">IPv6</p>
</td>
<td class="cellrowborder" valign="top" width="75.82%" headers="mcps1.3.6.2.4.2.1.2.3.1.2 "><p id="cci_01_0001__p181431410162114">If this option is enabled, IPv4/IPv6 dual stack is supported.</p>
</td>
</tr>
<tr id="cci_01_0001__row1216991471016"><td class="cellrowborder" valign="top" width="24.18%" headers="mcps1.3.6.2.4.2.1.2.3.1.1 "><p id="cci_01_0001__p181695146109">VPC</p>
</td>
<td class="cellrowborder" valign="top" width="75.82%" headers="mcps1.3.6.2.4.2.1.2.3.1.2 "><p id="cci_01_0001__p816918145103">Select the VPC where the workloads are running. If no VPC is available, create one first. The VPC cannot be changed once selected.</p>
<p id="cci_01_0001__p1821515082314">Recommended CIDR blocks: 10.0.0.0/8-22, 172.16.0.0/12-22, and 192.168.0.0/16-22</p>
<div class="notice" id="cci_01_0001__note1877595182416"><span class="noticetitle"> NOTICE: </span><div class="noticebody"><p id="cci_01_0001__p1677512519243">10.247.0.0/16 is reserved for workloads. If you select this CIDR block, IP address conflicts may occur, which may result in workload creation failure or service unavailability. However, if you do not need to access pods through workloads, you can select this CIDR block.</p>
<p id="cci_01_0001__p137754552418">After the namespace is created, you can view the VPC and subnet by choosing <strong id="cci_01_0001__b91291253163817">Namespaces</strong> &gt; <strong id="cci_01_0001__b15129185343817">Subnet</strong>.</p>
</div></div>
</td>
</tr>
<tr id="cci_01_0001__row1606136131613"><td class="cellrowborder" valign="top" width="24.18%" headers="mcps1.3.6.2.4.2.1.2.3.1.1 "><p id="cci_01_0001__p26062364168">Subnet</p>
</td>
<td class="cellrowborder" valign="top" width="75.82%" headers="mcps1.3.6.2.4.2.1.2.3.1.2 "><p id="cci_01_0001__p12606163617165">Select the subnet where the workloads are running. If no subnet is available, create one first. The subnet cannot be changed once selected.</p>
<ul id="cci_01_0001__ul19477228122513"><li id="cci_01_0001__li9477132820257">Some IP addresses (<strong id="cci_01_0001__b358112818418">10</strong> by default) in the subnet will be warmed up for the namespace.</li><li id="cci_01_0001__li247772810252">You can set the number of IP addresses to be warmed up in <a href="#cci_01_0001__li9748113803217">Advanced Settings</a>.</li><li id="cci_01_0001__li347714289256">If warming up IP addresses for the namespace is enabled, the VPC and subnet can only be deleted after the namespace is deleted.</li></ul>
<div class="note" id="cci_01_0001__note1066635818247"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cci_01_0001__p116665587240">Sufficient available IP addresses in the subnet are required for creating workloads.</p>
</div></div>
</td>
</tr>
<tr id="cci_01_0001__row1960633671616"><td class="cellrowborder" valign="top" width="24.18%" headers="mcps1.3.6.2.4.2.1.2.3.1.1 "><p id="cci_01_0001__p7606133661613">Security Group</p>
</td>
<td class="cellrowborder" valign="top" width="75.82%" headers="mcps1.3.6.2.4.2.1.2.3.1.2 "><p id="cci_01_0001__p146062036181614">Select a security group. If no security group is available, create one first. The security group cannot be changed once selected.</p>
</td>
</tr>
</tbody>
</table>
</div>
</p></li><li id="cci_01_0001__li9748113803217"><a name="cci_01_0001__li9748113803217"></a><a name="li9748113803217"></a><span>(Optional) Advanced Settings</span><p><p id="cci_01_0001__p1497114552814">Each namespace provides an IP pool. You can specify the pool size to reduce the duration for assigning IP addresses and speed up the workload creation.</p>
<p id="cci_01_0001__p797184572816">For example, 200 pods are running routinely, and 200 IP addresses are required in the IP pool. During peak hours, the IP pool instantly scales out to provide 500 IP addresses. After a specified interval (for example, 23 hours), the IP addresses that exceed the pool size (500 – 200 = 300) will be recycled.</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cci_01_0001__table469361310272" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Advanced namespace settings</caption><thead align="left"><tr id="cci_01_0001__row1069411311270"><th align="left" class="cellrowborder" valign="top" width="50%" id="mcps1.3.6.2.5.2.3.2.3.1.1"><p id="cci_01_0001__p1694613112716">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="50%" id="mcps1.3.6.2.5.2.3.2.3.1.2"><p id="cci_01_0001__p8694013172711">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="cci_01_0001__row11694113142719"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.6.2.5.2.3.2.3.1.1 "><p id="cci_01_0001__p8694131302713">IP Pool Warm-up for Namespace</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.6.2.5.2.3.2.3.1.2 "><p id="cci_01_0001__p15674345163017">An IP pool is provided for each namespace, with the number of IP addresses you specify here, and IP addresses will be assigned in advance to accelerate workload creation.</p>
<p id="cci_01_0001__p0694313142715">An IP pool can contain a maximum of 500 IP addresses.</p>
</td>
</tr>
<tr id="cci_01_0001__row116941813142718"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.6.2.5.2.3.2.3.1.1 "><p id="cci_01_0001__p83515213308">IP Address Recycling Interval (h)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.6.2.5.2.3.2.3.1.2 "><p id="cci_01_0001__p1479021872919">Warmed-up IP addresses that become idle can be recycled within the duration you specify here.</p>
</td>
</tr>
</tbody>
</table>
</div>
</p></li><li id="cci_01_0001__li191084495496"><span>Click <span class="uicontrol" id="cci_01_0001__uicontrol2966124019519"><b>OK</b></span>.</span><p><p id="cci_01_0001__p845844016910">You can view the VPC and subnet on the namespace details page.</p>
</p></li></ol>
</div>
<div class="section" id="cci_01_0001__section1124711314815"><h4 class="sectiontitle">Deleting a Namespace</h4><div class="notice" id="cci_01_0001__note13768144414178"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><ul id="cci_01_0001__ul92063565202"><li id="cci_01_0001__li420613562208">Deleting a namespace will delete all resources (such as pods, ConfigMaps, and secrets) related to the namespace.</li><li id="cci_01_0001__li02061556202011">Cascading deletion of workloads and services is not supported after a namespace is deleted.</li><li id="cci_01_0001__li8573237185018">After a namespace is deleted, if a namespace with the same name is created immediately, 409 Conflict may be returned because it takes a while to delete a namespace. Create the namespace about 30 seconds later.</li></ul>
</div></div>
<ol id="cci_01_0001__ol81027211492"><li id="cci_01_0001__li181029219919"><span>Log in to the CCI console. In the navigation pane on the left, choose <strong id="cci_01_0001__b5353352153718">Namespaces</strong>.</span></li><li id="cci_01_0001__li1315084818910"><span>On the <strong id="cci_01_0001__b1190634515543">Namespaces</strong> page, locate the namespace you want to delete and click <strong id="cci_01_0001__b104748180544">Delete</strong> in the <strong id="cci_01_0001__b246942119540">Operation</strong> column. In the <strong id="cci_01_0001__b36284116465">Delete Namespace</strong> dialog box, enter <strong id="cci_01_0001__b19167739145514">DELETE</strong> and click <strong id="cci_01_0001__b13756114319557">OK</strong>.</span><p><div class="note" id="cci_01_0001__note10143135141916"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cci_01_0001__p1013160101818">To delete a VPC or subnet, go to the VPC console.</p>
</div></div>
</p></li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0000001971717269.html">Namespaces</a></div>
</div>
</div>

13
docs/cci/umn/cci_01_0003.html Normal file
View File

@ -0,0 +1,13 @@
<a name="cci_01_0003"></a><a name="cci_01_0003"></a>
<h1 class="topictitle1">Environment Configuration</h1>
<div id="body1516175174294"><div class="section" id="cci_01_0003__section581574714377"><h4 class="sectiontitle">Logging In to the CCI Console</h4><p id="cci_01_0003__p1229816521374">Log in to the CCI console and grant CCI the permissions to access other cloud services.</p>
</div>
<ol id="cci_01_0003__en-us_topic_0076770269_ol44768577204311"><li id="cci_01_0003__en-us_topic_0076770269_li2628738015918"><span id="cci_01_0003__p994113421013">Switch to the CCI console.</span></li><li id="cci_01_0003__li1892950164013"><span>If this is the first time you are logging in to the CCI console, click <strong id="cci_01_0003__b555617451817">Agree</strong> to grant CCI the permissions to access other cloud services.</span><p><p id="cci_01_0003__p16858112964718">After the permissions are granted, an agency named <strong id="cci_01_0003__b1866011042710">cci_admin_trust</strong> is created. You can view the agency on the IAM console.</p>
</p></li></ol>
<div class="section" id="cci_01_0003__section1593133403517"><h4 class="sectiontitle">(Optional) Uploading Images</h4><p id="cci_01_0003__p6557630164718">The cloud platform provides the SoftWare Repository for Container (SWR) service for you to upload container images to the image repository. You can easily pull these images when creating workloads on CCI. For details about how to upload images, see <a href="https://docs.otc.t-systems.com/software-repository-container/umn/image_management/uploading_an_image_through_the_client.html" target="_blank" rel="noopener noreferrer">Uploading an Image Through the Client</a>.</p>
<div class="notice" id="cci_01_0003__note1068691534313"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="cci_01_0003__p4841646155320">Currently, CCI does not support third-party image repositories.</p>
</div></div>
</div>
</div>

13
docs/cci/umn/cci_01_0033.html Normal file
View File

@ -0,0 +1,13 @@
<a name="cci_01_0033"></a><a name="cci_01_0033"></a>
<h1 class="topictitle1">Configuration Center</h1>
<div id="body0000001704131226"></div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="cci_01_0034.html">ConfigMaps</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cci_01_0035.html">Secrets</a></strong><br>
</li>
</ul>
</div>

50
docs/cci/umn/cci_01_0034.html Normal file
View File

@ -0,0 +1,50 @@
<a name="cci_01_0034"></a><a name="cci_01_0034"></a>
<h1 class="topictitle1">ConfigMaps</h1>
<div id="body0000001751811141"><p id="cci_01_0034__p1945294919171">ConfigMaps are objects that you can use to store the configurations required by applications. After you create a ConfigMap, you can use it as a file in a containerized application.</p>
<div class="section" id="cci_01_0034__section18512531861"><a name="cci_01_0034__section18512531861"></a><a name="section18512531861"></a><h4 class="sectiontitle">Creating a ConfigMap</h4><ol id="cci_01_0034__ol18179910114616"><li id="cci_01_0034__li383017919498"><span>Log in to the CCI console. In the navigation pane on the left, choose <strong id="cci_01_0034__b284812351505">Configuration Center</strong>.</span></li><li id="cci_01_0034__li7850191719494"><span>Select a namespace and click the <strong id="cci_01_0034__b126001904511">ConfigMaps</strong> tab.</span></li><li id="cci_01_0034__li1320512613497"><span>Click <strong id="cci_01_0034__b14540529135820">Create from YAML</strong> in the upper left corner and edit the YAML file. For details about the YAML file, see <a href="#cci_01_0034__li5976173124010">YAML format</a>.</span><p><div class="note" id="cci_01_0034__note176631439613"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cci_01_0034__p1266333920117">CCI supports both JSON and YAML, and the file size cannot exceed 1 MB.</p>
</div></div>
</p></li><li id="cci_01_0034__li17271833124810"><span>Click <span class="uicontrol" id="cci_01_0034__uicontrol127555716018"><b>OK</b></span>.</span></li></ol>
</div>
<div class="section" id="cci_01_0034__section152761334151217"><h4 class="sectiontitle">Using a ConfigMap</h4><p id="cci_01_0034__p315717459125">After a ConfigMap is created, you can mount it to a container as a storage volume during pod creation. For example, mount a ConfigMap named <strong id="cci_01_0034__b195611331349">system-preset-aeskey</strong> to a container and set the storage volume name to <strong id="cci_01_0034__b11318012419">volume1</strong>.</p>
<p id="cci_01_0034__p092318591229"></p>
</div>
<div class="section" id="cci_01_0034__section18975165217385"><h4 class="sectiontitle">ConfigMap File Format</h4><p id="cci_01_0034__en-us_topic_0059326569_p35846391135">A ConfigMap resource file must be in either JSON or YAML format, and the file size cannot exceed 1 MB.</p>
<ul id="cci_01_0034__ul829615584011"><li id="cci_01_0034__li129619584020">JSON format<p id="cci_01_0034__en-us_topic_0059326569_p19584439031"><a name="cci_01_0034__li129619584020"></a><a name="li129619584020"></a>Example file: <strong id="cci_01_0034__b474121758">configmap.json</strong></p>
<pre class="screen" id="cci_01_0034__sba22796d7ba24e8f86496dfbfa1c9cb6">{
"kind": "ConfigMap",
"apiVersion": "v1",
"metadata": {
"name": "nginxconf",
"namespace": "cci-namespace-demo"
},
"data": {
"nginx.conf": "server {\n listen 80;\n server_name localhost;\n\n location / {\n root html;\n index index.html index.htm;\n }\n}"
}
}</pre>
</li><li id="cci_01_0034__li5976173124010"><a name="cci_01_0034__li5976173124010"></a><a name="li5976173124010"></a>YAML format<div class="p" id="cci_01_0034__en-us_topic_0059326569_p155754537311"><a name="cci_01_0034__li5976173124010"></a><a name="li5976173124010"></a>Example file: <strong id="cci_01_0034__b9927204018513">configmap.yaml</strong><pre class="screen" id="cci_01_0034__s854fd638f74b43e4a86b36f64aa3e3dd">kind: ConfigMap
apiVersion: v1
metadata:
name: nginxconf
namespace: cci-namespace-demo
data:
nginx.conf: |-
server {
listen 80;
server_name localhost;
location / {
root html;
index index.html index.htm;
}
}</pre>
</div>
</li></ul>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="cci_01_0033.html">Configuration Center</a></div>
</div>
</div>

64
docs/cci/umn/cci_01_0035.html Normal file
View File

@ -0,0 +1,64 @@
<a name="cci_01_0035"></a><a name="cci_01_0035"></a>
<h1 class="topictitle1">Secrets</h1>
<div id="body0000001703971746"><p id="cci_01_0035__p2879172915531">Secrets are objects that you can use to store sensitive data such as authentication information, certificates, and private keys. You can load a secret to a container as an environment variable when the container is started or mount a secret to a container as a file.</p>
<div class="note" id="cci_01_0035__note2278951132113"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cci_01_0035__p1291018422187">It is recommended that you encrypt the uploaded secrets.</p>
</div></div>
<div class="section" id="cci_01_0035__section18512531861"><a name="cci_01_0035__section18512531861"></a><a name="section18512531861"></a><h4 class="sectiontitle">Creating a Secret</h4><ol id="cci_01_0035__ol18179910114616"><li id="cci_01_0035__li383017919498"><span>Log in to the CCI console. In the navigation pane on the left, choose <strong id="cci_01_0035__b187877526575041">Configuration Center</strong>.</span></li><li id="cci_01_0035__li7850191719494"><span>Select a namespace and click the <strong id="cci_01_0035__b944217510812">Secrets</strong> tab.</span></li><li id="cci_01_0035__li1320512613497"><span>Click <strong id="cci_01_0035__b33901314589">Create from YAML</strong> in the upper left corner and edit the YAML file. For details about the YAML file, see <a href="#cci_01_0035__li6120118172019">YAML format</a>.</span><p><div class="note" id="cci_01_0035__note176631439613"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cci_01_0035__p1266333920117">CCI supports both JSON and YAML, and the file size cannot exceed 2 MB.</p>
</div></div>
</p></li><li id="cci_01_0035__li4706172635214"><span>Click <span class="uicontrol" id="cci_01_0035__uicontrol1167318030811"><b>OK</b></span>.</span><p><p id="cci_01_0035__p2679728155212">You can view the newly created secret in the secret list.</p>
</p></li></ol>
</div>
<div class="section" id="cci_01_0035__section152761334151217"><h4 class="sectiontitle">Using a Secret</h4><p id="cci_01_0035__p315717459125">After a secret is created, you can mount it to a container as a storage volume during pod creation. For example, mount a secret named <strong id="cci_01_0035__b0120133310129">aksk-secret</strong> to a container and set the storage volume name to <strong id="cci_01_0035__b134853437121">volume2</strong>.</p>
<p id="cci_01_0035__p1738714802520"></p>
</div>
<div class="section" id="cci_01_0035__section96481187193"><h4 class="sectiontitle">Secret File Format</h4><ul id="cci_01_0035__ul1212017811204"><li id="cci_01_0035__li6120118172019"><a name="cci_01_0035__li6120118172019"></a><a name="li6120118172019"></a><span class="filepath" id="cci_01_0035__filepath1281662011312"><b>secret.yaml</b></span> resource description file<p id="cci_01_0035__p36455081918">For example, you can use a secret to obtain the following key-value pairs and encrypt them for an application:</p>
<p id="cci_01_0035__p10651950201914">key1: value1</p>
<p id="cci_01_0035__p46525071912">key2: value2</p>
<p id="cci_01_0035__p196675051915">The <strong id="cci_01_0035__b216411536139">secret.yaml</strong> file is defined as below. (Base64 encoding is required for the value of each key. For details about the Base64 encoding method, see <a href="#cci_01_0035__section175000605919">Base64 Encoding</a>.)</p>
<pre class="screen" id="cci_01_0035__screen8682502193">apiVersion: v1
kind: Secret
metadata:
name: mysecret #Secret name
annotations:
description: "test"
labels:
label-01: value-01
label-02: value-02
data:
key1: dmFsdWUx #Base64 encoding required
key2: dmFsdWUy #Base64 encoding required
type: Opaque #The type must be Opaque.</pre>
</li><li id="cci_01_0035__li28971790206"><span class="filepath" id="cci_01_0035__filepath13489153671618"><b>secret.json</b></span> resource description file<div class="p" id="cci_01_0035__p14208151711216">The content is as follows:<pre class="screen" id="cci_01_0035__screen11209161710213">{
"apiVersion": "v1",
"kind": "Secret",
"metadata": {
"annotations": {
"description": "test"
},
"labels": {
"label-01": "value-01",
"label-02": "value-02"
},
"name": "mysecret"
},
"data": {
"key1": "dmFsdWUx",
"key2": "dmFsdWUy"
},
"type": "Opaque"
}</pre>
</div>
</li></ul>
</div>
<div class="section" id="cci_01_0035__section175000605919"><a name="cci_01_0035__section175000605919"></a><a name="section175000605919"></a><h4 class="sectiontitle">Base64 Encoding</h4><p id="cci_01_0035__p171051722165915">To perform Base64 encoding on a character string, run the <strong id="cci_01_0035__b1028619121717">echo -n </strong><em id="cci_01_0035__i19295195173">{Content to be encoded}</em><strong id="cci_01_0035__b1629719151714"> | base64</strong> command.</p>
<pre class="screen" id="cci_01_0035__screen18124926408">root@ubuntu:~# echo -n "3306" | base64
MzMwNg==</pre>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="cci_01_0033.html">Configuration Center</a></div>
</div>
</div>

157
docs/cci/umn/cci_01_0053.html Normal file
View File

File diff suppressed because it is too large Load Diff

35
docs/cci/umn/cci_03_0000.html Normal file
View File

@ -0,0 +1,35 @@
<a name="cci_03_0000"></a><a name="cci_03_0000"></a>
<h1 class="topictitle1">Change History</h1>
<div id="body0000001955255312">
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cci_03_0000__table15700183215116" frame="border" border="1" rules="all"><thead align="left"><tr id="cci_03_0000__row1270012323513"><th align="left" class="cellrowborder" valign="top" width="21.19%" id="mcps1.3.1.1.3.1.1"><p id="cci_03_0000__p3701143220513"><strong id="cci_03_0000__b10812185955017">Released On</strong></p>
</th>
<th align="left" class="cellrowborder" valign="top" width="78.81%" id="mcps1.3.1.1.3.1.2"><p id="cci_03_0000__p070193212518"><strong id="cci_03_0000__b31976111511">What's New</strong></p>
</th>
</tr>
</thead>
<tbody><tr id="cci_03_0000__row1085517357265"><td class="cellrowborder" valign="top" width="21.19%" headers="mcps1.3.1.1.3.1.1 "><p id="cci_03_0000__p285563582612">2027-08-14</p>
</td>
<td class="cellrowborder" valign="top" width="78.81%" headers="mcps1.3.1.1.3.1.2 "><p id="cci_03_0000__p58550350269">Modified the following:</p>
<ul id="cci_03_0000__ul7336651182612"><li id="cci_03_0000__li9336195119263"><a href="cci_03_0001.html">Overview</a></li></ul>
</td>
</tr>
<tr id="cci_03_0000__row192123153376"><td class="cellrowborder" valign="top" width="21.19%" headers="mcps1.3.1.1.3.1.1 "><p id="cci_03_0000__p1221216154372">2024-07-18</p>
</td>
<td class="cellrowborder" valign="top" width="78.81%" headers="mcps1.3.1.1.3.1.2 "><p id="cci_03_0000__p12759342184011">Added the following:</p>
<ul id="cci_03_0000__ul1153721064318"><li id="cci_03_0000__li16537191064319"><a href="en-us_topic_0000001955196756.html">Container Group Overview</a></li></ul>
<p id="cci_03_0000__p31997119382">Modified the following:</p>
<ul id="cci_03_0000__ul117824170619"><li id="cci_03_0000__li176572164311"><a href="cci_03_0007.html">Constraints</a></li></ul>
<ul id="cci_03_0000__ul1132502011436"><li id="cci_03_0000__li12325122094310"><a href="cci_01_0053.html">Creating a Container Group</a></li></ul>
</td>
</tr>
<tr id="cci_03_0000__row1416781274311"><td class="cellrowborder" valign="top" width="21.19%" headers="mcps1.3.1.1.3.1.1 "><p id="cci_03_0000__p7794151694314">2024-05-10</p>
</td>
<td class="cellrowborder" valign="top" width="78.81%" headers="mcps1.3.1.1.3.1.2 "><p id="cci_03_0000__p147944160433">This issue is the first official release.</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>

22
docs/cci/umn/cci_03_0001.html Normal file
View File

@ -0,0 +1,22 @@
<a name="cci_03_0001"></a><a name="cci_03_0001"></a>
<h1 class="topictitle1">Overview</h1>
<div id="body39451090"><div class="section" id="cci_03_0001__section1367401111913"><h4 class="sectiontitle">What Is CCI</h4><p id="cci_03_0001__p987912389242">Cloud Container Instance (CCI) is a serverless container engine that allows you to run containers without creating or managing server clusters.</p>
<p id="cci_03_0001__p1233048101711">Traditionally, to run containerized workloads, you need to create a server cluster first. In the serverless model, a cloud provider runs servers and dynamically allocates resources so that you can build and run applications without having to worry about server statuses. This model helps you improve development efficiency and reduce IT costs.</p>
<p id="cci_03_0001__p1199361912526">CCI uses the serverless model that allows you to directly create and use containerized workloads on the console, using kubectl, or by calling APIs, and pay only for the resources consumed by these workloads.</p>
<div class="note" id="cci_03_0001__note20522102620818"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cci_03_0001__p85221261485">CCI is in the beta phase. To use the service, contact customer service.</p>
</div></div>
</div>
<div class="section" id="cci_03_0001__section1832510543616"><h4 class="sectiontitle">Functions</h4><p id="cci_03_0001__p1289975264510"><strong id="cci_03_0001__b39771458332">One-Stop Container Lifecycle Management</strong></p>
<p id="cci_03_0001__p1899155211458">CCI allows you to run containers without creating or managing server clusters. In the serverless model, you can deploy and run workloads on the console, using kubectl, or by calling APIs, and pay only for the resources consumed by these workloads.</p>
</div>
<div class="section" id="cci_03_0001__section218752373612"><h4 class="sectiontitle">Architecture</h4><p id="cci_03_0001__p1622371622413">CCI is a serverless container service. It allows you to create large-scale converged resource pools using the cell-based architecture. It also integrates network and storage services of the cloud platform to allow you to easily deploy and run containerized workloads through the console, kubectl, and APIs.</p>
<ul id="cci_03_0001__ul79741255372"><li id="cci_03_0001__li2974175519710">CCI works with network and storage services of the cloud platform to provide robust network and storage performance.</li><li id="cci_03_0001__li91901840815">The QingTian architecture with hardware and software collaboration brings ultimate performance and user experience.</li><li id="cci_03_0001__li939133883319">Virtualization provides security isolation and works with in-house hardware virtualization acceleration technologies to allow you to create high-performance pods for running your workloads.</li><li id="cci_03_0001__li926795063317">With unified resource management and workload scheduling, you do not need to manage clusters.</li><li id="cci_03_0001__li1669172153419">Capabilities, such as quick workload deployment, elastic load balancing, and fast auto scaling, can iterate services quickly.</li></ul>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="cci_03_1000.html">Service Overview</a></div>
</div>
</div>

17
docs/cci/umn/cci_03_0003.html Normal file
View File

@ -0,0 +1,17 @@
<a name="cci_03_0003"></a><a name="cci_03_0003"></a>
<h1 class="topictitle1">Advantages</h1>
<div id="body1518060471944"><div class="section" id="cci_03_0003__section14169558143312"><h4 class="sectiontitle">Out of the Box</h4><p id="cci_03_0003__p9396171653615">CCI provides an industry-leading serverless container architecture, so you do not need to create server clusters. Instead, you can create large-scale converged resource pools using the cell-based architecture. CCI also integrates network and storage services to allow you to easily deploy and run containerized workloads through the console, kubectl, and APIs.</p>
</div>
<div class="section" id="cci_03_0003__section894512383224"><h4 class="sectiontitle">Fast Auto Scaling</h4><p id="cci_03_0003__p99131934152014">Resources are unlimited from a single user's perspective and can be scaled in seconds, helping you cope with service changes and ensure SLAs.</p>
</div>
<div class="section" id="cci_03_0003__section1360372611228"><h4 class="sectiontitle">High Security</h4><p id="cci_03_0003__p3741911198">CCI provides VM-level isolation without compromising the startup speed, offering you better container experience. CCI has the following security features:</p>
<ul id="cci_03_0003__ul71961323193016"><li id="cci_03_0003__li12196102363014">Virtualization is supported.</li><li id="cci_03_0003__li171962023113011">Kernel virtualization based on secure containers provides comprehensive security isolation.</li><li id="cci_03_0003__li15197172319303">In-house virtualization acceleration technologies improve the virtualization performance.</li></ul>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="cci_03_1000.html">Service Overview</a></div>
</div>
</div>

24
docs/cci/umn/cci_03_0004.html Normal file
View File

@ -0,0 +1,24 @@
<a name="cci_03_0004"></a><a name="cci_03_0004"></a>
<h1 class="topictitle1">Application Scenarios</h1>
<div id="body1518060471944"><div class="section" id="cci_03_0004__section1511653174111"><h4 class="sectiontitle">Scientific Computing</h4><p id="cci_03_0004__p579615415429">Scientific R&amp;D in fields such as genomics and drug development requires high-performance and high-density computing. In addition, scientific computing is generally task-based and requires quick resource allocation and release. Therefore, a low-cost computing platform with automated O&amp;M is required.</p>
<p id="cci_03_0004__p45661435590">The following CCI features make it suitable for computing in this scenario:</p>
<ul id="cci_03_0004__ul363813681411"><li id="cci_03_0004__li1963814364146">High-performance computing and network, and high I/O storage</li><li id="cci_03_0004__li56387368146">Resource scaling in seconds minimizes resource consumption</li><li id="cci_03_0004__li1463814363145">No O&amp;M required for clusters and servers, greatly reducing O&amp;M costs</li></ul>
</div>
<div class="section" id="cci_03_0004__section173351217204210"><h4 class="sectiontitle"><strong id="cci_03_0004__b0233181132815">DevOps/Continuous Delivery</strong></h4><p id="cci_03_0004__p258133224219">Software development enterprises need complete DevOps processes from code submission to application deployment to improve the development efficiency. DevOps processes such as continuous integration/continuous delivery (CI/CD) are generally task-based computing and require quick resource allocation and release.</p>
<p id="cci_03_0004__p7322914175">The following CCI features make it suitable for computing in this scenario:</p>
<ul id="cci_03_0004__ul17963183810186"><li id="cci_03_0004__li19963153811188">Automation for the entire CI/CD process, with no cluster creation and maintenance required</li><li id="cci_03_0004__li20963113811187">Image-based delivery, allowing for consistency between the development and production environments</li></ul>
<div class="fignone" id="cci_03_0004__fig967071601916"><span class="figcap"><b>Figure 1 </b>DevOps/Continuous delivery</span><br><span><img id="cci_03_0004__image197671721465" src="en-us_image_0197840533.png"></span></div>
</div>
<div class="section" id="cci_03_0004__section11833448204219"><h4 class="sectiontitle">Services with Fluctuating Traffic</h4><p id="cci_03_0004__p9387183174316">Some types of applications, such as live video, media information, e-commerce, and online education, have obvious service peaks and troughs. For these applications, resources need to be expanded rapidly during peak hours without breaking the bank.</p>
<p id="cci_03_0004__p111521413152411">The following CCI features make it suitable for these applications:</p>
<ul id="cci_03_0004__ul994983213247"><li id="cci_03_0004__li39493321244"><strong id="cci_03_0004__b1330141110345">Fast scaling</strong>: CCI can quickly take over services from CCE to ensure uptime during peak hours.</li></ul>
<div class="fignone" id="cci_03_0004__fig15337188132713"><span class="figcap"><b>Figure 2 </b>Auto scaling</span><br><span><img id="cci_03_0004__image1278015258487" src="en-us_image_0197840757.png"></span></div>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="cci_03_1000.html">Service Overview</a></div>
</div>
</div>

33
docs/cci/umn/cci_03_0005.html Normal file
View File

@ -0,0 +1,33 @@
<a name="cci_03_0005"></a><a name="cci_03_0005"></a>
<h1 class="topictitle1">Basic Concepts</h1>
<div id="body1544520355481"><p id="cci_03_0005__p69967501167">CCI provides enhanced features, such as security isolation, fast workload deployment, elastic load balancing, and auto scaling.</p>
<p id="cci_03_0005__p18224445616">The graphical CCI console provides end-to-end user experience. In addition, CCI supports native APIs and kubectl. Before using CCI, you are advised to understand related basic concepts.</p>
<div class="section" id="cci_03_0005__section08921420185317"><h4 class="sectiontitle">Image</h4><p id="cci_03_0005__p183442245533">A container image is a special file system that provides the programs, libraries, resources, and configuration files required for running a container. It also contains configuration parameters, for example, anonymous volumes, environment variables, and users. An image does not contain any dynamic data, and its content will not be changed after creation.</p>
</div>
<div class="section" id="cci_03_0005__section97111729145312"><h4 class="sectiontitle">Container</h4><p id="cci_03_0005__p10716143713532">The relationship between an image and a container is similar to that between a class and an instance in object-oriented programming. Images are static, and containers are entities of running images. A container can be created, started, stopped, deleted, and suspended.</p>
</div>
<div class="section" id="cci_03_0005__section1611125018"><h4 class="sectiontitle">Namespace</h4><p id="cci_03_0005__p366216366496">A namespace provides a method of allocating resources among multiple users. When you have a large number of projects and personnel, you can define namespaces by project attributes, such as production, test, and development.</p>
</div>
<div class="section" id="cci_03_0005__section233315103516"><h4 class="sectiontitle">Pod</h4><p id="cci_03_0005__p356108173515">A pod is the smallest deployable unit of computing that you can create and manage. A pod is a group of one or more containers, with shared storage resources, a unique IP address, and a specification for how to run the containers.</p>
<div class="fignone" id="cci_03_0005__fig376711716199"><span class="figcap"><b>Figure 1 </b>Pod</span><br><span><img id="cci_03_0005__image177701028165017" src="en-us_image_0197841641.png"></span></div>
<p id="cci_03_0005__p4629172611480">Pods can be used in either of the following ways:</p>
<ul id="cci_03_0005__ul062982617481"><li id="cci_03_0005__li1629172611482">One pod that runs a single container: This is the most common use case. You can think of a pod as a wrapper around a single container, but pods can be managed directly rather than containers.</li><li id="cci_03_0005__li1962932615480">Pods that run multiple containers that need to work together:</li></ul>
<p id="cci_03_0005__p66785185206">Pods are rarely created directly. Instead, controllers such as Deployments are used to create and manage pods. Controllers create and manage multiple pods, and provide replica management, rolling upgrade, and self-healing capabilities. A controller typically uses a pod template to create corresponding pods.</p>
</div>
<div class="section" id="cci_03_0005__section98701316165813"><h4 class="sectiontitle">Label</h4><p id="cci_03_0005__p74758810716">A label is a key-value pair attached to an object and is used to transfer user-defined attributes.</p>
<p id="cci_03_0005__p74753818712">Labels are often used to select objects that meet conditions from a group of objects. Labels are currently the most important node grouping method.</p>
<p id="cci_03_0005__p1499211191580">For example, you may create labels (<strong id="cci_03_0005__b18810161163219">tier</strong>=frontend, <strong id="cci_03_0005__b987918553213">app</strong>=myapp) to mark frontend pods and labels (<strong id="cci_03_0005__b1639233323211">tier</strong>=backend, <strong id="cci_03_0005__b1649903983217">app</strong>=myapp) to mark backend pods. You can then use selectors to select pods with specific labels and apply services or Deployments to these pods.</p>
<div class="fignone" id="cci_03_0005__fig6404142813489"><span class="figcap"><b>Figure 2 </b>Pods organized with labels</span><br><span><img id="cci_03_0005__image101661511298" src="en-us_image_0197831172.png"></span></div>
</div>
<div class="section" id="cci_03_0005__section1393019326309"><h4 class="sectiontitle">ConfigMap</h4><p id="cci_03_0005__p17252111374115">A ConfigMap is used to store configuration data as key-value pairs or configuration files. ConfigMaps are similar to secrets, but provide a means of working with strings that do not contain sensitive information.</p>
</div>
<div class="section" id="cci_03_0005__section121677384302"><h4 class="sectiontitle">Secret</h4><p id="cci_03_0005__p133541154183013">A secret is an object for storing sensitive data such as authentication information, certificates, and private keys. A secret can be loaded to a container as environment variables when the container is started.</p>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="cci_03_1000.html">Service Overview</a></div>
</div>
</div>

24
docs/cci/umn/cci_03_0006.html Normal file
View File

@ -0,0 +1,24 @@
<a name="cci_03_0006"></a><a name="cci_03_0006"></a>
<h1 class="topictitle1">Related Services</h1>
<div id="body1544520355497"><p id="cci_03_0006__p13210141395319">CCI needs to be interconnected with the following cloud services. It requires permissions to access these cloud services.</p>
<ul id="cci_03_0006__ul11591225194318"><li id="cci_03_0006__li46058587445"><strong id="cci_03_0006__b7506154652716">SWR</strong><p id="cci_03_0006__p411612613451">SoftWare Repository for Container (SWR) provides easy, secure, and reliable management of container images throughout their lifecycles, facilitating quick deployment of containerized services.</p>
<p id="cci_03_0006__p55526964519">You can create workloads using SWR images.</p>
</li><li id="cci_03_0006__li92117261343"><strong id="cci_03_0006__b842352706162146">VPC</strong><p id="cci_03_0006__p11994154016510">Virtual Private Cloud (VPC) allows you to isolate online resources with virtual private networks. You can configure the CIDR block, subnets, and security groups, assign EIPs, and allocate bandwidth for a VPC.</p>
<p id="cci_03_0006__p18972142320612">When creating a namespace, you must associate it with a VPC. All containers to be created in the namespace will run in the VPC.</p>
</li><li id="cci_03_0006__li12102011174819"><strong id="cci_03_0006__b1718171216425">ELB</strong><p id="cci_03_0006__p17130245164815">Elastic Load Balance (ELB) automatically distributes access traffic to multiple Elastic Cloud Servers (ECSs) to balance the loads. It enhances an application's fault tolerance level and capabilities of providing service externally.</p>
<p id="cci_03_0006__p6131345194812">You can access a container workload from an external network through an elastic load balancer.</p>
</li><li id="cci_03_0006__li16775547201117"><strong id="cci_03_0006__b10256553114813">AOM</strong><p id="cci_03_0006__p324711191213">Application Operations Management (AOM) is a one-stop platform for O&amp;M personnel to monitor application and resource operating statuses in real time. By analyzing dozens of metrics, alarms, and logs, you can quickly locate root causes to ensure services run normally.</p>
<p id="cci_03_0006__p3249111125">AOM collects the .log files of containers from CCI to facilitate log query and viewing. In addition, AOM provides resource monitoring to enable CCI to automatically scale resources.</p>
</li><li id="cci_03_0006__li1749795914315"><strong id="cci_03_0006__b66021454181714">ECS</strong><p id="cci_03_0006__p1957838142">Elastic Cloud Server (ECS) allows you to create cloud servers that provide scalable, on-demand computing resources for secure, flexible, and efficient applications.</p>
<p id="cci_03_0006__p1328213752114">CCI imports data to SFS through ECS for container services to use.</p>
</li><li id="cci_03_0006__li8994145514576"><strong id="cci_03_0006__b15321856152518">NAT Gateway</strong><p id="cci_03_0006__p3172135965718">NAT Gateway provides source network address translation (SNAT), which translates private IP addresses to public IP addresses by binding an elastic IP address (EIP) to the gateway.</p>
<p id="cci_03_0006__p2386223115915">You can use NAT Gateway to set SNAT rules to allow containers in a VPC to access the Internet.</p>
</li></ul>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="cci_03_1000.html">Service Overview</a></div>
</div>
</div>

93
docs/cci/umn/cci_03_0007.html Normal file
View File

@ -0,0 +1,93 @@
<a name="cci_03_0007"></a><a name="cci_03_0007"></a>
<h1 class="topictitle1">Constraints</h1>
<div id="body1546827380361"><p id="cci_03_0007__p420413321016">This section describes the constraints on using CCI 2.0.</p>
<div class="section" id="cci_03_0007__section637792717444"><h4 class="sectiontitle">Constraints on CCI 2.0</h4><p id="cci_03_0007__p17774165219440">The following table lists the constraints on CCI 2.0.</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cci_03_0007__table1773418528440" frame="border" border="1" rules="all"><thead align="left"><tr id="cci_03_0007__row137747526445"><th align="left" class="cellrowborder" valign="top" width="32.83%" id="mcps1.3.2.3.1.3.1.1"><p id="cci_03_0007__p1177415522444">Item</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="67.17%" id="mcps1.3.2.3.1.3.1.2"><p id="cci_03_0007__p14774185284418">Constraint</p>
</th>
</tr>
</thead>
<tbody><tr id="cci_03_0007__row4774135214448"><td class="cellrowborder" valign="top" width="32.83%" headers="mcps1.3.2.3.1.3.1.1 "><p id="cci_03_0007__p677475264418">Account for creating CCI instances</p>
</td>
<td class="cellrowborder" valign="top" width="67.17%" headers="mcps1.3.2.3.1.3.1.2 "><p id="cci_03_0007__p197741952204410">The account must have complete real-name authentication.</p>
</td>
</tr>
<tr id="cci_03_0007__row5774185213444"><td class="cellrowborder" valign="top" width="32.83%" headers="mcps1.3.2.3.1.3.1.1 "><p id="cci_03_0007__p13774125264419">Number of vCPUs per CCI instance</p>
</td>
<td class="cellrowborder" valign="top" width="67.17%" headers="mcps1.3.2.3.1.3.1.2 "><p id="cci_03_0007__p1762264374711">0.25, 0.5, 1, 2, 4, 8, 16, 32, 48, and 64</p>
</td>
</tr>
<tr id="cci_03_0007__row127751952184412"><td class="cellrowborder" valign="top" width="32.83%" headers="mcps1.3.2.3.1.3.1.1 "><p id="cci_03_0007__p1477525244410">Supported OS</p>
</td>
<td class="cellrowborder" valign="top" width="67.17%" headers="mcps1.3.2.3.1.3.1.2 "><p id="cci_03_0007__p8775165212446">Only Linux</p>
</td>
</tr>
<tr id="cci_03_0007__row377545264415"><td class="cellrowborder" valign="top" width="32.83%" headers="mcps1.3.2.3.1.3.1.1 "><p id="cci_03_0007__p1177595210449">Network type</p>
</td>
<td class="cellrowborder" valign="top" width="67.17%" headers="mcps1.3.2.3.1.3.1.2 "><p id="cci_03_0007__p977545218444">Only VPC</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="section" id="cci_03_0007__section1815605917231"><h4 class="sectiontitle">Constraints on Pod Flavors</h4><div class="p" id="cci_03_0007__p1398916015241">The following table lists the pod flavors.
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cci_03_0007__table351612179257" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Requirements on pod flavors</caption><thead align="left"><tr id="cci_03_0007__row851631711254"><th align="left" class="cellrowborder" valign="top" width="39.4%" id="mcps1.3.3.2.1.2.3.1.1"><p id="cci_03_0007__p1516101717254">Item</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="60.6%" id="mcps1.3.3.2.1.2.3.1.2"><p id="cci_03_0007__p451691742511">Value Range</p>
</th>
</tr>
</thead>
<tbody><tr id="cci_03_0007__row10516131712259"><td class="cellrowborder" valign="top" width="39.4%" headers="mcps1.3.3.2.1.2.3.1.1 "><p id="cci_03_0007__p7516161712513">Number of vCPUs</p>
</td>
<td class="cellrowborder" valign="top" width="60.6%" headers="mcps1.3.3.2.1.2.3.1.2 "><p id="cci_03_0007__p5883195243810">0.25, 0.5, 1, 2, 4, 8, 16, 32, 48, and 64</p>
</td>
</tr>
<tr id="cci_03_0007__row175168179250"><td class="cellrowborder" valign="top" width="39.4%" headers="mcps1.3.3.2.1.2.3.1.1 "><p id="cci_03_0007__p18516101714254">Memory</p>
</td>
<td class="cellrowborder" valign="top" width="60.6%" headers="mcps1.3.3.2.1.2.3.1.2 "><ul id="cci_03_0007__ul824393132817"><li id="cci_03_0007__li924312362815">1 GiB to 512 GiB</li><li id="cci_03_0007__li324310382815">The memory must be an integer multiple of 1 GiB.</li></ul>
</td>
</tr>
<tr id="cci_03_0007__row1351681792520"><td class="cellrowborder" valign="top" width="39.4%" headers="mcps1.3.3.2.1.2.3.1.1 "><p id="cci_03_0007__p1351619171255">vCPU/memory ratio</p>
</td>
<td class="cellrowborder" valign="top" width="60.6%" headers="mcps1.3.3.2.1.2.3.1.2 "><p id="cci_03_0007__p13516161712258">Between 1:1 and 1:8</p>
</td>
</tr>
<tr id="cci_03_0007__row12516417132510"><td class="cellrowborder" valign="top" width="39.4%" headers="mcps1.3.3.2.1.2.3.1.1 "><p id="cci_03_0007__p1151617171255">Containers in a pod</p>
</td>
<td class="cellrowborder" valign="top" width="60.6%" headers="mcps1.3.3.2.1.2.3.1.2 "><p id="cci_03_0007__p1041871613611">A maximum of five containers</p>
<p id="cci_03_0007__p1751631732517">A single container has as few as 0.25 vCPUs and 0.5 GiB of memory. The maximum resource flavor of a container is the same as that of a pod.</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="section" id="cci_03_0007__section1537316135918"><h4 class="sectiontitle">Constraints on Pod Storage Space</h4><p id="cci_03_0007__p12832143317494">If no EVS disk is mounted, application data is stored in the rootfs of the container. The following table lists the storage space limit of each pod.</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cci_03_0007__table116726413504" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Storage space limit of each type of pod</caption><thead align="left"><tr id="cci_03_0007__row1467214165016"><th align="left" class="cellrowborder" valign="top" width="50%" id="mcps1.3.4.3.2.3.1.1"><p id="cci_03_0007__p1067354112503">Pod Type</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="50%" id="mcps1.3.4.3.2.3.1.2"><p id="cci_03_0007__p14673541135016">Storage Space</p>
</th>
</tr>
</thead>
<tbody><tr id="cci_03_0007__row5673134117503"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.3.2.3.1.1 "><p id="cci_03_0007__p19673241135018">General-computing pod</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.3.2.3.1.2 "><p id="cci_03_0007__p76735411508">30 GB</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="cci_03_1000.html">Service Overview</a></div>
</div>
</div>

863
docs/cci/umn/cci_03_0008.html Normal file
View File

File diff suppressed because it is too large Load Diff

22
docs/cci/umn/cci_03_0010.html Normal file
View File

@ -0,0 +1,22 @@
<a name="cci_03_0010"></a><a name="cci_03_0010"></a>
<h1 class="topictitle1">Region and AZ</h1>
<div id="body8662426"><div class="section" id="cci_03_0010__en-us_topic_0184026189_section388255972712"><h4 class="sectiontitle">Concept</h4><p id="cci_03_0010__en-us_topic_0184026189_p212716216381">A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.</p>
<ul id="cci_03_0010__en-us_topic_0184026189_ul86578533460"><li id="cci_03_0010__en-us_topic_0184026189_li14657175334618">A region is a physical data center, which is completely isolated to improve fault tolerance and stability. The region that is selected during resource creation cannot be changed after the resource is created.</li><li id="cci_03_0010__en-us_topic_0184026189_li45875020473">An AZ is a physical location where resources use independent power supplies and networks. A region contains one or more AZs that are physically isolated but interconnected through internal networks. Because AZs are isolated from each other, any fault that occurs in one AZ will not affect others.</li></ul>
<p id="cci_03_0010__en-us_topic_0184026189_p1479174514614"><a href="#cci_03_0010__en-us_topic_0184026189_fig8747114281212">Figure 1</a> shows the relationship between regions and AZs.</p>
<div class="fignone" id="cci_03_0010__en-us_topic_0184026189_fig8747114281212"><a name="cci_03_0010__en-us_topic_0184026189_fig8747114281212"></a><a name="en-us_topic_0184026189_fig8747114281212"></a><span class="figcap"><b>Figure 1 </b>Regions and AZs</span><br><span><img class="vsd" id="cci_03_0010__en-us_topic_0184026189_image12748194211128" src="en-us_image_0184026531.png"></span></div>
</div>
<div class="section" id="cci_03_0010__en-us_topic_0184026189_section67281149192216"><h4 class="sectiontitle">Selecting a Region</h4><p id="cci_03_0010__en-us_topic_0184026189_p68521454132212">Select a region closest to your target users for lower network latency and quick access.</p>
</div>
<div class="section" id="cci_03_0010__en-us_topic_0184026189_section193971112578"><h4 class="sectiontitle">Selecting an AZ</h4><p id="cci_03_0010__en-us_topic_0184026189_p859161416717">When deploying resources, consider your applications' requirements on disaster recovery (DR) and network latency.</p>
<ul id="cci_03_0010__en-us_topic_0184026189_ul157203571473"><li id="cci_03_0010__en-us_topic_0184026189_li7720175710711">For high DR capability, deploy resources in different AZs within the same region.</li><li id="cci_03_0010__en-us_topic_0184026189_li109763595719">For lower network latency, deploy resources in the same AZ.</li></ul>
</div>
<div class="section" id="cci_03_0010__en-us_topic_0184026189_section1110135820407"><h4 class="sectiontitle">Regions and Endpoints</h4><p id="cci_03_0010__en-us_topic_0184026189_p361784821111">Before you use an API to call resources, specify its region and endpoint. For more details, see <a href="https://docs.otc.t-systems.com/regions-and-endpoints/index.html" target="_blank" rel="noopener noreferrer">Regions and Endpoints</a>.</p>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="cci_03_1000.html">Service Overview</a></div>
</div>
</div>

25
docs/cci/umn/cci_03_1000.html Normal file
View File

@ -0,0 +1,25 @@
<a name="cci_03_1000"></a><a name="cci_03_1000"></a>
<h1 class="topictitle1">Service Overview</h1>
<div id="body39451090"></div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="cci_03_0001.html">Overview</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cci_03_0003.html">Advantages</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cci_03_0004.html">Application Scenarios</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cci_03_0005.html">Basic Concepts</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cci_03_0008.html">Permissions Management</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cci_03_0007.html">Constraints</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cci_03_0010.html">Region and AZ</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cci_03_0006.html">Related Services</a></strong><br>
</li>
</ul>
</div>

BIN
docs/cci/umn/en-us_image_0000001991238669.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 7.5 KiB

BIN
docs/cci/umn/en-us_image_0184026531.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 3.4 KiB

BIN
docs/cci/umn/en-us_image_0197831172.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 19 KiB

BIN
docs/cci/umn/en-us_image_0197840533.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 10 KiB

BIN
docs/cci/umn/en-us_image_0197840757.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 6.8 KiB

BIN
docs/cci/umn/en-us_image_0197841641.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 6.1 KiB

BIN
docs/cci/umn/en-us_image_0201693831.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 2.0 KiB

15
docs/cci/umn/en-us_topic_0000001955196756.html Normal file
View File

@ -0,0 +1,15 @@
<a name="EN-US_TOPIC_0000001955196756"></a><a name="EN-US_TOPIC_0000001955196756"></a>
<h1 class="topictitle1">Overview</h1>
<div id="body0000001955196756"><div class="section" id="EN-US_TOPIC_0000001955196756__section75255539102"><h4 class="sectiontitle">What Is a Pod or Container Group?</h4><p id="EN-US_TOPIC_0000001955196756__en-us_topic_0116111750_p356108173515">Pods (or container groups) are the smallest deployable units of computing that you can create and manage. A pod or a container group is a group of one or more containers, with shared storage, a unique IP address, and a specification for how to run the containers.</p>
<p id="EN-US_TOPIC_0000001955196756__en-us_topic_0116111750_p4629172611480">Pods can be used in either of the following ways:</p>
<ul id="EN-US_TOPIC_0000001955196756__en-us_topic_0116111750_ul062982617481"><li id="EN-US_TOPIC_0000001955196756__en-us_topic_0116111750_li1629172611482">A pod runs a single container. This is the most common use case. You can consider a pod as a wrapper around a single container. Pods can be managed directly rather than containers.</li><li id="EN-US_TOPIC_0000001955196756__en-us_topic_0116111750_li1962932615480">A pod runs multiple containers that need to work together. In this scenario, a pod can encapsulate an application that is running in a main container and several sidecar containers. As shown in <a href="#EN-US_TOPIC_0000001955196756__en-us_topic_0116111750_fig347141918551">Figure 1</a>, the main container serves as a web server that provides file services from a fixed directory, and the sidecar container periodically downloads files to the directory.<div class="fignone" id="EN-US_TOPIC_0000001955196756__en-us_topic_0116111750_fig347141918551"><a name="EN-US_TOPIC_0000001955196756__en-us_topic_0116111750_fig347141918551"></a><a name="en-us_topic_0116111750_fig347141918551"></a><span class="figcap"><b>Figure 1 </b>Pod</span><br><span><img id="EN-US_TOPIC_0000001955196756__en-us_topic_0116111750_image179071111185220" src="en-us_image_0000001991238669.png"></span></div>
</li></ul>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0000001975803021.html">Container Group</a></div>
</div>
</div>

15
docs/cci/umn/en-us_topic_0000001971717269.html Normal file
View File

@ -0,0 +1,15 @@
<a name="EN-US_TOPIC_0000001971717269"></a><a name="EN-US_TOPIC_0000001971717269"></a>
<h1 class="topictitle1">Namespaces</h1>
<div id="body0000001971717269"><p id="EN-US_TOPIC_0000001971717269__p8060118"></p>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="cci_01_0001.html">Creating a Namespace</a></strong><br>
</li>
</ul>
</div>

14
docs/cci/umn/en-us_topic_0000001975803021.html Normal file
View File

@ -0,0 +1,14 @@
<a name="EN-US_TOPIC_0000001975803021"></a><a name="EN-US_TOPIC_0000001975803021"></a>
<h1 class="topictitle1">Container Group</h1>
<div id="body0000001975803021"><p id="EN-US_TOPIC_0000001975803021__p8060118"></p>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="en-us_topic_0000001955196756.html">Overview</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cci_01_0053.html">Creating a Container Group</a></strong><br>
</li>
</ul>
</div>

BIN
docs/cci/umn/public_sys-resources/caution_3.0-en-us.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 2.7 KiB

BIN
docs/cci/umn/public_sys-resources/danger_3.0-en-us.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 2.7 KiB

BIN
docs/cci/umn/public_sys-resources/delta.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 836 B

BIN
docs/cci/umn/public_sys-resources/deltaend.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 834 B

BIN
docs/cci/umn/public_sys-resources/icon-arrowdn.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.8 KiB

BIN
docs/cci/umn/public_sys-resources/icon-arrowrt.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.8 KiB

BIN
docs/cci/umn/public_sys-resources/icon-caution.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.1 KiB

BIN
docs/cci/umn/public_sys-resources/icon-danger.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.1 KiB

BIN
docs/cci/umn/public_sys-resources/icon-huawei.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 2.7 KiB

BIN
docs/cci/umn/public_sys-resources/icon-note.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 983 B

BIN
docs/cci/umn/public_sys-resources/icon-notice.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 962 B

BIN
docs/cci/umn/public_sys-resources/icon-tip.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 879 B

BIN
docs/cci/umn/public_sys-resources/icon-warning.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.1 KiB

BIN
docs/cci/umn/public_sys-resources/note_3.0-en-us.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.1 KiB

BIN
docs/cci/umn/public_sys-resources/notice_3.0-en-us.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.6 KiB

BIN
docs/cci/umn/public_sys-resources/warning_3.0-en-us.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 3.1 KiB