[Starlingx-discuss] New build story

[Jones, Bruce E]

Here is yet another update on this topic.

At our F2F meeting yesterday we agreed on a 3 step plan for addressing the build issues.

Our short term solution is the story defined below.  We want to change the build to allow each company (and maybe different geos within companies) to create a shared mirror.  And change the build scripts to allow them to pick up and use that mirror.  As soon as possible.

Our medium term solution is to follow up on the idea suggested by Brent yesterday to create a build system where most of the RPM versions float.  Only those RPMs we patch or modify need to be tied to specific versions.

Long term, we are continuing to investigate options for hosting build artifacts for the project.  There are many options that we will be reviewing with our executives for feedback and approval.

Meanwhile, I'm very happy to hear that the Build team is already at work on the medium term solution, and I ask that they re-focus a bit on the short term solution so we can all get unblocked.

        brucej



From: Jones, Bruce E
Sent: Thursday, August 2, 2018 10:50 AM
To: starlingx-discuss at lists.starlingx.io
Subject: RE: New build story

Update from Ottawa.  Please hold off on this.   The team has come up with what might be a better idea.

From: Jones, Bruce E
Sent: Thursday, August 2, 2018 8:00 AM
To: starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>
Subject: New build story

I just created a new story for the Build team to change the mirror download and build scripts to enable us to create and manage per-company, shared import mirrors.  This should help insulate most developers from changes in upstream packages.  We recommend building one shared mirror per company per geography.  This is a short term band-aid while we figure out our long term build strategy.

The story is https://storyboard.openstack.org/#!/story/2003288.

Build team, please review and start work on this.  Thanks!

         brucej

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20180803/f9328f7d/attachment.html>