Re: FBR: Enable delta RPMs in Pungi+Bodhi

2017-11-01 Thread Dusty Mabe 


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?

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

Fedora Infrastructure Meeting 2017-11-02 1800 UTC

2017-11-01 Thread Stephen John Smoogen 
The infrastructure team will be having it's weekly meeting tomorrow,
2017-11-02 at 18:00 UTC in #fedora-meeting on the freenode network.

We have a gobby document
(see: https://fedoraproject.org/wiki/Gobby )

fedora-infrastructure-meeting-next is the document.

==
This shared document is for the next fedora infrastructure meeting.
= Introduction =
We will use it over the week before the meeting to gather status and info and
discussion items and so forth, then use it in the irc meeting to transfer
information to the meetbot logs.

= Meeting start stuff =

#startmeeting Infrastructure (2017-11-02)
#meetingname infrastructure
#topic aloha
#chair smooge relrod nirik dgilmore threebean pingou puiterwijk
pbrobinson maxamillion

= Let new people say hello =

#topic New folks introductions
#info This is a place where people who are interested in Fedora
Infrastructure can introduce themselves

= Status / Information / Trivia / Announcements =

(We put things here we want others on the team to know, but don't need
to discuss)
(Please use #info  - your name)

#topic announcements and information
#info PHX2 Colo Trip, Dec 4th - 9th
#info Infrastructure will be down during that trip.
#info Final freeze has started. PLEASE TEST ANY RCs.
#info EU daylight savings Oct 29/ US daylight savings Nov 5
#info new notifs in staging, please test!
#info


= Things we should discuss =

We use this section to bring up discussion topics. Things we want to talk about
as a group and come up with some consensus /suor decision or just brainstorm a
problem or issue. If there are none of these we skip this section.
(Use #topic your discussion topic - your username)

#topic Ticket cleanup
#info none this week.

#topic Apprentice work day - reschedule - kevin

#topic

= Apprentice office hours =

#topic Apprentice Open office hours

Here we will discuss any apprentice questions, try and match up people looking
for things to do with things to do, progress, testing anything like that.

= Learn about some application or setup in infrastructure =

(This section, each week we get 1 person to talk about an application or setup
that we have. Just going over what it is, how to contribute, ideas for
improvement,
etc. Whoever would like to do this, just add the i/nfo in this section. In the
event we don't find someone to teach about something, we skip this section
and just move on to open floor.)

#topic Learn about:
#info none this week

= Meeting end stuff =

#topic Open Floor

#endmeeting


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

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

2017-11-01 Thread Jeremy Cline 
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.


[0] https://github.com/fedora-infra/fmn/pull/206
[1] https://pagure.io/fedora-infrastructure/issue/6462
[2] https://github.com/fedora-infra/fmn/pull/248

-- 
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: November status update for Fedora Infrastructure Apprentices

2017-11-01 Thread Patrick Kuny 
>0. Whats your fedora account system login?
netcronin

>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?
Not lately. I've been busy/traveling for work and haven't had time. I do plan 
to. 

>2. Has it helped you decide any area you wish to focus on or contribute
>to more?
N/A. Already committed to sysadmin work.

>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&tags=easyfix
I believe the current easyfix list is beyond my skillset currently.

>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?
Yep, absolutely. 

>5. Is there any help or communication or ideas you have that would help
>you do any of the above?
Not really. Just trying to find tickets to work on. I get that it's a 
complicated architecture, so I'm not complaining, just keeping my eye out.

>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 tickets that are easyfix-ish and/or easy to work on without knowing a 
lot about how all the pieces interact within the architecture. The other main 
admins are very helpful and usually conversational about pieces, so it's okay. 
I just need to put in more time to find the right things for me to work on.

>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 I have. I've missed one or two. I have no suggestions and I think they're 
helpful.

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

>9. What kind of computer are you replying to this email on right now?
>Desktop? Phone? Be as specific or not as you like. :)
work laptop.
___
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

2017-11-01 Thread Athos Ribeiro 
On Wed, Nov 01, 2017 at 11:29:06AM -0700, Kevin Fenzi wrote:
> 0. Whats your fedora account system login?

athoscr

> 
> 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://pagure.io/fedora-infrastructure/issues?status=Open&tags=easyfix

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

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

not atm

> 
> 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 the time to commit to some interesting task

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

not recently

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

not recently

> 
> 9. What kind of computer are you replying to this email on right now?
> Desktop? Phone? Be as specific or not as you like. :)

my personal laptop

> 

-- 
Athos Ribeiro

http://www.ime.usp.br/~athoscr
___
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

2017-11-01 Thread Jlozada2426 
0. Whats your fedora account system login?
jlozadad

> - 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, Still trying to learn the layout and workflow how things work.
>
> - Has it helped you decide any area you wish to focus on or contribute
> to more? Yes. Still thinking on ask.fedora
> - 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&tags=easyfix
>
>   Still looking at tickets. Most of what I been able to do its to 
> comment, ask suggestions etc
>
> - 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 love this group!
>
> - Is there any help or communication or ideas you have that would help
> you do any of the above?
>
>  N/A
>
> - 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 tickets to work on. Some have barely any context.
>
> - 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?
>
>I have attended the meetings. They are helpful.
>
> - Have you logged into our Gobby instance and read/seen/added to our
> meeting agenda? https://fedoraproject.org/wiki/Gobby
>
>  Yes.
>
> - What kind of computer are you replying to this email on right now?
> Desktop? Phone? Be as specific or not as you like. :)
>
> 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

