To deploy a file storage cluster in an Arcfra Cloud Operating System cluster using Arcfra Virtualization Engine, that is, in an ACOS (AVE) cluster, and take the scenario where the file storage network reuses the Virtual Distributed Switch (VDS) of the ACOS (AVE) cluster storage network, and the file management network reuses the VDS of the ACOS (AVE) cluster management network as an example. The network topology of the file storage cluster is shown in the following figure:
File management network: The file storage cluster communicates with Arcfra Operation Center (AOC) through this network.
File storage network: The internal storage network of the file storage cluster, through which file controllers exchange data within the file storage cluster.
File access network: The file storage cluster provides file storage services to external clients through this network.
Before deployment, confirm that the ACOS (AVE) cluster has existing VM networks that meet the requirements in the following table.
| File storage cluster network | Network bandwidth requirements | VM network requirements | Requirements for the VDS to which the VM network belongs |
|---|---|---|---|
| File management network | 1 Gbps and above. | Connected to the management network of the ACOS (AVE) cluster. | Associated with at least one network interface on each host of the ACOS (AVE) cluster. |
| File storage network | 10 Gbps and above. | Not associated with other virtual machines, can be exclusively used by file controllers. | |
| File access network | 10 Gbps and above. | Connected to the client. |
Before deployment, you need to provide the following information as shown in the table below based on the planned number of file controllers.
| Network type | IP address | Subnet mask | Gateway |
|---|---|---|---|
| File management network | File controller 1: xx.xx.xx.xx File controller 2: xx.xx.xx.xx ··· File controller n: xx.xx.xx.xx |
xx.xx.xx.xx | xx.xx.xx.xx |
| File storage network | File controller 1: xx.xx.xx.xx File controller 2: xx.xx.xx.xx ··· File controller n: xx.xx.xx.xx |
xx.xx.xx.xx | - |
| File access network | File controller 1: xx.xx.xx.xx File controller 2: xx.xx.xx.xx ··· File controller n: xx.xx.xx.xx |
xx.xx.xx.xx | - |
If the IP address of the clients using the file storage service and the file access IP address of the file storage cluster are not in the same network segment, you need to enable static route configuration. After enabling, one static route corresponds to one client, and each static route needs to be configured with the following information:
Note:
The IP addresses of the file management network, file storage network, and file access network must belong to different network segments.
If the static route is enabled, the route gateway must be in the same network segment as the file access IP.
The IP addresses cannot overlap with any IP addresses within the following CIDR ranges:
- 169.254.0.0/16
- 240.0.0.0/4
- 224.0.0.0/4
- 198.18.0.0/15
- 127.0.0.0/8
- 0.0.0.0/8
AFS ensures high availability of the file management network through the file management Vitual IP (VIP)address. When the file controller hosting the file management VIP fails, it automatically switches to other healthy file controllers to continue providing services.
Therefore, when planning the file management VIP address for the file storage cluster, refer to the following requirements:
AOC can access the cluster through the file management VIP address.
The file management VIP address and the file management IP addresses of the file controllers are in the same subnet.
The file management VIP address cannot overlap with any IP addresses within the following CIDR ranges:
