[atomic-wg] Issue #180 `Future of Fedora Dockerfiles`
pfrields added a new comment to an issue you are following: `` If I understand the question -- we are working on fronting dist-git with Pagure. By spring it would hopefully allow for PRs on dist-git, helping maintainers collaborate more easily for a bunch of common use cases. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/180 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Re: Cloud and Server Q
On Tue, Oct 04, 2016 at 08:14:43AM -0500, Dennis Gilmore wrote: > On Friday, September 30, 2016 5:01:52 PM CDT Josh Boyer wrote: > > On Fri, Sep 30, 2016 at 4:41 PM, Josh Berkus <jber...@redhat.com> wrote: > > > On 09/30/2016 01:11 PM, Adam Miller wrote: > > >> On Fri, Sep 30, 2016 at 8:35 AM, Matthew Miller > > >> > > >> <mat...@fedoraproject.org> wrote: > > >>> On Thu, Sep 29, 2016 at 04:16:15PM -0700, Adam Williamson wrote: > > >>>>> think QA clearly understands what cloud image(s) are release blocking, > > >>>>> as previously they were just the non-atomic images. > > >>>> > > >>>> Which images are prominent on the download pages and how much of a > > >>>> relationship there is between that and 'release blocking' status is > > >>>> *also* not my problem, but I'd agree with you (Chris) that it'd be > > >>>> rather strange for the most prominently advertised deliverable for a > > >>>> given product not to be a release-blocking one. > > >>> > > >>> I don't think that Atomic *needs* to be release blocking, because if it > > >>> misses the grand unified release, we have the ability to update it at > > >>> the next cycle, so it's less of a big deal. But if we collectively > > >>> prefer to make sure everything is lined up on the release day... I can > > >>> see arguments for that, too. > > > > > > Well, currently I'm working with the designers on a new page for Atomic > > > F25. So if that's NOT going to be live the day of the F25 release, then > > > it's something we need to know ahead of time. > > > > > > I also really don't like the message Atomic not being ready sends. We > > > will have three branches for GetFedora: Workstation, Server, and Atomic. > > > > > > If Atomic isn't ready the day of the release, it looks pretty bad; > > > > > > that's saying we're ok with only being 2/3 ready, or that despite > > > promoting Atomic to 1st class status we don't really believe it's > > > important. > > So... there is a pretty big disparity between what you just said and > > what FESCo has been told in the past two meetings. Jan has been > > trying to get release blocking deliverables for the Cloud WG (now > > Atomic?) confirmed for a while [1]. Two weeks ago, Kushal confirmed > > the existing base images are release blocking and Atomic is not. That > > was repeated in today's meeting[2] as well: > > > > 16:44:56 Cloud base image is the only blocking deliverable. > > 16:44:59 Atomic is not. > > > > I realize this WG is in the middle of rebooting itself, but to have > > clearly conflicting information from the WG members is a bit > > concerning. > > > I will note that Atomic is not delivered as part of the relase at all. it is > only delivered as a stable artifact via the two week atomic host release > process. So there is no possible way it can be release blocking, there seems > to be some major confusion and disconnect here. We need to be clear on the difference between considering it important for Atomic images to be ready on release day, and being "release blockers." The latter has a very specific meaning as Adam W can attest. Being a deliverable is not the same as being release blocking. This seems like a problem of vocabulary. I think mattdm would agree we don't want to potentially, *indefinitely* block a six-month release with a deliverable that can be fixed and re-released in two weeks. That's what "release blocking" means. If it's not ready, the release doesn't go out. This was an overwhelming point in having that two week cycle -- to give more flexiblity vs. the standard Fedora release. Does this mean we shouldn't strive to have Atomic images ready day-and-date on GA? No. We missed this narrowly in F24, as I recall, and we should avoid repeating that, if at all possible. But let's not undermine a major dimension of the two-week release by confusing the release-blocker definition. -- 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 To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Re: Instances in AWS
On Mon, Jun 13, 2016 at 05:55:01PM +0530, Sayan Chowdhury wrote: > On Mon, Jun 13, 2016 at 8:16 AM, Dusty Mabe <du...@dustymabe.com> wrote: > > There are some extra running instances in our AWS account. > > > > They are named "Fedimg AMI Tester" and they have been up since June 7th. > > > > Can these be cleaned up? > > I have terminated the instances Sayan, are those supposed to terminate or be killed automatically, or am I mistaken? -- 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://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org
Re: [Marketing] Re: [MAGAZINE PROPOSAL] Fwd: [DRAFT] Why we're retiring 32-bit Images
On Fri, Apr 22, 2016 at 10:20:13AM -0400, Dusty Mabe wrote: > On 04/22/2016 09:44 AM, Paul W. Frields wrote: > > On Thu, Apr 21, 2016 at 06:14:05PM -0400, Justin W. Flory wrote: >> On > > 04/21/2016 05:10 PM, Joe Brockmeier wrote: >>> On 04/21/2016 05:04 PM, Paul > > W. Frields wrote: >>>> I can't make tonight's Magazine meeting, but I'm +1 > > to get this out >>>> ASAP. I've moved this article to Pending Review, but > > I already >>>> reviewed it and it looks fine. I added a couple additional > > links for >>>> SEO power. >>>> >>>> Anything Justin OK's for schedule for > > this is fine by me, assume >>>> +1. :-) And I'll be happy to help with > > social media, just please leave >>>> me an email or IRC message to do so > > and I'll catch it in the morning. >>> >>> I'd like to put this up too, but > > I don't think we've settled the >>> question on 32-bit that Dennis raised. > > Will check again. >>> >> >> Do we still want to aim for publishing this > > tomorrow? In the meeting, we >> agreed to publish it Friday, but if it's > > not ready or the questionable part >> can't be edited out, let's definitely > > hold on this. > > The article apparently was left in Scheduled status -- I > > moved it back > to > Pending Review status, and Patrick Uiterwijk kindly stripped it > from the > Fedora Planet so it wouldn't confuse anyone. It was out > there for a few > hours, though, FYI. > > > Too late phoronix picked it up: > > http://phoronix.com/scan.php?page=news_item=Fedora-Cloud-32-bit-Dead > > Looks like we might as well go ahead with it now. Let me be very clear and avoid confusion: :-) * This post has been pulled back from the Magazine and the Planet. It will 404 for page visitors. * I will expect Joe B from the Cloud WG to tell us authoritatively through the *marketing* list exactly what should happen next, since he (correctly) raised the issue of ensuring zero confusion over publishing these articles. Ideally this should have been settled between Cloud WG and rel-eng before an article was proposed. But failing that, we shouldn't schedule any Magazine post about changes in deliverables without clearly knowing it's decided. (To be fair, that seemed to be the case for at least a week, until dgilmore raised an objection.) Better communication will fix similar problems in the future. -- 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 http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org
Re: [Marketing] Re: [MAGAZINE PROPOSAL] Fwd: [DRAFT] Why we're retiring 32-bit Images
On Thu, Apr 21, 2016 at 06:14:05PM -0400, Justin W. Flory wrote: > On 04/21/2016 05:10 PM, Joe Brockmeier wrote: > >On 04/21/2016 05:04 PM, Paul W. Frields wrote: > >>I can't make tonight's Magazine meeting, but I'm +1 to get this out > >>ASAP. I've moved this article to Pending Review, but I already > >>reviewed it and it looks fine. I added a couple additional links for > >>SEO power. > >> > >>Anything Justin OK's for schedule for this is fine by me, assume > >>+1. :-) And I'll be happy to help with social media, just please leave > >>me an email or IRC message to do so and I'll catch it in the morning. > > > >I'd like to put this up too, but I don't think we've settled the > >question on 32-bit that Dennis raised. Will check again. > > > > Do we still want to aim for publishing this tomorrow? In the meeting, we > agreed to publish it Friday, but if it's not ready or the questionable part > can't be edited out, let's definitely hold on this. The article apparently was left in Scheduled status -- I moved it back to Pending Review status, and Patrick Uiterwijk kindly stripped it from the Fedora Planet so it wouldn't confuse anyone. It was out there for a few hours, though, FYI. -- 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 http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org
Re: [Marketing] Re: [MAGAZINE PROPOSAL] Fwd: [DRAFT] Why we're retiring 32-bit Images (was Re: Retiring 32-bit images)
On Tue, Apr 12, 2016 at 11:18:05AM -0400, Joe Brockmeier wrote: > On 04/07/2016 06:59 PM, Joe Brockmeier wrote: > > On 04/07/2016 06:47 PM, Ryan Lerch wrote: > >> Will it just be a featured image? Or are there other graphics required? > >> > > Just the featured image. Thanks! > > OK, looks like we have the featured image here: > > https://pagure.io/fedoramagazine-images/issue/12 > > Is this ready to go? Is there a specific date to target or run it now, > or...? I can't make tonight's Magazine meeting, but I'm +1 to get this out ASAP. I've moved this article to Pending Review, but I already reviewed it and it looks fine. I added a couple additional links for SEO power. Anything Justin OK's for schedule for this is fine by me, assume +1. :-) And I'll be happy to help with social media, just please leave me an email or IRC message to do so and I'll catch it in the morning. -- 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 http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org
Re: Cloud deliverables for F23
On Fri, Sep 04, 2015 at 04:27:05PM -0600, Mike Ruckman wrote: > On Fri, Sep 04, 2015 at 01:40:54PM -0400, Paul W. Frields wrote: > > Can someone in the Cloud WG please respond here? > > > > It seems surprising not to see the list of AMIs in this list, for > > instance, but there are probably other deliverables that need to be > > here. > > Hey Paul, > > We discussed it in our last meeting [0] and opened a ticket on our trac [1]. > I should have responded here so people knew things were moving. Sorry > about that. > > The ticket is up to date and I've also updated the wiki page. Just need > the final sign off. > > [0] > https://meetbot-raw.fedoraproject.org/fedora-meeting-1/2015-09-02/fedora-meeting-1.2015-09-02-17.00.txt > [1] https://fedorahosted.org/cloud/ticket/118 Awesome, thanks Mike. -- 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: Cloud deliverables for F23
On Tue, Sep 01, 2015 at 10:10:45AM +0200, Jan Kurik wrote: > Hi Working Group, > > currently we are missing list of release deliverables (blocking as > well as non-blocking) for Fedora releases. Some time ago there has > been an activity started in FESCo to fill this gap [1]. > As part of this activity has been put together a Wiki page summarizing > all the deliverables we need, to have a Fedora release complete [2]. > > I would like to ask you (WG) to go through the section "Cloud" of the > Wiki page and put together the list of deliverables which is produced > by Cloud WG for Fedora 23. > > Thanks for your cooperation. > Regards, > Jan > > > [1] https://fedorahosted.org/fesco/ticket/1427 > [2] > https://fedoraproject.org/wiki/Fedora_Program_Management/ReleaseBlocking/Fedora23#Cloud Can someone in the Cloud WG please respond here? It seems surprising not to see the list of AMIs in this list, for instance, but there are probably other deliverables that need to be here. -- 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
Cloud SIG release work
Hi Cloud SIG folks, I wanted to let you know that David Gay is pursuing other opportunities outside the Fedora Engineering team at Red Hat. He told me he wants to continue to contribute to Fedora, so you may still see him around. In the meantime, I'm working with Kushal Das and others as needed to pick up the critical tasks David was handling as part of his day job, so Fedora releases aren't unduly affected. If and when Red Hat opens up a slot for that position, I'll let the community know. Thanks as always for your contributions and your understanding! -- 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: Atomic 2 week releases
On Fri, Mar 13, 2015 at 05:13:29PM -0400, Michael P. McGrath wrote: - Original Message - From: Ian McLeod imcl...@fedoraproject.org To: cloud@lists.fedoraproject.org Sent: Friday, March 13, 2015 4:08:46 PM Subject: Re: Atomic 2 week releases On 03/13/2015 02:58 PM, Matthew Miller wrote: On Fri, Mar 13, 2015 at 02:26:42PM -0400, Joe Brockmeier wrote: We are on the hook for an Atomic Host release for F22, but I think I'd rather message why we're putting our weight behind a rapid-release host based on Fedora than dealing with two competing Fedora-based offerings. Has the spinner deciding whether the rapid-release host will be based on Rawhide or on $current come to a definitive rest yet? If the focus is on Rawhide, and we don't have interest / resources in keeping the $current branch up to date, I share Joe's concern — not just for confusion due to too many options, but also because in that case $current would almost always be the wrong choice (lagging CentOS and even RHEL). I think this would weigh heavily towards presenting that rawhide-based output on its own atomic.fpo home, because if $current is really going to be $outofdate, new users _will_ inevitably get the wrong thing. If development is done in Rawhide but also released to $current on a two-week cycle, I might have other worries, but this wouldn't be one of them. :) Apologies for joining in late folks. I'd like to summarize (I hope) a few points that have been made in this thread and in a handful of side-conversations. If we want something that is able to be consistently released every two weeks, we will likely struggle with rawhide. Although we all want rawhide to be usable day to day, it is not guaranteed to be stable and/or able to be built. We, the Atomic team, are in no position to either A) force it to be stable or B) apply even more effort as part of Atomic beyond the core work to ensure that rawhide stabilizes every two weeks. So this pushes us in the $current direction. The primary concern with $current is that Atomic may, for a narrow set of core packages, wish to run slightly ahead of what is in updates-stable for $current. However, I think this is more of a hypothetical/future concern at the moment. The core elements (docker, kubernetes, and rpm-ostree/ostree) are being pushed out to updates-testing (and our CentOS CBS builds) pretty rapidly. If we have a problem, it's that they are not being tested and/or promoted. So, two concrete options to consider: * Option 1 We target our 2 week release efforts at $current, which should involve a greater focus on testing and karma-ing the Atomic components as they show up in updates-testing. This gets us the stable base and gets non-Atomic $current users a nice flow of updates to popular and topical packages. And, at the risk of stating the obvious, this in no way prevents rawhide Atomic spins. The road to updates-testing passes through rawhide and the rawhide nightly compose, AIUI, already includes attempts at Atomic tree composes and Atomic images builds. So the Atomic spins would be $current + the updates-testing packages we care about (and have tested / have some influence over). That spin would then be copied to the mirrors and we'd be able to link to it. There's a nice side benefit there which is if someone who's running non-atomic Fedora wants to look at the latest of docker, kubernetes, etcd, ostree, whatever, they could just enable updates-testing and have access. Sounds like all of the benefits of the original rawhide suggestion with none of the pain. * Option 2 If at some point we feel we must carry some Atomic-focused updates that are not appropriate for $current, we maintain a very small side-tag to hold them. This is essentially what we are already doing for CentOS in the atomic7-testing tag on the CBS koji instance here: http://cbs.centos.org/koji/taginfo?tagID=40 Who exactly manages this tag and how content is promoted into it is TBD. I personally think we should at least try Option 1 with 2 as a fallback. Thoughts? +1 to at least trying option 1. FWIW this makes sense to me, too. In a chicken-and-egg twist, Atomic may hold part of the key(s) to making Rawhide more reliably stable and usable in the future. I think Atomic stands a better chance for testing and visibility on $current as already pointed out. So eventually that will, I hope, yield more effective iteration on features that allow us to build if not a less broken Rawhide overall, than at least a more easily recoverable one. This issue may be somewhat orthogonal to problems with building or composition of Rawhide. But still I hope it's a future possibility. -- Paul W. Frieldshttp://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906
Re: Fedora 22 Alpha release announcement
On Tue, Mar 03, 2015 at 11:48:59AM -0500, Jaroslav Reznik wrote: - Original Message - On 03/02/2015 10:50 AM, Jaroslav Reznik wrote: Hey everyone! As Fedora 22 Alpha is coming, the readiness meeting is this week, I'd like to have draft release announcement draft written prior the meeting, sooner than later (even there's still possibility of Alpha delays). Crossposting so this email finds the right people to provide the content :). As always, place to coordinate/write announcement is at: https://fedoraproject.org/wiki/F22_Alpha_release_announcement Willing to take point here, but if folks could send me some bullet points (or more) on what's interesting/new in the release that's appropriate for the alpha, that'd be greatly appreciated. Roshi is going to take a look on Cloud/bring it to the meeting. We have a few points for Server. So Workstation is needed now. And thanks Joe! I'll take this on for Workstation. I have the page open in my editor now, as a matter of fact, though I may not have changes done by today. -- 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 release announcement coordination
On Tue, Dec 02, 2014 at 11:00:17AM -0600, Joe Brockmeier wrote: On 12/02/2014 10:49 AM, Paul W. Frields wrote: As you guys are crafting improved notes, for better consistency, it would be great to write in present tense about the release. INCONSISTENT: Fedora 21 Foobar will include special flavor crystals that defy gravity and help you fly like Superman. CONSISTENT: Fedora 21 Foobar includes special flavor crystals that defy gravity and help you fly like Superman. Be sure to use passive voice too. Paul likes that.[1] Best, jzb [1] May not be entirely true. Consult your attorney. Offer not valid in Utah. Passive voice is not liked by me! Oh, wait... ;-) Just to clarify -- I think much of the current announcement dervies, from Alpha/Beta so it's natural it reads in future tense. I just figured to get a head start on the rewrite as it comes from multiple people. :-D -- 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 release announcement coordination
On Tue, Dec 02, 2014 at 10:26:49AM -0500, Jaroslav Reznik wrote: Hi all! As we're getting to pretty solid RC, it's again time for release announcement. Readiness meeting is on Thursday, would be nice to have a draft ready for review and final version next Monday, so text formatted and magazine versions can be prepared in advance. Workstation seems to be pretty covered, do we have any additions to Server and Cloud? The other thing is to get rid of all Beta strings. http://fedoraproject.org/wiki/F21_Final_release_announcement Thanks Joe for starting it and Paul for Workstation bit so far! We had the best Alpha/Beta announcements so far, let's continue with this high bar :). As you guys are crafting improved notes, for better consistency, it would be great to write in present tense about the release. INCONSISTENT: Fedora 21 Foobar will include special flavor crystals that defy gravity and help you fly like Superman. CONSISTENT: Fedora 21 Foobar includes special flavor crystals that defy gravity and help you fly like Superman. HTH! -- 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: Better testimonial for site?
On Sat, Nov 22, 2014 at 01:21:57PM +0100, Haïkel wrote: @Paul: only for Atomic or also for the cloud base image ? Both would be great. I'd rather have them both in hand and then let the designers website team figure out placement. -- 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: Testimonial #1
On Mon, Nov 24, 2014 at 12:52:57PM -0600, Major Hayden wrote: On 11/24/14 10:59 AM, Joe Brockmeier wrote: Here's the first testimonial - big thanks to Dusty for running this down and Major for being massively responsive! Thanks for including me! ;) Thanks for being so darn quotable. ;-) And thanks to Dusty for working on 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
Better testimonial for site?
Right now the Cloud flavor page on the new website has a single testimonial: “Fedora Atomic Host is the most up-to-date way to deploy Docker containers.” – Joe Brockmeier, Cloud Dude AIUI there were one or more Cloud WG contributors trying to get us a better testimonial. We've already shipped strings to translators but we could put a better quote in place on Monday if someone actually gets us the quote. Can someone advise on status here? -- 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: New Meeting Time
On Tue, Nov 11, 2014 at 06:22:28AM -0600, Joe Brockmeier wrote: On 11/11/2014 12:15 AM, Dennis Gilmore wrote: the Tuesday and Thursday times should work okay when I am in the states. Ah - when will that be? I thought I heard earlier Dennis will be returning ~December 3 -- 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
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
Spins issue
As I was going through some email this morning I saw that the Spins SIG is concerned that the Cloud SIG hasn't followed the Spins process to get their ec2 labeled Spin included in the spins-kickstart collection in git: http://lists.fedoraproject.org/pipermail/spins/2011-March/001734.html If the Cloud group needs to see this Spin included in the F15 release, then my recommendation is to start talking with the Spins SIG about the process. I believe there's a deadline that's passed, although you can request an exception and still make it into the release. To the Spins SIG, I would also recommend keeping lines of communication open if something goes wrong. A Cc: to the cloud@ list, for example, would help raise the issue to more people in a way that would help reach a solution faster. -- 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/ Where open source multiplies: http://opensource.com ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud
Re: Spins issue
On Tue, Mar 01, 2011 at 11:20:52AM -0500, Jared K. Smith wrote: On Tue, Mar 1, 2011 at 8:47 AM, Paul W. Frields sticks...@gmail.com wrote: As I was going through some email this morning I saw that the Spins SIG is concerned that the Cloud SIG hasn't followed the Spins process to get their ec2 labeled Spin included in the spins-kickstart collection in git: I've talked to Dennis about this already, and this was simply a miscommunication on his part. As we're moving towards having Koji generate the release images for EC2, he needed a place to store the EC2 kickstart file so that it was public and being tracked in revision control, and so that Koji could pull the kickstart file when it generated the images. As I understand it (and I'm sure Dennis will correct me if I'm wrong), Koji can either pull from packages.fedoraproject.org or from the spins git repo. So, to make a long story short, Dennis put the EC2 kickstart file in the spins git repo out of convenience. He wasn't trying to say that EC2 was a spin. I've got to admit that I never saw the EC2 images as being a spin per se, but that's certainly a discussion we can have going forward. As I re-read through the Spins guidelines, it's still not clear to me how this would even qualify as a spin -- it's really a different animal than our traditional spins. At the same time, I think it needs a lot of the same process for review, oversight, and QA that we currently have in place for spins, so there might be some ability to roll the cloud images into the spins concept. I'm certainly open to comments and suggestions either way. OK, thanks for this explanation. At the time it wasn't clear why the kickstart file was coming to the spins-kickstart repo. If there was a need for it to be there, then I wanted to see the teams involved get into a conversation about it. -- 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/ Where open source multiplies: http://opensource.com ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud
Re: Deltacloud Aggregator renamed to Aeolus Conductor
On Mon, Jan 17, 2011 at 02:26:50PM -0500, Chris Lalancette wrote: All, As promised[1], we have renamed the Deltacloud Aggregator to the Aeolus Conductor. The new website is http://www.aeolusproject.org. The now-obsolete deltacloud git repositories have been left in place, but set read-only; new code will be committed to the aeolus repositories (links to these are at the website). The yum repositories with in-progress packages have been moved from http://repos.fedorapeople.org/deltacloud/appliance to http://repos.fedorapeople.org/aeolus/packages . There is also a new mailing list for Aeolus development, aeolus-de...@fedorahosted.org [2]. The old mailing list will continue to function for now, but those who mail to that list will be gently asked to repost to aeolus-devel. As usual, any questions, comments, or requests for clarification are welcome. http://www.aeolusproject.org Can someone transform the repo URL in the news block on Aeolus' front page into link text (Click here for packages.)? It looks really amateurish right now. -- 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/ Where open source multiplies: http://opensource.com ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud
Re: Deltacloud Aggregator renamed to Aeolus Conductor
On Tue, Jan 18, 2011 at 09:31:57AM -0500, Chris Lalancette wrote: On 01/18/11 - 08:06:41AM, Paul W. Frields wrote: On Mon, Jan 17, 2011 at 02:26:50PM -0500, Chris Lalancette wrote: All, As promised[1], we have renamed the Deltacloud Aggregator to the Aeolus Conductor. The new website is http://www.aeolusproject.org. The now-obsolete deltacloud git repositories have been left in place, but set read-only; new code will be committed to the aeolus repositories (links to these are at the website). The yum repositories with in-progress packages have been moved from http://repos.fedorapeople.org/deltacloud/appliance to http://repos.fedorapeople.org/aeolus/packages . There is also a new mailing list for Aeolus development, aeolus-de...@fedorahosted.org [2]. The old mailing list will continue to function for now, but those who mail to that list will be gently asked to repost to aeolus-devel. As usual, any questions, comments, or requests for clarification are welcome. http://www.aeolusproject.org Can someone transform the repo URL in the news block on Aeolus' front page into link text (Click here for packages.)? It looks really amateurish right now. Heh, I'll give another whack at it. Earlier on I couldn't figure out how to make haml do that, but I've since learned more about haml, so I might have better success now. Thanks for the feedback, Chris -- sorry I returned to the list later than you. My feedback came out a lot more churlish than I meant it -- forgive me! I do think Aeolus is awesome. :-) -- 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/ Where open source multiplies: http://opensource.com ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud
Re: Meeting times...
On Mon, May 24, 2010 at 11:46:22PM -0500, Justin M. Forbes wrote: There has been a lack of participation at our weekly meeting the past couple of weeks. I am wondering if Thursdays at 17:00EST is still a good time for everyone, or if we would get better participation at some other time. Would another time perhaps work better for everyone? I've found that using a web app like http://whenisgood.net is far superior than general calls for people's schedules, which are hard to collate via an email list. -- 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/ Where open source multiplies: http://opensource.com ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud
