March 2019 - infrastructure - Fedora mailing-lists

About JS framework
by Pierre-Yves Chibon 17 Oct '22

17 Oct '22

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. 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? Thanks for your inputs, Pierre

10 12

Fedora 30 Beta freeze now in efect
by Kevin Fenzi 03 Apr '19

03 Apr '19

Greetings. we are now in the infrastructure freeze leading up to the Fedora 30 Beta release. This is a pre release freeze. We do this to ensure that our infrastructure is stable and ready to release the Fedora 30 Beta when it's available. You can see a list of hosts that do not freeze by checking out the ansible repo and running the freezelist script: git clone https://infrastructure.fedoraproject.org/infra/ansible.git ansible/scripts/freezelist -i inventory Any hosts listed as freezes is frozen until 2019-03-26 (or later if release slips). Frozen hosts should have no changes made to them without a sign-off on the change from at least 2 sysadmin-main or rel-eng members, along with (in most cases) a patch of the exact change to be made to this list. Thanks, kevin

1 1

[PATCH] distgit/pagure: Increase the cross-project ACLs
by Pierre-Yves Chibon 02 Apr '19

02 Apr '19

This just makes pagure accept to generate project-less API tokens with these two ACLs. Signed-off-by: Pierre-Yves Chibon <pingou(a)pingoured.fr> --- roles/distgit/pagure/templates/pagure.cfg | 2 -- 1 file changed, 2 deletions(-) diff --git a/roles/distgit/pagure/templates/pagure.cfg b/roles/distgit/pagure/templates/pagure.cfg index a66b3278b..385b80464 100644 --- a/roles/distgit/pagure/templates/pagure.cfg +++ b/roles/distgit/pagure/templates/pagure.cfg @@ -273,10 +273,8 @@ USER_ACLS = [ CROSS_PROJECT_ACLS = [ 'fork_project', 'modify_project', -{% if env == 'staging' %} 'pull_request_create', 'pull_request_comment', -{% endif %} ] ADMIN_API_ACLS = [ -- 2.20.1

4 3

FBR: Unfreeze RelEng to push updates
by Mohan Boddu 01 Apr '19

01 Apr '19

Hello, I dont know if this FBR is needed or not, but now that we have a GOLD compose for F30 Beta and all the requested f30 builds pushed stable and I cloned f30-Beta tag from f30, now we can start pushing updates to F30 stable as well along with the others. +1's please diff --git a/vars/all/RelEngFrozen.yaml b/vars/all/RelEngFrozen.yaml index bd7553f..72af779 100644 --- a/vars/all/RelEngFrozen.yaml +++ b/vars/all/RelEngFrozen.yaml @@ -1 +1 @@ -RelEngFrozen: True +RelEngFrozen: False Thanks.

3 2

Future of fedora-packages
by Clement Verna 01 Apr '19

01 Apr '19

Hi all, fedora-packages [0] code base is showing its age. The code base and the technology stack (Turbogears2 [1] web framework and the Moksha [2] middleware) is currently not ready for Python3 and I am not planning to do the work required to make it Python3 compatible, so the application will stop working when Fedora 29 is EOL. In order to keep the service running, I have started a Proof Of Concept (fedora-search [3]) to replace the backend of the application. Fedora-search would be a REST API service offering full test search API. Such a service would then be available for other application to use, fedora-packages would then become a frontend only application using the service provided by fedora-search. While the POC shows that this is a viable solution, I don't think that we should be proceeding that way, for the simple reason that this add yet another code base to maintain, I think we should use this opportunity to consider using Elasticsearch instead of maintaining our own "search engine". I think that Elasticsearch offers quite a few advantages : - Powerful Query language - Python bindings - Javascript bindings - Can be deployed in our infrastructure or used as a service - Can be useful for other applications ( docs.fp.o, pagure, ??) So what is the general feeling about using Elasticsearch in our infrastructure ? Should we look at deploying a cluster in our infra / Should we approach the Council to see if we can get founding to have this service hosted by Elastic ? Thanks Clément [0] - https://apps.fedoraproject.org/packages/ [1] - http://www.turbogears.org/ [2] - https://mokshaproject.github.io/mokshaproject.net/ [3] - https://github.com/fedora-infra/fedora-search

13 32

[Freeze Break Request] Add zchunk support to updates and updates-testing repositories
by Jonathan Dieter 31 Mar '19

31 Mar '19

This adds zchunk support for the updates and updates-testing repositories for both rpms and modularity. We already have zchunk metadata being generated for the fedora repository. I'd like to get this in before Beta comes out so Beta users will have zchunk-enabled updates-testing repositories when Beta is released. I am making the assumption that a zchunk-enabled createrepo_c (0.12.0-2 or later) is available on the builders (I think I'm safe making that assumption, since zchunk metadata is already being generated for some repos). I have *not* tested this patch, because I'm not sure how I'd go about doing so. If we don't have any test builders, my suggestion would be to wait until no compose is running, and then run this play on a builder, verifying that the generated pungi configuration is valid for both f29 and f30, with no createrepo_extra_args in f29. Signed-off-by: Jonathan Dieter <jdieter(a)gmail.com> --- roles/bodhi2/backend/templates/pungi.module.conf.j2 | 3 +++ roles/bodhi2/backend/templates/pungi.rpm.conf.j2 | 3 +++ 2 files changed, 6 insertions(+) diff --git a/roles/bodhi2/backend/templates/pungi.module.conf.j2 b/roles/bodhi2/backend/templates/pungi.module.conf.j2 index bb021eb13..7dad35403 100644 --- a/roles/bodhi2/backend/templates/pungi.module.conf.j2 +++ b/roles/bodhi2/backend/templates/pungi.module.conf.j2 @@ -59,6 +59,9 @@ greedy_method = 'build' createrepo_c = True createrepo_checksum = 'sha256' createrepo_deltas = False +[% if release.version_int >= 30 %] +createrepo_extra_args = ['--zck', '--zck-dict-dir=/usr/share/fedora-repo-zdicts/f[[ release.version_int ]]'] +[% endif %] #jigdo create_jigdo = False diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 index 8d9e9a3f2..020736aee 100644 --- a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 +++ b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 @@ -66,6 +66,9 @@ createrepo_deltas = [ ('^Everything$', {'*': True}) ] createrepo_database = True +[% if release.version_int >= 30 %] +createrepo_extra_args = ['--zck', '--zck-dict-dir=/usr/share/fedora-repo-zdicts/f[[ release.version_int ]]'] +[% endif %] # CHECKSUMS media_checksums = ['sha256']

4 21

FBR: clean up disk space on mirrors
by Stephen John Smoogen 31 Mar '19

31 Mar '19

1. Remove F29beta from mirrors so mirrors can keep up /pub/fedora/linux/releases/test/29_Beta/ 2. Move F27 to archives a. Have mirrormanager point to /pub/archives/fedora/linux/27 b. Remove /pub/fedora/linux/27 -- Stephen J Smoogen.

4 7

FBR: some test machines
by Kevin Fenzi 31 Mar '19

31 Mar '19

Greetings. I'd like to apply the following to ansible, then run maintainer-test playbook (not frozen) and then noc playbook (frozen). This will add a f30-test instance in old cloud (x86_64) and a pair of aarch64 ones (f29) on two virthosts in the new community openshift area. +1s? kevin --

3 4

[FBR] cache headers for emojione.sprites.png
by Alessandro Lorenzi 30 Mar '19

30 Mar '19

Hi all, I've wrote two patch for issue #7629. pagure frontend: caching emojione sprites for 1 week roles/pagure/frontend/templates/0_pagure.conf | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/roles/pagure/frontend/templates/0_pagure.conf b/roles/pagure/frontend/templates/0_pagure.conf index 50c2d6e9b..87009fce0 100644 --- a/roles/pagure/frontend/templates/0_pagure.conf +++ b/roles/pagure/frontend/templates/0_pagure.conf @@ -78,6 +78,12 @@ WSGIDaemonProcess paguredocs user=git group=git maximum-requests=1000 display-na Alias /static /usr/lib/python2.7/site-packages/pagure/static/ + <Location "/static/vendor/emojione/emojione.sprites.png"> + ExpiresActive On + ExpiresDefault "access plus 1 week" + Header append Cache-Control "public" + </Location> + SetEnv GIT_PROJECT_ROOT /srv/git/repositories <Location /> @@ -145,6 +151,12 @@ WSGIDaemonProcess paguredocs user=git group=git maximum-requests=1000 display-na Alias /static /usr/lib/python2.7/site-packages/pagure/static/ + <Location "/static/vendor/emojione/emojione.sprites.png"> + ExpiresActive On + ExpiresDefault "access plus 1 week" + Header append Cache-Control "public" + </Location> + <Location /> WSGIProcessGroup paguredocs <IfModule mod_authz_core.c> -- 2.20.1 Site src.fp.org: caching emojione sprites for 1 week --- roles/fedora-web/src/files/expires.conf | 5 +++++ roles/fedora-web/src/tasks/main.yml | 12 ++++++++++++ roles/httpd/website/templates/website.conf | 5 ++++- 4 files changed, 22 insertions(+), 2 deletions(-) create mode 100644 roles/fedora-web/src/files/expires.conf diff --git a/roles/fedora-web/src/files/expires.conf b/roles/fedora-web/src/files/expires.conf new file mode 100644 index 000000000..199080880 --- /dev/null +++ b/roles/fedora-web/src/files/expires.conf @@ -0,0 +1,5 @@ +<Location "/static/vendor/emojione/emojione.sprites.png"> + ExpiresActive On + ExpiresDefault "access plus 1 week" + Header append Cache-Control "public" +</Location> diff --git a/roles/fedora-web/src/tasks/main.yml b/roles/fedora-web/src/tasks/main.yml index d7616e84c..fbe8e87d1 100644 --- a/roles/fedora-web/src/tasks/main.yml +++ b/roles/fedora-web/src/tasks/main.yml @@ -19,3 +19,15 @@ tags: - fedora-web - fedora-web/src + +- name: Copy some config files for {{website}} + copy: > + src={{item}} dest=/etc/httpd/conf.d/{{website}}/{{item}} + owner=root group=root mode=0644 + with_items: + - expires.conf + notify: + - reload proxyhttpd + tags: + - fedora-web + - fedora-web/src diff --git a/roles/httpd/website/templates/website.conf b/roles/httpd/website/templates/website.conf index 2a6241a77..931655e6a 100644 --- a/roles/httpd/website/templates/website.conf +++ b/roles/httpd/website/templates/website.conf @@ -20,6 +20,10 @@ Alias /static/hotspot.txt /srv/web/hotspot.txt {% endif %} +{% if site_name == "src.fedoraproject.org" %} + Include "conf.d/src.fedoraproject.org/expires.conf" +{% endif %} + {% if sslonly %} RewriteEngine On RewriteCond %{REQUEST_URI} !/.well-known/acme-challenge/.* @@ -85,4 +89,3 @@ Include "conf.d/{{ site_name }}/*.conf" </VirtualHost> {% endif %} - -- 2.20.1 -- Alessandro Lorenzi

3 2

[FBR] proxies: fix logic for websockets in reversepassproxy
by Tim Flink 29 Mar '19

29 Mar '19

The last patch I did for this added some bits that didn't need to be there and made a bad assumption about the default value for remotepath for the reversepassproxy.conf template. This ended up with unneccesarry complication in the ws balancers and a unintended RewriteCond for any declared reversepassproxy that didn't redefine remotepath. This patch fixes the bad assumptions and removes the cruft that didn't actually do or fix anything --- roles/httpd/reverseproxy/templates/reversepassproxy.conf | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git a/roles/httpd/reverseproxy/templates/reversepassproxy.conf b/roles/httpd/reverseproxy/templates/reversepassproxy.conf index 1e4afe0..1ea0b97 100644 --- a/roles/httpd/reverseproxy/templates/reversepassproxy.conf +++ b/roles/httpd/reverseproxy/templates/reversepassproxy.conf @@ -29,25 +29,17 @@ SSLProxyEngine On <Proxy "balancer://{{balancer_name}}-websocket"> {% for member in balancer_members %} {% if http_not_https_yes_this_is_insecure_and_i_feel_bad %} - {% if remotepath is defined %} - BalancerMember "ws://{{ member }}{{ remotepath }} - {% else %} BalancerMember "ws://{{ member }}" - {% endif %} - {% else %} - {% if remotepath is defined %} - BalancerMember "wss://{{ member }}{{ remotepath }} {% else %} BalancerMember "wss://{{ member }}" {% endif %} - {% endif %} {% endfor %} </Proxy> RewriteEngine on RewriteCond %{HTTP:Upgrade} ^WebSocket$ [NC] RewriteCond %{HTTP:Connection} Upgrade [NC] -{% if remotepath is defined %} +{% if remotepath != "/" %} RewriteCond %{REQUEST_URI} ^{{ remotepath }}/(.)* {% endif %} RewriteRule .* "balancer://{{ balancer_name }}-websocket%{REQUEST_URI}" [P] -- 1.8.3.1

2 3

FBR: Make rabbitmq.fp.o go to proxy101/110 internally
by Patrick Uiterwijk 29 Mar '19

29 Mar '19

Can I get +1s for the patch to the "dns" repo underneath? This should make "rabbitmq.fp.o" resolve to proxy101/proxy110 internally. Patrick diff --git a/fedoraproject.org.template b/fedoraproject.org.template index b0e659c..eac02a0 100644 --- a/fedoraproject.org.template +++ b/fedoraproject.org.template @@ -507,9 +507,15 @@ teams IN TXT "v=spf1 a ip4:35.172.234.62 ?all" teams-api IN A 35.172.234.62 teams-media-protected IN A 35.172.234.62 teams-static IN A 35.172.234.62 +{% if region == "PHX2" %} +; Point to proxy101/proxy110 +rabbitmq IN A 10.5.126.8 +rabbitmq IN A 10.5.126.9 +{% else %} ; for now just point rabbitmq at proxy01/10 until/unless rabbitmq hosts get vpn. rabbitmq IN A 209.132.181.15 rabbitmq IN A 209.132.181.16 +{% endif %} rabbitmq.stg IN CNAME admin.stg.fedoraproject.org. rdu IN A 66.187.233.101 redhat.download IN A 209.132.181.23

4 3

FBR: add proxy101/proxy110 to static syncHttpLogs.sh
by Patrick Uiterwijk 29 Mar '19

29 Mar '19

Hi, So it would seem that even though there's a syncHttpLogs.sh.j2 template, that is not actually used... The one that's used is a static syncHttpLogs.sh file. Could I get +1s to add proxy101/proxy110 to that file (see patch underneath) until it gets replaced with the template? Thanks, Patrick diff --git a/roles/base/files/syncHttpLogs.sh b/roles/base/files/syncHttpLogs.sh index 88aecbf44..c64f805c4 100644 --- a/roles/base/files/syncHttpLogs.sh +++ b/roles/base/files/syncHttpLogs.sh @@ -42,6 +42,8 @@ syncHttpLogs proxy11.vpn.fedoraproject.org syncHttpLogs proxy12.vpn.fedoraproject.org syncHttpLogs proxy13.vpn.fedoraproject.org syncHttpLogs proxy14.vpn.fedoraproject.org +syncHttpLogs proxy101.phx2.fedoraproject.org +syncHttpLogs proxy110.phx2.fedoraproject.org syncHttpLogs proxy01.stg.phx2.fedoraproject.org syncHttpLogs fas01.phx2.fedoraproject.org syncHttpLogs fas02.phx2.fedoraproject.org

3 2

FBR: To add coreos-continuous permission to koji hub policy
by Mohan Boddu 28 Mar '19

28 Mar '19

Core OS folks wanted to have a separate koji tag to build and tag their Core OS continuous builds. This has been discussed in the releng ticket - https://pagure.io/releng/issue/8165. Also, we tested it staging koji and has been working fine. Here's the staging koji ansible commit: https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=c07ff32 Once, this patch is deployed, I will make the necessary koji tags and permissions as we did in staging koji (which are listed in the releng issue linked above). diff --git a/roles/koji_hub/templates/hub.conf.j2 b/roles/koji_hub/templates/hub.conf.j2 index 71792c7..5142491 100644 --- a/roles/koji_hub/templates/hub.conf.j2 +++ b/roles/koji_hub/templates/hub.conf.j2 @@ -96,6 +96,8 @@ tag = # These two rules makes sure people can't build srpms in infra tags and tag them into distribution tags tag *infra* && fromtag *infra* && has_perm infra :: allow fromtag *infra* :: deny + # CoreOS continuous builds, https://pagure.io/releng/issue/8165 + tag f{{FedoraRawhideNumber}}-coreos-continuous f{{FedoraBranchedNumber}}-coreos-continuous f{{Fedora CycleNumber}}-coreos-continuous f{{FedoraPreviousCycleNumber}}-coreos-continuous && has_perm coreos-conti nuous && match action add unblock block :: allow all :: allow channel = If you have any questions, please let me know. Thanks.

2 1

FBR: Enable central http logging for internal proxies
by Patrick Uiterwijk 28 Mar '19

28 Mar '19

Hi, Can I get +1s for applying the underneath patch and running the logserver.yml playbook? This will make sure we also capture the proxy101/proxy110 http logs on log01. Patrick diff --git a/roles/base/templates/syncHttpLogs.sh.j2 b/roles/base/templates/syncHttpLogs.sh.j2 index d83f63d65..8cca68d5d 100644 --- a/roles/base/templates/syncHttpLogs.sh.j2 +++ b/roles/base/templates/syncHttpLogs.sh.j2 @@ -33,6 +33,11 @@ function syncHttpLogs { syncHttpLogs {{host}} {% endfor %} +## Sync up all internal proxies +{% for host in groups['proxies-internal'] %} +syncHttpLogs {{host}} +{% endfor %} + ## Sync up all staging proxies {% for host in groups['proxies-stg'] %} syncHttpLogs {{host}}

3 2

Need someone to run Thursday meeting
by Stephen John Smoogen 28 Mar '19

28 Mar '19

I will be gone Wed->Sun this week and will need someone to run the Thursday Infrastructure meeting. The basics of the meeting are in the gobby-0.5 on infinote.fedoraproject.org On Wednesday, call for items to be added to the document on IRC in #fedora-admin, #fedora-apps, #fedora-noc, #fedora-releng . Send out an email around 20:00 UTC. On Thursday, go to IRC an hour before meeting and remind people on #fedora-admin, #fedora-apps, #fedora-noc, #fedora-releng . Start the meeting and follow the form. After each section either mark sub-items to be used next meeting or remove it. Thanks -- Stephen J Smoogen.

3 2

FBR: Apply MBS PR#1185 to fix Module Stream Expansion with new platform streams
by Jan Kaluža 28 Mar '19

28 Mar '19

Hi, Mohan filled MBS issue https://pagure.io/fm-orchestrator/issue/1184 and asked us to fix and deploy that during the freeze to unblock him. I therefore want to ask for +1 to deploy this small patch (already merged upstream): https://pagure.io/fm-orchestrator/pull-request/1185#request_diff . I think the issue is well described in the PR, unit-test and MBS issue tracker, so I won't repeat myself here. I hope that's OK. Regards, Jan Kaluza

5 5

Retirement of sse2fedmsg
by Michal Konecny 28 Mar '19

28 Mar '19

Hi everybody, month ago I sent an e-mail asking about the future of this project and nobody responded. So our team decided to retire this project. Project will be officially retired on 28th April 2019. Here is the link to previous e-mail in archive list: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapr… Regards, mkonecny

1 0

FBR clean up repospanner on batcave01/pagure01
by Kevin Fenzi 28 Mar '19

28 Mar '19

Greetings. Back a long time ago we setup a repospanner cluster for our ansible repo. We used repospanner01, batcave01 and pagure01 in this cluster. However, there were some things that needed fixing up before we could use it, so we never used it. Fast forward to todaay and we have setup a new cluster for src, but will also just reuse it for ansible repo as well. That cluster has repospanner01 (reinstalled), repospanner-osuosl01, and repospanner-cc-rdu01 in it. That is all great, however, we still have repospanner installed and trying to cluster on batcave01 and pagure01. it's sending many messages per second about it's missing repospanner01 cluster member being gone. So, I would like to apply the following to ansible, stop and remove the repospanner package from batcave01/pagure01. It shouldn't cause any issues I wouldn't think. +1s? kevin -- > diff --git a/playbooks/groups/batcave.yml b/playbooks/groups/batcave.yml > index e0f7213..fe0f450 100644 > --- a/playbooks/groups/batcave.yml > +++ b/playbooks/groups/batcave.yml > @@ -31,7 +31,6 @@ > SSLCertificateChainFile: "{{wildcard_int_file}}" > - openvpn/client > - batcave > - - { role: repospanner/server, when: inventory_hostname.startswith('batcave01'), node: batcave01, region: ansible, spawn_repospanner_node: false, join_repospanner_node: repospanner01.ansible.fedoraproject.org } > - { role: nfs/client, when: inventory_hostname.startswith('batcave'), mnt_dir: '/srv/web/pub', nfs_src_dir: 'fedora_ftp/fedora.redhat.com/pub' } > - { role: nfs/client, when: inventory_hostname.startswith('batcave01'), mnt_dir: '/mnt/fedora/app', nfs_src_dir: 'fedora_app/app' } > > diff --git a/playbooks/groups/pagure.yml b/playbooks/groups/pagure.yml > index a6dd601..d9f8c29 100644 > --- a/playbooks/groups/pagure.yml > +++ b/playbooks/groups/pagure.yml > @@ -56,7 +56,6 @@ > roles: > - pagure/frontend > - pagure/fedmsg > - - { role: repospanner/server, when: inventory_hostname.startswith('pagure01'), node: pagure01, region: ansible, spawn_repospanner_node: false, join_repospanner_node: repospanner01.ansible.fedoraproject.org } > > handlers: > - import_tasks: "{{ handlers_path }}/restart_services.yml"

3 2

FBR: Push a fix to clean_amis.py in fedimg box
by Sayan Chowdhury 27 Mar '19

27 Mar '19

I need to push a fix to run the clean_amis script. The diff is as follows: diff --git a/roles/fedimg/files/clean-amis.py b/roles/fedimg/files/clean-amis.py index d0a491824..8e8cfff91 100644 --- a/roles/fedimg/files/clean-amis.py +++ b/roles/fedimg/files/clean-amis.py @@ -116,7 +116,7 @@ def get_page(page, delta, topic, start=None, end=None): return resp.json() -def _get_two_week_atomic_released_compose_id(delta, start=None, end=None): +def _get_two_week_released_atomic_compose_id(delta, start=None, end=None): """ Returns the release compose ids for last n days """ topic = "org.fedoraproject.prod.releng.atomic.twoweek.complete" @@ -136,7 +136,7 @@ def _get_two_week_atomic_released_compose_id(delta, start=None, end=None): for msg in messages: # This is to support the older-format fedmsg messages if "atomic_raw" in msg: - released_atomic_compose_ids.append(["atomic_raw"]["compose_id"]) + released_atomic_compose_ids.append(msg["atomic_raw"]["compose_id"]) # We are just trying here multiple archs to get the compose id elif "aarch64" in msg: released_atomic_compose_ids.append( @@ -186,7 +186,7 @@ def _get_nightly_amis_nd(delta, start=None, end=None): # Sometimes the compose label is None # and they can be blindly put in for deletion - if compose_label is None: + if not compose_label: amis.append((compose_id, ami_id, region)) if compose_id in released_atomic_compose_ids: @@ -209,7 +209,7 @@ def _get_nightly_amis_nd(delta, start=None, end=None): def delete_amis_nd(deletetimestamp, dry_run=False): """ Delete the give list of nightly AMIs - :args deletetimestamp: the timestamp for the delete + :args deletetimestamp: the timestamp for the delete :args dry_run: dry run the flow """ log.info("Deleting AMIs") The PR to this diff is merged into releng repo[1]. +1s [1] https://pagure.io/releng/pull-request/8193#request_diff -- Sayan Chowdhury <https://words.yudocaa.in/> GPG Fingerprint : 0F16 E841 E517 225C 7D13 AB3C B023 9931 9CD0 5C8B

4 3

[Fedocal] Reminder meeting : Fedora Infrastructure
by smooge＠gmail.com 27 Mar '19

27 Mar '19

Dear all, You are kindly invited to the meeting: Fedora Infrastructure on 2019-03-28 from 15:00:00 to 16:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Weekly Fedora Infrastructure meeting. See infrastructure list for agenda a day before or view it at https://infinote.fedoraproject.org/cgit/infinote/tree/fedora-infrastructure… Source: https://apps.fedoraproject.org/calendar/meeting/22/

1 0

Looking for a GSoC mentor for a bodhi project
by Tomas Tomecek 27 Mar '19

27 Mar '19

Hello, I am reaching out to this ML because I know that possible candidates for the mentorship are here. Pardon my ignorance if there is a better place to ask. Feel free to cross-post. During DevConf.cz we had a container SIG meetup and we've come up with a bunch of tasks [1] which would have been nice to do. One of them was to improve the experience for container image updates in bodhi. We concluded this could be a nice GSoC project, so I submitted it [2]. Sadly, I did not find a mentor for it back then (and there was also a concern the work may not be needed in the end) so I withdrew. I am already mentoring a different project and my knowledge of bodhi's codebase is close to 0, this is why I'm calling out to you. Yesterday, Shreyas contacted me (in CC) and said he would love to work on this project. So this a call to all of you guys: would anyone be interested in mentoring Shreyas? Here is a link [3] to what it takes to be a GSoC mentor. I'm also CCing Sumantro who leads the Fedora GSoC effort. [1] https://public.etherpad-mozilla.org/p/fedoracontainerSIG [2] https://pagure.io/mentored-projects/issue/48 [3] https://google.github.io/gsocguides/mentor/ Thank you, Tomas

1 0

Older Fedora AMIs to be deleted
by Sayan Chowdhury 27 Mar '19

27 Mar '19

Hi, There has been a huge backlog of the nightly Fedora AMIs. So, today I will be deleting kicking off the process to purge the older AMIs. The process that I would be following to delete the AMIs is: - The launch permission of the AMIs will be removed. - I'll wait for 20 days. This is the time period when you can check if any of the Fedora AMIs which is meant to be deleted affects you. If yes, connect back to us via the mailing list or IRC and I'll have a look at it. - After 20 days, I will delete all the AMIs whose launch permission was removed previously. I hope to publish a list of AMIs that were purge after the completion of the process. For any questions find me on #fedora-cloud -- Sayan Chowdhury <https://words.yudocaa.in/> GPG Fingerprint : 0F16 E841 E517 225C 7D13 AB3C B023 9931 9CD0 5C8B

1 1

Freeze Break Request: reinstall buildvm-ppc64le-01/02 to power9 hw
by Kevin Fenzi 27 Mar '19

27 Mar '19

I'd like to reinstall buildvm-ppc64le-01 and 02 on power9 hardware. This should allow us to stop the crazy things we have had to do on the current ones (running on power8) which includes: * downgrading qemu * downgrading libfdt * downgrading the kernel and booting it and removing all other kernels * disabling security updates because we don't want to mess up the above. It should take only a few minutes and I will save the old vm's so we can back out to them if we have to. (Although I need to re-downgrade qemu on them because it was upgraded the other day when I upgraded libseccomp). kevin

4 3

Re: FBR: update prod tag name in WaiverDB
by Pierre-Yves Chibon 27 Mar '19

27 Mar '19

On Mon, Mar 25, 2019 at 06:34:27PM +0800, Yuxiang Zhu wrote: > Hi, we are going to follow the same practice as Greenwave, where tag > `prod` will be used for Red Hat internal deployments and `prod-fedora` for > Fedora deployments. > The image pointed by `prod` tag will be updated by automated process while > `prod-fedora` will be still changed manually. It should be harmless. I guess you need this now because you want to deploy something internally and not in Fedora yet. In this case +1 for me. Pierre

4 4

[FBR] Adjust #fedora-diversity fedmsg IRC bot topics
by Justin W. Flory 25 Mar '19

25 Mar '19

Hi, the attached patch makes a small change to ircbot.py to change the #fedora-diversity IRC bot to only listen for new Pagure tickets, pull requests, and comments. This helps reduce the noise in the IRC channel and hopefully makes the bot more useful for the team. Let me know if anyone has feedback on this patch. -- Cheers, Justin W. Flory jflory7(a)gmail.com

4 6

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure March 2019