Re: February status update for Fedora Infrastructure Apprentices

2016-02-15 Thread Mikolaj Izdebski 
On 02/02/2016 12:36 AM, Kevin Fenzi wrote:
> 0. Whats your fedora account system login?

mizdebsk

> 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, I did and I do.

> 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

Not in the past month.

> 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?

No.

> 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? 

Getting access to relevant systems.

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

Not in the past month.

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

Recently no.

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

Work, just like any other ordinary day.

-- 
Mikolaj Izdebski
Software Engineer, Red Hat
IRC: mizdebsk
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: ansible 2.0 on batcave01

2016-02-15 Thread Kevin Fenzi 
On Mon, 15 Feb 2016 15:04:10 +0100
Miroslav Suchý  wrote:

> Dne 12.2.2016 v 22:29 Kevin Fenzi napsal(a):
> > But it should migrate sometime... 1.9.x isn't going to be supported
> > all that much longer, so it should move to the new 2.0 api as soon
> > as it can.   
> 
> F23 will stay on 1.9.x, isn't it... oh, there is an update filed for
> F23. I really hope it did not get into stable.

Not yet. The plan was to keep it in testing until all the minor
breakage was fixed up (ie, 2.0.x) and things stablized. 

For epel there's going to be a ansible1.9 compat package (that will
live for just 6 months or something). I guess we could also push that
to Fedora, but seems like a lot of additional work. 

> > Would you like me to file a bug somewhere to track that, or it's
> > already on the roadmap?  
> 
> Not on the roadmap, but I'm putting it there. We will work on that
> next sprint (14 days from now).

Sounds good. 

kevin


pgpDj3W_VMPfN.pgp
Description: OpenPGP digital signature
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: ansible 2.0 on batcave01

2016-02-15 Thread Miroslav Suchý 
Dne 12.2.2016 v 22:29 Kevin Fenzi napsal(a):
> But it should migrate sometime... 1.9.x isn't going to be supported all
> that much longer, so it should move to the new 2.0 api as soon as it
> can. 

F23 will stay on 1.9.x, isn't it... oh, there is an update filed for F23.
I really hope it did not get into stable.

> Would you like me to file a bug somewhere to track that, or it's
> already on the roadmap?

Not on the roadmap, but I'm putting it there. We will work on that next sprint 
(14 days from now).

-- 
Miroslav Suchy, RHCA
Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys
___
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

2016-02-15 Thread Adrian Reber 
On Mon, Feb 08, 2016 at 07:43:14AM -0500, Kamil Paral wrote:
> > 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.
> 
> In other words, some of those repos included in the metalink might not 
> correspond to the included repomd.xml hash, right?

Correct.

> Is that a problem? I believe DNF should just skip those repos and find the 
> first one which matches the provided metadata hash.

It shouldn't be a problem. It is a situation which can happen anytime.
Just wanted to mention it once more.

Adrian


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