>  Original Message 
> Subject: November status update for Fedora Infrastructure Apprentices
> Local Time: November 1, 2017 2:29 PM
> UTC Time: November 1, 2017 6:29 PM
> From: ke...@scrye.com
> To: Fedora Infrastructure , 
> fi-apprentice-memb...@fedoraproject.org
>
> 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?
>
> - Have you logged in and used your fi-apprentice membership to look at
> our machines/setup in the last month? Do you plan to?
> - Has it helped you decide any area you wish to focus on or contribute
> to more?
> - 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&tags=easyfix
> - 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?
> - Is there any help or communication or ideas you have that would help
> you do any of the above?
> - 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?
> - 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?
> - Have you logged into our Gobby instance and read/seen/added to our
> meeting agenda? https://fedoraproject.org/wiki/Gobby
> - What kind of computer are you replying to this email on right now?
> Desktop? Phone? Be as specific or not as you like. :)
>
> 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

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

2017-11-01 Thread Kevin Fenzi 
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



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

November status update for Fedora Infrastructure Apprentices

2017-11-01 Thread Kevin Fenzi 
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://pagure.io/fedora-infrastructure/issues?status=Open&tags=easyfix

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? Do you have any suggestions for changing them?

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

9. What kind of computer are you replying to this email on right now?
Desktop? Phone? Be as specific or not as you like. :)

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













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 purge-ami's cron

2017-11-01 Thread Stephen John Smoogen 
+1 on this

