Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

Set version baseline for all components #160

Closed
WeiZhang555 opened this issue Aug 29, 2018 · 2 comments
Closed

Set version baseline for all components #160

WeiZhang555 opened this issue Aug 29, 2018 · 2 comments

Comments

@WeiZhang555
Copy link
Member

1. Issue

Our kata-containers components are fast moving and we don't have configurations/docs for minimal working version of every components, everyone likes cool features from latest stable branch of kernel/qemu/crio/docker, but for absorbing more users and support more OS distribute, we should set a baseline version of each components including:

1.1 kernel

We only provide config for kernel 4.14, but I tried kernel 4.1 then find that user has to debug and modify the kernel config to make it work, so I suggest we also provide a kernel config for mininal supported kernel version which can be 3.10 or 4.1 or other, we need to discuss.

As docker/runc asks for kernel > 3.10 IIRC, I suppose 3.10 could be a good start version.

1.2 qemu

Same question, 2.6? 2.7? 2.8?

1.3 crio, cri-containerd, docker, Kubernetes

Same question.

Q: are there other components need a baseline?

2. How

First we need a config, or configuration script, or simple document to make kata-containers work with oldest supported components version.

Second we need a Jenkins Job in CI to test backward compatibility for every PR to make sure it won't break the backward compatibility.

@jodh-intel
Copy link
Contributor

Hi @WeiZhang555 - agreed. We really need someone to step up and solve some of the complex issues we have around kernel configs imho.

Regarding versions, we've tried to capture everything relevant in the versions database:

1.1 kernel

$ yq read versions.yaml assets.kernel

1.2 qemu

$ yq read versions.yaml 'assets.hypervisor'

1.3 crio, cri-containerd, docker, Kubernetes

$ yq read versions.yaml externals

Since that file lives in the runtime repo and we need this for packaging, maybe it makes sense to create stable packaging branches to mirror the stable branches in the other repos? That way if you're using the stable-1.1 packaging branch, you can rely on the version details in the equivalent stable runtime repo branch:

/cc @egernst, @jcvenegas.

@WeiZhang555
Copy link
Member Author

@jodh-intel

$ yq read versions.yaml assets.kernel

That sounds smart! 👍

jcvenegas pushed a commit that referenced this issue Jul 2, 2019
Fixes: #160

Signed-off-by: Marco Vedovati <mvedovati@suse.com>
jcvenegas pushed a commit that referenced this issue Jul 2, 2019
Increase the build timeout to 50 minutes, this is required to allow more
distros to be built.

Fixes: #160

Signed-off-by: Marco Vedovati <mvedovati@suse.com>
@jodh-intel jodh-intel added this to To do in Issue backlog Aug 10, 2020
Issue backlog automation moved this from To do to Done Apr 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
Issue backlog
  
Done
Development

No branches or pull requests

2 participants