For https://fedoraproject.org/wiki/Changes/Atomic_Cloud_Image I was talking with Dennis Gilmore about some of what we would need to do in order to have Atomic be more closely integrated into the mainline infrastructure.
From memory, some action items:
* Define repodata.xml or similar to enable mirroring, add mirrorlist support [walters] * Start doing tree composes in daily compose runs [dgilmore] * Move fedora-atomic git repository into fedorahosted [walters] * Determine how Anaconda-in-Koji can pull tree content [?]
Also, I need to followup to Kevin on the mirroring, which is related to the last item.
Dennis, can you post the picture you took of the whiteboard?
On Mon, 07 Jul 2014 10:35:38 -0700 Colin Walters walters@verbum.org wrote:
For https://fedoraproject.org/wiki/Changes/Atomic_Cloud_Image I was talking with Dennis Gilmore about some of what we would need to do in order to have Atomic be more closely integrated into the mainline infrastructure.
From memory, some action items:
- Define repodata.xml or similar to enable mirroring, add mirrorlist
support [walters]
- Start doing tree composes in daily compose runs [dgilmore]
Was this going to be in koji? Then we may need a koji plugin, or to get a generic 'run in chroot' koji plugin working.
- Move fedora-atomic git repository into fedorahosted [walters]
- Determine how Anaconda-in-Koji can pull tree content [?]
Also, I need to followup to Kevin on the mirroring, which is related to the last item.
We could mirror at alt for now, I can set that up... if we are doing the composes in koji, we could also just ask folks to use kojipkgs, and only mirror 'release' trees?
Dennis, can you post the picture you took of the whiteboard?
That would be good.
kevin
On Mon, Jul 07, 2014 at 02:47:34PM -0600, Kevin Fenzi wrote:
- Determine how Anaconda-in-Koji can pull tree content [?]
Also, I need to followup to Kevin on the mirroring, which is related to the last item.
We could mirror at alt for now, I can set that up... if we are doing the composes in koji, we could also just ask folks to use kojipkgs, and only mirror 'release' trees?
For it to be practically useful, we'll need, eventually, to have trees with updates available somewhere public.
Here is the photo of the whiteboard.
On July 7, 2014 12:35:38 PM CDT, Colin Walters walters@verbum.org wrote:
For https://fedoraproject.org/wiki/Changes/Atomic_Cloud_Image I was talking with Dennis Gilmore about some of what we would need to do in order to have Atomic be more closely integrated into the mainline infrastructure.
From memory, some action items:
- Define repodata.xml or similar to enable mirroring, add mirrorlist
support [walters]
- Start doing tree composes in daily compose runs [dgilmore]
- Move fedora-atomic git repository into fedorahosted [walters]
- Determine how Anaconda-in-Koji can pull tree content [?]
Also, I need to followup to Kevin on the mirroring, which is related to the last item.
Dennis, can you post the picture you took of the whiteboard? _______________________________________________ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Hi,
I've now finished my action item for moving fedora-atomic into fedora hosted:
[1]https://fedorahosted.org/fedora-atomic/
I cleaned up the repository too; we now no longer need to pull from my COPR, and also I dropped the rawhide-kernel-nodebug (for now).
Should be ready to try doing a compose in infrastructure. Note you will need rpm-ostree 2014.104: [2]http://koji.fedoraproject.org/koji/buildinfo?buildID=543657
Which I just realized now that we're branched needs to be built for f21. Doing that now.
References
1. https://fedorahosted.org/fedora-atomic/ 2. http://koji.fedoraproject.org/koji/buildinfo?buildID=543657
infrastructure@lists.fedoraproject.org