moving around some ostree repos

[Dusty Mabe]

-----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 





-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEPb6zG5c6sV89tRYPMwLb1zlS5nEFAlqUgSEACgkQMwLb1zlS
5nFqpA//YO/g1+dfvLRK4MFMM9t4h6TbSVMIPpA/fx45dbqpXXQq5ViFJDSvmdqm
F0UTpwN95TmPQvTNu7OSh6qW2LEGxNlrdqqKUN5C9HCNg+tF/sxYG+RXboTJWfyr
ZzfPQYv7dSoPZQvZ92cORVUGUwdSE8BXj1BOXHz59XOQOQRNfVk+XUxRm0P0XEBi
91NycUgqTSsWI7TkrxPidWpUlQdXUMo/nGgWSyeoHsGisLFSA6QrQMaMJ9d1CF0H
Qlnl62OeTmGuSbuiK/8aDOt0Sl+opeX3olTktjkIkHG9csRf4i6sYm0hEYt5lBOA
O6Osexza7M7frQX7X9b4qzUAf9CCSKUOrXEWXPnjm9OyvzTmyRSbMaTG2hCLRm4d
dXyL8wynMMjkNMzHyI6Kn4tZPnv59p7cgVxyfKP+B26O6o4wWbWMjFUPzPjVM7OZ
68b1uLnRLCjuyaJG70PlqeYIgCkullQzMmUC9di4uLUcDCviO5J5tRxsrrEvK5rx
5/0HDG6+4SiNCIlx7rCbbyg+2W8redSahccBXhbQuyPY4Rz6+8fmoLVK3uPz5oCw
2iAdq+CY5/3Z7hlWdljX7gTJXi0/dCClmI1bikrSOypiK3OO9lzex4MfNoHhRlKJ
kADsd82nn3ECrac8euAi37VqEzUe99FTPztGs4Dm2uwvMGSg0X0=
=jOxb
-----END PGP SIGNATURE-----

[Dusty Mabe]

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:
>  
>  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. 
reminder. patrick and I will try to do this tomorrow if no one objects

Dusty

[Dennis Gilmore]

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:
>  > 
>  > 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/ 
My only question
is why publish to separate locations?

Dennis

[Dusty Mabe]

-----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:
> >>
> >> 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/
>  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 





-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEPb6zG5c6sV89tRYPMwLb1zlS5nEFAlqWJL0ACgkQMwLb1zlS
5nGtWhAAkfQXKAwNX2i72lJgIbBBtLmiOT5ncprkEVB0A8QZ3iLF+/2I13Mus67B
G+d+J0UwdLJtV5HPqJqjzSq6vwOavDaEXWLvjXH0geHIs2SHUeUxcQhU2d2/qWta
OnVT22JkPIEq8s86yCfn0XDNhUqVoaFWlA+3fPTBOSnVuRBdDOtUkih+nreXBENS
5++wSHav47W1mzMoB+mBHLZPm7InQjuOWuE0jjTRSt6ztKFb5rYAPgixmbIm7kJD
gZBslP182TW/qlKlDoZxaZRrtux3AjSA0UF/OSyi/6bptef2ptdJY2rMsT+Qiar1
XNwPokFvRFk0+9UL1slVzR5ur+YI3FbliD7UtatqhHMjOWGBlttoJrdLUM61m116
9i6WMBhA5+WNgtklF5URaaykefXvmyH+sPincm06syT6kOC9qnjGbhAOnyvbGX7E
4Icb6jipK8/yxmUNyKWaugROGCkKe+BLJzaaRdTYwuXcvq2JL/SE6J+QOL11Tc1j
JVltnzwZ3FsqNrLQ3qcwgk7kWSqGVW2R1N+gQFcsv5CdmADg4xu2QJWU3izTnigF
QUMd6Qn+8Zjdwwe/0CIZDZnXOZ9Ya3kXg4uwcYu8XejAqxMHxN44mkpxtQUDyViV
Gz4UXH3tDxK1IdTiLzOlFHIUd8Au+FOf5D7ATkgc5izpthL1W5I=
=LJNI
-----END PGP SIGNATURE-----

[Dennis Gilmore]

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:
>  > > > 
>  > > > 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/
>  > 
>  > 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 
>  
>  
>  
>  
>

[Colin Walters]

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.

[Dusty Mabe]

-----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/[e-mail]...
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEPb6zG5c6sV89tRYPMwLb1zlS5nEFAlqYtd8ACgkQMwLb1zlS
5nH6nRAAjdS9VQy1WFlVml4Y+VJu36ICZkpP8/Gzt3TTsQfSrckXZxz2AvTlUmsY
cr21bLvQlklpnoYHoGQtLiGc5HavvvQb0HWJW0kSJU8nM2pIy4wJNkK/iyDMacpb
kakMtQdMQg3cCDZQ0VL7FDetA5DVzAeCiJU6cTiGoMtUwn2p0UyBILSkcVbxY2As
pROj88dZu0khKbYHH05HmcE40GUUmu9W+X9hLp58ge9gQq+eg+s3jjilIz0umVxO
h6zi2NronpFvJEQaU2QAdAsBCqN4LlepShYEDe13ZUaVFxeciQxCYOUv9VPZrec9
CDaorFuqRjWNz2sq6Ph3gu6uNObbZpyUpSh1rOL+vMc23SSqf7Qn8VpYrPPIBBnv
NFaZrKB6mrUre8qLxc6jK07rKnmnN8OvD7yeNsEm/JmpU8mPbJpp6gqpMEyeTIqh
4W0XxtfoqOcRlUw29giVz5ZV9nUGVIz+AXYUKpc8tu8/iF/7hlgNv6Rkd2ilrRvK
ru9St6MBXvJZq/M/bir9atFmI5ezzYHLlC7Xfyai9lT7TWa7mZsmqnqI4qVNwfBY
lQfhx8WMvnp/KR5eNfuPc0Bu8zoiPKDOvNdSZdZMbUUAQJMwSywXV5ncWTBpwFn/
8qgEisFJhf8UDlDTdtNmRX1YHqi6cpAoi4PUNHUu6sJvHurv2wY=
=zGIY
-----END PGP SIGNATURE-----