Open Stack

On Wed, Nov 22, 2017 at 2:29 AM, Ben Nemec <openstack at nemebean.com> wrote:
> Thanks.  Unfortunately I don't see anything obviously wrong with that, but
> I'm not a DPDK expert either.  Hopefully one of our networking gurus can
> chime in and comment on whether this should work.
>
> On 11/21/2017 02:01 PM, Samuel Monderer wrote:
>>
>> http://paste.openstack.org/show/626557/
>>
>> On Tue, Nov 21, 2017 at 8:22 PM Ben Nemec <openstack at nemebean.com
>> <mailto:openstack at nemebean.com>> wrote:
>>
>>     Your configuration lost all of its indentation, which makes it
>> extremely
>>     difficult to read.  Can you try sending it a different way, maybe
>>     paste.openstack.org <http://paste.openstack.org>?
>>
>>
>>     On 11/16/2017 02:43 AM, Samuel Monderer wrote:
>>      > Hi,
>>      >
>>      > I managed to deploy a compute node with ovs-dpdk using two NICs.
>> The
>>      > first for the provisioning network and control plane, the other
>>     NIC is
>>      > used tenant network over ovs-dpdk.
>>      >
>>      > I then tried to use only a single nic for provisioning and
>> ovs-dpdk.
This is not a recommended way of using DPDK.

>>      > I used the nic configuration below for the compute nodes running
>>      > ovs-dpdk but encountered two problems.
>>      > First the tenant network was working (wasn't able to get DHCP
>> running
>>      > and even when I manually configured it wasn't able to reach the
>>     router)
I am assuming that your dpdk ports are active (verified by ovs-vsctl
show command). The only usecases that we have validated is using DPDK
as provider network and DPDK as Tenant network [1] which will have the
tenant and vlan configured directly on the bridge (this configuration
was recommended from the ovs team).

>>      > Second the default route on control plane is not set even though
>>     it is
>>      > configured in /etc/sysconfig/network-scripts/route-br-ex
>>      >
I am not sure if there is any difference between system and netdev
bridges in setting the routes, but you could validate by adding logs
to the ifup scripts and trace it out why the route is not invoked.

Regards,
Saravanan KR

[1] http://paste.openstack.org/show/627030/

>>      > Samuel
>>      >
>>      > OsNetConfigImpl:
>>      > type: OS::Heat::StructuredConfig
>>      > properties:
>>      > group: os-apply-config
>>      > config:
>>      > os_net_config:
>>      > network_config:
>>      > -
>>      > type: ovs_user_bridge
>>      > name: {get_input: bridge_name}
>>      > use_dhcp: false
>>      > dns_servers: {get_param: DnsServers}
>>      > addresses:
>>      > -
>>      > ip_netmask:
>>      > list_join:
>>      > - '/'
>>      > - - {get_param: ControlPlaneIp}
>>      > - {get_param: ControlPlaneSubnetCidr}
>>      > routes:
>>      > -
>>      > ip_netmask: 169.254.169.254/32 <http://169.254.169.254/32>
>>     <http://169.254.169.254/32>
>>      > next_hop: {get_param: EC2MetadataIp}
>>      > -
>>      > default: true
>>      > next_hop: {get_param: ControlPlaneDefaultRoute}
>>      > members:
>>      > -
>>      > type: ovs_dpdk_port
>>      > name: dpdk0
>>      > members:
>>      > -
>>      > type: interface
>>      > name: nic1
>>      > -
>>      > type: vlan
>>      > vlan_id: {get_param: InternalApiNetworkVlanID}
>>      > addresses:
>>      > -
>>      > ip_netmask: {get_param: InternalApiIpSubnet}
>>      > -
>>      > type: vlan
>>      > vlan_id: {get_param: TenantNetworkVlanID}
>>      > addresses:
>>      > -
>>      > ip_netmask: {get_param: TenantIpSubnet}
>>      >
>>      >
>>      >
>>      >
>>
>> __________________________________________________________________________
>>      > OpenStack Development Mailing List (not for usage questions)
>>      > Unsubscribe:
>>     OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>     <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>>      > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>      >
>>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev