Re: FBR: Enable delta RPMs in Pungi+Bodhi

[Kevin Fenzi]

On 11/01/2017 06:05 PM, Dusty Mabe wrote:
> 
> 
> On 11/01/2017 11:53 AM, Patrick Uiterwijk wrote:
>> Seems that this is disabled by default.
>> Any +1s?
>>
>>
>> diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
>> b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
>> index 140f3438e..1c6dc02f2 100644
>> --- a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
>> +++ b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
>> @@ -55,6 +55,9 @@ repoclosure_backend = 'dnf'
>>  # CREATEREPO
>>  createrepo_c = True
>>  createrepo_checksum = 'sha256'
>> +createrepo_deltas = [
>> +   ('^Everything$', {'*': True})
>> +]
>>
>>  # CHECKSUMS
>>  media_checksums = ['sha256']
> 
> I'm thinking we don't need to create deltas for updates-testing repos?
> Should we special case it to only run for non u-t?

We have always done them for updates-testing too in the past.

We could drop that, but not sure how much it gets us. updates-testing is
usually quite a lot smaller than updates.

kevin



signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: Freeze Break Request: Fix FMN notifications for package (co)maintainers

[Kevin Fenzi]

On 11/01/2017 03:18 PM, Jeremy Cline wrote:
> Hey folks,
> 
> The latest version of FMN in production includes a patch[0] that breaks
> all the rules that query for package watchers, resulting in this[1]
> infrastructure issue. There's an open PR[2] on FMN that fixes the issue
> (reviews welcome). To fix this we have two options.
> 
> The first is to backport it to the current version in production (1.5)
> which should be trivial since nothing in this area has been touched in
> 2.0. We can then update production and carry on.
> 
> The second option is to update production to 2.0 now (I've included [2]
> as a patch in the RPM currently in stage). 2.0 includes a re-write of
> the back-end components of FMN to use Celery. It's running in stage now.
> Things to note about this:
> 
> * The FMN back-end now requires F26 because of celery versions.
> 
> * The FMN front-end is currently still on RHEL7, but I haven't updated
>   it in stage yet so I don't know if there's any adjustments necessary
>   for that (the front-end doesn't use celery so the fact that it's old
>   _shouldn't_ be a problem).
> 
> * Some care will need to be taken to switch over AMQP queue-wise,
>   especially because the current FMN queues are jammed with unformatable
>   messages it keeps requeuing (about 25K of them). We could also just
>   cut our losses and drop these.
> 
> * The scripts that monitor queue length will need to be adjusted since
>   there are more queues now and existing queues have been renamed.
> 
> One thing to note is that we're going to have to go through all those
> things above at some point anyway. FMN also doesn't really have anything
> to do with the release process so if it all goes south during the freeze
> it shouldn't matter.
> 
> I don't have a preference one way or the other, really. Whatever makes
> the admins happy makes me happy.

I'm a bit torn on this one. It seems a bit of a rush to push into prod
without having tested the frontends and confirmed that one fix for
watchers, but on the other hand nothing around release should block on
this and it would be nice to get prod on a code base that we have more
confidence in and ability to further fix.

do we have any way to tell what all those bad 25k messages are?
Likely copr rubygems rebuild ones? If thats all they are I am fine with
dropping them and starting afresh.

Can you make a patch to fix the monitoring scripts and attach it and
update the staging frontends and confirm they are ok?

With those in hand, I would be +1 just to upgrade and drop the old
messages I think.

kevin





signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: Freeze Break Request: Fix FMN notifications for package (co)maintainers

[Jeremy Cline]

On 11/01/2017 06:18 PM, Jeremy Cline wrote> * The FMN front-end is
currently still on RHEL7, but I haven't updated
>   it in stage yet so I don't know if there's any adjustments necessary
>   for that (the front-end doesn't use celery so the fact that it's old
>   _shouldn't_ be a problem).

For what it's worth, I did this today and it seems to be fine.


-- 
Jeremy Cline
XMPP: jer...@jcline.org
IRC:  jcline



signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: Server space for Fedora users?

[Matthew Miller]

On Thu, Nov 02, 2017 at 07:22:04PM +0100, Jun Aruga wrote:
> I want to build Mongo DB server somewhere in Fedora servers as my
> experiment for effective Fedora packaging.
> Because I want to research a correlation between the build error and how to
> be fixed by machine learning approach to automate RPM packaging.
> I do not want to pay my money for my private AWS server for that. :)
> Is it possible to a server space?

Possibly. https://fedoraproject.org/wiki/Request_For_Resources

Could your database run in Fedora's OpenShift instance?

-- 
Matthew Miller

Fedora Project Leader
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: Changes in hardware in December affecting QA servers

[Adam Williamson]

On Thu, 2017-11-02 at 12:41 -0400, Stephen John Smoogen wrote:
> I realized I had only informally gone over some of the items which
> will be changing in December when hardware is moved. However the date
> is finally arriving so it needs to be laid out more formally :).
> 
> In December, Infrastructure will be moving to new racks with better
> power monitoring, networking, and other tools. One of the side goals
> of this is that any old hardware which has been meant to be recycled
> over the years is to be done so. Which brings us to a set of qa
> systems which were listed to be replaced a couple of years ago.
> 
> qa01, qa02, qa03, qa04, qa05, qa07, qa08 are all IBM systems which
> have reached the end of the road and are planned not to be moved over
> to the new racks. [They have been scheduled to be removed for 2-3
> years now but it has finally come to that date.] What processes are
> currently running on these systems and what is needed to replace them?