On 31 October 2017 at 19:10, Kevin Fenzi  wrote:
> Greetings.
>
> I happened to notice some cron output a while back and looked into it and 
> found a slight mistake in the purge-ami's cron.
>
> 'git clone -n' was being used which tells it to not bother checking out HEAD 
> after the clone. Just leave the checkout empty. Then it tries to run things 
> from the checkout that just fails. :)
>
> The solution is just to drop the -n I think, but I'd love to have sayan 
> confirm.
>
> kevin
> --
> diff --git a/roles/releng/files/purge-amis b/roles/releng/files/purge-amis
> index b49942a..be677e5 100644
> --- a/roles/releng/files/purge-amis
> +++ b/roles/releng/files/purge-amis
> @@ -1,5 +1,5 @@
>  # Remove launch permissions from the AMIs after every 5 days
> -0 0 */5 * * root TMPDIR=`mktemp -d /tmp/purgeamis.XX` && pushd $TMPDIR 
> && git clone -n https://pagure.io/releng.git && cd releng/scripts && 
> AWS_ACCESS_KEY={{ ec2_image_delete_access_key_id }} AWS_SECRET_ACCESS_KEY={{ 
> ec2_image_delete_access_key }} ./clean-amis.py --change-perms && popd && rm 
> -rf $TMPDIR
> +0 0 */5 * * root TMPDIR=`mktemp -d /tmp/purgeamis.XX` && pushd $TMPDIR 
> && git clone https://pagure.io/releng.git && cd releng/scripts && 
> AWS_ACCESS_KEY={{ ec2_image_delete_access_key_id }} AWS_SECRET_ACCESS_KEY={{ 
> ec2_image_delete_access_key }} ./clean-amis.py --change-perms && popd && rm 
> -rf $TMPDIR
>
>  # Delete the AMIs after every 10 days.
> -0 0 */10 * * root TMPDIR=`mktemp -d /tmp/purgeamis.XX` && pushd $TMPDIR 
> && git clone -n https://pagure.io/releng.git && cd releng/scripts && 
> AWS_ACCESS_KEY={{ ec2_image_delete_access_key_id }} AWS_SECRET_ACCESS_KEY={{ 
> ec2_image_delete_access_key }} ./clean-amis.py --delete && popd && rm -rf 
> $TMPDIR
> +0 0 */10 * * root TMPDIR=`mktemp -d /tmp/purgeamis.XX` && pushd $TMPDIR 
> && git clone https://pagure.io/releng.git && cd releng/scripts && 
> AWS_ACCESS_KEY={{ ec2_image_delete_access_key_id }} AWS_SECRET_ACCESS_KEY={{ 
> ec2_image_delete_access_key }} ./clean-amis.py --delete && popd && rm -rf 
> $TMPDIR
>
>
> ___
> 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: FBR: Enable delta RPMs in Pungi+Bodhi

2017-11-01 Thread Stephen John Smoogen 
+1

On 1 November 2017 at 12:26, Kevin Fenzi  wrote:
> On 11/01/2017 08:53 AM, Patrick Uiterwijk wrote:
>> Seems that this is disabled by default.
>> Any +1s?
>
> +1
>
> kevin
>
>
> ___
> 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: update rpm on builders

2017-11-01 Thread Patrick マルタインアンドレアス Uiterwijk 
> Greetings.
> 
> In order to allow the new rich deps that rust packaging requires we need
> to update rpm on the builders to a version that has backported support
> for 3 new rich deps. It needs these at srpm generation time to
> understand the new rich deps.
> 
> ignatenkobrain has created a rpm with this backported patches and has
> promised to update it as needed. When we update builders to f27 after
> the release we will no longer need it, so it's only for a few weeks.
> 
> We updated staging builders and tested and all looks good there.

I guess +1.

> 
> So, I would like to:
> 
> koji move-build f26-infra-stg f26-infra rpm-4.13.0.2-1.fc26.infrastructure
> 
> then
> 
> update rpm on all the prod builders.
> 
> In the event this causes a problem we can downgrade them back and/or get
> a fixed version.
> 
> +1s?
> 
> kevin
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: F26 delta RPMs

2017-11-01 Thread Kevin Fenzi 
On 11/01/2017 01:18 AM, Ron Yorston wrote:
> Another big batch of F26 updates without any delta RPMs today:
> libreoffice (again), wine, openjdk.

Yeah, they were not enabled in the new compose setup we just switched to.

As soon as we apply the freeze break on this list, they should appear
again. Hopefully tomorrow.

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: FBR: Enable delta RPMs in Pungi+Bodhi

2017-11-01 Thread Kevin Fenzi 
On 11/01/2017 08:53 AM, Patrick Uiterwijk wrote:
> Seems that this is disabled by default.
> Any +1s?

+1

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

FBR: Enable delta RPMs in Pungi+Bodhi

2017-11-01 Thread Patrick Uiterwijk 
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']
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: Higher quota for Copr

