Re: February status update for Fedora Infrastructure Apprentices

[David Shier]

0. odin2016
1. Yes.
2. I think so.
3. Yes.
4. Yes.
5. No.
6. Finding tickets that are not already being worked.
7. Yes, yes.
8. Yes.
9. Sleeping, running, hopefully doing some things around here. if my young kids 
will allow it. :)
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: February status update for Fedora Infrastructure Apprentices

[Amitakhya Phukan]

Hello all,

On Tue, Feb 2, 2016 at 5:06 AM, Kevin Fenzi  wrote:

> You are getting this email because you are in the 'fi-apprentice' group
> in the fedora account system (or are reading this on the
> infrastructure list).
>
> Feel free to reply just directly to me, or cc the infrastructure list
> for everyone to see and comment on.
>
> https://fedoraproject.org/wiki/Infrastructure_Apprentice
>
> At the first of every month(or so), I am going to be sending out an
> email like this one. I would like feedback on how things are going for
> you.
>
> I'd like to ask for everyone to send me a quick reply with the
> following data or anything related you can think of that might help us
> make the apprentice program more useful.
>
> 0. Whats your fedora account system login?
>
>
aphukan


> 1. Have you logged in and used your fi-apprentice membership to look at
> our machines/setup in the last month? Do you plan to?
>
>
Yes


> 2. Has it helped you decide any area you wish to focus on or contribute
> to more?
>
> 3. Have you looked at or been able to work on any of the fi-apprentice
> 'easyfix' tickets?
> https://fedorahosted.org/fedora-infrastructure/report/14
>
>
Yes


> 4. Do you still wish to be a member of the group? If not (for whatever
> reason) could you provide any hints to help others down the road?
>
>
Yes



> 5. Is there any help or communication or ideas you have that would help
> you do any of the above?
>
> 6. What do you find to be the hardest part of getting involved?
> Finding things to work on? Getting attention from others to help you?
> Finding tickets in your interest area?
>
> 7. Have you been able to make any weekly irc meetings? Do you find them
> helpful or interesting?
>
> 8. Have you logged into our Gobby instance and read/seen/added to our
> meeting agenda? https://fedoraproject.org/wiki/Gobby
>
> 9. What will you spend leap day on this year? (2016-02-29)
>
>
That's an extra Monday. Might take the day off !!


> Any other general feedback is also quite welcome, including
> improvements to this email, the wiki page, etc.
>
> Any folks I do not hear from in the next week will be removed from the
> group. (Note that it's easy to be readded when you have time or
> whatever and it's nothing at all personal, we just want to keep the
> group up to date with active folks).
>
> Thanks, and looking forward to your feedback!
>
> kevin
>



-- 
Best regards,
Amitakhya Phukan
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: February status update for Fedora Infrastructure Apprentices

[Aleš Petrovický]

Hi,
responses are in line...

Dne 2.2.2016 v 00:36 Kevin Fenzi napsal(a):
> You are getting this email because you are in the 'fi-apprentice' group
> in the fedora account system (or are reading this on the
> infrastructure list). 
> 
> Feel free to reply just directly to me, or cc the infrastructure list
> for everyone to see and comment on. 
> 
> https://fedoraproject.org/wiki/Infrastructure_Apprentice
> 
> At the first of every month(or so), I am going to be sending out an
> email like this one. I would like feedback on how things are going for
> you.
> 
> I'd like to ask for everyone to send me a quick reply with the
> following data or anything related you can think of that might help us
> make the apprentice program more useful.
> 
> 0. Whats your fedora account system login?
alda
> 
> 1. Have you logged in and used your fi-apprentice membership to look at
> our machines/setup in the last month? Do you plan to?
yes and yes
> 
> 2. Has it helped you decide any area you wish to focus on or contribute
> to more?
not yet, but Iam open to do any work
> 
> 3. Have you looked at or been able to work on any of the fi-apprentice
> 'easyfix' tickets?
> https://fedorahosted.org/fedora-infrastructure/report/14
yes, I am working on Varnish caching ticket now
> 
> 4. Do you still wish to be a member of the group? If not (for whatever
> reason) could you provide any hints to help others down the road?
yes
> 
> 5. Is there any help or communication or ideas you have that would help
> you do any of the above?
yes, during a last few weeks, Iam trying to catch someone with access on
IRC to check and push my patches to staging and I also try ask for help
at meeting, but I have no response from anyone who promise help to me. I
know that I must be patient, but its hard and frustrating if it takes
weeks. I hopes its temporary state, because communications and help
works well in 2015.

