Skip to content
Snippets Groups Projects
Verified Commit 9c245d2c authored by Vivek Dutta's avatar Vivek Dutta
Browse files

Update vendor extension in pipeline

parent 01e1c5f6
No related branches found
No related tags found
1 merge request!30Update vendor extension in pipeline
Pipeline #195873 failed
......@@ -10,7 +10,7 @@ OBJS = $(addprefix $(SRC_DIR)/, ethmngr.o helper.o ethernet.o dmlayer.o vendor_e
PROG_CFLAGS = $(CFLAGS) $(DIAG_CFLAGS) -Werror -fstrict-aliasing -fPIC -g
ifeq ($(filter -DBBF_VENDOR_PREFIX=%,$(PROG_CFLAGS)),)
PROG_CFLAGS += -DBBF_VENDOR_PREFIX=\"X_IOPSYS_EU_\"
PROG_CFLAGS += -DBBF_VENDOR_PREFIX=\"X_IOWRT_EU_\"
endif
# MUSL has the following issue in snprintf, so it is ignored:
......
# MACVLAN Vendor Extension Data Model
The purpose of this document is to explain the X_IOPSYS_EU_MACVLAN datamodel parameters handling/mapping for the network configuration.
The purpose of this document is to explain the X_IOWRT_EU_MACVLAN datamodel parameters handling/mapping for the network configuration.
## MACVLAN
The MACVLAN driver is the newest built-in network driver and offers several unique characteristics. It's a very lightweight driver, because rather than using any Linux bridging or port mapping, it connects container interfaces directly to host interfaces.
......@@ -72,7 +72,7 @@ To simplify the interface stacking, we introduce a new vendor specific interface
```mermaid
flowchart TD
A[IP.Interface.] --> B[Ethernet.X_IOPSYS_EU_MACVLAN.]
A[IP.Interface.] --> B[Ethernet.X_IOWRT_EU_MACVLAN.]
B --> C[Ethernet.Link.]
```
......@@ -81,7 +81,7 @@ It could be possible to create a MACVLAN interface on tagged and untagged interf
### Datamodel for MACVLAN over untagged interface
```mermaid
flowchart TD
A[IP.Interface.] --> B[Ethernet.X_IOPSYS_EU_MACVLAN.]
A[IP.Interface.] --> B[Ethernet.X_IOWRT_EU_MACVLAN.]
B --> C[Ethernet.Link.]
C --> D[Ethernet.Interface.]
```
......@@ -89,7 +89,7 @@ flowchart TD
### Datamodel for MACVLAN over Tagged interface
```mermaid
flowchart TD
A[IP.Interface.] --> B[Ethernet.X_IOPSYS_EU_MACVLAN.]
A[IP.Interface.] --> B[Ethernet.X_IOWRT_EU_MACVLAN.]
B --> C[Ethernet.VLANTermination.]
C --> D[Ethernet.Link.]
D --> E[Ethernet.Interface.]
......@@ -99,18 +99,18 @@ flowchart TD
Since this new vendor extension is an interface object, we introduce parameters that are similar to those on an interface object, which are as below:
```bash
Device.Ethernet.X_IOPSYS_EU_MACVLAN.{i}.Enable
Device.Ethernet.X_IOPSYS_EU_MACVLAN.{i}.Status
Device.Ethernet.X_IOPSYS_EU_MACVLAN.{i}.Alias
Device.Ethernet.X_IOPSYS_EU_MACVLAN.{i}.Name
Device.Ethernet.X_IOPSYS_EU_MACVLAN.{i}.LowerLayers
Device.Ethernet.X_IOPSYS_EU_MACVLAN.{i}.MACAddress
Device.Ethernet.X_IOPSYS_EU_MACVLAN.{i}.Stats.BytesSent
Device.Ethernet.X_IOPSYS_EU_MACVLAN.{i}.Stats.BytesReceived
Device.Ethernet.X_IOPSYS_EU_MACVLAN.{i}.Stats.PacketsSent
Device.Ethernet.X_IOPSYS_EU_MACVLAN.{i}.Stats.PacketsReceived
Device.Ethernet.X_IOPSYS_EU_MACVLAN.{i}.Stats.ErrorsSent
Device.Ethernet.X_IOPSYS_EU_MACVLAN.{i}.Stats.ErrorsReceived
Device.Ethernet.X_IOPSYS_EU_MACVLAN.{i}.Stats.DiscardPacketsSent
Device.Ethernet.X_IOPSYS_EU_MACVLAN.{i}.Stats.DiscardPacketsReceived
Device.Ethernet.X_IOWRT_EU_MACVLAN.{i}.Enable
Device.Ethernet.X_IOWRT_EU_MACVLAN.{i}.Status
Device.Ethernet.X_IOWRT_EU_MACVLAN.{i}.Alias
Device.Ethernet.X_IOWRT_EU_MACVLAN.{i}.Name
Device.Ethernet.X_IOWRT_EU_MACVLAN.{i}.LowerLayers
Device.Ethernet.X_IOWRT_EU_MACVLAN.{i}.MACAddress
Device.Ethernet.X_IOWRT_EU_MACVLAN.{i}.Stats.BytesSent
Device.Ethernet.X_IOWRT_EU_MACVLAN.{i}.Stats.BytesReceived
Device.Ethernet.X_IOWRT_EU_MACVLAN.{i}.Stats.PacketsSent
Device.Ethernet.X_IOWRT_EU_MACVLAN.{i}.Stats.PacketsReceived
Device.Ethernet.X_IOWRT_EU_MACVLAN.{i}.Stats.ErrorsSent
Device.Ethernet.X_IOWRT_EU_MACVLAN.{i}.Stats.ErrorsReceived
Device.Ethernet.X_IOWRT_EU_MACVLAN.{i}.Stats.DiscardPacketsSent
Device.Ethernet.X_IOWRT_EU_MACVLAN.{i}.Stats.DiscardPacketsReceived
```
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment