Age | Commit message (Collapse) | Author | Files | Lines |
|
Issue-ID: MULTICLOUD-1324
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: I3193fb5983394c6ac9a95dffaaa36074f07cacf6
|
|
|
|
|
|
This enables the sriov interface type in kubevirt VMs.
Issue-ID: MULTICLOUD-1324
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: I03ab6a4d374b6abdcad9264ac8a959bb40ca9870
|
|
This allows for CPU pinning in VirtualMachine specs with the
dedicatedCpuPlacement and isolateEmulatorThread keys.
Issue-ID: MULTICLOUD-1324
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: Icba3eb07b80367d5bdda8708658f50486fc0780d
|
|
Issue-ID: MULTICLOUD-1324
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: I38a8dab6b57847f9f7b4f6a816772783fa981079
|
|
This chart contains the ovn-networkobj NetworkAttachmentDefinition
required by EMCO.
Issue-ID: MULTICLOUD-1324
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: Iaf10bacaf7ff263b165ca18a427958f7e75c3628
|
|
|
|
Create SDEWAN CNF helm chart and configure it with default value
Issue-ID: MULTICLOUD-1092
Signed-off-by: Yao Le <le.yao@intel.com>
Change-Id: Ib80e6b734c599a91f90d2fa4c32b098d6d279c0b
Signed-off-by: Ruoyu <ruoyu.ying@intel.com>
|
|
Issue-ID: MULTICLOUD-1324
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: I6ba134140f0aca6717c656ffa35c6576426a8b98
|
|
This fixes the "unknown FS magic" error reported by nfn-agent:
E0518 22:05:58.596460 20593 cni.go:150] Failed to configure
interface in pod: failed to open netns
"/var/run/netns/cni-c24e4d8e-819c-6a0c-9ae5-6b4e5cf8f68d": unknown
FS magic on
"/var/run/netns/cni-c24e4d8e-819c-6a0c-9ae5-6b4e5cf8f68d": 1021994
It can be observed as a failure of the ovn4nfv.sh test when
CONTAINER_RUNTIME is "containerd".
Issue-ID: MULTICLOUD-1324
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: If979110d125511827a65a5de5101a2832d5efeb5
|
|
This chart contains the upstream qat plugin from
intel-device-plugins-for-kubernetes together with a qat driver
installer.
Issue-ID: MULTICLOUD-1324
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: I3467ba204276999dac4087bdf68ac0d4439861ad
|
|
|
|
|
|
|
|
|
|
This chart follows the upstream installation guide with the following
exceptions:
- The node-role.kubernetes.io/master:NoSchedule taint is not removed.
The YAML files already included the necessary tolerations.
- No node labeling is done. Instead, the ovn-control-plane node
selector is for the master role, and the nfn-operator pod affinity
is for "role: ovn-control-plane". This ensures that the
ovn-control-plane and nfn-operator run are scheduled on the same
master node, equivalent to the labelling approach used upstream.
Also, additional allowed capabilities are needed to run the pods with
the restricted PodSecurityPolicy. These capabilities are requested by
the Pods, but not available in the default set of allowed
capabilities.
Issue-ID: MULTICLOUD-1324
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: I54ae12434572e2e2dd1fe2ec9298d04557331d94
|
|
This chart deploys the CR used by the sriov-network-operator.
Issue-ID: MULTICLOUD-1324
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: I9364868d3e58fd64e51a77aaa934284fad86a1b1
|
|
This chart contains the upstream sriov-network-operator from
k8snetworkplumbingwg together with an iavf driver installer.
Issue-ID: MULTICLOUD-1324
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: Ic925c66f8e2b28b7604240c3ed35b1a56883b60b
|
|
|
|
|
|
The chart follows the instructions laid out in the CMK operator
manual, with the following notes:
- The nodes are prepared by running each CMK subcommand as a Pod
instead of running cmk cluster-init. The first reason for this is
that the existing addon only deploys CMK to the worker nodes in the
cluster. This is not possible using cluster-init without explicitly
providing the list of worker nodes to cluster-init, and this list is
unknown by helm. Instead it is sufficient to rely on the
node-role.kubernetes.io/master:NoSchedule taint. The second reason
is that cluster-init creates resources which are unknown to helm,
thus uninstall does not behave as expected.
- The v1.4.1 version of CMK is chosen. In v1.5.2, the description key
of the cmk-nodereport resource is not correct.
- All values listed as possibly requiring modification are exposed in
values.yaml
Issue-ID: MULTICLOUD-1324
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: Ibc75462de3729cd88edeb4b15602d57fe12791ca
|
|
- Support for calico configuration is present but currently disabled.
Issue-ID: MULTICLOUD-1324
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: I2d2161564c4da2e165e5cf13cea92fae4935f8b2
|
|
Issue-ID: MULTICLOUD-1324
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: I90a9cf23a8fb01cbc579d2b6670b476494c2a7bb
|
|
This change adds iavf, qat, and pci device labels to the node feature
discovery config.
Issue-ID: MULTICLOUD-1324
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: Ie6296caf898983149483ac581428f2c80405bca8
|
|
Deploy the sdewan controller on master node
Change sdewan-contoller-manager to sdewan-crd-controller
Issue-ID: MULTICLOUD-1253
Signed-off-by: Le Yao <le.yao@intel.com>
Change-Id: Ic55744914266278f1c344c10af587d41f4426918
|
|
Create helm chart for sdewan-controller in KUD
Issue-ID: MULTICLOUD-1104
Signed-off-by: Yao Le <le.yao@intel.com>
Change-Id: Ic5d8daecdecba52c05d3ed38fa91ebd555ce5533
|