> 
> 6. What do you find to be the hardest part of getting involved?
> Finding things to work on? Getting attention from others to help you?
> Finding tickets in your interest area? 

finding thinks to work on

> 
> 7. Have you been able to make any weekly irc meetings? Do you find them
> helpful or interesting? 
Yes, Yes

> 
> 8. Have you logged into our Gobby instance and read/seen/added to our
> meeting agenda? https://fedoraproject.org/wiki/Gobby
Yes
> 
> 9. What will you spend leap day on this year? (2016-02-29)
In work Iam presuming
> 
> Any other general feedback is also quite welcome, including
> improvements to this email, the wiki page, etc.
No
> 
> Any folks I do not hear from in the next week will be removed from the
> group. (Note that it's easy to be readded when you have time or
> whatever and it's nothing at all personal, we just want to keep the
> group up to date with active folks).
> 
> Thanks, and looking forward to your feedback!
> 
> kevin
> 

Ales
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: pagure tickets brainstorming

[Pierre-Yves Chibon]

On Mon, Jan 25, 2016 at 02:27:09PM -0700, Kevin Fenzi wrote:
> * Custom ticket statuses (some projects use this to make statuses that
>   are more descriptive for their project, like "upstream" or "accepted"
>   or whatever. This might require splitting the status of tickets to
>   open or closed 'status' and have a seperate 'resolution' or
>   something. 

There is a ticket for this: https://pagure.io/pagure/issue/538
but I've been asking what the idea/use-case is for this.

> * Tagging of issues. Tons of projects use a 'meeting' keyword to mark
>   tickets they want to discuss in meetings. A way to display only
>   tagged tickets would be good and a bonus would be a irc friendly
>   meeting output to copy and paste. I see a "Tags:" field, but not how
>   to populate it. Is this in progress?

So for each ticket, you can edit the metadata on the right column and add/remove
tags there.
Then clicking on the tag will give you the list of tickets with this tag.
You can also just click on the tag from the tag list shown above all the tickets
on the page listing them:
https://pagure.io/pagure/issues (right next to [open|close])

> * A way to cc or bcc a group of people on all tickets in a project. Do
>   we already have this?

That's not currently there, I do think people @mentioned in a ticket should be
added, but it's not there yet. As for batch or CC'ing a group, it'd be a second
stage.

I added a ticket to trac the @mention question :
https://pagure.io/pagure/issue/690

> * Milestones (but I am not sure how much these are used). Some projects
>   have "Fedora 24 Alpha" "Fedora 24 Beta" type milestones for things to
>   be finished before some event. Perhaps we just want to drop this idea
>   in favor of some kind of deadline listing and emiting a message when
>   the deadline is reached? "This ticket was supposed to be done by now!"

So pagure uses tags on ticket for this.
You would tag the ticket: easyfix, f24
Then watching the f24 tags you can see a progress bar indicating the percentage
of tickets close vs open, for example:
https://pagure.io/pagure/issues?tags=0.2 (96 tickets closed, 0 open)

It misses the concept of dead-line, but I always wondered of the applicability
of it, what happens when the dead-line is passed? Issue shows in red? Are
closed? But then doesn't the devs/users know they are late?

> * Templates. We use these a lot in infrastructure. Basically when
>   filing a new issue there's a list of templates and when someone
>   selects one it sets the initial contents and assigned and such. These
>   are handy for making sure users give the needed info for a type of
>   request. 

There is a ticket requesting this:
https://pagure.io/pagure/issue/585

> * Theres a batch modify plugin that lets you modify a bunch of tickets
>   at once. I don't think this is critical, but might be nice to have. 

Currently not there, but we have an API and we can extend it as needed.

> * Is there a way to completely delete a ticket? Sometimes we have done
>   that on trac for spam tickets. 

That's already available


So in summary what is missing is:
- cc people to a ticket or at least notify them when @mentioning them
- Custom status
- Custom templates for issues


Thanks,
Pierre


pgp2mEVucaQkI.pgp
Description: PGP signature
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: Infra YIR draft

[Zach Villers]

Hello - tried to add in everyone's edits. I also created a Gobby doc titled
"Infra 2015 YIR" and added to Gobby - Infra Meeting Next as a topic.

On Mon, Feb 1, 2016 at 5:29 PM Kevin Fenzi  wrote:

> On Mon, 1 Feb 2016 15:33:42 -0500
> Ralph Bean  wrote:
>
> > On Thu, Jan 28, 2016 at 02:35:57PM -0500, Zach Villers wrote:
> > > Here is a draft of a Year In Review post for the Community Ops
> > > Blog. I left some things blank (and omitted ALOT - wow - lost of
> > > stuff happened in 2015). I didn't take a stab at the conclusion or
> > > 2016 goals section. JFlory7 had asked Infra if we would submit a
> > > YIR post. Kevin and Ralph (Nirik/Threebean) also had some ideas. I
> > > left out ticket and outage numbers, but can add in something if we
> > > want. This is formatted as markdown.
> >
> > Thanks for this Zach!  I took it and just added more pieces:
>
> Thanks to both of you. ;)
>
> Perhaps we should also try and go over this in the meeting thursday and
> then send it off after that? Would give people a chance to look it over
> and specific time to read on and comment on it.
>
> > Introduction
> > 
> >
> > The Infrastructure Team consists of dedicated volunteers and
> > professionals managing the servers, building the tools and utilities,
> > and creating new applications to make Fedora development a smoother
> > process. We're located all over the globe and communicate primarily by
> > IRC and e-mail.
> >
> > Infrastructure Highlights
> > -
> >
> > * Ansible Migration - We believe Ansible is the best new technology
> >   for systems deployment and management. This year, Infrastructure
> >   team moved all remaining Puppet recipes (78 at start of FY2016) in
> >   the infrastructure to Ansible playbooks. The automation provided by
> >   Ansible allows us to quickly fix/rebuild/scale our existing services
> >   and deploy new services.
> >   https://infrastructure.fedoraproject.org/cgit/ansible.git/
> Additionally, we worked with Ansible upstream to test the new Ansible
> 2.0 and have just recently moved our control host to 2.0.
>
> > * RHEL 6 to 7 conversion - As we moved hosts over from puppet to
> > ansible, we used the opportunity to rebuild all hosts on top of RHEL7
> > and dealt with all the yak shaving entailed therein.
>
> The last RHEL6 instances (aside from some few that need to stay like
> jenkins RHEL6 builder) should go away next year.
>
> > * OpenStack migration - We migrated our old Openstack instance to a
> > newer version and moved out from under the .cloud.fedoraproject.org
> > domain to .fedorainfracloud.org for HSTS reasons.
> >
> > Development Highlights
> > --
> >
> > * Pagure - Our very own git forge!  It just got a facelift last week
> > and we think it’s pretty cool.
> >   https://pagure.io
> >   https://pagure.io/pagure
> >   https://fedoramagazine.org/pagure-diy-git-project-hosting/
> >
> > * HyperKitty - HyperKitty is a web front end to the new
> >   Mailman version 3 which allows users to browse topics in a more
> >   familiar, forum-like interface. We will complete development of
> >   this application and deploy for use with Fedora mailing lists.
> >
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/
> >   https://gitlab.com/mailman/hyperkitty
> >   http://aurelien.bompard.org/post/2015/05/21/Mailman-3-is-out
>
> Might reword this a little. Hyperkitty is the archiver/web interface.
> There's also the base mailman3 and postorius (the admin interface).
>
> > * Koschei - Koschei is a continuous integration service for
> >   Fedora packages. Koschei is aimed at helping Fedora developers
> >   by detecting problems as soon as they appear in rawhide - it
> >   tries to detect package FTBFS in rawhide by scratch-building
> >   them in Koji.
> >   https://apps.fedoraproject.org/koschei
> >   https://github.com/msimacek/koschei
> >
> > * Bodhi2 - Pronounced as bo-dee is a buddhist term for the wisdom
> >   by which one attains enlightenment. Bodhi is a modular web-based
> >   system that facilitates the process of publishing package updates
> >   for Fedora. It maintains a single stage of repositories by
> >   adding/updating/removing packages.
> >   https://bodhi.fedoraproject.org/
> >   https://github.com/fedora-infra/bodhi
> >
> > * MirrorManager 2 - This started with a FAD at the end of 2014 but
> > was finished and deployed in 2015.  The new MirrorManager 2 is
> > written on top of a modern framework and has many more people
> > familiar with its code now.
> > https://admin.fedoraproject.org/mirrormanager
> > https://github.com/fedora-infra/mirrormanager2
> >
> > * fedora-packages - This service got a partial rewrite this year,
> > attempting to resolve some data stability issues.
> >   https://apps.fedoraproject.org/packages
> >   https://github.com/fedora-infra/fedora-packages
> >   http://threebean.org/blog/history-of-fedora-packages/
> >
> > * 

