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

ecs_umn_0712_g6

Browse Source 
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-authored-by: guoyanyan <guoyanyan3@huawei.com>
Co-committed-by: guoyanyan <guoyanyan3@huawei.com>
This commit is contained in:
guoyanyan 2023-07-25 19:31:44 +00:00 committed by zuul
parent 78cb06737e
commit 46367646b1
23 changed files with 1024 additions and 687 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

286
docs/ecs/umn/ALL_META.TXT.json
View File

File diff suppressed because it is too large Load Diff

551
docs/ecs/umn/CLASS.TXT.json
View File

File diff suppressed because it is too large Load Diff

2
docs/ecs/umn/en-us_topic_0013771092.html
View File

@ -14,7 +14,7 @@
</li><li id="EN-US_TOPIC_0013771092__li572184075211">Click <strong id="EN-US_TOPIC_0013771092__b25955399219229">More</strong> in the <strong id="EN-US_TOPIC_0013771092__b211788459919229">Operation</strong> column and select <strong id="EN-US_TOPIC_0013771092__b84235270619250">Modify Specifications</strong>.<p id="EN-US_TOPIC_0013771092__p20946954194414">The <strong id="EN-US_TOPIC_0013771092__b842352706172049">Modify ECS Specifications</strong> page is displayed.</p>
</li><li id="EN-US_TOPIC_0013771092__li137218401522">Select the new <span id="EN-US_TOPIC_0013771092__text1626718488409">ECS</span> type, vCPUs, and memory as prompted.</li><li id="EN-US_TOPIC_0013771092__li654534825212">(Optional) Set <strong id="EN-US_TOPIC_0013771092__b8423527062212">DeH</strong>.<p id="EN-US_TOPIC_0013771092__p196261841172818">If the ECS is created on a DeH, the system allows you to change the DeH.</p>
<p id="EN-US_TOPIC_0013771092__p1730463595012">To do so, select the target DeH from the drop-down list. If no DeH is available in the drop-down list, remaining DeH resources are insufficient and cannot be used to create the ECS with specifications modified.</p>
</li><li id="EN-US_TOPIC_0013771092__li19732406526">Click <strong id="EN-US_TOPIC_0013771092__en-us_topic_0013859511_b84235270613416">Next</strong>.</li><li id="EN-US_TOPIC_0013771092__li2073740175218">Confirm the settings and click <strong id="EN-US_TOPIC_0013771092__b842352706171854">Submit</strong>.</li><li id="EN-US_TOPIC_0013771092__li4711114720243">Check whether the specifications have been modified.<p id="EN-US_TOPIC_0013771092__p9749161119245"><a name="EN-US_TOPIC_0013771092__li4711114720243"></a><a name="li4711114720243"></a>After modifying the specifications, you can check whether the specifications have been modified in <strong id="EN-US_TOPIC_0013771092__b1222491910231911">Failures</strong>.</p>
</li><li id="EN-US_TOPIC_0013771092__li19732406526">Click <strong id="EN-US_TOPIC_0013771092__en-us_topic_0013859511_b84235270613416">Next</strong>.</li><li id="EN-US_TOPIC_0013771092__li10434112511110">Confirm the settings and click <strong id="EN-US_TOPIC_0013771092__b7210181018014">Submit</strong>.</li><li id="EN-US_TOPIC_0013771092__li4711114720243">Check whether the specifications have been modified.<p id="EN-US_TOPIC_0013771092__p9749161119245"><a name="EN-US_TOPIC_0013771092__li4711114720243"></a><a name="li4711114720243"></a>After modifying the specifications, you can check whether the specifications have been modified in <strong id="EN-US_TOPIC_0013771092__b1222491910231911">Failures</strong>.</p>
<ol type="a" id="EN-US_TOPIC_0013771092__ol142539992417"><li id="EN-US_TOPIC_0013771092__li142511395248">Check whether <strong id="EN-US_TOPIC_0013771092__b38312896231932">Failures</strong> is displayed on the management console. For details, see <a href="en-us_topic_0108255889.html">Viewing Failed Tasks</a>.<ul id="EN-US_TOPIC_0013771092__ul1925149152416"><li id="EN-US_TOPIC_0013771092__li102516982413">If yes, go to step <a href="#EN-US_TOPIC_0013771092__li6253192246">10.b</a>.</li><li id="EN-US_TOPIC_0013771092__li1251792246">If no, the specifications have been modified.</li></ul>
</li><li id="EN-US_TOPIC_0013771092__li6253192246"><a name="EN-US_TOPIC_0013771092__li6253192246"></a><a name="li6253192246"></a>Click <strong id="EN-US_TOPIC_0013771092__b84235270617246">Failures</strong>. Then, in the <strong id="EN-US_TOPIC_0013771092__b84235270617249">Failures</strong> dialog box, click <strong id="EN-US_TOPIC_0013771092__b842352706144228">Operation Failures</strong> and check whether the task is contained in the list by <strong id="EN-US_TOPIC_0013771092__b842352706172633">Name/ID</strong>, <strong id="EN-US_TOPIC_0013771092__b842352706172637">Operated At</strong>, or <strong id="EN-US_TOPIC_0013771092__b842352706143412">Task</strong>.<ul id="EN-US_TOPIC_0013771092__ul1325379162412"><li id="EN-US_TOPIC_0013771092__li152539915242">If yes, the specifications modification failed. See <a href="#EN-US_TOPIC_0013771092__section9461027528">Follow-up Procedure</a> for failure causes.</li><li id="EN-US_TOPIC_0013771092__li15253149162415">If no, the specifications have been modified.</li></ul>
</li></ol>

2
docs/ecs/umn/en-us_topic_0024911405.html
View File

@ -17,7 +17,7 @@
</li><li id="EN-US_TOPIC_0024911405__li23576357205117">(Optional) Select a <strong id="EN-US_TOPIC_0024911405__b84235270615319">License Type</strong> (<strong id="EN-US_TOPIC_0024911405__b842352706153129">Use license from the system</strong> or <strong id="EN-US_TOPIC_0024911405__b842352706153134">Bring your own license (BYOL)</strong>) if the reinstalled OS running on your ECS is billed. For more details, see <a href="en-us_topic_0046566932.html">License Types</a>.<p id="EN-US_TOPIC_0024911405__p46529483205117">The following OSs are billed:</p>
<ul id="EN-US_TOPIC_0024911405__ul55183157205155"><li id="EN-US_TOPIC_0024911405__en-us_topic_0046566932_li2586589022251">SUSE Linux Enterprise Server</li><li id="EN-US_TOPIC_0024911405__en-us_topic_0046566932_li6521605722253">Oracle Enterprise Linux</li><li id="EN-US_TOPIC_0024911405__en-us_topic_0046566932_li37000181205155">Red Hat Enterprise Linux</li></ul>
</li><li id="EN-US_TOPIC_0024911405__li65835346143541">Select the login mode.<p id="EN-US_TOPIC_0024911405__p35928679153231"><a name="EN-US_TOPIC_0024911405__li65835346143541"></a><a name="li65835346143541"></a>If the target <span id="EN-US_TOPIC_0024911405__text22614242316">ECS</span> uses key pair authentication, you can replace the original key pair.</p>
</li><li id="EN-US_TOPIC_0024911405__li55647207143541">Click <strong id="EN-US_TOPIC_0024911405__b32047965114410">OK</strong>.</li><li id="EN-US_TOPIC_0024911405__li31062819143541"><a name="EN-US_TOPIC_0024911405__li31062819143541"></a><a name="li31062819143541"></a>On the <strong id="EN-US_TOPIC_0024911405__b634582917420">ECS OS Reinstallation</strong> page, confirm the settings, and click <strong id="EN-US_TOPIC_0024911405__b1644575594916">Submit</strong>.<div class="p" id="EN-US_TOPIC_0024911405__p3796675416556">After the request is submitted, the status <strong id="EN-US_TOPIC_0024911405__b84235270616717">Reinstalling</strong> is displayed. When this status disappears, the reinstallation is complete.<div class="note" id="EN-US_TOPIC_0024911405__note8958845143541"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0024911405__p13520745143541">A temporary <span id="EN-US_TOPIC_0024911405__text11832184415256">ECS</span> is created during the reinstallation process. After reinstallation, this <span id="EN-US_TOPIC_0024911405__text976155011257">ECS</span> will be automatically deleted. Do not perform any operation on the temporary <span id="EN-US_TOPIC_0024911405__text97141831172413">ECS</span> during the reinstallation process.</p>
</li><li id="EN-US_TOPIC_0024911405__li55647207143541">Click <strong id="EN-US_TOPIC_0024911405__b32047965114410">OK</strong>.</li><li id="EN-US_TOPIC_0024911405__li31062819143541"><a name="EN-US_TOPIC_0024911405__li31062819143541"></a><a name="li31062819143541"></a>On the <strong id="EN-US_TOPIC_0024911405__b633652744713">ECS OS Reinstallation</strong> page, confirm the settings, and click <strong id="EN-US_TOPIC_0024911405__b115771559144917">Submit</strong>.<div class="p" id="EN-US_TOPIC_0024911405__p3796675416556">After the request is submitted, the status <strong id="EN-US_TOPIC_0024911405__b84235270616717">Reinstalling</strong> is displayed. When this status disappears, the reinstallation is complete.<div class="note" id="EN-US_TOPIC_0024911405__note8958845143541"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0024911405__p13520745143541">A temporary <span id="EN-US_TOPIC_0024911405__text11832184415256">ECS</span> is created during the reinstallation process. After reinstallation, this <span id="EN-US_TOPIC_0024911405__text976155011257">ECS</span> will be automatically deleted. Do not perform any operation on the temporary <span id="EN-US_TOPIC_0024911405__text97141831172413">ECS</span> during the reinstallation process.</p>
</div></div>
</div>
</li></ol>

12
docs/ecs/umn/en-us_topic_0030878383.html
View File

