Cloudbase-init side effects of auto-expander-play 5 minutes a day OpenStack (154)

This is the 4th chapter in the OpenStack implementation experience sharing series.

One feature of Cloudbase-init is the automatic expansion of Windows's C drive. For example, Windows mirroring is 20G, when deploying instance, the flavor disk definition is 40G, then cloudbase-init automatically expands the C drive to 40G instance deployment.

Cloudbase-init Auto-Expander This operation is what we need, but it has a side effect.

In Windows, we can divide the hard disk into multiple logical disks C:,D: etc., for example, 40G space, the user can give the C disk 20g,d disk 20G, but this for the installation of Cloudbase-init system will have problems. *

Each time the system starts, Cloudbase-init will merge the C and D disks into a C drive.

The solution to this problem is simple: unload the Cloudbase-initso that it is a normal windwos virtual machine. However, if you do a resize operation on instance in OpenStack, you can only expand the disk manually.

the recommended way is : The system disk only for the C drive, if you need D disk, E disk, by adding cinder volume implementation.

The following section discusses the usage techniques for Linux cloud-init.

650) this.width=650; "Src=" http://7xo6kd.com1.z0.glb.clouddn.com/ Upload-ueditor-image-20170222-1487717214801030450.png "title=" http://7xo6kd.com1.z0.glb.clouddn.com/ Upload-ueditor-image-20170222-1487717214801030450.png "alt=" two-dimensional code + fingerprint. png "/>

Cloudbase-init side effects of auto-expander-play 5 minutes a day OpenStack (154)