I want to use only one NIC and run all the networks on top of it
http://paste.openstack.org/show/626509/

On Thu, Nov 16, 2017 at 12:21 PM Sanjay Upadhyay <supad...@redhat.com>
wrote:

> On Thu, Nov 16, 2017 at 1:51 PM, Numan Siddique <nusid...@redhat.com>
> wrote:
>
>> I think sending this email to openstack-dev ML with tripleo tagged could
>> help in getting more responses.
>>
>
> +1
>
>
>> Thanks
>> Numan
>>
>>
>> On Thu, Nov 16, 2017 at 4:11 AM, Samuel Monderer <
>> smonde...@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.
>>>
>>
>
> In the config I see only 1 nic
> use pastebin <http://paste.openstack.org> to preserve the yaml structure.
>
> /sanjay
>
>
>> 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@lists.rdoproject.org
>>> http://lists.rdoproject.org/mailman/listinfo/users
>>>
>>> To unsubscribe: users-unsubscr...@lists.rdoproject.org
>>>
>>>
>>
>> _______________________________________________
>> users mailing list
>> users@lists.rdoproject.org
>> http://lists.rdoproject.org/mailman/listinfo/users
>>
>> To unsubscribe: users-unsubscr...@lists.rdoproject.org
>>
>> _______________________________________________
> users mailing list
> users@lists.rdoproject.org
> http://lists.rdoproject.org/mailman/listinfo/users
>
> To unsubscribe: users-unsubscr...@lists.rdoproject.org
>
_______________________________________________
users mailing list
users@lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/users

To unsubscribe: users-unsubscr...@lists.rdoproject.org

Reply via email to