WIXLIB

MOS Deployment Guideversion latest

MOS Deployment GuideMOS UssuriContentsCopyright notice1Preface2About this documentation set2Intended audience2Technology Preview support scope3Documentation history3Conventions3Introduction5Plan the deployment6Provision a Container Cloud bare metal management cluster7Configure host operating system8Configure kernel modules8Configure networking8Configure networking on a server with three NICsConfigure networking on a server with five NICsConfigure hosts files for a deployment with TF91215Create a MOS managed cluster16Add bare metal hosts to the MOS cluster17Add machines to the MOS cluster18Deploy a Ceph cluster19Deploy OpenStack21Deploy an OpenStack cluster21Advanced OpenStack configuration (optional)26Enable LVM ephemeral storage27Enable DPDK with OVS29Enable SR-IOV with OVS31Advanced configuration for OpenStack compute nodes33Enable huge pages for OpenStack34Configure CPU isolation for an instance35Configure custom CPU topologies36Configure PCI passthrough for guests37 2021, Mirantis Inc.Page i

MOS Deployment GuideAccess OpenStack after deploymentMOS Ussuri38Configure DNS to access OpenStack38Access your OpenStack environment41Access OpenStack using the Kubernetes built-in admin CLI42Access an OpenStack environment through Horizon42Access OpenStack through CLI from your local machine42Troubleshoot an OpenStack deployment44Debugging the HelmBundle controller44Verify the Helm releases statuses44Verify the status of a HelmBundle release45Debugging the OpenStack ControllerThe openstack-operator pod is missingDebugging the OsDpl CR454646The osdpl has DEPLOYED false46Some pods are stuck in Init46Some HelmBundles are not present47Deploy Tungsten Fabric48Tungsten Fabric deployment prerequisites48Deploy Tungsten Fabric49Advanced Tungsten Fabric configuration (optional)51Enable DPDK for Tungsten Fabric52Enable SR-IOV for Tungsten Fabric54Specify custom vRouter settings56Access the Tungsten Fabric web UI57Troubleshoot the Tungsten Fabric deployment58Enable debug logs for the Tungsten Fabric services58Troubleshoot access to the Tungsten Fabric web UI59 2021, Mirantis Inc.Page ii

MOS Deployment GuideMOS UssuriCopyright notice2021 Mirantis, Inc. All rights reserved.This product is protected by U.S. and international copyright and intellectual property laws. Nopart of this publication may be reproduced in any written, electronic, recording, or photocopyingform without written permission of Mirantis, Inc.Mirantis, Inc. reserves the right to modify the content of this document at any time without priornotice. Functionality described in the document may not be available at the moment. Thedocument contains the latest information at the time of publication.Mirantis, Inc. and the Mirantis Logo are trademarks of Mirantis, Inc. and/or its affiliates in theUnited States an other countries. Third party trademarks, service marks, and names mentionedin this document are the properties of their respective owners. 2021, Mirantis Inc.Page 1

MOS Deployment GuideMOS UssuriPreface About this documentation set Intended audience Technology Preview support scope Documentation history ConventionsAbout this documentation setThis documentation provides information on how to deploy and operate a Mirantis OpenStack forKubernetes (MOS) environment. The documentation is intended to help operators to understandthe core concepts of the product. The documentation provides sufficient information to deployand operate the solution.The information provided in this documentation set is being constantly improved and amendedbased on the feedback and kind requests from the consumers of MOS.The following table lists the guides included in the documentation set you are reading:Guides listGuidePurposeMOS ReferenceArchitectureLearn the fundamentals of MOS reference architecture toappropriately plan your deploymentMOS Deployment GuideDeploy a MOS environment of a preferred configuration usingsupported deployment profiles tailored to the demands of specificbusiness casesMOS Operations GuideOperate your MOS environmentMOS Release notesLearn about new features and bug fixes in the current MOS versionThe MOS documentation home page contains references to all guides included in thisdocumentation set. For your convenience, we provide all guides in HTML (default), single-pageHTML, PDF, and ePUB formats. To use the preferred format of a guide, select the required optionfrom the Formats menu next to the guide title.Intended audienceThis documentation is intended for engineers who have the basic knowledge of Linux,virtualization and containerization technologies, Kubernetes API and CLI, Helm and Helm charts,Mirantis Kubernetes Engine (MKE), and OpenStack. 2021, Mirantis Inc.Page 2

