[Starlingx-discuss] 3. Re: Migrate Starling X kernel patches to LTS kernel (Saul Wold)
Cordoba Malibran, Erich
erich.cordoba.malibran at intel.com
Fri Nov 23 16:21:56 UTC 2018
I think is a good approach to migrate to LTS kernel, however just keep
in mind that isn't just a patch rebase effort. We've seen virtual
networking losses only because the upgrade of kernel (on CentOs 7.5)
and a patch DPDK was needed. So, it is possible to find this kind of
surprises that could result in a chain of needed upgrades.
We need to define a proper testing scope to know in which parts put
more attention in the upgrade.
On Thu, 2018-11-22 at 08:02 -0800, Saul Wold wrote:
>
> On 11/22/18 7:06 AM, Einarsson, Jim wrote:
> > Saul,
> > We have no objections to your investigation of a kernel up version,
> > but the forklift may be heavier than you realize. Certainly
> > considerable work needs to be done to validate both functionality
> > and performance aspects. I assume the investigation will happen in
> > a sandbox side stream, to avoid disruption to the main branch. I
> > highly recommend a spec be created and reviewed, to make sure all
> > the necessary angles of the investigation are covered.
> >
>
> Exactly, we need to start this work for the Clear port we are
> currently
> doing and it will also need to be done as part of the Multi-OS
> effort
> since Ubuntu has a newer kernel.
>
> I am not proposing this happen on CentOS / master at this time, we
> know
> there is a large amount of work the forklift the patches, that work
> is
> already started against the 4.19 LTS kernel internally at Intel.
>
> We will work on a spec and address testing of the kernel.
>
> Sau!
>
>
> > JimE.
> >
> > Message: 3
> > Date: Wed, 21 Nov 2018 09:10:47 -0800
> > From: Saul Wold <sgw at linux.intel.com>
> > To: Victor Rodriguez <vm.rod25 at gmail.com>, Brent.Rowsell at windriver.
> > com
> > Cc: starlingx-discuss at lists.starlingx.io
> > Subject: Re: [Starlingx-discuss] Migrate Starling X kernel patches
> > to
> > LTS kernel
> > Message-ID: <b2bea0e0-c0c8-e57b-91d1-00a76da9c512 at linux.intel.com>
> > Content-Type: text/plain; charset=utf-8; format=flowed
> >
> > Victor, Brent:
> >
> > There are a couple of things not mentioned that I have heard talked
> > about on both sides of this discussion.
> >
> > My understanding is that the kernel version is based on the
> > RHEL/CentOS
> > version as it's a known tested combination at the Distro level,
> > even
> > though there are patches to the kernel and user-space.
> >
> > On the other side, the 3.10 RHEL kernel (with all the RHEL patches)
> > may
> > not address all the known CVEs, so there is a concern about overall
> > security. Intel is looking at the newer kernel and porting the
> > StarlingX patches (as needed) for the Clear and Multi-OS parts of
> > the
> > project.
> >
> > The overall question becomes can StarlingX take the 4.19LTS kernel
> > as a
> > newer base kernel for the project, it reduces the overall patch
> > load and
> > address some security issues.
> >
> > I believe you understand these objectives.
> >
> > Sau!
> >
> > -----Original Message-----
> > From: starlingx-discuss-request at lists.starlingx.io [mailto:starling
> > x-discuss-request at lists.starlingx.io]
> > Sent: Wednesday, November 21, 2018 4:37 PM
> > To: starlingx-discuss at lists.starlingx.io
> > Subject: Starlingx-discuss Digest, Vol 6, Issue 70
> >
> > Send Starlingx-discuss mailing list submissions to
> > starlingx-discuss at lists.starlingx.io
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-di
> > scuss
> > or, via email, send a message with subject or body 'help' to
> > starlingx-discuss-request at lists.starlingx.io
> >
> > You can reach the person managing the list at
> > starlingx-discuss-owner at lists.starlingx.io
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of Starlingx-discuss digest..."
> >
> >
> > Today's Topics:
> >
> > 1. StarlingX mini-PTG Jan 15-16 in Phoenix (Jones, Bruce E)
> > 2. Re: stx-tools: document isn't aligned with code
> > (Arevalo, Mario Alfredo C)
> > 3. Re: Migrate Starling X kernel patches to LTS kernel (Saul
> > Wold)
> > 4. Re: Migrate Starling X kernel patches to LTS kernel
> > (Rowsell, Brent)
> > 5. [build][meetings]Agenda for Build team meeting 11/22/
> > 2018
> > (Lara, Cesar)
> >
> >
> > -----------------------------------------------------------------
> > -----
> >
> > Message: 1
> > Date: Wed, 21 Nov 2018 16:26:43 +0000
> > From: "Jones, Bruce E" <bruce.e.jones at intel.com>
> > To: "starlingx-discuss at lists.starlingx.io"
> > <starlingx-discuss at lists.starlingx.io>
> > Subject: [Starlingx-discuss] StarlingX mini-PTG Jan 15-16 in
> > Phoenix
> > Message-ID:
> > <9A85D2917C58154C960D95352B22818BB1EB0050 at fmsmsx115.amr.corp.in
> > tel.com>
> >
> > Content-Type: text/plain; charset="utf-8"
> >
> > We are thinking about holding a StarlingX mini-PTG meeting in
> > January in Phoenix, to be hosted on the Intel campus.
> >
> > I'd like to get an early headcount and make sure there are no
> > conflicts for the dates. Please reply to this email and let me
> > know if you can/want to attend, or if you would like to attend but
> > have a conflict for these dates.
> >
> > Thank you!
> >
> > brucej
> >
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> > URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachm
> > ents/20181121/daa8ea1b/attachment-0001.html>
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Wed, 21 Nov 2018 16:55:39 +0000
> > From: "Arevalo, Mario Alfredo C" <mario.alfredo.c.arevalo at intel.com
> > >
> > To: "Arce Moreno, Abraham" <abraham.arce.moreno at intel.com>, "Liu,
> > Changcheng" <changcheng.liu at intel.com>,
> > "starlingx-discuss at lists.starlingx.io"
> > <starlingx-discuss at lists.starlingx.io>
> > Subject: Re: [Starlingx-discuss] stx-tools: document isn't aligned
> > with code
> > Message-ID:
> > <6594B51DBE477C48AAE23675314E6C466451F8E3 at fmsmsx107.amr.corp.in
> > tel.com>
> >
> > Content-Type: text/plain; charset="Windows-1252"
> >
> > Hi Changcheng and Abraham,
> >
> > I have sent a new version in order to update the documentation
> > according
> > to the new changes in Dockerfile[s]. You can take a look in this
> > link:
> >
> > https://review.openstack.org/#/c/601308/
> >
> > sorry for any inconvenience.
> >
> > Best regards.
> > Mario.
> > ________________________________________
> > From: Arce Moreno, Abraham
> > Sent: Wednesday, November 21, 2018 7:35 AM
> > To: Liu, Changcheng; starlingx-discuss at lists.starlingx.io; Arevalo,
> > Mario Alfredo C
> > Subject: RE: stx-tools: document isn't aligned with code
> >
> > Hi again Changcheng,
> >
> > > I’m following below document to create-starlingx-packages. It’s
> > > not
> > > aligned with latest code.
> >
> > You are right...
> >
> > > https://docs.starlingx.io/developer_guide/index.html#create-
> > > starlingx-packages
> > > <https://docs.starlingx.io/developer_guide/index.html#create-star
> > > lingx-
> > > packages>
> > > Could the man, who’s responsible for continuous-integration,
> > > clean the
> > > document and make it more clear?
> >
> > Under this review we will include the changes to align with Mario's
> > cleanup:
> > [Developer Guide] Setup Building Docker Container [0]
> >
> > The logic behind to accommodate the new "Developer Guide" flow
> > proposal
> > would look like:
> >
> > FYI "..." means content is not intended to be changed.
> >
> > - Requirements
> > - ...
> > - Development Environment Setup
> > - ...
> > - Prepare the Base Docker Image
> > - Configuration
> > - Sample localrc
> > - Build Base Docker Image
> > - Build the CentOS Mirror Repository
> > - Run Mirror Docker Container
> > - Download Packages
> > - Verify Packages
> > - Packages Structure
> > - Create CentOS Mirror Repository
> > - Create StarlingX Packages
> > - Run Building Docker Container
> > - Download Source Code Repositories
> > - Build Packages
> > - Build StarlingX ISO
> > - Build Installer
> > - ...
> > - Build Avoidance
> > - ...
> >
> > In summary, "flow proposal" could look like:
> >
> > - Prepare Base Docker Image
> > - Build "base image"
> > - Build the CentOS Mirror Repository
> > - Run container from "base image"
> > - Get mirror files
> > - Create StarlingX Packages
> > - Run container from "base image"
> > - Get StarlingX source code
> > - Build StarlingX packages
> > - Build StarlingX ISO
> >
> > > 1. The stx-tools code isn’t aligned with the above document
> > > since base-
> > > build/build target has been removed.
> > > 2. Besides this, README.rst is not updated in time when
> > > the build rule
> > > has been changed.
> >
> > README.rst from stx-tools project is going under a review process
> > [1] so please
> > feel free to leave your comments.
> >
> > [0] https://review.openstack.org/#/c/619043/
> > [1] https://review.openstack.org/#/c/601308/
> >
> >
> >
> > ------------------------------
> >
> > Message: 3
> > Date: Wed, 21 Nov 2018 09:10:47 -0800
> > From: Saul Wold <sgw at linux.intel.com>
> > To: Victor Rodriguez <vm.rod25 at gmail.com>, Brent.Rowsell at windriver.
> > com
> > Cc: starlingx-discuss at lists.starlingx.io
> > Subject: Re: [Starlingx-discuss] Migrate Starling X kernel patches
> > to
> > LTS kernel
> > Message-ID: <b2bea0e0-c0c8-e57b-91d1-00a76da9c512 at linux.intel.com>
> > Content-Type: text/plain; charset=utf-8; format=flowed
> >
> > Victor, Brent:
> >
> > There are a couple of things not mentioned that I have heard talked
> > about on both sides of this discussion.
> >
> > My understanding is that the kernel version is based on the
> > RHEL/CentOS
> > version as it's a known tested combination at the Distro level,
> > even
> > though there are patches to the kernel and user-space.
> >
> > On the other side, the 3.10 RHEL kernel (with all the RHEL patches)
> > may
> > not address all the known CVEs, so there is a concern about overall
> > security. Intel is looking at the newer kernel and porting the
> > StarlingX patches (as needed) for the Clear and Multi-OS parts of
> > the
> > project.
> >
> > The overall question becomes can StarlingX take the 4.19LTS kernel
> > as a
> > newer base kernel for the project, it reduces the overall patch
> > load and
> > address some security issues.
> >
> > I believe you understand these objectives.
> >
> > Sau!
> >
> >
> > On 11/20/18 6:42 PM, Victor Rodriguez wrote:
> > > On Tue, Nov 20, 2018 at 8:25 PM Rowsell, Brent
> > > <Brent.Rowsell at windriver.com> wrote:
> > > >
> > > > There are two kernels, standard and rt.
> > > > Both are centos 7.5 based with a small set of patches applied
> > > > on top along with modified kernel config options.
> > > >
> > >
> > > Thanks for the clarification
> > >
> > > > Not quite understanding what you are asking. Are you proposing
> > > > to replace the kernel in the starlingX project or just in your
> > > > local environment ?
> > >
> > > For my local environment. I would not like to use CentOS kernel
> > > 3.10
> > > but instead LTS 4.19
> > >
> > > > What is the objective here ?
> > >
> > > To have a more stable and secure kernel on my production system,
> > > there
> > > are security fixes that would like to have on my kernel that LTS
> > > provides
> > >
> > > I know RHEL/CentOS is based on kernel 3.10 but other OSs are ot
> > > like
> > > ubuntu/debian/fedora
> > >
> > > Regards
> > >
> > > >
> > > > Brent
> > > >
> > > > -----Original Message-----
> > > > From: Victor Rodriguez [mailto:vm.rod25 at gmail.com]
> > > > Sent: Tuesday, November 20, 2018 9:20 PM
> > > > To: starlingx-discuss at lists.starlingx.io
> > > > Subject: [Starlingx-discuss] Migrate Starling X kernel patches
> > > > to LTS kernel
> > > >
> > > > Hi team
> > > >
> > > > I am a new user/developer of starling X and after searching
> > > > into the kernel metapatches at:
> > > >
> > > > https://git.starlingx.io/cgit/stx-integ/tree/kernel
> > > >
> > > > Some questions came to me :
> > > >
> > > > As far as I can see we are under kernel 3.10 from RHEL RT fork
> > > > right?
> > > > There are some ( actually many ) security and functional
> > > > changes that exist in the LTS kernel ( like 4.19 as an
> > > > example), because of that I would like to use a more stable
> > > > kernel into my starling x system
> > > >
> > > > Is there any specific reason why use that specific for from
> > > > RHEL?
> > > >
> > > > What does starling X think about the migration of these patches
> > > > ( some of them are already applied into the latest versions of
> > > > Linux Kernel)?
> > > >
> > > > What kind of test should I perform to check that my vanilla
> > > > kernel + STX patches work as expected?
> > > >
> > > > All feedback is more than welcome
> > > >
> > > > BTW thanks to Mario and Saul for the help on understand more
> > > > these patches
> > > >
> > > > Regards
> > > >
> > > > Victor Rodriguez
> > > >
> > > > _______________________________________________
> > > > Starlingx-discuss mailing list
> > > > Starlingx-discuss at lists.starlingx.io
> > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-di
> > > > scuss
> > >
> > > _______________________________________________
> > > Starlingx-discuss mailing list
> > > Starlingx-discuss at lists.starlingx.io
> > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-disc
> > > uss
> > >
> >
> >
> >
> > ------------------------------
> >
> > Message: 4
> > Date: Wed, 21 Nov 2018 17:21:49 +0000
> > From: "Rowsell, Brent" <Brent.Rowsell at windriver.com>
> > To: Saul Wold <sgw at linux.intel.com>, Victor Rodriguez
> > <vm.rod25 at gmail.com>
> > Cc: "starlingx-discuss at lists.starlingx.io"
> > <starlingx-discuss at lists.starlingx.io>
> > Subject: Re: [Starlingx-discuss] Migrate Starling X kernel patches
> > to
> > LTS kernel
> > Message-ID:
> > <2588653EBDFFA34B982FAF00F1B4844EBB31A592 at ALA-MBD.corp.ad.wrs.c
> > om>
> > Content-Type: text/plain; charset="utf-8"
> >
> > Saul,
> >
> > This is a big change. I suggest adding it to the next TSC call.
> >
> >
> > Brent
> >
> > -----Original Message-----
> > From: Saul Wold [mailto:sgw at linux.intel.com]
> > Sent: Wednesday, November 21, 2018 12:11 PM
> > To: Victor Rodriguez <vm.rod25 at gmail.com>; Rowsell, Brent <Brent.Ro
> > wsell at windriver.com>
> > Cc: starlingx-discuss at lists.starlingx.io
> > Subject: Re: [Starlingx-discuss] Migrate Starling X kernel patches
> > to LTS kernel
> >
> > Victor, Brent:
> >
> > There are a couple of things not mentioned that I have heard talked
> > about on both sides of this discussion.
> >
> > My understanding is that the kernel version is based on the
> > RHEL/CentOS version as it's a known tested combination at the
> > Distro level, even though there are patches to the kernel and user-
> > space.
> >
> > On the other side, the 3.10 RHEL kernel (with all the RHEL patches)
> > may not address all the known CVEs, so there is a concern about
> > overall security. Intel is looking at the newer kernel and porting
> > the StarlingX patches (as needed) for the Clear and Multi-OS parts
> > of the project.
> >
> > The overall question becomes can StarlingX take the 4.19LTS kernel
> > as a newer base kernel for the project, it reduces the overall
> > patch load and address some security issues.
> >
> > I believe you understand these objectives.
> >
> > Sau!
> >
> >
> > On 11/20/18 6:42 PM, Victor Rodriguez wrote:
> > > On Tue, Nov 20, 2018 at 8:25 PM Rowsell, Brent
> > > <Brent.Rowsell at windriver.com> wrote:
> > > >
> > > > There are two kernels, standard and rt.
> > > > Both are centos 7.5 based with a small set of patches applied
> > > > on top along with modified kernel config options.
> > > >
> > >
> > > Thanks for the clarification
> > >
> > > > Not quite understanding what you are asking. Are you proposing
> > > > to replace the kernel in the starlingX project or just in your
> > > > local environment ?
> > >
> > > For my local environment. I would not like to use CentOS kernel
> > > 3.10
> > > but instead LTS 4.19
> > >
> > > > What is the objective here ?
> > >
> > > To have a more stable and secure kernel on my production system,
> > > there
> > > are security fixes that would like to have on my kernel that LTS
> > > provides
> > >
> > > I know RHEL/CentOS is based on kernel 3.10 but other OSs are ot
> > > like
> > > ubuntu/debian/fedora
> > >
> > > Regards
> > >
> > > >
> > > > Brent
> > > >
> > > > -----Original Message-----
> > > > From: Victor Rodriguez [mailto:vm.rod25 at gmail.com]
> > > > Sent: Tuesday, November 20, 2018 9:20 PM
> > > > To: starlingx-discuss at lists.starlingx.io
> > > > Subject: [Starlingx-discuss] Migrate Starling X kernel patches
> > > > to LTS
> > > > kernel
> > > >
> > > > Hi team
> > > >
> > > > I am a new user/developer of starling X and after searching
> > > > into the kernel metapatches at:
> > > >
> > > > https://git.starlingx.io/cgit/stx-integ/tree/kernel
> > > >
> > > > Some questions came to me :
> > > >
> > > > As far as I can see we are under kernel 3.10 from RHEL RT fork
> > > > right?
> > > > There are some ( actually many ) security and functional
> > > > changes that
> > > > exist in the LTS kernel ( like 4.19 as an example), because of
> > > > that I
> > > > would like to use a more stable kernel into my starling x
> > > > system
> > > >
> > > > Is there any specific reason why use that specific for from
> > > > RHEL?
> > > >
> > > > What does starling X think about the migration of these patches
> > > > ( some of them are already applied into the latest versions of
> > > > Linux Kernel)?
> > > >
> > > > What kind of test should I perform to check that my vanilla
> > > > kernel + STX patches work as expected?
> > > >
> > > > All feedback is more than welcome
> > > >
> > > > BTW thanks to Mario and Saul for the help on understand more
> > > > these
> > > > patches
> > > >
> > > > Regards
> > > >
> > > > Victor Rodriguez
> > > >
> > > > _______________________________________________
> > > > Starlingx-discuss mailing list
> > > > Starlingx-discuss at lists.starlingx.io
> > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-di
> > > > scuss
> > >
> > > _______________________________________________
> > > Starlingx-discuss mailing list
> > > Starlingx-discuss at lists.starlingx.io
> > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-disc
> > > uss
> > >
> >
> > ------------------------------
> >
> > Message: 5
> > Date: Wed, 21 Nov 2018 21:36:29 +0000
> > From: "Lara, Cesar" <cesar.lara at intel.com>
> > To: "starlingx-discuss at lists.starlingx.io"
> > <starlingx-discuss at lists.starlingx.io>
> > Subject: [Starlingx-discuss] [build][meetings]Agenda for Build team
> > meeting 11/22/2018
> > Message-ID:
> > <0B566C62EC792145B40E29EFEBF1AB471056AB69 at fmsmsx104.amr.corp.in
> > tel.com>
> >
> > Content-Type: text/plain; charset="utf-8"
> >
> > Build team meeting 11/22/2018
> >
> > Agenda
> > - Cengn follow up - Ken
> > - Mirror script refactor - Marcela
> > - Build team Imperatives for next release
> >
> > Most of us are in non-holiday areas, please let me know if there is
> > a showstopper to host this meeting without people from USA
> >
> >
> > Regards
> >
> > Cesar Lara
> > Software Engineering Manager
> > OpenSource Technology Center
> >
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> > URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachm
> > ents/20181121/8805e005/attachment.html>
> >
> > ------------------------------
> >
> > Subject: Digest Footer
> >
> > _______________________________________________
> > Starlingx-discuss mailing list
> > Starlingx-discuss at lists.starlingx.io
> > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus
> > s
> >
> >
> > ------------------------------
> >
> > End of Starlingx-discuss Digest, Vol 6, Issue 70
> > ************************************************
> > _______________________________________________
> > Starlingx-discuss mailing list
> > Starlingx-discuss at lists.starlingx.io
> > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus
> > s
> >
>
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
More information about the Starlingx-discuss
mailing list