So in today's FESCo meeting, it was decided that since the workaround for making the netinstall image isn't all... worked around... rel-eng wants to just drop making a separate installable Workstation tree. On the mirrors, Workstation will just contain the live images. (Netinstall will still be possible, from the server netinstall, but not the default.) I'm thinking that if that's being done, we should do the same with Cloud, and just have Cloud images directly under Cloud (with no repo or rpms there).
What do you think?
This will all need to be revisited for F22 in any case.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wed, 22 Oct 2014 20:28:50 -0400 Matthew Miller mattdm@fedoraproject.org wrote:
So in today's FESCo meeting, it was decided that since the workaround for making the netinstall image isn't all... worked around... rel-eng wants to just drop making a separate installable Workstation tree. On the mirrors, Workstation will just contain the live images. (Netinstall will still be possible, from the server netinstall, but not the default.) I'm thinking that if that's being done, we should do the same with Cloud, and just have Cloud images directly under Cloud (with no repo or rpms there).
What do you think?
This will all need to be revisited for F22 in any case.
Not possible as we use the cloud install tree to make the cloud images. we would have to tweak the kickstarts and change the processes dramatically to drop the cloud install tree.
Dennis
On Thu, Oct 23, 2014 at 07:17:06AM -0500, Dennis Gilmore wrote:
Not possible as we use the cloud install tree to make the cloud images. we would have to tweak the kickstarts and change the processes dramatically to drop the cloud install tree.
That's only with the more involved "refactor the compose process" approach. Is there a reason that everything used in the compose process has to end up in the mirrors? For Cloud, everything we want is under "Cloud/Images".
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, 23 Oct 2014 08:56:16 -0400 Matthew Miller mattdm@fedoraproject.org wrote:
On Thu, Oct 23, 2014 at 07:17:06AM -0500, Dennis Gilmore wrote:
Not possible as we use the cloud install tree to make the cloud images. we would have to tweak the kickstarts and change the processes dramatically to drop the cloud install tree.
That's only with the more involved "refactor the compose process" approach. Is there a reason that everything used in the compose process has to end up in the mirrors? For Cloud, everything we want is under "Cloud/Images".
We need to ship what we use to make what we ship, in F22 we can look at refactoring things and put the cloud install tree into alt space. but we will need to ship it.
Dennis
On Fri, Oct 24, 2014 at 04:28:14PM -0500, Dennis Gilmore wrote:
That's only with the more involved "refactor the compose process" approach. Is there a reason that everything used in the compose process has to end up in the mirrors? For Cloud, everything we want is under "Cloud/Images".
We need to ship what we use to make what we ship, in F22 we can look at refactoring things and put the cloud install tree into alt space. but we will need to ship it.
I don't understand something here. Or else, I understand and I just disagree. We need to make our processes and tools open, transparent, and available — but that doesn't mean everything we use needs to be shipped to mirrors and end-users. That's especially the case for intermediate results — basically temp files that happen to be used in the construction of the final artifacts.
If we decide to go to different lifecycles or other more radical changes for the products, we'll likely need separate trees, and possibly more. That's one of the reasons I didn't argue when the duplicate-trees approach was proposed. But if we're not going to do it, I don't see a downside in removing the scaffolding used to build the images (or, not copying from the build area to staging, or not copying from staging to mirrors).
On Sun, Oct 26, 2014 at 11:57:00AM -0400, Matthew Miller wrote:
duplicate-trees approach was proposed. But if we're not going to do it, I don't see a downside in removing the scaffolding used to build the images (or, not copying from the build area to staging, or not copying from staging to mirrors).
And for whatever it's worth, I still think the minimum-necessary change of simply removing the netinstall images from the tree before it goes to the mirrors is the right solution for F21. But at this point, whatever gets us out the door in decent shape works for me!
rel-eng@lists.fedoraproject.org
-
Dennis Gilmore -
Matthew Miller