@ -10,9 +10,9 @@
</li><li id="EN-US_TOPIC_0030878383__en-us_topic_0029320966_li110100322530">Configure required parameters.<p id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_p10544530320"><a name="EN-US_TOPIC_0030878383__en-us_topic_0029320966_li110100322530"></a><a name="en-us_topic_0029320966_li110100322530"></a>You can click <strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b84235270617413">+</strong> to add more inbound rules.</p>
<div class="fignone" id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_fig1786518124129"><span class="figcap"><b>Figure 1 </b>Add Inbound Rule</span><br><span><img id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_image186617129126" src="en-us_image_0284920908.png" title="Click to enlarge" class="imgResize"></span></div>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_table111445216564" width="90%" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Inbound rule parameter description</caption><thead align="left"><tr id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_row1811565205613"><th align="left" class="cellrowborder" valign="top" width="12.55%" id="mcps1.3.2.2.7.3.2.4.1.1"><p id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_p51151452125620"><strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b1472201319">Parameter</strong></p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_table111445216564" width="90%" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Inbound rule parameter description</caption><thead align="left"><tr id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_row1811565205613"><th align="left" class="cellrowborder" valign="top" width="12.55%" id="mcps1.3.2.2.7.3.2.4.1.1"><p id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_p51151452125620"><strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b540999511">Parameter</strong></p>
</th>
<th align="left" class="cellrowborder" valign="top" width="69.45%" id="mcps1.3.2.2.7.3.2.4.1.2"><p id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_p5115552175613"><strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b1218327882">Description</strong></p>
<th align="left" class="cellrowborder" valign="top" width="69.45%" id="mcps1.3.2.2.7.3.2.4.1.2"><p id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_p5115552175613"><strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b399552255">Description</strong></p>
</th>
<th align="left" class="cellrowborder" valign="top" width="18%" id="mcps1.3.2.2.7.3.2.4.1.3"><p id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_p711565219563"><strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b984193573219">Example Value</strong></p>
</th>
@ -28,7 +28,7 @@
<tr id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_row9115105219562"><td class="cellrowborder" rowspan="2" valign="top" width="12.55%" headers="mcps1.3.2.2.7.3.2.4.1.1 "><p id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_p151157525565">Protocol &amp; Port</p>
<p id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_p3510193211510"></p>
</td>
<td class="cellrowborder" valign="top" width="69.45%" headers="mcps1.3.2.2.7.3.2.4.1.2 "><p id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_p1711515526562"><strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b1939852442315">Protocol</strong>: The network protocol. Currently, the value can be <strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b140030183">All</strong>, <strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b1169023126">TCP</strong>, <strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b1217177236">UDP</strong>, <strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b470698349">ICMP</strong>, <strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b175264618215">GRE</strong>, or others.</p>
<td class="cellrowborder" valign="top" width="69.45%" headers="mcps1.3.2.2.7.3.2.4.1.2 "><p id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_p1711515526562"><strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b1939852442315">Protocol</strong>: The network protocol. Currently, the value can be <strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b1889956601">All</strong>, <strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b1803161861">TCP</strong>, <strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b1395559813">UDP</strong>, <strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b1392189438">ICMP</strong>, <strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b175264618215">GRE</strong>, or others.</p>
</td>
<td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.2.2.7.3.2.4.1.3 "><p id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_p193908441914">TCP</p>
</td>
@ -62,9 +62,9 @@
</li><li id="EN-US_TOPIC_0030878383__li114871417141">Configure required parameters.<p id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_p161151454111115"><a name="EN-US_TOPIC_0030878383__li114871417141"></a><a name="li114871417141"></a>You can click <strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b842352706174116">+</strong> to add more outbound rules.</p>
<div class="fignone" id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_fig11809848184019"><span class="figcap"><b>Figure 2 </b>Add Outbound Rule</span><br><span><img id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_image138102048204017" src="en-us_image_0284993717.png" title="Click to enlarge" class="imgResize"></span></div>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_table0614192319232" width="90%" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Outbound rule parameter description</caption><thead align="left"><tr id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_row19614623202312"><th align="left" class="cellrowborder" valign="top" width="12.55%" id="mcps1.3.2.2.8.3.2.4.1.1"><p id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_p361592319230"><strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b763754973">Parameter</strong></p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_table0614192319232" width="90%" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Outbound rule parameter description</caption><thead align="left"><tr id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_row19614623202312"><th align="left" class="cellrowborder" valign="top" width="12.55%" id="mcps1.3.2.2.8.3.2.4.1.1"><p id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_p361592319230"><strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b405193869">Parameter</strong></p>
</th>
<th align="left" class="cellrowborder" valign="top" width="69.45%" id="mcps1.3.2.2.8.3.2.4.1.2"><p id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_p1961514231232"><strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b1017502369">Description</strong></p>
<th align="left" class="cellrowborder" valign="top" width="69.45%" id="mcps1.3.2.2.8.3.2.4.1.2"><p id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_p1961514231232"><strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b336772555">Description</strong></p>
</th>
<th align="left" class="cellrowborder" valign="top" width="18%" id="mcps1.3.2.2.8.3.2.4.1.3"><p id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_p1061552372311"><strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b78071625745">Example Value</strong></p>
</th>
@ -80,7 +80,7 @@
<tr id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_row76161523132311"><td class="cellrowborder" rowspan="2" valign="top" width="12.55%" headers="mcps1.3.2.2.8.3.2.4.1.1 "><p id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_p1761652313238">Protocol &amp; Port</p>
<p id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_p4616323182310"></p>
</td>
<td class="cellrowborder" valign="top" width="69.45%" headers="mcps1.3.2.2.8.3.2.4.1.2 "><p id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_p1461632352313"><strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b114706499477">Protocol</strong>: The network protocol. Currently, the value can be <strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b342111460">All</strong>, <strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b590273277">TCP</strong>, <strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b47375111">UDP</strong>, <strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b53288437">ICMP</strong>, <strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b1791880049">GRE</strong>, or others.</p>
<td class="cellrowborder" valign="top" width="69.45%" headers="mcps1.3.2.2.8.3.2.4.1.2 "><p id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_p1461632352313"><strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b114706499477">Protocol</strong>: The network protocol. Currently, the value can be <strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b1728508328">All</strong>, <strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b1404941812">TCP</strong>, <strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b2084536363">UDP</strong>, <strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b2048983235">ICMP</strong>, <strong id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_b562416727">GRE</strong>, or others.</p>
</td>
<td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.2.2.8.3.2.4.1.3 "><p id="EN-US_TOPIC_0030878383__en-us_topic_0118534005_p157082238193">TCP</p>
</td>

2
docs/ecs/umn/en-us_topic_0031107266.html
View File

@ -4,7 +4,7 @@
<div id="body1464342274212"><div class="section" id="EN-US_TOPIC_0031107266__section83915017466"><h4 class="sectiontitle">Scenarios</h4><p id="EN-US_TOPIC_0031107266__p5548482995849">Password authentication is required to log in to a Windows <span id="EN-US_TOPIC_0031107266__text2418174235815">ECS</span>. Therefore, you must use the key file used when you created the <span id="EN-US_TOPIC_0031107266__text9971154710587">ECS</span> to obtain the administrator password generated during <span id="EN-US_TOPIC_0031107266__text120830195810">ECS</span> creation. The administrator user is <strong id="EN-US_TOPIC_0031107266__b2049513373585">Administrator</strong> or the user configured using Cloudbase-Init. This password is randomly generated, offering high security.</p>
<p id="EN-US_TOPIC_0031107266__p703221995027">You can obtain the initial password for logging in to a Windows <span id="EN-US_TOPIC_0031107266__text66814149599">ECS</span> through the management console or APIs. For details, see this section.</p>
</div>
<div class="section" id="EN-US_TOPIC_0031107266__section38475220193847"><h4 class="sectiontitle">Obtaining the Password Through the Management Console</h4><ol id="EN-US_TOPIC_0031107266__ol5405292620557"><li id="EN-US_TOPIC_0031107266__li584178495530">Obtain the private key file (.pem file) used when you created the <span id="EN-US_TOPIC_0031107266__text136800010221">ECS</span>.</li><li id="EN-US_TOPIC_0031107266__li3490190117228">Log in to the management console.</li><li id="EN-US_TOPIC_0031107266__li464234814566">Click <span><img id="EN-US_TOPIC_0031107266__en-us_topic_0014250631_image1862675853202121" src="en-us_image_0210779229.png"></span> in the upper left corner and select your region and project.</li><li id="EN-US_TOPIC_0031107266__en-us_topic_0029320966_li40039532224047">Under <strong id="EN-US_TOPIC_0031107266__b52081541033"><span id="EN-US_TOPIC_0031107266__text82071840315">Computing</span></strong>, click <strong id="EN-US_TOPIC_0031107266__b2020864138">Elastic Cloud Server</strong>.</li><li id="EN-US_TOPIC_0031107266__en-us_topic_0029320966_li24833369224047">On the <strong id="EN-US_TOPIC_0031107266__b577318918018">Elastic Cloud Server</strong> page, select the target <span id="EN-US_TOPIC_0031107266__text11584529221">ECS</span>.</li><li id="EN-US_TOPIC_0031107266__li46427097215215">In the <strong id="EN-US_TOPIC_0031107266__b1334448587">Operation</strong> column, click <strong id="EN-US_TOPIC_0031107266__b1949701279">More</strong> and select <strong id="EN-US_TOPIC_0031107266__b1789385252">Get Password</strong>.</li><li id="EN-US_TOPIC_0031107266__li50525424215555">Use either of the following methods to obtain the password through the key file:<ul id="EN-US_TOPIC_0031107266__ul6527186921565"><li id="EN-US_TOPIC_0031107266__li1887355017131">Click <strong id="EN-US_TOPIC_0031107266__b842352706144939">Select File</strong> and upload the key file from a local directory.</li><li id="EN-US_TOPIC_0031107266__li42486460215639">Copy the key file content to the text field.</li></ul>
<div class="section" id="EN-US_TOPIC_0031107266__section38475220193847"><h4 class="sectiontitle">Obtaining the Password Through the Management Console</h4><ol id="EN-US_TOPIC_0031107266__ol5405292620557"><li id="EN-US_TOPIC_0031107266__li584178495530">Obtain the private key file (.pem file) used when you created the <span id="EN-US_TOPIC_0031107266__text136800010221">ECS</span>.</li><li id="EN-US_TOPIC_0031107266__li3490190117228">Log in to the management console.</li><li id="EN-US_TOPIC_0031107266__li464234814566">Click <span><img id="EN-US_TOPIC_0031107266__en-us_topic_0014250631_image1862675853202121" src="en-us_image_0210779229.png"></span> in the upper left corner and select your region and project.</li><li id="EN-US_TOPIC_0031107266__en-us_topic_0029320966_li40039532224047">Under <strong id="EN-US_TOPIC_0031107266__b52081541033"><span id="EN-US_TOPIC_0031107266__text82071840315">Computing</span></strong>, click <strong id="EN-US_TOPIC_0031107266__b2020864138">Elastic Cloud Server</strong>.</li><li id="EN-US_TOPIC_0031107266__en-us_topic_0029320966_li24833369224047">On the <strong id="EN-US_TOPIC_0031107266__b577318918018">Elastic Cloud Server</strong> page, select the target <span id="EN-US_TOPIC_0031107266__text11584529221">ECS</span>.</li><li id="EN-US_TOPIC_0031107266__li46427097215215">In the <strong id="EN-US_TOPIC_0031107266__b56570316">Operation</strong> column, click <strong id="EN-US_TOPIC_0031107266__b2000944574">More</strong> and select <strong id="EN-US_TOPIC_0031107266__b1314168695">Get Password</strong>.</li><li id="EN-US_TOPIC_0031107266__li50525424215555">Use either of the following methods to obtain the password through the key file:<ul id="EN-US_TOPIC_0031107266__ul6527186921565"><li id="EN-US_TOPIC_0031107266__li1887355017131">Click <strong id="EN-US_TOPIC_0031107266__b842352706144939">Select File</strong> and upload the key file from a local directory.</li><li id="EN-US_TOPIC_0031107266__li42486460215639">Copy the key file content to the text field.</li></ul>
</li><li id="EN-US_TOPIC_0031107266__li18672759215816">Click <strong id="EN-US_TOPIC_0031107266__b102668266317244">Get Password</strong> to obtain a random password.</li></ol>
</div>
<div class="section" id="EN-US_TOPIC_0031107266__section1118765310423"><h4 class="sectiontitle">Obtaining the Password Through APIs</h4><ol id="EN-US_TOPIC_0031107266__ol507546510433"><li id="EN-US_TOPIC_0031107266__li17213488101942">Obtain the private key file (.pem file) used when you created the <span id="EN-US_TOPIC_0031107266__text356411314017">ECS</span>.</li><li id="EN-US_TOPIC_0031107266__li1110886810299">Set up the API calling environment.</li><li id="EN-US_TOPIC_0031107266__li54866977184131">Call APIs. For details, see <a href="https://docs.otc.t-systems.com/api/ecs/en-us_topic_0020805967.html" target="_blank" rel="noopener noreferrer">API Usage Guidelines</a> in <em id="EN-US_TOPIC_0031107266__i84235269711913">Elastic Cloud Server API Reference</em>.</li><li id="EN-US_TOPIC_0031107266__li5770130102852"><a name="EN-US_TOPIC_0031107266__li5770130102852"></a><a name="li5770130102852"></a>Obtain the ciphertext password.<p id="EN-US_TOPIC_0031107266__p44462590102854"><a name="EN-US_TOPIC_0031107266__li5770130102852"></a><a name="li5770130102852"></a>Call the password obtaining APIs to obtain the ciphertext password of the public key encrypted using RSA. The API URI is in the format "GET /v2/{<em id="EN-US_TOPIC_0031107266__i842352697152819">tenant_id</em>}/servers/{<em id="EN-US_TOPIC_0031107266__i842352697152825">server_id</em>}/os-server-password".</p>

