The Macvtap mechanism driver for the ML2 plug-in generally increases network performance of instances.
Consider the following attributes of this mechanism driver to determine practicality in your environment:
コンピュートリソースだけが macvtap 経由で接続できます。 DHCP、ルーターなどの他のリソースの接続には対応していません。したがって、コントローラーノードでは OVS エージェントか Linux ブリッジエージェントを VLAN かフラットモードで動かします。
You can add this mechanism driver to an existing environment using either the Linux bridge or OVS mechanism drivers with only provider networks or provider and self-service networks. You can change the configuration of existing compute nodes or add compute nodes with the Macvtap mechanism driver. The example configuration assumes addition of compute nodes with the Macvtap mechanism driver to the Linux bridge: セルフサービスネットワーク or Open vSwitch: Self-service networks deployment examples.
Add one or more compute nodes with the following components:
注釈
To support integration with the deployment examples, this content configures the Macvtap mechanism driver to use the overlay network for untagged (flat) or tagged (VLAN) networks in addition to overlay networks such as VXLAN. Your physical network infrastructure must support VLAN (802.1q) tagging on the overlay network.
The Macvtap mechanism driver only applies to compute nodes. Otherwise, the environment resembles the prerequisite deployment example.
Use the following example configuration as a template to add support for the Macvtap mechanism driver to an existing operational environment.
ml2_conf.ini ファイル:
Add macvtap to mechanism drivers.
[ml2]
mechanism_drivers = macvtap
Configure network mappings.
注釈
Use of macvtap is arbitrary. Only the self-service deployment examples require VLAN ID ranges. Replace VLAN_ID_START and VLAN_ID_END with appropriate numerical values.
Restart the following services:
サーバー
変更なし。
Install the Networking service Macvtap layer-2 agent.
In the neutron.conf file, configure common options:
[DEFAULT]
core_plugin = ml2
auth_strategy = keystone
rpc_backend = rabbit
notify_nova_on_port_status_changes = true
notify_nova_on_port_data_changes = true
[database]
...
[keystone_authtoken]
...
[oslo_messaging_rabbit]
...
[nova]
...
See the Installation Guide for your OpenStack release to obtain the appropriate configuration for the [database], [keystone_authtoken], [oslo_messaging_rabbit], and [nova] sections.
In the macvtap_agent.ini file, configure the layer-2 agent.
[macvtap]
physical_interface_mappings = macvtap:MACVTAP_INTERFACE
[securitygroup]
firewall_driver = noop
Replace MACVTAP_INTERFACE with the name of the underlying interface that handles Macvtap mechanism driver interfaces. If using a prerequisite deployment example, replace MACVTAP_INTERFACE with the name of the underlying interface that handles overlay networks. For example, eth1.
以下のサービスを実行します。
macvtap エージェント
管理プロジェクトのクレデンシャルを読み込みます。
エージェントが存在し、動作していることを確認します。
$ neutron agent-list
+--------------------------------------+---------------+----------+-------------------+-------+----------------+---------------------------+
| id | agent_type | host | availability_zone | alive | admin_state_up | binary |
+--------------------------------------+--------------------+----------+-------------------+-------+----------------+---------------------------+
| 7af923a4-8be6-11e6-afc3-3762f3c3cf6e | Macvtap agent | compute1 | | :-) | True | neutron-macvtap-agent |
| 80af6934-8be6-11e6-a046-7b842f93bb23 | Macvtap agent | compute2 | | :-) | True | neutron-macvtap-agent |
+--------------------------------------+---------------+----------+-------------------+-------+----------------+---------------------------+
This mechanism driver simply changes the virtual network interface driver for instances. Thus, you can reference the Create initial networks content for the prerequisite deployment example.
This mechanism driver simply changes the virtual network interface driver for instances. Thus, you can reference the Verify network operation content for the prerequisite deployment example.
This mechanism driver simply removes the Linux bridge handling security groups on the compute nodes. Thus, you can reference the network traffic flow scenarios for the prerequisite deployment example.
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.