Show Table of Contents Hide Table of Contents English English 한국어 简体中文 日本語 Multi-page HTML Single-page HTML PDF ePub Deploying Red Hat Hyperconverged Infrastructure1. Known IssuesI. Plan2. Architecture3. Support Requirements3.1. Operating System3.2. Physical Machines3.3. Virtual Machines3.4. Networking3.5. Storage3.5.1. Architecture3.5.2. RAID3.5.3. JBOD3.5.4. Volume Types3.6. Support limitations3.7. Disaster RecoveryII. Deploy4. Deployment Workflow5. Install Host Physical Machines6. Configure Public Key based SSH Authentication7. Configure Red Hat Gluster Storage for Hosted Engine using the Cockpit UI8. Deploy the Hosted Engine using the Cockpit UI9. Configure Red Hat Gluster Storage as a Red Hat Virtualization storage domain9.1. Create the logical network for gluster traffic9.2. Create the master storage domain9.3. Add remaining virtualization hosts to the hosted engineIII. Troubleshoot10. Handling Hosted Engine Deployment Errors11. Cleaning up Automated Red Hat Gluster Storage Deployment ErrorsIV. Verify12. Verify your deploymentV. Reference MaterialA. Configuring encryption during deploymentA.1. Configuring TLS/SSL during deployment using a Certificate Authority signed certificateA.1.1. Before you beginA.1.2. Configuring TLS/SSL encryption using a CA-signed certificateA.2. Configuring TLS/SSL encryption during deployment using a self signed certificateB. Example cleanup configuration files for gdeployC. Understanding the generated gdeploy configuration fileLegal Notice Part III. Troubleshoot 9.3. Add remaining virtualization hosts to the hosted engine 10. Handling Hosted Engine Deployment Errors Where did the comment section go?Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.