Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
Issue-ID: MULTICLOUD-1324
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: If2845857cd72768b0a1c6cf3831e64f3dc412ebf
|
|
The steps performed by the existing ansible playbook can be
performed directly by kubespray. In addtion, fix and enable the
topology-manager.sh test.
Issue-ID: MULTICLOUD-1324
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: Iee2197c1fc3e35288796399cccff0d3ae0925a6c
|
|
The specific error is:
jq: error (at <stdin>:1232): null (null) cannot be parsed as a
number
Issue-ID: MULTICLOUD-1361
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: I1821e5002260cd65ac467756753e2a2ffa01a4ce
|
|
Issue-ID: MULTICLOUD-1360
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: Iac32b8a1551253302134ad34b829ea9aa578ff8e
|
|
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
|
|
Issue-ID: MULTICLOUD-1324
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: I90b33cd99c42017b50f3174b6f9033a861e11dd3
|
|
Specifying 'latest' as the docker_version without specifying a
compatible version of containerd can lead to package dependency
errors. Let kubespray select the versions to ensure consistency.
Also, installing docker from vagrant installer instead of letting
kubespray install it can lead to the same issues.
Issue-ID: MULTICLOUD-1359
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: Iff41682fa0897fae8200e0f179137af844e314c0
|
|
The CAP_NET_RAW capability is not available with the default
PodSecurityPolicy. Create a service account and role binding to the
privileged policy and specify the sink to use it.
Issue-ID: MULTICLOUD-1310
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: Ib00ee1e8797d497d024a167fc9a0336d4c2a7ae1
|
|
Issue-ID: MULTICLOUD-1324
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: Ie913d3f26d039fae0bff98149ebe0a6e6dea2ebd
|
|
|
|
|
|
webhook
Issue-ID: MULTICLOUD-1320
Signed-off-by: Eric Adams <eric.adams@intel.com>
Change-Id: I9ef0bcde7c2ef22a04c32311d4571abc3b688ffe
|
|
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
|
|
|
|
Go reports a missing crypto/ed25519 module when running the vagrant
installer with KUD_PLUGIN_ENABLED. The package was introduced in go
1.13 (https://golang.org/doc/go1.13#crypto/ed25519).
Issue-ID: MULTICLOUD-1343
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: I2fdd06b67122506308038be0fe6b00a2e737f0f0
|
|
An example is provided with instructions on how to install the addons
with emcoctl. Addtionally, the containerized installer will populate
/opt/kud/addons and /opt/kud/multi-cluster/$CLUSTER_NAME/artifacts
with the files and instructions necessary as well.
Issue-ID: MULTICLOUD-1324
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: I74de1c9d18a0aaec4a96e38684ec80f00ab0b940
|
|
|
|
|
|
|
|
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
|
|
|
|
|
|
|
|
|
|
The policy is changed to Background operation
which is default for helm application. Later
on dedicated parametr will be added to the profile
to let it be changed for particular helm chart.
Issue-ID: MULTICLOUD-1338
Signed-off-by: Lukasz Rajewski <lukasz.rajewski@orange.com>
Change-Id: I29978bc39fe6e1d10b0278fe10736ff1b7cc2006
|
|
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
|
|
Issue-ID: MULTICLOUD-1324
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: I42eed23905c848e5ea1ea829a129215817394448
|
|
This change also installs emcoctl in the artifacts directory, similar
to what is done for kubectl by kubespray.
Issue-ID: MULTICLOUD-1324
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: I8447210487578ceeef61afc7c3e4d97905303c8a
|
|
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Issue-ID: MULTICLOUD-1335
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: I83336983475bab25867c44153657d31b1bacb933
|
|
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
|
|
Issue-ID: MULTICLOUD-1324
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: I0c1d43de8506233eb62bde52641bb7fc95b422fc
|
|
|
|
|
|
Issue-ID: MULTICLOUD-1336
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: I7a0ee4302c020e6b7ec785d6a85af636b6a85ecc
|
|
|
|
Updated image tag to 0.9.0-SNAPSHOT
Issue-ID: MULTICLOUD-1294
Signed-off-by: Konrad Bańka <k.banka@samsung.com>
Change-Id: I052726df7d7fd7c58e39e157adb104db7d68a048
|