2
docs/ecs/umn/en-us_topic_0031523135.html
View File

@ -27,7 +27,7 @@
</li><li id="EN-US_TOPIC_0031523135__li17273849113530">(Optional) Select a <strong id="EN-US_TOPIC_0031523135__b84235270615319">License Type</strong> (<strong id="EN-US_TOPIC_0031523135__b842352706153129">Use license from the system</strong> or <strong id="EN-US_TOPIC_0031523135__b842352706153134">Bring your own license (BYOL)</strong>) if the changed OS running on your ECS is billed. For more details, see <a href="en-us_topic_0046566932.html">License Types</a>.<div class="p" id="EN-US_TOPIC_0031523135__p57004530113530">The following OSs are billed:<ul id="EN-US_TOPIC_0031523135__ul43278730113530"><li id="EN-US_TOPIC_0031523135__en-us_topic_0046566932_li2586589022251">SUSE Linux Enterprise Server</li><li id="EN-US_TOPIC_0031523135__en-us_topic_0046566932_li6521605722253">Oracle Enterprise Linux</li><li id="EN-US_TOPIC_0031523135__en-us_topic_0046566932_li37000181205155">Red Hat Enterprise Linux</li></ul>
</div>
</li><li id="EN-US_TOPIC_0031523135__li5336143212240">Configure the login mode.<p id="EN-US_TOPIC_0031523135__p1154194111115"><a name="EN-US_TOPIC_0031523135__li5336143212240"></a><a name="li5336143212240"></a>If the target <span id="EN-US_TOPIC_0031523135__text1916311471252">ECS</span> uses key pair authentication, you can replace the original key pair.</p>
</li><li id="EN-US_TOPIC_0031523135__en-us_topic_0031523135_en-us_topic_0024911405_li4798821517833">Click <strong id="EN-US_TOPIC_0031523135__b153798544917">OK</strong>.</li><li id="EN-US_TOPIC_0031523135__en-us_topic_0031523135_en-us_topic_0024911405_li45992498111556"><a name="EN-US_TOPIC_0031523135__en-us_topic_0031523135_en-us_topic_0024911405_li45992498111556"></a><a name="en-us_topic_0031523135_en-us_topic_0024911405_li45992498111556"></a>On the <strong id="EN-US_TOPIC_0031523135__b155074211453">Change ECS OS</strong> page, confirm the settings, and click <strong id="EN-US_TOPIC_0031523135__b95751929154917">Submit</strong>.<p id="EN-US_TOPIC_0031523135__p4013850816820">After the application is submitted, the status <strong id="EN-US_TOPIC_0031523135__b84235270616717">Changing OS</strong> is displayed. When this status disappears, the OS change is complete.</p>
</li><li id="EN-US_TOPIC_0031523135__en-us_topic_0031523135_en-us_topic_0024911405_li4798821517833">Click <strong id="EN-US_TOPIC_0031523135__b153798544917">OK</strong>.</li><li id="EN-US_TOPIC_0031523135__en-us_topic_0031523135_en-us_topic_0024911405_li45992498111556"><a name="EN-US_TOPIC_0031523135__en-us_topic_0031523135_en-us_topic_0024911405_li45992498111556"></a><a name="en-us_topic_0031523135_en-us_topic_0024911405_li45992498111556"></a>On the <strong id="EN-US_TOPIC_0031523135__b13373172575011">Change ECS OS</strong> page, confirm the specifications, and click <strong id="EN-US_TOPIC_0031523135__b182849562519">Submit</strong>.<p id="EN-US_TOPIC_0031523135__p4013850816820">After the application is submitted, the status <strong id="EN-US_TOPIC_0031523135__b84235270616717">Changing OS</strong> is displayed. When this status disappears, the OS change is complete.</p>
<div class="note" id="EN-US_TOPIC_0031523135__note1993244016842"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0031523135__p3492635716815">A temporary <span id="EN-US_TOPIC_0031523135__text26231188142">ECS</span> is created during the OS changing process. After the process is complete, this <span id="EN-US_TOPIC_0031523135__text1418210226147">ECS</span> will be automatically deleted.</p>
</div></div>
</li></ol>

9
docs/ecs/umn/en-us_topic_0035470096.html
View File

