美文网首页
实战OpenStack之控制节点(三)

实战OpenStack之控制节点(三)

作者: mark_meng | 来源:发表于2017-03-30 10:59 被阅读0次

    3.7 Nova compute计算节点的部署

    •图解Nova cpmpute

    src="http://cdn.oldboyedu.com/wp-content/uploads/2016/02/wpid-631325ba70ea05d245906c576f3ef421_openstack-architecture-49-638.jpg"

    alt="" title="">
    nova-compute一般运行在计算节点上,通过Message Queue接收并管理VM的生命周期

    •nova-compute通过Libvirt管理KVN,通过XenAPI管理Xen等

    •配置时间同步

    •修改其配置文件

    1[root@linux-node1 ~]# vim/etc/chrony.conf

    2server 192.168.56.11 iburst(只保留这一个server,也就是控制节点的时间)

    chrony开机自启动,并且启动

    1[root@linux-node1 ~]#systemctl enablechronyd.service

    2[root@linux-node1 ~]#systemctlstartchronyd.service

    设置Centos7的时区

    1[root@linux-node1 ~]# timedatectlset-timezone

    2``` Asia/Shanghai

    3查看时区和时间

    4```bash

    5[root@linux-node ~]# timedatectlstatus

    6Local time: Fri 2015-12-18 00:12:26 CST

    7Universal time: Thu 2015-12-17 16:12:26 UTC

    8RTC time: Sun 2015-12-13 15:32:36

    9Timezone: Asia/Shanghai (CST, +0800)

    10NTP enabled: yes

    11NTP synchronized: no

    12RTC in local TZ: no

    13DST active: n/a

    14[root@linux-node1 ~]# date

    15Fri Dec 18 00:12:43 CST 2015

    •开始部署计算节点

    •更改计算节点上的配置文件,直接使用控制节点的配置文件

    1[root@linux-node1 ~]# scp

    /etc/nova/nova.conf 192.168.56.12:/etc/nova/ (在控制节点上操作的scp)

    更改配置文件后的过滤结果

    1[root@linux-node ~]# grep -n '^[a-Z]'/etc/nova/nova.conf

    261:rpc_backend=rabbit

    3124:my_ip=192.168.56.12改成本机ip

    4268:enabled_apis=osapi_compute,metadata

    5425:auth_strategy=keystone

    61053:network_api_class=nova.network.neutronv2.api.API

    71171:linuxnet_interface_driver=nova.network.linux_net.NeutronLinuxBridgeInterfaceDriver

    81331:security_group_api=neutron

    91370:debug=true

    101374:verbose=True

    111760:firewall_driver =nova.virt.firewall.NoopFirewallDriver

    121820:novncproxy_base_url=http://192.168.56.11:6080/vnc_auto.html指定novncproxy的IP地址和端口

    131828:vncserver_listen=0.0.0.0 vnc监听0.0.0.0

    141832:vncserver_proxyclient_address=$my_ip

    151835:vnc_enabled=true启用vnc

    161838:vnc_keymap=en-us英语键盘

    172213:connection=mysql://nova:nova@192.168.56.11/nova

    182334:host=192.168.56.11

    192546:auth_uri =http://192.168.56.11:5000

    202547:auth_url =http://192.168.56.11:35357

    212548:auth_plugin = password

    222549:project_domain_id = default

    232550:user_domain_id = default

    242551:project_name = service

    252552:username = nova

    262553:password = nova

    272727:virt_type=kvm使用kvm虚拟机,需要cpu支持,可通过grep

    "vmx" /proc/cpuinfo查看

    283807:lock_path=/var/lib/nova/tmp

    293970:rabbit_host=192.168.56.11

    303974:rabbit_port=5672

    313986:rabbit_userid=openstack

    323990:rabbit_password=openstack

    启动计算节点的libvirt和nova-compute

    1[root@linux-node ~]# systemctl enablelibvirtd openstack-nova-compute

    2ln -s'/usr/lib/systemd/system/openstack-nova-compute.service''/etc/systemd/system/multi-user.target.wants/openstack-nova-compute.service'

    3[root@linux-node ~]# systemctl startlibvirtd openstack-nova-compute

    •在控制节点中查看注册的host,最后一个compute即是注册的host

    1[root@linux-node1 ~]# openstack hostlist

    2+---------------------------+-------------+----------+

    3| Host Name| Service| Zone|

    4+---------------------------+-------------+----------+

    5| linux-node1.oldboyedu.com |conductor| internal |

    6| linux-node1.oldboyedu.com |consoleauth | internal |

    7| linux-node1.oldboyedu.com |cert| internal |

    8| linux-node1.oldboyedu.com |scheduler| internal |

    9| linux-node.oldboyedu.com| compute| nova|

    10+---------------------------+-------------+----------+

    在控制节点中测试nova和glance连接正常,nova链接keystone是否正常

    1[root@linux-node1 ~]# nova image-list

    2+--------------------------------------+--------+--------+--------+

    3| ID| Name| Status | Server |

    4+--------------------------------------+--------+--------+--------+

    5| 4b36361f-1946-4026-b0cb-0f7073d48ade| cirros | ACTIVE ||

    6+--------------------------------------+--------+--------+--------+

    7[root@linux-node1 ~]# nova endpoints

    8WARNING: keystone has no endpoint in !Available endpoints for this service:

    9+-----------+----------------------------------+

    10| keystone| Value|

    11+-----------+----------------------------------+

    12| id| 1143dcd58b6848a1890c3f2b9bf101d5 |

    13| interface | public|

    14| region| RegionOne|

    15| region_id | RegionOne|

    16| url| http://192.168.56.11:5000/v2.0|

    17+-----------+----------------------------------+

    18+-----------+----------------------------------+

    19| keystone| Value|

    20+-----------+----------------------------------+

    21| id| 28283cbf90b5434ba7a8780fac9308df |

    22| interface | admin|

    23| region| RegionOne|

    24| region_id | RegionOne|

    25| url| http://192.168.56.11:35357/v2.0|

    26+-----------+----------------------------------+

    27+-----------+----------------------------------+

    28| keystone| Value|

    29+-----------+----------------------------------+

    30| id| 496f648007a04e5fbe99b62ed8a76acd |

    31| interface | internal|

    32| region| RegionOne|

    33| region_id | RegionOne|

    34| url| http://192.168.56.11:5000/v2.0|

    35+-----------+----------------------------------+

    36WARNING: nova has no endpoint in !Available endpoints for this service:

    37+-----------+---------------------------------------------------------------+

    38| nova| Value|

    39+-----------+---------------------------------------------------------------+

    40| id| 1d67f3630a0f413e9d6ff53bcc657fb6|

    41| interface | internal|

    42| region| RegionOne|

    43| region_id | RegionOne|

    44| url|http://192.168.56.11:8774/v2/45ec9f72892c404897d0f7d6668d7a53 |

    45+-----------+---------------------------------------------------------------+

    46+-----------+---------------------------------------------------------------+

    47| nova| Value|

    48+-----------+---------------------------------------------------------------+

    49| id| 23e9132aeb3a4dcb8689aa1933ad7301|

    50| interface | public|

    51| region| RegionOne|

    52| region_id | RegionOne|

    53| url|http://192.168.56.11:8774/v2/45ec9f72892c404897d0f7d6668d7a53 |

    54+-----------+---------------------------------------------------------------+

    55+-----------+---------------------------------------------------------------+

    56| nova| Value|

    57+-----------+---------------------------------------------------------------+

    58| id| b7f7c210becc4e54b76bb454966582e4|

    59| interface | admin|

    60| region| RegionOne|

    61| region_id | RegionOne|

    62| url|http://192.168.56.11:8774/v2/45ec9f72892c404897d0f7d6668d7a53 |

    63+-----------+---------------------------------------------------------------+

    64WARNING: glance has no endpoint in !Available endpoints for this service:

    65+-----------+----------------------------------+

    66| glance| Value|

    67+-----------+----------------------------------+

    68| id| 2b55d6db62eb47e9b8993d23e36111e0 |

    69| interface | admin|

    70| region| RegionOne|

    71| region_id | RegionOne|

    72| url| http://192.168.56.11:9292|

    73+-----------+----------------------------------+

    74+-----------+----------------------------------+

    75| glance| Value|

    76+-----------+----------------------------------+

    77| id| 56cf6132fef14bfaa01c380338f485a6 |

    78| interface | public|

    79| region| RegionOne|

    80| region_id | RegionOne|

    81| url| http://192.168.56.11:9292|

    82+-----------+----------------------------------+

    83+-----------+----------------------------------+

    84| glance| Value|

    85+-----------+----------------------------------+

    86| id| 8005e8fcd85f4ea281eb9591c294e760 |

    87| interface | internal|

    88| region| RegionOne|

    89| region_id | RegionOne|

    90| url| http://192.168.56.11:9292|

    91+-----------+----------------------------------+

    3.8 Neturn服务部署

    注册neutron服务

    1[root@linux-node1 ~]# sourceadmin-openrc.sh

    2[root@linux-node1 ~]# openstack servicecreate --name neutron --description "OpenStack Networking" network

    3+-------------+----------------------------------+

    4| Field| Value|

    5+-------------+----------------------------------+

    6| description | OpenStack Networking|

    7| enabled| True|

    8| id| e698fc8506634b05b250e9fdd8205565 |

    9| name| neutron|

    10| type| network|

    11+-------------+----------------------------------+

    12[root@linux-node1 ~]# openstackendpoint create --region RegionOne network public http://192.168.56.11:9696

    13+--------------+----------------------------------+

    14| Field| Value|

    15+--------------+----------------------------------+

    16| enabled| True|

    17| id| 3cf4a13ec1b94e66a47e27bfccd95318 |

    18| interface| public|

    19| region| RegionOne|

    20| region_id| RegionOne|

    21| service_id| e698fc8506634b05b250e9fdd8205565 |

    22| service_name | neutron|

    23| service_type | network|

    24| url| http://192.168.56.11:9696|

    25+--------------+----------------------------------+

    26[root@linux-node1 ~]# openstackendpoint create --region RegionOne network internal http://192.168.56.11:9696

    27+--------------+----------------------------------+

    28| Field| Value|

    29+--------------+----------------------------------+

    30| enabled| True|

    31| id| 5cd1e54d14f046dda2f7bf45b418f54c |

    32| interface| internal|

    33| region| RegionOne|

    34| region_id| RegionOne|

    35| service_id| e698fc8506634b05b250e9fdd8205565 |

    36| service_name | neutron|

    37| service_type | network|

    38| url| http://192.168.56.11:9696|

    39+--------------+----------------------------------+

    40[root@linux-node1 ~]# openstackendpoint create --region RegionOne network admin http://192.168.56.11:9696

    41+--------------+----------------------------------+

    42| Field| Value|

    43+--------------+----------------------------------+

    44| enabled| True|

    45| id| 2c68cb45730d470691e6a3f0656eff03 |

    46| interface| admin|

    47| region|RegionOne|

    48| region_id| RegionOne|

    49| service_id| e698fc8506634b05b250e9fdd8205565 |

    50| service_name | neutron|

    51| service_type | network|

    52| url| http://192.168.56.11:9696|

    53+--------------+----------------------------------+

    54创建neutron用户,并添加大service项目,给予admin权限

    55[root@linux-node1 config]# openstackuser create --domain default --password=neutron neutron

    56+-----------+----------------------------------+

    57| Field| Value|

    58+-----------+----------------------------------+

    59| domain_id | default|

    60| enabled| True|

    61| id| 5143854f317541d68efb8bba8b2539fc |

    62| name| neutron|

    63+-----------+----------------------------------+

    64[root@linux-node1 config]# openstackrole add --project service --user neutron admin

    修改neturn配置文件

    1[root@linux-node1 ~]# grep -n"^[a-Z]" /etc/neutron/neutron.conf

    220:state_path = /var/lib/neutron

    360:core_plugin = ml2核心插件为ml2

    477:service_plugins = router服务插件为router

    592:auth_strategy = keystone

    6360:notify_nova_on_port_status_changes= True

    7端口改变需通知nova

    8364:notify_nova_on_port_data_changes =True

    9367:nova_url =http://192.168.56.11:8774/v2

    10573:rpc_backend=rabbit

    11717:auth_uri =http://192.168.56.11:5000

    12718:auth_url =http://192.168.56.11:35357

    13719:auth_plugin = password

    14720:project_domain_id = default

    15721:user_domain_id = default

    16722:project_name = service

    17723:username = neutron

    18724:password = neutron

    19737:connection =mysql://neutron:neutron@192.168.56.11:3306/neutron

    20780:auth_url =http://192.168.56.11:35357

    21781:auth_plugin = password

    22782:project_domain_id = default

    23783:user_domain_id = default

    24784:region_name = RegionOne

    25785:project_name = service

    26786:username = nova

    27787:password = nova

    28818:lock_path = $state_path/lock

    29998:rabbit_host = 192.168.56.11

    301002:rabbit_port = 5672

    311014:rabbit_userid = openstack

    321018:rabbit_password = openstack

    修改ml2的配置文件,ml2后续会有详细说明

    1[root@linux-node1 ~]# grep"^[a-Z]" /etc/neutron/plugins/ml2/ml2_conf.ini

    2type_drivers =

    flat,vlan,gre,vxlan,geneve各种驱动

    3tenant_network_types =

    vlan,gre,vxlan,geneve网络类型

    4mechanism_drivers = openvswitch,linuxbridge支持的底层驱动

    5extension_drivers = port_security端口安全

    6flat_networks = physnet1使用单一扁平网络(和host一个网络)

    7enable_ipset = True

    修改的linuxbridge配置文件、

    1[root@linux-node1 ~]# grep -n"^[a-Z]" /etc/neutron/plugins/ml2/linuxbridge_agent.ini

    29:physical_interface_mappings =

    physnet1:eth0网卡映射eth

    316:enable_vxlan = false关闭vxlan

    451:prevent_arp_spoofing = True

    557:firewall_driver =neutron.agent.linux.iptables_firewall.IptablesFirewallDriver

    661:enable_security_group = True

    修改dhcp的配置文件

    1[root@linux-node1 ~]# grep -n"^[a-Z]" /etc/neutron/dhcp_agent.ini

    227:interface_driver =neutron.agent.linux.interface.BridgeInterfaceDriver

    331:dhcp_driver =

    neutron.agent.linux.dhcp.Dnsmasq使用Dnsmasq作为dhcp服务

    452:enable_isolated_metadata = true

    修改metadata_agent.ini配置文件

    1[root@linux-node1 config]# grep -n"^[a-Z]" /etc/neutron/metadata_agent.ini

    24:auth_uri = http://192.168.56.11:5000

    35:auth_url =http://192.168.56.11:35357

    46:auth_region = RegionOne

    57:auth_plugin = password

    68:project_domain_id = default

    79:user_domain_id = default

    810:project_name = service

    911:username = neutron

    1012:password = neutron

    1129:nova_metadata_ip = 192.168.56.11

    1252:metadata_proxy_shared_secret =neutron

    在控制节点的nova中添加关于neutron的配置,`添加如下内容到neutron模块即可

    13033:url = http://192.168.56.11:9696

    23034:auth_url =http://192.168.56.11:35357

    33035:auth_plugin = password

    43036:project_domain_id = default

    53037:user_domain_id = default

    63038:region_name = RegionOne

    73039:project_name = service

    83040:username = neutron

    93041:password = neutron

    103043:service_metadata_proxy = True

    113044:metadata_proxy_shared_secret =neutron

    12````

    13创建ml2的软连接

    14```bash

    15[root@linux-node1 config]# ln -s/etc/neutron/plugins/ml2/ml2_conf.ini /etc/neutron/plugin.ini

    同步neutron数据库,并检查结果

    1[root@linux-node1 config]# 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

    2MariaDB [(none)]> use neutron;

    3Database changed

    4MariaDB [neutron]> show tables;

    5+-----------------------------------------+

    6| Tables_in_neutron|

    7+-----------------------------------------+

    8| address_scopes|

    9| agents|

    10| alembic_version|

    11| allowedaddresspairs|

    12| arista_provisioned_nets|

    13| arista_provisioned_tenants|

    14| arista_provisioned_vms|

    15| brocadenetworks|

    16| brocadeports|

    17| cisco_csr_identifier_map|

    18| cisco_hosting_devices|

    19| cisco_ml2_apic_contracts|

    20| cisco_ml2_apic_host_links|

    21| cisco_ml2_apic_names|

    22| cisco_ml2_n1kv_network_bindings|

    23| cisco_ml2_n1kv_network_profiles|

    24| cisco_ml2_n1kv_policy_profiles|

    25| cisco_ml2_n1kv_port_bindings|

    26| cisco_ml2_n1kv_profile_bindings|

    27| cisco_ml2_n1kv_vlan_allocations|

    28|cisco_ml2_n1kv_vxlan_allocations|

    29| cisco_ml2_nexus_nve|

    30| cisco_ml2_nexusport_bindings|

    31| cisco_port_mappings|

    32| cisco_router_mappings|

    33| consistencyhashes|

    34| csnat_l3_agent_bindings|

    35| default_security_group|

    36| dnsnameservers|

    37| dvr_host_macs|

    38| embrane_pool_port|

    39| externalnetworks|

    40| extradhcpopts|

    41| firewall_policies|

    42| firewall_rules|

    43| firewalls|

    44| flavors|

    45| flavorserviceprofilebindings|

    46| floatingips|

    47| ha_router_agent_port_bindings|

    48| ha_router_networks|

    49| ha_router_vrid_allocations|

    50| healthmonitors|

    51| ikepolicies|

    52| ipallocationpools|

    53| ipallocations|

    54| ipamallocationpools|

    55| ipamallocations|

    56| ipamavailabilityranges|

    57| ipamsubnets|

    58| ipavailabilityranges|

    59| ipsec_site_connections|

    60| ipsecpeercidrs|

    61| ipsecpolicies|

    62| lsn|

    63| lsn_port|

    64| maclearningstates|

    65| members|

    66| meteringlabelrules|

    67| meteringlabels|

    68| ml2_brocadenetworks|

    69| ml2_brocadeports|

    70| ml2_dvr_port_bindings|

    71| ml2_flat_allocations|

    72| ml2_geneve_allocations|

    73| ml2_geneve_endpoints|

    74| ml2_gre_allocations|

    75| ml2_gre_endpoints|

    76| ml2_network_segments|

    77| ml2_nexus_vxlan_allocations|

    78| ml2_nexus_vxlan_mcast_groups|

    79| ml2_port_binding_levels|

    80| ml2_port_bindings|

    81| ml2_ucsm_port_profiles|

    82| ml2_vlan_allocations|

    83| ml2_vxlan_allocations|

    84| ml2_vxlan_endpoints|

    85| multi_provider_networks|

    86| networkconnections|

    87| networkdhcpagentbindings|

    88| networkgatewaydevicereferences|

    89| networkgatewaydevices|

    90| networkgateways|

    91| networkqueuemappings|

    92| networkrbacs|

    93| networks|

    94| networksecuritybindings|

    95| neutron_nsx_network_mappings|

    96| neutron_nsx_port_mappings|

    97| neutron_nsx_router_mappings|

    98|neutron_nsx_security_group_mappings|

    99| nexthops|

    100| nsxv_edge_dhcp_static_bindings|

    101| nsxv_edge_vnic_bindings|

    102| nsxv_firewall_rule_bindings|

    103| nsxv_internal_edges|

    104| nsxv_internal_networks|

    105| nsxv_port_index_mappings|

    106| nsxv_port_vnic_mappings|

    107| nsxv_router_bindings|

    108| nsxv_router_ext_attributes|

    109| nsxv_rule_mappings|

    110|nsxv_security_group_section_mappings|

    111|nsxv_spoofguard_policy_network_mappings |

    112| nsxv_tz_network_bindings|

    113| nsxv_vdr_dhcp_bindings|

    114|nuage_net_partition_router_mapping|

    115| nuage_net_partitions|

    116| nuage_provider_net_bindings|

    117| nuage_subnet_l2dom_mapping|

    118| ofcfiltermappings|

    119| ofcnetworkmappings|

    120| ofcportmappings|

    121| ofcroutermappings|

    122| ofctenantmappings|

    123| packetfilters|

    124| poolloadbalanceragentbindings|

    125| poolmonitorassociations|

    126| pools|

    127| poolstatisticss|

    128| portbindingports|

    129| portinfos|

    130| portqueuemappings|

    131| ports|

    132| portsecuritybindings|

    133| providerresourceassociations|

    134| qos_bandwidth_limit_rules|

    135| qos_network_policy_bindings|

    136| qos_policies|

    137| qos_port_policy_bindings|

    138| qosqueues|

    139| quotas|

    140| quotausages|

    141| reservations|

    142| resourcedeltas|

    143| router_extra_attributes|

    144| routerl3agentbindings|

    145| routerports|

    146| routerproviders|

    147| routerroutes|

    148| routerrules|

    149| routers|

    150| securitygroupportbindings|

    151| securitygrouprules|

    152| securitygroups|

    153| serviceprofiles|

    154| sessionpersistences|

    155| subnetpoolprefixes|

    156| subnetpools|

    157| subnetroutes|

    158| subnets|

    159| tz_network_bindings|

    160| vcns_router_bindings|

    161| vips|

    162| vpnservices|

    163+-----------------------------------------+

    164155 rows in set (0.00 sec)

    重启nova-api,并启动neutron服务

    1[root@linux-node1 config]# systemctlrestart openstack-nova-api

    2[root@linux-node1 config]# systemctlenable neutron-server.serviceneutron-linuxbridge-agent.service neutron-dhcp-agent.serviceneutron-metadata-agent.service

    3[root@linux-node1 config]# systemctlstart neutron-server.serviceneutron-linuxbridge-agent.service neutron-dhcp-agent.serviceneutron-metadata-agent.service

    检查neutron-agent结果

    1[root@linux-node1 config]# neutronagent-list

    2+--------------------------------------+--------------------+---------------------------+-------+----------------+---------------------------+

    3| id|agent_type| host| alive | admin_state_up | binary|

    4+--------------------------------------+--------------------+---------------------------+-------+----------------+---------------------------+

    5| 5a9a522f-e2dc-42dc-ab37-b26da0bfe416| Metadata agent|linux-node1.oldboyedu.com || True| neutron-metadata-agent|

    6| 8ba06bd7-896c-47aa-a733-8a9a9822361c| DHCP agent|linux-node1.oldboyedu.com || True| neutron-dhcp-agent|

    7| f16eef03-4592-4352-8d5e-c08fb91dc983| Linux bridge agent | linux-node1.oldboyedu.com || True| neutron-linuxbridge-agent |

    8+--------------------------------------+--------------------+---------------------------+-------+----------------+---------------------------+

    src="http://cdn.oldboyedu.com/wp-content/themes/Play-LM/images/smilies/icon_smile.gif"

    alt=":-)" class="wp-smiley" style="height: 1em;

    max-height: 1em;" />

    |

    class="pln"> True

    class="pln">

    class="pun">|

    neutron-

    class="pln">metadata

    class="pun">-agent

    class="pun">|

    class="L5">

    class="pun">|

    8ba06bd7

    class="pun">-

    class="lit">896c

    class="pun">-

    class="lit">47aa-

    class="pln">a733

    class="pun">-

    class="lit">8a9a9822361c

    class="pln"> |

    class="pln"> DHCP agent

    class="pun">|

    linux-

    class="pln">node1

    class="pun">.

    class="pln">oldboyedu

    class="pun">.com

    |

    class="pln">

    class="pun">

    alt=":-)" class="wp-smiley" style="height: 1em;

    max-height: 1em;" />

    |

    class="pln">

    class="typ">True

    |

    class="pln"> neutron

    class="pun">-

    class="pln">dhcp-

    class="pln">agent

    class="pun">|

    class="L6">

    class="pun">|

    f16eef03-

    class="lit">4592-

    class="lit">4352

    class="pun">-

    class="lit">8d5e-

    class="pln">c08fb91dc983

    class="pun">|

    Linux

    class="pln"> bridge agent

    class="pun">|

    linux-

    class="pln">node1

    class="pun">.

    class="pln">oldboyedu

    class="pun">.com

    |

    class="pln">

    class="pun">

    alt=":-)" class="wp-smiley" style="height: 1em;

    max-height: 1em;" />

    |

    class="pln">

    class="typ">True

    |

    class="pln"> neutron

    class="pun">-

    class="pln">linuxbridge

    class="pun">-agent

    class="pun">|

    class="L7">

    class="pun">+--------------------------------------+--------------------+---------------------------+-------+----------------+---------------------------+

    开始部署neutron的计算节点,在这里直接scp过去,不需要做任何更改

    1[root@linux-node1 config]#scp /etc/neutron/neutron.conf192.168.56.12:/etc/neutron/

    2[root@linux-node1 config]# scp/etc/neutron/plugins/ml2/linuxbridge_agent.ini192.168.56.12:/etc/neutron/plugins/ml2/

    修改计算节点的nova配置,添加如下内容到neutron模块即可

    13033:url = http://192.168.56.11:9696

    23034:auth_url =http://192.168.56.11:35357

    33035:auth_plugin = password

    43036:project_domain_id = default

    53037:user_domain_id = default

    63038:region_name = RegionOne

    73039:project_name = service

    83040:username = neutron

    93041:password = neutron

    103043:service_metadata_proxy = True

    113044:metadata_proxy_shared_secret =neutron

    12````

    13复制linuxbridge_agent

    14文件,无需更改,并创建ml2软连接

    15```bash

    16[root@linux-node1 ~]# scp/etc/neutron/plugins/ml2/linuxbridge_agent.ini192.168.56.12:/etc/neutron/plugins/ml2/

    17[root@linux-node ~]# ln -s/etc/neutron/plugins/ml2/ml2_conf.ini /etc/neutron/plugin.ini

    重启计算节点的nova-computer

    1[root@linux-node ml2]# systemctlrestart openstack-nova-compute.service

    计算机点上启动linuxbridge_agent服务

    1[root@linux-node ml2]# systemctlrestart openstack-nova-compute.service

    2[root@linux-node ml2]# systemctlenable neutron-linuxbridge-agent.service

    3ln -s'/usr/lib/systemd/system/neutron-linuxbridge-agent.service''/etc/systemd/system/multi-user.target.wants/neutron-linuxbridge-agent.service'

    4[root@linux-node ml2]# systemctl startneutron-linuxbridge-agent.service

    检查neutron的结果,有四个(控制节点一个,计算节点两个)结果代表正确

    1[root@linux-node1 config]# neutronagent-list

    2+--------------------------------------+--------------------+---------------------------+-------+----------------+---------------------------+

    3| id|agent_type| host| alive | admin_state_up| binary|

    4+--------------------------------------+--------------------+---------------------------+-------+----------------+---------------------------+

    5| 5a9a522f-e2dc-42dc-ab37-b26da0bfe416| Metadata agent|linux-node1.oldboyedu.com || True| neutron-metadata-agent|

    6| 7d81019e-ca3b-4b32-ae32-c3de9452ef9d| Linux bridge agent | linux-node.oldboyedu.com|| True| neutron-linuxbridge-agent |

    7| 8ba06bd7-896c-47aa-a733-8a9a9822361c| DHCP agent|linux-node1.oldboyedu.com || True| neutron-dhcp-agent|

    8| f16eef03-4592-4352-8d5e-c08fb91dc983| Linux bridge agent | linux-node1.oldboyedu.com || True| neutron-linuxbridge-agent |

    9+--------------------------------------+--------------------+---------------------------+-------+----------------+---------------------------+

    src="http://cdn.oldboyedu.com/wp-content/themes/Play-LM/images/smilies/icon_smile.gif"

    alt=":-)" class="wp-smiley" style="height: 1em;

    max-height: 1em;" />

    class="pun">|

    class="typ">True

    |

    class="pln"> neutron

    class="pun">-

    class="pln">metadata

    class="pun">-agent

    |

    class="L5">

    class="pun">|

    7d81019e

    class="pun">-

    class="pln">ca3b

    class="pun">-

    class="lit">4b32

    class="pun">-

    class="pln">ae32

    class="pun">-

    class="pln">c3de9452ef9d

    class="pun">|

    Linux

    class="pln"> bridge agent |

    class="pln"> linux

    class="pun">-

    class="pln">node

    class="pun">.oldboyedu

    class="pun">.com

    |

    class="pln">

    class="pun">

    src="http://cdn.oldboyedu.com/wp-content/themes/Play-LM/images/smilies/icon_smile.gif"

    alt=":-)" class="wp-smiley" style="height: 1em;

    max-height: 1em;" />

    |

    True

    class="pln">

    class="pun">|

    neutron-

    class="pln">linuxbridge

    class="pun">-agent

    |

    class="L6">

    class="pun">|

    8ba06bd7

    class="pun">-

    class="lit">896c

    class="pun">-47aa

    class="pun">-

    class="pln">a733

    class="pun">-

    class="lit">8a9a9822361c

    class="pln">

    class="pun">| DHCP

    agent |

    class="pln"> linux

    class="pun">-

    class="pln">node1

    class="pun">.

    class="pln">oldboyedu.

    class="pln">com

    class="pun">|

    src="http://cdn.oldboyedu.com/wp-content/themes/Play-LM/images/smilies/icon_smile.gif"

    alt=":-)" class="wp-smiley" style="height: 1em;

    max-height: 1em;" />

    |

    class="pln"> True

    class="pln">

    class="pun">|

    neutron-

    class="pln">dhcp

    class="pun">-agent

    class="pun">|

    class="L7">

    class="pun">|

    f16eef03-

    class="lit">4592

    class="pun">-

    class="lit">4352

    class="pun">-8d5e

    class="pun">-

    class="pln">c08fb91dc983

    class="pun">|

    Linux

    class="pln"> bridge agent

    class="pun">|

    linux-

    class="pln">node1

    class="pun">.

    class="pln">oldboyedu

    class="pun">.com

    |

    class="pln">

    class="pun">

    alt=":-)" class="wp-smiley" style="height: 1em;

    max-height: 1em;" />

    |

    class="pln">

    class="typ">True

    |

    class="pln"> neutron

    class="pun">-

    class="pln">linuxbridge

    class="pun">-agent

    class="pun">|

    class="L8">

    class="pun">+--------------------------------------+--------------------+---------------------------+-------+----------------+---------------------------+

    相关文章

      网友评论

          本文标题:实战OpenStack之控制节点(三)

          本文链接:https://www.haomeiwen.com/subject/zipuottx.html