qa05 and qa07 are the 'small' worker hosts for openQA (prod and stg,
respectively). Each hosts 4 of the total 14 x86_64 worker instances. So
losing them will cut the capacity of each openQA instance by about 30%.

What I'd need to replace them *most easily* is...another couple of
hosts in infra (technically, 'able to mount the NFS shares from the
openQA servers and connect back to the openQA servers via http and
possibly websockets', I think) capable of running four or more x86_64
VMs simultaneously, basically. Up till now openQA worker hosts have
always been dedicated to that task; there's no fundamental theoretical
reason why openQA workers couldn't run on a box which also does some
other stuff, though we'd have to check if there were any conflicts in
requirements as to how the box has to be set up (check the ansible
plays).

openQA has some newer capabilities that are basically about making
'more remote' workers possible, but I have not investigated those yet.
It *may* be possible to use those to run workers in some kind of cloud,
but that'd involve much more research and configuration and probably
debugging than just doing straight-up replacements in infra.

Another possibility I guess is having a single more powerful box
hosting workers for both prod and staging. Again I believe it may be
possible to get openQA to do this but it's different from what we do
now and I'd need to look into it.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Server space for Fedora users?

[Jun Aruga]

I want to build Mongo DB server somewhere in Fedora servers as my
experiment for effective Fedora packaging.

Because I want to research a correlation between the build error and how to
be fixed by machine learning approach to automate RPM packaging.
I do not want to pay my money for my private AWS server for that. :)

Is it possible to a server space?

For example,

A RPM package's repository has
  Time line: Commit A => Commit B

- Commit hash A that has a build error.
- Commit hash B that the error is fixed on.

The record may be like this.

Input data:
  - Fedora package name
  - The RPM spec file content at commit hash A.
  - root.log and build.log at the commit hash A.
Output data:
  - Commit hash B: How to be fixed for commit hash A's error.

Jun
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: [FBR] support msi binaries released on pagure.io

[Patrick マルタインアンドレアス Uiterwijk]

> Good Morning Everyone,
> 
> There was a report that releases.pagure.org doesn't serve .msi binaries
> properly.
> 
> I believe this diff should fix it:
> 
>  roles/pagure/frontend/templates/0_pagure.conf | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/roles/pagure/frontend/templates/0_pagure.conf
> b/roles/pagure/frontend/templates/0_pagure.conf
> index 4b76d20..8b3cda8 100644
> --- a/roles/pagure/frontend/templates/0_pagure.conf
> +++ b/roles/pagure/frontend/templates/0_pagure.conf
> @@ -175,6 +175,8 @@ WSGIDaemonProcess paguredocs user=git group=git 
> maximum-requests=1000
> display-na
>ServerName releases.pagure.org
>  {% endif %}
> 
> +  AddType application/octet-stream msi
> +
>
>  Options +Indexes
>  IndexOptions NameWidth=*
> 
> 
> Thoughts/+1s?

+1

> 
> Thanks,
> Pierre
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: [FBR] support msi binaries released on pagure.io

[Kevin Fenzi]

+1 here

kevin



signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Changes in hardware in December affecting QA servers

[Stephen John Smoogen]

I realized I had only informally gone over some of the items which
will be changing in December when hardware is moved. However the date
is finally arriving so it needs to be laid out more formally :).