@ -8,15 +8,16 @@
<p id="EN-US_TOPIC_0035470096__p1985920011446">The format is defined as follows:</p>
<ul id="EN-US_TOPIC_0035470096__ul5780315811459"><li id="EN-US_TOPIC_0035470096__li5046637411459"><strong id="EN-US_TOPIC_0035470096__b1468984664418">A</strong> specifies the ECS type. For example, <strong id="EN-US_TOPIC_0035470096__b106951046104414">s</strong> indicates a general-purpose ECS, <strong id="EN-US_TOPIC_0035470096__b5696204644416">c</strong> a general computing-plus ECS, and <strong id="EN-US_TOPIC_0035470096__b8696134612442">m</strong> a memory-optimized ECS.</li><li id="EN-US_TOPIC_0035470096__li5154418311459"><strong id="EN-US_TOPIC_0035470096__b5569188194819">B</strong> specifies the type ID. For example, <strong id="EN-US_TOPIC_0035470096__b8210154611507">3</strong> in <strong id="EN-US_TOPIC_0035470096__b1191504725013">s3</strong> indicates the third-generation general-purpose ECS.</li><li id="EN-US_TOPIC_0035470096__li6124446611459"><strong id="EN-US_TOPIC_0035470096__b1780433431194419">C</strong> specifies the flavor size, such as medium, large, xlarge, 2xlarge, 4xlarge, or 8xlarge.</li><li id="EN-US_TOPIC_0035470096__li3693402711546"><strong id="EN-US_TOPIC_0035470096__b84235270611859">D</strong> specifies the ratio of memory to vCPUs expressed in a digit. For example, value <strong id="EN-US_TOPIC_0035470096__b842352706111144">4</strong> indicates that the ratio of memory to vCPUs is 4.</li></ul>
</div>
<div class="section" id="EN-US_TOPIC_0035470096__section3154475711225"><h4 class="sectiontitle">Obtaining Specifications When Creating an ECS</h4><p id="EN-US_TOPIC_0035470096__en-us_topic_0030888081_en-us_topic_0029599331_p43304173161639">Specifications for the ECS being created are located in the specifications list.</p>
<div class="fignone" id="EN-US_TOPIC_0035470096__fig64292023143619"><span class="figcap"><b>Figure 1 </b>ECS specifications</span><br><span><img id="EN-US_TOPIC_0035470096__image2131101111256" src="en-us_image_0172453607.png" title="Click to enlarge" class="imgResize"></span></div>
<div class="section" id="EN-US_TOPIC_0035470096__section3154475711225"><h4 class="sectiontitle">How Do I Know My ECS Flavor?</h4><p id="EN-US_TOPIC_0035470096__en-us_topic_0030888081_en-us_topic_0029599331_p43304173161639">When creating an ECS, you can view the flavors in the flavor list.</p>
<div class="fignone" id="EN-US_TOPIC_0035470096__fig64292023143619"><span class="figcap"><b>Figure 1 </b>ECS flavors</span><br><span><img id="EN-US_TOPIC_0035470096__image2131101111256" src="en-us_image_0172453607.png" title="Click to enlarge" class="imgResize"></span></div>
</div>
<div class="section" id="EN-US_TOPIC_0035470096__section196385116449"><h4 class="sectiontitle">vCPU</h4><p id="EN-US_TOPIC_0035470096__p194105569440">The ECS processor uses the hyper-threading technology. The CPU exposes two execution contexts per physical core. This means that one physical core now works like two "logical cores" that can handle different software threads.</p>
<div class="section" id="EN-US_TOPIC_0035470096__section196385116449"><h4 class="sectiontitle">vCPU</h4><p id="EN-US_TOPIC_0035470096__p194105569440">The processor uses the hyper-threading technology. The CPU exposes two execution contexts per physical core. This means that one physical core now works like two "logical cores" that can handle different software threads.</p>
<p id="EN-US_TOPIC_0035470096__p0840205565113">For example, a 10-core physical CPU contains 20 vCPUs (threads).</p>
</div>
<div class="section" id="EN-US_TOPIC_0035470096__section9843135016217"><h4 class="sectiontitle">Network QoS</h4><p id="EN-US_TOPIC_0035470096__p2719863452">Network QoS uses basic technologies to improve the quality of network communication. A network with QoS enabled offers predictable network performance and effectively allocates network bandwidth to use network resources.</p>
<p id="EN-US_TOPIC_0035470096__p177731525134614">To obtain the QoS data of an ECS flavor, including the maximum bandwidth, assured bandwidth, maximum intranet PPS, and NIC multi-queue, see <a href="en-us_topic_0177512565.html">A Summary List of ECS Specifications</a>.</p>
<div class="p" id="EN-US_TOPIC_0035470096__p835110576352">The intranet bandwidth and PPS of an ECS are determined based on ECS flavors.<ul id="EN-US_TOPIC_0035470096__ul123521357113516"><li id="EN-US_TOPIC_0035470096__li37913491485">Assured intranet bandwidth: indicates the guaranteed bandwidth allocated to an ECS when network bandwidth contention occurs in the entire network.</li><li id="EN-US_TOPIC_0035470096__li379249134818">Maximum intranet bandwidth: indicates the maximum bandwidth that can be allocated to an ECS when the ECS does not compete for network bandwidth (other ECSs on the host do not have high requirements on network bandwidth).</li><li id="EN-US_TOPIC_0035470096__li2352195783519">Maximum intranet PPS: maximum number of packets that the ECS can transmit and receive per second</li><li id="EN-US_TOPIC_0035470096__li192851238163616">NIC multi-queues: allocates NIC interrupt requests to multiple vCPUs for higher PPS performance and bandwidth</li><li id="EN-US_TOPIC_0035470096__li839012814476">Maximum NICs: maximum number of NICs that can be attached to an ECS.<div class="note" id="EN-US_TOPIC_0035470096__note439042864715"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0035470096__ul1439014285471"><li id="EN-US_TOPIC_0035470096__li239011287472">For instructions about how to test PPS, see <a href="en-us_topic_0115820205.html">How Can I Test Network Performance?</a></li><li id="EN-US_TOPIC_0035470096__li17390182813478">For instructions about how to enable NIC multi-queue, see <a href="en-us_topic_0058758453.html">Enabling NIC Multi-Queue</a>.</li></ul>
<div class="p" id="EN-US_TOPIC_0035470096__p835110576352">The intranet bandwidth and PPS of an ECS are determined by the ECS flavor.<ul id="EN-US_TOPIC_0035470096__ul123521357113516"><li id="EN-US_TOPIC_0035470096__li37913491485">Assured intranet bandwidth: indicates the guaranteed bandwidth allocated to an ECS when there is a network bandwidth contention in the entire network.</li><li id="EN-US_TOPIC_0035470096__li379249134818">Maximum intranet bandwidth: indicates the maximum bandwidth that can be allocated to an ECS when the ECS does not compete for network bandwidth (other ECSs on the host do not have high requirements on network bandwidth).</li><li id="EN-US_TOPIC_0035470096__li2352195783519">Maximum intranet PPS: indicates the maximum ECS capability in sending and receiving packets.<p id="EN-US_TOPIC_0035470096__p167561739502"><a name="EN-US_TOPIC_0035470096__li2352195783519"></a><a name="li2352195783519"></a>PPS: packets per second, indicates the number of packets sent per second. It is usually used to measure the network performance.</p>
</li><li id="EN-US_TOPIC_0035470096__li192851238163616">NIC multi-queues: allocates NIC interrupt requests to multiple vCPUs for higher PPS performance and bandwidth</li><li id="EN-US_TOPIC_0035470096__li839012814476">Maximum NICs: indicates the maximum number of NICs that can be attached to an ECS.<div class="note" id="EN-US_TOPIC_0035470096__note439042864715"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0035470096__ul1439014285471"><li id="EN-US_TOPIC_0035470096__li239011287472">For instructions about how to test PPS, see <a href="en-us_topic_0115820205.html">How Can I Test Network Performance?</a></li><li id="EN-US_TOPIC_0035470096__li17390182813478">For instructions about how to enable NIC multi-queue, see <a href="en-us_topic_0058758453.html">Enabling NIC Multi-Queue</a>.</li></ul>
</div></div>
</li></ul>
</div>

2
docs/ecs/umn/en-us_topic_0035470099.html
View File

@ -255,7 +255,7 @@
</li></ol>
</div></div>
</li></ul>
</li><li id="EN-US_TOPIC_0035470099__en-us_topic_0088142885_li1717385122398">The local disk data of a D2 ECS may be lost due to some reasons, such as physical server breakdown or local disk damage. If your application does not use the data reliability architecture, it is a good practice to use EVS disks to build your ECS.</li><li id="EN-US_TOPIC_0035470099__en-us_topic_0088142885_li2034693822398">When a D2 ECS is deleted, its local disk data is automatically deleted. Back up the data before deleting such an ECS. Deleting local disk data is time-consuming. Therefore, a D2 ECS requires a longer period of time than other ECSs for releasing resources.</li><li id="EN-US_TOPIC_0035470099__en-us_topic_0088142885_li4890471922398">Do not store long-term service data in local disks. Instead, back up data in a timely manner and use a high availability data architecture. Store long-term service data in EVS disks.</li><li id="EN-US_TOPIC_0035470099__en-us_topic_0088142885_li1242239722417">Local disks can only be purchased during ECS creation. The quantity and capacity of your local disks are determined according to the specifications of your ECS.</li></ul>
</li><li id="EN-US_TOPIC_0035470099__en-us_topic_0088142885_li1717385122398">The local disk data of a D2 ECS may be lost due to some reasons, such as physical server breakdown or local disk damage. If your application does not use the data reliability architecture, it is a good practice to use EVS disks to build your ECS.</li><li id="EN-US_TOPIC_0035470099__en-us_topic_0088142885_li2034693822398">When a D2 ECS is deleted, its local disk data is automatically deleted. Back up the data before deleting such an ECS. Deleting local disk data is time-consuming, so releasing resources is slow.</li><li id="EN-US_TOPIC_0035470099__en-us_topic_0088142885_li4890471922398">Do not store long-term service data in local disks. Instead, back up data in a timely manner and use a high availability data architecture. Store long-term service data in EVS disks.</li><li id="EN-US_TOPIC_0035470099__en-us_topic_0088142885_li1242239722417">Local disks can only be purchased during ECS creation. The quantity and capacity of your local disks are determined according to the specifications of your ECS.</li></ul>
</div>
</div>
<div>

22
docs/ecs/umn/en-us_topic_0035470100.html
View File

