安装rackspace private cloud --4 配置Target hosts
在每个target host上执行以下操作:
- Naming target hosts.
- Install the operating system.
- Generate and set up security measures.
- Update the operating system and install additional software packages.
- Create LVM volume groups.
- Configure networking devices.
Deployment host到taget host无密码登陆:
Copy Deployment hos的public key到taget /root/.ssh/authorized_keys ssh-copy-id -i ~/.ssh/id_rsa.pub root@192.168.2.22
Configuring the operating system
kernel版本为3.13.0-34-generic or later
$ uname -a
Linux rpc- 3.13.--generic #-Ubuntu SMP Tue Mar :: UTC x86_64 x86_64 x86_64 GNU/Linux
# apt-get install bridge-utils debootstrap ifenslave ifenslave-2.6 \
lsof lvm2 ntp ntpdate openssh-server sudo tcpdump vlan
加入kernel 模块到/etc/modules来enable VLAN和接口bond
# echo 'bonding' >> /etc/modules
# echo '8021q' >> /etc/modules
Configure NTP
Reboot the host to activate the changes
Configuring LVM
Cinder节点上要一个cinder-volumes VG,metadata size必须是 2048
pvcreate --metadatasize /dev/vdb
vgcreate cinder-volumes /dev/vdb
Configuring the network
target hosts上的网络必须手动配置因为它们随环境不同而变化很大。
target hosts contains the following components:
可以配置bond:
Bond1 (eth0/2) static IP address 作为管理网络
Bond2 (eth1/3) without an IP address
Bond0 interface and br-mgmt bridge with a static IP address.
bond1 interface and br-vxlan bridge with a static IP address.
VLAN br-vlan bridge on the bond1 interface without an IP
the bond0 interface and br-storage bridge with a static IP address.
- VLANs:
- Host management: Untagged/Native
- Container management: 10
- Tunnels: 30
- Storage: 20
Networks:
- Host management: 10.240.0.0/22
- Container management: 172.29.236.0/22
- Tunnel: 172.29.240.0/22
- Storage: 172.29.244.0/22
Addresses:
- Host management: 10.240.0.11
- Host management gateway: 10.240.0.1
- DNS servers: 69.20.0.164 69.20.0.196
- Container management: 172.29.236.11
- Tunnel: 172.29.240.11
- Storage: 172.29.244.11
控制节点的网络图:

计算节点网络图:

存储节点网络图:

