infrastructure November 2017

infrastructure@lists.fedoraproject.org

42 participants
53 discussions

Fedora 27 Final Freeze now in effect
by Kevin Fenzi 15 Nov '17

15 Nov '17

Greetings. we are now in the infrastructure freeze leading up to the Fedora 27 release. This is a final release freeze. We do this to ensure that our infrastructure is stable and ready to release the Fedora 27 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 2017-10-31 (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

FBR: bodhi-dequeue-stable dies
by Randy Barlow 15 Nov '17

15 Nov '17

I'd like to get a freeze break request to do two things: 1) Apply the patch from #2005[0] to production bodhi-backend01. 2) Manually run bodhi-dequeue-stable on backend01. I guess I should technically ask for review on [0] as well, since we shouldn't really apply unreviewed PRs on production… [0] https://github.com/fedora-infra/bodhi/pull/2005

4 3

RFR: Transtats
by Sundeep Anand 15 Nov '17

15 Nov '17

Hi Everyone, We are working on a project: transtats <http://transtats.org/> and wanted to discuss this here. Transtats tries to harmonize and give clear picture of translations across different places (upstream, translation platform and build system) about strings. Also, it captures release schedule dates/milestones and generates some summary, stats and alerts which could be meaningful to developers, i18n quality engineers, translators and localization coordinators/maintainers. I have tried including description and advantage to fedora here [1]. In flock 2017, we had some discussions around "string breakage detection" and some sort of solution whereby tracking of translations across packages could be done. Thanks to flock 2017 committee for giving me chance to present / introduce [2] transtats. It keeps some list of languages (+their sets), list of packages (+their relationships) and releases (schedule, build sys info); interact with translation platforms (zanata / damned lies) and build system (koji - *under development*) through jobs to generate information. Transtats server is a django/postgres application [3] and has one client [4]. This is to request resources whereby we can setup server and make things ready probably for f28. We have some running instances for demo purposes [5]. FAS auth is working (on localhost:8080) thanks Patrick. May be plain VM with f27 can do, we are planning to try openshift v3 shortly. As of now load balancing or caching are not required, but surely going to be. I am really excited and hoping to have questions / comments / suggestions ! thanks, sundeep fas: suanand [1] https://pagure.io/fedora-infrastructure/issue/6459 [2] https://www.youtube.com/watch?v=Ln9e3LM2Ht8 [3] https://github.com/transtats/transtats [4] https://src.fedoraproject.org/rpms/transtats-cli [5] http://transtats.devlab.redhat.com http://transtats.xyz

1 0

Images in Fedorainfracloud.org are not in playbook
by Miroslav Suchý 14 Nov '17

14 Nov '17

Please, if you are adding new images to fedorainfracloud.org then add those images to playbook too: https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/playbooks/ho… It is not needed for special playbooks (e.g. copr-builders) but it should be done for common images (i.e., Fedora-Cloud-Base-27-1.6.x86_64.qcow2) Miroslav Suchý

1 0

FBR: robosig: sign F27AH ostree refs
by Dusty Mabe 13 Nov '17

13 Nov '17

[PATCH 1/2] robosig: sign F27AH updates refs [PATCH 2/2] robosig: sign F27AH updates-testing refs

3 4

FBR (retroactive): Create fedora websites live fedimg indicator file
by Patrick Uiterwijk 12 Nov '17

12 Nov '17

Hi, For optimization purposes, the website build scripts now need a file to exist before they grab live data from fedmsg for displaying AMIs. I had to apply this change on the sundries nodes to make sure that they do continue to generate a usable website. Can I get +1s for the following patch? Regards, Patrick commit 0a0b58be97ea5e8abe44011f5e233dec74d5e543 Author: Patrick Uiterwijk <puiterwijk(a)redhat.com> Date: Sun Nov 12 20:49:05 2017 +0000 Create live fedimg indicator file on sundries Signed-off-by: Patrick Uiterwijk <puiterwijk(a)redhat.com> diff --git a/roles/fedora-web/build/tasks/main.yml b/roles/fedora-web/build/tasks/main.yml index 890d7cb..2c5e1bd 100644 --- a/roles/fedora-web/build/tasks/main.yml +++ b/roles/fedora-web/build/tasks/main.yml @@ -19,6 +19,12 @@ - packages - fedora-web +- name: Create file to indicate we want live fedimg data + copy: dest=/var/fedora_websites_live_fedimg + content="Indicator file" + tags: + - fedora-web + - name: Create directories file: state=directory path=/srv/web/{{item}}

3 2

November status update for Fedora Infrastructure Apprentices
by Kevin Fenzi 10 Nov '17

10 Nov '17

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

13 12

FBR: Only sync drpms if repo has them
by Patrick Uiterwijk 10 Nov '17

10 Nov '17

Source repos do not have drpms, and neither do new repos (aka, first time a release gets mashed). +1s? diff --git a/roles/bodhi2/backend/files/new-updates-sync b/roles/bodhi2/backend/files/new-updates-sync index a241eeb..7f3baae 100755 --- a/roles/bodhi2/backend/files/new-updates-sync +++ b/roles/bodhi2/backend/files/new-updates-sync @@ -204,11 +204,13 @@ def sync_single_repo_arch(release, repo, arch, dest_path): maindir = 'tree' if arch == 'source' else 'os' results = [] + do_drpms = os.path.exists(os.path.join(source_path, maindir, 'drpms')) results.append(rsync(os.path.join(source_path, maindir, 'Packages'), os.path.join(dest_path))) - results.append(rsync(os.path.join(source_path, maindir, 'drpms'), - os.path.join(dest_path))) + if do_rpms: + results.append(rsync(os.path.join(source_path, maindir, 'drpms'), + os.path.join(dest_path))) if arch != 'source': results.append(rsync(os.path.join(source_path, 'debug', 'tree', 'Packages'), os.path.join(dest_path, 'debug'))) @@ -224,9 +226,10 @@ def sync_single_repo_arch(release, repo, arch, dest_path): results.append(rsync(os.path.join(source_path, maindir, 'Packages'), os.path.join(dest_path), delete=True)) - results.append(rsync(os.path.join(source_path, maindir, 'drpms'), - os.path.join(dest_path)), - delete=True) + if do_rpms: + results.append(rsync(os.path.join(source_path, maindir, 'drpms'), + os.path.join(dest_path), + delete=True)) return collect_stats(results)

3 2

FBR: Enable multi-arch ostree composes for F27+
by Patrick Uiterwijk 10 Nov '17

10 Nov '17

Hi all, We can now do multi-arch ostrees for updates! \o/ Can I get +1s to apply this patch to enable that for Fedora 27 and up? Thanks, Patrick diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 index 1c6dc02..b0f6ab7 100644 --- a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 +++ b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 @@ -107,9 +107,15 @@ createiso_skip = [ ] [% if release.id_prefix == 'FEDORA' and release.version_int >= 26 %] +{% if release.version_int >= 27 %} + {% set ostree_arches = ['x86_64', 'ppc64le', 'aarch64'] %} +{% else %} + {% set ostree_arches = ['x86_64'] %} +{% endif %} ostree = [ ("^Everything$", { - "x86_64": { + {% for arch in ostree_arches %} + "{{ arch }}": { [% if release.version_int >= 28 %] "version": "!OSTREE_VERSION_FROM_LABEL_DATE_TYPE_RESPIN", [% endif %] @@ -120,17 +126,18 @@ ostree = [ "Everything", [% if request.name == 'testing' %] # In the case of testing, also inject the last stable updates - "https://kojipkgs{{ env_suffix }}.fedoraproject.org/pub/fedora/linux/updates/[[ release.version ]]/x86_64/" + "https://kojipkgs{{ env_suffix }}.fedoraproject.org/pub/fedora/linux/updates/[[ release.version ]]/{{ arch }}/" [% endif %] [% if release.version_int == 27 %] - "https://kojipkgs{{ env_suffix }}.fedoraproject.org/pub/fedora/linux/development/[[ release.version_int ]]/Everything/x86_64/os/" + "https://kojipkgs{{ env_suffix }}.fedoraproject.org/pub/fedora/linux/development/[[ release.version_int ]]/Everything/{{ arch }}/os/" [% else %] - "https://kojipkgs{{ env_suffix }}.fedoraproject.org/pub/fedora/linux/releases/[[ release.version_int ]]/Everything/x86_64/os/" + "https://kojipkgs{{ env_suffix }}.fedoraproject.org/pub/fedora/linux/releases/[[ release.version_int ]]/Everything/{{ arch }}/os/" [% endif %] ] "ostree_repo": "/mnt/koji/compose/updates/atomic", "tag_ref": False - } + }, + {% endfor %} }) ] [% endif %]

5 7

FBR add syncing for f27-updates
by Dusty Mabe 10 Nov '17

10 Nov '17

add syncing for f27-updates

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure November 2017