@ -130,17 +130,17 @@
</table>
</div>
</div>
<div class="section" id="EN-US_TOPIC_0035470100__section1792295234211"><h4 class="sectiontitle">Scenarios</h4><ul id="EN-US_TOPIC_0035470100__ul1747111313338"><li id="EN-US_TOPIC_0035470100__li1947119315335">Applications<p id="EN-US_TOPIC_0035470100__p114710393311"><a name="EN-US_TOPIC_0035470100__li1947119315335"></a><a name="li1947119315335"></a>H2 and HL1: High-performance computing (HPC), big data, and Artificial Intelligence (AI)</p>
</li><li id="EN-US_TOPIC_0035470100__li1147203113313">Application scenarios<p id="EN-US_TOPIC_0035470100__p747213353313"><a name="EN-US_TOPIC_0035470100__li1147203113313"></a><a name="li1147203113313"></a>H2 and HL1</p>
<ul id="EN-US_TOPIC_0035470100__ul247312320331"><li id="EN-US_TOPIC_0035470100__li204732353318">High-performance hardware: The ratio of memory to vCPU is 8:1, and a large number of multi-thread physical CPUs are available to provide high-performance storage I/O and high-throughput network connections.</li><li id="EN-US_TOPIC_0035470100__li204736313336">Designed for HPC clusters: Multiple HL1 ECSs can be clustered to install scalable, clustered file system, such as Lustre. HPC applications running on H2 ECSs can read and modify the data stored in the ECSs.</li><li id="EN-US_TOPIC_0035470100__li114731037333">RDMA network connection: Same as H2 ECSs, HL1 ECSs also offer RDMA network using EDR 100 Gbit/s InfiniBand NICs. HL1 ECSs can communicate with H2 ECSs with RDMA protocol. In addition, HL1 ECSs can access EVS disks over the RDMA protocol, which allows up to 56 Gbit/s storage bandwidth.</li></ul>
</li><li id="EN-US_TOPIC_0035470100__li17474123183311">Application scenarios<p id="EN-US_TOPIC_0035470100__p747433163311"><a name="EN-US_TOPIC_0035470100__li17474123183311"></a><a name="li17474123183311"></a>H2 and HL1 ECSs provide computing capabilities for clusters with a large memory, good connectivity between nodes, and high storage I/O. The typical application scenarios include HPC, big data, and AI. In HPC solution, HL1 ECSs are perfectly suited for the Lustre parallel distributed file system, generally used for large-scale cluster computing.</p>
<p id="EN-US_TOPIC_0035470100__p84741136330">For example, in HPC scenario, H2 ECSs can be used as compute nodes, and HL1 ECSs can be used as storage nodes.</p>
<div class="section" id="EN-US_TOPIC_0035470100__section1792295234211"><h4 class="sectiontitle">Scenarios</h4><ul id="EN-US_TOPIC_0035470100__ul1747111313338"><li id="EN-US_TOPIC_0035470100__li1947119315335">Applications<p id="EN-US_TOPIC_0035470100__p114710393311"><a name="EN-US_TOPIC_0035470100__li1947119315335"></a><a name="li1947119315335"></a>H2 and Hl1: High-performance computing (HPC), big data, and Artificial Intelligence (AI)</p>
</li><li id="EN-US_TOPIC_0035470100__li1147203113313">Application scenarios<p id="EN-US_TOPIC_0035470100__p747213353313"><a name="EN-US_TOPIC_0035470100__li1147203113313"></a><a name="li1147203113313"></a>H2 and Hl1</p>
<ul id="EN-US_TOPIC_0035470100__ul247312320331"><li id="EN-US_TOPIC_0035470100__li204732353318">High-performance hardware: The ratio of memory to vCPU is 8:1, and a large number of multi-thread physical CPUs are available to provide high-performance storage I/O and high-throughput network connections.</li><li id="EN-US_TOPIC_0035470100__li204736313336">Designed for HPC clusters: Multiple Hl1 ECSs can be clustered to install scalable, clustered file system, such as Lustre. HPC applications running on H2 ECSs can read and modify the data stored in the ECSs.</li><li id="EN-US_TOPIC_0035470100__li114731037333">RDMA network connection: Same as H2 ECSs, Hl1 ECSs also offer RDMA network using EDR 100 Gbit/s InfiniBand NICs. Hl1 ECSs can communicate with H2 ECSs with RDMA protocol. In addition, Hl1 ECSs can access EVS disks over the RDMA protocol, which allows up to 56 Gbit/s storage bandwidth.</li></ul>
</li><li id="EN-US_TOPIC_0035470100__li17474123183311">Application scenarios<p id="EN-US_TOPIC_0035470100__p747433163311"><a name="EN-US_TOPIC_0035470100__li17474123183311"></a><a name="li17474123183311"></a>H2 and Hl1 ECSs provide computing capabilities for clusters with a large memory, good connectivity between nodes, and high storage I/O. The typical application scenarios include HPC, big data, and AI. In HPC solution, Hl1 ECSs are perfectly suited for the Lustre parallel distributed file system, generally used for large-scale cluster computing.</p>
<p id="EN-US_TOPIC_0035470100__p84741136330">For example, in HPC scenario, H2 ECSs can be used as compute nodes, and Hl1 ECSs can be used as storage nodes.</p>
</li></ul>
</div>
<div class="section" id="EN-US_TOPIC_0035470100__section3551415510283"><h4 class="sectiontitle">Features</h4><p id="EN-US_TOPIC_0035470100__p6169740610289">High-performance computing ECSs have the following features:</p>
<ul id="EN-US_TOPIC_0035470100__ul30901477102834"><li id="EN-US_TOPIC_0035470100__li25466125102834">Large memory capacity and more processor cores than other types of ECSs</li><li id="EN-US_TOPIC_0035470100__li62807138102845">Up to 32 vCPUs</li><li id="EN-US_TOPIC_0035470100__li56066977204829">H2 and HL1 ECSs use InfiniBand NICs that provide a bandwidth of 100 Gbit/s.</li><li id="EN-US_TOPIC_0035470100__li17935614203945">HL1 ECSs can use the following types of EVS disks as system disk and data disk:<p id="EN-US_TOPIC_0035470100__p445304620409"><a name="EN-US_TOPIC_0035470100__li17935614203945"></a><a name="li17935614203945"></a>High I/O (performance-optimized I)</p>
<ul id="EN-US_TOPIC_0035470100__ul30901477102834"><li id="EN-US_TOPIC_0035470100__li25466125102834">Large memory capacity and more processor cores than other types of ECSs</li><li id="EN-US_TOPIC_0035470100__li62807138102845">Up to 32 vCPUs</li><li id="EN-US_TOPIC_0035470100__li56066977204829">H2 and Hl1 ECSs use InfiniBand NICs that provide a bandwidth of 100 Gbit/s.</li><li id="EN-US_TOPIC_0035470100__li17935614203945">Hl1 ECSs can use the following types of EVS disks as system disk and data disk:<p id="EN-US_TOPIC_0035470100__p445304620409"><a name="EN-US_TOPIC_0035470100__li17935614203945"></a><a name="li17935614203945"></a>High I/O (performance-optimized I)</p>
<p id="EN-US_TOPIC_0035470100__p4007741720409">Ultra-high I/O (latency-optimized)</p>
</li><li id="EN-US_TOPIC_0035470100__li1552840811116">HL1 ECSs support 56 Gbit shared high I/O storage.<p id="EN-US_TOPIC_0035470100__p37896208172113"><a name="EN-US_TOPIC_0035470100__li1552840811116"></a><a name="li1552840811116"></a>To support 56 Gbit shared high I/O storage, you only need to attach high I/O (performance-optimized I) or ultra-high I/O (latency-optimized) EVS disks to target HL1 ECSs.</p>
</li><li id="EN-US_TOPIC_0035470100__li1552840811116">Hl1 ECSs support 56 Gbit shared high I/O storage.<p id="EN-US_TOPIC_0035470100__p37896208172113"><a name="EN-US_TOPIC_0035470100__li1552840811116"></a><a name="li1552840811116"></a>To support 56 Gbit shared high I/O storage, you only need to attach high I/O (performance-optimized I) or ultra-high I/O (latency-optimized) EVS disks to target Hl1 ECSs.</p>
</li></ul>
</div>
<div class="section" id="EN-US_TOPIC_0035470100__section11683564103115"><h4 class="sectiontitle">Notes on Using H2 ECSs</h4><ul id="EN-US_TOPIC_0035470100__ul28795795103351"><li id="EN-US_TOPIC_0035470100__li6293836016353">H2 ECSs do not support OS reinstallation or change.</li><li id="EN-US_TOPIC_0035470100__li2957432816353">H2 ECSs do not support specifications modification.</li><li id="EN-US_TOPIC_0035470100__li28617379163511">H2 ECSs do not support cold migration, live migration, or HA.</li><li id="EN-US_TOPIC_0035470100__li935721021619"><a href="#EN-US_TOPIC_0035470100__table192771727112217">Table 3</a> lists the OSs supported by H2 ECSs.
@ -176,9 +176,9 @@
</li><li id="EN-US_TOPIC_0035470100__li400496121194">H2 ECSs use InfiniBand NICs that provide a bandwidth of 100 Gbit/s.</li><li id="EN-US_TOPIC_0035470100__li4181675610821">Each H2 ECS uses one PCIe 3.2 TB SSD card for temporary local storage.</li><li id="EN-US_TOPIC_0035470100__li3049386411946">If an H2 ECS is created using a private image, install an InfiniBand NIC driver on the ECS after the ECS creation following the instructions provided by Mellanox. Download the required version (4.2-1.0.0.0) of InfiniBand NIC driver from the official Mellanox website and install the driver by following the instructions provided by Mellanox.<ul id="EN-US_TOPIC_0035470100__ul39673800112337"><li id="EN-US_TOPIC_0035470100__li24962954112332">InfiniBand NIC type: <span class="parmvalue" id="EN-US_TOPIC_0035470100__parmvalue748518566142929"><b>Mellanox Technologies ConnectX-4 Infiniband HBA (MCX455A-ECAT)</b></span></li><li id="EN-US_TOPIC_0035470100__li8393429112358">Mellanox official website: <a href="http://www.mellanox.com/" target="_blank" rel="noopener noreferrer">http://www.mellanox.com/</a></li><li id="EN-US_TOPIC_0035470100__li46521583144614">NIC driver download path: <a href="https://network.nvidia.com/products/infiniband-drivers/linux/mlnx_ofed/" target="_blank" rel="noopener noreferrer">https://network.nvidia.com/products/infiniband-drivers/linux/mlnx_ofed/</a></li></ul>
</li><li id="EN-US_TOPIC_0035470100__li4951377311549">For SUSE H2 ECSs, if IP over InfiniBand (IPoIB) is required, you must manually configure an IP address for the InfiniBand NIC after installing the InfiniBand driver. For details, see <a href="en-us_topic_0083225171.html">How Can I Manually Configure an IP Address for an InfiniBand NIC?</a></li><li id="EN-US_TOPIC_0035470100__li2356792611282">After you delete an H2 ECS, the data stored in SSDs is automatically cleared. Therefore, do not store persistence data into SSDs during ECS running.</li></ul>
</div>
<div class="section" id="EN-US_TOPIC_0035470100__section10721258203459"><h4 class="sectiontitle">Notes on Using HL1 ECSs</h4><ul id="EN-US_TOPIC_0035470100__ul4302655220366"><li id="EN-US_TOPIC_0035470100__li16593109204138">HL1 ECSs only support the attachment of high I/O (performance-optimized I) and ultra-high I/O (latency-optimized) EVS disks.<p id="EN-US_TOPIC_0035470100__p6694708171846"><a name="EN-US_TOPIC_0035470100__li16593109204138"></a><a name="li16593109204138"></a>To support 56 Gbit shared high I/O storage, you only need to attach high I/O (performance-optimized I) or ultra-high I/O (latency-optimized) EVS disks to target HL1 ECSs.</p>
</li><li id="EN-US_TOPIC_0035470100__li25572732203713">HL1 ECSs do not support specifications modification.</li><li id="EN-US_TOPIC_0035470100__li44397844204037">HL1 ECSs use InfiniBand NICs that provide a bandwidth of 100 Gbit/s.</li><li id="EN-US_TOPIC_0035470100__li2353082593959">HL1 ECSs created using a private image must have the InfiniBand NIC driver installed. Download the required version (4.2-1.0.0.0) of InfiniBand NIC driver from the official Mellanox website and install the driver by following the instructions provided by Mellanox.<ul id="EN-US_TOPIC_0035470100__ul1045084093959"><li id="EN-US_TOPIC_0035470100__li2694870093959">InfiniBand NIC type: <span class="parmvalue" id="EN-US_TOPIC_0035470100__parmvalue1073888698"><b>Mellanox Technologies ConnectX-4 Infiniband HBA (MCX455A-ECAT)</b></span></li><li id="EN-US_TOPIC_0035470100__li3536107193959">Mellanox official website: <a href="http://www.mellanox.com/" target="_blank" rel="noopener noreferrer">http://www.mellanox.com/</a></li></ul>
</li><li id="EN-US_TOPIC_0035470100__li35926083111552">For SUSE HL1 ECSs, if IPoIB is required, you must manually configure an IP address for the InfiniBand NIC after installing the InfiniBand driver. For details, see <a href="en-us_topic_0083225171.html">How Can I Manually Configure an IP Address for an InfiniBand NIC?</a></li><li id="EN-US_TOPIC_0035470100__li16497101912286"><a href="#EN-US_TOPIC_0035470100__table204972196287">Table 4</a> lists the OSs supported by HL1 ECSs.
<div class="section" id="EN-US_TOPIC_0035470100__section10721258203459"><h4 class="sectiontitle">Notes on Using Hl1 ECSs</h4><ul id="EN-US_TOPIC_0035470100__ul4302655220366"><li id="EN-US_TOPIC_0035470100__li16593109204138">HL1 ECSs only support the attachment of high I/O (performance-optimized I) and ultra-high I/O (latency-optimized) EVS disks.<p id="EN-US_TOPIC_0035470100__p6694708171846"><a name="EN-US_TOPIC_0035470100__li16593109204138"></a><a name="li16593109204138"></a>To support 56 Gbit shared high I/O storage, you only need to attach high I/O (performance-optimized I) or ultra-high I/O (latency-optimized) EVS disks to target Hl1 ECSs.</p>
</li><li id="EN-US_TOPIC_0035470100__li25572732203713">Hl1 ECSs do not support specifications modification.</li><li id="EN-US_TOPIC_0035470100__li44397844204037">Hl1 ECSs use InfiniBand NICs that provide a bandwidth of 100 Gbit/s.</li><li id="EN-US_TOPIC_0035470100__li2353082593959">Hl1 ECSs created using a private image must have the InfiniBand NIC driver installed. Download the required version (4.2-1.0.0.0) of InfiniBand NIC driver from the official Mellanox website and install the driver by following the instructions provided by Mellanox.<ul id="EN-US_TOPIC_0035470100__ul1045084093959"><li id="EN-US_TOPIC_0035470100__li2694870093959">InfiniBand NIC type: <span class="parmvalue" id="EN-US_TOPIC_0035470100__parmvalue1742625603"><b>Mellanox Technologies ConnectX-4 Infiniband HBA (MCX455A-ECAT)</b></span></li><li id="EN-US_TOPIC_0035470100__li3536107193959">Mellanox official website: <a href="http://www.mellanox.com/" target="_blank" rel="noopener noreferrer">http://www.mellanox.com/</a></li></ul>
</li><li id="EN-US_TOPIC_0035470100__li35926083111552">For SUSE Hl1 ECSs, if IPoIB is required, you must manually configure an IP address for the InfiniBand NIC after installing the InfiniBand driver. For details, see <a href="en-us_topic_0083225171.html">How Can I Manually Configure an IP Address for an InfiniBand NIC?</a></li><li id="EN-US_TOPIC_0035470100__li16497101912286"><a href="#EN-US_TOPIC_0035470100__table204972196287">Table 4</a> lists the OSs supported by Hl1 ECSs.
<div class="tablenoborder"><a name="EN-US_TOPIC_0035470100__table204972196287"></a><a name="table204972196287"></a><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0035470100__table204972196287" frame="border" border="1" rules="all"><caption><b>Table 4 </b>Supported OS versions</caption><thead align="left"><tr id="EN-US_TOPIC_0035470100__en-us_topic_0035470100_row11278327192211"><th align="left" class="cellrowborder" valign="top" width="49.95%" id="mcps1.3.6.2.6.2.2.3.1.1"><p id="EN-US_TOPIC_0035470100__en-us_topic_0035470100_p19278162716225">OS</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="50.05%" id="mcps1.3.6.2.6.2.2.3.1.2"><p id="EN-US_TOPIC_0035470100__en-us_topic_0035470100_p8278112752216">Version</p>
@ -208,7 +208,7 @@
</tbody>
</table>
</div>
</li><li id="EN-US_TOPIC_0035470100__li57288538182023">Charging an HL1 ECS is stopped when it is stopped.</li></ul>
</li><li id="EN-US_TOPIC_0035470100__li57288538182023">Charging an Hl1 ECS is stopped when it is stopped.</li></ul>
</div>
<div class="section" id="EN-US_TOPIC_0035470100__section26607449225539"><h4 class="sectiontitle">Related Links</h4><ul id="EN-US_TOPIC_0035470100__ul7086781175927"><li id="EN-US_TOPIC_0035470100__li65158884175927"><a href="en-us_topic_0058758453.html">Enabling NIC Multi-Queue</a></li><li id="EN-US_TOPIC_0035470100__li23974359175927"><a href="en-us_topic_0058747426.html">How Can I Check Whether the Network Communication Is Normal Between Two ECSs Equipped with an InfiniBand NIC Driver?</a></li></ul>
</div>

