13 KiB
13 KiB
Preparing for the Mirantis OpenStack Deployment
Preparing the Mirantis OpenStack Deployment
Before installation, plan your deployment. Determine the deployment type that is appropriate for you configuration needs. You may want to print this list and make notes indicating your selection so you can be sure you have planned your deployment correctly.
The following table provides a list of configuration steps that you must complete to plan the Mirantis OpenStack deployment.
| Step Description | Additional Information | |
|---|---|---|
| 1 | Consider which deployment mode you will deploy (Multi-node HA or non HA) | For more information, see: Reference Architecture <ref-arch>. |
| 2 | Select a network service (Nova-Network: FlatDHCP, VLAN manager or Neutron: GRE, VLAN). | For more information, see: Network <fuelui-network>. |
| 3 | Prepare all the necessary hardware. | For more information, see: the Mirantis Hardware Bill of Materials calculator, HardwarePrerequisites |
| 4 | Plan a role (or roles) to be assigned to each node server. | A node may act as a controller, compute or storage node - or combine storage or compute role. Network services are automatically installed onto the controller when utilizing the Fuel UI. |
| 5 | Prepare an addressing plan and network association. | Identify the network addresses and VLAN IDs for your Public, floating, Management, Storage, and virtual machine (fixed) networks. For more information on how to plan your network, see: NetworkConfiguration |
| 6 | Prepare a logical network diagram. | For more information, see: NetworkConfiguration |
| 7 | Connect the Fuel and node servers' NICs to the switches. | For more information, see the instructions for your network. |
| 8 | Connect the Fuel and node servers' IPMI cards to the out of band management network. | For more information, see the instructions for your hardware. |
| 9 | Configure access to the node servers through IPMI | For more information, see the IPMI instructions for your hardware. |
| 10 | Prepare the proper physical network configuration (configure switches, routers, etc). | According to your addressing plan and logical network diagram. |
| 11 | Connect the OpenStack networks to the server Ethernet port on each server. | For more information, see the instructions for your routers and/or switches. |
| 12 | Install the Fuel server | For more information, see: FuelQuickInstall. |
Post-installation Configuration Tasks
You must complete the following steps for configuring your OpenStack environment. After completing this stage, configure the parameters for deployment, including networking, storage, and optional parameters.
| Step Description | Additional Information | |
|---|---|---|
| 1 | Point your browser to the Fuel server (on port 8000) | For example: http://10.20.0.2:8000/ |
| 2 | Click on the New OpenStack environment icon to create a new environment. | The Create a new OpenStack Environment wizard launches automatically. |
| 3 | Choose a name for your environment and choose the Operating System and OpenStack distribution. | If you install Mirantis OpenStack, you can select Ubuntu Enterprise Linux or CentOS OpenStack. If you install Red Hat OpenStack, select Red Hat Enterprise Linux. |
| 4 | Choose your Deployment Mode (Multi-node HA or non HA). | High Availability mode requires at least 3 nodes to be assigned as controllers. |
| 5 | Choose your hypervisor. | Current choices from the UI are KVM or QEMU. Additional hypervisors are available through the Mirantis Services engagement. |
| 6 | Select your network service (Nova-network, Neutron with GRE segmentation or Neutron with VLAN segmentation. | If you choose Nova-network, you can choose FlatDHCP or VLAN Manager later in the Network settings tab. |
| 7 | Select your storage backend for Cinder. | If you select default, then the Local Volumes over iSCSI are used as backend for Cinder. If you select Ceph, you must assign at least 2 nodes as Ceph-OSD nodes. |
| 8 | Select your storage backend for Glance. | If you select default, then the local storage in non-HA mode and Swift in HA mode is used as backend for Cinder. Swift will be automatically installed on the controllers. If you select Ceph, you must assign at least 2 nodes as Ceph-OSD nodes. |
| 9 | Choose additional Platform Services. | Savanna enables on-demand provisioning of Hadoop clusters on OpenStack. Murano enables Windows-based datacenter services to be deployed on OpenStack. |
| 10 | Select Create and click on the icon with your named environment. | Additional configuration tabs appear. |
| 11 | In Nodes tab, assign a role or roles to each node server. | A node may act as a controller, compute, or storage node. You can combine a storage role with a controller or compute role. |
| 12 | In Network tab, configure the network settings from the address plan prepared earlier. | If you chose Neutron as your network service, additional sections are available for setting your L2 and L3 configuration. |
| 13 | Click Verify Networks to check and confirm the network configuration. | This sends test frames and 802.1Q tagged frames to each node server to confirm connectivity. |
| 14 | (Optional) In the Settings tab, you can configure or modify the options for Horizon access, scheduler type, logging, and other OpenStack options. | You may also modify your choices for hypervisor, storage, and Platform Services configured before the deployment. |
| 15 | Click the Deploy Changes button. | Mirantis OpenStack deployment may take 15-60 minutes, depending on your the selected options. You can monitor status by opening the Nodes tab or by checking individual node logs in the Logs tab. |
| 16 | Once deployed, run the tests in the Health Check tab to confirm success. | You can run the test groups in parallel or one at a time. |
After you complete these tasks, Mirantis OpenStack is ready to use.
In the following sections, you can view specific examples of deploying Mirantis OpenStack, including complete switch configuration and cabling.
Nova-network <novanetwork>, Neutron <neutron>