Please add mechanism permutations for interdomain

[edwarnicke]

Currently interdomain only has Kernel2Vxlan2Kernel, we should test the other permutations as well.

[denis-tingaikin]

Will do!

Currently, we have wireguard support and the issue now makes much sense.

[denis-tingaikin]

Currently, I see these combinations:

Kernel2Wireguard2Kernel
Kernel2Wireguard2Memif
Memif2Wireguard2Memif
Memif2Wireguard2Kernel

Kernel2Vxlan2Kernel
Kernel2Vxlan2Memif
Memif2Vxlan2Memif
Memif2Vxlan2Kernel

Kernel2Ipec2Kernel
Kernel2Ipec2Memif
Memif2Ipec2Memif
Memif2Ipec2Kernel

@edwarnicke Is it enough for the definition of done?

[edwarnicke]

Yep!

[glazychev-art]

In my opinion, our directory hierarchy looks a little confusing right now. For example, adding interdomain ipsec here will make the problem worse. In this issue, I propose to structure at least multicluster subdirectory:

└── multicluster
    ├── clusters-configuration
    │   ├── nsm-system
    │   │   ├── basic
    │   │   │   ├── cluster1
    │   │   │   ├── cluster2
    │   │   │   ├── cluster3
    │   │   │   └── README.md
    │   │   └── ipsec
    │   │       ├── cluster1
    │   │       ├── cluster2
    │   │       ├── cluster3
    │   │       └── README.md
    │   └── requirements
    │       ├── dns
    │       │   └── README.md
    │       ├── loadbalancer
    │       │   └── README.md
    │       └── spiffe_federation
    │           └── README.md
    ├── suites
    │   ├── basic
    │   │   └── README.md
    │   ├── heal
    │   │   └── README.md
    │   └── ipsec
    │       └── README.md
    └── usecases
        ├── floating
        │   ├── floating_Kernel2Ethernet2Kernel
        │   └── floating_Kernel2Ethernet2Memif
        ├── heal
        │   ├── floating-forwarder-death
        │   └── floating-nse-death
        └── interdomain
            ├── interdomain_dns
            └── interdomain_Kernel2Ethernet2Kerne