Rhosp: TSN provison fails if the interface of TSN and compute nodes are not same in contrail-net.yaml

Bug #1709974 reported by shajuvk on 2017-08-10
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R3.2
Won't Fix
Critical
Michael Henkel
R4.0
Won't Fix
High
Michael Henkel
R4.1
Won't Fix
High
Michael Henkel
R5.0
Fix Committed
High
Michael Henkel
Trunk
Fix Committed
High
Michael Henkel

Bug Description

Contrail-TSN provisioning failed in R3.2 since the vrouter nic name and TSN node nic name are different.
Vrouter eno1 wil be vhost0 but in TSN node it is eth1. contrail-net.ymal has an entry VrouterPhysicalInterface: eno1 to provision vrouter vhost0 byt tsn vhost0 it coudn't identify

We don't have a separate option in contrail-net.yaml for specifying nic name for TSN.

shajuvk (shajuvk) on 2017-08-10
information type: Proprietary → Public
Jeba Paulaiyan (jebap) on 2017-08-11
tags: added: provisioning rhosp
shajuvk (shajuvk) on 2017-08-15
description: updated
Michael Henkel (mhenkel-3) wrote :

This problem cannot be solved in OSP10 as there is only a global definition for the vrouter interface. In OSP11 it will be per role. In OSP12 it won't be needed anymore as we'll use os-net-config.

Jeba Paulaiyan (jebap) wrote :

Notes for Release notes:

TSN support in RHOSP based clusters are supported upto RHOSP10

Michael Henkel (mhenkel-3) wrote :

Workaround until OSP12:

Deploy the stack with computes and dpdk first. Then change the VrouterPhysicalInterface and add the TSN nodes and update the stack.

Jeba Paulaiyan (jebap) on 2018-06-28
tags: added: beta-blocker
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers