How to clear and recreate the CloudStack Environment

I have had a lot of experience with the CloudStack kids shoes. More or less when I was just getting started with CloudStack, I had to create N times for a Build Environment and delete it to finally run a cloud environment, however, in this process, if you encounter problems and cannot find other solutions, many new users can think of re-creating the environment. In this process, there are several important points to note. Otherwise, even if the environment is re-built, new problems may occur in the new environment due to the residue of some configurations.

1. CloudStack + KVM

This combination is actually the cooperation between the CloudStack-Management Service and CloudStack-Agent on the two RHEL6U3 systems. Of course, libvirt is also an important component for the Agent. Assume that it is a management node and a proxy node. Generally, the following steps are taken to build a combination:

Management node:

(1) install the Operating System

(2) configure the YUM source and install the cloudstack-management and mysql-server components.

(3) initialize the mysql database file of cloudstack

(4) Mount Level 2 Storage and import the system VM Template

(5) use the cloudstack-setup-management command to start the cloustack management Service and configure firewall policies.

Proxy node:

(1) install the Operating System

(2) configure the YUM source and install the cloudstack-agent component.

(3) configure the configuration file libvirt,/etc/libvirt/libvirtd. conf, and/etc/sysconfig/libvirtd.

After the configuration is complete, log on to the cloudstack management node through the web interface.

Http: // cloudstack-management's ip: 8080/client

Admin/password Logon

Create a Zone. For more information, see other blogs.

2. CloudStack + VMWARE

This combination is generally the cooperation between CloudStack and VCenter. A RHEL6U3 system runs the CloudStack-Management service, and a VCenter configures all the host information.

The procedure is as follows:

Management Node

Apart from mounting level-2 storage, the imported system VM templates are different (the OVA template of VMWARE needs to be imported here, rather than the qcow2 template of KVM). All other steps are the same as those of CloudStack + KVM.

Proxy NodeRefers to the ESXI host, but does not need to install the CloudStack Agent component)

(1) install the ESXI Operating System

(2) install VCenter using the Windows Server 2008 R2 Operating System

(3) log on to VCenter, add a data center-cluster, and add an ESXI host.

After the configuration is complete, log on to the cloudstack management node through the web interface.

Http: // cloudstack-management's ip: 8080/client

Admin/password Logon

Create a region: Enter the actual data center and cluster information on the VCenter During the creation process. For detailed steps, refer to other blogs of the blogger.

The preceding steps are a combination of CloudStack and the two mainstream virtualization platforms. Now, we need to take note of the steps to clean up the environment and then reconstruct the environment.

1. manage nodes

(1) log on to the mysql server through the mysql client and delete the cloud, cloud_usage, and cloudbridge databases.

(2) reinitialize the above database through the command

If necessary), Mount level-2 storage, level-1 storage, delete all files, re-mount level-2 storage, and import the system VM template.

2. Proxy Node

(1) For KVM hosts, virsh pool-destroy's original storage pool level-1 storage and level-2 Storage)

(2) For VCenter, unmount the original attached storage level-1 storage and level-2 storage), you need to delete all host and template files in advance.

Then re-build the environment by following the above installation steps, there is basically no strange problem caused by the residual data in the old environment.

This article from the "dark magic king Teng cloud end" blog, please be sure to keep this source http://clovemfong.blog.51cto.com/3297559/1340857