[release] elections: 2.6 and 2.6.1

[Pierre-Yves Chibon]

Good Morning everyone,

I just cut and pushed two new releases of fedora-elections: 2.6 and 2.6.1

Here are the corresponding changelog
* Tue Feb 02 2016 Pierre-Yves Chibon  - 2.6.1-1
- Update to 2.6.1
- Fix editing a single candidate when the election asks for the FAS names
- Fix displaying the candidates' names if the sync with FAS wasn't complete

* Mon Feb 01 2016 Pierre-Yves Chibon  - 2.6-1
- Update to 2.6
- Add the possibility to change one's vote on an election (Joshua Santos)
- Cache the candidate's name retrieved from FAS locally
- Improve the runserver script and adjust the README accordingly
- Drop the requirement on dogpile.cache

It was running fine in stg, so I pushed to prod as well.

More testing always welcome :)

Happy voting,
Pierre


pgp9owuZNYsei.pgp
Description: PGP signature
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: February status update for Fedora Infrastructure Apprentices

[Bruno Queiros]

0. Whats your fedora account system login?

lnxslck

1. Have you logged in and used your fi-apprentice membership to look at
our machines/setup in the last month? Do you plan to?

yes

2. Has it helped you decide any area you wish to focus on or contribute
to more?

no

3. Have you looked at or been able to work on any of the fi-apprentice
'easyfix' tickets?
https://fedorahosted.org/fedora-infrastructure/report/14

