Openstack implementation management manual-Chapter 1 deployment preparation

Chapter 1. provisioning and deployment(Deployment preparation)

Automatic deployment

Automatic Configuration

Remote Management

A critical part of a cloud's scalability is the amount of effort that it takes to run your cloud. to minimize the operational cost of running your cloud, set up and use an automatic deployment and configuration infrastructure.

A key part of cloud computing's scalability is that you need a lot of energy to run your cloud. To minimize the operating costs of running the cloud, you need to configure the infrastructure with automatic deployment and configuration.

This infrastructure implements des systems to automatically install the operating system's initial configuration and later coordinate the configuration of all services automatically and centrally, which has CES both manual effort and chance for error.

These include the initial configuration for automatic installation of the operating system and the centralized automatic configuration management for subsequent service configurations to reduce the chance of manual operation errors.

Automatic deployment

Disk partitioning and raid

Network Configuration

An automatic deployment system installand configures operating systems on new servers, without intervention, after the absolute minimum amount of manual work, including physical racking, Mac to IP assignment, power configuration, and so on. typically solutions rely on Wrappers und PXE boot and TFTP servers for the basic operating system install, then hand off to an automatic configuration management system.

On the new server, there is an absolute amount of physical labor, including physical shelves, IP addresses assigned by Mac, power configuration, and so on. Then, the system is automatically deployed and configured. Typical solutions include PXE boot and TFTP server-dependent basic operating system installation, and then hand over to an automated configuration management system.

Ubuntu and Red Hat Linux both include mechanisms for operating ing the operating system, including preseed and KickStart, that you can use after a network boot. typically these are used to bootstrap an automatic configuration system. alternatively, you can use an image-based approach for deploying the operating system, such as systemimager. you can use both approaches with a specified alized infrastructure, such as when you run VMS to separate your control services and physical infrastructure.

Both Ubuntu and Red Hat Linux include the configuration mechanism operating system, including preseed and KickStart, which can be used to boot from the network. These are usually used to guide an automated Configuration System. You can also deploy an operating system, such as systemimager, using an image-based method. You can use these two methods and virtualized infrastructure, such as when you run the Control Service separately from the physical infrastructure virtual machine.

When you create a deployment plan, focus on a few vital areas because they are very hard to modify post-deployment.

When creating a deployment plan, you should focus on some important areas, because they will be very difficult to modify after deployment.

Disk partitioning and raid

At the very base of any operating system are the hard drives on which the OS is installed.

Install a basic hard disk operating system on any operating system.

You must complete the following deployments on the server's hard drives:

You must complete the following configurations for the server's hard drive:

• Partitioning Partition
• Adding to a raid array add to raid Array

The simplest option is to use one hard drive with two partitions:

The simplest choice is a hard disk with two partitions:

• File System
• Swap space

Raid is not used in this setup.
Raid is not used in this setting.

Note

This option is not recommended for production because if the hard drive fails, that entire server is down. instead, we recommend that you use more than one disk. the number of disks determine what types of RAID arrays to build. This option is not recommended for production environments, because if the hard drive fails, the entire server is shut down. Instead, we recommend that you use multiple disks. The number of disks determines the type of RAID array to be created.

We recommend that you choose one of the following multiple disk options:
We recommend that you select from the following disk options:

• Option 1:Partition all drives in the same way in a horizontal fashion, as shown in the following disince:
  The horizontal mode of all drives in the partition is shown in the following figure in the same way:

With this option, you can assign different partitions to different raid arrays. you can allocate partition 1 of disk One and two to the/bootpartition mirror. you can make partition 2 of all disks the root partition mirror. you can use partition 3 of all disks for a cinder-volumes LVM partition running on a raid 10 array.
With this option, you can specify different partitions to use different raid arrays. You can allocate the first and second partitions to the/boot partition image. You can give the second partition of all disks to the root partition mirror. You can have cinder-volumes LVM run on the third partition of all disks on the raid 10 array.

While you might end up with unused partitions, such as partition 1 in disk three and four of this example, it allows for maximum utilization off disk space. i/O performance might be an issue due to all disks being used for all tasks.
Although you may end with unused partitions, such as partition 1 in this implementation example 3 and 4, it allows maximum utilization to close disk space. Because the I/O performance of all disks may be a problem for all tasks.

