OpenStack (5) -neutron service deployment

Others 2019-09-09 23:00:56 views: null

OpenStack Networking (neutron) allows you to create the interface device managed by other OpenStack services and connect it to the network. Plug-ins can be implemented to accommodate different network equipment and software, providing flexibility for OpenStack architecture and deployment.

It includes the following components:

Neutron server

Receiving and routes the request to the appropriate API OpenStack Networking widget to operate.

OpenStack Networking plug-ins and agents

Plug port, create a network or subnet, and provides IP addressing. These plug-ins and agents due to a specific cloud vendor and technology used varies. OpenStack Networking comes for virtual and physical Cisco switch, NEC OpenFlow products, Open vSwitch, Linux and VMware NSX bridging products, plug-ins and agents.

Common Agent is L3 (Layer 3), DHCP (Dynamic Host IP addressing) and the plug agents.

message queue

Most OpenStack Networking to install and use it to route between the server and the various neutron proxy information. Also acts as a database to store the state of the network-specific plug-ins.

OpenStack Networking major OpenStack Compute interact with, and provide network connections for instance.

Next, we performed neutron to build;

1. Create a neutron database;

mysql> CREATE DATABASE neutron;
Query OK, 1 row affected (0.00 sec)

mysql> GRANT ALL PRIVILEGES ON neutron.* TO 'neutron'@'localhost' \
    ->   IDENTIFIED BY '123';
Query OK, 0 rows affected, 1 warning (0.09 sec)

mysql> GRANT ALL PRIVILEGES ON neutron.* TO 'neutron'@'%' \
    ->   IDENTIFIED BY '123';
Query OK, 0 rows affected, 1 warning (0.00 sec)

mysql>

2. Create a neutron users;

[root@sxb1 ~]# openstack user create --domain default --password-prompt neutron
User Password:
Repeat User Password:
+---------------------+----------------------------------+
| Field               | Value                            |
+---------------------+----------------------------------+
| domain_id           | default                          |
| enabled             | True                             |
| id                  | 454a19cd9fe24a32857e17a8ee8d8b40 |
| name                | neutron                          |
| options             | {}                               |
| password_expires_at | None                             |
+---------------------+----------------------------------+

3. neutron added to the admin role;

[root@sxb1 ~]# openstack role add --project service --user neutron admin

4. Create a neutron services;

[root@sxb1 ~]# openstack service create --name neutron \
>   --description "OpenStack Networking" network
+-------------+----------------------------------+
| Field       | Value                            |
+-------------+----------------------------------+
| description | OpenStack Networking             |
| enabled     | True                             |
| id          | 0c0e5eed3b9446dbb21a24fce483c665 |
| name        | neutron                          |
| type        | network                          |
+-------------+----------------------------------+

5. Resume api network service endpoint;

[root@sxb1 ~]# openstack endpoint create --region RegionOne   network public http://192.168.88.101:9696^C
[root@sxb1 ~]# openstack endpoint create --region RegionOne   network internal http://192.168.88.101:9696^C
[root@sxb1 ~]# openstack endpoint create --region RegionOne   network admin http://192.168.88.101:9696^C

6. Select Networking Option 2: Self-service networks mode;

Installing software;

yum install openstack-neutron openstack-neutron-ml2 openstack-neutron-linuxbridge ebtables

7. The neutron configuration file;

[root@sxb1 ~]# vim /etc/neutron/neutron.conf

[nova]
auth_url = http://192.168.88.101:5000　　　　　　需自己填写
auth_type = password
project_domain_name = default
user_domain_name = default
region_name = RegionOne
project_name = service
username = nova
password = 123

[DEFAULT]
core_plugin = ml2
service_plugins = router
allow_overlapping_ips = true
transport_url = rabbit://openstack:[email protected]
auth_strategy = keystone
notify_nova_on_port_status_changes = true
notify_nova_on_port_data_changes = true

