[Starlingx-discuss] CentOS 7.5 upgrade discussion
Brent, Saul, Shuicheng, Let's initiate the discussion about how we'd like to handle CentOS 7.5 upgrade, we have a master xls sheet online for all non-openStack patches analysis (@Saul, I only have Google doc link but not accessible by WR). And here is the SRPM files we've already looked into, and believe they need upgrade. I put some columns in to fill-in more data (Shuicheng should have most of the data available). We can start from here. Thx. - cindy
I think we can safely drop the "vim" modification. It has a long history back to where we were inheriting code customizations from another layer, which was providing its own customized vimrc that had features enabled that were frustrating. From: Xie, Cindy [mailto:cindy.xie@intel.com] Sent: Thursday, August 09, 2018 11:01 AM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] CentOS 7.5 upgrade discussion Brent, Saul, Shuicheng, Let's initiate the discussion about how we'd like to handle CentOS 7.5 upgrade, we have a master xls sheet online for all non-openStack patches analysis (@Saul, I only have Google doc link but not accessible by WR). And here is the SRPM files we've already looked into, and believe they need upgrade. I put some columns in to fill-in more data (Shuicheng should have most of the data available). We can start from here. Thx. - cindy
On 08/09/2018 08:17 AM, Penney, Don wrote:
I think we can safely drop the “vim” modification. It has a long history back to where we were inheriting code customizations from another layer, which was providing its own customized vimrc that had features enabled that were frustrating.
Yeah, +1 to that, thanks for the confirmation!
*From:*Xie, Cindy [mailto:cindy.xie@intel.com] *Sent:* Thursday, August 09, 2018 11:01 AM *To:* starlingx-discuss@lists.starlingx.io *Subject:* [Starlingx-discuss] CentOS 7.5 upgrade discussion
Brent, Saul, Shuicheng,
Let’s initiate the discussion about how we’d like to handle CentOS 7.5 upgrade, we have a master xls sheet online for all non-openStack patches analysis (@Saul, I only have Google doc link but not accessible by WR).
We should be able to provide a link to anyone that has a gmail account, I think (Bruce is that correct?)
And here is the SRPM files we’ve already looked into, and believe they need upgrade. I put some columns in to fill-in more data (Shuicheng should have most of the data available). We can start from here.
Can we please merge this into the existing master spreadsheet. We are going to continue to winnow down the list of patches and configuration from there. Sau!
Thx. - cindy
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
See below.... -----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Thursday, August 9, 2018 11:15 AM To: starlingx-discuss@lists.starlingx.io; Jones, Bruce E <bruce.e.jones@intel.com> Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade discussion On 08/09/2018 08:17 AM, Penney, Don wrote:
I think we can safely drop the "vim" modification. It has a long history back to where we were inheriting code customizations from another layer, which was providing its own customized vimrc that had features enabled that were frustrating.
Yeah, +1 to that, thanks for the confirmation! [brucej] Remember the process here is to create a SB Story for the changes needed to the code and the build to remove the patch, and put the link to the story in the spreadsheet. The distro.not-openstack team should do that.
*From:*Xie, Cindy [mailto:cindy.xie@intel.com] *Sent:* Thursday, August 09, 2018 11:01 AM *To:* starlingx-discuss@lists.starlingx.io *Subject:* [Starlingx-discuss] CentOS 7.5 upgrade discussion
Brent, Saul, Shuicheng,
Let's initiate the discussion about how we'd like to handle CentOS 7.5 upgrade, we have a master xls sheet online for all non-openStack patches analysis (@Saul, I only have Google doc link but not accessible by WR).
We should be able to provide a link to anyone that has a gmail account, I think (Bruce is that correct?) [brucej] Documents like this that are within the Intel Enterprise Google drive can be shared with anyone who has a gmail address.
And here is the SRPM files we've already looked into, and believe they need upgrade. I put some columns in to fill-in more data (Shuicheng should have most of the data available). We can start from here.
Can we please merge this into the existing master spreadsheet. We are going to continue to winnow down the list of patches and configuration from there. [brucej] +1! Sau!
Thx. - cindy
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Bruce, Please clarify " and the build to remove the patch" Brent -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones@intel.com] Sent: Thursday, August 9, 2018 2:37 PM To: Saul Wold <sgw@linux.intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade discussion See below.... -----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Thursday, August 9, 2018 11:15 AM To: starlingx-discuss@lists.starlingx.io; Jones, Bruce E <bruce.e.jones@intel.com> Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade discussion On 08/09/2018 08:17 AM, Penney, Don wrote:
I think we can safely drop the "vim" modification. It has a long history back to where we were inheriting code customizations from another layer, which was providing its own customized vimrc that had features enabled that were frustrating.
Yeah, +1 to that, thanks for the confirmation! [brucej] Remember the process here is to create a SB Story for the changes needed to the code and the build to remove the patch, and put the link to the story in the spreadsheet. The distro.not-openstack team should do that.
*From:*Xie, Cindy [mailto:cindy.xie@intel.com] *Sent:* Thursday, August 09, 2018 11:01 AM *To:* starlingx-discuss@lists.starlingx.io *Subject:* [Starlingx-discuss] CentOS 7.5 upgrade discussion
Brent, Saul, Shuicheng,
Let's initiate the discussion about how we'd like to handle CentOS 7.5 upgrade, we have a master xls sheet online for all non-openStack patches analysis (@Saul, I only have Google doc link but not accessible by WR).
We should be able to provide a link to anyone that has a gmail account, I think (Bruce is that correct?) [brucej] Documents like this that are within the Intel Enterprise Google drive can be shared with anyone who has a gmail address.
And here is the SRPM files we've already looked into, and believe they need upgrade. I put some columns in to fill-in more data (Shuicheng should have most of the data available). We can start from here.
Can we please merge this into the existing master spreadsheet. We are going to continue to winnow down the list of patches and configuration from there. [brucej] +1! Sau!
Thx. - cindy
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Hi Bruce, There is a story already for tracking the CentOS 7.5 upgrade. Shuicheng created it earlier (he's part of the Distro Non-Openstack team). https://storyboard.openstack.org/#!/story/2003389 Dealing with the vim patch (i.e. removing it) should be a task under this story. Regards, Ghada -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones@intel.com] Sent: Thursday, August 09, 2018 2:37 PM To: Saul Wold; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade discussion See below.... -----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Thursday, August 9, 2018 11:15 AM To: starlingx-discuss@lists.starlingx.io; Jones, Bruce E <bruce.e.jones@intel.com> Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade discussion On 08/09/2018 08:17 AM, Penney, Don wrote:
I think we can safely drop the "vim" modification. It has a long history back to where we were inheriting code customizations from another layer, which was providing its own customized vimrc that had features enabled that were frustrating.
Yeah, +1 to that, thanks for the confirmation! [brucej] Remember the process here is to create a SB Story for the changes needed to the code and the build to remove the patch, and put the link to the story in the spreadsheet. The distro.not-openstack team should do that.
*From:*Xie, Cindy [mailto:cindy.xie@intel.com] *Sent:* Thursday, August 09, 2018 11:01 AM *To:* starlingx-discuss@lists.starlingx.io *Subject:* [Starlingx-discuss] CentOS 7.5 upgrade discussion
Brent, Saul, Shuicheng,
Let's initiate the discussion about how we'd like to handle CentOS 7.5 upgrade, we have a master xls sheet online for all non-openStack patches analysis (@Saul, I only have Google doc link but not accessible by WR).
We should be able to provide a link to anyone that has a gmail account, I think (Bruce is that correct?) [brucej] Documents like this that are within the Intel Enterprise Google drive can be shared with anyone who has a gmail address.
And here is the SRPM files we've already looked into, and believe they need upgrade. I put some columns in to fill-in more data (Shuicheng should have most of the data available). We can start from here.
Can we please merge this into the existing master spreadsheet. We are going to continue to winnow down the list of patches and configuration from there. [brucej] +1! Sau!
Thx. - cindy
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
On 08/09/2018 11:44 AM, Khalil, Ghada wrote:
Hi Bruce, There is a story already for tracking the CentOS 7.5 upgrade. Shuicheng created it earlier (he's part of the Distro Non-Openstack team).
https://storyboard.openstack.org/#!/story/2003389
Dealing with the vim patch (i.e. removing it) should be a task under this story.
I thought we were doing 1 story / package, not 1 task / package? Can someone please clarify this, as I am also working on patches and they need stories or tasks. Sau!
Regards, Ghada
-----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones@intel.com] Sent: Thursday, August 09, 2018 2:37 PM To: Saul Wold; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade discussion
See below....
-----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Thursday, August 9, 2018 11:15 AM To: starlingx-discuss@lists.starlingx.io; Jones, Bruce E <bruce.e.jones@intel.com> Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade discussion
On 08/09/2018 08:17 AM, Penney, Don wrote:
I think we can safely drop the "vim" modification. It has a long history back to where we were inheriting code customizations from another layer, which was providing its own customized vimrc that had features enabled that were frustrating.
Yeah, +1 to that, thanks for the confirmation!
[brucej] Remember the process here is to create a SB Story for the changes needed to the code and the build to remove the patch, and put the link to the story in the spreadsheet. The distro.not-openstack team should do that.
*From:*Xie, Cindy [mailto:cindy.xie@intel.com] *Sent:* Thursday, August 09, 2018 11:01 AM *To:* starlingx-discuss@lists.starlingx.io *Subject:* [Starlingx-discuss] CentOS 7.5 upgrade discussion
Brent, Saul, Shuicheng,
Let's initiate the discussion about how we'd like to handle CentOS 7.5 upgrade, we have a master xls sheet online for all non-openStack patches analysis (@Saul, I only have Google doc link but not accessible by WR).
We should be able to provide a link to anyone that has a gmail account, I think (Bruce is that correct?)
[brucej] Documents like this that are within the Intel Enterprise Google drive can be shared with anyone who has a gmail address.
And here is the SRPM files we've already looked into, and believe they need upgrade. I put some columns in to fill-in more data (Shuicheng should have most of the data available). We can start from here.
Can we please merge this into the existing master spreadsheet. We are going to continue to winnow down the list of patches and configuration from there.
[brucej] +1!
Sau!
Thx. - cindy
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
On 08/09/2018 11:44 AM, Khalil, Ghada wrote:
Hi Bruce, There is a story already for tracking the CentOS 7.5 upgrade. Shuicheng created it earlier (he's part of the Distro Non-Openstack team).
https://storyboard.openstack.org/#!/story/2003389
Dealing with the vim patch (i.e. removing it) should be a task under this story.
I thought we were doing 1 story / package, not 1 task / package? Can someone please clarify this, as I am also working on patches and they need stories or tasks. [[GK]] Sorry Saul I didn't know about this decision as I was not part of the discussion. I personally feel if work items can be logically combined into one story with multiple tasks, that would be beneficial. It's a way to avoid story explosion. That being said, in the end, it's up to you and the sub-project team. If it makes more sense to have a story/package, that's fine as well. PS: I am a bit biased as I have been trying to tag the backlog, so the less stories the better for me. But that's a short term issue as each sub-project starts to tag their own. Ghada
Let's stick w/ one story we already have at this moment: https://storyboard.openstack.org/#!/story/2003389. I've already tagged as stx-distro.other. we need to target it at Oct's release, thus I am adding stx.2018.10 tag as well. Thx. - cindy -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil@windriver.com] Sent: Friday, August 10, 2018 4:13 AM To: Saul Wold <sgw@linux.intel.com>; Jones, Bruce E <bruce.e.jones@intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade discussion On 08/09/2018 11:44 AM, Khalil, Ghada wrote:
Hi Bruce, There is a story already for tracking the CentOS 7.5 upgrade. Shuicheng created it earlier (he's part of the Distro Non-Openstack team).
https://storyboard.openstack.org/#!/story/2003389
Dealing with the vim patch (i.e. removing it) should be a task under this story.
I thought we were doing 1 story / package, not 1 task / package? Can someone please clarify this, as I am also working on patches and they need stories or tasks. [[GK]] Sorry Saul I didn't know about this decision as I was not part of the discussion. I personally feel if work items can be logically combined into one story with multiple tasks, that would be beneficial. It's a way to avoid story explosion. That being said, in the end, it's up to you and the sub-project team. If it makes more sense to have a story/package, that's fine as well. PS: I am a bit biased as I have been trying to tag the backlog, so the less stories the better for me. But that's a short term issue as each sub-project starts to tag their own. Ghada _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Hi Don, I also was thinking drop the vim srpm. Thanks for the confirmation. Best Regards Shuicheng From: Penney, Don [mailto:Don.Penney@windriver.com] Sent: Thursday, August 9, 2018 11:17 PM To: Xie, Cindy <cindy.xie@intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade discussion I think we can safely drop the "vim" modification. It has a long history back to where we were inheriting code customizations from another layer, which was providing its own customized vimrc that had features enabled that were frustrating. From: Xie, Cindy [mailto:cindy.xie@intel.com] Sent: Thursday, August 09, 2018 11:01 AM To: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] CentOS 7.5 upgrade discussion Brent, Saul, Shuicheng, Let's initiate the discussion about how we'd like to handle CentOS 7.5 upgrade, we have a master xls sheet online for all non-openStack patches analysis (@Saul, I only have Google doc link but not accessible by WR). And here is the SRPM files we've already looked into, and believe they need upgrade. I put some columns in to fill-in more data (Shuicheng should have most of the data available). We can start from here. Thx. - cindy
There is a separate story created by Saul on this one: https://storyboard.openstack.org/#!/story/2003389 Please sync-up with Saul if he already has patch available or you want to create one. Thx. - cindy From: Lin, Shuicheng Sent: Friday, August 10, 2018 8:45 AM To: Penney, Don <Don.Penney@windriver.com>; Xie, Cindy <cindy.xie@intel.com>; starlingx-discuss@lists.starlingx.io Subject: RE: CentOS 7.5 upgrade discussion Hi Don, I also was thinking drop the vim srpm. Thanks for the confirmation. Best Regards Shuicheng From: Penney, Don [mailto:Don.Penney@windriver.com] Sent: Thursday, August 9, 2018 11:17 PM To: Xie, Cindy <cindy.xie@intel.com<mailto:cindy.xie@intel.com>>; starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade discussion I think we can safely drop the "vim" modification. It has a long history back to where we were inheriting code customizations from another layer, which was providing its own customized vimrc that had features enabled that were frustrating. From: Xie, Cindy [mailto:cindy.xie@intel.com] Sent: Thursday, August 09, 2018 11:01 AM To: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] CentOS 7.5 upgrade discussion Brent, Saul, Shuicheng, Let's initiate the discussion about how we'd like to handle CentOS 7.5 upgrade, we have a master xls sheet online for all non-openStack patches analysis (@Saul, I only have Google doc link but not accessible by WR). And here is the SRPM files we've already looked into, and believe they need upgrade. I put some columns in to fill-in more data (Shuicheng should have most of the data available). We can start from here. Thx. - cindy
Sorry wrong link: https://storyboard.openstack.org/#!/story/2003398 From: Xie, Cindy Sent: Friday, August 10, 2018 8:55 AM To: Lin, Shuicheng <shuicheng.lin@intel.com>; Penney, Don <Don.Penney@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: RE: CentOS 7.5 upgrade discussion There is a separate story created by Saul on this one: https://storyboard.openstack.org/#!/story/2003389 Please sync-up with Saul if he already has patch available or you want to create one. Thx. - cindy From: Lin, Shuicheng Sent: Friday, August 10, 2018 8:45 AM To: Penney, Don <Don.Penney@windriver.com<mailto:Don.Penney@windriver.com>>; Xie, Cindy <cindy.xie@intel.com<mailto:cindy.xie@intel.com>>; starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: RE: CentOS 7.5 upgrade discussion Hi Don, I also was thinking drop the vim srpm. Thanks for the confirmation. Best Regards Shuicheng From: Penney, Don [mailto:Don.Penney@windriver.com] Sent: Thursday, August 9, 2018 11:17 PM To: Xie, Cindy <cindy.xie@intel.com<mailto:cindy.xie@intel.com>>; starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade discussion I think we can safely drop the "vim" modification. It has a long history back to where we were inheriting code customizations from another layer, which was providing its own customized vimrc that had features enabled that were frustrating. From: Xie, Cindy [mailto:cindy.xie@intel.com] Sent: Thursday, August 09, 2018 11:01 AM To: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] CentOS 7.5 upgrade discussion Brent, Saul, Shuicheng, Let's initiate the discussion about how we'd like to handle CentOS 7.5 upgrade, we have a master xls sheet online for all non-openStack patches analysis (@Saul, I only have Google doc link but not accessible by WR). And here is the SRPM files we've already looked into, and believe they need upgrade. I put some columns in to fill-in more data (Shuicheng should have most of the data available). We can start from here. Thx. - cindy
Get it. Thanks Cindy. Best Regards Shuicheng From: Xie, Cindy Sent: Friday, August 10, 2018 8:57 AM To: Lin, Shuicheng <shuicheng.lin@intel.com>; Penney, Don <Don.Penney@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: RE: CentOS 7.5 upgrade discussion Sorry wrong link: https://storyboard.openstack.org/#!/story/2003398 From: Xie, Cindy Sent: Friday, August 10, 2018 8:55 AM To: Lin, Shuicheng <shuicheng.lin@intel.com<mailto:shuicheng.lin@intel.com>>; Penney, Don <Don.Penney@windriver.com<mailto:Don.Penney@windriver.com>>; starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: RE: CentOS 7.5 upgrade discussion There is a separate story created by Saul on this one: https://storyboard.openstack.org/#!/story/2003389 Please sync-up with Saul if he already has patch available or you want to create one. Thx. - cindy From: Lin, Shuicheng Sent: Friday, August 10, 2018 8:45 AM To: Penney, Don <Don.Penney@windriver.com<mailto:Don.Penney@windriver.com>>; Xie, Cindy <cindy.xie@intel.com<mailto:cindy.xie@intel.com>>; starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: RE: CentOS 7.5 upgrade discussion Hi Don, I also was thinking drop the vim srpm. Thanks for the confirmation. Best Regards Shuicheng From: Penney, Don [mailto:Don.Penney@windriver.com] Sent: Thursday, August 9, 2018 11:17 PM To: Xie, Cindy <cindy.xie@intel.com<mailto:cindy.xie@intel.com>>; starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade discussion I think we can safely drop the "vim" modification. It has a long history back to where we were inheriting code customizations from another layer, which was providing its own customized vimrc that had features enabled that were frustrating. From: Xie, Cindy [mailto:cindy.xie@intel.com] Sent: Thursday, August 09, 2018 11:01 AM To: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] CentOS 7.5 upgrade discussion Brent, Saul, Shuicheng, Let's initiate the discussion about how we'd like to handle CentOS 7.5 upgrade, we have a master xls sheet online for all non-openStack patches analysis (@Saul, I only have Google doc link but not accessible by WR). And here is the SRPM files we've already looked into, and believe they need upgrade. I put some columns in to fill-in more data (Shuicheng should have most of the data available). We can start from here. Thx. - cindy
I do not have a patch for this yet, so go ahead an work on it. On another subject, I am looking into options for our different configuration / initialization files changes. Using RPM vs Puppet, which based on a discussion will depend on the type of configuration or initialization changes required. I will move that discussion to existing thread here: http://lists.starlingx.io/pipermail/starlingx-discuss/2018-August/000615.htm... Sau! On 08/09/2018 09:00 PM, Lin, Shuicheng wrote:
Get it. Thanks Cindy.
Best Regards
Shuicheng
*From:* Xie, Cindy *Sent:* Friday, August 10, 2018 8:57 AM *To:* Lin, Shuicheng <shuicheng.lin@intel.com>; Penney, Don <Don.Penney@windriver.com>; starlingx-discuss@lists.starlingx.io *Subject:* RE: CentOS 7.5 upgrade discussion
Sorry wrong link: https://storyboard.openstack.org/#!/story/2003398
*From:* Xie, Cindy *Sent:* Friday, August 10, 2018 8:55 AM *To:* Lin, Shuicheng <shuicheng.lin@intel.com <mailto:shuicheng.lin@intel.com>>; Penney, Don <Don.Penney@windriver.com <mailto:Don.Penney@windriver.com>>; starlingx-discuss@lists.starlingx.io <mailto:starlingx-discuss@lists.starlingx.io> *Subject:* RE: CentOS 7.5 upgrade discussion
There is a separate story created by Saul on this one: https://storyboard.openstack.org/#!/story/2003389
Please sync-up with Saul if he already has patch available or you want to create one.
Thx. - cindy
*From:* Lin, Shuicheng *Sent:* Friday, August 10, 2018 8:45 AM *To:* Penney, Don <Don.Penney@windriver.com <mailto:Don.Penney@windriver.com>>; Xie, Cindy <cindy.xie@intel.com <mailto:cindy.xie@intel.com>>; starlingx-discuss@lists.starlingx.io <mailto:starlingx-discuss@lists.starlingx.io> *Subject:* RE: CentOS 7.5 upgrade discussion
Hi Don,
I also was thinking drop the vim srpm. Thanks for the confirmation.
Best Regards
Shuicheng
*From:* Penney, Don [mailto:Don.Penney@windriver.com] *Sent:* Thursday, August 9, 2018 11:17 PM *To:* Xie, Cindy <cindy.xie@intel.com <mailto:cindy.xie@intel.com>>; starlingx-discuss@lists.starlingx.io <mailto:starlingx-discuss@lists.starlingx.io> *Subject:* Re: [Starlingx-discuss] CentOS 7.5 upgrade discussion
I think we can safely drop the “vim” modification. It has a long history back to where we were inheriting code customizations from another layer, which was providing its own customized vimrc that had features enabled that were frustrating.
*From:*Xie, Cindy [mailto:cindy.xie@intel.com] *Sent:* Thursday, August 09, 2018 11:01 AM *To:* starlingx-discuss@lists.starlingx.io <mailto:starlingx-discuss@lists.starlingx.io> *Subject:* [Starlingx-discuss] CentOS 7.5 upgrade discussion
Brent, Saul, Shuicheng,
Let’s initiate the discussion about how we’d like to handle CentOS 7.5 upgrade, we have a master xls sheet online for all non-openStack patches analysis (@Saul, I only have Google doc link but not accessible by WR).
And here is the SRPM files we’ve already looked into, and believe they need upgrade. I put some columns in to fill-in more data (Shuicheng should have most of the data available). We can start from here.
Thx. - cindy
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
participants (7)
-
Jones, Bruce E
-
Khalil, Ghada
-
Lin, Shuicheng
-
Penney, Don
-
Rowsell, Brent
-
Saul Wold
-
Xie, Cindy