yes

4. Do you still wish to be a member of the group? If not (for whatever
reason) could you provide any hints to help others down the road?

Of course

5. Is there any help or communication or ideas you have that would help
you do any of the above?

not really

6. What do you find to be the hardest part of getting involved?
Finding things to work on? Getting attention from others to help you?
Finding tickets in your interest area?

Finding things to work on

7. Have you been able to make any weekly irc meetings? Do you find them
helpful or interesting?

Yes

8. Have you logged into our Gobby instance and read/seen/added to our
meeting agenda? https://fedoraproject.org/wiki/Gobby

no

9. What will you spend leap day on this year? (2016-02-29)

Working ...

Kevin Fenzi  escreveu no dia segunda, 1/02/2016 às 23:36:

> You are getting this email because you are in the 'fi-apprentice' group
> in the fedora account system (or are reading this on the
> infrastructure list).
>
> Feel free to reply just directly to me, or cc the infrastructure list
> for everyone to see and comment on.
>
> https://fedoraproject.org/wiki/Infrastructure_Apprentice
>
> At the first of every month(or so), I am going to be sending out an
> email like this one. I would like feedback on how things are going for
> you.
>
> I'd like to ask for everyone to send me a quick reply with the
> following data or anything related you can think of that might help us
> make the apprentice program more useful.
>
> 0. Whats your fedora account system login?
>
> 1. Have you logged in and used your fi-apprentice membership to look at
> our machines/setup in the last month? Do you plan to?
>
> 2. Has it helped you decide any area you wish to focus on or contribute
> to more?
>
> 3. Have you looked at or been able to work on any of the fi-apprentice
> 'easyfix' tickets?
> https://fedorahosted.org/fedora-infrastructure/report/14
>
> 4. Do you still wish to be a member of the group? If not (for whatever
> reason) could you provide any hints to help others down the road?
>
> 5. Is there any help or communication or ideas you have that would help
> you do any of the above?
>
> 6. What do you find to be the hardest part of getting involved?
> Finding things to work on? Getting attention from others to help you?
> Finding tickets in your interest area?
>
> 7. Have you been able to make any weekly irc meetings? Do you find them
> helpful or interesting?
>
> 8. Have you logged into our Gobby instance and read/seen/added to our
> meeting agenda? https://fedoraproject.org/wiki/Gobby
>
> 9. What will you spend leap day on this year? (2016-02-29)
>
> Any other general feedback is also quite welcome, including
> improvements to this email, the wiki page, etc.
>
> Any folks I do not hear from in the next week will be removed from the
> group. (Note that it's easy to be readded when you have time or
> whatever and it's nothing at all personal, we just want to keep the
> group up to date with active folks).
>
> Thanks, and looking forward to your feedback!
>
> kevin
> ___
> infrastructure mailing list
> infrastructure@lists.fedoraproject.org
>
> http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org
>
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

