Plan for tomorrow's Fedora Infrastructure meeting - 2016-06-23
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2016-06-23 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.
Please try and review and edit that document before the meeting and we
will use it to have our agenda of things to discuss. A copy as of today
is included in this email.
If you have something to discuss, add the topic to the discussion area
with your name. If you would like to teach other folks about some
application or setup in our infrastructure, please add that topic and
your name to the learn about section.
kevin
--
= Introduction =
This shared document is for the next fedora infrastructure meeting.
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 (2016-06-23)
#meetingname infrastructure
#topic aloha
#chair smooge relrod nirik abadger1999 lmacken dgilmore threebean pingou puiterwijk pbrobinson
#topic New folks introductions / Apprentice feedback
= 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 <the thing> - your name)
#topic announcements and information
#info Fedora 24 is released! Hurray! - everyone
#info release day went pretty smoothly - everyone
#info ansible upgraded to 2.1.1 rc1 on batcave - kevin
#info pkgdb notifications moved from scm-commits to new scm-notifications list - kevin
#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 or 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 items to get done before f25 alpha? - kevin
= Apprentice 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 info 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:
= Meeting end stuff =
#topic Open Floor
#endmeeting
7 years, 10 months
'Meeting Agenda Item: Nikos Vassilakis'
by nikos vassilakis
Greetings,My IRC handle on HexChat is: nikobasiI am familiar with programming languages C, Java, PHP, SQL, HTML ,JavaScript, C#, CSS and i am familiar withTerminal(bash scripting and unix administration). I want to get experience mostly as linux administrator
but i would not mind contributing to programming projects. I worked in the past as systems administrator onLinux machines. I am also CS graduate. I am fast learner. I want to join to linux community to keep up with
technology and to learn,I hope i was descriptive enough. If you want to ask me anything please don't hesitate.
Kind Regards,
Nikos Vassilakis.
7 years, 10 months
Code browser for SRPMs
by Joseph Mullally
Are there any ongoing plans for being able to browse/link/search Fedora SRPM contents online?
One obvious use case is automatically generating links for FAF stack traces to omnigrok(etc) SRPM:file:lines. Having permalink URLS would also be useful for ongoing bugfix/feature discussions.
E.g. lines in this
https://retrace.fedoraproject.org/faf/problems/1378013/
could link to the cgit,opengrok view of the file:line of its original SRPM (for a selected release)
http://koji.fedoraproject.org/koji/buildinfo?buildID=742571
Also, in general having some reusable functionality to bidirectionally map between these...
RPM binary/script line/debugsymbol <-> SRPM NVR file:line <-> pkgs.fedoraproject.org commit/srcfile-or-patch:line <-> upstream commit/file:line
... would be useful for many use cases considering the low complexity of the problem (E.g. examples above, tagging, upstream auto-mining of FAF, future https://fedoraproject.org/wiki/StaticAnalysis LXR style browser etc.)
Previous efforts/discussions in this area:
This was promising but looks dead: https://fedoraproject.org/wiki/LubomirKundrak/OpenGrok
Previous discussion: https://lists.fedoraproject.org/pipermail/users/2010-November/387149.html
> I think you're out of luck. It would be a huge
> amount of resources for fedora to host the exploded contents of all
> 10k+ packages (let along keeping multiple versions or revision control
> history for those upstream projects)
This is a critical point, but maybe a workaround is to dynamicaly extract the existing SRPMs on request along with some simple caching.
(PS Just curious about this area, I don't think I'd be able to do much more than a hacky PoC:)
Thanks!
- Joe
7 years, 10 months
Fedora 24 Final freeze now in effect!
by Kevin Fenzi
Greetings.
we are now in the infrastructure freeze leading up to the Fedora 24
Final release. This is a Final freeze.
We do this to ensure that our infrastructure is stable and ready to
release the Fedora 24 Final 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
scripts/freezelist -i inventory
Any hosts listed as freezes is frozen until 2016-06-14. (or later if
Final 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
7 years, 10 months
Re: [ansible] Disable crawler and automatic pkl push before the
release
by Adrian Reber
I git two +1's on IRC to quickly push this out. The goal was to better
control what is crawled and when the result is published on the
mirrorlist servers. I will revert this after the release to return to
normal operation.
Adrian
On Tue, Jun 21, 2016 at 11:57:36AM +0000, Adrian Reber wrote:
> This is the public repository, do not commit sensitive
> or confidential information here.
> X-Git-Refname: refs/heads/master
> X-Git-Oldrev: 12d3665003022025baa60c9980f6a48ae6c6bdb9
> X-Git-Newrev: 8e83d2cc8f827e6124ac698aef37ec123e9f3eb5
>
> commit 8e83d2cc8f827e6124ac698aef37ec123e9f3eb5
> Author: Adrian Reber <adrian(a)lisas.de>
> Date: Tue Jun 21 11:53:39 2016 +0000
>
> Disable crawler and automatic pkl push before the release
>
> To better control what is available on the mirrorlist servers the
> cronjob are disabled.
>
> Signed-off-by: Adrian Reber <adrian(a)lisas.de>
>
> roles/mirrormanager/backend/files/backend.cron | 2 +-
> roles/mirrormanager/crawler/files/crawler.cron | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
> ---
> diff --git a/roles/mirrormanager/backend/files/backend.cron b/roles/mirrormanager/backend/files/backend.cron
> index b63d3fb..bcf4cde 100644
> --- a/roles/mirrormanager/backend/files/backend.cron
> +++ b/roles/mirrormanager/backend/files/backend.cron
> @@ -2,7 +2,7 @@ MAILTO=root
>
> # Refresh the mirrorlist cache at the top of the hour and sync it to the
> # mirrorlist servers
> -55 * * * * mirrormanager /usr/bin/mm2_update-mirrorlist-server && /usr/local/bin/sync_pkl_to_mirrorlists.sh
> +#55 * * * * mirrormanager /usr/bin/mm2_update-mirrorlist-server && /usr/local/bin/sync_pkl_to_mirrorlists.sh
>
> # update master directory
> # logs sent to /var/log/mirrormanager/umdl.log by default
> diff --git a/roles/mirrormanager/crawler/files/crawler.cron b/roles/mirrormanager/crawler/files/crawler.cron
> index 2b68c76..1060aa1 100644
> --- a/roles/mirrormanager/crawler/files/crawler.cron
> +++ b/roles/mirrormanager/crawler/files/crawler.cron
> @@ -4,4 +4,4 @@
> # [ "`hostname -s`" == "mm-crawler02" ] && sleep 2h is used to start the crawl
> # later on the second crawler to reduce the number of parallel accesses to
> # the database
> -0 */12 * * * mirrormanager [ "`hostname -s`" == "mm-crawler02" ] && sleep 2h; /usr/bin/mm2_crawler --timeout-minutes 180 --threads 20 `/usr/local/bin/run_crawler.sh 2` > /dev/null 2>&1
> +#0 */12 * * * mirrormanager [ "`hostname -s`" == "mm-crawler02" ] && sleep 2h; /usr/bin/mm2_crawler --timeout-minutes 180 --threads 20 `/usr/local/bin/run_crawler.sh 2` > /dev/null 2>&1
7 years, 10 months
[PATCH] disable branched composes now we are go
by Dennis Gilmore
From: Dennis Gilmore <ausil(a)fedoraproject.org>
Signed-off-by: Dennis Gilmore <ausil(a)fedoraproject.org>
---
roles/releng/files/branched | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/roles/releng/files/branched b/roles/releng/files/branched
index a2d68d3..4430d67 100644
--- a/roles/releng/files/branched
+++ b/roles/releng/files/branched
@@ -1,3 +1,3 @@
# branched compose
MAILTO=releng-cron(a)lists.fedoraproject.org
-15 7 * * * root TMPDIR=`mktemp -d /tmp/branched.XXXXXX` && cd $TMPDIR && git clone https://pagure.io/pungi-fedora.git && cd pungi-fedora && git checkout f24 && LANG=en_US.UTF-8 ./nightly.sh && sudo -u ftpsync /usr/local/bin/update-fullfilelist fedora
+#15 7 * * * root TMPDIR=`mktemp -d /tmp/branched.XXXXXX` && cd $TMPDIR && git clone https://pagure.io/pungi-fedora.git && cd pungi-fedora && git checkout f24 && LANG=en_US.UTF-8 ./nightly.sh && sudo -u ftpsync /usr/local/bin/update-fullfilelist fedora
--
1.8.3.1
7 years, 10 months
[release] MirrorManager2: 0.7.2
by Adrian Reber
Good evening everyone,
with Pierre-Yves' help I made new release of MirrorManager2: 0.7.2
* Wed Jun 15 2016 Adrian Reber <adrian(a)lisas.de> - 0.7.2-1
- Update to 0.7.2
- Fix propagation diagram creation
- Use yesterday's date in get_global_netblocks
- Mark path containing /stage/ as testing
- Added an option with which the user can define the preferred
protocol)
- Adjust repomap for the new repo layout (Pierre-Yves Chibon)
- Typo fix in readme (Taranjeet)
This is currently running in stg for those who want to test it.
No plans to update the production systems before the freeze ends.
Adrian
7 years, 10 months
Plan for tomorrow's Fedora Infrastructure meeting - 2016-06-16
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2016-06-16 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.
Please try and review and edit that document before the meeting and we
will use it to have our agenda of things to discuss. A copy as of today
is included in this email.
If you have something to discuss, add the topic to the discussion area
with your name. If you would like to teach other folks about some
application or setup in our infrastructure, please add that topic and
your name to the learn about section.
kevin
--
= Introduction =
This shared document is for the next fedora infrastructure meeting.
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 (2016-06-16)
#meetingname infrastructure
#topic aloha
#chair smooge relrod nirik abadger1999 lmacken dgilmore threebean pingou puiterwijk pbrobinson
#topic New folks introductions / Apprentice feedback
= 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 <the thing> - your name)
#topic announcements and information
#info Still in F24 final freeze - everyone
#info spam attacks continue - patrick/smooge/kevin
#info (re)setup proxy07 on a cloud node at bodhost, seems working so far - kevin
#info New 10G switches and new bladecenters arriving in phx2 to be setup in coming weeks - kevin/smooge/patrick
#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 or 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 Some upcoming releng changes that may affect infra:
Review F25 change that may impact Infra: Automated Docker Releases
Review F25 change that may impact Infra: Fedora Docker Registry
= Apprentice 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.
#topic Apprentice office hours
= 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 info 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:
= Meeting end stuff =
#topic Open Floor
#endmeeting
7 years, 10 months
Freeze Break Request: allow rdu2 community cage host repo access
by Kevin Fenzi
Greetings.
I'd like to (re)install the new virthost-cc-rdu01 box (a virthost
server thats in the new rdu2 community cage). It needs to be allowed
access to our repos however.
diff --git a/roles/batcave/files/allows b/roles/batcave/files/allows
index 18a2f2f..2e767bd 100644
--- a/roles/batcave/files/allows
+++ b/roles/batcave/files/allows
@@ -97,6 +97,9 @@ require ip 67.219.144.68
require ip 67.219.144.69
require ip 67.219.144.70
+# rdu2 community cage machines
+require ip 8.43.85.65
+
#
# We put this at the end because it fails for hosts with no reverse dns
# and then they don't check the rest of the ip allows.
+1s?
kevin
7 years, 10 months