配置taget上的 /etc/network/interfaces文件如下:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(). # The loopback network interface
auto lo
iface lo inet loopback # Source interfaces
# Please check /etc/network/interfaces.d before changing this file
# as interfaces may have been defined in /etc/network/interfaces.d
# NOTE: the primary ethernet device is defined in
# /etc/network/interfaces.d/eth0
# See LP: #
source /etc/network/interfaces.d/*.cfg # Physical interface 1
auto eth1
iface eth1 inet manual
bond-master bond0
bond-primary eth1 # Physical interface 2
auto eth2
iface eth2 inet manual
bond-master bond1
bond-primary eth2 # Physical interface 3
auto eth3
iface eth3 inet manual
bond-master bond0 # Physical interface 4
auto eth4
iface eth4 inet manual
bond-master bond1 # Bond interface 0 (physical interfaces 1 and 3)
auto bond0
iface bond0 inet static
bond-slaves eth1 eth3
bond-mode active-backup
bond-miimon 100
bond-downdelay 200
bond-updelay 200
address 192.168.2.112
netmask 255.255.255.0
gateway 192.168.2.1
dns-nameservers 69.20.0.164 69.20.0.196 # Bond interface 1 (physical interfaces 2 and 4)
auto bond1
iface bond1 inet manual
bond-slaves eth2 eth4
bond-mode active-backup
bond-miimon 100
bond-downdelay 250
bond-updelay 250 # Container management VLAN interface
iface bond0.10 inet manual
vlan-raw-device bond0 # OpenStack Networking VXLAN (tunnel/overlay) VLAN interface
iface bond1.30 inet manual
vlan-raw-device bond1 # Storage network VLAN interface (optional)
iface bond0.20 inet manual
vlan-raw-device bond0 # Container management bridge
auto br-mgmt
iface br-mgmt inet static
bridge_stp off
bridge_waitport 0
bridge_fd 0
# Bridge port references tagged interface
bridge_ports bond0.10
address 172.29.236.11
netmask 255.255.252.0
dns-nameservers 69.20.0.164 69.20.0.196 # OpenStack Networking VXLAN (tunnel/overlay) bridge
auto br-vxlan
iface br-vxlan inet static
bridge_stp off
bridge_waitport 0
bridge_fd 0
# Bridge port references tagged interface
bridge_ports bond1.30
address 172.29.240.11
netmask 255.255.252.0 # OpenStack Networking VLAN bridge
auto br-vlan
iface br-vlan inet manual
bridge_stp off
bridge_waitport 0
bridge_fd 0
# Bridge port references untagged interface
bridge_ports bond1 # Storage bridge (optional)
auto br-storage
iface br-storage inet static
bridge_stp off
bridge_waitport 0
bridge_fd 0
# Bridge port reference tagged interface
bridge_ports bond0.20
address 172.29.244.11
netmask 255.255.252.0
注意:bond0的IP每个taget都应该不同
service networking restart
之后验证网络配置:
ubuntu@rpc-3:~$ ifconfig -a
bond0 Link encap:Ethernet HWaddr fa::3e::7b:0a
inet addr:192.168.2.112 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::f816:3eff:fe59:7b0a/ Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU: Metric:
RX packets: errors: dropped: overruns: frame:
TX packets: errors: dropped: overruns: carrier:
collisions: txqueuelen:
RX bytes: (89.5 KB) TX bytes: (4.3 KB)
bond1 Link encap:Ethernet HWaddr fa::3e::2d:1a
inet6 addr: fe80::f816:3eff:fe51:2d1a/ Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU: Metric:
RX packets: errors: dropped: overruns: frame:
TX packets: errors: dropped: overruns: carrier:
collisions: txqueuelen:
RX bytes: (89.6 KB) TX bytes: (3.3 KB)
bond0. Link encap:Ethernet HWaddr fa::3e::7b:0a
inet6 addr: fe80::f816:3eff:fe59:7b0a/ Scope:Link
UP BROADCAST RUNNING MULTICAST MTU: Metric:
RX packets: errors: dropped: overruns: frame:
TX packets: errors: dropped: overruns: carrier:
collisions: txqueuelen:
RX bytes: (0.0 B) TX bytes: (1.3 KB)
bond0. Link encap:Ethernet HWaddr fa::3e::7b:0a
inet6 addr: fe80::f816:3eff:fe59:7b0a/ Scope:Link
UP BROADCAST RUNNING MULTICAST MTU: Metric:
RX packets: errors: dropped: overruns: frame:
TX packets: errors: dropped: overruns: carrier:
collisions: txqueuelen:
RX bytes: (0.0 B) TX bytes: (1.3 KB)
bond1. Link encap:Ethernet HWaddr fa::3e::2d:1a
inet6 addr: fe80::f816:3eff:fe51:2d1a/ Scope:Link
UP BROADCAST RUNNING MULTICAST MTU: Metric:
RX packets: errors: dropped: overruns: frame:
TX packets: errors: dropped: overruns: carrier:
collisions: txqueuelen:
RX bytes: (0.0 B) TX bytes: (1.2 KB)
br-mgmt Link encap:Ethernet HWaddr fa::3e::7b:0a
inet addr:172.29.236.11 Bcast:172.29.239.255 Mask:255.255.252.0
inet6 addr: fe80::f816:3eff:fe59:7b0a/ Scope:Link
UP BROADCAST RUNNING MULTICAST MTU: Metric:
RX packets: errors: dropped: overruns: frame:
TX packets: errors: dropped: overruns: carrier:
collisions: txqueuelen:
RX bytes: (0.0 B) TX bytes: (648.0 B)
br-storage Link encap:Ethernet HWaddr fa::3e::7b:0a
inet addr:172.29.244.11 Bcast:172.29.247.255 Mask:255.255.252.0
inet6 addr: fe80::f816:3eff:fe59:7b0a/ Scope:Link
UP BROADCAST RUNNING MULTICAST MTU: Metric:
RX packets: errors: dropped: overruns: frame:
TX packets: errors: dropped: overruns: carrier:
collisions: txqueuelen:
RX bytes: (0.0 B) TX bytes: (648.0 B)
br-vlan Link encap:Ethernet HWaddr fa::3e::2d:1a
inet6 addr: fe80::f816:3eff:fe51:2d1a/ Scope:Link
UP BROADCAST RUNNING MULTICAST MTU: Metric:
RX packets: errors: dropped: overruns: frame:
TX packets: errors: dropped: overruns: carrier:
collisions: txqueuelen:
RX bytes: (12.4 KB) TX bytes: (180.0 B)
br-vxlan Link encap:Ethernet HWaddr fa::3e::2d:1a
inet addr:172.29.240.11 Bcast:172.29.243.255 Mask:255.255.252.0
inet6 addr: fe80::f816:3eff:fe51:2d1a/ Scope:Link
UP BROADCAST RUNNING MULTICAST MTU: Metric:
RX packets: errors: dropped: overruns: frame:
TX packets: errors: dropped: overruns: carrier:
collisions: txqueuelen:
RX bytes: (0.0 B) TX bytes: (648.0 B)
eth0 Link encap:Ethernet HWaddr fa::3e:1b:3f:
inet addr:192.168.2.22 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::f816:3eff:fe1b:3f54/ Scope:Link
UP BROADCAST RUNNING MULTICAST MTU: Metric:
RX packets: errors: dropped: overruns: frame:
TX packets: errors: dropped: overruns: carrier:
collisions: txqueuelen:
RX bytes: (68.3 KB) TX bytes: (104.3 KB)
eth1 Link encap:Ethernet HWaddr fa::3e::7b:0a
inet6 addr: fe80::f816:3eff:fe59:7b0a/ Scope:Link
UP BROADCAST RUNNING SLAVE MULTICAST MTU: Metric:
RX packets: errors: dropped: overruns: frame:
TX packets: errors: dropped: overruns: carrier:
collisions: txqueuelen:
RX bytes: (44.7 KB) TX bytes: (3.5 KB)
eth2 Link encap:Ethernet HWaddr fa::3e::2d:1a
inet6 addr: fe80::f816:3eff:fe51:2d1a/ Scope:Link
UP BROADCAST RUNNING SLAVE MULTICAST MTU: Metric:
RX packets: errors: dropped: overruns: frame:
TX packets: errors: dropped: overruns: carrier:
collisions: txqueuelen:
RX bytes: (44.7 KB) TX bytes: (2.7 KB)
eth3 Link encap:Ethernet HWaddr fa::3e::7b:0a
inet6 addr: fe80::f816:3eff:fe59:7b0a/ Scope:Link
UP BROADCAST RUNNING SLAVE MULTICAST MTU: Metric:
RX packets: errors: dropped: overruns: frame:
TX packets: errors: dropped: overruns: carrier:
collisions: txqueuelen:
RX bytes: (44.8 KB) TX bytes: (856.0 B)
eth4 Link encap:Ethernet HWaddr fa::3e::2d:1a
inet6 addr: fe80::f816:3eff:fe51:2d1a/ Scope:Link
UP BROADCAST RUNNING SLAVE MULTICAST MTU: Metric:
RX packets: errors: dropped: overruns: frame:
TX packets: errors: dropped: overruns: carrier:
collisions: txqueuelen:
RX bytes: (44.8 KB) TX bytes: (578.0 B)
安装rackspace private cloud --4 配置Target hosts的更多相关文章
- 在openstack环境中安装rackspace private cloud --1 环境准备
在一个openstack环境中安装rackspace private cloud, 环境准备: 在good-net网络中创建3个虚拟机vm Network Detail: good-net Netwo ...
- 中安装rackspace private cloud --6 Deployment rpc
运行ansible playbook安装之前的准备工作: Perform deployment host initial setup Build containers on target hosts ...
- 安装rackspace private cloud --5 Deployment configuration
运行Ansible playbooks之前,需要配置taget host Prerequisites . cp -r /opt/openstack-ansible/etc/openstack_depl ...
- 安装rackspace private cloud --2 overview
Target hosts 包含以下 network bridges: LXC internal lxcbr0: 必须的,自动生成,containers的外网连接,不连接到host上任何物理/逻辑接口, ...
- 安装rackspace private cloud --3 Deployment host
on deploy host: 在deploy host上安装 Ubuntu Server 14.04 (Trusty Tahr) LTS 64-bit # apt-get install aptit ...
- 虚拟私有云(Virtual Private Cloud,专有网络)配置方式总结
虚拟私有云 虚拟私有云(Virtual Private Cloud)是用户在云上申请的隔离的.私密的虚拟网络环境.用户可以自由配置VPC内的IP地址段.子网.安全组等子服务,也可以申请弹性带宽和弹性公 ...
- CentOS7下安装Nexus私服及基础配置
环境准备 VMware上安装CentOS7 XShell/Xftp NexusOSS-3.10 jdk1.8 安装 使用root用户登录,将安装包均放置在/usr/local文件夹下 使用Xshell ...
- Windows Azure Cloud Service (36) 在Azure Cloud Service配置SSL证书
<Windows Azure Platform 系列文章目录> 在某些时候,我们需要在Azure PaaS Cloud Service配置HTTPS连接.本章将介绍如何在本地创建证书,然后 ...
- 使用VMware安装linux虚拟机以及相关配置
前言 使用VMware安装虚拟机这个一般都知道,操作简单.而本文主要讲使用虚拟机的后续相关配置.并记录使用过程中遇到的问题以及一些技巧.本篇文章以后回持续更新的... 安装包准备 VM:12 Linu ...
随机推荐
- 【转】再谈CLR查找和加载程序集的方式
这是一个老问题,以前也有朋友写过一些文章介绍,但可能还不是很全面.我也多次被人问到,这里结合案例再次谈谈,希望对大家有所帮助. 本文范例代码可以通过这里下载 http://files.cnblogs. ...
- maven仓库添加本地jar
一.将jar添加到本地仓库的做法: 以下面pom.xml依赖的jar包为例: 实际项目中pom.xml依赖写法: <dependency> <groupId>org.sprin ...
- Centos7安装dubbo管理控制台
1.下载dubbo源代码 wget https://github.com/apache/incubator-dubbo/archive/2.5.x.zip 2.进入dubbo-admin目录下 cd ...
- linux下tcpdump命令的使用
一般情况下linux系统会自带tcpdump工具,如果系统没有安装,直接用命令安装就行了. 安装命令:yum install -y tcpdump 查看安装版本命令:tcpdump --help 查看 ...
- 如何修改本地hosts文件?
1.window7修改本地hosts文件 # window7系统hosts文件位置 C:\Windows\System32\drivers\etc 2.linux # linux系统hosts文件位置 ...
- 笔记:zookeeper Hello World
下载zookeeper-3.4.6 , 试用了一下 standlone 启动 ./bin/zkServer.sh start 注: Usage: ./bin/zkServer.sh {start|st ...
- Linux vim编写程序时出现高亮字符,如何取消?
在“命令模式”下输入“:nohl“,再按回车,便可以取消高亮显示.
- app开发制作会难吗?app开发好学吗?
前面我们讲到了app是什么,APP是运行在智能手机的第三方应用程序,可以满足用户的不同需求.那么app开发制作会难吗?这个与产品的复杂度有很大的关系,复杂度包括业务逻辑多不多,业务模块多不多等,对于玩 ...
- "深入理解C语言" 指针
本文对coolshell中的"深入理解C语言"这篇文章中提到的指针问题, 进行简要的分析. #include <stdio.h> int main(void){ ]; ...
- Personal Ubuntu
@1:修改了打开主文件夹的快捷键 CTRL + ALT + R @2:增加了强制关闭程序的快捷键CTRL + ALT+ X,程序为~/lxw0109/ownAdmin/closeProgram.sh( ...