-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
We are moving to a unified ostree repo model where we compose/ship content for different releases in a single repo.
- From this we'll basically have one "compose" repo where all the different branches and rawhide write into it and we'll have two unified repos (one for atomic workstation and one for atomic host) where the content will be published to.
When we moved bodhi over to start using pungi we configured it to use a unified compose repo locatated at https://kojipkgs.fedoraproject.org/compose/updates/atomic/. The plan is to take this existing repo and mv it to /compose/atomic and use it for all composes.
The steps are:
1. archive /compose/atomic to /compose/atomic_archive_20180226 2. move the /compose/updates/atomic/ unified repo to /compose/atomic/ 3. update all configs to compose into /compose/atomic and sync to /atomic/host and /atomic/workstation/
Summary: - - rawhide now composes in /compose/atomic/ - - branched now composes in /compose/atomic/ - - bodhi now composes in /compose/atomic
- - FAH rawhide now publishes to /atomic/host/ - - FAW rawhide now publishes to /atomic/workstation/ - - FAH branched now publishes to /atomic/host/ - - FAW branched now publishes to /atomic/workstation/ - - FAH released updates now publishes to /atomic/host/ - - FAW released updates now publishes to /atomic/workstation/
If no one objects patrick and I will perform these changes on Wednesday 02/28 during a period of time in which no bodhi updates runs are executing.
Thanks, Dusty
On 02/26/2018 04:50 PM, Dusty Mabe wrote:
We are moving to a unified ostree repo model where we compose/ship content for different releases in a single repo.
From this we'll basically have one "compose" repo where all the different branches and rawhide write into it and we'll have two unified repos (one for atomic workstation and one for atomic host) where the content will be published to.
When we moved bodhi over to start using pungi we configured it to use a unified compose repo locatated at https://kojipkgs.fedoraproject.org/compose/updates/atomic/. The plan is to take this existing repo and mv it to /compose/atomic and use it for all composes.
The steps are:
- archive /compose/atomic to /compose/atomic_archive_20180226
- move the /compose/updates/atomic/ unified repo to /compose/atomic/
- update all configs to compose into /compose/atomic and sync to /atomic/host and /atomic/workstation/
Summary:
rawhide now composes in /compose/atomic/
branched now composes in /compose/atomic/
bodhi now composes in /compose/atomic
FAH rawhide now publishes to /atomic/host/
FAW rawhide now publishes to /atomic/workstation/
FAH branched now publishes to /atomic/host/
FAW branched now publishes to /atomic/workstation/
FAH released updates now publishes to /atomic/host/
FAW released updates now publishes to /atomic/workstation/
If no one objects patrick and I will perform these changes on Wednesday 02/28 during a period of time in which no bodhi updates runs are executing.
reminder. patrick and I will try to do this tomorrow if no one objects
Dusty
El mar, 27-02-2018 a las 17:17 -0500, Dusty Mabe escribió:
On 02/26/2018 04:50 PM, Dusty Mabe wrote:
We are moving to a unified ostree repo model where we compose/ship content for different releases in a single repo.
From this we'll basically have one "compose" repo where all the different branches and rawhide write into it and we'll have two unified repos (one for atomic workstation and one for atomic host) where the content will be published to.
When we moved bodhi over to start using pungi we configured it to use a unified compose repo locatated at https://kojipkgs.fedoraproject.or g/compose/updates/atomic/. The plan is to take this existing repo and mv it to /compose/atomic and use it for all composes.
The steps are:
- archive /compose/atomic to /compose/atomic_archive_20180226
- move the /compose/updates/atomic/ unified repo to
/compose/atomic/ 3. update all configs to compose into /compose/atomic and sync to /atomic/host and /atomic/workstation/
Summary:
rawhide now composes in /compose/atomic/
branched now composes in /compose/atomic/
bodhi now composes in /compose/atomic
FAH rawhide now publishes to /atomic/host/
FAW rawhide now publishes to /atomic/workstation/
FAH branched now publishes to /atomic/host/
FAW branched now publishes to /atomic/workstation/
FAH released updates now publishes to /atomic/host/
FAW released updates now publishes to /atomic/workstation/
My only question is why publish to separate locations?
Dennis
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 02/27/2018 05:53 PM, Dennis Gilmore wrote:
El mar, 27-02-2018 a las 17:17 -0500, Dusty Mabe escribió:
On 02/26/2018 04:50 PM, Dusty Mabe wrote:
We are moving to a unified ostree repo model where we compose/ship content for different releases in a single repo.
From this we'll basically have one "compose" repo where all the different branches and rawhide write into it and we'll have two unified repos (one for atomic workstation and one for atomic host) where the content will be published to.
When we moved bodhi over to start using pungi we configured it to use a unified compose repo locatated at https://kojipkgs.fedoraproject.or g/compose/updates/atomic/. The plan is to take this existing repo and mv it to /compose/atomic and use it for all composes.
The steps are:
- archive /compose/atomic to /compose/atomic_archive_20180226
- move the /compose/updates/atomic/ unified repo to
/compose/atomic/ 3. update all configs to compose into /compose/atomic and sync to /atomic/host and /atomic/workstation/
Summary:
rawhide now composes in /compose/atomic/
branched now composes in /compose/atomic/
bodhi now composes in /compose/atomic
FAH rawhide now publishes to /atomic/host/
FAW rawhide now publishes to /atomic/workstation/
FAH branched now publishes to /atomic/host/
FAW branched now publishes to /atomic/workstation/
FAH released updates now publishes to /atomic/host/
FAW released updates now publishes to /atomic/workstation/
My only question is why publish to separate locations?
I think the original reason was so that clients aren't likely to rebase to a ref of a different type (host -> workstation). Also we already have the workstation repo so i figured the appropriate action would be to create a corresponding "host" repo.
I don't have a strong preference here, though. If we think it would be better to publish to a single repo then I'm open to that change.
Dusty
I think its better and more in the spirit of ostree to have a single repo for delivery
Dennis
El mar, 27-02-2018 a las 22:40 -0500, Dusty Mabe escribió:
On 02/27/2018 05:53 PM, Dennis Gilmore wrote:
El mar, 27-02-2018 a las 17:17 -0500, Dusty Mabe escribió:
On 02/26/2018 04:50 PM, Dusty Mabe wrote:
We are moving to a unified ostree repo model where we compose/ship content for different releases in a single repo.
From this we'll basically have one "compose" repo where all the different branches and rawhide write into it and we'll have two unified repos (one for atomic workstation and one for atomic host) where the content will be published to.
When we moved bodhi over to start using pungi we configured it to use a unified compose repo locatated at https://kojipkgs.fedoraprojec t.or g/compose/updates/atomic/. The plan is to take this existing repo and mv it to /compose/atomic and use it for all composes.
The steps are:
- archive /compose/atomic to /compose/atomic_archive_20180226
- move the /compose/updates/atomic/ unified repo to
/compose/atomic/ 3. update all configs to compose into /compose/atomic and sync to /atomic/host and /atomic/workstation/
Summary:
rawhide now composes in /compose/atomic/
branched now composes in /compose/atomic/
bodhi now composes in /compose/atomic
FAH rawhide now publishes to /atomic/host/
FAW rawhide now publishes to /atomic/workstation/
FAH branched now publishes to /atomic/host/
FAW branched now publishes to /atomic/workstation/
FAH released updates now publishes to /atomic/host/
FAW released updates now publishes to /atomic/workstation/
My only question is why publish to separate locations?
I think the original reason was so that clients aren't likely to rebase to a ref of a different type (host -> workstation). Also we already have the workstation repo so i figured the appropriate action would be to create a corresponding "host" repo.
I don't have a strong preference here, though. If we think it would be better to publish to a single repo then I'm open to that change.
Dusty
On Wed, Feb 28, 2018, at 9:43 AM, Dennis Gilmore wrote:
I think its better and more in the spirit of ostree to have a single repo for delivery
I agree! But...it also seems OK to have them be separate. The fact that one *can* rebase between the two is IMO very cool, but it's also not a common use case. (Having them be merged does highlight ostree's dedup, but I don't think we're hurting for storage space that much)
That said as you all (hopefully) know I am heads down on obsoleting this via https://github.com/projectatomic/rpm-ostree/issues/1081
So let's not try to do spend a significant amount of time engineering this; if merging them is easier, that's cool! If not, that's OK too by me. I'd really like to focus on productizing the rojig model, including details like how we maintain the history via RPMs.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 02/26/2018 04:50 PM, Dusty Mabe wrote:
We are moving to a unified ostree repo model where we compose/ship content for different releases in a single repo.
v2 of this proposal is in a new post: https://lists.fedoraproject.org/archives/list/rel-eng@lists.fedoraproject.or...
rel-eng@lists.fedoraproject.org
-
Colin Walters -
Dennis Gilmore -
Dusty Mabe