MOS Deployment GuideMOS UssuriTechnology Preview support scopeThis documentation set includes description of the Technology Preview features. A TechnologyPreview feature provide early access to upcoming product innovations, allowing customers toexperience the functionality and provide feedback during the development process. TechnologyPreview features may be privately or publicly available and neither are intended for productionuse. While Mirantis will provide support for such features through official channels, normalService Level Agreements do not apply. Customers may be supported by Mirantis CustomerSupport or Mirantis Field Support.As Mirantis considers making future iterations of Technology Preview features generallyavailable, we will attempt to resolve any issues that customers experience when using thesefeatures.During the development of a Technology Preview feature, additional components may becomeavailable to the public for testing. Because Technology Preview features are being underdevelopment, Mirantis cannot guarantee the stability of such features. As a result, if you areusing Technology Preview features, you may not be able to seamlessly upgrade to subsequentreleases of that feature. Mirantis makes no guarantees that Technology Preview features will begraduated to a generally available product release.The Mirantis Customer Success Organization may create bug reports on behalf of support casesfiled by customers. These bug reports will then be forwarded to the Mirantis Product team forpossible inclusion in a future release.Documentation historyThe following table contains the released revision of the documentation set you are reading:Release dateDescriptionNovember 05, 2020MOS GA releaseDecember 23, 2020MOS GA Update releaseMarch 01, 2021MOS 21.1ConventionsThis documentation set uses the following conventions in the HTML format:Documentation conventionsConventionDescriptionboldface fontInline CLI tools and commands, titles of the procedures andsystem response examples, table titlesmonospaced fontFiles names and paths, Helm charts parameters and their values,names of packages, nodes names and labels, and so onitalic fontInformation that distinguishes some concept or termLinksExternal links and cross-references, footnotes 2021, Mirantis Inc.Page 3

MOS Deployment GuideMOS UssuriMain menu menu itemGUI elements that include any part of interactive user interfaceand menu navigationSuperscriptSome extra, brief informationMessages of a generic meaning that may be useful for the userNoteThe Note blockInformation that prevents a user from mistakes and undesirableconsequences when following the proceduresCaution!The Caution blockWarningThe Warning blockMessages that include details that can be easily missed, butshould not be ignored by the user and are valuable beforeproceedingList of references that may be helpful for understanding of somerelated tools, concepts, and so onSeealsoThe See also blockLearn moreUsed in the Release Notes to wrap a list of internal references tothe reference architecture, deployment and operation proceduresspecific to a newly implemented product featureThe Learn moreblock 2021, Mirantis Inc.Page 4

MOS Deployment GuideMOS UssuriIntroductionMirantis OpenStack for Kubernetes (MOS) enables the operator to create, scale, update, andupgrade OpenStack deployments on Kubernetes through a declarative API.The Kubernetes built-in features, such as flexibility, scalability, and declarative resourcedefinition make MOS a robust solution. 2021, Mirantis Inc.Page 5

MOS Deployment GuideMOS UssuriPlan the deploymentThe detailed plan of any Mirantis OpenStack for Kubernetes (MOS) deployment is determined ona per-cloud basis. For the MOS reference architecture and design overview, see MOS ReferenceArchitecture.Also, read through Mirantis Container Cloud Reference Architecture: Container Cloud bare metalas a MOS managed cluster is deployed on top of a baremetal-based Container Cloudmanagement cluster.NoteOne of the industry best practices is to verify every new update or configuration change ina non-customer-facing environment before applying it to production. Therefore, Mirantisrecommends having a staging cloud, deployed and maintained along with the productionclouds. The recommendation is especially applicable to the environments that: Receive updates often and use continuous delivery. For example, any non-isolateddeployment of Mirantis Container Cloud and Mirantis OpenStack for Kubernetes(MOS). Have significant deviations from the reference architecture or third party extensionsinstalled. Are managed under the Mirantis OpsCare program. Run business-critical workloads where even the slightest application downtime isunacceptable.A typical staging cloud is a complete copy of the production environment including thehardware and software configurations, but with a bare minimum of compute and storagecapacity. 2021, Mirantis Inc.Page 6

MOS Deployment GuideMOS UssuriProvision a Container Cloud bare metalmanagement clusterThe bare metal management system enables the Infrastructure Operator to deploy ContainerCloud on a set of bare metal servers. It also enables Container Cloud to deploy MOS managedclusters on bare metal servers without a pre-provisioned operating system.To provision your bare metal management cluster, refer to Mirantis Container Cloud DeploymentGuide: Deploy a baremetal-based management cluster 2021, Mirantis Inc.Page 7

MOS Deployment GuideMOS UssuriConfigure host operating systemBefore you proceed with the OpenStack deployment, you need to configure the host operatingsystem to run OpenStack.To calculate the required number of hosts, read through Hardware requirements.Configure kernel modulesThe OpenStack Nova and Neutron services may require additional kernel modules to be loadedfor normal operation. This section instructs you on how to enable the required kernel modules.To enable KVMA kernel-based Virtual Machine (KVM) is a virtualization module in the Linux kernel that enablesthe kernel to function as a hypervisor. The KVM-based virtualization is recommended oncompute hosts to provide high performance VMs. See OpenStack Ussuri official documentation:Enable KVM for details.NoteSome systems require that you enable the VT support in the system BIOS. To enable theVT support, refer to the BIOS guides of the manufacturer of your server motherboard.Configure networkingMirantis OpenStack for Kubernetes (MOS) typically requires common/PXE, management, tenant,and storage types of networks. For the details, refer to MOS Reference Architecture: Networking.This section describes how to configure persistent networking on hosts with three and five NICsusing the Mirantis Container Cloud L2 Templates. 2021, Mirantis Inc.Page 8