Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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
|
|
|
|
Signed-off-by: Konrad Bańka <k.banka@samsung.com>
Issue-ID: MULTICLOUD-1307
Issue-ID: MULTICLOUD-1308
Issue-ID: MULTICLOUD-1311
Change-Id: I4645cc1dd9c8e6dfcf2a5c27dddf09e4c8de5e5c
|
|
Moving to Helm v3. Updated unit tests.
Reworked Healthcheck Execution to align
with v3 design.
Helm v3 requires newer version for K8s
libraries. Moved to use version 0.19.4.
Issue-ID: MULTICLOUD-1295
Signed-off-by: Ritu Sood <ritu.sood@intel.com>
Signed-off-by: Konrad Bańka <k.banka@samsung.com>
Change-Id: I091b75d69841dde56ad2c294cca2d5a0291ffa8f
|
|
- 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
|
|
Update image version of k8splugin to 0.8.1-SNAPSHOT
Issue-ID: MULTICLOUD-1294
Signed-off-by: Lukasz Rajewski <lukasz.rajewski@orange.com>
Change-Id: I009da40eec82ad7fddb22018935928a62451c768
|
|
Issue-ID: MULTICLOUD-1324
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: I90a9cf23a8fb01cbc579d2b6670b476494c2a7bb
|
|
|
|
Fix several issues related to Healthcheck creation.
Updated GET/DELETE methods to work properly.
This commit leaves few FIXME/TODOs that will be handled within Helm3
Rebase commit
Issue-ID: MULTICLOUD-1308
Signed-off-by: Konrad Bańka <k.banka@samsung.com>
Change-Id: I5da50363bb240fdc85d3624f43cb0526786da542
|
|
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
|
|
Issue-ID: MULTICLOUD-1323
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: Iac2046b6df4f76efc7f7745567740fffb9b8e72a
|
|
This fixes the following error when running ./setup.sh -p libvirt:
usermod: group 'libvirtd' does not exist
Newer versions of Ubuntu appear to have renamed the libvirtd group to
libvirt.
Issue-ID: MULTICLOUD-1322
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: I54ffc4558cb8945e8c9f9ca751518b20a6de64d0
|
|
This fixes the following error when running ./setup.sh -p libvirt:
Installing the 'vagrant-libvirt' plugin. This can take a few minutes...
Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:
nokogiri requires Ruby version < 3.1.dev, >= 2.5.
Issue-ID: MULTICLOUD-1321
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: Ia867df9df3ec1cc27e2f17df4a72ffc88f6bdf44
|
|
|
|
Modified day2 config template handler to return metadata of created
configuration template on its creation.
Issue-ID: MULTICLOUD-1311
Signed-off-by: Konrad Bańka <k.banka@samsung.com>
Change-Id: I139486a41c7dbd67d414a07776e9a5d711d9887b
|
|
Addition of hooks in instantiation response needs to be handled by other
parties or else it may break connectivity. Because currently Hooks
field doesn't provide any relevant public data, this change makes it
hidden.
Issue-ID: MULTICLOUD-1311
Signed-off-by: Konrad Bańka <k.banka@samsung.com>
Change-Id: I4ca522cf8c6409ddf71fe06de0b905cfdf219a2f
|
|
|
|
|