2017-11-01 Thread Kevin Fenzi 
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
that will replace fed-cloud01-09, so we may have somewhat increased
capacity (and will definitely have newer openstack) before too long anyhow.

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: FBR: bump compose-x86-01 to 16 GB

2017-11-01 Thread Kevin Fenzi 
+1 make it so.

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: FBR: bump compose-x86-01 to 16 GB

2017-11-01 Thread Patrick Uiterwijk 
On Wed, Nov 1, 2017 at 4:29 PM, Stephen John Smoogen  wrote:
> The system is currently at 8 GB and the compose is failing due to OOM.
> I am going to bump this to 16GB. If this not enough, we need to
> re-engineer what this box is doing and deploy many of its tasks to
> other systems

Reluctant +1.
The tasks of this box need to be splitten up across multiple boxes,
but for now we can do this.

>
> Steps:
>
> sudo virsh setmem compose-x86-01.phx2.fedoraproject.org  16777216 --config
>
> diff --git a/inventory/host_vars/compose-x86-01.phx2.fedoraproject.org
> b/inventory/host_vars/compose-x86-01.phx2.fedoraproject.org
> index cef3131..bd2a2de 100644
> --- a/inventory/host_vars/compose-x86-01.phx2.fedoraproject.org
> +++ b/inventory/host_vars/compose-x86-01.phx2.fedoraproject.org
> @@ -12,7 +12,7 @@ ks_repo:
> http://10.5.126.23/pub/fedora/linux/releases/25/Server/x86_64/os/
>  virt_install_command: "{{ virt_install_command_two_nic }}"
>
>  lvm_size: 3
> -mem_size: 8192
> +mem_size: 16384
>  num_cpus: 8
>
>  volgroup: /dev/xenGuests
>
>
> --
> Stephen J Smoogen.
> ___
> 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

FBR: bump compose-x86-01 to 16 GB

2017-11-01 Thread Stephen John Smoogen 
The system is currently at 8 GB and the compose is failing due to OOM.
I am going to bump this to 16GB. If this not enough, we need to
re-engineer what this box is doing and deploy many of its tasks to
other systems

Steps:

sudo virsh setmem compose-x86-01.phx2.fedoraproject.org  16777216 --config

diff --git a/inventory/host_vars/compose-x86-01.phx2.fedoraproject.org
b/inventory/host_vars/compose-x86-01.phx2.fedoraproject.org
index cef3131..bd2a2de 100644
--- a/inventory/host_vars/compose-x86-01.phx2.fedoraproject.org
+++ b/inventory/host_vars/compose-x86-01.phx2.fedoraproject.org
@@ -12,7 +12,7 @@ ks_repo:
http://10.5.126.23/pub/fedora/linux/releases/25/Server/x86_64/os/
 virt_install_command: "{{ virt_install_command_two_nic }}"

 lvm_size: 3
-mem_size: 8192
+mem_size: 16384
 num_cpus: 8

 volgroup: /dev/xenGuests


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

Higher quota for Copr

2017-11-01 Thread Miroslav Suchý 
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.

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

Re: Freeze Break Request: fix purge-ami's cron

2017-11-01 Thread Sayan Chowdhury 
On Wed, Nov 1, 2017 at 4:40 AM, Kevin Fenzi  wrote:
> Greetings.
>
> I happened to notice some cron output a while back and looked into it and 
> found a slight mistake in the purge-ami's cron.
>
> 'git clone -n' was being used which tells it to not bother checking out HEAD 
> after the clone. Just leave the checkout empty. Then it tries to run things 
> from the checkout that just fails. :)
>
> The solution is just to drop the -n I think, but I'd love to have sayan 
> confirm.

+1 on this one.

-- 
Sayan Chowdhury 
Senior Software Engineer, Fedora Engineering - Emerging Platform
GPG Fingerprint : 0F16 E841 E517 225C 7D13  AB3C B023 9931 9CD0 5C8B


Proud to work at The Open Organization!
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: F26 delta RPMs

2017-11-01 Thread Ron Yorston 
Another big batch of F26 updates without any delta RPMs today:
libreoffice (again), wine, openjdk.

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