Fuel7.0 Installation

Source: Internet
Author: User

Chen Shak has analyzed several installation deployment tools for OpenStack deployment in his classic article.

Of course the times have changed, so many of these tools have been transformed.

At present,

1 Mirantis fuel is still the best commercially available option, though still flawed.

Fuel has provided open source plugin plugins, such as Contrail plugins, after 7 and 7. and put the fuel plugin solution into OpenStack development.

Fuel is already offering commercial plugin at 6.

Fuel current 8 There is a nasty place is need to network to fetch some content (is my network problem, the network to take Docker image for Slave), the version of centos7.0 compatibility is not good. (Is centos7.0 's problem, its liter kernel to 7.1 very large may hang)

Fuel defects are mainly some scenes will be inexplicable abnormal, some delete and increase the cloud will cause an exception, some hard disk size identification at the end of the installation to tell you that the capacity is insufficient. (mainly 6 of the problems, 8 because of network problems so far no sense)

2 RDO, which is the original Packstack

RDO is not a CD-ROM, is also a famous network installation, no network how to live?

The size of the RDO installation must be full OpenStack

RDO installed Ceilemeter, the second IP (if the DHCP application), reinstall, if you do not select Ceilemeter, the original ceil will not die automatically, there is blind to send messages to request communication.

3 other puppet classes, such as Chen said.

Rackspace, I didn't find the disc, and I didn't find the script. is Rackspace not playing OpenStack anymore?

4 Ansible and Kolla

Ansible more convenient, because there are always people hate puppet, in the next do not understand puppet, so also do not want to touch

Kolla is the upper-level development of the ansible language. Provides an OpenStack service-level granular, OpenStack installation deployment.

Kolla can support the re-deployment of Nova,keystone services to failed OpenStack.

Kolla is also based on Docker


fuel7.0 installation, and fuel5.0, 6 installation Similar, this time the younger brother is installed on the VirtualBox.

My little brother modified config.sh.

Major change points

1 master, 1compute, 1controller,

Multipoint resources to compute nodes.

However, after the installation success, surprised to find that fuel7 very smart to the size of the entire plate to the Compute,controller

The configuration of each node in memory is the same as config.sh.

Put on config.sh.


#!/bin/bash# Copyright Mirantis, inc.## Licensed under the Apache License, Version 2.0 (the "License"); You may# don't use this file except in compliance with the License. obtain# a copy of the License at## http://www.apache.org/licenses/LICENSE-2.0## unless required by a Pplicable law or agreed to in writing, software# distributed under the License are distributed on a "as is" BASIS, with out# warranties or CONDITIONS of any KIND, either express or implied. See the# License for the specific language governing permissions and limitations# under the License.source./functio ns/memory.sh# Get the first available ISO from the directory ' ISO ' iso_path= ' ls-1t iso/*.iso 2>/dev/null |  Head-1 ' # every mirantis OpenStack machine name would start from this prefixvm_name_prefix=fuel-# by default, all available Network Interfaces Vboxnet won ' is removed,# if their IP addresses don ' t match with Fuel_master_ips (10.20.0.1 172.16.0. 254# 172.16.1.1) # If yoU want to remove all existing vbox interfaces and then use rm_network=1# 0-don ' t remove all vbox networks. Remove Networks if they exist# 1-remove all vbox networksrm_network=0# Fuel Add the IPs accordingly if you G oing to create Non-default NICs number# 10.20.0.1/24-mirantis OpenStack Admin network# 172.16.0.1/24-openstack Publ Ic/external/floating network# 172.16.1.1/24-openstack fixed/internal/private network# 192.168.0.1/24-openstack Manag Ement network# 192.168.1.1/24-openstack Storage Network (for Ceph, Swift etc) fuel_master_ips= "10.20.0.1 172.16.0.254 172 .16.1.1 "# Network Mask for fuel interfacesmask=" 255.255.255.0 "# Determining the type of operating system and adding CPU Co Re to the master node case "$ (uname)" in Linux) os_type= "Linux" if ["$ (Nproc)"-GT "1"];    Then vm_master_cpu_cores=2 else Vm_master_cpu_cores=1 fi;; Darwin) os_type= "Darwin" Mac_nproc= ' sysctl-a | grep Machdep.cpu.thread_count |Sed ' s/^machdep.cpu.thread_count\:[\t]*//' if ["$mac _nproc"-GT "1"];    Then vm_master_cpu_cores=2 else Vm_master_cpu_cores=1 fi;; cygwin*) os_type= "CYGWIN" If ["$ (Nproc)"-GT "1"];    Then vm_master_cpu_cores=2 else Vm_master_cpu_cores=1 fi;;      *) echo "$ (uname) is not supported operating system."  Exit 1;;  esac# Master node settingsvm_master_memory_mb=1536vm_master_disk_mb=65535# master node access to the Internet through the Host system, using VirtualBox NAT adaptervm_master_nat_network=192.168.200.0/24vm_master_nat_gateway=192.168.200.2#  These settings'll be used to check if master node have installed or not.# if you modify networking params for master node During the boot time# (i.e. if you pressed Tab-a boot loader and modified params), # Make sure that these values re Flect that change.vm_master_ip=10.20.0.2vm_master_username=rootvm_master_password=r00tmevm_master_prompt= ' [email  Protected] ~]# ' # The number of nodes for installing OpenStack on#-for minimal non-ha installation, specify 2 (1 contro Ller + 1 Compute) #-for minimal non-ha with Cinder installation, specify 3 (1 CTRL + 1 COMPUTE + 1 Cinder) #-for Min iMAL HA Installation, specify 4 (3 controllers + 1 Compute) If ["$CONFIG _for" = "16GB"]; Then Cluster_size=5elif ["$CONFIG _for" = "8GB"]; Then Cluster_size=3else # sections for custom configuration cluster_size=2fi# Slave node settings. This section allows the CPU count for each slave node.# you can specify the CPU count for your nodes as you wish, BU  T keep in mind resources of your machine.# If you don't, then'll be used default Parameterif ["$CONFIG _for" = "16GB"]; Then vm_slave_cpu_default=1 vm_slave_cpu[1]=1 vm_slave_cpu[2]=1 vm_slave_cpu[3]=1 vm_slave_cpu[4]=1 vm_slave_cpu[5] =1elif ["$CONFIG _for" = "8GB"]; Then vm_slave_cpu_default=1 vm_slave_cpu[1]=1 vm_slave_cpu[2]=1 vm_slave_cpu[3]=1else # sections for custom COnfiguration vm_slave_cpu_default=1 vm_slave_cpu[1]=4 vm_slave_cpu[2]=1fi# This section allows your to define RAM size I n MB for each slave node.# Keep in mind the PXE boot might not work correctly with values lower than 768.# can Specif Y memory size for the specific slaves, and other would get default vm_slave_memory_default# mirantis OpenStack 3.2 Controllers Require, MiB of RAM as absolute minimum due to heat!#-all comment memory following-use D Efault value for each node.# It's recommended if you going to try HA configurations.# for controller node at least 1.5GB is required if also run Ceph and Heat on it# and for Ubuntu controllers we need 2Gb of ram# for compute node 1GB is rec ommended, otherwise VM instances in OpenStack if boot# for dedicated Cinder, 768Mb are OK, but Ceph needs 1Gb Minimumi f ["$CONFIG _for" = "16GB"]; Then vm_slave_memory_default=1536 vm_slave_memory_mb[1]=2048 vm_slave_memory_mb[2]=2048 vm_slave_memory_mb[3]=20vm_slave_memory_mb[4]=2048 vm_slave_memory_mb[5]=2048elif ["$CONFIG _for" = "8GB"]; Then vm_slave_memory_default=1024 vm_slave_memory_mb[1]=1536 vm_slave_memory_mb[2]=1536 vm_slave_memory_mb[3]= 1536else # section for custom configuration vm_slave_memory_default=1024 vm_slave_memory_mb[1]=12048 Vm_slave_memory_m b[2]=1024 vm_slave_memory_mb[3]=1024fi# within demo cluster created by this script, all slaves (controller# and Compute n Odes) would have identical disk configuration. each# slave'll has three disks with sizes defined by the variables below. In a disk configuration# dialog you'll be able to allocate the whole disk or it's part for# operating system (Base OS), VMs (Virtual Storage), Ceph or other function,# depending on the roles applied to the server.# Nodes with combined roles m ay require more disk space.vm_slave_first_disk_mb=85535vm_slave_second_disk_mb=35535vm_slave_third_disk_mb=65535# Set to 1 to run VirtualBox in headless modeheadless=0skipfuelmenu= "no"



Fuel7.0 Installation

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.