In December, Infrastructure will be moving to new racks with better
power monitoring, networking, and other tools. One of the side goals
of this is that any old hardware which has been meant to be recycled
over the years is to be done so. Which brings us to a set of qa
systems which were listed to be replaced a couple of years ago.

qa01, qa02, qa03, qa04, qa05, qa07, qa08 are all IBM systems which
have reached the end of the road and are planned not to be moved over
to the new racks. [They have been scheduled to be removed for 2-3
years now but it has finally come to that date.] What processes are
currently running on these systems and what is needed to replace them?


-- 
Stephen J Smoogen.
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: [FBR] support msi binaries released on pagure.io

[Stephen John Smoogen]

+1

On 2 November 2017 at 11:11, Pierre-Yves Chibon  wrote:
> Good Morning Everyone,
>
> There was a report that releases.pagure.org doesn't serve .msi binaries
> properly.
>
> I believe this diff should fix it:
>
>  roles/pagure/frontend/templates/0_pagure.conf | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/roles/pagure/frontend/templates/0_pagure.conf 
> b/roles/pagure/frontend/templates/0_pagure.conf
> index 4b76d20..8b3cda8 100644
> --- a/roles/pagure/frontend/templates/0_pagure.conf
> +++ b/roles/pagure/frontend/templates/0_pagure.conf
> @@ -175,6 +175,8 @@ WSGIDaemonProcess paguredocs user=git group=git 
> maximum-requests=1000 display-na
>ServerName releases.pagure.org
>  {% endif %}
>
> +  AddType application/octet-stream msi
> +
>
>  Options +Indexes
>  IndexOptions NameWidth=*
>
>
> Thoughts/+1s?
>
> Thanks,
> Pierre
>
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
>



-- 
Stephen J Smoogen.
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: Freeze Break Request: fix typo in resultsdb public db dump copy script.

[Stephen John Smoogen]

+1 Backups are good.

On 2 November 2017 at 04:26, Pierre-Yves Chibon  wrote:
> On Wed, Nov 01, 2017 at 11:48:11AM -0700, Kevin Fenzi wrote:
>> Greetings.
>>
>> Before freeze I added resultsdb database dump to one of the ones we make
>> public.
>>
>> However, I had a small mistake in the script, so it wasn't making them
>> public.
>>
>> This should be a very simple change and I cannot imagine how it would
>> impact anything else. :)
>>
>> +1s?
>>
>> kevin
>> --
>> diff --git a/scripts/public-db-copy b/scripts/public-db-copy
>> index dc0300f..6bfd9a9 100755
>> --- a/scripts/public-db-copy
>> +++ b/scripts/public-db-copy
>> @@ -16,5 +16,5 @@ scp
>> db01.phx2.fedoraproject.org:/backups/mailman-$(date +%F).dump.xz /srv/web/in
>>  scp db01.phx2.fedoraproject.org:/backups/mbs-$(date +%F).dump.xz
>> /srv/web/infra/db-dumps/mbs.dump.xz
>>  scp db01.phx2.fedoraproject.org:/backups/odcs-$(date +%F).dump.xz
>> /srv/web/infra/db-dumps/odcs.dump.xz
>>  scp db01.phx2.fedoraproject.org:/backups/hyperkitty-$(date +%F).dump.xz
>> /srv/web/infra/db-dumps/hyperkitty.dump.xz
>> -scp db-qa01.qa.fedoraproject.org:/resultsdb-$(date +%F).dump.xz
>> /srv/web/infra/db-dumps/resultsdb.dump.xz
>> +scp db-qa01.qa.fedoraproject.org:/backups/resultsdb-$(date +%F).dump.xz
>> /srv/web/infra/db-dumps/resultsdb.dump.xz
>>  scp db01.phx2.fedoraproject.org:/backups/waiverdb-$(date +%F).dump.xz
>> /srv/web/infra/db-dumps/waiverdb.dump.xz
>
> +1 for me
>
>
> Pierre
>
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
>



-- 
Stephen J Smoogen.
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

[FBR] support msi binaries released on pagure.io

[Pierre-Yves Chibon]

Good Morning Everyone,

There was a report that releases.pagure.org doesn't serve .msi binaries
properly.

I believe this diff should fix it:

 roles/pagure/frontend/templates/0_pagure.conf | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/roles/pagure/frontend/templates/0_pagure.conf 
b/roles/pagure/frontend/templates/0_pagure.conf
index 4b76d20..8b3cda8 100644
--- a/roles/pagure/frontend/templates/0_pagure.conf
+++ b/roles/pagure/frontend/templates/0_pagure.conf
@@ -175,6 +175,8 @@ WSGIDaemonProcess paguredocs user=git group=git 
maximum-requests=1000 display-na
   ServerName releases.pagure.org
 {% endif %}

