When networking configuration for a cluster is needed and all the details are common between the nodes in the cluster a NMState yaml configuration is enough.
Problems arise when some of the network configuration details are different between nodes and depend on the current node network state.
For that a different NMState yaml configuration needs to be generated per node and that's not convenient for big clusters and also at scale up scenarios.
The NMPolicy goal is to solve this problem.
Given a node network state and a network configuration policy (common to the cluster), the NMPolicy tool will generate a node specific desired network state.
NMPolicy was already integrated to kubernetes-nmstate and a usage example can be found here.
CLI Usage example -
Simulated --help output
Output of - nmstatectl show | nmpolicyctl gen policy.yaml
~/.cache/nmpolicy/cache.yaml (the default captured states output file)
Stdout (the desired state to be applied by nmstatectl)
--
You received this message because you are subscribed to the Google Groups "kubevirt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubevirt-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubevirt-dev/CAJOMPacxNke2pJnjJ1PKxz0f%3Dmm%3DrNpnWqZwAMtNXf7f0HXL_Q%40mail.gmail.com.
Thanks for sharing your plan.I would like to create a Linux bond of all the NICs of my machine, create a Linux bridge on top of it, and copy my original mac/IP/routing to that bridge. Can you share a policy that would let me express this desired state?
To view this discussion on the web visit https://groups.google.com/d/msgid/kubevirt-dev/CAHOEP56e4zhHPtP8rZp%3D%3DZ_zf_XyTb-hOB%2BvVOiwMX%3DniqRNrg%40mail.gmail.com.
CNV networking Senior Software Engineer
On Fri, Dec 17, 2021 at 3:58 PM Dan Kenigsberg <dan...@redhat.com> wrote:Thanks for sharing your plan.I would like to create a Linux bond of all the NICs of my machine, create a Linux bridge on top of it, and copy my original mac/IP/routing to that bridge. Can you share a policy that would let me express this desired state?You need to know the number of NICs, for example for three of them this would be it.
On Fri, Dec 17, 2021 at 5:25 PM Felix Enrique Llorente Pastora <ello...@redhat.com> wrote:On Fri, Dec 17, 2021 at 3:58 PM Dan Kenigsberg <dan...@redhat.com> wrote:Thanks for sharing your plan.I would like to create a Linux bond of all the NICs of my machine, create a Linux bridge on top of it, and copy my original mac/IP/routing to that bridge. Can you share a policy that would let me express this desired state?You need to know the number of NICs, for example for three of them this would be it.Thanks. Having a Python-like `0:-1` slice index to select a sublist could be even cooler.More importantly, I would like to be able to select all interfaces which have vlan 204 enabled on their switch port, as reported by lldp. What would the capture look like in this case?
On Sun, Dec 19, 2021 at 10:42 AM Dan Kenigsberg <dan...@redhat.com> wrote:On Fri, Dec 17, 2021 at 5:25 PM Felix Enrique Llorente Pastora <ello...@redhat.com> wrote:On Fri, Dec 17, 2021 at 3:58 PM Dan Kenigsberg <dan...@redhat.com> wrote:Thanks for sharing your plan.I would like to create a Linux bond of all the NICs of my machine, create a Linux bridge on top of it, and copy my original mac/IP/routing to that bridge. Can you share a policy that would let me express this desired state?You need to know the number of NICs, for example for three of them this would be it.Thanks. Having a Python-like `0:-1` slice index to select a sublist could be even cooler.