Re: final mirrorlist location for Atomic
On Mon, Nov 10, 2014 at 12:46:05AM -0600, Dennis Gilmore wrote: On Sat, 08 Nov 2014 13:16:19 -0500 Colin Walters walt...@verbum.org wrote: On Fri, Nov 7, 2014, at 08:03 AM, Dennis Gilmore wrote: On Sun, 02 Nov 2014 16:33:57 -0500 Colin Walters walt...@verbum.org wrote: Currently, the Atomic cloud image still tries to contact the compose server internal mirror for updates. Do we know what the final mirrorlist URL will be? Where are we on getting content sync'd out? the metalink should be https://mirrors.fedoraproject.org/metalink?repo=fedora-atomic-21arch=x86_64 Thanks, Dennis. The attached patch should implement this, once we: 1) Get https://admin.fedoraproject.org/updates/ostree-2014.11-1.fc21 through 2) Recompose the tree with it 3) Get a metalink generated pointing at that tree This likely needs work in mirrormanager to work. when mm detects the repo things happen automatically in the background. if mm can not detect a atomic tree it will do nothing and there will be no metalink url Previously the location was discussed and I thought most of the stakeholders had agreed to keep the Atomic trees on alt.fp.o, not on mirrors. Was this change (putting trees on mirrors) discussed with the other stakeholders? The reason I ask is that it appears that, for clients to use a metalink, additional work is required on MirrorManager, which wasn't planned. As we mentioned in IRC, alternately this stuff can sit on mirrors and not be used (yet?) until we have those changes made. But we definitely need it on a specific location (alt.fp.o) as well, so Colin can point to that for now. I assume this location can safely be changed later, once we have other MirrorManager capability (either fixes in MM1 or, more likely, MM2) available? 4) Do some end-to-end testing of this -- Paul W. Frieldshttp://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ The open source story continues to grow: http://opensource.com ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: final mirrorlist location for Atomic
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, 08 Nov 2014 13:16:19 -0500 Colin Walters walt...@verbum.org wrote: On Fri, Nov 7, 2014, at 08:03 AM, Dennis Gilmore wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 02 Nov 2014 16:33:57 -0500 Colin Walters walt...@verbum.org wrote: Currently, the Atomic cloud image still tries to contact the compose server internal mirror for updates. Do we know what the final mirrorlist URL will be? Where are we on getting content sync'd out? the metalink should be https://mirrors.fedoraproject.org/metalink?repo=fedora-atomic-21arch=x86_64 Thanks, Dennis. The attached patch should implement this, once we: 1) Get https://admin.fedoraproject.org/updates/ostree-2014.11-1.fc21 through 2) Recompose the tree with it 3) Get a metalink generated pointing at that tree This likely needs work in mirrormanager to work. when mm detects the repo things happen automatically in the background. if mm can not detect a atomic tree it will do nothing and there will be no metalink url 4) Do some end-to-end testing of this -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBAgAGBQJUYF8xAAoJEH7ltONmPFDRiYYQAKGuM1H4u+EOqzdQtMww+QRg M3Tj9LPd/vnM/TMtMg72kY2mBexwGPlTatsEMQDz0MEjedu7Xfzx6GJd/+Ymj0cn w46m1eE2kZ9R9rUa6HXIH8JltEEU6+9W9/BEVMgPVuaD3Jqht6PwwRTlxmtgzaWc DQvALY1z31BWwj7HnqHk48IgXakB70ejoN6g7DwKMP7xCPQNZMM7Thye16vVb4oU nPc6qK2DAcBh0XH+QTdzM+n3h1OBXLVXbsf1eg8mc7D1ZbTntSWhkWgtc+qjQxOW 9XBq/XMaX4Jsi+p0TekyFPMXugtluDOZn7Kz6Fa8RXynVTLgMPFtnM1nr7FCk++M eeIoKiNuO5YZziXV04R1ThbNNGUqxh9HW8Q4SMhhCV0TkXIYoEiLXvTtBPZ8vVL+ Nt9sc4/6K0zNwnLiEXIBu6AFF/S6T7VQD7belmbaAlfDsYE2TSx/JBSMORkKHHYM sCj5JBjkecKfjj3iJIsr1gwNRhrJoQmsuHpCdDnDLAISwCAYg1h6tYJxM1ENatMe 8KW5YfqKc6yXajZrb+N0Fggfyb6c1lx/NecPG0KWiPeJuuUsdTkarCkkxuzY+UQz 3wsc125LPTVSfNA2OcnH+ruVfRBH1Zq5m7ITvZJQJrC7A2WqHyrDAiN9EQyGsBfM 1BkaIdqP5KBsHFObhgcQ =6LMx -END PGP SIGNATURE- ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: final mirrorlist location for Atomic
On Fri, Nov 7, 2014, at 08:03 AM, Dennis Gilmore wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 02 Nov 2014 16:33:57 -0500
Colin Walters walt...@verbum.org wrote:
Currently, the Atomic cloud image still tries to contact the compose
server internal mirror for updates.
Do we know what the final mirrorlist URL will be? Where are we on
getting content sync'd out?
the metalink should be
https://mirrors.fedoraproject.org/metalink?repo=fedora-atomic-21arch=x86_64
Thanks, Dennis. The attached patch should implement this, once we:
1) Get https://admin.fedoraproject.org/updates/ostree-2014.11-1.fc21 through
2) Recompose the tree with it
3) Get a metalink generated pointing at that tree
4) Do some end-to-end testing of this
From e2317e1449749759d0a8895bca46f28b1739fa42 Mon Sep 17 00:00:00 2001
From: Colin Walters walt...@verbum.org
Date: Fri, 7 Nov 2014 13:49:57 -0500
Subject: [PATCH] atomic: Rewrite origin to point to metalink
Basically Anaconda-in-ImageFactory is set up to pull from the
builder, so that's what ends up in the origin file. But that's
obviously not what we want to ship to users.
ostree/rpm-ostree do not yet have a convenient command to change this,
so brute force it with sed.
Implements https://lists.fedoraproject.org/pipermail/cloud/2014-November/004570.html
---
fedora-cloud-atomic.ks | 3 +++
1 file changed, 3 insertions(+)
diff --git a/fedora-cloud-atomic.ks b/fedora-cloud-atomic.ks
index be862c4..8861d1e 100644
--- a/fedora-cloud-atomic.ks
+++ b/fedora-cloud-atomic.ks
@@ -36,6 +36,9 @@ reboot
%post --erroronfail
+# See https://github.com/projectatomic/rpm-ostree/issues/42
+ostree remote add --set=gpg-verify=false fedora-atomic 'metalink=https://mirrors.fedoraproject.org/metalink?repo=fedora-atomic-21arch=x86_64'
+(origin_file=$(echo -n /ostree/deploy/fedora-atomic-host/deploy/*.origin); sed -e 's,installmedia:,fedora-atomic:,' ${origin_file} ${origin_file}.new mv ${origin_file}{.new,})
# older versions of livecd-tools do not follow rootpw --lock line above
# https://bugzilla.redhat.com/show_bug.cgi?id=964299
--
1.8.3.1
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: final mirrorlist location for Atomic
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 7 Nov 2014 08:58:29 -0500 Matthew Miller mat...@fedoraproject.org wrote: On Fri, Nov 07, 2014 at 07:03:28AM -0600, Dennis Gilmore wrote: Do we know what the final mirrorlist URL will be? Where are we on getting content sync'd out? the metalink should be https://mirrors.fedoraproject.org/metalink?repo=fedora-atomic-21arch=x86_64 with the location on the primary mirror being http://dl.fedoraproject.org/pub/fedora/linux/atomic/21/ So we _are_ putting this out to the mirrors after all? Is this included in fedora-enchilada or is it separate? it is included in the fedora module which means also fedora-enchilada. we could move it to alt space is people prefer, in the end everything goes on mirrors. depending on where it goes changes how many mirrors will carry it. Dennis -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBAgAGBQJUXWXKAAoJEH7ltONmPFDRJyIQAJkdfbZfiDS+J+Q16nHo2pSr TAWtLde4WDYIoyWtwCVoV6OWlGUWpe000xo7R7V2Hmqa0RLgWjztJ0EBwl2Wm5UX l8WC3HYaSARQiL6Py8mLZcTef52eqOAOMMVr0Ieevv3gFTJe6b+hPoxcCsSTrNgg 5608Up5vydDVHCB7f51A3pAPRaB4Y2w0Xx7peEQ1qZ+Zd3KCyFkmXegqcgXIWflR m7wztpTUukMZP7JKGB3ftm5vd9hwSLXki+pU697u3DkNtmN7W/b46cXbtiGl7RaS +qBchXyCmOFWEjEkQ6ke/+aDUU/OHWEnq/Zem+m9GK08v9vdaBBaZYjwaEw6NnLM OHOGxvxGuQZQlVg4bMmY4L8RvFRBjEQkH0PJqRjhrZsuvHh+IHZZA1f4rQHQ46ug NClaw20Tc5j3SxHNzSFOSSGMQrKo+OY5/alAK9wr5cG4RFouKvINNGrQJNDxO7fE lx+Wy7i+K649wdEBunNODow2VFTay63BmcxyORvBXSe3h0ASuM4WnvH1U35Z+G45 Xxa/ZzgyeBJuBE53XWzW60VLmEM+Q8S9bx2S1S1YLnZPtz1YCCzE2S5/AvqQOVDZ 2HOskxXZcjFuqq2vCX6sVGlZBRPEh+ZFyO8m/F1i+5eMICoX4qpoWsbkfDMcfPE/ WQJAALiU+DVLxQ/RXFWe =g9+s -END PGP SIGNATURE- ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: final mirrorlist location for Atomic
On Mon, Nov 3, 2014, at 11:24 AM, Luke Macken wrote: I'm not sure exactly where the final bits will live, or what the URL will be, but the fedmsg-atomic-composer is up and running on the composer.stg box and successfully spitting out rawhide f21 trees. Nice. Maybe we can deprecate atomic01.qa.fp.org in favor of this? You could change it to take over the rawhide sync to dl.fedoraproject.org at least? Pushing this out to a production releng box will be simple once we determine where the trees will live on /pub. Who owns that decision/how do we move forward? ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: final mirrorlist location for Atomic
On Tue, Nov 04, 2014 at 10:28:02AM -0500, Colin Walters wrote: Assuming that this is correct, what needs to change? Is this a kickstart line? We should make the appropriate change _today_. That's not a globally replicated location, it means we're not taking advantage of mirrorlists. Particularly for cloud, I think we really Right, we decided a long time ago to defer worrying about mirroring until F22. want content replicated in each provider's AZ to avoid transit costs. Not sure if Fedora does this now. We had this set up several releases ago but it was dropped due to lack of popularity, if I recall. Now that we're scaling up our efforts we should revisit. ^ Kushal that's one for the todo list. :) Also: 1) That data comes from the atomic01.qa box that was provisioned as a testbed for Atomic work, with the idea that official composes would be done in rel-eng I thought that's what Luke was working on? 2) It's only composing rawhide right now :-/ And also note that until I get a chance to push some changes to spin-kickstarts, we're not going to have optimized LVM, which is 36% of the point of Atomic. Since beta is out the door, let's make those changes right now and get to testing them. The most realistic option to me seems to be to deliver Atomic 21 asynchronously from Fedora 21 final. Ideally within a few weeks? Welcome to other ideas though. We _really_ don't have a mechanism for that, although we have previously shipped updated images in emergencies. We've got people on this -- let's get it done with the actual release — there's still a month to go. (Two weeks of unfrozen, two where we can request exceptions but hopefully won't need to.) -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: final mirrorlist location for Atomic
On Tue, Nov 04, 2014 at 10:34:30AM -0500, Colin Walters wrote: Pushing this out to a production releng box will be simple once we determine where the trees will live on /pub. Who owns that decision/how do we move forward? Ticket at https://fedorahosted.org/rel-eng/ — I think the existing alt location is good enough for now and just using that might save wrangling. -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: final mirrorlist location for Atomic
On Sun, Nov 02, 2014 at 04:33:57PM -0500, Colin Walters wrote: Currently, the Atomic cloud image still tries to contact the compose server internal mirror for updates. Do we know what the final mirrorlist URL will be? Where are we on getting content sync'd out? I'm not sure exactly where the final bits will live, or what the URL will be, but the fedmsg-atomic-composer is up and running on the composer.stg box and successfully spitting out rawhide f21 trees. Pushing this out to a production releng box will be simple once we determine where the trees will live on /pub. As far as getting them hooked into MirrorManager, I opened this ticket last week to try and figure out what it will take: https://fedorahosted.org/fedora-infrastructure/ticket/4585 luke ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: final mirrorlist location for Atomic
On Mon, Nov 03, 2014 at 11:24:18AM -0500, Luke Macken wrote: I'm not sure exactly where the final bits will live, or what the URL will be, but the fedmsg-atomic-composer is up and running on the composer.stg box and successfully spitting out rawhide f21 trees. Pushing this out to a production releng box will be simple once we determine where the trees will live on /pub. Is it https://dl.fedoraproject.org/pub/alt/fedora-atomic/ ? -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
final mirrorlist location for Atomic
Currently, the Atomic cloud image still tries to contact the compose server internal mirror for updates. Do we know what the final mirrorlist URL will be? Where are we on getting content sync'd out? ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
