Shulou(Shulou.com)06/01 Report--

Editor to share with you how to achieve the basic configuration and deployment of OpenStack, I believe most people do not know much about it, so share this article for your reference, I hope you can learn a lot after reading this article, let's learn about it!

Configuration and deployment

A key part of the scalability of cloud computing is the amount of work required to operate it. To reduce your operating costs, you need to set up and use automated deployment and configuration facilities. This includes the system automatically installing the initial configuration of the operating system and automatically centrally coordinating the configuration of all services, thereby reducing manual workload and error opportunities.

Automatic deployment

The automated deployment system installs and configures the operating system on the new server without intervention, after the most streamlined manual work (such as server shelves, MAC IP allocation, power configuration, etc.). A typical solution relies on PXE boot and TFTP servers for the most basic operating system installation, and then switch to an automatic configuration management system.

Both Ubuntu and Red Hat Linux have mechanisms for configuring the operating system, including presets and kickstart, and can be booted over the network. Typically, these are used to boot an automated configuration system. Alternatively, you can deploy an operating system, such as systemimager, using an image-based approach. You can use these two methods in a virtualized infrastructure, such as when you run virtual machines to separate control services and physical infrastructure.

When you create a deployment plan, you need to focus on some important areas, because they are very difficult to change after deployment.

Disk partitions and RAID

The foundation of any operating system is inseparable from the hard drive, because the operating system needs to be installed on the hard drive.

On the hard drive on the server, you must complete the following configuration:

Add partitions to the RAID array

The easiest way is to use a hard disk with the following two partitions:

File system swap space

This setting does not use RAID.

Note: this option is not recommended for production environments, because if the hard drive fails, the entire server will down down. Instead, we recommend that you use more than one hard drive. The number of disks depends on what type of RAID array needs to be built.

We recommend that you select the following disk options:

1: all drives in the partition are arranged horizontally in the same way, as shown in the following figure:

Using this option, you can specify different partitions to different RAID arrays. You can assign partition 1 to / boot partition images of disks 1 and 2. You can also mirror partition 2 of all disks to the root partition. You can also use partition 3 of all hard drives to run on a RAID 10 array as a cinder-volumes LVM partition.

You may end up with unused partitions, such as partition 1 of disks 3 and 4 in this example, which allows the use of disk space. Ihop O performance can be a problem because all the disks in use are used to run all tasks.

2: add a large RAID array based on all raw disks of hardware or software. You can boot, root, swap, and LVM partition this big array. This option is easy to implement and use for all partitions. However, disk Imax O may be affected.

3: assign a specific partition to the entire disk. For example, you can allocate disks 1 and 2 all as boot, root, and swap partition images under RAID 1. Then, allocate disks 3 and 4 all as LVM partitions under RAID 1. Since Iswap O focuses on specific tasks, disk Imax O should be better. Of course, the partition in LVM will be much smaller.

As the choice of most architectures, the correct answer depends on your own environment.

Network configuration

Network configuration is a very big topic that spans many topics in this book. Now, make sure that your server starts with PXE and successfully communicates with the deployment server.

For example, when PXE starts, it is usually not possible to configure the network card of VLAN. In addition, it is usually not possible to start bonded NICs with PXE. In this case, consider using a simple 1 GB switch in a private network with which only your cloud can communicate.

Automatic configuration

The purpose of automatic configuration management is to establish and maintain the consistency of the system without human intervention. You want to keep your deployment consistent so that you can have the same cloud configuration every time and recreate your cloud environment. Use automatic configuration management tools correctly to ensure that all components of the cloud computing system are in a specific state, in addition to simplifying deployment and configuration change propagation. These tools can also test and roll back changes because they are fully repeatable. Fortunately, a lot of work in this area has been done by the OpenStack community. Puppet-a configuration management tool-even provides an official module for OpenStack.

An integral part of the configuration management system is the projects it controls. You should carefully consider whether all the projects you want need to be managed automatically.

Remote management

In our experience, most administrators don't sit next to servers running cloud computing, and many don't necessarily like to access data centers. OpenStack should be configured entirely remotely, but sometimes not everything goes according to plan. In this case, having an out-of-band access (out-of-band) to the node running the OpenStack component would be a boon. The IPMI protocol is a de facto standard and requires hardware support, so it is highly recommended to implement an unattended data center.

In addition, remote power management also needs to be considered. Although IPMI can control the power state of the server, the PDU that can access the server remotely when everything fails is the patron saint.

These are all the contents of the article "how to achieve the basic configuration and deployment of OpenStack". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.