156
docs/ecs/umn/en-us_topic_0035550301.html
View File

File diff suppressed because it is too large Load Diff

4
docs/ecs/umn/en-us_topic_0035643949.html
View File

@ -19,12 +19,12 @@
</tr>
<tr id="EN-US_TOPIC_0035643949__row17252528164719"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.3.1.1 "><p id="EN-US_TOPIC_0035643949__p162521428144711"><a href="en-us_topic_0021426802.html">Resetting the Password for Logging In to a Windows ECS</a></p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.3.1.2 "><p id="EN-US_TOPIC_0035643949__p11252172864710">The password reset plug-ins have not been installed.</p>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.3.1.2 "><p id="EN-US_TOPIC_0035643949__p11252172864710">The password reset plug-in has not been installed.</p>
</td>
</tr>
<tr id="EN-US_TOPIC_0035643949__row122524283473"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.3.1.1 "><p id="EN-US_TOPIC_0035643949__p1325262884715"><a href="en-us_topic_0021427650.html">Resetting the Password for Logging In to a Linux ECS</a></p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.3.1.2 "><p id="EN-US_TOPIC_0035643949__p1468216387506">The password reset plug-ins have not been installed.</p>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.3.1.2 "><p id="EN-US_TOPIC_0035643949__p1468216387506">The password reset plug-in has not been installed.</p>
</td>
</tr>
</tbody>

2
docs/ecs/umn/en-us_topic_0038024694.html
View File

@ -6,8 +6,6 @@
</li><li id="EN-US_TOPIC_0038024694__li199896412293">Application scenarios<p id="EN-US_TOPIC_0038024694__p789411216236"><a name="EN-US_TOPIC_0038024694__li199896412293"></a><a name="li199896412293"></a>OLAP and OLTP applications with hyper-threading enabled</p>
</li></ul>
</div>
<div class="section" id="EN-US_TOPIC_0038024694__section60740876172648"><h4 class="sectiontitle">Specifications</h4>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0038024694__table2918193115615" frame="border" border="1" rules="all"><caption><b>Table 1 </b>E3 ECS specifications</caption><thead align="left"><tr id="EN-US_TOPIC_0038024694__row59341131185617"><th align="left" class="cellrowborder" valign="top" width="12.000000000000002%" id="mcps1.3.2.3.2.10.1.1"><p id="EN-US_TOPIC_0038024694__p1893453117564">Flavor</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="10.110000000000001%" id="mcps1.3.2.3.2.10.1.2"><p id="EN-US_TOPIC_0038024694__p15934431195619">vCPUs</p>

19
docs/ecs/umn/en-us_topic_0041169567.html
View File

