How to configure right network interface?

LINSTOR
1

How to choose second network interface during deploy linstorCluster/linstorSatelliteConfigurations
my config is:

linstorSatelliteConfigurations:
- name: host-network
  podTemplate:
    spec:
      hostNetwork: true
      dnsPolicy: ClusterFirstWithHostNet

linstorNodeConnections:
- name: network-paths
  paths:
  - interface: enp4s0
    name: data

Finaly Linstor does not see second interface - enp4s0. It takes first interface(enp3s0) and if look at UI to node details I can see as default-ipv4 is taken

2

What exactly do you mean by “choose second network interface”? Do you mean you want to use this network interface for DRBD replication traffic?

If so, at the CLI it would be:

linstor node interface create mynode drbd 1.2.3.4
linstor node set-property mynode PrefNic drbd

(repeat for each node in the cluster)

Note that you don’t have to use the local NIC name like enp4s0 - here I’ve chosen “drbd” as the name by which Linstor refers to the NIC. In turn, it identifies the NIC by its IP address, in this example 1.2.3.4.

Maybe you can convert the above into kubernetes-ese.

3

Thanks a lot for your answer
it means, that i can’t configure second interface via helm of linstor-cluster? only via linstor cli? i have to perform cli command to create drbd interface?

4

There seem to be a bunch of Linstor operators out there, and I don’t know or use any of them.

What I’m saying is: once you know how to do it with the CLI, you may be able to find out how to do it via whichever operator you are using (that is, create a “node interface” and set a “node property”). And if it’s not possible, you can raise it as a feature request on the operator’s issue tracker.

5

ok, Thank You very much

6

Although you haven’t named the helm chart you’re using, one of the possibilities is the piraeus operator linstor-cluster chart. Is that the one?

Looking at values.yaml I see:

## Additional properties to apply on the LINSTOR Satellite. Can inherit values from the Kubernetes Node resource.
#  properties:
#    - name: AutoplaceTarget
#      value: "no"
#    - name: Aux/topology/failure-domain
#      valueFrom:
#        nodeFieldRef: metadata.annotations['example.com/failure-domain']
#      optional: true

and in the docs:

apiVersion: piraeus.io/v1
kind: LinstorSatelliteConfiguration
metadata:
  name: ipv6-nodes
spec:
  properties:
    - name: PrefNic
      value: "default-ipv6"

Hence it’s clear how to set PrefNic.

However here it says:

Paths configure one or more network connections between nodes. If a path is configured, LINSTOR will use the given network interface to configure DRBD replication. The network interfaces have to be registered with LINSTOR first, using linstor node interface create ... .

So, it doesn’t look like this particular helm chart supports doing this declaratively.

If you are using a different chart, check its documentation.

7

Yes, I use this helm chart and as You right noticed i have to create interface via cli first, but it is not always convinietn.
anyway Thanks a lot