+  AddType application/octet-stream msi
+
   
 Options +Indexes
 IndexOptions NameWidth=*


Thoughts/+1s?

Thanks,
Pierre


signature.asc
Description: PGP signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: November status update for Fedora Infrastructure Apprentices

[Alberto Rodriguez Sanchez]

Hey all,


On 11/01/2017 12:29 PM, 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?
bt0dotninja
> 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?
sysadmin mainly
> 3. Have you looked at or been able to work on any of the fi-apprentice
> 'easyfix' tickets?
> https://pagure.io/fedora-infrastructure/issues?status=Open=easyfix
no this 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
> 5. Is there any help or communication or ideas you have that would help
> you do any of the above?
no 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?
find a ticket to work :)
> 7. Have you been able to make any weekly irc meetings? Do you find them
> helpful or interesting? Do you have any suggestions for changing them?
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 kind of computer are you replying to this email on right now?
> Desktop? Phone? Be as specific or not as you like. :)
Laptop, lenovo thinkpad t440s (my baby :P)
> Any other general feedback is also quite welcome, including improvements
> to this email, the wiki page, etc. Note that we recently revamped the
> getting started and other pages. Please do take a minute to re-read them
> and let me know if they are more clear or need further adjustments.
>
> 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
> todate with active folks).
>
> Thanks, and looking forward to your feedback!
>
> kevin
>
>
>
>
>
>
>
>
>
>
>
>
>
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: Freeze Break Request: fix typo in resultsdb public db dump copy script.

[Pierre-Yves Chibon]

On Wed, Nov 01, 2017 at 11:48:11AM -0700, Kevin Fenzi wrote:
> Greetings.
> 
> Before freeze I added resultsdb database dump to one of the ones we make
> public.
> 
> However, I had a small mistake in the script, so it wasn't making them
> public.
> 
> This should be a very simple change and I cannot imagine how it would
> impact anything else. :)
> 
> +1s?
> 
> kevin
> --
> diff --git a/scripts/public-db-copy b/scripts/public-db-copy
> index dc0300f..6bfd9a9 100755
> --- a/scripts/public-db-copy
> +++ b/scripts/public-db-copy
> @@ -16,5 +16,5 @@ scp
> db01.phx2.fedoraproject.org:/backups/mailman-$(date +%F).dump.xz /srv/web/in
>  scp db01.phx2.fedoraproject.org:/backups/mbs-$(date +%F).dump.xz
> /srv/web/infra/db-dumps/mbs.dump.xz
>  scp db01.phx2.fedoraproject.org:/backups/odcs-$(date +%F).dump.xz
> /srv/web/infra/db-dumps/odcs.dump.xz
>  scp db01.phx2.fedoraproject.org:/backups/hyperkitty-$(date +%F).dump.xz
> /srv/web/infra/db-dumps/hyperkitty.dump.xz
> -scp db-qa01.qa.fedoraproject.org:/resultsdb-$(date +%F).dump.xz
> /srv/web/infra/db-dumps/resultsdb.dump.xz
> +scp db-qa01.qa.fedoraproject.org:/backups/resultsdb-$(date +%F).dump.xz
> /srv/web/infra/db-dumps/resultsdb.dump.xz
>  scp db01.phx2.fedoraproject.org:/backups/waiverdb-$(date +%F).dump.xz
> /srv/web/infra/db-dumps/waiverdb.dump.xz

+1 for me


Pierre


signature.asc
Description: PGP signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: Higher quota for Copr

[Miroslav Suchý]

Dne 1.11.2017 v 16:37 Kevin Fenzi napsal(a):
> On 11/01/2017 05:32 AM, Miroslav Suchý wrote:
>> Hi,
>> Copr is using up to 29 x86 VMs and 10 ppc VMs from Fedora Cloud for builders.
>> We are hitting the limits quite often. So I would like to ask if I can 
>> assign another 10 x86 VMs to Copr?
>> I can do it myself, I am just asking in advance if anyone is against it.
>> I checked the hypervisors and there is still plenty of space.
>>   VCPU Usage: Used 400 of 512
>>   Memory Usage: Used 869.0GB of 1.6TB
>> One Copr builder has 2VCPU and 5GB RAM.
> 
> Seems fine to me to increase it. Note that we have new hardware waiting

Done. Thank you.

Mirek



signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org