forked from docs/doc-exports
CCE API 20231108 version
Reviewed-by: Eotvos, Oliver <oliver.eotvos@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:
parent
4b019093fa
commit
61a61f01a7
File diff suppressed because it is too large
Load Diff
@ -829,29 +829,6 @@
|
||||
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.3.20.2.5.1.4 "><p id="AddNode__p1634016791518">Maximum number of pods that can be created on a node, including the default system pods. Value range: 16 to 256. This limit prevents the node from being overloaded of pods.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="AddNode__row1123918712150"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.20.2.5.1.1 "><p id="AddNode__p43401574159">nicMultiqueue</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.20.2.5.1.2 "><p id="AddNode__p1334015741514">No</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.20.2.5.1.3 "><p id="AddNode__p83401076158">String</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.3.20.2.5.1.4 "><ul id="AddNode__ul143411676155"><li id="AddNode__li13411378151">Number of ENI queues. Example setting:</li></ul>
|
||||
<pre class="screen" id="AddNode__screen3341272157">"[{\"queue\":4}]"</pre>
|
||||
<p id="AddNode__p5341167121517">The following fields are included:</p>
|
||||
<ul id="AddNode__ul334157141518"><li id="AddNode__li15341107111511"><strong id="AddNode__b334120712156">queue</strong>: number of ENI queues.</li><li id="AddNode__li834114771518">This field can be configured only for BMS nodes in a CCE Turbo cluster.</li><li id="AddNode__li14342177151">Supported proportions are {"1":128, "2":92, "4":92, "8":32, "16":16, "28":9}. That is, if there is one queue, a maximum of 128 ENIs can be bound. If there are two queues, a maximum of 92 ENIs can be bound for two queues.</li><li id="AddNode__li113423715157">A larger number of ENI queues indicates higher performance but fewer ENIs can be bound. The queue settings cannot be changed after the node pool is created.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="AddNode__row11239174156"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.20.2.5.1.1 "><p id="AddNode__p434207101512">nicThreshold</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.20.2.5.1.2 "><p id="AddNode__p123422716157">No</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.20.2.5.1.3 "><p id="AddNode__p234215711517">String</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.3.20.2.5.1.4 "><ul id="AddNode__ul934217781518"><li id="AddNode__li9342177161510">ENI pre-binding thresholds. Example setting:</li></ul>
|
||||
<pre class="screen" id="AddNode__screen634320716155">"0.3:0.6"</pre>
|
||||
<ul id="AddNode__ul113432761510"><li id="AddNode__li634313761514">Low threshold (L): determines the minimum number of pre-bound ENIs (Min). Formula: Min = Total number of ENIs of the node x L</li><li id="AddNode__li0343879159">High threshold (H): determines the maximum number of pre-bound ENIs (Max). Formula: Max = Total number of ENIs of the node x H</li><li id="AddNode__li19343107131512">Number of ENIs bound to a BMS node (B) and number of ENIs being used by pods (U): U + Min < B < U + Max</li><li id="AddNode__li43433731512">If the number of pre-bound ENIs on a BMS node is smaller than the minimum allowed, the system will bind more ENIs to make the numbers equal.</li><li id="AddNode__li1334447131518">If the number of pre-bound ENIs on a BMS node is larger than the maximum allowed, the system periodically unbinds ENIs (about every 2 minutes) to make the numbers equal.</li><li id="AddNode__li11344875154">Both the thresholds are one-decimal-place values ranging from 0.0 to 1.0. The low threshold must be smaller than or equal to the high one.</li><li id="AddNode__li1334457101515">This field can be configured only for BMS nodes in a CCE Turbo cluster.</li><li id="AddNode__li234447131513">Pre-binding ENIs can speed up workload creation but occupies IP addresses.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
|
||||
@ -494,6 +494,15 @@
|
||||
"p_code":"45",
|
||||
"code":"55"
|
||||
},
|
||||
{
|
||||
"desc":"Different regions support different node flavors, and node flavors may be changed. You are advised to log in to the CCE console and check whether the required node flavor",
|
||||
"product_code":"cce",
|
||||
"title":"Node Flavor Description",
|
||||
"uri":"cce_02_0368.html",
|
||||
"doc_type":"api2",
|
||||
"p_code":"45",
|
||||
"code":"56"
|
||||
},
|
||||
{
|
||||
"desc":"In disk planning and striped logical disk creation, it is difficult for users to flexibly attach and partition disks when creating a node.During node creation, the storag",
|
||||
"product_code":"cce",
|
||||
@ -501,7 +510,7 @@
|
||||
"uri":"node_storage_example.html",
|
||||
"doc_type":"api2",
|
||||
"p_code":"45",
|
||||
"code":"56"
|
||||
"code":"57"
|
||||
},
|
||||
{
|
||||
"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
|
||||
@ -510,6 +519,6 @@
|
||||
"uri":"cce_02_0273.html",
|
||||
"doc_type":"api2",
|
||||
"p_code":"",
|
||||
"code":"57"
|
||||
"code":"58"
|
||||
}
|
||||
]
|
||||
@ -24,6 +24,8 @@
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_02_0101.html">Creating a Key Pair</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_02_0368.html">Node Flavor Description</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="node_storage_example.html">Attaching Disks to a Node</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
@ -586,8 +586,7 @@
|
||||
"External": "https://10.185.69.54:5443",
|
||||
},
|
||||
{
|
||||
"external_otc": "https://a140174a-2f3e-11e9-9f91-0255ac101405.cce.eu-de.otc.t-systems.com",
|
||||
},
|
||||
"external_otc": "https://a140174a-2f3e-11e9-9f91-0255ac101405.cce.eu-de.otc.t-systems.com", },
|
||||
]
|
||||
}
|
||||
}</pre>
|
||||
|
||||
@ -194,8 +194,7 @@
|
||||
"External": "https://10.185.69.54:5443",
|
||||
},
|
||||
{
|
||||
"external_otc": "https://a140174a-2f3e-11e9-9f91-0255ac101405.cce.eu-de.otc.t-systems.com",
|
||||
}
|
||||
"external_otc": "https://a140174a-2f3e-11e9-9f91-0255ac101405.cce.eu-de.otc.t-systems.com", }
|
||||
]
|
||||
}
|
||||
}</pre>
|
||||
|
||||
@ -306,8 +306,7 @@
|
||||
"External": "https://10.185.69.54:5443",
|
||||
},
|
||||
{
|
||||
"external_otc": "https://a140174a-2f3e-11e9-9f91-0255ac101405.cce.eu-de.otc.t-systems.com",
|
||||
},
|
||||
"external_otc": "https://a140174a-2f3e-11e9-9f91-0255ac101405.cce.eu-de.otc.t-systems.com", },
|
||||
]
|
||||
}
|
||||
}</pre>
|
||||
|
||||
@ -266,6 +266,14 @@
|
||||
<td class="cellrowborder" valign="top" width="60%" headers="mcps1.3.4.6.2.4.1.3 "><p id="cce_02_0269__p15934153110241">Node management configuration.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_02_0269__row14612125195016"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.4.6.2.4.1.1 "><p id="cce_02_0269__p192871247122213">customSecurityGroups</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.4.6.2.4.1.2 "><p id="cce_02_0269__p1628820473224">Array of strings</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="60%" headers="mcps1.3.4.6.2.4.1.3 "><p id="cce_02_0269__p428894742218">Custom security group settings for a node pool. New nodes scaled out in a node pool can be bound to a specified security group.</p>
|
||||
<ul id="cce_02_0269__ul1828884752220"><li id="cce_02_0269__li11288124716222">Specifying no security group ID will add the new nodes to the default security group of the worker nodes.</li><li id="cce_02_0269__li112895479227">Specifying a valid security group ID will put new nodes in that security group.</li><li id="cce_02_0269__li9289154742219">When specifying a security group, do not modify the rules of the port on which CCE running depends.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
<a name="cce_02_0273"></a><a name="cce_02_0273"></a>
|
||||
|
||||
<h1 class="topictitle1">Change History</h1>
|
||||
<h1 class="topictitle1"><span id="ph281717370445"></span>Change History</h1>
|
||||
<div id="body1592289440118">
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_02_0273__table1795742913571" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Change history</caption><thead align="left"><tr id="cce_02_0273__row096122965720"><th align="left" class="cellrowborder" valign="top" width="17.98%" id="mcps1.3.1.2.3.1.1"><p id="cce_02_0273__p11962329165717">Date</p>
|
||||
</th>
|
||||
@ -8,7 +8,12 @@
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="cce_02_0273__row11483457202418"><td class="cellrowborder" valign="top" width="17.98%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_02_0273__p1510922618183">2023-02-10</p>
|
||||
<tbody><tr id="cce_02_0273__row1734251589"><td class="cellrowborder" valign="top" width="17.98%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_02_0273__p6348517811">2023-11-06</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="82.02000000000001%" headers="mcps1.3.1.2.3.1.2 "><ul id="cce_02_0273__ul96157381188"><li id="cce_02_0273__li116152387811">Added the customSecurityGroups field. For details, see <a href="cce_02_0354.html#cce_02_0354__table620623542313">Table 5</a>.</li><li id="cce_02_0273__li837712353338">Added <a href="cce_02_0368.html">Node Flavor Description</a>.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_02_0273__row11483457202418"><td class="cellrowborder" valign="top" width="17.98%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_02_0273__p1510922618183">2023-02-10</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="82.02000000000001%" headers="mcps1.3.1.2.3.1.2 "><ul id="cce_02_0273__ul197373613514"><li id="cce_02_0273__li77303614352">Supported clusters of v1.25.</li><li id="cce_02_0273__li7540238153518">Added the <strong id="cce_02_0273__b18326191216368">storage</strong> field in <a href="cce_02_0242.html#cce_02_0242__table3150105216225">Table 5</a>.</li><li id="cce_02_0273__li510795673612">Added <a href="node_storage_example.html">Attaching Disks to a Node</a>.</li><li id="cce_02_0273__li4400165319375">Added <a href="AddNode.html">Accepting a Node</a>.</li><li id="cce_02_0273__li133126145388">Added <a href="ResetNode.html">Resetting a Node</a>.</li><li id="cce_02_0273__li1542271514385">Added <a href="RemoveNode.html">Removing a Node</a>.</li><li id="cce_02_0273__li121495301382">Added <a href="MigrateNode.html">Migrating a Node</a>.</li></ul>
|
||||
</td>
|
||||
|
||||
@ -202,6 +202,16 @@
|
||||
<td class="cellrowborder" valign="top" width="43.53%" headers="mcps1.3.3.7.2.5.1.4 "><p id="cce_02_0354__p99811242122710">Node management parameters.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_02_0354__row1758015984114"><td class="cellrowborder" valign="top" width="18.23%" headers="mcps1.3.3.7.2.5.1.1 "><p id="cce_02_0354__p1840734618226">customSecurityGroups</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="12.41%" headers="mcps1.3.3.7.2.5.1.2 "><p id="cce_02_0354__p34081461226">No</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="25.83%" headers="mcps1.3.3.7.2.5.1.3 "><p id="cce_02_0354__p4408146102213">Array of strings</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="43.53%" headers="mcps1.3.3.7.2.5.1.4 "><p id="cce_02_0354__p14088461221">Custom security group settings for a node pool. New nodes scaled out in a node pool can be bound to a specified security group.</p>
|
||||
<ul id="cce_02_0354__ul11409134619225"><li id="cce_02_0354__li240964672218">Specifying no security group ID will add the new nodes to the default security group of the worker nodes.</li><li id="cce_02_0354__li15409174616221">Specifying a valid security group ID will put new nodes in that security group.</li><li id="cce_02_0354__li140919464229">When specifying a security group, do not modify the rules of the port on which CCE running depends.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
@ -454,7 +464,7 @@
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="15.620000000000001%" headers="mcps1.3.3.10.2.5.1.3 "><p id="cce_02_0354__p463115285250">String</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="52.22%" headers="mcps1.3.3.10.2.5.1.4 "><p id="cce_02_0354__p35816473259">Disk type. For details, see the description of <strong id="cce_02_0354__b185814710254">root_volume</strong> in <a href="https://docs.otc.t-systems.com/en-us/api/ecs/en-us_topic_0020212668.html" target="_blank" rel="noopener noreferrer">Creating an ECS</a>.</p>
|
||||
<td class="cellrowborder" valign="top" width="52.22%" headers="mcps1.3.3.10.2.5.1.4 "><p id="cce_02_0354__p35816473259">Disk type. For details, see the description of <strong id="cce_02_0354__b185814710254">root_volume</strong> in<span id="cce_02_0354__ph13428221161220"> </span><a href="https://docs.otc.t-systems.com/en-us/api/ecs/en-us_topic_0020212668.html" target="_blank" rel="noopener noreferrer">Creating an ECS</a>.</p>
|
||||
<ul id="cce_02_0354__ul1458114792517"><li id="cce_02_0354__li155824732518"><strong id="cce_02_0354__b1558194742518">SATA</strong>: common I/O disk type.</li><li id="cce_02_0354__li1159144715251"><strong id="cce_02_0354__b859547132512">SAS</strong>: high I/O disk type.</li><li id="cce_02_0354__li459847122511"><strong id="cce_02_0354__b17590476252">SSD</strong>: ultra-high I/O disk type.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
@ -473,7 +483,7 @@
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="15.620000000000001%" headers="mcps1.3.3.10.2.5.1.3 "><p id="cce_02_0354__p854653992810">Map<String,Object></p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="52.22%" headers="mcps1.3.3.10.2.5.1.4 "><p id="cce_02_0354__p15461339142814">Disk extension parameter. For details, see the description of the extendparam parameter in <a href="https://docs.otc.t-systems.com/en-us/api/ecs/en-us_topic_0020212668.html" target="_blank" rel="noopener noreferrer">Creating an ECS</a>.</p>
|
||||
<td class="cellrowborder" valign="top" width="52.22%" headers="mcps1.3.3.10.2.5.1.4 "><p id="cce_02_0354__p15461339142814">Disk extension parameter. For details, see the description of the extendparam parameter in<span id="cce_02_0354__ph6613201513129"> </span><a href="https://docs.otc.t-systems.com/en-us/api/ecs/en-us_topic_0020212668.html" target="_blank" rel="noopener noreferrer">Creating an ECS</a>.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_02_0354__row18344936121710"><td class="cellrowborder" valign="top" width="15.840000000000002%" headers="mcps1.3.3.10.2.5.1.1 "><p id="cce_02_0354__p2340611183010">hw:passthrough</p>
|
||||
@ -1472,6 +1482,14 @@
|
||||
<td class="cellrowborder" valign="top" width="47%" headers="mcps1.3.4.6.2.4.1.3 "><p id="cce_02_0354__p163594610515">Node management parameters.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_02_0354__row839012910442"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.6.2.4.1.1 "><p id="cce_02_0354__p5956489221">customSecurityGroups</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="28.000000000000004%" headers="mcps1.3.4.6.2.4.1.2 "><p id="cce_02_0354__p595184822219">Array of strings</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="47%" headers="mcps1.3.4.6.2.4.1.3 "><p id="cce_02_0354__p6955489221">Custom security group settings for a node pool. New nodes scaled out in a node pool can be bound to a specified security group.</p>
|
||||
<ul id="cce_02_0354__ul695248102218"><li id="cce_02_0354__li5951548202214">Specifying no security group ID will add the new nodes to the default security group of the worker nodes.</li><li id="cce_02_0354__li49584820226">Specifying a valid security group ID will put new nodes in that security group.</li><li id="cce_02_0354__li18957483227">When specifying a security group, do not modify the rules of the port on which CCE running depends.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
|
||||
@ -285,6 +285,14 @@
|
||||
<td class="cellrowborder" valign="top" width="47%" headers="mcps1.3.4.7.2.4.1.3 "><p id="cce_02_0355__p163594610515">Node management parameters.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_02_0355__row12836172824816"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.7.2.4.1.1 "><p id="cce_02_0355__p188291455220">customSecurityGroups</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="28.000000000000004%" headers="mcps1.3.4.7.2.4.1.2 "><p id="cce_02_0355__p382914512222">Array of strings</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="47%" headers="mcps1.3.4.7.2.4.1.3 "><p id="cce_02_0355__p98291845122214">Custom security group settings for a node pool. New nodes scaled out in a node pool can be bound to a specified security group.</p>
|
||||
<ul id="cce_02_0355__ul13829745202214"><li id="cce_02_0355__li2830144522214">Specifying no security group ID will add the new nodes to the default security group of the worker nodes.</li><li id="cce_02_0355__li1283054513221">Specifying a valid security group ID will put new nodes in that security group.</li><li id="cce_02_0355__li683016454226">When specifying a security group, do not modify the rules of the port on which CCE running depends.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
|
||||
@ -205,6 +205,14 @@
|
||||
<td class="cellrowborder" valign="top" width="60%" headers="mcps1.3.4.5.2.4.1.3 "><p id="cce_02_0357__p15934153110241">Node management configuration.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_02_0357__row75271555115414"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.4.5.2.4.1.1 "><p id="cce_02_0357__p158570488223">customSecurityGroups</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.4.5.2.4.1.2 "><p id="cce_02_0357__p2857174872210">Array of strings</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="60%" headers="mcps1.3.4.5.2.4.1.3 "><p id="cce_02_0357__p9858134802216">Custom security group settings for a node pool. New nodes scaled out in a node pool can be bound to a specified security group.</p>
|
||||
<ul id="cce_02_0357__ul1685814872219"><li id="cce_02_0357__li2858448112212">Specifying no security group ID will add the new nodes to the default security group of the worker nodes.</li><li id="cce_02_0357__li208589487222">Specifying a valid security group ID will put new nodes in that security group.</li><li id="cce_02_0357__li28591148112217">When specifying a security group, do not modify the rules of the port on which CCE running depends.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
@ -452,7 +460,7 @@
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.4.8.2.4.1.2 "><p id="cce_02_0357__p4187732162420">Map<String,Object></p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="60%" headers="mcps1.3.4.8.2.4.1.3 "><p id="cce_02_0357__p1918711328245">Disk extension parameter. For details, see the description of the <strong id="cce_02_0357__b1718723222417">extendparam</strong> parameter in <a href="https://docs.otc.t-systems.com/en-us/api/ecs/en-us_topic_0020212668.html" target="_blank" rel="noopener noreferrer">Creating an ECS</a>.</p>
|
||||
<td class="cellrowborder" valign="top" width="60%" headers="mcps1.3.4.8.2.4.1.3 "><p id="cce_02_0357__p1918711328245">Disk extension parameter. For details, see the description of the <strong id="cce_02_0357__b1718723222417">extendparam</strong> parameter in <a href="https://docs.otc.t-systems.com/en-us/api/ecs/en-us_topic_0020212668.html" target="_blank" rel="noopener noreferrer">Creating an ECS</a>.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_02_0357__row7891829123511"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.4.8.2.4.1.1 "><p id="cce_02_0357__p2340611183010">hw:passthrough</p>
|
||||
|
||||
73
docs/cce/api-ref/cce_02_0368.html
Normal file
73
docs/cce/api-ref/cce_02_0368.html
Normal file
@ -0,0 +1,73 @@
|
||||
<a name="cce_02_0368"></a><a name="cce_02_0368"></a>
|
||||
|
||||
<h1 class="topictitle1">Node Flavor Description</h1>
|
||||
<div id="body0000001700565328"><div class="note" id="cce_02_0368__note68135111799"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_02_0368__p145110527493">Different regions support different node flavors, and node flavors may be changed. You are advised to log in to the CCE console and check whether the required node flavors are supported on the page for creating nodes.</p>
|
||||
</div></div>
|
||||
<ul id="cce_02_0368__ul7625154972220"><li id="cce_02_0368__li179801572443"><strong id="cce_02_0368__b136239571583">CCE cluster</strong><p id="cce_02_0368__p13172123665913">CCE clusters support only 2 vCPUs and 4 GiB or higher specifications. You are advised to query node specifications on the console. For details about node specifications, see ECS Specifications.</p>
|
||||
<p id="cce_02_0368__p10326155310591">You need to enter the specific flavor name, for example, <strong id="cce_02_0368__b8769920165712">c4.large.2</strong>.</p>
|
||||
<div class="p" id="cce_02_0368__p1498081811139">The following tables list the specifications supported by CCE. (The specifications of some ECS models vary by region. The actual specifications displayed on the console are used.)<ul id="cce_02_0368__ul498091831314"><li id="cce_02_0368__li1698071812132">ECS (VM):
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_02_0368__table998013189139" frame="border" border="1" rules="all"><caption><b>Table 1 </b>x86 nodes</caption><thead align="left"><tr id="cce_02_0368__row179811518181315"><th align="left" class="cellrowborder" valign="top" width="23.75%" id="mcps1.3.2.1.4.1.1.1.2.3.1.1"><p id="cce_02_0368__p698191811132">Node Type</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="76.25%" id="mcps1.3.2.1.4.1.1.1.2.3.1.2"><p id="cce_02_0368__p9981141871314">Flavor</p>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="cce_02_0368__row109811518191315"><td class="cellrowborder" valign="top" width="23.75%" headers="mcps1.3.2.1.4.1.1.1.2.3.1.1 "><p id="cce_02_0368__p199813182137">General computing-plus</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="76.25%" headers="mcps1.3.2.1.4.1.1.1.2.3.1.2 "><p id="cce_02_0368__p1048539161616">c4, c3</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_02_0368__row398111814134"><td class="cellrowborder" valign="top" width="23.75%" headers="mcps1.3.2.1.4.1.1.1.2.3.1.1 "><p id="cce_02_0368__p998181818132">General-purpose</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="76.25%" headers="mcps1.3.2.1.4.1.1.1.2.3.1.2 "><p id="cce_02_0368__p1698113183133">s3, s2</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_02_0368__row698115180135"><td class="cellrowborder" valign="top" width="23.75%" headers="mcps1.3.2.1.4.1.1.1.2.3.1.1 "><p id="cce_02_0368__p498120188137">Memory-optimized</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="76.25%" headers="mcps1.3.2.1.4.1.1.1.2.3.1.2 "><p id="cce_02_0368__p69811189135">m4, m3</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_02_0368__row0981181831318"><td class="cellrowborder" valign="top" width="23.75%" headers="mcps1.3.2.1.4.1.1.1.2.3.1.1 "><p id="cce_02_0368__p3982101813138">Disk-intensive</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="76.25%" headers="mcps1.3.2.1.4.1.1.1.2.3.1.2 "><p id="cce_02_0368__p139822189131">d2</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_02_0368__row1982111851314"><td class="cellrowborder" valign="top" width="23.75%" headers="mcps1.3.2.1.4.1.1.1.2.3.1.1 "><p id="cce_02_0368__p199821718181313">GPU-accelerated</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="76.25%" headers="mcps1.3.2.1.4.1.1.1.2.3.1.2 "><p id="cce_02_0368__p5982171816135">pi2, p2s, g6, and p2v</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
</li></ul>
|
||||
</div>
|
||||
</li><li id="cce_02_0368__li5905203842610"><strong id="cce_02_0368__b111318198471">CCE Turbo clusters</strong><ul id="cce_02_0368__ul490517387261"><li id="cce_02_0368__li1990513812265">ECS (VM):
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_02_0368__table10905738172611" frame="border" border="1" rules="all"><caption><b>Table 2 </b>x86 nodes</caption><thead align="left"><tr id="cce_02_0368__row4905538162611"><th align="left" class="cellrowborder" valign="top" width="24.84%" id="mcps1.3.2.2.2.1.1.2.3.1.1"><p id="cce_02_0368__p6905133852614">Node Type</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="75.16000000000001%" id="mcps1.3.2.2.2.1.1.2.3.1.2"><p id="cce_02_0368__p20905103812620">Flavor</p>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="cce_02_0368__row690517385266"><td class="cellrowborder" valign="top" width="24.84%" headers="mcps1.3.2.2.2.1.1.2.3.1.1 "><p id="cce_02_0368__p190583852611">General computing-plus</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="75.16000000000001%" headers="mcps1.3.2.2.2.1.1.2.3.1.2 "><p id="cce_02_0368__p6905113882618">c3n</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_02_0368__row890563812266"><td class="cellrowborder" valign="top" width="24.84%" headers="mcps1.3.2.2.2.1.1.2.3.1.1 "><p id="cce_02_0368__p3905203852614">Container-plus</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="75.16000000000001%" headers="mcps1.3.2.2.2.1.1.2.3.1.2 "><p id="cce_02_0368__p16647111919307">m3n</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
</li></ul>
|
||||
</li></ul>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_02_0083.html">Appendix</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@ -15,16 +15,16 @@ storageDevice=/dev/vdb
|
||||
vgcreate ${vgName} ${storageDevice}</pre>
|
||||
</div>
|
||||
</li><li id="node_storage_example__en-us_topic_0000001207069618_li23058191031">EVS disks match the disks created in <strong id="node_storage_example__en-us_topic_0000001207069618_b121287102717">dataVolumes</strong> based on the settings of <strong id="node_storage_example__en-us_topic_0000001207069618_b131291350152416">matchLabels</strong>.</li></ol>
|
||||
</li><li id="node_storage_example__en-us_topic_0000001207069618_li117111634433">Policies have priorities to match <strong id="node_storage_example__en-us_topic_0000001207069618_b1925417132278">matchLabels</strong>. The <strong id="node_storage_example__en-us_topic_0000001207069618_b204408516511">matchLabels</strong> policy nearest to <strong id="node_storage_example__en-us_topic_0000001207069618_b41561438317">storageSelectors</strong> has a higher priority and the disk nearest to <strong id="node_storage_example__en-us_topic_0000001207069618_b1491422012711">dataVolumes</strong> will be preferentially matches. As <strong id="node_storage_example__en-us_topic_0000001207069618_b13629123310290">matchLabels</strong> uses loose matching, you are advised to place the <strong id="node_storage_example__en-us_topic_0000001207069618_b1092135719611">matchLabels</strong> policy with a small matching range on the top. For example:<div class="p" id="node_storage_example__en-us_topic_0000001207069618_p177629163419"><span><img id="node_storage_example__en-us_topic_0000001207069618_image5240152411538" src="en-us_image_0000001207617538.png" title="Click to enlarge" class="imgResize"></span><ol type="a" id="node_storage_example__en-us_topic_0000001207069618_ol1754716742"><li id="node_storage_example__en-us_topic_0000001207069618_li9541116248">In step 1, the first disk in <strong id="node_storage_example__en-us_topic_0000001207069618_b113884264325">dataVolumes</strong> is matched by the EVS disk whose size is 100 GB and storage class is SAS. In step 2, the second disk in <strong id="node_storage_example__en-us_topic_0000001207069618_b1674773313449">dataVolumes</strong> is matched by the EVS disk whose size is 100 GB because the first disk has been selected.</li><li id="node_storage_example__en-us_topic_0000001207069618_li25415160410">In step 3, two disks in <strong id="node_storage_example__en-us_topic_0000001207069618_b1191053713331">dataVolumes</strong> can be matched because <strong id="node_storage_example__en-us_topic_0000001207069618_b153181629153315">volumeType</strong> or <strong id="node_storage_example__en-us_topic_0000001207069618_b119099318338">count</strong> is not specified in <strong id="node_storage_example__en-us_topic_0000001207069618_b75458247126">matchLabels</strong>. In this case, no disk is available for matching in step 4.</li></ol>
|
||||
</li><li id="node_storage_example__en-us_topic_0000001207069618_li117111634433">Policies have priorities to match <strong id="node_storage_example__en-us_topic_0000001207069618_b1925417132278">matchLabels</strong>. The <strong id="node_storage_example__en-us_topic_0000001207069618_b204408516511">matchLabels</strong> policy nearest to <strong id="node_storage_example__en-us_topic_0000001207069618_b41561438317">storageSelectors</strong> has a higher priority and the disk nearest to <strong id="node_storage_example__en-us_topic_0000001207069618_b1491422012711">dataVolumes</strong> will be preferentially matches. As <strong id="node_storage_example__en-us_topic_0000001207069618_b13629123310290">matchLabels</strong> uses loose matching, you are advised to place the <strong id="node_storage_example__en-us_topic_0000001207069618_b1092135719611">matchLabels</strong> policy with a small matching range on the top. For example:<div class="p" id="node_storage_example__en-us_topic_0000001207069618_p177629163419"><span><img id="node_storage_example__en-us_topic_0000001207069618_image5240152411538" src="en-us_image_0000001207617538.png" title="Click to enlarge" class="imgResize"></span><ol type="a" id="node_storage_example__en-us_topic_0000001207069618_ol1754716742"><li id="node_storage_example__en-us_topic_0000001207069618_li9541116248">In step 1, the first disk in <strong id="node_storage_example__en-us_topic_0000001207069618_b113884264325">dataVolumes</strong> is matched by the EVS disk whose size is 100 GiB and storage class is SAS. In step 2, the second disk in <strong id="node_storage_example__en-us_topic_0000001207069618_b1674773313449">dataVolumes</strong> is matched by the EVS disk whose size is 100 GiB because the first disk has been selected.</li><li id="node_storage_example__en-us_topic_0000001207069618_li25415160410">In step 3, two disks in <strong id="node_storage_example__en-us_topic_0000001207069618_b1191053713331">dataVolumes</strong> can be matched because <strong id="node_storage_example__en-us_topic_0000001207069618_b153181629153315">volumeType</strong> or <strong id="node_storage_example__en-us_topic_0000001207069618_b119099318338">count</strong> is not specified in <strong id="node_storage_example__en-us_topic_0000001207069618_b75458247126">matchLabels</strong>. In this case, no disk is available for matching in step 4.</li></ol>
|
||||
</div>
|
||||
</li><li id="node_storage_example__en-us_topic_0000001207069618_li78286464319"><strong id="node_storage_example__en-us_topic_0000001207069618_b181371053114510">storageGroups</strong> associates with <strong id="node_storage_example__en-us_topic_0000001207069618_b16743185584513">storageSelectors</strong> based on <strong id="node_storage_example__en-us_topic_0000001207069618_b7844135573316">selectorName</strong>. Finally, two 100 GB disks are selected. The CCE backend groups the two PVs into a volume group (VG) and divides the VG into two logical volumes (LVs) in the ratio of 9:1. 10% of Kubernetes LVs are partitioned in striped mode. 90% runtime LVs are partitioned in linear mode by default because runtimeConfig is not configured.</li></ol>
|
||||
</li><li id="node_storage_example__en-us_topic_0000001207069618_li78286464319"><strong id="node_storage_example__en-us_topic_0000001207069618_b181371053114510">storageGroups</strong> associates with <strong id="node_storage_example__en-us_topic_0000001207069618_b16743185584513">storageSelectors</strong> based on <strong id="node_storage_example__en-us_topic_0000001207069618_b7844135573316">selectorName</strong>. Finally, two 100 GiB disks are selected. The CCE backend groups the two PVs into a volume group (VG) and divides the VG into two logical volumes (LVs) in the ratio of 9:1. 10% of Kubernetes LVs are partitioned in striped mode. 90% runtime LVs are partitioned in linear mode by default because runtimeConfig is not configured.</li></ol>
|
||||
</div>
|
||||
<div class="section" id="node_storage_example__en-us_topic_0000001207069618_section22804228617"><h4 class="sectiontitle">Creating a Raw Disk</h4><p id="node_storage_example__en-us_topic_0000001207069618_p88015491162">During node creation on the CCE console, click <strong id="node_storage_example__en-us_topic_0000001207069618_b178910329254">Add Data Disk</strong>. Then, click <strong id="node_storage_example__en-us_topic_0000001207069618_b1883614131533">Expand</strong> next to the newly added data disk and select <strong id="node_storage_example__en-us_topic_0000001207069618_b5952416125316">Default</strong>. The created disk is a raw disk.</p>
|
||||
<p id="node_storage_example__en-us_topic_0000001207069618_p10930817875"></p>
|
||||
<p id="node_storage_example__en-us_topic_0000001207069618_p5963163618186"></p>
|
||||
<p id="node_storage_example__en-us_topic_0000001207069618_p1722816492715">The following figure shows the API calling logic.</p>
|
||||
<p id="node_storage_example__en-us_topic_0000001207069618_p1783711149811"><span><img id="node_storage_example__en-us_topic_0000001207069618_image10250144612593" src="en-us_image_0000001252018205.png" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<ol id="node_storage_example__en-us_topic_0000001207069618_ol1843119561388"><li id="node_storage_example__en-us_topic_0000001207069618_li643185611813">The <strong id="node_storage_example__en-us_topic_0000001207069618_b136567312016">cceUse</strong> selector matches a 100 GB data disk.</li><li id="node_storage_example__en-us_topic_0000001207069618_li3431956187">The selected disk is managed by CCE and used as a data disk.</li><li id="node_storage_example__en-us_topic_0000001207069618_li1543117569815">The other 100 GB data disk created in <strong id="node_storage_example__en-us_topic_0000001207069618_b119946317551">dataVolumes</strong> is not selected by any selector and is managed by storageGroups. Therefore, this EVS disk will be attached to the node as a raw disk and will not be initialized.</li></ol>
|
||||
<p id="node_storage_example__en-us_topic_0000001207069618_p461483131011">After the node is created, log in to the node and check whether a 100 GB disk has been attached but not initialized.</p>
|
||||
<ol id="node_storage_example__en-us_topic_0000001207069618_ol1843119561388"><li id="node_storage_example__en-us_topic_0000001207069618_li643185611813">The <strong id="node_storage_example__en-us_topic_0000001207069618_b136567312016">cceUse</strong> selector matches a 100 GiB data disk.</li><li id="node_storage_example__en-us_topic_0000001207069618_li3431956187">The selected disk is managed by CCE and used as a data disk.</li><li id="node_storage_example__en-us_topic_0000001207069618_li1543117569815">The other 100 GiB data disk created in <strong id="node_storage_example__en-us_topic_0000001207069618_b119946317551">dataVolumes</strong> is not selected by any selector and is managed by storageGroups. Therefore, this EVS disk will be attached to the node as a raw disk and will not be initialized.</li></ol>
|
||||
<p id="node_storage_example__en-us_topic_0000001207069618_p461483131011">After the node is created, log in to the node and check whether a 100 GiB disk has been attached but not initialized.</p>
|
||||
<p id="node_storage_example__en-us_topic_0000001207069618_p14773913101019"><span><img id="node_storage_example__en-us_topic_0000001207069618_image101350300432" src="en-us_image_0000001207129076.png" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<p id="node_storage_example__en-us_topic_0000001207069618_p145826201119">The following is an API example: </p>
|
||||
<pre class="screen" id="node_storage_example__en-us_topic_0000001207069618_screen4311171562013">{
|
||||
@ -106,11 +106,11 @@ vgcreate ${vgName} ${storageDevice}</pre>
|
||||
}</pre>
|
||||
</div>
|
||||
<div class="section" id="node_storage_example__en-us_topic_0000001207069618_section1112811362118"><h4 class="sectiontitle">Attaching a Disk to a Specified Path</h4><p id="node_storage_example__en-us_topic_0000001207069618_p111136915128">During node creation on the CCE console, click <strong id="node_storage_example__en-us_topic_0000001207069618_b7690192711571">Add Data Disk</strong>. Then, click <strong id="node_storage_example__en-us_topic_0000001207069618_b669052718577">Expand</strong> next to the newly added data disk, select <strong id="node_storage_example__en-us_topic_0000001207069618_b269072735718">Mount Disk</strong>, and set the mount path. In this case, CCE initializes and attaches the disk by default.</p>
|
||||
<p id="node_storage_example__en-us_topic_0000001207069618_p84032038181117"></p>
|
||||
<p id="node_storage_example__en-us_topic_0000001207069618_p858524619167"></p>
|
||||
<p id="node_storage_example__en-us_topic_0000001207069618_p12486124715129">The following figure shows the API calling logic.</p>
|
||||
<p id="node_storage_example__en-us_topic_0000001207069618_p920725214124"><span><img id="node_storage_example__en-us_topic_0000001207069618_image1232892319320" src="en-us_image_0000001207618830.png" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<ol id="node_storage_example__en-us_topic_0000001207069618_ol1967572812138"><li id="node_storage_example__en-us_topic_0000001207069618_li8675142812134">The <strong id="node_storage_example__en-us_topic_0000001207069618_b133591278562">user1</strong> selector selects a 100 GB data disk.</li><li id="node_storage_example__en-us_topic_0000001207069618_li1467616282135">Create a VG named <strong id="node_storage_example__en-us_topic_0000001207069618_b22173146213">vguser1</strong> using LVM.</li><li id="node_storage_example__en-us_topic_0000001207069618_li76769287137">Strip all the space of <strong id="node_storage_example__en-us_topic_0000001207069618_b184282703811">vguser1</strong> into an LV named <strong id="node_storage_example__en-us_topic_0000001207069618_b126428424387">user</strong> and format the disk in ext4 format. Finally, attach the disk to the <strong id="node_storage_example__en-us_topic_0000001207069618_b225225814379">/tmp2</strong> directory.</li></ol>
|
||||
<p id="node_storage_example__en-us_topic_0000001207069618_p6882176151410">After the node is created, log in to the node and check whether a 100 GB disk has been attached and managed by LVM.</p>
|
||||
<ol id="node_storage_example__en-us_topic_0000001207069618_ol1967572812138"><li id="node_storage_example__en-us_topic_0000001207069618_li8675142812134">The <strong id="node_storage_example__en-us_topic_0000001207069618_b133591278562">user1</strong> selector selects a 100 GiB data disk.</li><li id="node_storage_example__en-us_topic_0000001207069618_li1467616282135">Create a VG named <strong id="node_storage_example__en-us_topic_0000001207069618_b22173146213">vguser1</strong> using LVM.</li><li id="node_storage_example__en-us_topic_0000001207069618_li76769287137">Strip all the space of <strong id="node_storage_example__en-us_topic_0000001207069618_b184282703811">vguser1</strong> into an LV named <strong id="node_storage_example__en-us_topic_0000001207069618_b126428424387">user</strong> and format the disk in ext4 format. Finally, attach the disk to the <strong id="node_storage_example__en-us_topic_0000001207069618_b225225814379">/tmp2</strong> directory.</li></ol>
|
||||
<p id="node_storage_example__en-us_topic_0000001207069618_p6882176151410">After the node is created, log in to the node and check whether a 100 GiB disk has been attached and managed by LVM.</p>
|
||||
<p id="node_storage_example__en-us_topic_0000001207069618_p5696135118138"><span><img id="node_storage_example__en-us_topic_0000001207069618_image976162414610" src="en-us_image_0000001207129902.png" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<p id="node_storage_example__en-us_topic_0000001207069618_p1271019234152">The following is an API example. There are two data disks. One is used by CCE, and the other is mounted to the <strong id="node_storage_example__en-us_topic_0000001207069618_b48037274010">/tmp2</strong> directory.</p>
|
||||
<pre class="screen" id="node_storage_example__en-us_topic_0000001207069618_screen6658115720478">{
|
||||
@ -218,8 +218,8 @@ vgcreate ${vgName} ${storageDevice}</pre>
|
||||
</div>
|
||||
<div class="section" id="node_storage_example__en-us_topic_0000001207069618_section163256264156"><h4 class="sectiontitle">Creating Striped LVs to Improve Disk Performance</h4><p id="node_storage_example__en-us_topic_0000001207069618_p12858184310159">Currently, the striped LV function is supported only by calling an API. The following is an example:</p>
|
||||
<p id="node_storage_example__en-us_topic_0000001207069618_p911834651514"><span><img id="node_storage_example__en-us_topic_0000001207069618_image1389812341168" src="en-us_image_0000001252020583.png" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<ol id="node_storage_example__en-us_topic_0000001207069618_ol7789413121719"><li id="node_storage_example__en-us_topic_0000001207069618_li17891013121712"><strong id="node_storage_example__en-us_topic_0000001207069618_b154262614309">storageSelectors</strong> matches all EVS disks in <strong id="node_storage_example__en-us_topic_0000001207069618_b15422634143016">dataVolumes</strong> because <strong id="node_storage_example__en-us_topic_0000001207069618_b10454154613011">matchLables</strong> is not contained in <strong id="node_storage_example__en-us_topic_0000001207069618_b33031551153018">storageSelectors</strong>.</li><li id="node_storage_example__en-us_topic_0000001207069618_li12789131310171">Create a VG named <strong id="node_storage_example__en-us_topic_0000001207069618_b89501408324">vgpaas</strong> using LVM.</li><li id="node_storage_example__en-us_topic_0000001207069618_li3789161317176">Strip 90% of the <strong id="node_storage_example__en-us_topic_0000001207069618_b1914129113217">vgpaas</strong> space into runtime LVs.</li><li id="node_storage_example__en-us_topic_0000001207069618_li157893136179">Strip 10% of the <strong id="node_storage_example__en-us_topic_0000001207069618_b14091386321">vgpaas</strong> space into Kubernetes LVs.</li></ol>
|
||||
<div class="note" id="node_storage_example__en-us_topic_0000001207069618_note1598564031718"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="node_storage_example__en-us_topic_0000001207069618_ul77543234504"><li id="node_storage_example__en-us_topic_0000001207069618_li7790024155011">Two or more data disks are required for striping.</li><li id="node_storage_example__en-us_topic_0000001207069618_li18754102315014">When creating a striped LV, ensure that the types and sizes of the PVs added to the VG are the same. Otherwise, the striping fails.</li></ul>
|
||||
<ol id="node_storage_example__en-us_topic_0000001207069618_ol7789413121719"><li id="node_storage_example__en-us_topic_0000001207069618_li17891013121712"><strong id="node_storage_example__en-us_topic_0000001207069618_b154262614309">storageSelectors</strong> matches all EVS disks in <strong id="node_storage_example__en-us_topic_0000001207069618_b15422634143016">dataVolumes</strong> because <strong id="node_storage_example__en-us_topic_0000001207069618_b10454154613011">matchLabels</strong> is not contained in <strong id="node_storage_example__en-us_topic_0000001207069618_b33031551153018">storageSelectors</strong>.</li><li id="node_storage_example__en-us_topic_0000001207069618_li12789131310171">Create a VG named <strong id="node_storage_example__en-us_topic_0000001207069618_b89501408324">vgpaas</strong> using LVM.</li><li id="node_storage_example__en-us_topic_0000001207069618_li3789161317176">Strip 90% of the <strong id="node_storage_example__en-us_topic_0000001207069618_b1914129113217">vgpaas</strong> space into runtime LVs.</li><li id="node_storage_example__en-us_topic_0000001207069618_li157893136179">Strip 10% of the <strong id="node_storage_example__en-us_topic_0000001207069618_b14091386321">vgpaas</strong> space into Kubernetes LVs.</li></ol>
|
||||
<div class="note" id="node_storage_example__en-us_topic_0000001207069618_note1598564031718"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="node_storage_example__en-us_topic_0000001207069618_ul77543234504"><li id="node_storage_example__en-us_topic_0000001207069618_li7790024155011">Two or more data disks are required for striping.</li><li id="node_storage_example__en-us_topic_0000001207069618_li18754102315014">When creating a striped LV, ensure that the types and sizes of the PVs added to the VG are the same. Otherwise, the creation will fail.</li><li id="node_storage_example__en-us_topic_0000001207069618_li32967561071">When creating a striped LV, use the striping configuration for both the runtime LV and Kubernetes LV. Otherwise, the creation will fail.</li></ul>
|
||||
</div></div>
|
||||
<p id="node_storage_example__en-us_topic_0000001207069618_p1529343517181">Log in to the node and run the following command to view the striping result:</p>
|
||||
<p id="node_storage_example__en-us_topic_0000001207069618_p8987164519177"><span><img id="node_storage_example__en-us_topic_0000001207069618_image193301714114414" src="en-us_image_0000001251962373.png"></span></p>
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user