Devstack Study and use summary

I've been in touch with the OpenStack concept since August 22, 2016 and started looking for tools to deploy OpenStack, which is now just 2 months away. In the meantime, I used the Mirantis company's fuel, preliminary study of the official version of OpenStack, but the most experience is spent on the devstack.

I personally understand that Devstack is an automated installation Deployment Tool software that runs OpenStack's basic modules using screen mode. It can install OpenStack integration on a single machine or virtual machine, use a local.conf configuration file before installation, run a fully automated advanced script in the installation, and use it for OpenStack debugging and small experiments after installation.

Then this blog also follow the installation, installation and after installation.

1. Before installation:

I tested Ubuntu 14.04 lts and 16.04 lts, two versions can be successfully installed Devstack, I was tested on bare metal. Before installing, you need git to devstack all kinds of files, refer to http://devstack.org. Git to the official website folder, you need to create and configure a file called local.conf, in this file, I have tested to specify the Host IP, specify which network to use, specify the floating IP range, and so on. The following configuration examples are available for testing:

+++++++++++++++++++++++

[[LOCAL|LOCALRC]]
Database_password=pass
Admin_password=pass
Service_password=pass
Service_token=pass
Rabbit_password=pass

host_ip=134.124.108.112
service_host=134.124.108.112
mysql_host=134.124.108.112
rabbit_host=134.124.108.112
glance_hostport=134.124.108.112:9292

Disable_service n-net
Enabled_services+=,q-svc,q-dhcp,q-meta,q-agt,q-13

# # Neutron Options
Q_use_secgroup=true
Floating_range= "134.124.108.0/24"
Fixed_range= "10.0.0.0/24"
q_floating_allocation_pool=start=134.124.108.120,end=134.124.108.130
Public_network_gateway= "134.124.108.1"
Public_interface=eno1

Q_use_providernet_for_public=true
Ovs_physical_bridge=br-ex
Public_bridge=br-ex
Ovs_bridge_mappings=public:br-ex

++++++++++++++++++++++++++

(Note: HostIP is the IP address of the installation of Devstack computer, FLOATINGIP is the same network segment with the host IP address, the purpose is for the external computer can communicate with OpenStack intranet VMS, Fixedrange is the IP address of the OpenStack intranet Publicbridge is the network card of the computer and the external network communication, because the Devstack will automatically configure the network card as the bridge mode, so this network card is used here)

2. In the installation:

Once configured, run stack.sh to begin the automatic installation process. It is worth mentioning that the installation process may be a variety of unexpected bugs, resulting in a stop, even if you completed 90, will be naught, and sometimes the reason is unknown. For example, the same configuration, the same computer, may today and tomorrow run the same command, will fail and succeed. Therefore, it is recommended to try the installation more. Run unstack.sh and restart your PC before each attempt to install. If you encounter a real failure, reinstall the operating system again.

3. After installation:

After successful installation, you can use the browser to open the OpenStack UI interface, complete various controls and functions on the UI, run the virtual machine, and so on.

It is important to note that the correct installation should have the same IP address as the computer's network card and the newly generated BR-EX network card. When I installed the computer's physical network card in the installation after the IP address is not, only Br-ex have IP, this situation is the result of a short period of time after installation, the computer and the external network will be broken, resulting in computers can not network, let alone OpenStack VMs. Analyze my reasons for failure, Perhaps because my host IP is 134.124.108.255, although the mask of the network is 255.255.254.0, so this is an available IP instead of a broadcast IP, but the Devstack installer may not think so, resulting in a failed configuration. So the normal IP should be OK.

If there is no problem with the generated network configuration, we can then control OpenStack, which can also be used in the UI or CLI (http://docs.openstack.org/cli-reference/common/cli-overview.html). Once the VM is created, the floating IP should theoretically be implemented to communicate with the extranet computer.

Note: After the installation of the computer can not restart, or you will lose the Network bridge configuration, resulting in network problems, unable to connect the extranet. I boil it down to Devstack's flaws.

Summary: Always feel that you might want to start deploying real OpenStack with three or four machines. The day will come, come on

Devstack Study and use summary