Pre-flight checklist
This checklist confirms that the decisions from Planning & Sizing are made and that the environment is ready, before the first package is installed. Each item links to the page that decides it. Work through the list once per deployment and fix what fails before you continue.
The planning decisions are made
- Capacity is calculated: raw space for the user space you promise and RAM for the Master Server.
- Hardware is chosen to match the hardware guidance for each role, Master Servers and Chunkservers in particular.
- The redundancy format is decided: copies or Erasure Coding. The cluster has enough Chunkservers for the chosen Erasure Coding scheme.
- If the cluster spans sites PRO (PRO Edition only): you have chosen between one undivided cluster and locations (when locations help). The vote count across sites is decided, including whether an even count gets a Chunkserver without disks as the tie-breaking vote. The installation itself then follows Divide a new cluster into locations.
The machines are ready
- Every machine runs a supported operating system.
- The machine that serves the GUI, and any machine that runs
mfscli, has the Python release those two need. - PRO PRO (PRO Edition only): the license file is available. Installing it is one of the first deployment steps.
- Every machine runs a time service, so the clocks of the cluster stay synchronized: every machine keeps its clock in step.
The network is ready
- The MTU is the same end to end on every path that carries MooseFS traffic.
- The links meet the bandwidth and latency budget for the planned workload.
- Nothing on the path blocks the ports: every component connects to the Master Server. Clients and Chunkservers connect to every Chunkserver.
The Master Server name resolves on every machine
- Every component resolves the Master Server name to reach the Master Server. That name resolves on every machine of the cluster, Chunkservers and Metaloggers included, not only on the clients: make the Master Server name resolve on every machine.
- In MooseFS PRO PRO (PRO Edition only), every machine resolves that name to the same complete set of addresses, because the resolved list is the roster that leader election uses (DNS carries the list of Master Servers).
When every item passes, installation starts
Continue with preparing the operating system and then installing the server components.