diff options
author | davidjchou <david.j.chou@intel.com> | 2017-03-05 17:39:24 -0900 |
---|---|---|
committer | Dan Radez <dradez@redhat.com> | 2017-03-09 17:54:20 +0000 |
commit | fb8c23c5413ee7c820f7c947fb1bb007d5d4cf95 (patch) | |
tree | 334bec4406bb7b503556911974db8150d23ae876 /config | |
parent | 8b2ca87007c2cb477765c183325e5af03bf9f80d (diff) |
Adding "Real Time KVM" support
Adding the support to run the "Real Time KVM" kernel in the compute
node(s) to reduce the network latency caused by the virtualization of
the network functions. Since the current "Real Time KVM" kernel
doesn't support physical to logical network interface mapping yet, we
need to use the real physical interface name rather than the logical
interface name for all compute interfaces in network_settings.yaml.
Also updates tests for the network settings changes and fixes a bug
where interface was being queried on the controller nics before it
interfaces were validated.
JIRA: APEX-128
Change-Id: Iccb6c9fbdcf7e3b482f4283039ef17c38e0a6df7
Signed-off-by: davidjchou <david.j.chou@intel.com>
Signed-off-by: Tim Rozet <trozet@redhat.com>
Signed-off-by: Dan Radez <dradez@redhat.com>
Diffstat (limited to 'config')
-rw-r--r-- | config/deploy/deploy_settings.yaml | 4 | ||||
-rw-r--r-- | config/deploy/os-nosdn-kvm-ha.yaml | 11 | ||||
-rw-r--r-- | config/deploy/os-nosdn-kvm-noha.yaml | 11 | ||||
-rw-r--r-- | config/network/network_settings.yaml | 10 |
4 files changed, 31 insertions, 5 deletions
diff --git a/config/deploy/deploy_settings.yaml b/config/deploy/deploy_settings.yaml index b3d3ac2b..73535795 100644 --- a/config/deploy/deploy_settings.yaml +++ b/config/deploy/deploy_settings.yaml @@ -41,6 +41,10 @@ deploy_options: # 'ovs', 'ovs_dpdk' and 'fdio'. dataplane : ovs + # Whether to run the kvm real time kernel (rt_kvm) in the compute node(s) to + # reduce the network latencies caused by network function virtualization + rt_kvm: false + # Whether to install and configure fdio functionality in the overcloud # The dataplane should be specified as fdio if this is set to true vpp: false diff --git a/config/deploy/os-nosdn-kvm-ha.yaml b/config/deploy/os-nosdn-kvm-ha.yaml new file mode 100644 index 00000000..cb68a313 --- /dev/null +++ b/config/deploy/os-nosdn-kvm-ha.yaml @@ -0,0 +1,11 @@ +global_params: + ha_enabled: true + +deploy_options: + sdn_controller: false + sdn_l3: false + tacker: true + congress: true + sfc: false + vpn: false + rt_kvm: true diff --git a/config/deploy/os-nosdn-kvm-noha.yaml b/config/deploy/os-nosdn-kvm-noha.yaml new file mode 100644 index 00000000..bf737d71 --- /dev/null +++ b/config/deploy/os-nosdn-kvm-noha.yaml @@ -0,0 +1,11 @@ +global_params: + ha_enabled: false + +deploy_options: + sdn_controller: false + sdn_l3: false + tacker: true + congress: true + sfc: false + vpn: false + rt_kvm: true diff --git a/config/network/network_settings.yaml b/config/network/network_settings.yaml index 1cba64bb..be0b6836 100644 --- a/config/network/network_settings.yaml +++ b/config/network/network_settings.yaml @@ -80,7 +80,7 @@ networks: # Network configurations compute: # Mapping for compute profile (nodes that will be used as Compute nodes) phys_type: interface # Physical interface type (interface or bond) members: # Physical NIC members of this mapping (Single value allowed for interface phys_type) - - nic1 + - eth0 controller: # Mapping for controller profile (nodes that will be used as Controller nodes) phys_type: interface members: @@ -99,7 +99,7 @@ networks: # Network configurations phys_type: interface # Physical interface type (interface or bond) vlan: native # VLAN tag to use with this NIC members: # Physical NIC members of this mapping (Single value allowed for interface phys_type) - - nic2 # Note, for Apex you may also use the logical nic name (found by nic order), such as "nic1" + - eth1 # Note, for Apex you may also use the logical nic name (found by nic order), such as "nic1" controller: # Mapping for controller profile (nodes that will be used as Controller nodes) phys_type: interface vlan: native @@ -130,7 +130,7 @@ networks: # Network configurations phys_type: interface # Physical interface type (interface or bond) vlan: native # VLAN tag to use with this NIC members: # Physical NIC members of this mapping (Single value allowed for interface phys_type) - - nic3 + - eth2 controller: # Mapping for controller profile (nodes that will be used as Controller nodes) phys_type: interface vlan: native @@ -163,7 +163,7 @@ networks: # Network configurations phys_type: interface # Physical interface type (interface or bond) vlan: 101 # VLAN tag to use with this NIC members: # Physical NIC members of this mapping (Single value allowed for interface phys_type) - - nic3 # Note, for Apex you may also use the logical nic name (found by nic order), such as "nic1" + - eth2 # Note, for Apex you may also use the logical nic name (found by nic order), such as "nic1" controller: # Mapping for controller profile (nodes that will be used as Controller nodes) phys_type: interface vlan: 101 @@ -184,7 +184,7 @@ networks: # Network configurations phys_type: interface # Physical interface type (interface or bond) vlan: native # VLAN tag to use with this NIC members: # Physical NIC members of this mapping (Single value allowed for interface phys_type) - - nic4 # Note, for Apex you may also use the logical nic name (found by nic order), such as "nic1" + - eth3 # Note, for Apex you may also use the logical nic name (found by nic order), such as "nic1" controller: # Mapping for controller profile (nodes that will be used as Controller nodes) phys_type: interface vlan: native |