[database]
connection = mysql+pymysql://neutron:[email protected]/neutron

[keystone_authtoken]
www_authenticate_uri = http://192.168.88.101:5000
auth_url = http://192.168.88.101:5000
memcached_servers = 192.168.88.101:11211
auth_type = password
project_domain_name = default
user_domain_name = default
project_name = service
username = neutron
password = 123

[oslo_concurrency]
lock_path = /var/lib/neutron/tmp

8. Layer configuration file;

[root@sxb1 ~]# vim /etc/neutron/plugins/ml2/ml2_conf.ini

[ml2]
type_drivers = flat,vlan,vxlan
tenant_network_types = vxlan
mechanism_drivers = linuxbridge,l2population

extension_drivers = port_security

[ml2_type_flat]
flat_networks = provider

[ml2_type_vxlan]
vni_ranges = 1:1000

[securitygroup]
enable_ipset = true

9. Layer bridge configuration;

[root@sxb1 ~]# vim /etc/neutron/plugins/ml2/linuxbridge_agent.ini

[linux_bridge]
physical_interface_mappings = provider:ens37

[vxlan]
enable_vxlan = true
local_ip = 192.168.88.101
l2_population = true

[securitygroup]
enable_security_group = true
firewall_driver = neutron.agent.linux.iptables_firewall.IptablesFirewallDriver

1 to 10. The modified kernel parameters; (kernel parameters required loading)

[root@sxb1 ~]# modprobe br_netfilter

[root@sxb1 ~]# cat /proc/sys/net/bridge/bridge-nf-call-iptables 
1
[root@sxb1 ~]# cat /proc/sys/net/bridge/bridge-nf-call-ip6tables 
1

11. Configure Layer plug-in files;

[root@sxb1 ~]# vim /etc/neutron/l3_agent.ini 

[DEFAULT]
interface_driver = linuxbridge

12. DHCP configuration file;

[root@sxb1 ~]# vim /etc/neutron/dhcp_agent.ini

[DEFAULT]
interface_driver = linuxbridge
dhcp_driver = neutron.agent.linux.dhcp.Dnsmasq
enable_isolated_metadata = true

13. metadaba configuration file;

[root@sxb1 ~]# vim /etc/neutron/metadata_agent.ini 

[DEFAULT]
nova_metadata_host = controller
metadata_proxy_shared_secret = 123

14. nova configuration file;

[root@sxb1 ~]# vim /etc/nova/nova.conf 

[neutron]
url = http://192.168.88.101:9696
auth_url = http://192.168.88.101:5000
auth_type = password
project_domain_name = default
user_domain_name = default
region_name = RegionOne
project_name = service
username = neutron
password = 123
service_metadata_proxy = true
metadata_proxy_shared_secret = 123

15. plugin configuration file to initialize the OK to database;

[root@sxb1 ~]# ln -s /etc/neutron/plugins/ml2/ml2_conf.ini /etc/neutron/plugin.ini^C


[root@sxb1 ~]# 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

16. Restart nova services;

[root@sxb1 ~]# systemctl restart openstack-nova-api.service
[root@sxb1 ~]# systemctl status openstack-nova-api.service
● openstack-nova-api.service - OpenStack Nova API Server
   Loaded: loaded (/usr/lib/systemd/system/openstack-nova-api.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2019-09-09 02:59:40 EDT; 7s ago
 Main PID: 6249 (nova-api)
   CGroup: /system.slice/openstack-nova-api.service
           ├─6249 /usr/bin/python2 /usr/bin/nova-api
           ├─6260 /usr/bin/python2 /usr/bin/nova-api
           └─6261 /usr/bin/python2 /usr/bin/nova-api

Sep 09 02:59:37 sxb1.101.com systemd[1]: Stopped OpenStack Nova API Server.
Sep 09 02:59:37 sxb1.101.com systemd[1]: Starting OpenStack Nova API Server...
Sep 09 02:59:38 sxb1.101.com nova-api[6249]: /usr/lib/python2.7/site-packages/p....
Sep 09 02:59:38 sxb1.101.com nova-api[6249]: return pkg_resources.EntryPoint.pa...)
Sep 09 02:59:40 sxb1.101.com systemd[1]: Started OpenStack Nova API Server.
Hint: Some lines were ellipsized, use -l to show in full.

