Hackathon update
* I updated the wiki details here with expensing status: https://fedoraproject.org/wiki/Infrastructure_Hackathon_2018#Attendees_and_Travel_Details If any of this is erroneous, please let me know and/or feel free to correct. * Hotel rooms are reserved, and our venue as well. * If you haven't booked travel yet and we haven't spoken recently, please let me know. I think this is only nb, smooge, and bowlofeggs still pending. * If there's anyone we haven't reached yet who would be useful to have at the hackathon, please say so. -- 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 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Re: VDO
On Fri, Feb 16, 2018 at 03:47:08PM +0100, Miroslav Suchý wrote: > Dne 16.2.2018 v 14:56 Dusty Mabe napsal(a): > > Once we get it into Fedora this would be a great blog post for the > > magazine. What do you think? > > Yes. Sure. Would love to have a feature on this. Refer here for the process, if you haven't done an article before: https://fedoramagazine.org/writing-an-article-for-the-fedora-magazine/ -- 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 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Re: congrats to Mikolaj Izdebski
On Tue, Feb 06, 2018 at 12:04:38PM -0800, Kevin Fenzi wrote: > I'm happy to announce that We have approved Mikolaj into the > sysadmin-main group. > > This is the core group of trusted folks that high level access to most > things. He's done great work maintaining koschei, helping us with > jenkins and java things and koji. > > Congrats and use your powers for good! Wow, this is great. Thank you for your efforts, Mikolaj, and congratulations. -- 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 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Infrastructure move -- thanks
I might be a bit biased from my perspective as the guy who manages the folks on the Infrastructure team. But I wanted to take a moment to say thank you to all the team members and everyone involved for conducting the recent colo move, a complex and critical process, in an outstanding manner. There were some difficulties along the way and the team dealt with them in their usual professional way. Kudos to all, and well done! -- 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 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Re: Adding Dusty Access/Membership to Releng/Infra
On Mon, Nov 27, 2017 at 04:33:44PM -0500, Matthew Miller wrote: > On Mon, Nov 27, 2017 at 04:20:23PM -0500, Dusty Mabe wrote: > > For Fedora Atomic we release content every two weeks. A lot of ducks > > have to be in a row in order to do this and often times behind the > > scenes work is time sensitive. I really need access to releng/infra > > so that I can be more efficient in doing this. I'd like to be able to: > > To whatever degree me vouching for Dusty counts, I vouch for him. :) As would I, although I suspect my voucher is worth less. :-) -- 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 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Re: bodhi-3.0.0-0.0.beta deployed to stg
On Thu, Oct 19, 2017 at 03:41:07PM -0400, Randy Barlow wrote: > bodhi-3.0.0-0.0.beta[0] has been deployed to staging. We plan to ask for > an FBR to deploy the final release when it is ready, but we plan to keep > this in testing through Monday, with a theoretical Tuesday production > deployment (assuming ACKs and testing goes well). > > This is a major release as it is backwards incompatible in how > repositories are layed out, and technically the bodhi CLI also has a > backwards-incompatibility too (the USERNAME env variable is no longer > used, as it clashed with GDM's). Patrick plans to rework the sync script > when we deploy to production so this will not impact our users. > > The primary purpose of this release is to switch to Pungi instead of > mash for repository composition. This allows many things, but the big > one is modular repository mashing, which is why we will be asking for a > Freeze Break. > > > [0] https://bodhi.stg.fedoraproject.org/docs/release_notes.html Congratulations on (nearly) the 3.0 release! This is a big-deal milestone -- thanks to all who contributed. -- 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 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
PDC release data (for F28)
Hi, I met up with abompard and Kellin today to solidify a plan to deal with this issue affecting Fedora: <https://github.com/product-definition-center/product-definition-center/issues/294> Here are the notes from the session. It looks like Django makes this reasonably easy to solve via extending the app. Andrew, the guy mentioned below, is one of the PDC owners inside Red Hat. I don't think he's involved in Fedora, which is not an issue; the point is to keep in touch with him to validate our approach. * * * PDC enhancements -- 2017-09-29 Attendees: pfrields, rmarshall, abompard https://github.com/product-definition-center/product-definition-center/issues/294 https://github.com/product-definition-center/product-definition-center/issues/459 * What did Rob discover about PDC approach? * Talked with Andrew, so if we have an app with an API endpoint we can hit with our dataset, that should work well. We can extend the data model the way that we need it. * Rob's stuff he was looking at was about builder and architecture type, not really related to these issues. * What can/should Aurélien contribute? * Looked at PDC source code -- can write the resource containing the necessary models and hooking up an API endpoint * Should keep in touch with Andrew to get the patch in * AGREED: abompard will take this work up... target is to get this in so we can use for F28 * Dates can change over time * E.g. release date slips or the EOL date is changed * rob: If we can keep a "changelog" of slip dates, that might be helpful. Not sure how to handle this in the API but it would be great if the data model could accommodate somehow. -- 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 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Re: Retroactive FBR
On Fri, Sep 22, 2017 at 05:20:57PM -0500, Dennis Gilmore wrote: > El vie, 22-09-2017 a las 17:38 -0400, Paul W. Frields escribió: > > I want to apologize profusely -- I pushed a tiny change to the email > > aliases and completely failed to consider they are covered by FBR > > requirement. > > > > https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id= > > fe766d267f4e3149b2931573216de96db8406101 > > > > Kushal's no longer at Red Hat effective COB today, and AIUI this > > alias > > sometimes is used for internally destined info like billing or other > > contact. > > > > So I'm seeking retroactive +1 and promise to give myself 50 lashes > > with a wet noodle. > > > > Does Robyn need to be in that list still? Probably not. I'll go over it again and revise but not until post-freeze. ;-) -- 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 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Retroactive FBR
I want to apologize profusely -- I pushed a tiny change to the email aliases and completely failed to consider they are covered by FBR requirement. https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=fe766d267f4e3149b2931573216de96db8406101 Kushal's no longer at Red Hat effective COB today, and AIUI this alias sometimes is used for internally destined info like billing or other contact. So I'm seeking retroactive +1 and promise to give myself 50 lashes with a wet noodle. -- 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 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Re: Congrats to Adam Miller
On Fri, Sep 01, 2017 at 10:28:48AM -0400, Kevin Fenzi wrote: > I'm happy to announce that We have approved Adam into the sysadmin-main > group. > > This is the core group of trusted folks that high level access to most > things. Adam has done great work rolling out and maintaining and working > on the next generation of the Open Shift Build System and other work > with releng. > > This should allow him to more easily roll out and provision new versions > of OSBS. > > Congrats and use your powers for good! :) \o/ This is a big deal. Congratulations Adam and remeber, with great power comes great responsibility. ;-) -- 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 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Re: Storage requirements for CI
On Tue, Jul 25, 2017 at 12:12:30PM -0400, Dennis Gregorovic wrote: > > > On 07/25/2017 10:59 AM, Paul W. Frields wrote: > > I'd meant to raise this question last week but it turned out several > > folks were out of pocket who'd probably want to discuss. One of the > > aspects of continuous integration[1] that impacts my team is the > > storage requirement. How much storage is required for keeping test > > results, composed trees and ostrees, and other artifacts? What is > > their retention policy? > > > > A policy of "keep everything ever made, forever" clearly isn't > > scalable. We don't do that in the non-CI realm either, e.g. with > > scratch builds. I do think that we must retain everything we > > officially ship, that's well understood. But atop that, anything we > > keep costs storage, and over time this storage costs money. So we > > need to draw some reasonable line that balances thrift and service. > > > > A. Retention > > > > > > The second question is probably a good one to start with, so we can > > answer the first. So we need to answer the retention question for > > some combination of: > > > > 1. candidate builds that fail a CI pipeline > > 2. candidate builds that pass a CI pipeline > > 3. CI composed testables > > * a tree, ISO, AMI, other image, etc. that's a unit > > * ostree change which is more like a delta (AIUI) > > 4. CI generated logs > > 5. ...other stuff I may be forgetting > > The other big bucket is packages in the buildroot used to build the > builds. You may want to keep these as well if there is a desire to > be able to rebuild packages at a later point. Thanks for that. My bet is we'd want to set the retention dial for those no higher than "when that release goes EOL." > > My general thoughts are that these things are kept forever: > > > > * (2), but only if that build is promoted as an update or as part of a > > shipped tree/ostree/image > > * (3), but only if the output is shipped to users > > * (4), but only if corresponding to an item in (2) or (3) > > > > Outside that, artifacts and logs are kept only for a reasonable amount > > of troubleshooting time. Say 30 days, but I'm not too worried about > > the actual time period. It could be adjusted based on factors we have > > yet to encounter. > > How does this proposal compare the existing practice in Fedora? My initial guess is, pretty well in concept -- but that the *practice* is that we've not been very aggressive about trimming ancient shipped stuff. How many people are liable to seek Fedora <= 18 releases at this point, for example? -- 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 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Storage requirements for CI
I'd meant to raise this question last week but it turned out several folks were out of pocket who'd probably want to discuss. One of the aspects of continuous integration[1] that impacts my team is the storage requirement. How much storage is required for keeping test results, composed trees and ostrees, and other artifacts? What is their retention policy? A policy of "keep everything ever made, forever" clearly isn't scalable. We don't do that in the non-CI realm either, e.g. with scratch builds. I do think that we must retain everything we officially ship, that's well understood. But atop that, anything we keep costs storage, and over time this storage costs money. So we need to draw some reasonable line that balances thrift and service. A. Retention The second question is probably a good one to start with, so we can answer the first. So we need to answer the retention question for some combination of: 1. candidate builds that fail a CI pipeline 2. candidate builds that pass a CI pipeline 3. CI composed testables * a tree, ISO, AMI, other image, etc. that's a unit * ostree change which is more like a delta (AIUI) 4. CI generated logs 5. ...other stuff I may be forgetting My general thoughts are that these things are kept forever: * (2), but only if that build is promoted as an update or as part of a shipped tree/ostree/image * (3), but only if the output is shipped to users * (4), but only if corresponding to an item in (2) or (3) Outside that, artifacts and logs are kept only for a reasonable amount of troubleshooting time. Say 30 days, but I'm not too worried about the actual time period. It could be adjusted based on factors we have yet to encounter. B. Storage - How much? == To get an idea of what this might look like, I think we might make estimates based on: * the number of builds currently happening per day * how many of these builds are within the definition for an officially shipped thing (like Atomic Host, Workstation, Server, etc.) * The average size of the sources + binaries, summed out over the ways we deliver them (SRPM + RPM, ostree binary, binary in another image), and multiplied out by arches * Then sum this out over the length of a Fedora release This is the part I think will need information from the rel-eng and CI contributors, working together. My assumption is there are gaping holes in this concept, so don't take this as a full-on proposal. Rather, looking for folks to help harden the concepts and fill in the missing pieces. I don't think we need a measurement down to the single GB; a broad estimate in 100s of GB (or even at the 1 TB order of magnitude) is likely good enough. I'm setting the follow-up to infrastructure@lists.fedoraproject.org, since that team has the most information about our existing storage and constraints. -- 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 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Re: SLE (Service level expectations)
On Wed, Jul 19, 2017 at 01:24:08PM -0400, Stephen John Smoogen wrote: > On 18 July 2017 at 15:34, Kevin Fenzi wrote: > > Take a look at: > > > > https://pagure.io/fedora-infrastructure/issue/6140 > > > > and > > > > https://fedoraproject.org/wiki/Infrastructure/ServiceLevelExpectations > > > > Any comments or additions to the doc? > > > I would say that we should all read through the Cornell website > https://confluence.cornell.edu/display/itsmp/Service+Level+Expectations > (also linked in wiki document) and also read through > > https://confluence.cornell.edu/display/itsmp/Service+Level+Expectations?preview=/165319876/174489819/Information_Technology_Service_Level_Expectation_(SLE)_Template.dotx > > Examples of completed documents: > https://www.emich.edu/it/help/pdf/ithdsle.pdf > > https://cms.montgomerycollege.edu/oit/HelpAndSupport.aspx?id=91 > > In general these are more of a setting expectations documents and > ability to say "no we don't agree to be up at 0500 UTC to support XYZ > service. You can get help at 1000 UTC -> 2300 UTC Monday through > Friday.] Yeah, I think the idea should be to get this into the template Cornell provides at their site. Not the lame MS Office format, obviously, just in terms of sections and content. The nice thing about an official format is it gives us yet another backstop for anchoring our expectations. An SLE is designed to help anyone who approaches understand our current offerings. So the more precisely we can document, the less it requires us to play "police" and rather be seen as providing a service. I think the format probably gives us the flexibility we need to outline different levels, i.e. fedoraproject.org vs. fedoracommunity.org (which may also need to have sites aligned?) for expected response/maintenance levels. -- 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 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Re: OpenShift, Greenwave, and WaiverDB
On Wed, Jul 19, 2017 at 09:36:52PM +0200, Pierre-Yves Chibon wrote: > On Wed, Jul 19, 2017 at 02:32:26PM -0400, Randy Barlow wrote: > > Hello! > > > > There is some effort right now to make Bodhi gate updates based on > > Greenwave. We would like to test Bodhi and Greenwave together in > > staging and ultimately use it in production soon. > > We do have the staging instance of openshift, could it be leveraged for your > tests ? From last night's discussion in IRC, it sounded like the agreement was that: (1) Ralph & co. will get a deployment template ready for our OpenShift in staging; (2) Ricky Elrod is working on similar for our Modernpaste (currently in staging) to make that a first target for production; (3) We were up until just recently waiting for a production wildcard cert, but that is now in place AIUI from other list mail from Smooge From (2) and (3) it sounds like we can have something in production Very Soon(tm), but this doesn't change the need to test things out in staging before they go to production. (And everyone gets that, and can roll with it.) Is there another wrinkle here I missed? -- 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 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Re: CI/CD requirements
On Thu, Jul 20, 2017 at 03:50:00PM +, Justin W. Flory wrote: > On 07/11/2017 11:18 AM, Paul W. Frields wrote: > > One of the things I've been working on (along with several other > > people, including mattdm, dgilmore and pingou) is sussing out Fedora > > requirements on a CI/CD pipeline. I published the results to this > > page: > > > > https://fedoraproject.org/wiki/Fedora_requirements_for_CI_and_CD > > > > Since Fedora infra is a stakeholder (along with release engineering, > > QA, etc.), my thought is this page helps us clarify requirements and > > avoid surprises down the road. Also this might be useful to show to > > e.g. FESCo as a joint policy. > > > > Rather than just editing the page willy nilly, based on the number of > > people it's already been through, it would be great if folks could use > > the "discussion" (Talk) page to suggest changes. But I have a watch > > on the page and can help resolve issues. > > > > I've fallen behind on email the past couple of weeks, but I saw this > when I was quickly scrolling through the Infrastructure list… this is > really interesting and I'd like to keep up with more updates on progress > on developing the CI/CD pipeline for Fedora. > > Is there any singular place where someone can follow along with updates > about this outside of the Infrastructure list? Or has anyone considered > writing a Community Blog article about some of these plans / ideas? Even > though I don't have a lot of feedback to contribute, I'm sure a > Community Blog article might solicit a little wider feedback and also > inform people about some of these plans, even if it's still very early > in the process. :) There's a list and channel expressly for it. This is the best jumping off point: https://fedoraproject.org/wiki/CI -- 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 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Re: OpenShift plans
On Mon, Jul 03, 2017 at 08:01:16PM +0200, Pierre-Yves Chibon wrote: > On Mon, Jul 03, 2017 at 11:51:03AM -0600, Kevin Fenzi wrote: > > On 07/03/2017 11:17 AM, Pierre-Yves Chibon wrote: > > > On Mon, Jul 03, 2017 at 01:12:48PM -0400, Paul W. Frields wrote: > > >> So we currently have a staging instance of OpenShift Container > > >> Platform -- what are the next actions needed to get a production > > >> deployment going? > > > > > > My understanding is that we are at least waiting on the wildcard cert for > > > it. > > > > We were, but that arrived a week or two ago. ;) > [...] > > > Might be more, but at that point I think we could look at spinning up > > the prod one and getting a wildcard cert for it. > > I meant the prod wildcard cert :) Do we have that prod wildcard cert 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/ The open source story continues to grow: http://opensource.com ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
PkgDB issue for Fedora upgrades
https://pagure.io/fedora-workstation/issue/23 Kalev Lember realized during our WG meeting that the Pkgdb deprecation/removal has side effects on users' ability to upgrade their older Fedora systems via the GNOME Software facility. It would be good to get some input from the infra team in that ticket. -- 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 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
CI/CD requirements
One of the things I've been working on (along with several other people, including mattdm, dgilmore and pingou) is sussing out Fedora requirements on a CI/CD pipeline. I published the results to this page: https://fedoraproject.org/wiki/Fedora_requirements_for_CI_and_CD Since Fedora infra is a stakeholder (along with release engineering, QA, etc.), my thought is this page helps us clarify requirements and avoid surprises down the road. Also this might be useful to show to e.g. FESCo as a joint policy. Rather than just editing the page willy nilly, based on the number of people it's already been through, it would be great if folks could use the "discussion" (Talk) page to suggest changes. But I have a watch on the page and can help resolve issues. -- 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 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
OpenShift plans
So we currently have a staging instance of OpenShift Container Platform -- what are the next actions needed to get a production deployment going? (My understanding is that, as a new service, we're not blocked by infra freeze itself, but there may be other things in the way on top of just having cycles free.) -- 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 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Re: [Release] pagure: 3.0
On Fri, Jun 30, 2017 at 11:46:47AM +0200, Pierre-Yves Chibon wrote: > Good Morning Everyone, > > I just cut a new release of pagure: 3.0. [...] A big milestone -- congratulations! -- 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 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Re: The Future of the Fedora Layered Image Build System's OpenShift Deployment
On Wed, Jun 21, 2017 at 11:27:58AM +0100, Peter Robinson wrote: > On Tue, Jun 20, 2017 at 9:09 PM, Adam Miller > wrote: > > Hello all, > > I wanted to bring up the topic of the future of Fedora's Layered > > Image Build System (FLIBS) as it pertains to OpenShift as a backend > > technology that FLIBS is built on top of. > > > > TL;DR - Does anyone care if we move FLIBS to be run on OpenShift > > Container Platform instead of OpenShift Origin in the future? > > > > OpenShift itself comes in two forms. The first is the upstream > > OpenShift Origin which is very rapidly releasing which has no official > > support for older releases (no N-1 support), so it would require a > > fresh roll out every three months. The second is the Red Hat OpenShift > > Container Platform which is the productized version based on OpenShift > > Origin, follows a slower release cadence, and offers longer life > > support per release than Origin. I would like to note for the sake of > > posterity for the mailing list thread that both of these are Open > > Source. > > > > I outline these points in order to ask if there is any preference from > > the Fedora Infrastructure Team on which "edition" of OpenShift that > > FLIBS is built on top of in the future. I ask this because currently > > FLIBS is built on OpenShift Origin which has already proven difficult > > to keep up with latest releases since I'm currently the only one > > working on FLIBS and it's not the only thing I am actively working on > > at any one point in time and I would like to move to OpenShift > > Container Platform in the future. > > +1 we use RHEL and other downstream of the community in other places > within the infrastructure too for various reasons, I think it makes > perfect sense to move to a platform that has less churn and active > support so that people, whether it be Infra team or yourself, have > more time to work on enhancements to the service that sits on top > rather than just churning to maintain the underlying infrastructure. And with my manager hat on, +1 here. Not meaning, "yes, we must do this." Rather, as someone who monitors how cycles get spent, I mean it makes sense as a change that frees up those cycles for more productive, net-new work. -- 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 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Re: FBR: Remove piwik from websites
On Thu, Jun 08, 2017 at 11:09:29AM -0400, Stephen John Smoogen wrote:
> I would like to remove Piwik from the wiki and other websites which
> use it. Currently the main change would be in the files:
>
>
> roles/mediawiki/files/skins/Fedora.php
> roles/mediawiki123/files/skins/Fedora.php
>
> diff --git a/roles/mediawiki123/files/skins/Fedora.php
> b/roles/mediawiki123/files/skins/Fedora.php
> index fda1a78..1956819 100644
> --- a/roles/mediawiki123/files/skins/Fedora.php
> +++ b/roles/mediawiki123/files/skins/Fedora.php
> @@ -91,22 +91,6 @@ class FedoraTemplate extends QuickTemplate {
> if($this->data['trackbackhtml']) print
> $this->data['trackbackhtml']; ?>
>
> html('headscripts') ?>
> -
> -
> - var _paq = _paq || [];
> - _paq.push(["setDomains", ["*.fedoraproject.org"]]);
> - _paq.push(['trackPageView']);
> - _paq.push(['enableLinkTracking']);
> - (function() {
> -var u="//piwik.fedorainfracloud.org/piwik/";
> -_paq.push(['setTrackerUrl', u+'piwik.php']);
> -_paq.push(['setSiteId', 12]);
> -var d=document, g=d.createElement('script'),
> s=d.getElementsByTagName('script')[0];
> -g.type='text/javascript'; g.async=true;
> g.defer=true; g.src=u+'piwik.js'; s.parentNode.insertBefore(g,s);
> - })();
> -
> - src="//piwik.fedorainfracloud.org/piwik/piwik.php?idsite=12"
> style="border:0;" alt="" />
> -
>
> data['body_ondblclick']) { ?>ondblclick=" $this->text('body_ondblclick') ?>"
> data['body_onload']) { ?>onload=" $this->text('body_onload') ?>"
>
> This will then necessitate a rerun of the associated playbook
FWIW, as long as the relevant stakeholders have been consulted
(e.g. robyduck, mattdm) and are OK with the change, +1 here. (Not
sure I really get a vote here, but noting I agree with the change as
one of the earlier Piwik stakeholders.)
--
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
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Re: Pagure on dist-git, the state of things
Just making sure the whole original message made it to rel-eng list. Reply-to is set to infra@ so we can keep discussion in one place. On Thu, Apr 20, 2017 at 12:08:35PM -0500, Dennis Gilmore wrote: > Can you please report this to releng also? > > Dennis > > > El jue, 20-04-2017 a las 15:45 +0200, Pierre-Yves Chibon escribió: > > Good Morning Everyone, > > > > I figured it has been a while since I reported progress on making pagure a > > front-end for dist-git. > > > > So here is a small status update. > > > > What works: > > - Well currently pagure is working as a front-end for dist-git in stg: > > https://src.stg.fedoraproject.org/pagure/ > > - Hosting repos, browsing them, creating PR works all fine (w/ one , see > > below) > > - Features we want to exclude have been turned off (no user management on > > the > > pagure side) > > > > What does not work: > > - Syncing the ACLs from pkgdb to gitolite takes ~3 minutes in prod, in stg, > > the > > updated script in stg (which sync the ACLs from pkgdb to gitolite and > > pagure) > > runs in ~30/35 minutes (if it doesn't crash, which my last run just did) > > This is a blocker since it means it takes 30 to 35 minutes for someone to > > get > > access to their git repo or (worse) their fork > > - This pagure instance has the same issue as the main one, including a > > heisenbug > > we're trying to track but have had no luck reproducing so far :( > > > > What needs to be done: > > - Fix the sync script > > - Make it *way* faster than it is > > - Make it creates the project on pagure using the releng user rather than > > relying on the first contributor it finds in the list of maintainers > > - Make fedmsg-genacls be triggered on pagure's fork fedmsg message so > > that we > > re-generate the gitolite configuration file when someone forks a project > > (and thus give them access to their fork) > > - Once above is done: call for more testers > > > > In the future: > > - I think we will want to deprecate pkgdb entirely, so while the work above > > is > > important, ideally it won't be there for too long. > > - With pkgdb out of the loop, we'll need to figure some things out: > > - Where/How to store the contact info for bugzilla > > - Not sure relying on pagure's ACLs there is the way to go since we > > would > > loose a level of granularity in the ACLs that I know people like and > > ask > > for (having commit w/o being on the CC list in bugzilla or being on > > the CC > > list w/o being a packager) > > - How/when to require people be part of the packager group in FAS? > > - Since one of the idea of pagure is to make it easier for "drive-by" > > contribution to spec files, requiring to be a packager should only be > > there for maintainers, but pagure doesn't have this level of > > information/requirement, so we would need to find something or some > > place > > to add this requirement or see if that requirement still stands > > > > This is all I can think of for now, I'll update this thread if I come up > > with > > more ideas/challenges. > > > > > > Have a nice day, > > Pierre ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Re: 2017-03-21 PHX2 Outage thoughts
On Sat, Apr 22, 2017 at 07:42:18AM -0600, Kevin Fenzi wrote: [...snip...] > So, IMHO, some action items we might consider: > > * Create a batcave02.rdu that has all our repos, ansible keys and dns > keys. We can then use this to push things out if needed. It shouldn't be > too hard to pull from batcave01 or otherwise keep things in sync. Hey, maybe there's a use for the git mirroring code that Clint was referring to earlier... -- 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 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Re: Pagure on dist-git, the state of things
Reply-to is set to infra@ so we can keep discussion in one place. On Thu, Apr 20, 2017 at 12:08:35PM -0500, Dennis Gilmore wrote: > Can you please report this to releng also? > > Dennis > > > El jue, 20-04-2017 a las 15:45 +0200, Pierre-Yves Chibon escribió: > > Good Morning Everyone, > > > > I figured it has been a while since I reported progress on making > > pagure a > > front-end for dist-git. > > > > So here is a small status update. > > > > What works: > > - Well currently pagure is working as a front-end for dist-git in > > stg: > > https://src.stg.fedoraproject.org/pagure/ > > - Hosting repos, browsing them, creating PR works all fine (w/ one , > > see > > below) > > - Features we want to exclude have been turned off (no user > > management on the > > pagure side) > > > > What does not work: > > - Syncing the ACLs from pkgdb to gitolite takes ~3 minutes in prod, > > in stg, the > > updated script in stg (which sync the ACLs from pkgdb to gitolite > > and pagure) > > runs in ~30/35 minutes (if it doesn't crash, which my last run just > > did) > > This is a blocker since it means it takes 30 to 35 minutes for > > someone to get > > access to their git repo or (worse) their fork > > - This pagure instance has the same issue as the main one, including > > a heisenbug > > we're trying to track but have had no luck reproducing so far :( > > > > What needs to be done: > > - Fix the sync script > > - Make it *way* faster than it is > > - Make it creates the project on pagure using the releng user > > rather than > > relying on the first contributor it finds in the list of > > maintainers > > - Make fedmsg-genacls be triggered on pagure's fork fedmsg message > > so that we > > re-generate the gitolite configuration file when someone forks a > > project > > (and thus give them access to their fork) > > - Once above is done: call for more testers > > > > In the future: > > - I think we will want to deprecate pkgdb entirely, so while the work > > above is > > important, ideally it won't be there for too long. > > - With pkgdb out of the loop, we'll need to figure some things out: > > - Where/How to store the contact info for bugzilla > > - Not sure relying on pagure's ACLs there is the way to go since > > we would > > loose a level of granularity in the ACLs that I know people > > like and ask > > for (having commit w/o being on the CC list in bugzilla or > > being on the CC > > list w/o being a packager) > > - How/when to require people be part of the packager group in FAS? > > - Since one of the idea of pagure is to make it easier for > > "drive-by" > > contribution to spec files, requiring to be a packager should > > only be > > there for maintainers, but pagure doesn't have this level of > > information/requirement, so we would need to find something or > > some place > > to add this requirement or see if that requirement still stands > > > > This is all I can think of for now, I'll update this thread if I come > > up with > > more ideas/challenges. > > > > > > Have a nice day, > > Pierre > > ___ > > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > > To unsubscribe send an email to infrastructure-leave@lists.fedoraproj > > ect.org > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org -- 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 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Review for PR on ansible
I'm trying to add to the filter on the ircbot for Magazine so it
doesn't output anything that concerns Council in Pagure. Is this
right, or even sane?
* * *
diff --git a/roles/fedmsg/irc/templates/ircbot.py
b/roles/fedmsg/irc/templates/ircbot.py
index 2b2e0c3..0dcb0e1 100644
--- a/roles/fedmsg/irc/templates/ircbot.py
+++ b/roles/fedmsg/irc/templates/ircbot.py
@@ -446,12 +446,13 @@ config = dict(
nickname='fm-magazine',
{% endif %}
channel='#fedora-magazine',
-# If the word modularity appears in any message, forward it.
+# If the word magazine appears in any message, forward it.
filters=dict(
topic=[
'^((?!(pagure|planet|badges|fas.group|mailman|meetbot\.meeting)).)*$',
],
-body=['^((?!(magazine|Magazine)).)*$'],
+body=['^((?!(magazine|Magazine)).)*$',
+ "u'namespace': u'Fedora-Council'"],
),
),
--
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
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Re: https blogs?
On Tue, Feb 14, 2017 at 09:52:53PM +0100, Robert Mayr wrote: > Il 14/feb/2017 08:52 PM, "Kevin Fenzi" ha scritto: > > In the past we haven't bothered to make fedoraplanet.org https because > > some/many of the blogs that are aggregated there are http. However, now > > with the advent of letsencrypt, I wonder if we shouldn't revisit that. > > > > I noticed this again due to a recent gnome planet post: > > http://nibblestew.blogspot.com/2017/02/enabling-https-is-easy.html > > > > Proposal: > > > > * We get a https cert for fedoraplanet.org and enable it. > > (of course right now it will show lots of insecure content which will > > be anoying support wise as people ask us about it, but no more so than > > 'why isn't it https enabled'). > > > > * We send out an announcement asking everyone who has a blog aggregated > > on fedoraplanet to https enable their blogs. > > > > * We have some deadline (like 6 months? a year? less?) and after that > > point we drop all the http blogs and only allow https. > > > > There's no real security advantage here, other than making more traffic > > on the net encrypted, which I think is a good goal. > > > > What do folks think? Doable? To harsh? Pointless? > > I think it is not only doable easily, but also an advantage for the blog > owners we collect on fedoraplanet. > Maybe a deadline is the right way here, probably 6 month is not enough, but > what about the end of the year? This could also be useful to clean up > abandoned blogs from people who are not posting anything anymore. > Just my thoughts on this topic. Generally in favor here. However, two things to add: (1) A year seems reasonable for this. We're not under pressure here, no need to pass it on to others either. (2) If this is truly important, infra team should (a) make themselves available to consult on how to fix, and/or (b) create a couple simple HOWTOs for the most prevalent self-hosted services. No need for us to carry large numbers of inactive blogs on the roll, and this is a good way to find out which are still maintained. At the same time, we need to balance the ability to give non-technical community members a voice. -- 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 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Re: Migrating license agreement from FAS2 to FAS3
On Thu, Nov 03, 2016 at 12:18:33PM +0100, Pierre-Yves Chibon wrote: > Good Morning Everyone, > > This morning I started looking at migration our license agreements from FAS2 > to > FAS3. > > We currently have 8 CLAs in FAS2: > - cla_dell > - cla_done > - cla_ibm > - cla_fedora > - cla_redhat > - cla_click > - cla_intel > - cla_fpca > > For the moment, in the migration script I created a dummy license agreement: > `cla_fpca` and migrated all the people member of the `cla_fpca` group in FAS2 > as > having signed that new license agreement. > > The question I have is basically: do we want to migrate all 8 CLAs by creating > their respective LAs in FAS3 and migrating their members or are we only > interested in the FPCA group these days? > > Thoughts? I think some of the alternate groups have value still to some Fedora participants. We may want to consult Spot, who knows more about the history of those groups. -- 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 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
FAS3 meetup recap 2016-Oct-18
Attendees: Xavier Lamien, Patrick Uiterwijk, Pierre-Yves Chibon, Paul Frields Agenda: Determine what remains to be done on FAS3 to get a new instance for testing followed by production deployment * * * * Features needing forward-porting: -> Basset -> IPA Sync -> python-fedora * Token support required for Hubs support * How to integrate with Ipsilon? - From FAS3 side, need a way to request token from Ipsilon and get it back into FAS3 * Cross-app authentication -> hubs to FAS, fedocal, pkgdb, bodhi... * Flock dead-line was F25-beta freeze (which we're past) * At Flock, FAS2 issue --> dropped FAS3 data until we can get security audit of FAS3 * Also need update to db-migration script -- new license agreement function * Convert this away from mechanism we used in FAS2 * This gives us a way to know which agreement(s) users agreed to, and/or prompt them accordingly * AGREED: Convert current FPCA agreement into FAS3 * Build clean Ansible playbook for FAS3 with a true role, but perhaps do this as a github.com/fedora-infra/fas3-ansible (or other repo e.g. Pagure) * Is there a method for getting client certificates in FAS3? Yes. Go to settings page for this. The certificate is no longer tied to the whole app, but rather per-group. * So for Koji this would be tied to @packager group. * Further, you can also optionally require SSH key for a group PROPOSED: Merge FAS3.0 to development branch when we switch over, since we still have FAS2 elsewhere supybot-fedora also has a fas3 branch which should be ready Timezone handling... AGREED: keep things postgresql-only, storing TZ for the moment. We will add an issue to backlog to handle this down the road to make FAS3 more db-agnostic ACTIONS: * Security audit (already started, using latest git code) --> ETA unknown, will have it soon * Meet to discuss FAS internals --> ETA: 2016-Oct-20, 0800 UTC (10:00 Paris/Amsterdam) * Update db-migration script for CLA handling --> ETA: 2016-Oct-25 * Integration with Ipsilon --> ETA: 2016-Nov-01 * FAS3 in staging --> ETA: 2016-Nov-01 * Update python-fedora --> ETA: 2016-Nov-08? * and deprecate functions where needed * Port all the apps using it (but that's for later) * Make this a major version update * Target for production: 2016-Dec-01? * If we don't make this, slip to early January LATER (for separate followup, not FAS3 blocking) * Updating all flask based apps * kill off flask-fas-openid? <-- happy Patrick -- will break most of our flask app :( * Patrick: would like to make it just use flask-openid transparently without anyone noticing :-) * ouch, we will need to line up changes here then -> plan for later?1 * agreed, I moved this to its own task since it's not (IIUC) strictly required for FAS3 to be deployed -- 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 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Re: Is it OK if I move fpaste to pagure?
On Thu, Jun 09, 2016 at 04:29:13PM +0100, Ankur Sinha wrote: > On Thu, 2016-06-09 at 07:55 -0600, Kevin Fenzi wrote: > > Fine with me. ;) > > > > Note that there will likely need to be some changes in fpaste before > > too long. We are looking at moving the server from sticky-notes to > > modernpaste. > > I'll move it and start tinkering with modernpaste then. Hi Ankur, be aware that Ricky Elrod has already done some work to get this toward a staging instance. Please get in touch with him and see how you can help. -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org
FAS3 meeting recap
Pierre, Patrick, Xavier, Szymon, and I met today to talk about FAS3 plans toward staging by end of July. The Etherpad plan is here: http://etherpad.osuosl.org/fas3-staging-plan Here are the meeting details: Minutes: https://meetbot.fedoraproject.org/fedora-apps/2016-05-26/fas3.2016-05-26-16.01.html Minutes (text): https://meetbot.fedoraproject.org/fedora-apps/2016-05-26/fas3.2016-05-26-16.01.txt Log: https://meetbot.fedoraproject.org/fedora-apps/2016-05-26/fas3.2016-05-26-16.01.log.html The minutes aren't too useful because we recorded the planning in the Etherpad. But the log might be useful if you are interested in the topic. There is a follow-up planned for Friday 2016-06-03 at 1600 UTC (12:00pm US-Eastern, 18:00 CEST). -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org
Re: [release] pagure: 2.0
On Fri, Apr 22, 2016 at 05:39:20PM +0200, Pierre-Yves Chibon wrote: > Good Morning everyone, > > The last release of pagure was on March 1st, since then there has been very > many > changes to it, improvements and bug fixes together. > In fact there has been so many changes, that it wasn't worth making this new > release 1.3 and it is instead a 2.0. [...snip...] Congratulations on this milestone, Pierre + Pagure team! -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org
Re: About JS framework
On Thu, Apr 21, 2016 at 08:17:50PM +0530, Ratnadeep Debnath wrote: > Hi, > > On Thu, Apr 21, 2016 at 2:46 PM, Pierre-Yves Chibon > wrote: > > Good Morning Everyone, > > > > Our infrastructure is mostly a python store, meaning almost all our apps are > > written in python and most using wsgi. > > However in python we are using a number of framework: > > * flask for most > > * pyramid for some of the biggest (bodhi, FAS3) > > * Django (askbot, Hyperkitty) > > * TurboGears2 (fedora-packages) > > * aiohttp (python3, async app: mdapi) > > > > While this makes sometime things difficult, these are fairly standard > > framework > > and most of our developers are able to help on all. > > Although there are a number of pros for the above approach, I'd like > to highlight a few downsides too: > - UI and backend development are tightly coupled > - HTML responses from backend are not that reusable > - Not ready for multi platforms > > > However, as I see us starting to look at JS for some of our apps > > (fedora-hubs, > > wartaa...), I wonder if we could start the discussion early about the > > different > > framework and eventually see if we can unify around one. > > This would also allow those of us not familiar with any JS framework to > > look at > > the recommended one instead of picking one up semi-randomly. > > > > So has anyone experience with one or more JS framework? Do you have one that > > would you recommend? Why? > > After doing quite a lot of reading on ReactJS vs Angular2, and based > on instinct, I prefer React because: > - lean and thin, less react specific jargon, mostly javascript > - initially it might have a bit of more learning curve, but once you > get the hang of it, it becomes easier. Unlike Angular2, which is easy > to start, but the learning curve, gets steeper and steeper as you > progress > - React shows errors at compile time itself, rather than on runtime > like Angular2 > - React is lightweight and has a simple API. You don't need to read > react's source code to understand what's happening > > On the other hand: > - Angular2 is a richer framework, easy for new developers to get started with > - I love how nativescript allows you to write native apps for mobile > platforms using Angular2, allowing 80% code reuse > > You can find some useful reads at [1], [2]. > > [1]: https://www.airpair.com/angularjs/posts/angular-vs-react-the-tie-breaker > [2]: > https://medium.freecodecamp.com/angular-2-versus-react-there-will-be-blood-66595faafd51#.5z805rq9p We should also give some thought to the framework(s) that: (1) have robust upstream communities themselves, with active development where appropriate, and (2) have massive uptake in the overall developer realm beyond just our current contributors; ...and balance that against perceived technical excellence, purity, etc. This way we can grow or maintain our ability to on-ramp new contributors to projects we work on. -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org
Re: Fedora 24 Alpha Freeze now over
On Wed, Mar 30, 2016 at 08:45:00AM -0600, Kevin Fenzi wrote: > With the release of Fedora 24 Alpha yesterday, we are now out of > freeze. > > The next freeze is scheduled to start 2016-04-19 for Beta. Nice job, everyone, making this a rather "boring" Alpha release from the internal perspective. :-) -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org
Re: Support levels and RFR adjustments
On Tue, Mar 08, 2016 at 07:22:44PM -0500, David Shier wrote: > I think this is a good idea, maybe add a sub header similar to 'technical > project sites in this region' to differentiate between something that is a > more or less general community forum and the ones where you've got > development types that likely want more focused conversation related to > their projects. Reminder since snipped: The context is that I recommended we use *.fedoracommunity.org for projects outside regular support from the infrastructure team, but which are good to associate with Fedora overall, with COPR being an example. What do we need to do to make this happen, if there are no objections? -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org
COPR builds/services for other distros?
Hi Miroslav, I recently became aware of this info on the buildsys list: https://lists.fedoraproject.org/archives/list/build...@lists.fedoraproject.org/thread/QKGI24LEWKWAVMYTXJFPMXXTPBBWQ554/ (*refers to https://ml.mageia.org/l/arc/dev/2015-11/msg00092.html) I had a few questions: * Do you have an idea what increase in usage will come from extending COPR to Mageia? * Are there other distributions with whom you've discussed extending COPR support that potentially bring along usage increases? * Are Mageia folks (and any other distro interests) aware of the non-production support level of COPR currently? Thanks for any information you can provide. I'm trying to determine if there's any discussion needed about infrastructure resources. This is especially important because Red Hat's internal budget for hardware is already set for the fiscal year that started this month. -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org
COPR builds/services for other distros?
Hi Miroslav, I recently became aware of this info on the buildsys list: https://lists.fedoraproject.org/archives/list/build...@lists.fedoraproject.org/thread/QKGI24LEWKWAVMYTXJFPMXXTPBBWQ554/ (*refers to https://ml.mageia.org/l/arc/dev/2015-11/msg00092.html) I had a few questions: * Do you have an idea what increase in usage will come from extending COPR to Mageia? * Are there other distributions with whom you've discussed extending COPR support that potentially bring along usage increases? * Are Mageia folks (and any other distro interests) aware of the non-production support level of COPR currently? Thanks for any information you can provide. I'm trying to determine if there's any discussion needed about infrastructure resources. This is especially important because Red Hat's internal budget for hardware is already set for the fiscal year that started this month. -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org
Re: Support levels and RFR adjustments
On Mon, Jan 25, 2016 at 10:12:47AM -0700, Kevin Fenzi wrote: > On Mon, 25 Jan 2016 15:29:05 +0100 > Miroslav Suchý wrote: > > > I personally do not like fedorainfracloud.org. It is fine for > > hostnames of machines in cloud. I would rather see some subdomain > > under fedoraproject.org - e.g. .devel.fedoraproject.org > > or .playground.fedoraproject.org or something similar. > > Well, it's in the cloud, so it's more descriptive, IMHO. > And sorry for the quick change, we needed new ssl certs very soon, so > thought it would make sense to get them with these names. > > > > I personally dislike the change of copr.fedoraproject.org to > > copr.fedorainfracloud.org. We have been usin this name for past two > > years and it is referenced a lot (35k by Google): > > https://www.google.com/search?lr=&hl=cs&q=%22copr.fedoraproject.org%22&oq=copr.fedoraproject.org%22 > > This is not pure technical decision but marketing decision as well. A > > lot of people are treating it as integral part of Fedora. So instead > > of changing hostname I would rather start RFR process. > > Well, for what? We have talked about moving the non builder parts of > copr into regular infrastructure in the past, but we didn't do it for > whatever reasons. Doing so would get us some advantages and some > problems: > > Advantages: could use the proxy system to cache things and also do HA > with multiple frontends or possibly even backends if we wanted. Could > mean frontend/backend/sign/git are more stable as they are not on the > cloud. > > Disadvantages: would need to figure out how to shuffle around storage, > as we have copr storage tied to the cloud right now. It would be some > work to move things around and get it all working right. > > > I think that some icon at the top or link at the bottom of page, > > which will clearly state the level of support will do the same from > > technical POV, but will be better solution from marketing POV. > > The problem with that is when the thing is down, users have no way to > look at that. They just see it's down and have the expectation that > they already do in their minds. I was talking to Kevin about this today and came up with what I think is a good solution. We have a fedoracommunity.org domain which already is provided for communities that want to set up Fedora related sites. Those sites are: * understood as owned and managed by someone other than the Fedora infrastructure team * granted trademark approval to use Fedora marks to associate closely with the Fedora Project Currently this domain is used exclusively for local communities. For example, a Czech community might run a site for Czech speaking community members at cz.fedoracommunity.org, and we simply provide a DNS pointer for them. However, the use case is exactly the same for a technical project not hosted/managed by the Infrastructure team. The owner seeks to brand it as Fedora and associate it with the Project, which is good for everyone involved. But it doesn't automatically inherit support from the team. Expanding fedoracommunity.org for this use makes a lot of sense to me. *And* it brings an immediate affiliation with Fedora just from the name, without misunderstanding. It's very clear the site is community run/supported. Thoughts? -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org
Re: FAS2 to FAS3 DB migration - state and questions
On Tue, Nov 17, 2015 at 11:04:20AM +0100, Pierre-Yves Chibon wrote: > * Tables of FAS2 I do not know what to do with: > - Log > We have some logs in the DB, we might be able to convert them but the > amount > of information missing for the new log table (people_activity_log) might > not > make it worth > - bugzilla_queue > There are a few entries in there, but I do not know what it is meant for > nor > used by Might this have something to do with a FAS change that results in a request to Bugzilla admins for BZ group membership? -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org
[PATCH] Bring back the "chair" alias, just one place to list FPL
--- roles/fas_client/files/aliases.template | 9 ++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/roles/fas_client/files/aliases.template b/roles/fas_client/files/aliases.template index 7b647f1..33dcd29 100644 --- a/roles/fas_client/files/aliases.template +++ b/roles/fas_client/files/aliases.template @@ -116,6 +116,9 @@ board: advisory-bo...@lists.fedoraproject.org chairman: chair directors: board +# This is the one place to change FPL identity, re: +# https://fedoraproject.org/wiki/Project_Leader +chair: mattdm # FESCo fesco-chair: kevin @@ -137,9 +140,9 @@ fudcon-cfp: /dev/null fudcon-paper:fudcon-cfp # flock -flockpress: rsuehle,spot,mattdm -flockinfo: rsuehle,spot,mattdm -flock-staff: rsuehle,spot,mattdm,jwboyer +flockpress: rsuehle,spot,fpl +flockinfo: rsuehle,spot,fpl +flock-staff: rsuehle,spot,fpl,jwboyer # gnome backups gnomebackup: back...@gnome.org -- 2.4.3 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org http://lists.fedoraproject.org/postorius/infrastructure@lists.fedoraproject.org
Re: FAS3 and next steps
On Thu, Aug 27, 2015 at 10:00:14AM -0400, Paul W. Frields wrote: > On Wed, Aug 26, 2015 at 11:07:20AM -0400, Paul W. Frields wrote: > > Sounds good. If anyone is interested in attending, here is the link > > for the video conference: > > > > CORRECTED LINK: https://bluejeans.com/466265686/7289 > > > Attendees will need to use Firefox and install the Blue Jeans plugin. > > If you're using a HiDPI display, due to an issue with display handling > > you may need to export an environment setting of GDK_SCALE=1 for > > Firefox to work properly. In other words, launch this way: > > > > $ GDK_SCALE=1 firefox & > > > > I'll look into getting a recording of the video we can post for later > > consumption, too. Here's an update from Christian: > Hello, > > thanks a lot for attending to the demo. I have made the Blue Jeans > recording public: > >https://bluejeans.com/s/8wHC/ > > By the way thanks for the ringing phone right at the beginning of the > call. It reminded me to press the record button. :) The recording is > missing 5 minutes of the general introduction. It's all covered in the > presentation. > > The slides are on my fedorapeople account: > > https://cheimes.fedorapeople.org/freeipa_community_portal_20150827.pdf > > If you have further questions, please feel free to contact me. I'm > back on Monday September 14th. Thanks Christian for the demo! -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org http://lists.fedoraproject.org/postorius/infrastructure@lists.fedoraproject.org
Re: FAS3 and next steps
On Wed, Aug 26, 2015 at 11:07:20AM -0400, Paul W. Frields wrote: > On Tue, Aug 25, 2015 at 12:22:06PM -0600, Stephen John Smoogen wrote: > > On 25 August 2015 at 08:18, Paul W. Frields wrote: > > > On Thu, Aug 20, 2015 at 10:45:58AM -0400, Paul W. Frields wrote: > > >> On Thu, Aug 20, 2015 at 10:31:14AM -0400, Paul W. Frields wrote: > > >> > Hi all, > > >> > > > >> > I had a short conversation with Xavier at Flock and it sounded like > > >> > things are coming along well with FAS3: > > >> > <https://fedoraproject.org/wiki/User:Laxathom/Drafts:FAS3.0#Status> > > >> > > > >> > Xavier and I agreed we should have a longer discussion about this with > > >> > the team after the conference. So I figured this was worth bringing > > >> > up here so everyone can contribute. A couple things (and we can split > > >> > this thread up if needed): > > >> > > > >> > 1. FAS3 roadmap > > >> > > > >> > How much more work is needed to make FAS3 test- and then > > >> > deployment-ready? And since obviously this will be an important > > >> > infrastructure change, is it a goal to try to deploy after F23 GA? > > >> > Further out? > > >> > > > >> > 2. FreeIPA web UI demo > > >> > > > >> > One of the developers on the freeIPA project, Christian Heimes, > > >> > reached out to me after Flock to ask whether he could present it to > > >> > the infrastructure team. He's been working on some additional web-UI > > >> > bits for administering freeIPA. He was hoping this team could offer > > >> > critique and suggest improvements to make the workflows more suitable > > >> > for a self-signup, free software project like ours. It would probably > > >> > be a video demo, venue TBD. > > >> > > > >> > I don't see this being at odds with FAS3 deployment, although if > > >> > anyone sees things differently, please speak up. Hopefully the > > >> > questions above support that goal too. > > >> > > > >> > If a few years down the line, a different solution (not necessarily > > >> > freeIPA) makes sense for us, then great, we can consider it. IMHO if > > >> > input from the infrastructure team makes freeIPA more suitable for > > >> > free software projects, it helps everyone. It's also helpful for the > > >> > freeIPA roadmap if their devs know when FAS3 will be up, and what > > >> > feature parity is needed for projects like ours to find their work > > >> > useful in the future. > > >> > > > >> > Are there people on the team willing to attend this demo? > > >> > > >> Instead of "administering freeIPA" I should have noted this demo would > > >> include things like installation + configuration, but also user > > >> self-administration. > > > > > > Christian just suggested this timeslot in IRC, this Thursday Aug 27 at > > > 1400 UTC: <http://timeanddate.com/s/2vfk> > > > > > > I would expect at least a couple folks from Red Hat on this team to > > > attend, but hopefully this is of broader interest to the community as > > > well. (Hi Xavier!) > > > > Hi Paul > > > > wanted to give a heads up on the thread. Kevin thinks he can make the > > meeting at 0800 MT (1400 UTC). I can be in for part of the meeting but > > will have another meeting at the half hour point. > > Sounds good. If anyone is interested in attending, here is the link > for the video conference: > CORRECTED LINK: https://bluejeans.com/466265686/7289 > Attendees will need to use Firefox and install the Blue Jeans plugin. > If you're using a HiDPI display, due to an issue with display handling > you may need to export an environment setting of GDK_SCALE=1 for > Firefox to work properly. In other words, launch this way: > > $ GDK_SCALE=1 firefox & > > I'll look into getting a recording of the video we can post for later > consumption, too. > > -- > 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 -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org http://lists.fedoraproject.org/postorius/infrastructure@lists.fedoraproject.org
Re: FAS3 and next steps
On Tue, Aug 25, 2015 at 12:22:06PM -0600, Stephen John Smoogen wrote: > On 25 August 2015 at 08:18, Paul W. Frields wrote: > > On Thu, Aug 20, 2015 at 10:45:58AM -0400, Paul W. Frields wrote: > >> On Thu, Aug 20, 2015 at 10:31:14AM -0400, Paul W. Frields wrote: > >> > Hi all, > >> > > >> > I had a short conversation with Xavier at Flock and it sounded like > >> > things are coming along well with FAS3: > >> > <https://fedoraproject.org/wiki/User:Laxathom/Drafts:FAS3.0#Status> > >> > > >> > Xavier and I agreed we should have a longer discussion about this with > >> > the team after the conference. So I figured this was worth bringing > >> > up here so everyone can contribute. A couple things (and we can split > >> > this thread up if needed): > >> > > >> > 1. FAS3 roadmap > >> > > >> > How much more work is needed to make FAS3 test- and then > >> > deployment-ready? And since obviously this will be an important > >> > infrastructure change, is it a goal to try to deploy after F23 GA? > >> > Further out? > >> > > >> > 2. FreeIPA web UI demo > >> > > >> > One of the developers on the freeIPA project, Christian Heimes, > >> > reached out to me after Flock to ask whether he could present it to > >> > the infrastructure team. He's been working on some additional web-UI > >> > bits for administering freeIPA. He was hoping this team could offer > >> > critique and suggest improvements to make the workflows more suitable > >> > for a self-signup, free software project like ours. It would probably > >> > be a video demo, venue TBD. > >> > > >> > I don't see this being at odds with FAS3 deployment, although if > >> > anyone sees things differently, please speak up. Hopefully the > >> > questions above support that goal too. > >> > > >> > If a few years down the line, a different solution (not necessarily > >> > freeIPA) makes sense for us, then great, we can consider it. IMHO if > >> > input from the infrastructure team makes freeIPA more suitable for > >> > free software projects, it helps everyone. It's also helpful for the > >> > freeIPA roadmap if their devs know when FAS3 will be up, and what > >> > feature parity is needed for projects like ours to find their work > >> > useful in the future. > >> > > >> > Are there people on the team willing to attend this demo? > >> > >> Instead of "administering freeIPA" I should have noted this demo would > >> include things like installation + configuration, but also user > >> self-administration. > > > > Christian just suggested this timeslot in IRC, this Thursday Aug 27 at > > 1400 UTC: <http://timeanddate.com/s/2vfk> > > > > I would expect at least a couple folks from Red Hat on this team to > > attend, but hopefully this is of broader interest to the community as > > well. (Hi Xavier!) > > Hi Paul > > wanted to give a heads up on the thread. Kevin thinks he can make the > meeting at 0800 MT (1400 UTC). I can be in for part of the meeting but > will have another meeting at the half hour point. Sounds good. If anyone is interested in attending, here is the link for the video conference: https://bluejeans.com/466265686/ Attendees will need to use Firefox and install the Blue Jeans plugin. If you're using a HiDPI display, due to an issue with display handling you may need to export an environment setting of GDK_SCALE=1 for Firefox to work properly. In other words, launch this way: $ GDK_SCALE=1 firefox & I'll look into getting a recording of the video we can post for later consumption, too. -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org http://lists.fedoraproject.org/postorius/infrastructure@lists.fedoraproject.org
Re: Migration of lists.fedorahosted.org failed
On Tue, Aug 25, 2015 at 04:19:17PM +0200, Aurelien Bompard wrote: > > Once you can implement upstream, do you plan to try again > > with a patched version while we await an upstream point-release? > > Yes, that's my plan. My RPM already carries a few patches that are not > released, and even still under review. I update them (and eventually > remove them :-) ) as they get reviewed. Brilliant. Thanks Aurélien! -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org http://lists.fedoraproject.org/postorius/infrastructure@lists.fedoraproject.org
Re: FAS3 and next steps
On Thu, Aug 20, 2015 at 10:45:58AM -0400, Paul W. Frields wrote: > On Thu, Aug 20, 2015 at 10:31:14AM -0400, Paul W. Frields wrote: > > Hi all, > > > > I had a short conversation with Xavier at Flock and it sounded like > > things are coming along well with FAS3: > > <https://fedoraproject.org/wiki/User:Laxathom/Drafts:FAS3.0#Status> > > > > Xavier and I agreed we should have a longer discussion about this with > > the team after the conference. So I figured this was worth bringing > > up here so everyone can contribute. A couple things (and we can split > > this thread up if needed): > > > > 1. FAS3 roadmap > > > > How much more work is needed to make FAS3 test- and then > > deployment-ready? And since obviously this will be an important > > infrastructure change, is it a goal to try to deploy after F23 GA? > > Further out? > > > > 2. FreeIPA web UI demo > > > > One of the developers on the freeIPA project, Christian Heimes, > > reached out to me after Flock to ask whether he could present it to > > the infrastructure team. He's been working on some additional web-UI > > bits for administering freeIPA. He was hoping this team could offer > > critique and suggest improvements to make the workflows more suitable > > for a self-signup, free software project like ours. It would probably > > be a video demo, venue TBD. > > > > I don't see this being at odds with FAS3 deployment, although if > > anyone sees things differently, please speak up. Hopefully the > > questions above support that goal too. > > > > If a few years down the line, a different solution (not necessarily > > freeIPA) makes sense for us, then great, we can consider it. IMHO if > > input from the infrastructure team makes freeIPA more suitable for > > free software projects, it helps everyone. It's also helpful for the > > freeIPA roadmap if their devs know when FAS3 will be up, and what > > feature parity is needed for projects like ours to find their work > > useful in the future. > > > > Are there people on the team willing to attend this demo? > > Instead of "administering freeIPA" I should have noted this demo would > include things like installation + configuration, but also user > self-administration. Christian just suggested this timeslot in IRC, this Thursday Aug 27 at 1400 UTC: <http://timeanddate.com/s/2vfk> I would expect at least a couple folks from Red Hat on this team to attend, but hopefully this is of broader interest to the community as well. (Hi Xavier!) -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org http://lists.fedoraproject.org/postorius/infrastructure@lists.fedoraproject.org
Re: Migration of lists.fedorahosted.org failed
On Fri, Aug 21, 2015 at 04:40:34PM +0200, Aurelien Bompard wrote: > Hey folks, > > I'm sorry to announce that I had to rollback the migration of > lists.fedorahosted.org to Mailman 3. > There's a missing feature again, that is heavily used by two lists on > this server, it's the header_filter_rules. It lets the admin decide on > header regexes that will set a different action on the email > (rejecting, holding, etc). It's designed for spam filtering: detect > X-Spam-Flag and drop the email. Those lists use it to filter commit > emails on the master branch only and drop the rest. The migration to > Mailman3 caused an email avalanche on their list when someone pushed a > branch, so... not very nice :-/ > > In Mailman3 this is implemented differently, you can only have a > global action set for emails whoose headers match the filters. Not per > regex as in Mailman 2, not even per list, only per server. > So I'll discuss this on the mailman dev list and write this feature, > in the meantime I had to rollback the migration. > > I wish it had worked better, sorry for the inconvenience. Sorry this didn't work out better (and that I'm catching up to list mail late). Once you can implement upstream, do you plan to try again with a patched version while we await an upstream point-release? -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org http://lists.fedoraproject.org/postorius/infrastructure@lists.fedoraproject.org
Re: FAS3 and next steps
Instead of "administering freeIPA" I should have noted this demo would include things like installation + configuration, but also user self-administration.
Re: FAS3 and next steps
Instead of "administering freeIPA" I should have noted this demo would include things like installation + configuration, but also user self-administration.
Re: FAS3 and next steps
Instead of "administering freeIPA" I should have noted this demo would include things like installation + configuration, but also user self-administration.
Re: FAS3 and next steps
On Thu, Aug 20, 2015 at 10:31:14AM -0400, Paul W. Frields wrote: > Hi all, > > I had a short conversation with Xavier at Flock and it sounded like > things are coming along well with FAS3: > <https://fedoraproject.org/wiki/User:Laxathom/Drafts:FAS3.0#Status> > > Xavier and I agreed we should have a longer discussion about this with > the team after the conference. So I figured this was worth bringing > up here so everyone can contribute. A couple things (and we can split > this thread up if needed): > > 1. FAS3 roadmap > > How much more work is needed to make FAS3 test- and then > deployment-ready? And since obviously this will be an important > infrastructure change, is it a goal to try to deploy after F23 GA? > Further out? > > 2. FreeIPA web UI demo > > One of the developers on the freeIPA project, Christian Heimes, > reached out to me after Flock to ask whether he could present it to > the infrastructure team. He's been working on some additional web-UI > bits for administering freeIPA. He was hoping this team could offer > critique and suggest improvements to make the workflows more suitable > for a self-signup, free software project like ours. It would probably > be a video demo, venue TBD. > > I don't see this being at odds with FAS3 deployment, although if > anyone sees things differently, please speak up. Hopefully the > questions above support that goal too. > > If a few years down the line, a different solution (not necessarily > freeIPA) makes sense for us, then great, we can consider it. IMHO if > input from the infrastructure team makes freeIPA more suitable for > free software projects, it helps everyone. It's also helpful for the > freeIPA roadmap if their devs know when FAS3 will be up, and what > feature parity is needed for projects like ours to find their work > useful in the future. > > Are there people on the team willing to attend this demo? Instead of "administering freeIPA" I should have noted this demo would include things like installation + configuration, but also user self-administration. -- 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
Re: FAS3 and next steps
Instead of "administering freeIPA" I should have noted this demo would include things like installation + configuration, but also user self-administration.
FAS3 and next steps
Hi all, I had a short conversation with Xavier at Flock and it sounded like things are coming along well with FAS3: <https://fedoraproject.org/wiki/User:Laxathom/Drafts:FAS3.0#Status> Xavier and I agreed we should have a longer discussion about this with the team after the conference. So I figured this was worth bringing up here so everyone can contribute. A couple things (and we can split this thread up if needed): 1. FAS3 roadmap How much more work is needed to make FAS3 test- and then deployment-ready? And since obviously this will be an important infrastructure change, is it a goal to try to deploy after F23 GA? Further out? 2. FreeIPA web UI demo One of the developers on the freeIPA project, Christian Heimes, reached out to me after Flock to ask whether he could present it to the infrastructure team. He's been working on some additional web-UI bits for administering freeIPA. He was hoping this team could offer critique and suggest improvements to make the workflows more suitable for a self-signup, free software project like ours. It would probably be a video demo, venue TBD. I don't see this being at odds with FAS3 deployment, although if anyone sees things differently, please speak up. Hopefully the questions above support that goal too. If a few years down the line, a different solution (not necessarily freeIPA) makes sense for us, then great, we can consider it. IMHO if input from the infrastructure team makes freeIPA more suitable for free software projects, it helps everyone. It's also helpful for the freeIPA roadmap if their devs know when FAS3 will be up, and what feature parity is needed for projects like ours to find their work useful in the future. Are there people on the team willing to attend this demo? -- 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
Re: Move to mailman3
On Wed, Aug 05, 2015 at 10:45:21AM +0200, Pierre-Yves Chibon wrote: > Good morning everyone, > > As you may know, mailman3 has been released and with it the new archiver > bridging mailing lists and forums: HyperKitty. > > Some of the automated mailing list have been already migrated to mailman3, > but we still need to migrate 'live' mailing list (ie: having user actually > discussing, not just bot sending emails). > There has been thoughts to use the infrastructure list as a potential first > list > to migrate. > > Thoughts on this? +1 for same reasons already stated by Patrick and others. -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Pruning sponsors list
On Tue, Aug 04, 2015 at 02:52:16PM -0400, Paul W. Frields wrote: > Our website includes a sponsor list, e.g.: > <https://getfedora.org/en/sponsors> > > A little digging plus help from Jared Smith showed that Arrival > Telecom and Technomonk are no longer sponsoring Fedora service. They > each provided DID service back when we ran Fedora Talk. So unless > there are objections, I'll trim them from future builds of the > website. I didn't see any objections, so I'll provide said patch. -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Pruning sponsors list
Our website includes a sponsor list, e.g.: <https://getfedora.org/en/sponsors> A little digging plus help from Jared Smith showed that Arrival Telecom and Technomonk are no longer sponsoring Fedora service. They each provided DID service back when we ran Fedora Talk. So unless there are objections, I'll trim them from future builds of the website. -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Fedora Hubs meetup
On Thu, May 14, 2015 at 10:51:36AM -0400, David Gay wrote: > Hi all. > > Based on the WIG responses, I propose we have the next meetup to discuss > Fedora Hubs on Thursday, May 21 at 12:00pm US/Pacific. I do believe that is > 7:00 PM UTC. This is probably our best shot at having a good amount of folks > attend. It's obviously quite hard to schedule a meeting for 20 people. Unless > there is a huge outcry, we could probably go ahead and set up Bluejeans for > this time. Not sure whether my response made it to list previously, but +1. Schedule away! -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Cantas open source card app?
I separately had both Adam Miller and Stephen Smoogen ask me about "card" based project tracking applications. I responded to both that there's a 100% open source app for that called Cantas: https://github.com/onepiecejs/nodejs-cantas I believe the major portion of its dependencies are all in Fedora already, probably thanks in part to Ralph Bean sorting through a ton of nodejs stuff earlier. I've seen numerous folks using apps like this, or Trello, or other similar, to get development done faster and with good accountability. Sometimes they're using Agile with a big A, sometimes they're just trying to be more agile with a little a. I think Adam's intent was to try to use this kind of system for upcoming projects that involve Fedora rel-eng and infrastructure. If Fedora data like that is in it, I'd love to see that eventually be tracked in Fedora itself. While it doesn't have to be a blocker to moving forward, it could end up being useful to more people. Is this of interest to anyone else in Fedora Infrastructure? -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: crowdsourcing an interview on git
On Wed, Apr 01, 2015 at 10:49:57AM -0600, Kevin Fenzi wrote: > On Tue, 31 Mar 2015 16:48:17 -0400 > Matthew Miller wrote: > > > Hi everyone! Linux Foundation is running a series on Git for its 10th > > anniversary. They asked me a few questions, and I thought it might be > > even better to get a community answer from the whole infrastructure > > team. So, if you have anything interesting to say to any of these, say > > it, and I'll wrap up the responses into a unified Fedora Whole. I need > > to respond by Friday. > > > > * Why does Fedora use Git? > > It's known by most all developer/free software types these days, it's > distributed and it's got a lot of docs and folks that can help with > issues. > > > > * What makes Git such a great tool? > > For simple things/workflows it's pretty simple. Because it's distributed, you can be productive on a plane or at other locations without a network. > > * How many developers do you have collaborating on git? > > I guess that depends on what the question means by "you" here. ;) > > We have had 45 people commit at one time or another to our ansible > repo, and 163 to our old puppet repo. > > There's 1633 people in the fedora packager group and 19857 package > repos. (But some of those are dead.packaged). > > > * How much do you personally use it? (estimates are great) > > Many times a day. > > > * What's Fedora's most active git repo right now and why? > > Thats hard to say, we don't have a central place for all of them... > http://pkgs.fedoraproject.org/cgit/?s=idle > I suspect kernel gets updates most days. > The infrastructure ansible repo gets updates most days. > > > * What is your favorite pro tip for using git? > > Always run 'git status' and 'git diff' before commiting/pushing. That > can show you that you have unrelated other changes you might not want > to push. If you make really bad mistakes, you can use 'git reflog' to reverse even egregious issues. Also, 'git rebase -i' is great for times you forgot to keep your commits focused on the topic at hand. You can merge, split up, or edit diffs to make sure your commits are useful when you come back to them weeks or months later. -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Pkgdb2 1.24
On Wed, Mar 18, 2015 at 05:00:31PM +0100, Pierre-Yves Chibon wrote: > On Wed, Mar 18, 2015 at 09:44:56AM -0600, Kevin Fenzi wrote: > > On Wed, 18 Mar 2015 15:25:48 +0100 > > Pierre-Yves Chibon wrote: > > > > > Hi everyone, > > > > > > The next pkgdb2 release (1.24) will be a pretty big releases, to give > > > you an idea this is its current changelog: > > > > ...snip good stuff... > > > > > Since these changes might be pretty big and impact multiple person, I > > > would like to hear when people think it would be best to make the > > > release. > > > > > > Note: I will not do it today, but basically I could from tomorrow :) > > > > I'd say do it tomorrow. ;) > > > > Well, is it already in stg and working there? > > The main changes are running in stg yes (the new package/branch requests), the > other changes are either running already in prod (backported to 1.23) or are > small enough that I do not expect any problem. > > > I'd say push to staging and make sure there's nothing obviously > > broken, then go to prod. > > Sure, I can cut a 1.24 tomorrow and push it to prod. > > > > Note2: As it will likely take a little time for people to get > > > adjusted to the new workflow (that needs to be documented & so on), > > > there will likely be a time for pkgdb admins and releng when they > > > will have to check both bugzilla and pkgdb. > > > > Right. However, we should be able to roll this out and keep using the > > old process for new packages and branches right? ie, maintainers don't > > even need to know this is there unless we ask them to try it? > > Yes, since we do not touch bugzilla nor the way packages are created in pkgdb, > the old process will work just fine. > > > So, we should be able to put it in place and have a small group of > > folks test things and fix issues, and only then announce to maintainers > > to switch to the new process. > > Sounds good :) > Only people might notice the big blue button on the front page: > https://admin.stg.fedoraproject.org/pkgdb/ > > That's one way to make them aware I guess ;-) I'd suggest two announcements: One by Pierre through his blog, and one to the devel@ list so interested people can participate in testing and maintainers are aware of how the new functions impact (or don't impact) their work for 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/ The open source story continues to grow: http://opensource.com ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Questions about ask.fp.o
On Wed, Mar 11, 2015 at 03:27:58PM -0600, Pete Travis wrote: > On Mar 11, 2015 3:01 PM, "Paul W. Frields" wrote: > > On Wed, Mar 11, 2015 at 06:28:05PM +, Ankur Sinha wrote: > > > On Wed, 2015-03-11 at 11:58 -0400, Paul W. Frields wrote: > > > https://fedorahosted.org/fedora-infrastructure/ticket/4187 > > > > That's fine, but how does someone not familiar with ask.fp.o know to > > do that? Why not change the link and investigate the problem in the > > background? > > > We should definitely fix this, and probably add more signal to the > feedback/help section. Many site moderators (as defined by contribution > karma) don't idle in #fedora-ask - mostly just admins like myself or Ankur > and a few others. I would rate this a lower priority than the askbot > upgrade, though. Probably -- after the upgrade, if the link isn't magically fixed, :-) I recommend changing it. > > > The moderation queue in the version we're using is quite badly designed > > > - it's an upstream issue - that's how askbot is. All those posts aren't > > > actually waiting for moderation - even if a mod approves a post, it > > > still seems to show up in another mod's moderation queue :( > > > > OK, I understand. What should I do about the 10,000+ items in my > > queue? > > Skim over the most recent ones for obvious dupes and offensive or harmful > posts. Once you hit one that's already been approved or deleted (this is > where I check the fedmsg links), it's fairly safe to assume all subsequent > posts have been moderated. Askbot moderation means that each post must be > moderated by each moderator; there is no shared moderation queue. However, > anything you do to an already moderated post has no additional affect. > Bonus, askbot defines new users as "watched users" and the can be > administratively changed to "approved users" - which has no noticeable > effect. We're really hoping the new version works better. Is there a way for me to clear from the queue the 9900+ items I'm unlikely to skim? Or is it likely the upstream update will remove the problem? > > > We informed upstream about this and they've apparently rewritten the > > > moderation part and made a new release. None of us have managed to find > > > the cycles to update the package and test it out in staging so that we > > > can update the production instance. It's high time I looked into it, > > > though - it's been on my todo list for quite a while. > > > > I'm happy you are looking into it, and I see from your other post > > there is an updated package. > > > > However, this raises a potential issue about future maintenance. It > > appears the site gets quite a bit of visitors and use. What's the > > plan to find cycles for the maintenance required for such a service? > > I found cycles to update the package and test locally, but haven't found > time to test in staging yet. maybe this weekend, if I can work it in with > the other Fedora commitments I've made. As for a plan... well, I keep > adding to my reading list when you drop quotes, Paul, the secret has to be > in there somewhere :) Joking aside, when the work required exceeds the > available volunteer manhours, the plan is a best-effort endeavor and good > communication. We can probably improve on the second part. This is an issue with any community-supported service, and that's a reasonable response. However, to avoid the "kick the can down the road" syndrome, I suggest setting some sort of review date for assessing whether that improvement has happened. One additional item of interest, but this may go OT for the infrastructure list: AIUI there is recent Docs team interest in how to better focus on audience. Unless our project is radically different from the rest of the Internet, I surmise users are looking for more succinct help and answers in general. This means there might be a way to build a sort of positive feedback loop into how we use ask.fp.o(*) to (1) engage Docs team members, especially new people who pop up to help; (2) deliver better answers to users; and (3) create content that can be effectively reused elsewhere. (*) or something like it, depending on how its maintenance goes -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Questions about ask.fp.o
On Wed, Mar 11, 2015 at 06:28:05PM +, Ankur Sinha wrote: > On Wed, 2015-03-11 at 11:58 -0400, Paul W. Frields wrote: > > I wasn't sure where else to ask these questions, so please feel free > > to refer me to a better venue! :-) > > > > * I found a 500 Server Error when I tried to leave feedback through > > the feedback link: > > > > https://ask.fedoraproject.org/en/feedback/?next=/en/questions/ > > > > Who is actively involved in administering the site, so I can refer > > this issue correctly? > > We know about this one. We're still not sure what's causing it. I've had > a couple of people e-mail me directly, which is fine. Community members > that run into issues generally open a fedora-infra trac ticket. > > https://fedorahosted.org/fedora-infrastructure/ticket/4187 That's fine, but how does someone not familiar with ask.fp.o know to do that? Why not change the link and investigate the problem in the background? > > * I don't visit the site very often. When I signed in today, I found > > over 10,000 posts in the moderation queue. Since I visited to find > > out status on a specific post the OP asked me about, and had to > > approve his question through, I'm worried all these posts represent > > questions blocked on moderator action. Am I correct about this or > > not? > > The moderation queue in the version we're using is quite badly designed > - it's an upstream issue - that's how askbot is. All those posts aren't > actually waiting for moderation - even if a mod approves a post, it > still seems to show up in another mod's moderation queue :( OK, I understand. What should I do about the 10,000+ items in my queue? > We informed upstream about this and they've apparently rewritten the > moderation part and made a new release. None of us have managed to find > the cycles to update the package and test it out in staging so that we > can update the production instance. It's high time I looked into it, > though - it's been on my todo list for quite a while. I'm happy you are looking into it, and I see from your other post there is an updated package. However, this raises a potential issue about future maintenance. It appears the site gets quite a bit of visitors and use. What's the plan to find cycles for the maintenance required for such a service? > > * No moderators or admins are camped in the #fedora-ask channel, which > > is referred to here as the canonical channel for help: > > > > https://fedoraproject.org/wiki/Ask_fedora?rd=AskFedora > > > > Is there a different channel or help venue that should be noted > > there? > > I should be in there pretty much 24x7, so would randomuser. We don't > speak much in the channel - it's more to monitor the fedmsg logs. :) I humbly retract this last bullet. :-) It turns out I was on the wrong IRC network and failed to read properly. I see three bots, and five people in there right now counting me. Sorry for my mistake! -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Questions about ask.fp.o
I wasn't sure where else to ask these questions, so please feel free to refer me to a better venue! :-) * I found a 500 Server Error when I tried to leave feedback through the feedback link: https://ask.fedoraproject.org/en/feedback/?next=/en/questions/ Who is actively involved in administering the site, so I can refer this issue correctly? * I don't visit the site very often. When I signed in today, I found over 10,000 posts in the moderation queue. Since I visited to find out status on a specific post the OP asked me about, and had to approve his question through, I'm worried all these posts represent questions blocked on moderator action. Am I correct about this or not? * No moderators or admins are camped in the #fedora-ask channel, which is referred to here as the canonical channel for help: https://fedoraproject.org/wiki/Ask_fedora?rd=AskFedora Is there a different channel or help venue that should be noted there? -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Fedora hosted planning
On Tue, Mar 10, 2015 at 09:26:59PM -0500, Dennis Gilmore wrote: > On Tuesday, March 10, 2015 05:56:58 PM Paul W. Frields wrote: > > On Tue, Mar 03, 2015 at 10:17:41PM -0600, Dennis Gilmore wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > > Hash: SHA1 > > > > > > On Tue, 3 Mar 2015 13:30:26 -0700 > > > > > > Stephen John Smoogen wrote: > > > > On 3 March 2015 at 13:22, Kevin Fenzi wrote: > > > > > Greetings. > > > > > > > > > > So, looking at fedorahosted, I thought I would start some discussion > > > > > about where we are and where we need to go short and longer term. > > > > > > > > > > Right now hosted03/04 are rhel6 and still in puppet. Short term, I > > > > > would very much like to move them to ansible, and ideally to rhel7. > > > > > > > > > > I looked into the trac situation upstream. We are currently using > > > > > 0.12.5 long term release on rhel6 (from epel6). There's a 0.12.6 > > > > > thats out, but it looks like that might be the last release in the > > > > > 0.12 series (or there might be a 0.12.7, but thats likely to be > > > > > it). They are looking at doing releases yearly if they can manage, > > > > > so 1.2 would appear later this year, then 1.3, etc. It's not clear > > > > > how long 1.0 will be supported really. At least a year, but not > > > > > clear after that. > > > > > > > > > > So, as I see it, our options are: > > > > > > > > > > 1 Just move to ansible, leave on rhel6 for now until we decide > > > > > > > > > > something better. > > > > > > > > > > 2 Move to ansible and rhel7, and build out trac-1.0 and plugins in > > > > > > > > > > epel7. This will take a bit longer since there's so many plugins, > > > > > > > > > > but shouldn't really be that hard. > > > > > > > > > > 3 Move to ansible and rhel7 and progit. I'm not sure if progit is > > > > > ready to replace trac though. I think it might need wiki features > > > > > and also more ticket handling stuff, since some of our projects use > > > > > trac ticketing heavily. > > > > > > > > > > 4 a combo of 2 and 3 (ie, offer trac and progit both) > > > > > > > > > > 5. a combo of 1 and 3 (ie, old trac projects stay on old hosted, we > > > > > move ones that want to progit, eventually we have a flag day and > > > > > move the rest). > > > > > > > > 5 sounds like the most likely. There are a lot of work flows which > > > > groups are using with the current trac. If they didn't.. they would > > > > have probably moved over to github by now. Having the old boxes on > > > > ansible is probably faster by at least 18 months over getting people > > > > moved to the newer system. > > > > > > I refuse to use github because I personally think its very bad for us as > > > a open and transparent community and project that prides itself on > > > making sure everyone can mimic what we do exactly to use something > > > closed and proprietary. For my own projects I think I would mostly be > > > okay with progit though something would be needed for ticketing for > > > releng, wiki space would be good for some projects but is not really > > > needed on all projects. some like mash only have a git repo on > > > fedorahosted, there is no associated trac. I think 4 or 5 would both be > > > viable. > > > > [Sorry for catching up late to this thread.] > > > > I'm not comfortable yet with the idea of taking on the service > > build-out that (3) represents above. That's a lot of commitment for > > something I don't think we can call critical path. Github may be a > > closed/paid service solution but it doesn't affect the public > > availability, transparency or forkability of any of our code. And a > > long-term investment in chasing that solution as a Fedora-specific > > service to replace hosted is not necessarily the best use of our > > resources. > We can agree to disagree here. I think without a good viable open source > option we will be locked into a closed proprietary platform. Define "locked"? If we're able to take our data (and even issues) and go elsewhere, where&#x
Re: Fedora hosted planning
On Tue, Mar 03, 2015 at 10:17:41PM -0600, Dennis Gilmore wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Tue, 3 Mar 2015 13:30:26 -0700 > Stephen John Smoogen wrote: > > > On 3 March 2015 at 13:22, Kevin Fenzi wrote: > > > > > Greetings. > > > > > > So, looking at fedorahosted, I thought I would start some discussion > > > about where we are and where we need to go short and longer term. > > > > > > Right now hosted03/04 are rhel6 and still in puppet. Short term, I > > > would very much like to move them to ansible, and ideally to rhel7. > > > > > > I looked into the trac situation upstream. We are currently using > > > 0.12.5 long term release on rhel6 (from epel6). There's a 0.12.6 > > > thats out, but it looks like that might be the last release in the > > > 0.12 series (or there might be a 0.12.7, but thats likely to be > > > it). They are looking at doing releases yearly if they can manage, > > > so 1.2 would appear later this year, then 1.3, etc. It's not clear > > > how long 1.0 will be supported really. At least a year, but not > > > clear after that. > > > > > > So, as I see it, our options are: > > > > > > 1 Just move to ansible, leave on rhel6 for now until we decide > > > something better. > > > > > > 2 Move to ansible and rhel7, and build out trac-1.0 and plugins in > > > epel7. This will take a bit longer since there's so many plugins, > > > but shouldn't really be that hard. > > > > > > 3 Move to ansible and rhel7 and progit. I'm not sure if progit is > > > ready to replace trac though. I think it might need wiki features > > > and also more ticket handling stuff, since some of our projects use > > > trac ticketing heavily. > > > > > > 4 a combo of 2 and 3 (ie, offer trac and progit both) > > > > > > 5. a combo of 1 and 3 (ie, old trac projects stay on old hosted, we > > > move ones that want to progit, eventually we have a flag day and > > > move the rest). > > > > > > > > 5 sounds like the most likely. There are a lot of work flows which > > groups are using with the current trac. If they didn't.. they would > > have probably moved over to github by now. Having the old boxes on > > ansible is probably faster by at least 18 months over getting people > > moved to the newer system. > > I refuse to use github because I personally think its very bad for us as > a open and transparent community and project that prides itself on > making sure everyone can mimic what we do exactly to use something > closed and proprietary. For my own projects I think I would mostly be > okay with progit though something would be needed for ticketing for > releng, wiki space would be good for some projects but is not really > needed on all projects. some like mash only have a git repo on > fedorahosted, there is no associated trac. I think 4 or 5 would both be > viable. [Sorry for catching up late to this thread.] I'm not comfortable yet with the idea of taking on the service build-out that (3) represents above. That's a lot of commitment for something I don't think we can call critical path. Github may be a closed/paid service solution but it doesn't affect the public availability, transparency or forkability of any of our code. And a long-term investment in chasing that solution as a Fedora-specific service to replace hosted is not necessarily the best use of our resources. -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: FAD proposal
This post[1] to rel-eng@ will also be of interest to folks working on infrastructure and applications in Fedora. On Thu, Feb 19, 2015 at 04:22:48PM -0500, Paul W. Frields wrote: > One of Matthew Miller's goals for Fedora is to diversify our release > deliverables. This is one reason the Fedora Engineering team is > bringing on a full-time person soon to work on release tools. We want > to contribute to the Fedora release engineering effort too (as opposed > to simply asking existing folks to do more). :-) > > I would expect over the first month or two in that role, our release > tools person will likely be: > > * looking at the field of deliverables needed, across not just the > products but also at containers and Project Atomic needs > > * getting familiar with any current release processes as needed > > * discussion with stakeholders in the project, including rel-eng, > mattdm, infrastructure, and others, on this list and elsewhere about > requirements > > During this time, I'd expect there will be some decisions on process, > architecture, etc. To kickstart development, I'd like to set up a FAD > where key community members, including developers and release > engineers, can start (or continue) working on actual code and > supporting infrastructure. > > I started a wiki page here for interested people to sign up: > https://fedoraproject.org/wiki/FAD_Release_Tools_and_Infrastructure_2015 > > There are some proposed dates listed on the wiki page. None have been > fully decided yet. I have preliminary approval from the FPL, and I'm > awaiting OSAS input on budget availability, and any time restrictions > from their POV. There is a good chance we will do this at the Red Hat > Tower (HQ) in Raleigh, NC USA. The event will not be restricted to > USA people, although we'll have to select a roster of people to meet > goals. > > There's a specific section in the page for you to write your name and > any restrictions on dates. This will help us make the best > date/location plan. > https://fedoraproject.org/wiki/FAD_Release_Tools_and_Infrastructure_2015#Potential_Attendees * * * [1] https://lists.fedoraproject.org/pipermail/rel-eng/2015-February/019355.html -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
[PATCH] Remove davej RH address from kernel-team emails
--- roles/fas_client/files/aliases.template|2 +- roles/fas_client/files/aliases.template.mailserver |2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/roles/fas_client/files/aliases.template b/roles/fas_client/files/aliases.template index fafc724..88ef746 100644 --- a/roles/fas_client/files/aliases.template +++ b/roles/fas_client/files/aliases.template @@ -260,7 +260,7 @@ fedora-docker-trusted: scollier,lsm5,mattdm fedoraqa-devel-admin: tflink,kparal,mkrizek # fedora kernel aliases -kernel-team: da...@redhat.com,jwbo...@redhat.com,jfor...@redhat.com +kernel-team: jwbo...@redhat.com,jfor...@redhat.com kernel-maint: kernel-ma...@redhat.com lvm-team: lvm-t...@redhat.com fedora-kernel-acpi: a...@linux.intel.com,len.br...@intel.com,mj...@srcf.ucam.org diff --git a/roles/fas_client/files/aliases.template.mailserver b/roles/fas_client/files/aliases.template.mailserver index a17aad7..4553039 100644 --- a/roles/fas_client/files/aliases.template.mailserver +++ b/roles/fas_client/files/aliases.template.mailserver @@ -264,7 +264,7 @@ fedora-docker-trusted: scollier,lsm5,mattdm fedoraqa-devel-admin: tflink,kparal,mkrizek # fedora kernel aliases -kernel-team: da...@redhat.com,jwbo...@redhat.com,jfor...@redhat.com +kernel-team: jwbo...@redhat.com,jfor...@redhat.com kernel-maint: kernel-ma...@redhat.com lvm-team: lvm-t...@redhat.com fedora-kernel-acpi: a...@linux.intel.com,len.br...@intel.com,mj...@srcf.ucam.org -- 1.7.2.1 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Remove invalid address from kernel-team alias
Since davej isn't at Red Hat any longer, this patch removes his old address from the kernel-team alias. ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Fedora identity plans
Hi Infra folks, I wanted to introduce Dmitri Pal, who manages the team at Red Hat that works on freeIPA[1] and SSSD[2] among other things. Patrick of course contributes to Ipsilon[3] which includes fedoauth, and has been collaborating with Simo, who's on Dmitri's team. Dmitri asked me about Fedora identity and authentication needs and whether any of these projects could be useful in Fedora infrastructure. I told him I'd make an introduction so the Infrastructure team can explain the problems we're trying to solve with the next Fedora Account System, and how that relates to work Dmitri's team is doing. Dmitri, most if not all of the Fedora Engineering team[4] are on this list, along with many other contributors to the Fedora community. Since some of us (Patrick, Pierre, myself) will be in Brno for the DevConf.cz event, we may have the opportunity to meet up there to follow up on this discussion in person, but this is a good place to start. Please keep on CC for the discussion, since he may not follow this list daily. * * * [1] http://www.freeipa.org/ [2] https://fedorahosted.org/sssd/ [3] https://fedorahosted.org/ipsilon/ -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: firewall rules on builders (iptables, firewalld, libvirt...)
On Tue, Oct 28, 2014 at 08:50:29AM -0600, Stephen John Smoogen wrote: > On 28 October 2014 08:04, Matthew Miller wrote: > > > It's my understanding (Dennis please correct if I'm wrong) that the > > problem with cloud image creation was due to libvirt iptables rules > > being lost when iptables was restarted. This is a fundamental known > > issue (see last paragraph of <http://libvirt.org/firewall.html>), and > > one of the things firewalld was meant to solve. > > > > Dennis says that there are lot of complicated rules on the builders > > making switching to firewalld difficult. One possibility might be to > > move those complicated rules from the builders to a network firewall, > > and keep the host rules simple and functional. But that's probably a > > big undertaking. > > > > > It would be.. It would be creating a new network for these boxes, putting > the hardware behind such a firewall, setting up routing for such devices > etc etc. [Plus a budget needed for that hardware.] > > > > In the meantime, any time iptables is restarted or reloaded, libvirt > > needs a SIGHUP. (I suppose this means: ansible playbooks and also added > > to any manual procedures.) > > > > That actually would be 'easier' to set up even if it is a cron job which > checks to see if a marker is in iptables and if not sends a sighup to > libvirt The firewalld rich language is probably also worth looking into -- if for no other reason than to determine whether it is capable of handling these use cases. If not, we should file RFEs upstream because we I'm betting we're not *that* special. :-) -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: MM2/Ansible FAD Hotel rooms
On Tue, Oct 21, 2014 at 07:25:36PM +0200, Pierre-Yves Chibon wrote: > On Sat, Oct 18, 2014 at 07:17:15PM +0200, Pierre-Yves Chibon wrote: > > Hi all, > > > > I would like to book the rooms for the hotel. Since we have 2 period (first > > days > > for MirrorManager, then the ansible migration part), I'd like to ask who > > will be > > there for which part? > > > > Patrick and I arrive on the 2rd and leave on the 9th, so we'll have an extra > > day to handle the jet-lag. > > > > The official dates are from Dec 4th to Dec 9th, as in, we start working on > > the > > 4th and finish on the 8th, thus departure on the 9th, so arrival dates > > should be > > Dec 3rd. > > > > Thank you all for replying. > I just phoned the hotel and booked 4 rooms > - 3 rooms from Dec 3rd to Dec 9th > - 1 room from Dec 2nd to Dec 9th > > All rooms are currently under my name, which needs to be changed by Dec 1st, > for > that we need: > a) figure out who shares a room with whom > b) who of the room will check-in first (unless I give the two names for each > room) > > Check-in time is from 3pm > Check-out time is noon > Parking and internet are included (breakfast isn't). For those in the USA who are flying in, please contact me off-list with flight preferences. I can help by making/consolidating those purchases, and holding onto the charges until December to meet OSAS budget limitations. -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Alias for list?
Hi, We've had a few occasions in the past year where people have sent email to workstat...@lists.fp.o instead of the actual Workstation WG list, desktop@. Would it be possible to alias workstation@ so that emails there reach the desktop@ list? Does that cause problems that make it a bad idea? -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
MM2/Ansible FAD (was FAS3/MM2 FAD)
As was discussed in a previous thread, the FAD was slightly reorganized to continue to cover (1) MirrorManager 2 work, and (2) based on available people, Ansible playbook migration. Thank you to pingou and others for organization efforts and willingness to help! mattdm gave his +1 for the FAD, and rsuehle has said she can support the budget, with the caveat that we Red Hatters hold off expensing our USA airfares until ~December 1, so they will hit the OSAS budget in Red Hat's fiscal Q4. This is something we can handle administratively within Red Hat, just noted here for transparency. If any of the travelers don't know what this means, please contact me off-list and I'll be glad to explain and help with planning. If possible, I'll try to drive down for at least one day of the FAD event, to see you guys and pitch in. -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: FAS3/MM2 FAD
On Fri, Oct 10, 2014 at 05:06:35PM +0200, Pierre-Yves Chibon wrote: > On Fri, Oct 10, 2014 at 08:21:21AM +0200, Pierre-Yves Chibon wrote: > > On Thu, Oct 09, 2014 at 03:20:06PM -0400, Paul W. Frields wrote: > > > On Thu, Oct 09, 2014 at 09:39:50AM +0200, Pierre-Yves Chibon wrote: > > > > On Tue, Oct 07, 2014 at 11:37:44AM +0200, Pierre-Yves Chibon wrote: > > > > > TODO: > > > > > * Confirm location and dates with Matt > > > > > * Confirm location and dates with Toshio > > > > > -> I will email them > > > > > > > > Matt confirmed that he is planning on attending and will make his own > > > > travel > > > > arrangements. > > > > > > > > Toshio isn't sure yet, should get back to me on this on Friday. > > > > > > > > If neither Toshio nor Xavier can make it, should we make the FAD a > > > > little > > > > shorter and focused on MirrorManager2 only? > > > > > > This is a possibility. It might also be possible to have a "Plan B" > > > application if the right people are present. Preferably this would be > > > something on the Fedora.next critical path, so we get maximum value > > > from the FAD event. > > > > Potential plan B: > > - hackfest on the ansible migration > > - hackfest on the el7 migration > > - hackfest on atomic's infrastructure? > > - ? > > If we move to one of these topics, the list of potential attendants would > become: > > pingou: TLS > Patrick: AMS > David: SEA > Ralph: ROC > Matt: HOU > Kevin: DEN > Smooge: ABQ > > > Luke: DEN ? > > Travel budget then becomes: > ► Raleigh > TLS -> RDU => ~$957 - Delta > AMS -> RDU => ~$692 - Delta > SEA -> RDU => ~$510 - Delta > ROC -> RDU => ~$260 - Delta > CHI -> RDU => ~$230 - United Airlines > HOU -> RDU => $0 - Matt said he was taking care of it himself > DEN -> RDU => ~$295 - Delta > ABQ -> RDU => ~$400 - Delta > -- > $3344 > With Luke > DEN -> RDU => ~$295 - Delta > -- > $3639 > > Note: prices might vary a little, I kept the Dec 2nd to Dec 9th dates for all > the travels here (and except for ABQ -> RDU they are from Oct 7th). > > Paul, do you have the info for the hotel rates? It should be $149 at the Sheraton Raleigh for each double occupancy room. The hotel is a very short walk to the office, practically just across the street. I separately sent Pierre a link to an internal Red Hat page that includes a bunch of other facilities and planning info for Red Hat Tower and Raleigh, NC visitors. -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: FAS3/MM2 FAD
On Thu, Oct 09, 2014 at 09:39:50AM +0200, Pierre-Yves Chibon wrote: > On Tue, Oct 07, 2014 at 11:37:44AM +0200, Pierre-Yves Chibon wrote: > > TODO: > > * Confirm location and dates with Matt > > * Confirm location and dates with Toshio > > -> I will email them > > Matt confirmed that he is planning on attending and will make his own travel > arrangements. > > Toshio isn't sure yet, should get back to me on this on Friday. > > > If neither Toshio nor Xavier can make it, should we make the FAD a little > shorter and focused on MirrorManager2 only? This is a possibility. It might also be possible to have a "Plan B" application if the right people are present. Preferably this would be something on the Fedora.next critical path, so we get maximum value from the FAD event. I wanted to raise two additional issues: (1) A budget is needed for this event very soon if the event will happen December 4-9. It's less than two months away, and flight costs are likely to rise imminently. The attendance roster and costs need to be finalized so the budget can be established and approved. (2) I'm not sure this timeframe will work well for Fedora release engineering. There is a release scheduled for December 2, and whether there's any further slip in the F21 release schedule, travel around this event would raise unnecessary challenges with the release. How vital is a rel-eng representative for MirrorManager hacking? -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: FAS3/MM2 FAD
On Tue, Oct 07, 2014 at 11:47:37AM +0200, Pierre-Yves Chibon wrote: > On Tue, Oct 07, 2014 at 11:37:44AM +0200, Pierre-Yves Chibon wrote: > > Hi Everyone, > > > > So here is where we are on the FAS3/MM2 FAD. > > > > Location: Raleigh (airport: RDU) > > Dates: December 2nd to December 9th > > Divided in two parts > > Dec 3rd to Dec 5th -> MirrorManager2 > > Actually, I see on the wiki that I had planned Dec 3rd to be a "social" day to > recover from the travel/jet-lag, do some sightseeing and start to settle down. > I think that was because Matt has agreed for the 4th and 5th (I'll confirm > with > him). > > Pierre > > > > Dec 6th to Dec 8th -> FAS3 > > > > This way those interested in both topics can be present for the whole week, > > the > > others can be present for only part of it. > > > > > > Attendants (airport of origin): > > pingou: TLS > > Xavier: CDG > > Patrick: AMS > > Toshio: LAX ? > > David: SEA > > Ralph: ROC > > Matt: HOU ? > > Dennis: CHI ? > > Kevin: DEN > > Luke: DEN > > > > Travel budget (Prices found on orbitz.com): > > ► Raleigh > > TLS -> RDU => ~$957 - Delta > > CDG -> RDU => ~$940 - American Airlines > > AMS -> RDU => ~$692 - Delta > > LAX -> RDU => ~$355 - Delta > > SEA -> RDU => ~$510 - Delta > > ROC -> RDU => ~$260 - Delta > > CHI -> RDU => ~$230 - United Airlines > > HOU -> RDU => ~$320 - Delta > > DEN -> RDU => ~$295 - Delta > > DEN -> RDU => ~$295 - Delta > > -- > > $4854 > > > > TODO: > > * Confirm location and dates with Matt I got in touch with Matt in a separate email to make sure RDU wouldn't be an immediate blocker for him. He said the travel shouldn't be a problem. However, go ahead and confirm the exact dates with him anyway. > > * Confirm location and dates with Toshio > > -> I will email them > > * Find hotel/housing (Paul any idea?) We can get a block at the nearby Marriott through internal resources. Just need to know how many rooms and for which dates. I'll email Pierre separately with internal info needed to use Red Hat's rate at the hotel. > > * Find social events > > * Submit budget to FPL for approval > > * Book ticket > > * Travel, hack and enjoy :) -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: FAS3/MM2 FAD (was Re: Summary/Minutes from today's Fedora Infrastructure meeting (2014-08-21))
On Thu, Oct 02, 2014 at 05:22:01PM -0600, Kevin Fenzi wrote: > On Thu, 2 Oct 2014 17:24:08 -0400 > "Paul W. Frields" wrote: > > > On Sat, Sep 06, 2014 at 03:36:33PM +0200, Pierre-Yves Chibon wrote: > > > Hi all, > > > > > > By popular demand, I added the costs for a couple of other possible > > > locations but as this was getting un-readable accross the multiple > > > emails, here is the complete list, new locations are at the bottom. > > > > Hi Pierre and all, > > > > Looks like this fell dormant for a while so I want to bump the > > topic. ;-) > > > > I was talking to Kevin Fenzi and although he hasn't had a chance to > > exhaustively search all spaces in Denver, so far he hasn't found any > > great alternatives. I found some coworking spaces but they were > > limited availability and/or quite expensive ($120/day and up). That's > > expensive enough that it makes more sense to do the FAD in RDU: > > > > * free space available at Red Hat Tower > > * hotel close to the site with Red Hat's courtesy rate > > * lots of food and nightlife in walking distance of both > > > > Also lots of Fedora friends are in the area as well, and we might be > > able to pick up a few extra contributors during the event. > > > > Would anyone be *uncomfortable* forging ahead with doing this FAD in > > RDU? > > I guess I'd be ok with it, but I just noticed that none of the airfare > estimates have DEN -> in them. ;) > > Of course I don't absolutely need to be there either... I think we'd greatly benefit from your being there! :-) I don't think one additional airfare from DEN, given the free workspace, will make/break the event. -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: FAS3/MM2 FAD (was Re: Summary/Minutes from today's Fedora Infrastructure meeting (2014-08-21))
On Sat, Sep 06, 2014 at 03:36:33PM +0200, Pierre-Yves Chibon wrote: > Hi all, > > By popular demand, I added the costs for a couple of other possible locations > but as this was getting un-readable accross the multiple emails, here is the > complete list, new locations are at the bottom. Hi Pierre and all, Looks like this fell dormant for a while so I want to bump the topic. ;-) I was talking to Kevin Fenzi and although he hasn't had a chance to exhaustively search all spaces in Denver, so far he hasn't found any great alternatives. I found some coworking spaces but they were limited availability and/or quite expensive ($120/day and up). That's expensive enough that it makes more sense to do the FAD in RDU: * free space available at Red Hat Tower * hotel close to the site with Red Hat's courtesy rate * lots of food and nightlife in walking distance of both Also lots of Fedora friends are in the area as well, and we might be able to pick up a few extra contributors during the event. Would anyone be *uncomfortable* forging ahead with doing this FAD in RDU? [...snip...] > Budget > == > > Prices found in orbitz.com > > Dec 2nd -> Dec 9th > > pingou: TLS > Xavier: CDG > Patrick: AMS > Toshio: LAX ? > David: SEA > Ralph: ROC > Matt: HOU ? > Dennis: CHI ? > Kevin: DEN > > ► Denver > TLS -> DEN => ~$950 - AF > CDG -> DEN => ~$940 - AF > AMS -> DEN => ~$770 - Delta > LAX -> DEN => ~$165 - Frontier Airlines > SEA -> DEN => ~$220 - Frontier Airlines > ROC -> DEN => ~$380 - United > CHI -> DEN => ~$170 - Spirit > -- > $3595 > > HOU -> DEN => ~$160 - Spirit -> Matt said it would drive there and Intel > pays for the car > > > ► Raleigh > TLS -> RDU => ~$705/$996 - American Arilines / Delta > CDG -> RDU => ~$740 - US Airways > AMS -> RDU => ~$885 - Delta > LAX -> RDU => ~$360 - US Airways > SEA -> RDU => ~$445 - United Airlines > ROC -> RDU => ~$270 - Delta > CHI -> RDU => ~$230 - American Airlines > HOU -> RDU => ~$315 - Delta > -- > $3950/4241 > > ► Boston > TLS -> BOS => ~$865 - Delta > CDG -> BOS => ~$600/$860 - British Airways/United > AMS -> BOS => ~$765/$786 - British Airways/KLM > LAX -> BOS => ~$390 - United > SEA -> BOS => ~$365/$355 - JetBlue/United > ROC -> BOS => ~$180 - US Airways > CHI -> BOS => ~$160 - United > HOU -> BOS => ~$215 - JetBlue > -- > $3530/3821 > > ► Fredericksburg > TLS -> IAD => ~$945 - KLM > CDG -> IAD => ~$945 - AF > AMS -> IAD => ~$685 - KLM > LAX -> IAD => ~$385 - United > SEA -> IAD => ~$560 - United > ROC -> IAD => ~$215 - United > CHI -> IAD => ~$275 - United > HOU -> IAD => ~$370 - Delta > -- > $4380 > > > ► Albuquerque > TLS -> ABQ => ~$1280 - Delta > CDG -> ABQ => ~$730 - US Airways > AMS -> ABQ => ~$1050 - United > LAX -> ABQ => ~$280 - American Airlines > SEA -> ABQ => ~$285 - Alaska Airlines > ROC -> ABQ => ~$420 - United > CHI -> ABQ => ~$410 - United > HOU -> ABQ => ~$520 - American Airlines > -- > $4975 > > > ► Paris > TLS -> ORY => ~$180 - AF > CDG -> CDG => ~$-- > AMS -> CDG => ~$130 - KLM > LAX -> CDG => ~$1250 - United (direct) > SEA -> CDG => ~$995 - Icelandair (1 stop) > ROC -> CDG => ~$1260 - AF (1 stop) > CHI -> CDG => ~$1200 - AF (direct) > HOU -> CDG => ~$1320 - AF (direct) > -- > $6335 > > > ► Amsterdam > TLS -> AMS => ~$210 - KLM > CDG -> AMS => ~$180 - KLM > AMS -> AMS => ~$-- > LAX -> AMS => ~$1380 - KLM (direct) > SEA -> AMS => ~$1390 - KLM (direct) > ROC -> AMS => ~$1170 - Delta (1 stop) > CHI -> AMS => ~$1060 - United (1 stop) > HOU -> AMS => ~$1118 - KLM (direct) > -- > $6508 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: [Fedocal] Reminder meeting : Atomic / Infrastructure Meeting
On Sun, Sep 21, 2014 at 07:00:02PM +, j...@fedoraproject.org wrote: > Dear all, > > You are kindly invited to the meeting: >Atomic / Infrastructure Meeting on 2014-09-23 from 19:00:00 to 19:30:00 UTC > > > The meeting will be about: > Meeting to work on infrastructure pieces required for building Fedora Atomic > images. Hmm, I think we have an old invite happening on fedocal or something? The 1800 UTC (2:00pm EDT) invite is the right one, for those of you keeping score at home. ;-) -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Atomic/infra/rel-eng meeting
We agreed ad hoc in IRC to move our regular Atomic/infra/releng sync meeting for *this week* to tomorrow (Wed 2014-Sep-17) at 2:00pm EDT / 1:00pm CDT / 1800 UTC so we can catch Dennis without making it hard for him to pick up his daughter from school. In the future the meeting will be back on Tuesday, but again at that *new* time of 2:00pm EDT / 1:00pm CDT / 1800 UTC. Dennis, does that work better for you? -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: fedmsg in Debian
On Sun, Sep 07, 2014 at 01:13:13PM -0400, Rahul Sundaram wrote: > Hi > > On Sun, Sep 7, 2014 at 1:40 AM, Ankur Sinha wrote: > > > > > Probably worth speaking to the marketing team about this, Rahul. I'll > > bring it up on the videos ML too. We may be able to post process videos > > to improve them. > > > Thanks and if you do, I would love to see them published in a free format. > I am probably in the minority here but I download videos and watch them > when I am traveling. You can do that already. The 'youtube-dl' package offers this capability, and you can download any of these videos now in the free webm format. -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: FAS3/MM2 FAD (was Re: Summary/Minutes from today's Fedora Infrastructure meeting (2014-08-21))
On Fri, Sep 05, 2014 at 10:18:36AM +0200, Pierre-Yves Chibon wrote: > On Thu, Sep 04, 2014 at 11:27:56AM -0400, Paul W. Frields wrote: > > On Mon, Aug 25, 2014 at 09:03:51AM -0600, Kevin Fenzi wrote: > > > On Fri, 22 Aug 2014 12:37:29 +0200 > > > Pierre-Yves Chibon wrote: > > > > > > > > We may want to pick another place but for the time period I think > > > > > this one works best for Matt and I for 2014. > > > > > > > > > > Other options: (*: question, +: pro, -: con) > > > > > ► Denver? > > > > > * Kevin, do you know of a place we could have access to to work? > > > > > > I don't off hand. If we are willing to pay a bit I think we could > > > reserve space at a hotel or the like. I'm not sure network will be > > > great, but most places have meeting rooms you can get and also that > > > would be handy for people staying there. > > > > > > However, if it's just me thats here, it might make sense to try and > > > find a location that would be cheaper for everyone to go to and find > > > meeting space there? > > > > Kevin, can you look into coworking spaces? There are usually a few of > > these in most metro areas. They're relatively affordable, often more > > so than hotel meeting space, and also usually more comfortable work > > environment. I found this one: > > > > http://densitycoworking.com/space/ > > > > > > > ► Houston? > > > > > + IIRC Matt isn't too far from it > > > > > + there are direct flights from AMS to there > > > > > - Do we have a local contact? > > > > > > I think tibbs might be near there... not sure if he has time to help > > > out, but we could ask. > > > > > > > > ► Boston? > > > > > + RH office > > > > > - Flying there in December might make the traveling "interesting" > > > > > ► Raleigh? > > > > > + RH office and facilities there > > > > > - No-one that signed up on the wiki is located near so we all > > > > > have to travel ► ? > > > > > > What are the cheapest/easiest US cities for the eu folks to fly into? > > > > If you guys are still looking for space, I could also throw my hat in > > the ring to host here in Fredericksburg, VA. > > > > + Coworking meeting space available for rent, used for previous FAD, > > reasonable price > > + Driving distance to IAD (Washington-Dulles) airport, relatively > > cheaper airfare > > + Affordable hotels > > + Unlikely to have crazy weather in early December > > - Not sure if it's as convenient for Matt > > - Everyone travels > > > Ok I spent sometime looking at orbitz.com to see what is the price difference > to > fly everyone to each location we mentionned. > > It seems that Denver and Boston are the winners. > > Details below. > > Pierre > > > Budget > == > > Prices found in orbitz.com > > Dec 2nd -> Dec 9th > > pingou: TLS > Xavier: CDG > Patrick: AMS > Toshio: LAX ? > David: SEA > Ralph: ROC > Matt: HOU ? > Dennis: CHI ? > Kevin: DEN > > ► Denver > TLS -> DEN => ~$950 - AF > CDG -> DEN => ~$940 - AF > AMS -> DEN => ~$770 - Delta > LAX -> DEN => ~$165 - Frontier Airlines > SEA -> DEN => ~$220 - Frontier Airlines > ROC -> DEN => ~$380 - United > CHI -> DEN => ~$170 - Spirit > -- > $3595 > > HOU -> DEN => ~$160 - Spirit -> Matt said it would drive there and Intel > pays for the car > > > ► Raleigh > TLS -> RDU => ~$705/$996 - American Arilines / Delta > CDG -> RDU => ~$740 - US Airways > AMS -> RDU => ~$885 - Delta > LAX -> RDU => ~$360 - US Airways > SEA -> RDU => ~$445 - United Airlines > ROC -> RDU => ~$270 - Delta > CHI -> RDU => ~$230 - American Airlines > HOU -> RDU => ~$315 - Delta > -- > $3950/4241 > > ► Boston > TLS -> BOS => ~$865 - Delta > CDG -> BOS => ~$600/$860 - British Airways/United > AMS -> BOS => ~$765/$786 - British Airways/KLM > LAX -> BOS => ~$390 - United > SEA -> BOS => ~$365/$355 - JetBlue/United > ROC -> BOS => ~$180 - US Airways > CHI -> BOS => ~$160 - United > HOU -> BOS =>
Re: FAS3/MM2 FAD (was Re: Summary/Minutes from today's Fedora Infrastructure meeting (2014-08-21))
On Mon, Aug 25, 2014 at 09:03:51AM -0600, Kevin Fenzi wrote: > On Fri, 22 Aug 2014 12:37:29 +0200 > Pierre-Yves Chibon wrote: > > > > We may want to pick another place but for the time period I think > > > this one works best for Matt and I for 2014. > > > > > > Other options: (*: question, +: pro, -: con) > > > ► Denver? > > > * Kevin, do you know of a place we could have access to to work? > > I don't off hand. If we are willing to pay a bit I think we could > reserve space at a hotel or the like. I'm not sure network will be > great, but most places have meeting rooms you can get and also that > would be handy for people staying there. > > However, if it's just me thats here, it might make sense to try and > find a location that would be cheaper for everyone to go to and find > meeting space there? Kevin, can you look into coworking spaces? There are usually a few of these in most metro areas. They're relatively affordable, often more so than hotel meeting space, and also usually more comfortable work environment. I found this one: http://densitycoworking.com/space/ > > > ► Houston? > > > + IIRC Matt isn't too far from it > > > + there are direct flights from AMS to there > > > - Do we have a local contact? > > I think tibbs might be near there... not sure if he has time to help > out, but we could ask. > > > > ► Boston? > > > + RH office > > > - Flying there in December might make the traveling "interesting" > > > ► Raleigh? > > > + RH office and facilities there > > > - No-one that signed up on the wiki is located near so we all > > > have to travel ► ? > > > > I did not include Amsterdam is the list above but for completeness' > > sake: > > > > ► Amsterdam? > > + RH office > > + Easy for Patrick, Xavier and Pingou to get there > > - Expensive for Matt, Kevin, Ralph, Toshio and David > > - Probably too much traveling for a 2 days hackfest for Matt (and > > Toshio?) > > Yeah. If we have more us people we probibly want to look at us just to > keep costs down. > > What are the cheapest/easiest US cities for the eu folks to fly into? If you guys are still looking for space, I could also throw my hat in the ring to host here in Fredericksburg, VA. + Coworking meeting space available for rent, used for previous FAD, reasonable price + Driving distance to IAD (Washington-Dulles) airport, relatively cheaper airfare + Affordable hotels + Unlikely to have crazy weather in early December - Not sure if it's as convenient for Matt - Everyone travels -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Atomic / Infrastructure Meeting minutes -- 2014-08-19 UTC 2000
Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2014-08-19/fedora-meeting.2014-08-19-20.00.html Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2014-08-19/fedora-meeting.2014-08-19-20.00.txt Log: http://meetbot.fedoraproject.org/fedora-meeting/2014-08-19/fedora-meeting.2014-08-19-20.00.log.html == #fedora-meeting: Atomic/Infrastructure == Meeting started by stickster at 20:00:08 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2014-08-19/fedora-meeting.2014-08-19-20.00.log.html . Meeting summary --- * jzb is traveling to LinuxCon so stickster is subbing for him (stickster, 20:02:23) * Status check (stickster, 20:02:29) * Alt composes of rawhide blocked on Atomic generating and deploying new images --> in progress (stickster, 20:04:40) * MirrorManager/metalinks (stickster, 20:06:51) * walters made progress on metalink implementation, ready to test once content is sync'd to mirrors and metalink.xml is generated -- need to make sure this works in MM2 later as well. (stickster, 20:08:36) * oddshocks in new hire orientation 18-19 Aug, then relocating to SEA but should be online afternoon/evening-ish while traveling (stickster, 20:13:16) * ACTION: stickster remind oddshocks to read log and check in on-list (stickster, 20:14:28) * rel-eng compose (stickster, 20:18:31) * dgilmore has sorted out producing cloud images \o/ (stickster, 20:20:32) * ACTION: dgilmore test installation of an atomic tree (stickster, 20:21:11) * jzb tested the installer ISO posted to atomic-devel earlier, fwiw (stickster, 20:22:25) * AGREED: atomic code will support a separate inline .signed copy of the summary file (stickster, 20:32:58) * ACTION: dgilmore produce .signed file as needed (stickster, 20:33:22) * ACTION: walters support .signed file as agreed (stickster, 20:33:41) * AOB - All other business (stickster, 20:36:50) * LINK: http://wiki.centos.org/Events/Dojo/Paris2014 (misc, 20:38:29) * ACTION: jzb Next meeting - discuss Rawhide status (stickster, 20:38:52) * ACTION: dgilmore examine ISO creation script in https://lists.projectatomic.io/projectatomic-archives/atomic/2014-July/msg2.html (stickster, 20:45:40) * ACTION: walters check out pungi at https://git.fedorahosted.org/git/pungi.git (stickster, 20:45:56) * AGREED: sync at next meeting to see how ISO creation could be handled in pungi (stickster, 20:46:16) Meeting ended at 20:47:35 UTC. Action Items * stickster remind oddshocks to read log and check in on-list * dgilmore test installation of an atomic tree * dgilmore produce .signed file as needed * walters support .signed file as agreed * jzb Next meeting - discuss Rawhide status * dgilmore examine ISO creation script in https://lists.projectatomic.io/projectatomic-archives/atomic/2014-July/msg2.html * walters check out pungi at https://git.fedorahosted.org/git/pungi.git Action Items, by person --- * dgilmore * dgilmore test installation of an atomic tree * dgilmore produce .signed file as needed * dgilmore examine ISO creation script in https://lists.projectatomic.io/projectatomic-archives/atomic/2014-July/msg2.html * jzb * jzb Next meeting - discuss Rawhide status * stickster * stickster remind oddshocks to read log and check in on-list * walters * walters support .signed file as agreed * walters check out pungi at https://git.fedorahosted.org/git/pungi.git * **UNASSIGNED** * (none) People Present (lines said) --- * stickster (60) * walters (33) * dgilmore (17) * jzb (13) * zodbot (9) * nirik (6) * agrimm (6) * misc (4) * dustymabe (3) * number80 (2) * pingou (2) * jbrooks (2) * geppetto (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Fedora Atomic Infrastructure meeting time results
On Fri, Jul 25, 2014 at 10:43:56AM -0700, Joe Brockmeier wrote: > On 07/25/2014 09:44 AM, Paul W. Frields wrote: > > http://whenisgood.net/atomic-2014-07/results/7n7atqe > > > > The best time is 4:00-4:30pm EDT on Tuesdays. We will be missing > > Mathieu (bochecha) but I've already talked to him and he's willing to > > stay tuned to meeting minutes and keep participating around them. > > > > Joe, do you want to set this up on fedocal? We should have some items > > to check progress next week if that's OK with all involved. > > Have set this up on the Cloud calendar to send reminders to > infrastructure@ - I don't have access to the Infrastructure calendar. > Will ask for that and put the reminder in the right place later this > weekend. Awesome -- thanks, Joe. -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Fedora Atomic Infrastructure meeting time results
http://whenisgood.net/atomic-2014-07/results/7n7atqe The best time is 4:00-4:30pm EDT on Tuesdays. We will be missing Mathieu (bochecha) but I've already talked to him and he's willing to stay tuned to meeting minutes and keep participating around them. Joe, do you want to set this up on fedocal? We should have some items to check progress next week if that's OK with all involved. -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: L10n fedmsg integration?
On Thu, Jul 24, 2014 at 12:12:54PM +1000, Sean Flanigan wrote: > On 2014-07-24 03:02, Paul W. Frields wrote: > > On Wed, Jul 23, 2014 at 10:51:04AM -0400, Ralph Bean wrote: > >> On Wed, Jul 23, 2014 at 10:24:57AM -0400, Paul W. Frields wrote: > >>> Is there any way to attach an outside hosted service such as Zanata or > >>> Transifex to the Fedora's fedmsg bus? Sorry if this is a naive > >>> question. > >> > >> Yeah, I looked into it with Transifex. They provide a > >> pubsubhubbub-like interface which would let us bridge nicely. > >> This is exactly how we currently interface with GitHub: > >> https://apps.fedoraproject.org/GitHub2fedmsg > >> Whenever an event would occur in GitHub or Transifex, they would send > >> an http POST to a listening web service on our side. Our web service > >> would then re-broadcast that event as a fedmsg event. > >> > >> The problem with Transifex, though, is that they do not > >> cryptographically sign their POSTs, which opens us up to.. anybody. > >> (GitHub actually signs each POST so we know its coming from them). > >> > >> I haven't looked at Zanata yet, though. > > > > ISTM we have an untapped stream of contributions we could recognize if > > the translation system (whichever it is) would sign those POSTs. I'm > > not sure whether glezos is on this list, but I'll ask him whether this > > is an interesting RFE, and do the same for Zanata. > > Zanata doesn't integrate with any buses yet, but a concrete use case > will help, so please feel free to submit an RFE. > > https://bugzilla.redhat.com/enter_bug.cgi?product=Zanata One use case would be for rewarding Fedora translation contributors with badges via the Fedora Badges app[1]. Having translation submissions trigger a message on the fedmsg bus allows the Badges app to record and award those. Our experience has shown community members like receiving these badges and exhibiting them for the accomplishments and contributions they represent. Ralph, would you be willing to file the RFE with details on signing the POSTs to prevent abuse? = = = [1] http://badges.fedoraproject.org/ -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: L10n fedmsg integration?
On Wed, Jul 23, 2014 at 10:51:04AM -0400, Ralph Bean wrote: > On Wed, Jul 23, 2014 at 10:24:57AM -0400, Paul W. Frields wrote: > > Is there any way to attach an outside hosted service such as Zanata or > > Transifex to the Fedora's fedmsg bus? Sorry if this is a naive > > question. > > Yeah, I looked into it with Transifex. They provide a > pubsubhubbub-like interface which would let us bridge nicely. > This is exactly how we currently interface with GitHub: > https://apps.fedoraproject.org/GitHub2fedmsg > Whenever an event would occur in GitHub or Transifex, they would send > an http POST to a listening web service on our side. Our web service > would then re-broadcast that event as a fedmsg event. > > The problem with Transifex, though, is that they do not > cryptographically sign their POSTs, which opens us up to.. anybody. > (GitHub actually signs each POST so we know its coming from them). > > I haven't looked at Zanata yet, though. ISTM we have an untapped stream of contributions we could recognize if the translation system (whichever it is) would sign those POSTs. I'm not sure whether glezos is on this list, but I'll ask him whether this is an interesting RFE, and do the same for Zanata. -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
L10n fedmsg integration?
Is there any way to attach an outside hosted service such as Zanata or Transifex to the Fedora's fedmsg bus? Sorry if this is a naive question. -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Regular meetup for Atomic
Visit this link to indicate preferences for a regular 30-minute slot. http://whenisgood.net/atomic-2014-07 All interested parties welcome; time preference will be given to critical representatives from Atomic, Infra, Rel-eng. -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Agenda for today's meeting on Atomic
On Mon, Jul 21, 2014 at 11:07:18AM -0400, Paul W. Frields wrote: > On Mon, Jul 21, 2014 at 09:21:22AM -0500, Joe Brockmeier wrote: > > Hi all, > > > > In the interest of keeping things moving well, I threw together a quick > > draft agenda: > > > > - Quick roll call > > > > - What is the minimum we need to get to alpha status? > > (e.g., produce something testable, consumable, usable but not > > necessarily "production quality") > > > > - What are other blockers we need to solve to be able to have an > > official release? (as opposed to a remix) > > > > - Where do we need help immediately, and who can step up? > > > > - What are we missing entirely? > > > > - Action items for the next week or two > > > > - Agreement on next meeting time Thanks zoddie. We'll try to keep the next one shorter now that we're on a roll. ;-) Minutes: http://meetbot.fedoraproject.org/atomic/2014-07-21/atomic.2014-07-21-15.03.html Minutes (text): http://meetbot.fedoraproject.org/atomic/2014-07-21/atomic.2014-07-21-15.03.txt Log: http://meetbot.fedoraproject.org/atomic/2014-07-21/atomic.2014-07-21-15.03.log.html Meeting summary --- * Minimum for Alpha (jzb, 15:04:18) * Mirroring approach probably needed for scale, even if we don't project a high number of users. (stickster, 15:14:51) * Volunteer oddshocks to work on MirrorManager code fixes needed (need to get this more granular, work with dgilmore/nirik) (stickster, 15:16:24) * Volunteer oddshocks to work on MirrorManager code fixes needed (need to get this more granular, work with dgilmore/nirik/walters as needed) (stickster, 15:17:18) * LINK: http://rpm-ostree.cloud.fedoraproject.org/repo/refs/heads/fedora-atomic/rawhide/x86_64/server/docker-host (walters, 15:19:42) * ACTION: stickster Send out whenisgood to figure out a slot for next week (stickster, 15:37:54) * ACTION: walters will start a thread on official tree composes and mirroring.. (jzb, 15:38:03) * Where do we need help immediately, and who can step up? (jzb, 15:40:53) * We need to consider where object stores might be backed in the future, based on the observed delta from F21 Alpha (stickster, 15:46:27) Meeting ended at 15:55:09 UTC. Action Items * stickster Send out whenisgood to figure out a slot for next week * walters will start a thread on official tree composes and mirroring.. Action Items, by person --- * stickster * stickster Send out whenisgood to figure out a slot for next week * walters * walters will start a thread on official tree composes and mirroring.. * **UNASSIGNED** * (none) People Present (lines said) --- * stickster (48) * walters (48) * jzb (39) * mattdm (32) * nirik (29) * dgilmore (19) * misc (14) * KidProton (8) * oddshocks (5) * zodbot (3) * bochecha (3) * smooge (1) -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Agenda for today's meeting on Atomic
On Mon, Jul 21, 2014 at 09:21:22AM -0500, Joe Brockmeier wrote: > Hi all, > > In the interest of keeping things moving well, I threw together a quick > draft agenda: > > - Quick roll call > > - What is the minimum we need to get to alpha status? > (e.g., produce something testable, consumable, usable but not > necessarily "production quality") > > - What are other blockers we need to solve to be able to have an > official release? (as opposed to a remix) > > - Where do we need help immediately, and who can step up? > > - What are we missing entirely? > > - Action items for the next week or two > > - Agreement on next meeting time > > # # # > > Anything else? Thoughts, comments, flames? Thanks for sending this out, Joe. Looks good. -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Atomic status
On Fri, Jul 18, 2014 at 04:48:50PM -0400, Matthew Miller wrote: > On Fri, Jul 18, 2014 at 09:40:59AM -0400, Colin Walters wrote: > > Let's look at blocking issues for Atomic in Fedora: > > - Having rpm-ostree be run as part of nightly compose > > As I understand it, Dennis is working on this. Dennis, anyone -- let me know > where particular help is needed. David Gay (oddshocks) is also available to > help (pretty much full time for a little while once fedimg is in production > in the next few days, as I understand it). That's correct, and David, Dennis, Matt, and I talked about that as well. Before I left for vacation I believe David, Colin, Dennis, and some others met to discuss about how to approach the ostree work, but no tasks came out of it for David yet (at least then). > > - Content mirroring > > * Server with SSL, some level of redundancy > > * Open question around how often/when composes are done, and how much > > history is retained > > From when we last talked, I thought you were going to bring up this last one > as a policy question on the Fedora Cloud list? But also from our discussion, > it doesn't look like keeping even full history would be hugely significant > -- 1.6GB over the lifetime, _worst case_. I also don't think that we need to > have this answered urgently... it's something we need to know by October, > right? > > > - GPG signing > > Can you elaborate here? If I remember right we had discussed this as a > release blocker but not necessarily an immediate blocker (for example, not > all RPMs in F21 branch are currently signed.) > > > - Method of having Koji/ImageFactory pull mirrored OSTree repository > > content to compose ISOs > > I think this is just making the above mirror available to ImageFactory > during install. > > > > - MirrorManager integration (no code written on ostree side yet) > > To the best of my knowledge, code exists for all of the above except the > > last, and the last bit is hard to write without having a deployment of > > MirrorManager using it, which depends > > Again, let me know if it would help to have someone focused on this and I'll > see if I can find the right help. > > > I see two solution paths: > > - Double down and fix the above, continue trying to sync Atomic with > > Fedora > > Based on our conversations last week and earlier this week, I don't think > it's really so dire that it comes to "double down", but this is the > direction I'd like to continue in. It's important to Fedora Cloud, and it's > important to F21 messaging overall. > > > Would more regular meetings help? > > If it would, let's do it. :) +1. Given the speed and priority of Atomic, I think I'd benefit from a regular checkpoint to see where things are blocked and making sure specific tasks get assigned to someone to do, especially where it hits my team. I feel like we have a sort of split -- some tasks for which we have resources for (like coding that David can help with), but not sure of direction; and some tasks for which we have a better idea of direction (the infra related stuff, to some extent), but not sure about resources. The resource problem we can probably solve, and we have alternatives other than doubling down, or overloading everyone already doing lots of stuff. But we need to be able to quantify exactly what's not getting done and why first, so I'd love to hash that out. Is Fedocal what we'd use to set something up for early next week? -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Plan of work for Copr signing
On Fri, May 23, 2014 at 10:07:40AM +0200, Miroslav Suchý wrote: > On 05/22/2014 08:47 PM, Paul W. Frields wrote: > >Has there been any review of the package signing process by security > >guys? Since this is presumably different from the standard Fedora > >package signing process, it might make sense to have someone advise, > >if not done already. > > Will do. Cool, I think there is a secur...@lists.fp.o for just such a thing. -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Plan of work for Copr signing
On Thu, May 22, 2014 at 09:58:47AM +0200, Miroslav Suchý wrote: > FYI - this is my schedule of work needed to sign packages in Copr: > > Hardware: > = > Next visit in PHX is planned on June/July. Next one is January of 2015. > > Ideal (and most paranoid) setup would require one physical machine for > Signing server and one for copr-backend and one wire between them. With no > remote access to signing server. > > But we have not HW for this. > > What we can have is have signing machine in VM with restrictive SW defined > network. If that VM can be only one VM on host, then it would be great. > > To set up VM and networking and create ansible manifest, can take up to one > week. > > > Software: > = > I would go the obs-sign way. > It would require to get one patch into GPG2. Patch is made by SuSe, but does > not live in upstream. > TMraz (RH packager) preliminary approved this patch, but have few comments, > which would need to be address (name of cmd option, no man page...). Then I > will try to get it in upstream, but there is risc of rejecting. But TMraz is > willing to accept it as patch into Fedora and RH package. This is backup > plan. (1.5 week to work on patch, 1 w for communitation with upstream or > tmraz) > JStribrny promised to re-package obs-sign. (0.5w) > We should enhance documentation of obs-sign and likely write HOWTO for > deployment. (0.75w) > We need to deploy and configure obs-sign on VM. (0.75w) > Mutatis mutandis of Copr (1w). > Sum it up (5.5 week) > > Total = 6.5 weeks Has there been any review of the package signing process by security guys? Since this is presumably different from the standard Fedora package signing process, it might make sense to have someone advise, if not done already. -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Looking for admin to increase attachment size limit of fudcon-planning trac
On Thu, Apr 24, 2014 at 09:57:51PM +0800, Zamir SUN wrote: > copy this to infrastructure list > > On 2014/4/24 21:17, Alick Zhao wrote: > >Hi all, > > > >I wonder who is currently an admin of fudcon-planning trac. Please help > >to increase the attachment size limit to allow good quality receipt > >files. Similar things has been done at fedora-apac trac ticket. > > > >Ref: https://fedorahosted.org/fedora-infrastructure/ticket/3683 I'm one of the admins, and I've upped the limit to 2 MB. -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: About cnucnu web
On Mon, Jan 20, 2014 at 02:16:25PM -0500, Rahul Sundaram wrote: > On Mon, Jan 20, 2014 at 9:38 AM, Pierre-Yves Chibon wrote: > > > On Sat, Dec 21, 2013 at 11:36:54AM +0800, Christopher Meng wrote: > > > On Fri, Dec 20, 2013 at 10:11 PM, Pierre-Yves Chibon > > > wrote: > > > > * Domain name suggestions? (release-monitoring.org, cnucnu.org, > > cnucnuweb.org, > > > > ?) > > > > > > releases-monitoring.org maybe the best among these three. I think some > > > guys may already know ROSA's ABI tracker and use it for comparing > > > ABI/API differences. http://upstream-tracker.org. It's free and open > > > for all users without OS limitation. And users can know its usage from > > > the name quickly. > > > > Any other vote for the domain name? :) > > > > FWIW, I am for release-monitoring.org as well That domain name seems in tune with the purpose, +1. -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: 2014 dreaming
On Wed, Jan 08, 2014 at 07:10:43PM +0100, Pierre-Yves Chibon wrote: > On Thu, Dec 19, 2013 at 02:16:31PM -0700, Kevin Fenzi wrote: > > Greetings. > > > > I meant to send this out sooner, but with the Fedora 20 release things > > have been crazy. :) Now that we are nearing the end of 2013, I think it > > might be a nice time to think ahead to next year. > > > > What would you love to see happen? What would you like to work on > > making happen? > > (even if it's not practical resource wise or logistically) > > > > Here's a list of some of mine: > > > > * 0 downtime upgrades. By this I mean we can update and reboot all our > > servers (probibly in some specific order with specific actions > > between) and not have to schedule any downtime or notify users > > anything is going on. This means at least that we have db > > replication/failover working and 2 of everything. > > > > * Migration to ansible fully done, with all hosts moved over and > > rebuilt and working. > > > > * Migration to RHEL7. :) > > > > * Ticket queue down to a very small set. When I first started it was > > gigantic, then I closed/fixed/redirected a lot of the ticket and we > > started going down in number, but over the last year or so we have > > hovered between 140-150. > > > > * Migration to hyperkitty/mailman3 complete with all lists moved. > > > > * All hosts selinux enforcing. :) > > > > * No "app" servers left. All applications split out to their own (at > > least pair) of instances. > > > > * Logging from every app/server goes to a known place and we process > > them all looking for problems. > > Here is my list (in no particular order): > > * FAS3 > - We need to port FAS to a new(er) framework > - Move the user auth completely out of FAS? > - Unit-tests! > - Integrate w/ announces -> new election, new deadline... > * Develop a 0Auth server? > * fedocal >- A number of changes and enhancements are required and I started a little > bit on this already :) > * pkgdb2 > - We are already close, but we need to push it to production > and fix the bugs that will be encountered > * Port our webapp to 2FA > - Toshio started some work on this but we need to continue it > * Unit-tests > - This makes our product so much more robust that we really > should keep writing them > * Fedmsg-Notifications (FMN) > - Already quite advanced, we need to push it to production and > add new notification options. > * Cnucnu web > - Basis is there but it would be nice to add to the database more > mapping of the project in more linux distribution than just Fedora > * Review-server > - Kick the package review-request out of bugzilla > - Tight(er) integration with koji > - Run fedora-review on each changes > - Run scratch build on each changes > - Provide a temporary git repo for each review that could then be > merged into the official git repo after the review > - This seems to interest the dev and stack group, see third point at: > > https://fedoraproject.org/wiki/User:Mmaslano/Draft:Env_and_Stack_PRD#Automation > - We may want to see with tflink and the QA if there are tools in addition > to > fedora-review that could be included > * Elections > - It would be nice to re-work the election application to build in some > sort of plugin systems allowing different votes > - Eventually it would be very nice to merge nuancier into election as > a plugin > => I have no real idea yet on how to do so, I just think it would be nice > to have it :) > * MirrorManager > - With FAS it is probably the oldest application that we have that does not > have a new version coming. We need to update it (new db scheme (?), new > framework, unit-tests...) > * Auto-rebuild > - Using fedmsg or koji directly we are able to retrieve the date of the last > successful build of any packages in our collections. This way we could > trigger > an automatic rebuild to check FTBFS of every package every X time (6 > month?). > * Auto-rebuild of broken deps > - When we detect a broken deps we should try to rebuild all the dependency > and > propose the change to the packager if the build succeeded Along the lines of automatic rebuilding, we should also think about what it will take to support the vision of continuous integration and increased automated testing that people like mattdm, threebean, and tflink have been discussing. Maybe this is a difficult proposition simply using our current lineup of koji serve
Re: Need help with script problem
On Wed, Jul 10, 2013 at 04:59:58PM -0600, Kevin Fenzi wrote:
> On Wed, 10 Jul 2013 17:12:23 -0400
> "Paul W. Frields" wrote:
>
> > The direct download numbers I'm gathering via script for F19 seem way
> > off. So much so that I think I must be missing a good bit of data.
> >
> > The script I'm using is attached. Can someone help me understand
> > where I might be missing relevant data? Looking through the entire
> > hosts log structure is kind of daunting but I'm thinking there might
> > have been some well-known change that moved a chunk of log data to a
> > place I'm not looking through.
>
> For one thing the logs are now bz2'ed...
>
> ie:
>
> /var/log/hosts/proxy09.vpn.fedoraproject.org/2013/07/09/http/download.fedoraproject.org-access.log.bz2
>
> [kevin@log02 ~]$ egrep
> "Fedora-19.*\.iso"
> /var/log/hosts/proxy09.vpn.fedoraproject.org/2013/07/09/http/download.fedoraproject.org-access.log.bz2
> | wc -l 0
> [kevin@log02 ~]$ bzgrep
> "Fedora-19.*\.iso"
> /var/log/hosts/proxy09.vpn.fedoraproject.org/2013/07/09/http/download.fedoraproject.org-access.log.bz2
> | wc -l 1478
>
> Patch:
>
> 15,16c15,16
> < egrep "Fedora-$RELEASE.*\.iso" \
> <
> /var/log/hosts/proxy*/${YEAR}/${MONTH}/${DAY}/http/download.fedoraproject.org-access.log
> | \ ---
> > bzgrep "Fedora-$RELEASE.*\.iso" \
> >
> > /var/log/hosts/proxy*/${YEAR}/${MONTH}/${DAY}/http/download.fedoraproject.org-access.log.bz2
> > | \
>
> I have no idea if those numbers look better or not tho, there might be
> something more going on.
Still looks really anemic.
$ NDAYS=9 ~/bin/dl-stats.sh
Direct downloads:
2013-07-02 672
2013-07-03 5130
2013-07-04 4769
2013-07-05 2942
2013-07-06 2540
2013-07-07 1762
2013-07-08 1495
2013-07-09 2051
2013-07-10 1852
That's roughly a half order of magnitude off from what I'd expect.
--
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
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Disable user Alberto783
On Wed, Apr 11, 2012 at 10:36:54AM -0400, seth vidal wrote: > On Wed, 11 Apr 2012 10:35:34 -0400 > "Paul W. Frields" wrote: > > > https://fedoraproject.org/wiki/Special:Contributions/Alberto783 > > > > This user has been spamming the wiki all morning. Can we please have > > the account disabled/blocked/removed? > > > > It's already been done. > All of his edits have been rolledback, too. > thanks Thanks guys! -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Disable user Alberto783
On Wed, Apr 11, 2012 at 10:35:34AM -0400, Paul W. Frields wrote: > https://fedoraproject.org/wiki/Special:Contributions/Alberto783 > > This user has been spamming the wiki all morning. Can we please have > the account disabled/blocked/removed? Catching up to wiki mail, I see that Kevin and Seth have been reverting the edits, so I assume they're already on the case. ;-) -- 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 ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
