Re: [atomic-devel] Creating -release rpms

[Colin Walters <walters verbum org>]

On Fri, Aug 22, 2014, at 03:25 AM, Karanbir Singh wrote:
> How do we get repo configs for ostree shipped into the resulting images
> / tree's ?

There are a few options.  The most flexible though for both Fedora and
CentOS I think will be to make use of the mirrorlist= code that's about
to land: https://bugzilla.gnome.org/show_bug.cgi?id=729585

That way all the flexibility that mirrorlists provide yum also can be
used for OSTree - closest mirrors, etc.

In the short term, adding a config file in e.g.
/etc/ostree/remotes.d/centos-atomic.conf in a -release RPM to a
hardcoded URL and ensuring the default origin file to point there would
likely work.

Clients can easily change the tree and location.

> Are there any docs on how the repo's are meant to be setup, so we can
> have a stab at trying to create -release like rpms for this ?

So OSTree has this concept of an "origin" for the current tree, located
in the .origin file.  The autobuilder script currently hardcodes an
origin of osname:target - so whatever you use as osname is assumed to be
the same as the remote name.

For the original Fedora prototypes, I was just hardcoding the URL, but
as soon as we have the mirroring sorted, I was planning to look at this
myself too.

The biggest gap actually I see is the installer path - it's kind of
weird how it uses a remote name of "installmedia".  We may need further
Anaconda/pykickstart patches for this to be saner - some way to tell
Anaconda to pull from the physical media during the install, but still
set up ostree to pull from another origin post-install.