17. Start neutron service (use status to see whether the service is started normally);

[root@sxb1 ~]# systemctl enable neutron-server.service   neutron-linuxbridge-agent.service neutron-dhcp-agent.service   neutron-metadata-agent.service^C
[root@sxb1 ~]# systemctl start neutron-server.service   neutron-linuxbridge-agent.service neutron-dhcp-agent.service   neutron-metadata-agent.service^C

18. Start layer 3 service (status check the service status);

[root@sxb1 ~]# systemctl restart neutron-l3-agent.service
[root@sxb1 ~]# systemctl status neutron-l3-agent.service
● neutron-l3-agent.service - OpenStack Neutron Layer 3 Agent
   Loaded: loaded (/usr/lib/systemd/system/neutron-l3-agent.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2019-09-09 03:39:22 EDT; 2s ago
 Main PID: 8267 (/usr/bin/python)
   CGroup: /system.slice/neutron-l3-agent.service
           └─8267 /usr/bin/python2 /usr/bin/neutron-l3-agent --config-file /usr/...

Sep 09 03:39:22 sxb1.101.com systemd[1]: Started OpenStack Neutron Layer 3 Agent.
Sep 09 03:39:23 sxb1.101.com neutron-l3-agent[8267]: net_mlx5: cannot load glue ...
Sep 09 03:39:23 sxb1.101.com neutron-l3-agent[8267]: net_mlx5: cannot initialize...
Sep 09 03:39:23 sxb1.101.com neutron-l3-agent[8267]: PMD: net_mlx4: cannot load ...
Sep 09 03:39:23 sxb1.101.com neutron-l3-agent[8267]: PMD: net_mlx4: cannot initi...
Hint: Some lines were ellipsized, use -l to show in full.

Here neutron controller node configuration is complete, then we compute nodes neutron configuration

1. Install the related components;

[root@sxb2 ~]# yum install openstack-neutron-linuxbridge ebtables ipset

2. neutron configuration file (database can not have configuration);

[root@sxb2 ~]# vim /etc/neutron/neutron.conf 

[DEFAULT]
transport_url = rabbit://openstack:[email protected]
auth_strategy = keystone

[keystone_authtoken]
www_authenticate_uri = http://192.168.88.101:5000
auth_url = http://192.168.88.101:5000
memcached_servers =192.168.88.101:11211
auth_type = password
project_domain_name = default
user_domain_name = default
project_name = service
username = neutron
password = 123

[oslo_concurrency]
lock_path = /var/lib/neutron/tmp

3.Networking Option 2: Self-service networks

Layer 2 network configuration file;

[root@sxb2 ~]# vim /etc/neutron/plugins/ml2/linuxbridge_agent.ini

[linux_bridge]
physical_interface_mappings = provider:ens37

[vxlan]
enable_vxlan = true
local_ip = 192.168.88.102
l2_population = true

[securitygroup]
enable_security_group = true
firewall_driver = neutron.agent.linux.iptables_firewall.IptablesFirewallDriver

4. Modify the kernel parameter is 1 (a load module);

[root@sxb2 ~]# modprobe br_netfilter
[root@sxb2 ~]# cat /proc/sys/net/bridge/bridge-nf-call-iptables 
1
[root@sxb2 ~]# cat /proc/sys/net/bridge/bridge-nf-call-ip6tables 
1

The configuration file nova computing node;

[root@sxb2 ~]# vim /etc/nova/nova.conf

[neutron]
url = http://192.168.88.101:9696
auth_url = http://192.168.88.101:5000
auth_type = password
project_domain_name = default
user_domain_name = default
region_name = RegionOne
project_name = service
username = neutron
password = 123

6. Restart nova service, check the service status;

[root@sxb2 ~]# systemctl restart openstack-nova-compute.service
[root@sxb2 ~]# systemctl status openstack-nova-compute.service
● openstack-nova-compute.service - OpenStack Nova Compute Server
   Loaded: loaded (/usr/lib/systemd/system/openstack-nova-compute.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2019-09-09 04:11:23 EDT; 9s ago
 Main PID: 17327 (nova-compute)
    Tasks: 22
   CGroup: /system.slice/openstack-nova-compute.service
           └─17327 /usr/bin/python2 /usr/bin/nova-compute

Sep 09 04:11:21 sxb2.102.com systemd[1]: Stopped OpenStack Nova Compute Server.
Sep 09 04:11:21 sxb2.102.com systemd[1]: Starting OpenStack Nova Compute Server...
Sep 09 04:11:23 sxb2.102.com systemd[1]: Started OpenStack Nova Compute Server.
Hint: Some lines were ellipsized, use -l to show in full.

7. Start neutron services, check the service status;

[root@sxb2 ~]# systemctl start neutron-linuxbridge-agent.service^C
[root@sxb2 ~]# systemctl status neutron-linuxbridge-agent.service^C
[root@sxb2 ~]# systemctl enable neutron-linuxbridge-agent.service^C

verification:

[Root @ sxb1 ~] # openstack extension list --network can be displayed on it
[root@sxb1 ~]# openstack network agent list
+--------------------------------------+--------------------+--------------+-------------------+-------+-------+---------------------------+
| ID                                   | Agent Type         | Host         | Availability Zone | Alive | State | Binary                    |
+--------------------------------------+--------------------+--------------+-------------------+-------+-------+---------------------------+
| 265134cd-eb4a-4eaa-a3bd-2de3acaf9a2c | L3 agent           | sxb1.101.com | nova              | :-)   | UP    | neutron-l3-agent          |
| 3ec7350c-1aea-4e09-9bd0-91096700a577 | Linux bridge agent | sxb2.102.com | None              | :-)   | UP    | neutron-linuxbridge-agent |
| 48fa3421-ece7-46b5-b161-c5a9bc7c805c | Metadata agent     | sxb1.101.com | None              | :-)   | UP    | neutron-metadata-agent    |
| 84130651-c3cd-4242-bde4-7a940cf7fc57 | Linux bridge agent | sxb1.101.com | None              | :-)   | UP    | neutron-linuxbridge-agent |
| cc65ec28-9f19-4097-9191-287122730c92 | DHCP agent         | sxb1.101.com | nova              | :-)   | UP    | neutron-dhcp-agent        |
+--------------------------------------+--------------------+--------------+-------------------+-------+-------+---------------------------+

5 appears there is no problem, the next chapter we Dashboard configuration

 

Guess you like

Origin www.cnblogs.com/loganSxb/p/11421332.html
Recommended
Ranking
A quick primer on numpy basics
Two sister tease python project
Java | Multiple keywords in the replacement content are returned to the front end in red style
C ++: references
The string leetcood 1018 is a binary prefix divisible by 5
Flutter 布局组件
Java combat spingboot-redis
PMP pre-exam sprint and wrong questions sorting
ActiveMq C# Message Features: Delayed and Timed Message Delivery
DSP28377S_ copy a program from the RAM to FLASH portion DETAILS
Daily
More
2024-05-16(23)
2024-05-15(5)
2024-05-14(9)
2024-05-13(8)
2024-05-12(28)
2024-05-11(32)
2024-05-10(34)
2024-05-09(32)
2024-05-08(18)
2024-05-07(34)

Code World

© 2018 codetd.com