OpenStack Learning Notes-1

Cloud computing is currently a hot spot, in line with the idea of wage-oriented programming, began to learn cloud computing.

There should be a burst of cloud computing growth in the coming years.

Start with the OpenStack. a preface 8.1 now has three machines in his hand, a pad with a desk and a pen. Start thinking about using the three machines to do the experiment. But looking at the home page of the Install Guide configuration requirements and some of the steps can not understand. And then find another way out. On the home page, you have the started with OpenStack, which gives you two options to try OpenStack. The first is the public cloud on the market. The second is the local development environment devstack.org, and its introduction is: with some technical capabilities, Devstack is a great choice, and he can be installed in your notebook (even in the cloud on the virtual machine). Devstack is a good choice for potentially looking at dashboard from the perspective of an administrator or user. The same is true for contributors who want to test the full local environment. The above mentioned dashboard, literal translation for the Instrument plate table. In OpenStack is a system that provides the UI for each service. Typical components such as Horizon.
two Devstack Devstack is a series of extended scripts that bring a complete OpenStack runtime environment from Git master, often the basis for interactive development environments and OpenStack project functional testing. Source code in Https://git.openstack.org/cgit/openstack-dev/devstack.
2.1 Quick Start Installing Linux OpenStack supports Ubuntu 16.04/17.04, Fedora 24/25, Centos/rhel 7, Debian and openSUSE. If you don't like it, the official recommendation is Ubuntu 16.04. Both of my machines are loaded with CentOS 7. Add Stack user Devstack should not be run as the root user. You can add a user by using the following command:

$ sudo useradd-s/bin/bash-d/opt/stack-m stack

Because this user will make a lot of changes to your system, so he should have sudo privileges

$ echo "Stack all= (All) Nopasswd:all" | sudo tee/etc/sudoers.d/stack
$ sudo su-stack

Download Devstack

$ git clone https://git.openstack.org/openstack-dev/devstack
$ cd Devstack

The Devstack warehouse contains scripts for installing OpenStack and profile templates.
Create local.confCreate a local.conf file containing four passwords in the root directory of the Devstack warehouse.

[[LOCAL|LOCALRC]]
Admin_password=secret
database_password= $ADMIN _password
rabbit_password= $ADMIN _password
service_ password= $ADMIN _password

The creation method is a CD to the Devstack directory, and then the Create File command is used. I'm using Vim. This is the minimum requirement for configuring Devstack. Start Installation

./stack.sh

I'm having a problem.

[Error]413:unable to determine distro, can not continue.

Navigate to the source code, the note wrote this paragraph

 # We can ' t make a good choice.  Setting a sensible distro # is part of the problem, but not the major issue--we really # only use distro
        In the code as a fine-filter. # The bigger problem is categorising ' system into one's # our two big categories as Ubuntu/debian-is
        H or # fedora/centos-ish. # The setting of Os_package above is only set to ' Deb ' based # on a hard-coded list of vendor names ...  Thus we'll # default to thinking unknown Distros are RPM based # (ie. is_ubuntu does not match).
        But the platform would then # also not match in Is_fedora, because that also has a list of # names. # So, if you are are reading this, getting your distro supported # is really about making sure it matches  Correctly in these # functions.
        Then can choose a sensible way to construct # distro based on your distros release approach. DiE $LINENO "Unable to determine distro, can not continue." 

It means that you can't be sure of distro. But mine is CentOS ah, so the die line of comment out, write

distro= "Rhel${os_release::1}"

Continue running, error

/opt/stack/logs/error.log:no Such File

Without this file or directory, the solution he gave was to set the Force=yes option. The first thing I thought of was creating this file, and it was a shame that I couldn't create it, with Su. Later used it to the force=yes, the result is still, and think that since only the error log, or directly to the code comment out, or forget. Toss for a while, only to discover is to write Force=yes in the front. Then there is the long process of password-losing. Error

Devstack.subunit:no such file or directory