github: add support for building kata-static-tarball for ppc64le #5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Make check gives us an "error: comparison to empty slice". Fixes kata-containers#8343 Signed-off-by: Beraldo Leal <[email protected]>
make check is giving us the following error: error: this expression creates a reference which is immediately dereferenced by the compiler. Fixes kata-containers#8344 Signed-off-by: Beraldo Leal <[email protected]>
This is to add a workflow for internal nightly tests for s390x in Jenkins. Fixes: kata-containers#7986 Signed-off-by: Hyounggyu Choi <[email protected]>
Introduce the `update_device` trait in Hypervisor to enable device updates for VMMs.This trait will initially be utilized for virtiofs Mount operations. Fixes: kata-containers#7915 Signed-off-by: alex.lyn <[email protected]>
With this change, we give the users the change to try kata-containers with their own pre-built tarball. This will become very useful in the CI context, as we won't be downloading a specific version of kata-containers, but rather installing whatever was built in previous steps of the CI pipeline. Fixes: kata-containers#8438 Signed-off-by: Fabiano Fidêncio <[email protected]>
This was added as part of d4d65be, but install_kata has never actually used the passed enable_debug var. With this in mind, let's just remove it. Signed-off-by: Fabiano Fidêncio <[email protected]>
When a direct volume is used by multiple containers in Kata, Generating many shared paths with cids will cause IO error as the result of one direct volume mounts more than once. To correct it, use the device_id instead of cid which ensures that the guest only mounts the FS once. Fixes: kata-containers#8328 Signed-off-by: alex.lyn <[email protected]>
When multiple containers in a kata pod share one direct volume, it's important to make sure that the corresponding block device is only mounted once in the guest. This means that there should be only one mount entry for the device in the mount information. Fixes: kata-containers#8328 Signed-off-by: alex.lyn <[email protected]>
Amulyam24
force-pushed
the
workflow-1
branch
6 times, most recently
from
8a8d492
to
3e05efa
Compare
This PR enables the stressng scalability test for kata CI. Fixes kata-containers#8420 Signed-off-by: Gabriela Cervantes <[email protected]>
This PR adds missing dependencies to run stability tests. Signed-off-by: Gabriela Cervantes <[email protected]>
This PR adds the iperf udp information to the network README for the kata metrics CI. Fixes kata-containers#8452 Signed-off-by: Gabriela Cervantes <[email protected]>
This PR updates the stressng test to run on the gha for kata CI. Signed-off-by: Gabriela Cervantes <[email protected]>
Amulyam24
force-pushed
the
workflow-1
branch
2 times, most recently
from
d474e47
to
5e953dd
Compare
these tarballs are useful for debugging and re-running jobs, keep them for 15 days. Fixes: kata-containers#8000 Signed-off-by: Lukáš Doktor <[email protected]>
tests|gha: add nightly tests for s390x
Initial support of the MicroVM machine type of StratoVirt hypervisor for the kata go runtime. Fixes: kata-containers#7794 Signed-off-by: Liu Wenyuan <[email protected]>
Add support for building StratoVirt hypervisor, including x86_64 and arm64. Fixes: kata-containers#7794 Signed-off-by: Liu Wenyuan <[email protected]>
Add configuration-stratovirt.toml.in to generate the StratoVirt configuration, and parser to deliver config to StratoVirt. Fixes: kata-containers#7794 Signed-off-by: Liu Wenyuan <[email protected]>
Allow kata-deploy process to pull StratoVirt from release binaries, and add them as a part of kata release. Fixes: kata-containers#7794 Signed-off-by: Liu Wenyuan <[email protected]>
This commit enables StratoVirt hypervisor to be tested in kata GHA, incluing k8s, metrics, cri-containerd, nydus and so on. Meanwhile, adding some unit tests for StratoVirt to make sure it works. Fixes: kata-containers#7794 Signed-off-by: Liu Wenyuan <[email protected]>
gha: Keep kata tarballs for 15 days
tests: Enable stressng scalability test
metrics: Add iperf udp information to README
This patch adds a protobuf definiton of the remote hypervisor type. Signed-off-by: Yohei Ueda <[email protected]> Co-authored-by: stevenhorsman <[email protected]> (based on commit 150e8ab)
This patch adds the support of the remote hypervisor type. Shim opens a Unix domain socket specified in the config file, and sends TTPRC requests to a external process to control sandbox VMs. Fixes kata-containers#4482 Co-authored-by: Pradipta Banerjee <[email protected]> Co-authored-by: stevenhorsman <[email protected]> Signed-off-by: Yohei Ueda <[email protected]> (based on commit f9278f2)
This patch fixes the issue of running containers with privileged as true. See the discussion at this URL for the details. confidential-containers/cloud-api-adaptor#111 Signed-off-by: Lei Li <[email protected]> (based on commit c3e6b66)
Add the SELinux setting to ensure it is passed through to the remote hypervisor Fixes: kata-containers#5936 Signed-off-by: stevenhorsman <[email protected]> (based on commit 3ef2fd1)
- Remote hypervisor template config - Add annotation enablement for machine_type, default_memory and default_vcpus for flexible instance types Fixes: kata-containers#6349 Signed-off-by: stevenhorsman <[email protected]> (based on commits 7c9a791 and 335a456)
This patch updates the template configuration file for the remote hypervisor to set static_sandbox_resource_mgmt to be true. The remote hypervisor uses the peer pod config to determine the sandbox size, so requires this to be set to true by default. Fixes: kata-containers#6616 Signed-off-by: Yohei Ueda <[email protected]> (based on commit 9384478)
In order to support different pod VM instance type via remote hypervisor implementation (cloud-api-adaptor), we need to pass machine_type, default_vcpus and default_memory annotations to cloud-api-adaptor. The cloud-api-adaptor then uses these annotations to spin up the appropriate cloud instance. Reference PR for cloud-api-adaptor confidential-containers/cloud-api-adaptor#1088 Fixes: kata-containers#7140 Signed-off-by: Pradipta Banerjee <[email protected]> (based on commit 004f07f)
It's CCv0 specific for now, and it's needed as the Operator is now delegating the runtimeclass creation to the kata-deploy daemonset. Fixes: kata-containers#7550 Signed-off-by: Fabiano Fidêncio <[email protected]> (cherry picked from commit 2df6cb7)
- Add remote to the list of shims in kata-deploy and kata-cleanup Signed-off-by: stevenhorsman <[email protected]>
Fixes make check errors
Add the corresponding data structure in the runtime part according to kata-containers/pull/7698. Fixes: kata-containers#8472 Signed-off-by: ChengyuZhu6 <[email protected]>
The changes are: - VirtIoError -> VirtioError - VirtIoResult -> VirtioResult - VirtIoDevice -> VirtioDevice Fixes: kata-containers#8464 Signed-off-by: Xuewei Niu <[email protected]>
In order to support PCI VFIO functionality in Dragonball, we should first add PCI bus and PCI device Interrupt information in Dragonball mptable setup process. This patch add : 1. pci_legacy_irqs transfered to setup_mptable function. 2. pci bus support in mptable mem 3. pci interrupt support in mptable mem fixes: kata-containers#8449 Signed-off-by: Chao Wu <[email protected]>
1. merge hashmap get logic according to Xuewei suggestion. 2. do cargo fmt Signed-off-by: Chao Wu <[email protected]>
As a follow-up PR for kata-containers#8404, this is to set a default value for an environment variable `ALLOWED_HYPERVISOR_ANNOTATIONS`. This will prevent a pod launching without an explicit configuration for the variable from getting into a `CrashLoop` state. Fixes: kata-containers#8477 Signed-off-by: Hyounggyu Choi <[email protected]>
…l-multicontainers runitme-rs/bugfix: kata pod with multi-containers sharing one direct volume
It mainly focus on the two parts: (1) redesign the ShareFsConfig with ShareFsMountConfig The device mount operation must depend on the fact that sharefs device exists, and re-design the structure of SharesFsConfig and move the ShareFsMountConfig into it with Option type, which is to describe the relation between ShareFsConfig and ShareFsMountConfig. (2) move virtiofs into device manager Currently, virtio-fs is still outside of the device manager. To do Enhancement of device manager, it will bring virtio-fs device in device-manager for unified management Fixes: kata-containers#7915 Signed-off-by: alex.lyn <[email protected]>
Fixes: kata-containers#7915 Signed-off-by: alex.lyn <[email protected]>
…wed_hypervisor_annotations kata-deploy: Set a default value for ALLOWED_HYPERVISOR_ANNOTATIONS
dragonball: Uniform the spelling of Virtio
…ervisor-cherry-picks CC: Remote hypervisor merge to main
…ger-install-a-given-kata-tarball utils: kata-manager: Allow installing kata from a given tarball
…-volume runtime: Introduce `KataVirtualVolume` structure into go runtime
…n-dm runtime-rs: bringing virtio-fs device in device-manager
- statically linked qemu requires slof.bin to run, hence remove it from blacklist - By default, initrd is used for Power, modify the configuration.toml accordingly Fixes: kata-containers#8458 Signed-off-by: Amulyam24 <[email protected]>
Since the release is not yet out for ppc64le, build oras from source and use it. Fixes: kata-containers#8458 Signed-off-by: Amulyam24 <[email protected]>
…pc64le Adds workflows for building kata static tarball and releasing it. Fixes: kata-containers#8458 Signed-off-by: Amulyam24 <[email protected]>
Amulyam24
force-pushed
the
workflow-1
branch
from
5e953dd
to
0c894b0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.