unsubscribe

[Juan Jimenez-Anca]

Hello,

How can I unsubscribe from this list? I've tried with https://lists.fed
oraproject.org/admin/accounts/subscriptions/ but with no success

Thanks
Juan___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: unsubscribe

[Paulo Ledo]

Hello,
Me too
On Feb 2, 2016 9:06 AM, "Juan Jimenez-Anca"  wrote:

> Hello,
>
> How can I unsubscribe from this list? I've tried with
> https://lists.fedoraproject.org/admin/accounts/subscriptions/ but with no
> success
>
> Thanks
> Juan
>
> ___
> infrastructure mailing list
> infrastructure@lists.fedoraproject.org
>
> http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org
>
>
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: unsubscribe

[Stephen John Smoogen]

Can you try mailto:infrastructure-le...@lists.fedoraproject.org and
let me know if that works. We need to get this fixed asap as I think
this is becoming the number one FAQ email for mailman2.

On 2 February 2016 at 04:06, Juan Jimenez-Anca  wrote:
> Hello,
>
> How can I unsubscribe from this list? I've tried with
> https://lists.fedoraproject.org/admin/accounts/subscriptions/ but with no
> success
>
> Thanks
> Juan
>
> ___
> infrastructure mailing list
> infrastructure@lists.fedoraproject.org
> http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org
>



-- 
Stephen J Smoogen.
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: February status update for Fedora Infrastructure Apprentices

[Patrick Creech]

On Mon, 2016-02-01 at 16:36 -0700, Kevin Fenzi wrote:
> You are getting this email because you are in the 'fi-apprentice' group
> in the fedora account system (or are reading this on the
> infrastructure list). 
> 
> I'd like to ask for everyone to send me a quick reply with the
> following data or anything related you can think of that might help us
> make the apprentice program more useful.
> 
> 0. Whats your fedora account system login?

pcreech17

> 1. Have you logged in and used your fi-apprentice membership to look at
> our machines/setup in the last month? Do you plan to?

Yes!

> 2. Has it helped you decide any area you wish to focus on or contribute
> to more?

Yes

