-
Notifications
You must be signed in to change notification settings - Fork 1.3k
systemvmtemplate: use latest LTS kernel from buster-ports #5073
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Use the latest v5.10 Linux kernel (LTS) from buster-ports Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com> (cherry picked from commit 2dd1650276e7fa31fc3b920b67be8396647c279d) Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>
|
@rhtyd good. |
|
@weizhouapache I think it would be too much maintenance work for gain to maintain separate systemvmtemplate for each hypervisor. These days users can download 100MBs more in few extra seconds. |
| apt-get autoclean | ||
| apt-get clean | ||
| reboot | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rhtyd might 'reboot' be an issue in packer processing ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No see template.json
|
|
||
| function configure_grub() { | ||
| # Remove old kernel | ||
| apt-get remove -y --purge linux-image-amd64 linux-image-4.19.0-16-amd64 || true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rhtyd two potential issues in my opinion
(1) the versions are different in debian releases (debian 10.9.0: kernel 4.19.0.16.debian 10.8.0: kernel 4.19.0.14,etc)
(2) might there be more than 2 versions ? for example, one new kernel by apt-get -q -y dist-upgrade, another new kernel by apt-get -q -y dist-upgrade -t buster-backports ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, we can explore some general way of removing kernels that are not in use.
@rhtyd yes, agree. let's use same template for hypervisors. |
| "scripts/apt_upgrade.sh", | ||
| "scripts/apt_upgrade.sh" | ||
| ], | ||
| "expect_disconnect": true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@weizhouapache this handles for reboot case. You can read more about it here https://www.packer.io/docs/provisioners/shell
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rhtyd good. thanks for the info.
|
|
||
| function configure_grub() { | ||
| # Remove old kernel | ||
| apt-get remove -y --purge linux-image-amd64 linux-image-4* || true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@weizhouapache would this help, essentially saying remove all the old 4.x kernels. As the new/LTS Linux kernel are in the 5.x series - https://www.kernel.org/category/releases.html
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rhtyd ok, I will test it.
|
Is this good to be merged @weizhouapache @Pearl1594 |
weizhouapache
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rhtyd yes, it is good to me.
Will we wait for debian 11 which is planned to be released in July ?
|
@weizhouapache yes we should update to Debian 11 if/when it comes before 4.16. In the meanwhile we can use the same Linux kernel backport same as Debian 11. |
@rhtyd ok, let's merge it when Pearl approves. the codename of debian11 is 'Bullseye', cool. |
|
@blueorangutan package |
|
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔️ centos7 ✔️ centos8 ✔️ debian. SL-JID 264 |
Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>
| [[ -f /bin/vhd-util ]] && return | ||
|
|
||
| wget --no-check-certificate https://github.com/shapeblue/cloudstack-nonoss/raw/master/vhd-util -O /bin/vhd-util | ||
| wget --no-check-certificate https://github.com/shapeblue/cloudstack-nonoss/raw/main/vhd-util -O /bin/vhd-util |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
jfyi @sureshanaparti - fixed this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
noted, thanks @rhtyd
|
@blueorangutan test matrix |
|
@rhtyd a Trillian-Jenkins matrix job (centos7 mgmt + xs71, centos7 mgmt + vmware65, centos7 mgmt + kvmcentos7) has been kicked to run smoke tests |
|
@blueorangutan test matrix |
|
@rhtyd a Trillian-Jenkins matrix job (centos7 mgmt + xs71, centos7 mgmt + vmware65, centos7 mgmt + kvmcentos7) has been kicked to run smoke tests |
|
Trillian test result (tid-985)
|
|
Trillian test result (tid-988)
|
|
@rhtyd good. are you going to build new systemvm template and upload to download.cloudstack.org ? |
|
@weizhouapache the current 4.16 systemvmtemplate from this PR has been already on download.cloudstack.org for weeks now, all PRs being tested against that systemvmtemplate |
@rhtyd nice, good to know. thanks |
Use the latest v5.10 Linux kernel (LTS) from buster-ports and fixes systemvmtemplate build issue on
mainbranch.Signed-off-by: Rohit Yadav rohit.yadav@shapeblue.com