• Option 2: Add all raw disks to one large raid array, Either hardware or software based. you can partition this large array with the boot, root, swap, and LVM areas. this option is simple to implement and uses all partitions. however, disk I/O might suffer.
  Add all original disks to a large raid array, hardware or software-based. You can perform boot, root, swap, and LVM with this raid display. This option is easy to implement and uses all partitions. However, disk I/O performance may be affected.
• Option 3: dedicate entire disks to certain partitions. for example, you cocould allocate disk One and Two entirely to the boot, root, and swap partitions under a RAID 1 mirror. then, allocate disk 3 and 4 entirely to the LVM partition, also under a RAID 1 mirror. disk I/O shoshould be better because I/O is focused on dedicated tasks. however, the LVM partition is much smaller.
  partition the entire disk. For example, you can allocate the first and second disks to use RAID 1 and then partition the boot, root, and swap disks. Then, the allocated disks 3 and 4 Use the LVM partition and the Raid 1 image. Disk I/O should be better because I/O is concentrated in dedicated tasks. However, the LVM partition is much smaller.

As with most architecture choices, the right answer depends on your environment.
There are many architecture choices. The correct answer depends on your environment.

Network Configuration

Network configuration is a very large topic that spans multiple areas of this book. For now, make sure that your servers can PXE boot and successfully communicate with the Deployment Server.
Network configuration is a big topic. This book spans many fields. Now, what you need to do is make sure that your server can be successfully guided with PXE from the deployed server.

For example, you usually cannot configure failed for VLANs when PXE booting. additionally, you usually cannot PXE boot with bonded finished. if you run into this scenario, consider using a simple 1 GB switch in a private network on which only your cloud communicates.
For example, you usually cannot configure the nic pxe boot for a VLAN. In addition, you usually use the bonded Nic PXE boot. In this case, you can use a simple 1 GB switch for cloud communication on a private network.

Automatic Configuration

The purpose of automatic configuration management is to establish and maintain the consistency of a system with no human intervention. you want to maintain consistency in your deployments so you can have the same cloud every time, repeatably. proper use of automatic configuration management tools ensures that components of the cloud systems are in particle states, in addition to simplifying deployment, and configuration change propagation.
The purpose of automatic configuration management is to establish and maintain system consistency through unattended intervention. You want your deployment to be consistent, so you can repeat each time. Correct use of the automatic configuration management tool not only simplifies the automatic deployment release of deployment and configuration changes, but also ensures that each component of the cloud system is in a specific State.

These tools also make it possible to test and roll back changes, as they are fully repeatable. conveniently, a large body of work has been done by the openstack community in this space. puppet-a configuration management tool-even provides official modules for openstack.

These tools also enable people to perform tests and roll back changes because they can be completely repeated. In openstackCommunityA large organization has completed the relevant work. Puppet-a configuration management tool-or even an official openstack Module

An integral part of a configuration management system is the items that it controls. You shoshould carefully consider all of the items that you want, or do not want, to be automatically managed.
A project that can be controlled by a component of the Configuration Management System. You should carefully consider all the projects that you want or do not want that can be managed automatically.

Remote Management

In our experience, most operators don't sit right next to the servers running the cloud, and don't necessarily enjoy visiting the data center. openstack shocould be entirely remotely retriable, but sometimes not everything goes according to plan.
Our experience is that most operators do not sit next to the server and run the cloud. Many users do not necessarily like to access the data center. Openstack should be fully configured remotely, but sometimes not everything goes as planned.

In this instance, having an out-of-band access into nodes running openstack components, is a boon. the ipmi protocol is the de-facto standard here, and acquiring hardware that supports it is highly recommended to achieve that lights-out data center aim.
In this case, it is a good news that an out-of-band Access Node runs openstack. The ipmi protocol is actually the standard here, and obtaining the hardware that supports it is highly recommended to achieve the goal of a data center that lights out.

In addition, consider remote power control as well. while IPMI usually controls the server's power State, having remote access to the PDU that the server is plugged into can really be useful for situations when everything seems wedged.
In addition, remote power control is considered. Although IPMI usually controls the power status of the server, a PDU with remote access can be used only when the server is powered on.