@ -8,7 +8,18 @@
</th>
</tr>
</thead>
<tbody><tr id="EN-US_TOPIC_0041169567__row4641146173810"><td class="cellrowborder" valign="top" width="18.970000000000002%" headers="mcps1.3.1.1.3.1.1 "><p id="EN-US_TOPIC_0041169567__p8642446133818">2023-03-04</p>
<tbody><tr id="EN-US_TOPIC_0041169567__row1295203313412"><td class="cellrowborder" valign="top" width="18.970000000000002%" headers="mcps1.3.1.1.3.1.1 "><p id="EN-US_TOPIC_0041169567__p529616332343">2023-06-27</p>
</td>
<td class="cellrowborder" valign="top" width="81.03%" headers="mcps1.3.1.1.3.1.2 "><p id="EN-US_TOPIC_0041169567__p1329615338346">Added <a href="en-us_topic_0116262067.html">Key Operations Supported by CTS</a>.</p>
</td>
</tr>
<tr id="EN-US_TOPIC_0041169567__row2612158112313"><td class="cellrowborder" valign="top" width="18.970000000000002%" headers="mcps1.3.1.1.3.1.1 "><p id="EN-US_TOPIC_0041169567__p4612168162312">2023-05-10</p>
</td>
<td class="cellrowborder" valign="top" width="81.03%" headers="mcps1.3.1.1.3.1.2 "><p id="EN-US_TOPIC_0041169567__p1861258132311">Modified the following content:</p>
<ul id="EN-US_TOPIC_0041169567__ul350072202310"><li id="EN-US_TOPIC_0041169567__li6999131416258">Added the following I3 flavors in <a href="en-us_topic_0094118976.html">Ultra-high I/O ECSs</a>: i3.2xlarge.8, i3.4xlarge.8, i3.8xlarge.8, i3.12xlarge.8, and i3.16xlarge.8.</li></ul>
</td>
</tr>
<tr id="EN-US_TOPIC_0041169567__row4641146173810"><td class="cellrowborder" valign="top" width="18.970000000000002%" headers="mcps1.3.1.1.3.1.1 "><p id="EN-US_TOPIC_0041169567__p8642446133818">2023-03-04</p>
</td>
<td class="cellrowborder" valign="top" width="81.03%" headers="mcps1.3.1.1.3.1.2 "><p id="EN-US_TOPIC_0041169567__p1764234618384">Added the following content:</p>
<ul id="EN-US_TOPIC_0041169567__ul127071253917"><li id="EN-US_TOPIC_0041169567__li1270717233920"><a href="en-us_topic_0170232209.html">Permissions Management</a></li><li id="EN-US_TOPIC_0041169567__li3510118183917"><a href="en-us_topic_0170265910.html">Permissions Management</a></li></ul>
@ -443,7 +454,7 @@
<tr id="EN-US_TOPIC_0041169567__row12324184065612"><td class="cellrowborder" valign="top" width="18.970000000000002%" headers="mcps1.3.1.1.3.1.1 "><p id="EN-US_TOPIC_0041169567__p2032414011567">2017-10-18</p>
</td>
<td class="cellrowborder" valign="top" width="81.03%" headers="mcps1.3.1.1.3.1.2 "><p id="EN-US_TOPIC_0041169567__p133246406565">Modified the following content:</p>
<ul id="EN-US_TOPIC_0041169567__ul52016792102046"><li id="EN-US_TOPIC_0041169567__li65497948102046">Changed the OSs supported by H2 and HL1 ECSs in <a href="en-us_topic_0035470100.html">High-Performance Computing ECSs</a>.</li></ul>
<ul id="EN-US_TOPIC_0041169567__ul52016792102046"><li id="EN-US_TOPIC_0041169567__li65497948102046">Changed the OSs supported by H2 and Hl1 ECSs in <a href="en-us_topic_0035470100.html">High-Performance Computing ECSs</a>.</li></ul>
</td>
</tr>
<tr id="EN-US_TOPIC_0041169567__row117249335719"><td class="cellrowborder" valign="top" width="18.970000000000002%" headers="mcps1.3.1.1.3.1.1 "><p id="EN-US_TOPIC_0041169567__p1972414312579">2017-10-06</p>
@ -463,7 +474,7 @@
<tr id="EN-US_TOPIC_0041169567__row94571277117"><td class="cellrowborder" valign="top" width="18.970000000000002%" headers="mcps1.3.1.1.3.1.1 "><p id="EN-US_TOPIC_0041169567__p24570278114">2017-09-18</p>
</td>
<td class="cellrowborder" valign="top" width="81.03%" headers="mcps1.3.1.1.3.1.2 "><p id="EN-US_TOPIC_0041169567__p34571027910">Modified the following content:</p>
<ul id="EN-US_TOPIC_0041169567__ul6121825018151"><li id="EN-US_TOPIC_0041169567__li111754418151">Modified the overview, functions, and notes on using HL1 ECSs in <a href="en-us_topic_0035470100.html">High-Performance Computing ECSs</a>.</li><li id="EN-US_TOPIC_0041169567__li813196418158">Modified notes in "Automatically Recovering ECSs".</li><li id="EN-US_TOPIC_0041169567__li1657727218456">Added notes on using tools, such as ibstat in <a href="en-us_topic_0058747426.html">How Can I Check Whether the Network Communication Is Normal Between Two ECSs Equipped with an InfiniBand NIC Driver?</a></li></ul>
<ul id="EN-US_TOPIC_0041169567__ul6121825018151"><li id="EN-US_TOPIC_0041169567__li111754418151">Modified the overview, functions, and notes on using Hl1 ECSs in <a href="en-us_topic_0035470100.html">High-Performance Computing ECSs</a>.</li><li id="EN-US_TOPIC_0041169567__li813196418158">Modified notes in "Automatically Recovering ECSs".</li><li id="EN-US_TOPIC_0041169567__li1657727218456">Added notes on using tools, such as ibstat in <a href="en-us_topic_0058747426.html">How Can I Check Whether the Network Communication Is Normal Between Two ECSs Equipped with an InfiniBand NIC Driver?</a></li></ul>
</td>
</tr>
<tr id="EN-US_TOPIC_0041169567__row8254132413320"><td class="cellrowborder" valign="top" width="18.970000000000002%" headers="mcps1.3.1.1.3.1.1 "><p id="EN-US_TOPIC_0041169567__p22545248311">2017-09-06</p>
@ -478,7 +489,7 @@
<ul id="EN-US_TOPIC_0041169567__ul18637103101145"><li id="EN-US_TOPIC_0041169567__li2989101227">Added automatic recovery.</li></ul>
<p id="EN-US_TOPIC_0041169567__p18218610129">Modified the following content:</p>
<ul id="EN-US_TOPIC_0041169567__ul31392294101036"><li id="EN-US_TOPIC_0041169567__li1595464101036">Modified description, indicating that SCSI EVS disks cannot be added during ECS creation.</li></ul>
<ul id="EN-US_TOPIC_0041169567__ul95473161312"><li id="EN-US_TOPIC_0041169567__li1554731151320">Deleted the description of exporting the ECS list.</li><li id="EN-US_TOPIC_0041169567__li43493472131">Changed the KVM ECS types to H2, M2, and HL1.</li><li id="EN-US_TOPIC_0041169567__li20711255161314">Confirmed and modified all issues in this document.</li></ul>
<ul id="EN-US_TOPIC_0041169567__ul95473161312"><li id="EN-US_TOPIC_0041169567__li1554731151320">Deleted the description of exporting the ECS list.</li><li id="EN-US_TOPIC_0041169567__li43493472131">Changed the KVM ECS types to H2, M2, and Hl1.</li><li id="EN-US_TOPIC_0041169567__li20711255161314">Confirmed and modified all issues in this document.</li></ul>
</td>
</tr>
<tr id="EN-US_TOPIC_0041169567__row183011751412"><td class="cellrowborder" valign="top" width="18.970000000000002%" headers="mcps1.3.1.1.3.1.1 "><p id="EN-US_TOPIC_0041169567__p16301157111411">2017-08-11</p>

4
docs/ecs/umn/en-us_topic_0085634796.html
View File

@ -3,7 +3,7 @@
<h1 class="topictitle1">Initializing a Windows Data Disk (Windows Server 2008)</h1>
<div id="body8662426"><div class="section" id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_section29374781163839"><h4 class="sectiontitle">Scenarios</h4><p id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_p12171195813313">This section uses Windows Server 2008 R2 Enterprise 64bit to describe how to initialize a data disk attached to <span id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_text1464237810424">a server</span> running Windows.</p>
<p id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_p12929101615417">The maximum disk capacity supported by MBR is 2 TiB, and that supported by GPT is 18 EiB. Therefore, use the GPT partition style if your disk capacity is larger than 2 TiB. To learn more about disk partition styles, see <a href="en-us_topic_0030831623.html">Scenarios and Disk Partitions</a>.</p>
<p id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_p52314842171548">The method for initializing a disk varies depending on the OS running on the <span id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_en-us_topic_0044524669_text849922751145419">server</span>. This document is used for reference only. For the detailed operations and differences, see the product documents of the corresponding OS.</p>
<p id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_p52314842171548">The method for initializing a disk varies slightly depending on the OS running on the <span id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_en-us_topic_0044524669_text849922751145419">server</span>. This document is used for reference only. For the detailed operations and differences, see the product documents of the corresponding OS.</p>
<div class="notice" id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_note135622619317"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_p205672613317">When using a disk for the first time, if you have not initialized it, including creating partitions and file systems, the additional space added to this disk in an expansion later may not be normally used.</p>
</div></div>
</div>
@ -20,7 +20,7 @@
</p></li><li id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_li1703337311146"><span>After making the disk online, the disk status changes from <strong id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_b689355908171858">Offline</strong> to <strong id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_b58237880171858">Not Initialized</strong>. Right-click the disk status and choose <strong id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_b542117337171858">Initialize Disk</strong> from the shortcut menu, as shown in <a href="#EN-US_TOPIC_0085634796__en-us_topic_0044524740_fig409808111224">Figure 3</a>.</span><p><div class="fignone" id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_fig409808111224"><a name="EN-US_TOPIC_0085634796__en-us_topic_0044524740_fig409808111224"></a><a name="en-us_topic_0044524740_fig409808111224"></a><span class="figcap"><b>Figure 3 </b>Initialize Disk</span><br><span><img id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_image2374105914559" src="en-us_image_0132360430.png" title="Click to enlarge" class="imgResize"></span></div>
</p></li><li id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_li34991214122212"><a name="EN-US_TOPIC_0085634796__en-us_topic_0044524740_li34991214122212"></a><a name="en-us_topic_0044524740_li34991214122212"></a><span>In the <strong id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_b842352706165531">Initialize Disk</strong> dialog box, select the target disk, click <strong id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_b842352706165554">MBR (Master Boot Record)</strong> or <strong id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_b12309111733110">GPT (GUID Partition Table)</strong>, and click <strong id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_b842352706165612">OK</strong>, as shown in <a href="#EN-US_TOPIC_0085634796__en-us_topic_0044524740_fig68332918241">Figure 4</a>.</span><p><div class="fignone" id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_fig68332918241"><a name="EN-US_TOPIC_0085634796__en-us_topic_0044524740_fig68332918241"></a><a name="en-us_topic_0044524740_fig68332918241"></a><span class="figcap"><b>Figure 4 </b>Unallocated space</span><br><span><img id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_image15264857111617" src="en-us_image_0097597141.png" title="Click to enlarge" class="imgResize"></span></div>
<div class="p" id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_p46071644112515"><div class="notice" id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_note9642468151238"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_en-us_topic_0085245975_p11834286151113">The maximum disk size supported by MBR is 2 TiB, and that supported by GPT is 18 EiB. Because an EVS data disk currently supports up to 32 TiB, use GPT if your disk size is larger than 2 TiB.</p>
<p id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_en-us_topic_0085245975_p612681541585">If the partition style is changed after the disk has been used, data on the disk will be cleared. Therefore, select an appropriate partition style when initializing the disk. If you must change the partition style to GPT after a disk has been used, it is recommended that you back up the disk data before the change.</p>
<p id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_en-us_topic_0085245975_p612681541585">If the partition style is changed after the disk has been used, all data on the disk will be lost, so take care to select an appropriate partition style when initializing the disk. If you must change the partition style to GPT after a disk has been used, it is recommended that you back up the disk data before the change.</p>
</div></div>
</div>
</p></li><li id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_li19767114614287"><span>Right-click at the unallocated space and choose <strong id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_b985527710499">New Simple Volume</strong> from the shortcut menu, as shown in <a href="#EN-US_TOPIC_0085634796__en-us_topic_0044524740_fig1945583522619">Figure 5</a>.</span><p><div class="fignone" id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_fig1945583522619"><a name="EN-US_TOPIC_0085634796__en-us_topic_0044524740_fig1945583522619"></a><a name="en-us_topic_0044524740_fig1945583522619"></a><span class="figcap"><b>Figure 5 </b>New Simple Volume</span><br><span><img id="EN-US_TOPIC_0085634796__en-us_topic_0044524740_image19502102492612" src="en-us_image_0097597143.png" title="Click to enlarge" class="imgResize"></span></div>

61
docs/ecs/umn/en-us_topic_0085634797.html
View File

File diff suppressed because it is too large Load Diff

66
docs/ecs/umn/en-us_topic_0085634798.html
View File

File diff suppressed because it is too large Load Diff

4
docs/ecs/umn/en-us_topic_0094118976.html
View File

