[rdo-users] [Tripleo] Composable role OVS-DPDK compute node with single NIC

[Samuel Monderer]

I've attached the NIC config file and also pasted it to
http://paste.openstack.org/show/626557/

On Thu, Nov 16, 2017 at 9:05 PM Dan Sneddon <dsneddon at redhat.com> wrote:

> On Wed, Nov 15, 2017 at 2:41 PM, Samuel Monderer <
> smonderer at vasonanetworks.com> 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.
>> 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)
>> Second the default route on control plane is not set even though it is
>> configured in /etc/sysconfig/network-scripts/route-br-ex
>>
>> 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
>> 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}
>>
>> _______________________________________________
>> users mailing list
>> users at lists.rdoproject.org
>> http://lists.rdoproject.org/mailman/listinfo/users
>>
>> To unsubscribe: users-unsubscribe at lists.rdoproject.org
>>
>>
> Samuel,
>
> Can you attach an unmodified version of this NIC config, rather than
> copy/paste into the email?
>
> I think you have an issue here:
>
> members:
> -
> type: ovs_dpdk_port
> name: dpdk0
> members:
> -
> type: interface
> name: nic1
>
> It appears that you have the ovs_dpdk_port as a member of the user bridge,
> but then you have the NIC and the VLANs as members of the ovs_dpdk_port,
> but the VLANs should be members of the bridge, not the ovs_dpdk_port.
>
> But that might not be the case, which is why I would like to see the
> original unmodifed NIC config.
>
> --
> Dan Sneddon         |  Senior Principal OpenStack Engineer
> dsneddon at redhat.com |  redhat.com/openstack
> dsneddon:irc        |  @dxs:twitter
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rdoproject.org/pipermail/users/attachments/20171116/18478cfe/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ComputeOvsDpdk.yaml
Type: application/x-yaml
Size: 3797 bytes
Desc: not available
URL: <http://lists.rdoproject.org/pipermail/users/attachments/20171116/18478cfe/attachment.bin>