On Wed, Jun 19, 2019, at 14:55, Karanbir Singh wrote:
On 19/06/2019 20:14, Brian Stinson wrote:

> Operationally, this means we'd compose BaseOS by itself at a
> point-release time,  hard-link that tree over to the 'kickstart'
> location on the masters, and then re-spin for 0-day updates.


I was thinking we may just need a createrepo run somewhere else while
the baseos does not have 0+day updates etc. I dont know if we need to
hardlink content around etc.

Thinking one step out, would this metadata be the same as what we ship
on the ISO media ?

regards

I'm trying to get us away from one-off processes done by hand. It's easier to copy the structure as-is after a GA compose, and run an update compose with all of updates directly afterward.

We could (and probably should) generate the install media from the GA compose.