@ -407,9 +407,9 @@
</tbody>
</table>
</div>
</li><li id="EN-US_TOPIC_0094118976__li866163911333">When the physical server where an ultra-high I/O ECS is deployed becomes faulty, the ECS cannot be migrated.<p id="EN-US_TOPIC_0094118976__p12852112517138"><a name="EN-US_TOPIC_0094118976__li866163911333"></a><a name="li866163911333"></a>If the hardware of host machines is faulty or subhealthy and needs to be repaired, you need to stop the ECS.</p>
</li><li id="EN-US_TOPIC_0094118976__li16411373253">If the host where an ultra-high I/O ECS resides becomes faulty, the ECS cannot be restored through live migration.<ul id="EN-US_TOPIC_0094118976__ul14550172322517"><li id="EN-US_TOPIC_0094118976__li18942142152516">If the host is faulty or subhealthy, you need to stop the ECS for hardware repair.</li><li id="EN-US_TOPIC_0094118976__li11944122122512">In case of system maintenance or hardware faults, the ECS will be redeployed (to ensure HA) and cold migrated to another host. The local disk data of the ECS will not be retained.</li></ul>
</li><li id="EN-US_TOPIC_0094118976__li2549184113178">Ultra-high I/O ECSs do not support specifications modification.</li><li id="EN-US_TOPIC_0094118976__en-us_topic_0035470099_en-us_topic_0088142885_li14386295223843">Ultra-high I/O ECSs do not support local disk snapshots or backups.</li><li id="EN-US_TOPIC_0094118976__en-us_topic_0035470099_en-us_topic_0088142885_li18838856223614">Ultra-high I/O ECSs can use local disks, and can also have EVS disks attached to provide a larger storage size. Note the following when using the two types of storage media:<ul id="EN-US_TOPIC_0094118976__en-us_topic_0035470099_en-us_topic_0088142885_ul35331977223614"><li id="EN-US_TOPIC_0094118976__en-us_topic_0035470099_en-us_topic_0088142885_li49552340223614">Only an EVS disk, not a local disk, can be used as the system disk of an ultra-high I/O ECS.</li><li id="EN-US_TOPIC_0094118976__en-us_topic_0035470099_en-us_topic_0088142885_li43317883223614">Both EVS disks and local disks can be used as data disks of an ultra-high I/O ECS.</li><li id="EN-US_TOPIC_0094118976__li1912894412312">An ultra-high I/O ECS can have a maximum of 60 attached disks (including VBD, SCSI, and local disks). An ECS can have a maximum of 60 attached disks, including the system disk. For details about constraints, see <a href="en-us_topic_0018073215.html">Can I Attach Multiple Disks to an ECS?</a></li></ul>
</li><li id="EN-US_TOPIC_0094118976__li7909173042914">Modify the <strong id="EN-US_TOPIC_0094118976__b38401553202110">fstab</strong> file to set automatic disk mounting at ECS start. For details, see <a href="en-us_topic_0085634798.html#EN-US_TOPIC_0085634798__en-us_topic_0084935709_section15839912195453">Setting Automatic Mounting at System Start</a>.</li><li id="EN-US_TOPIC_0094118976__en-us_topic_0035470099_en-us_topic_0088142885_li1717385122398">The local disk data of an ultra-high I/O ECS may be lost due to some reasons, such as physical server breakdown or local disk damage. If your application does not use the data reliability architecture, it is a good practice to use EVS disks to build your ECS.</li><li id="EN-US_TOPIC_0094118976__li6549174117179">After an ultra-high I/O ECS is deleted, the data on local NVMe SSDs is automatically deleted. Back up the data before deleting such an ECS. Deleting local disk data is time-consuming. Therefore, an ultra-high I/O ECS requires a longer period of time than other ECSs for releasing resources.</li><li id="EN-US_TOPIC_0094118976__li175491741191710">The data reliability of local disks depends on the reliability of physical servers and hard disks, which are SPOF-prone. It is a good practice to use data redundancy mechanisms at the application layer to ensure data availability. Use EVS disks to store service data that needs to be stored for a long time.</li><li id="EN-US_TOPIC_0094118976__li7292749141819">The device name of a local disk attached to an ultra-high I/O ECS is <strong id="EN-US_TOPIC_0094118976__b5497105251714">/dev/nvme0n1</strong> or <strong id="EN-US_TOPIC_0094118976__b0503652101712">/dev/nvme0n2</strong>.</li><li id="EN-US_TOPIC_0094118976__li117233308228">The basic resources, including vCPUs, memory, and image of an ultra-high I/O ECS will continue to be billed after the ECS is stopped. To stop the ECS from being billed, delete it and its associated resources. </li></ul>
</li><li id="EN-US_TOPIC_0094118976__li7909173042914">Modify the <strong id="EN-US_TOPIC_0094118976__b38401553202110">fstab</strong> file to set automatic disk mounting at ECS start. For details, see <a href="en-us_topic_0085634798.html#EN-US_TOPIC_0085634798__en-us_topic_0084935709_section15839912195453">Configuring Automatic Mounting at System Start</a>.</li><li id="EN-US_TOPIC_0094118976__en-us_topic_0035470099_en-us_topic_0088142885_li1717385122398">The local disk data of an ultra-high I/O ECS may be lost due to some reasons, such as physical server breakdown or local disk damage. If your application does not use the data reliability architecture, it is a good practice to use EVS disks to build your ECS.</li><li id="EN-US_TOPIC_0094118976__li6549174117179">After an ultra-high I/O ECS is deleted, the data on local NVMe SSDs is automatically deleted. Back up the data before deleting such an ECS. Deleting local disk data is time-consuming, so releasing resources is slow.</li><li id="EN-US_TOPIC_0094118976__li175491741191710">The data reliability of local disks depends on the reliability of physical servers and hard disks, which are SPOF-prone. It is a good practice to use data redundancy mechanisms at the application layer to ensure data availability. Use EVS disks to store service data that needs to be stored for a long time.</li><li id="EN-US_TOPIC_0094118976__li7292749141819">The device name of a local disk attached to an ultra-high I/O ECS is <strong id="EN-US_TOPIC_0094118976__b5497105251714">/dev/nvme0n1</strong> or <strong id="EN-US_TOPIC_0094118976__b0503652101712">/dev/nvme0n2</strong>.</li><li id="EN-US_TOPIC_0094118976__li117233308228">The basic resources, including vCPUs, memory, and image of an ultra-high I/O ECS will continue to be billed after the ECS is stopped. To stop the ECS from being billed, delete it and its associated resources. </li></ul>
</div>
<div class="section" id="EN-US_TOPIC_0094118976__section121148461119"><h4 class="sectiontitle">Handling Damaged Local Disks Attached to an ECS of I Series</h4><p id="EN-US_TOPIC_0094118976__p398664513218">If a local disk attached to an ECS is damaged, perform the following operations to handle this issue:</p>
<p id="EN-US_TOPIC_0094118976__p16492123493916"><strong id="EN-US_TOPIC_0094118976__b16804131412409">For a Linux ECS:</strong></p>

60
docs/ecs/umn/en-us_topic_0097289624.html
View File

File diff suppressed because it is too large Load Diff

256
docs/ecs/umn/en-us_topic_0116262067.html Normal file
View File

File diff suppressed because it is too large Load Diff

2
docs/ecs/umn/en-us_topic_0116266206.html
View File

@ -5,6 +5,8 @@
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="en-us_topic_0116262067.html">Key Operations Supported by CTS</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="en-us_topic_0116266207.html">Viewing Audit Logs</a></strong><br>
</li>
</ul>

4
docs/ecs/umn/en-us_topic_0117490178.html
View File

@ -3,7 +3,7 @@
<h1 class="topictitle1">Initializing a Windows Data Disk (Windows Server 2019)</h1>
<div id="body8662426"><div class="section" id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_section29374781163839"><h4 class="sectiontitle">Scenarios</h4><p id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_p12171195813313">This section uses Windows Server 2019 Standard 64bit to describe how to initialize a data disk attached to <span id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_text1464237810424">a server</span> running Windows.</p>
<p id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_p8817185417191">The maximum disk capacity supported by MBR is 2 TiB, and that supported by GPT is 18 EiB. Therefore, use the GPT partition style if your disk capacity is larger than 2 TiB. To learn more about disk partition styles, see <a href="en-us_topic_0030831623.html">Scenarios and Disk Partitions</a>.</p>
<p id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_p52314842171548">The method for initializing a disk varies depending on the OS running on the <span id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_en-us_topic_0044524669_text849922751145419">server</span>. This document is used for reference only. For the detailed operations and differences, see the product documents of the corresponding OS.</p>
<p id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_p52314842171548">The method for initializing a disk varies slightly depending on the OS running on the <span id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_en-us_topic_0044524669_text849922751145419">server</span>. This document is used for reference only. For the detailed operations and differences, see the product documents of the corresponding OS.</p>
<div class="notice" id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_note13926451175010"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_en-us_topic_0044524740_p205672613317">When using a disk for the first time, if you have not initialized it, including creating partitions and file systems, the additional space added to this disk in an expansion later may not be normally used.</p>
</div></div>
</div>
@ -20,7 +20,7 @@
</p></li><li id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_li2535853320"><span>In the <strong id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_b20212184910251">Initialize Disk</strong> dialog box, the to-be-initialized disk is selected. Select a disk partition style and click <strong id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_b11120628113016">OK</strong>. In this example, <strong id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_b7881113093010">GPT (GUID Partition Table)</strong> is selected.</span><p><div class="p" id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_p115521330048">The <strong id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_b267754040">Computer Management</strong> window is displayed.<div class="fignone" id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_fig68332918241"><span class="figcap"><b>Figure 4 </b>Computer Management</span><br><span><img id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_image37491117105518" src="en-us_image_0175083507.png" title="Click to enlarge" class="imgResize"></span></div>
</div>
<div class="p" id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_p16552123015416"><div class="notice" id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_note9642468151238"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_en-us_topic_0085245975_p11834286151113">The maximum disk size supported by MBR is 2 TiB, and that supported by GPT is 18 EiB. Because an EVS data disk currently supports up to 32 TiB, use GPT if your disk size is larger than 2 TiB.</p>
<p id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_en-us_topic_0085245975_p612681541585">If the partition style is changed after the disk has been used, data on the disk will be cleared. Therefore, select an appropriate partition style when initializing the disk. If you must change the partition style to GPT after a disk has been used, it is recommended that you back up the disk data before the change.</p>
<p id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_en-us_topic_0085245975_p612681541585">If the partition style is changed after the disk has been used, all data on the disk will be lost, so take care to select an appropriate partition style when initializing the disk. If you must change the partition style to GPT after a disk has been used, it is recommended that you back up the disk data before the change.</p>
</div></div>
</div>
</p></li><li id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_li19767114614287"><span>Right-click at the unallocated disk space and choose <strong id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_b842352706195547">New Simple Volume</strong> from the shortcut menu.</span><p><div class="p" id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_p1255310301449">The <strong id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_b03172043153315">New Simple Volume Wizard</strong> window is displayed.<div class="fignone" id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_fig19509202633615"><span class="figcap"><b>Figure 5 </b>New Simple Volume Wizard</span><br><span><img id="EN-US_TOPIC_0117490178__en-us_topic_0115255433_image1713903555519" src="en-us_image_0175083508.png" title="Click to enlarge" class="imgResize"></span></div>

183
docs/ecs/umn/en-us_topic_0177512565.html
View File

File diff suppressed because it is too large Load Diff