OpenStack搭建之Networking(五)
文章
林里克斯
在Linux
下搭建OpenStack
之Networking
一、实验平台:CentOS Linux release 7.3.1611 (Core)
二、openstack版本:Mitake
三、本机所有IP:内网:192.168.1.2 192.168.1.3
外网:192.168.2.4 192.168.2.5
四、openstack1:192.168.1.2 #控制节点 1 处理器, 4 GB 内存, 及20 GB 存储
五、openstack2:192.168.1.3 #计算节点 1 处理器, 2 GB 内存, 及20 GB 存储
![OpenStack搭建之Networking(五) OpenStack搭建之Networking(五)]()
一、网络服务概览
OpenStack Networking(neutron
,允许创建
、插入接口设备
,这些设备由其他的OpenStack
服务管理。插件式的实现可以容纳不同的网络设备和软件,为OpenStack
架构与部署提供了灵活性。
它包含下列组件:
neutron-server
接收和路由API请求到合适的OpenStack
网络插件,以达到预想的目的。
OpenStack
网络插件和代理 插拔端口,创建网络和子网,以及提供IP
地址,这些插件和代理依赖于供应商和技术而不同,OpenStack
网络基于插件和代理为Cisco 虚拟
和物理交换机
、NEC OpenFlow
产品,Open vSwitch
,Linux bridging
以及VMware NSX
产品穿线搭桥。
常见的代理L3(3层)
,DHCP(动态主机IP地址)
,以及插件代理
。
消息队列
大多数的OpenStack Networking
安装都会用到,用于在neutron-server
和各种各样的代理进程间路由信息。也为某些特定的插件扮演数据库的角色,以存储网络状态
OpenStack
网络主要和OpenStack
计算交互,以提供网络连接到它的实例。
二、安装并配置控制节点
在配置OpenStack网络(neutron)
服务之前,你必须为其创建一个数据库
,服务凭证
和API端点
。
创建neutron
数据库:
对neutron
数据库授予合适的访问权限
获得admin
凭证来获取只有管理员能执行的命令的访问权限:
要创建服务证书,完成这些步骤:
创建neutron
用户:
添加admin
角色到neutron
用户: openstack role add --project service --user neutron admin
创建neutron
服务实体:
创建网络服务API端点:
检查neutron
是否安装成功
网络选项:配置公共网络
安装组件
编辑/etc/neutron/neutron.conf
配置Modular Layer 2 (ML2)
插件
编辑/etc/neutron/plugins/ml2/ml2\_conf.ini
配置Linuxbridge
代理
编辑/etc/neutron/plugins/ml2/linuxbridge\_agent.ini
配置DHCP
代理
编辑/etc/neutron/dhcp\_agent.ini
配置元数据代理
编辑/etc/nova/nova.conf
为计算节点配置网络服务 编辑/etc/nova/nova.conf
网络服务初始化脚本需要一个超链接/etc/neutron/plugin.ini
指向ML2
插件配置文件/etc/neutron/plugins/ml2/ml2\_conf.ini
。如果超链接不存在,使用下面的命令创建它:
同步数据库:
$ su -s /bin/sh -c "neutron-db-manage --config-file /etc/neutron/neutron.conf \
> --config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head" neutron
No handlers could be found for logger "oslo_config.cfg"
INFO [alembic.runtime.migration] Context impl MySQLImpl.
INFO [alembic.runtime.migration] Will assume non-transactional DDL.
Running upgrade for neutron ...
INFO [alembic.runtime.migration] Context impl MySQLImpl.
INFO [alembic.runtime.migration] Will assume non-transactional DDL.
INFO [alembic.runtime.migration] Running upgrade -> kilo, kilo_initial
INFO [alembic.runtime.migration] Running upgrade kilo -> 354db87e3225, nsxv_vdr_metadata.py
INFO [alembic.runtime.migration] Running upgrade 354db87e3225 -> 599c6a226151, neutrodb_ipam
INFO [alembic.runtime.migration] Running upgrade 599c6a226151 -> 52c5312f6baf, Initial operations in support of address scopes
INFO [alembic.runtime.migration] Running upgrade 52c5312f6baf -> 313373c0ffee, Flavor framework
INFO [alembic.runtime.migration] Running upgrade 313373c0ffee -> 8675309a5c4f, network_rbac
INFO [alembic.runtime.migration] Running upgrade 8675309a5c4f -> 45f955889773, quota_usage
INFO [alembic.runtime.migration] Running upgrade 45f955889773 -> 26c371498592, subnetpool hash
INFO [alembic.runtime.migration] Running upgrade 26c371498592 -> 1c844d1677f7, add order to dnsnameservers
INFO [alembic.runtime.migration] Running upgrade 1c844d1677f7 -> 1b4c6e320f79, address scope support in subnetpool
INFO [alembic.runtime.migration] Running upgrade 1b4c6e320f79 -> 48153cb5f051, qos db changes
INFO [alembic.runtime.migration] Running upgrade 48153cb5f051 -> 9859ac9c136, quota_reservations
INFO [alembic.runtime.migration] Running upgrade 9859ac9c136 -> 34af2b5c5a59, Add dns_name to Port
INFO [alembic.runtime.migration] Running upgrade 34af2b5c5a59 -> 59cb5b6cf4d, Add availability zone
INFO [alembic.runtime.migration] Running upgrade 59cb5b6cf4d -> 13cfb89f881a, add is_default to subnetpool
INFO [alembic.runtime.migration] Running upgrade 13cfb89f881a -> 32e5974ada25, Add standard attribute table
INFO [alembic.runtime.migration] Running upgrade 32e5974ada25 -> ec7fcfbf72ee, Add network availability zone
INFO [alembic.runtime.migration] Running upgrade ec7fcfbf72ee -> dce3ec7a25c9, Add router availability zone
INFO [alembic.runtime.migration] Running upgrade dce3ec7a25c9 -> c3a73f615e4, Add ip_version to AddressScope
INFO [alembic.runtime.migration] Running upgrade c3a73f615e4 -> 659bf3d90664, Add tables and attributes to support external DNS integration
INFO [alembic.runtime.migration] Running upgrade 659bf3d90664 -> 1df244e556f5, add_unique_ha_router_agent_port_bindings
INFO [alembic.runtime.migration] Running upgrade 1df244e556f5 -> 19f26505c74f, Auto Allocated Topology - aka Get-Me-A-Network
INFO [alembic.runtime.migration] Running upgrade 19f26505c74f -> 15be73214821, add dynamic routing model data
INFO [alembic.runtime.migration] Running upgrade 15be73214821 -> b4caf27aae4, add_bgp_dragent_model_data
INFO [alembic.runtime.migration] Running upgrade b4caf27aae4 -> 15e43b934f81, rbac_qos_policy
INFO [alembic.runtime.migration] Running upgrade 15e43b934f81 -> 31ed664953e6, Add resource_versions row to agent table
INFO [alembic.runtime.migration] Running upgrade 31ed664953e6 -> 2f9e956e7532, tag support
INFO [alembic.runtime.migration] Running upgrade 2f9e956e7532 -> 3894bccad37f, add_timestamp_to_base_resources
INFO [alembic.runtime.migration] Running upgrade 3894bccad37f -> 0e66c5227a8a, Add desc to standard attr table
INFO [alembic.runtime.migration] Running upgrade kilo -> 30018084ec99, Initial no-op Liberty contract rule.
INFO [alembic.runtime.migration] Running upgrade 30018084ec99 -> 4ffceebfada, network_rbac
INFO [alembic.runtime.migration] Running upgrade 4ffceebfada -> 5498d17be016, Drop legacy OVS and LB plugin tables
INFO [alembic.runtime.migration] Running upgrade 5498d17be016 -> 2a16083502f3, Metaplugin removal
INFO [alembic.runtime.migration] Running upgrade 2a16083502f3 -> 2e5352a0ad4d, Add missing foreign keys
INFO [alembic.runtime.migration] Running upgrade 2e5352a0ad4d -> 11926bcfe72d, add geneve ml2 type driver
INFO [alembic.runtime.migration] Running upgrade 11926bcfe72d -> 4af11ca47297, Drop cisco monolithic tables
INFO [alembic.runtime.migration] Running upgrade 4af11ca47297 -> 1b294093239c, Drop embrane plugin table
INFO [alembic.runtime.migration] Running upgrade 1b294093239c -> 8a6d8bdae39, standardattributes migration
INFO [alembic.runtime.migration] Running upgrade 8a6d8bdae39 -> 2b4c2465d44b, DVR sheduling refactoring
INFO [alembic.runtime.migration] Running upgrade 2b4c2465d44b -> e3278ee65050, Drop NEC plugin tables
INFO [alembic.runtime.migration] Running upgrade e3278ee65050 -> c6c112992c9, rbac_qos_policy
INFO [alembic.runtime.migration] Running upgrade c6c112992c9 -> 5ffceebfada, network_rbac_external
INFO [alembic.runtime.migration] Running upgrade 5ffceebfada -> 4ffceebfcdc, standard_desc
OK
重启计算API
服务:
当系统启动时,启动 Networking 服务并配置它启动
三、安装和配置计算节点
安装包
编辑/etc/neutron/neutron.conf
配置Linuxbridge
代理
编辑/etc/neutron/plugins/ml2/linuxbridge\_agent.ini
为计算节点配置网络服务 编辑/etc/nova/nova.conf
重启计算服务:
启动Linuxbridge
代理并配置它开机自启动:
四、验证操作
获得admin
凭证来获取只有管理员能执行的命令的访问权限:
在控制节点上执行这些命令。
列出加载的扩展来验证neutron-server
进程是否正常启动:
Over ~
版权协议须知!
本篇文章来源于
Uambiguous
,如本文章侵犯到任何版权问题,请立即告知本站,本站将及时予与删除并致以最深的歉意
1487
0
2017-01-17

如果觉得我的文章对你有用,请随意赞赏