> 3. Have you looked at or been able to work on any of the fi-apprentice
> 'easyfix' tickets?
> https://fedorahosted.org/fedora-infrastructure/report/14

Not recently

> 4. Do you still wish to be a member of the group? If not (for whatever
> reason) could you provide any hints to help others down the road?

Yes I do

> 5. Is there any help or communication or ideas you have that would help
> you do any of the above?

Not at this time

> 6. What do you find to be the hardest part of getting involved?
> Finding things to work on? Getting attention from others to help you?
> Finding tickets in your interest area? 

Spare time at the moment.

> 7. Have you been able to make any weekly irc meetings? Do you find them
> helpful or interesting? 

Yes.  Both

> 8. Have you logged into our Gobby instance and read/seen/added to our
> meeting agenda? https://fedoraproject.org/wiki/Gobby

I have not

> 9. What will you spend leap day on this year? (2016-02-29)

Probably working

> Thanks, and looking forward to your feedback!
> 
> kevin
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: Infra YIR draft

[Pierre-Yves Chibon]

On Mon, Feb 01, 2016 at 03:28:36PM -0700, Kevin Fenzi wrote:
> On Mon, 1 Feb 2016 15:33:42 -0500
> Ralph Bean  wrote:
> 
> > On Thu, Jan 28, 2016 at 02:35:57PM -0500, Zach Villers wrote:
> > > Here is a draft of a Year In Review post for the Community Ops
> > > Blog. I left some things blank (and omitted ALOT - wow - lost of
> > > stuff happened in 2015). I didn't take a stab at the conclusion or
> > > 2016 goals section. JFlory7 had asked Infra if we would submit a
> > > YIR post. Kevin and Ralph (Nirik/Threebean) also had some ideas. I
> > > left out ticket and outage numbers, but can add in something if we
> > > want. This is formatted as markdown.  
> > 
> > Thanks for this Zach!  I took it and just added more pieces:
> 
> Thanks to both of you. ;) 
> 
> Perhaps we should also try and go over this in the meeting thursday and
> then send it off after that? Would give people a chance to look it over
> and specific time to read on and comment on it. 

Global +1 for me, text looks good :)

> > * MirrorManager 2 - This started with a FAD at the end of 2014 but
> > was finished and deployed in 2015.  The new MirrorManager 2 is
> > written on top of a modern framework and has many more people
> > familiar with its code now.
> > https://admin.fedoraproject.org/mirrormanager
> > https://github.com/fedora-infra/mirrormanager2

I just wonder a little about this one MM2 isn't quite an user-facing app, so
while it might be interesting to mention it, I don't know if it is that
interesting to bring it forward here for our readers.


Pierre


pgp3LoVYlUcfT.pgp
Description: PGP signature
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: a new MirrorManager-related tool for stripping old metadata and pushing critical updates in a defined time

[Adrian Reber]

On Fri, Jan 08, 2016 at 02:40:52PM -0500, Patrick Uiterwijk wrote:
> > 3. The tool will go through all metalinks for f23-updates (all primary
> > architectures), and drop each  section which has
> >  older than the provided date (let's say midnight UTC).
> 
> Please note that there are no metalink files: these files are generated on 
> the fly from a cache
> by the mirrorlist servers.
> I have a patch for this that I'll submit upstream to add the feature itself, 
> and will discuss
> with releng how they want to fire this off.

The new script is now available on mm-backend01: mm2_emergency-expire-repo

I think I have seen that Patrick also created a playbook to let the
script run in the correct environment and configuration.

We have successfully tested the script in the staging environment and
after it runs only the newest repomd.xml file is listed in the metalink.

As far as I understand MirrorManager this script only changes the number
of alternate repomd.xml files in the metalink. The number of mirrors
returned does not change. Depending on the last run of the master mirror
crawler (umdl), the state of the crawler checking the mirrors and the
mirrors which are running report_mirror this may lead to situation where
mirrors are offered to clients which might not yet have the newest
files.

Adrian


pgprqb0L5EUX9.pgp
Description: PGP signature
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org