Quickly deploy OpenStack on the Ubuntu14.04

Address of this document (http://blog.sina.com.cn/s/blog_68d0c6c30102v8c4.html)
For beginners, OpenStack manual deployment is cumbersome and takes more time to learn. But we can use deployment scripts to install OpenStack.
Online there is a known as the most stupid OpenStack deployment tool called Devstack. I used to think it was quite a fool. The component is pulled straight down from GitHub, not only slow not to say, Even version compatibility may be problematic. It took 4 hours to install. It's more than just going back to changing the parameters. Even worse, it uses a Python setup script to add some potentially outdated packages directly to the system's Python library. Throws a lot of errors. Basically with Devstack installation failed to reinstall the system again.
Openshit is a gadget that can quickly deploy OpenStack on a Ubuntu14.04 system, using shell scripts and Python scripts to complete the installation and configuration of OpenStack components. And can easily change the configuration parameter reconfiguration, Restart the service to clear the database, and so on. Use commands to fully automate installation and configuration. The following is the address of Openshit
Openshit Command Introduction
./openshit.sh <--all|service_name> Start|stop|restart can start, stop, and restart the various (or all) OpenStack components.
./openshit.sh <--all|service_name> Install|uninstall|download can install, uninstall, and download packages for all OpenStack components
./openshit.sh <--all|service_name> Config can configure the build database, the original configuration file in the Config-backup folder by time back up, Easy rollback of profile changes using the rollback.sh script
./openshit.sh <--all|service_name> Clean can clear the database of the service, if the service problem can be directly clear the database and then re-config this address (http://blog.sina.com.cn/ s/blog_68d0c6c30102v8c4.html)

For beginners, OpenStack manual deployment is cumbersome and takes more time to learn. But we can use deployment scripts to install OpenStack.

Online there is a known as the most stupid OpenStack deployment tool called Devstack. I used to think it was quite a fool. The component is pulled straight down from GitHub, not only slow not to say, Even version compatibility may be problematic. It took 4 hours to install. It's more than just going back to changing the parameters. Even worse, it uses a Python setup script to add some potentially outdated packages directly to the system's Python library. Throws a lot of errors. Basically with Devstack installation failed to reinstall the system again.

Openshit is a gadget that can quickly deploy OpenStack on a Ubuntu14.04 system, using shell scripts and Python scripts to complete the installation and configuration of OpenStack components. And can easily change the configuration parameter reconfiguration, Restart the service to clear the database, and so on. Use commands to fully automate installation and configuration. The following is the address of Openshit

Openshit Command Introduction

./openshit.sh <--all|service_name> Start|stop|restart
The various (or all) OpenStack components can be started, stopped, and restarted.

./openshit.sh <--all|service_name> Install|uninstall|download
Can install, uninstall, and download package operations for all OpenStack components

./openshit.sh <--all|service_name> Config
You can configure the build database, the original configuration file in the Config-backup folder according to time back up, using the rollback.sh script can easily rollback the configuration file changes

./openshit.sh <--all|service_name> Clean
Can clear the service database, if the service problem can be directly clear the database and then re-config

Next we use Openshit to deploy OpenStack on Ubuntu14.04. Here are a few small requirements:
1. The Ubuntu14.04 partition must have enough space. OpenStack uses partitioned space when creating instances, and cannot create instances if there is not enough space. The test was Ubuntu14.04 100G, enough to use.
2. It is advisable to install the Ubuntu partition. If the god horse Devstack did not install the success of a pile of rubbish left in the system library and then use Openshit not successful that would be embarrassed.
Not much to say now start 1. Install Git and use git to download openshit git clone https://github.com/windworst/openshit.git.
2. Modify the configuration file setting.conf.       There are many passwords: The database password, the service password. The default can be changed, not changed, and nothing. Change the network configuration. The IP value within the profile is set to its own IP, and the NIC is set to its own network card (default is eth0).
3. After the configuration file modification is complete, start the installation./openshit.sh--all install. This command will ask you if you need to configure the source of the software, use Openshit for the first time, select Y, so the command can be written like this: Echo y |./openshit.sh--all Install
4. After a period of time the installation is complete, please enter./openshit.sh--all config modifies the configuration files and database configuration for each component based on the value of setting.conf.
5. Run the source admin-env.sh after completion; Nova service-list View service status if both are up installed successfully in the browser open Http://localhost/horizon can see the OpenStack management interface input password can login
OpenStack is now successfully deployed on the Ubuntu14.04 server.
To successfully run an instance, we need to create and upload a mirror, configure the network, and launch the instance. This makes an image of UBUNTU14 server 1. Make image qemu-img create-f qcow2 ubuntu.img 20G kvm-cdrom ubuntu-14.04-server-amd64.iso-drive file=ubuntu.img,if=vi Rtio,index=0-boot d-net nic-net User here is to install the Ubuntu14-server directly from the CD-ROM installation is OK
2. Upload image Execute source admin-env.sh in Openshit directory glance image-create--name "ubuntu"--file ubunut.img--disk-for Mat qcow2--container-format Bare--is-public True--progress progress bar quickly rolled over, upload complete
3. Create the network execute the source admin-env.sh in the Openshit directory (the previous execution is not performed here) perform Nova network-create v-net--bridge br100--m Ulti-host T--fixed-range-v4 10.0.1.0/29 Here v-net is the network name 10.0.1.0/29 is the net segment and the number of hosts to be allocated do not set the network segment to the same as this network segment, otherwise the egg hurts beyond your imagination to execute no VA net-list can see the network you just created
4. Create an instance in the Web management side of the image bar run to create an instance (will be assigned to the IP address of the network just created) Click on the console, you can see the virtual machine's screen through VNC there is a problem with the virtual machine and the host can ping each other (need to switch off the firewall), but not access Outside the network, where there may be no settings.
By the way, the instance has run, and the article is finished.