vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/sfs/umn/sfs_01_0036.html
zhangyue 5da982a576 SFS UMN DOC 
Reviewed-by: Muller, Martin <martin.muller@t-systems.com>
Co-authored-by: zhangyue <zhangyue164@huawei.com>
Co-committed-by: zhangyue <zhangyue164@huawei.com>
2023-05-01 08:03:33 +00:00

94 lines
17 KiB
HTML
Raw Blame History

<a name="sfs_01_0036"></a><a name="sfs_01_0036"></a>
<h1 class="topictitle1">Configuring Multi-VPC Access</h1>
<div id="body1521721681680"><p id="sfs_01_0036__p1144235913116">VPC provisions an isolated virtual network environment defined and managed by yourself, improving the security of cloud resources and simplifying network deployment. When using SFS, a file system and the associated ECSs need to belong to the same VPC for file sharing.</p>
<p id="sfs_01_0036__p694313172198">In addition, VPC can use network access control lists (ACLs) to implement access control. A network ACL is an access control policy system for one or more subnets. Based on inbound and outbound rules, it determines whether data packets are allowed in or out of any associated subnet. In the VPC list of a file system, each time an authorized address is added and corresponding permissions are set, a network ACL is created.</p>
<p id="sfs_01_0036__p85972038153720">For more information about VPC, see the <em id="sfs_01_0036__i98899183816">Virtual Private Cloud User Guide</em>.</p>
<div class="section" id="sfs_01_0036__section89101543712"><h4 class="sectiontitle">Scenarios</h4><p id="sfs_01_0036__p11815182495217">Multi-VPC access can be configured for an SFS Capacity-Oriented file system so that ECSs in different VPCs can share the same file system, as long as the VPCs that the ECSs belong to are added to the VPC list of the file system or the ECS IP addresses are added as authorized IP addresses of the VPCs.</p>
<p id="sfs_01_0036__p2790419134817">This section describes how to configure multi-VPC access for an SFS Capacity-Oriented file system.</p>
</div>
<div class="section" id="sfs_01_0036__section1888617013249"><h4 class="sectiontitle">Restrictions</h4><ul id="sfs_01_0036__ul4452192218241"><li id="sfs_01_0036__li1145242219242">You can add a maximum of 20 VPCs for each file system. A maximum of 400 ACL rules for added VPCs can be created. When adding a VPC, the default IP address 0.0.0.0/0 is automatically added.</li><li id="sfs_01_0036__li3452622182415">If a VPC added to a file system has been deleted from the VPC console, the IP address/address segment of this VPC can still be seen as activated in the file system's VPC list. But this VPC can no longer be used and you are advised to delete it from the list.</li></ul>
</div>
<div class="section" id="sfs_01_0036__section696112185365"><h4 class="sectiontitle">Procedure for SFS Capacity-Oriented</h4><ol id="sfs_01_0036__ol129571239183614"><li id="sfs_01_0036__li430994684419"><span>Log in to the SFS console.</span></li><li id="sfs_01_0036__li24762113720"><span>In the file system list, click the name of the target file system. On the displayed page, locate the <strong id="sfs_01_0036__b233916151456">Authorizations</strong> area.</span></li><li id="sfs_01_0036__li850502324818"><span>If no VPCs are available, create one. You can add multiple VPCs for a file system. Click <span class="uicontrol" id="sfs_01_0036__uicontrol14522195763120"><b>Add Authorized VPC</b></span> and the <span class="wintitle" id="sfs_01_0036__wintitle4726126183019"><b>Add Authorized VPC</b></span> dialog box is displayed. See <a href="#sfs_01_0036__fig8892193084618">Figure 1</a>.</span><p><p id="sfs_01_0036__p598710161333">You can select multiple VPCs from the drop-down list.</p>
<div class="fignone" id="sfs_01_0036__fig8892193084618"><a name="sfs_01_0036__fig8892193084618"></a><a name="fig8892193084618"></a><span class="figcap"><b>Figure 1 </b>Adding VPCs</span><br><span><img id="sfs_01_0036__image6568125384015" src="en-us_image_0000001515917280.png"></span></div>
</p></li><li id="sfs_01_0036__li1375034443414"><span>Click <span class="uicontrol" id="sfs_01_0036__uicontrol1672354401102455"><b>OK</b></span>. A successfully added VPC is displayed in the list. When adding a VPC, the default IP address <strong id="sfs_01_0036__b191582019999">0.0.0.0/0</strong> is automatically added. The default read/write permission is <strong id="sfs_01_0036__b1323805420918">Read-write</strong>, the default user permission is <strong id="sfs_01_0036__b9232101121015">no_all_squash</strong>, and the default root permission is <strong id="sfs_01_0036__b887187131017">no_root_squash</strong>.</span></li><li id="sfs_01_0036__li172115388229"><span>View the VPC information in the VPC list. For details about the parameters, see <a href="#sfs_01_0036__table99851739124510">Table 1</a>.</span><p>
<div class="tablenoborder"><a name="sfs_01_0036__table99851739124510"></a><a name="table99851739124510"></a><table cellpadding="4" cellspacing="0" summary="" id="sfs_01_0036__table99851739124510" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Parameter description</caption><thead align="left"><tr id="sfs_01_0036__row18986439164514"><th align="left" class="cellrowborder" valign="top" width="50%" id="mcps1.3.6.2.5.2.1.2.3.1.1"><p id="sfs_01_0036__p13986133914512">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="50%" id="mcps1.3.6.2.5.2.1.2.3.1.2"><p id="sfs_01_0036__p2986193915452">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="sfs_01_0036__row159865391455"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.6.2.5.2.1.2.3.1.1 "><p id="sfs_01_0036__p4986163914454">Name</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.6.2.5.2.1.2.3.1.2 "><p id="sfs_01_0036__p398663944512">Name of the added VPC, for example, <strong id="sfs_01_0036__b842352706102553">vpc-01</strong></p>
</td>
</tr>
<tr id="sfs_01_0036__row1398615399451"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.6.2.5.2.1.2.3.1.1 "><p id="sfs_01_0036__p1998693919458">Authorized Addresses/Segments</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.6.2.5.2.1.2.3.1.2 "><p id="sfs_01_0036__p2986939164516">Number of added IP addresses or IP address segments</p>
</td>
</tr>
<tr id="sfs_01_0036__row498693904514"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.6.2.5.2.1.2.3.1.1 "><p id="sfs_01_0036__p1998643964514">Operation</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.6.2.5.2.1.2.3.1.2 "><p id="sfs_01_0036__p55891167164624">The value can be <strong id="sfs_01_0036__b842352706164653">Add</strong> or <strong id="sfs_01_0036__b842352706164656">Delete</strong>. <strong id="sfs_01_0036__b842352706164735">Add</strong>: Adds an authorized VPC. This operation configures the IP address, read/write permission, user permission, user root permission, and priority. For details, see <a href="#sfs_01_0036__table1242824684814">Table 2</a>. <strong id="sfs_01_0036__b842352706165531">Delete</strong>: Deletes this VPC.</p>
</td>
</tr>
</tbody>
</table>
</div>
</p></li><li id="sfs_01_0036__li1592219953017"><span>Click <span><img id="sfs_01_0036__image444354516361" src="en-us_image_0000001516076852.png"></span> on the left of the VPC name to view details about the IP addresses/segments added to this VPC. You can add, edit, or delete IP addresses/segments. In the <span class="parmname" id="sfs_01_0036__parmname298195713010"><b>Operation</b></span> column of the target VPC, click <span class="uicontrol" id="sfs_01_0036__uicontrol20982185753017"><b>Add</b></span>. The <span class="uicontrol" id="sfs_01_0036__uicontrol1857612373316"><b>Add Authorized Address/Segment</b></span> dialog box is displayed. See <a href="#sfs_01_0036__fig3912714184914">Figure 2</a>. <a href="#sfs_01_0036__table1242824684814">Table 2</a> describes the parameters to be configured.</span><p><div class="fignone" id="sfs_01_0036__fig3912714184914"><a name="sfs_01_0036__fig3912714184914"></a><a name="fig3912714184914"></a><span class="figcap"><b>Figure 2 </b>Adding an authorized address or segment</span><br><span><img id="sfs_01_0036__image189820251427" src="en-us_image_0000001567076705.png"></span></div>
<div class="tablenoborder"><a name="sfs_01_0036__table1242824684814"></a><a name="table1242824684814"></a><table cellpadding="4" cellspacing="0" summary="" id="sfs_01_0036__table1242824684814" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Parameter description</caption><thead align="left"><tr id="sfs_01_0036__row18428154644810"><th align="left" class="cellrowborder" valign="top" width="25%" id="mcps1.3.6.2.6.2.2.2.3.1.1"><p id="sfs_01_0036__p842884615488">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="75%" id="mcps1.3.6.2.6.2.2.2.3.1.2"><p id="sfs_01_0036__p19428104612489">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="sfs_01_0036__row242814617489"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.6.2.6.2.2.2.3.1.1 "><p id="sfs_01_0036__p11428104616485">Authorized Address/Segment</p>
</td>
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.3.6.2.6.2.2.2.3.1.2 "><ul id="sfs_01_0036__ul13324116192216"><li id="sfs_01_0036__li1261189122212">Enter one IPv4 address or address segment at a time.</li><li id="sfs_01_0036__li357151522214">The entered IPv4 address or address segment must be valid and cannot be one starting with 0 except 0.0.0.0/0. If you add <strong id="sfs_01_0036__b24422010192617">0.0.0.0/0</strong>, any IP address within this VPC will be authorized for accessing the file system. Class D and class E IP addresses are not supported. Therefore, do not enter an IP address or address segment starting with any number ranging from 224 to 255, for example 224.0.0.1 or 255.255.255.255. IP addresses or address segments starting with 127 are also not supported. If an invalid IP address or address segment is used, the access rule may fail to be added or the added access rule cannot take effect.</li><li id="sfs_01_0036__li49791420172214">Do not enter multiple IP addresses (separated using commas) at a time. For example, do not enter 10.0.1.32,10.5.5.10.</li><li id="sfs_01_0036__li1832413612223">If you enter an IP address segment, enter it in the format of <em id="sfs_01_0036__i39008571274">IP address/mask</em>. For example, enter 192.168.1.0/24. Do not enter in the format of 192.168.1.0-255 or 192.168.1.0-192.168.1.255. The number of bits in a subnet mask must be an integer ranging from 0 to 31, and mask value <strong id="sfs_01_0036__b18561934112812">0</strong> is valid only in 0.0.0.0/0.</li></ul>
</td>
</tr>
<tr id="sfs_01_0036__row144285465480"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.6.2.6.2.2.2.3.1.1 "><p id="sfs_01_0036__p4428946144813">Read-Write Permission</p>
</td>
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.3.6.2.6.2.2.2.3.1.2 "><p id="sfs_01_0036__p144281746204810">The value can be <strong id="sfs_01_0036__b1993124163617">Read-write</strong> or <strong id="sfs_01_0036__b65273913364">Read-only</strong>. The default value is <strong id="sfs_01_0036__b6645857123512">Read-write</strong>.</p>
</td>
</tr>
<tr id="sfs_01_0036__row4428104634818"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.6.2.6.2.2.2.3.1.1 "><p id="sfs_01_0036__p242894610484">User Permission</p>
</td>
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.3.6.2.6.2.2.2.3.1.2 "><p id="sfs_01_0036__p144285462480">Whether to retain the user identifier (UID) and group identifier (GID) of the shared directory. The default value is <strong id="sfs_01_0036__b35617280106">no_all_squash</strong>.</p>
<ul id="sfs_01_0036__ul1829105884712"><li id="sfs_01_0036__li1059210110489"><strong id="sfs_01_0036__b2918132125215">all_squash</strong>: The UID and GID of a shared directory are mapped to user <strong id="sfs_01_0036__b558762611616">nobody</strong>, which is applicable to public directories.</li><li id="sfs_01_0036__li582905810476"><strong id="sfs_01_0036__b45475389525">no_all_squash</strong>: The UID and GID of a shared directory are retained.</li></ul>
</td>
</tr>
<tr id="sfs_01_0036__row1942884614813"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.6.2.6.2.2.2.3.1.1 "><p id="sfs_01_0036__p442816468484">User Root Permission</p>
</td>
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.3.6.2.6.2.2.2.3.1.2 "><p id="sfs_01_0036__p19428446204818">Whether to allow the root permission of the client. The default value is <strong id="sfs_01_0036__b139817316101">no_root_squash</strong>.</p>
<ul id="sfs_01_0036__ul202950116498"><li id="sfs_01_0036__li3295717496"><strong id="sfs_01_0036__b19579155013523">root_squash</strong>: Clients cannot access as the <strong id="sfs_01_0036__b8737141111813">root</strong> user. When a client accesses as the <strong id="sfs_01_0036__b83701013121810">root</strong> user, the user is mapped to the <strong id="sfs_01_0036__b964011173181">nobody</strong> user.</li><li id="sfs_01_0036__li22953111495"><strong id="sfs_01_0036__b74998567522">no_root_squash</strong>: Clients are allowed to access as the <strong id="sfs_01_0036__b18458191611912">root</strong> user who has full control and access permissions of the root directories.</li></ul>
</td>
</tr>
<tr id="sfs_01_0036__row144282465483"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.6.2.6.2.2.2.3.1.1 "><p id="sfs_01_0036__p1542834624815">Priority</p>
</td>
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.3.6.2.6.2.2.2.3.1.2 "><p id="sfs_01_0036__p1764711356199">The value must be an integer ranging from <strong id="sfs_01_0036__b1926211414217">0</strong> to <strong id="sfs_01_0036__b763510644213">100</strong>. <strong id="sfs_01_0036__b1765312117429">0</strong> indicates the highest priority, and <strong id="sfs_01_0036__b6839113184216">100</strong> indicates the lowest priority. In the same VPC, the permission of the IP address or address segment with the highest priority is preferentially used. If some IP addresses or address segments are of the same priority, the permission of the most recently added or modified one is used.</p>
<p id="sfs_01_0036__p20428114604814">For example, if the IP address for mounting is 10.1.1.32 and both 10.1.1.32 (read/write) with priority <strong id="sfs_01_0036__b3542162110301">100</strong> and 10.1.1.0/24 (read-only) with priority <strong id="sfs_01_0036__b147721131184317">50</strong> meet the requirements, the permission of 10.1.1.0/24 (read-only) with priority <strong id="sfs_01_0036__b1475923344312">50</strong> is used. That is, if there is no other authorized priority, the permission of all IP addresses in the 10.1.1.0/24 segment, including 10.1.1.32, is read-only.</p>
</td>
</tr>
</tbody>
</table>
</div>
<div class="note" id="sfs_01_0036__note3469176175419"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="sfs_01_0036__p446936195411">For an ECS in VPC A, its IP address can be added to the authorized IP address list of VPC B, but the file system of VPC B cannot be mounted to this ECS. The VPC of the ECS and the file system must be the same.</p>
</div></div>
</p></li></ol>
</div>
<div class="section" id="sfs_01_0036__section394553315387"><h4 class="sectiontitle">Verification</h4><p id="sfs_01_0036__p628912374387">After another VPC is configured for the file system, if the file system can be mounted to ECSs in the VPC and the ECSs can access the file system, the configuration is successful.</p>
</div>
<div class="section" id="sfs_01_0036__section311012135113"><h4 class="sectiontitle">Example</h4><p id="sfs_01_0036__p62481817412">A user creates an SFS Capacity-Oriented file system A in VPC-B. The network segment is <strong id="sfs_01_0036__b8274421274">10.0.0.0/16</strong>. The user has an ECS D in VPC-C, using the private IP address <strong id="sfs_01_0036__b17808141892817">192.168.10.11</strong> in network segment <strong id="sfs_01_0036__b6820172652813">192.168.10.0/24</strong>. If the user wants to mount file system A to ECS D and allow the file system to be read and written, the user needs to add VPC-C to file system A's VPC list, add ECS D's private IP address or address segment to the authorized addresses of VPC-C, and then set <strong id="sfs_01_0036__b13231181511318">Read-Write Permission</strong> to <strong id="sfs_01_0036__b52111943153114">Read-write</strong>.</p>
<p id="sfs_01_0036__p17819122716491">The user purchases an ECS F that uses the private IP address <strong id="sfs_01_0036__b681344714385">192.168.10.22</strong> in the VPC-C network segment <strong id="sfs_01_0036__b99484414386">192.168.10.0/24</strong>. If the user wants ECS F to have only the read permission for file system A and its read priority to be lower than that of ECS D, the user needs to add ECS F's private IP address to VPC-C's authorized addresses, set <strong id="sfs_01_0036__b64751714113516">Read-Write Permission</strong> to <strong id="sfs_01_0036__b127092110355">Read-only</strong>, and set <strong id="sfs_01_0036__b4312136183114">Priority</strong> to an integer between 0 and 100 and greater than the priority set for ECS D.</p>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="sfs_01_0035.html">Network Configuration</a></div>
</div>
</div>
View Git Blame Copy Permalink