Technical Debt Fighters, Assemble!
by Ralph Bean
At Flock, we talked about scheduling some kind of regular
technical-debt-fighting week to happen every so often - some period of
time where we don't do any new features (and even try to de-prioritize
interrupt-driven stuff) and focus on shoring up, cleaning up,
tightening the bolts, etc[1].
Here are some things broadly to think about:
- Add unit tests where there are none. Increase "code coverage".
- Write docs (and make diagrams!) where there are none.
- Reduce code duplication, and increase code re-use where appropriate.
- Break up ultra long methods, classes, and files into more
understandable chunks.
- Remove half-implemented features!
- Remove dead code!!
- Add comments where there are none, and correct inaccurate comments.
- Deal with the existential questions facing the code that none of us
wants to touch.
- Increase happiness and general zest for life.
Time-wise, how about we try and schedule a week to try this on the
first week back from the holiday break -- a New Year, a New
Infrastructure(!) That would be January 4-8th[2].
Here's a question I have. It seems like we could approach this in two
different ways:
- We could select one or two projects we want to prioritize, and try
to do *all* of the best-practices things to them.
- We could select one or two of the best-practices things, and try to
do them to *all* of our projects.
Or.. something inbetween. If you have a preferences here, chime in on
the list, or we can take this up in our IRC meeting at the beginning
of December, too.
As an aside, it would be especially fun if we could keep track of our
collective damage on some kind of scoreboard (it doesn't have to be
automatic, even manual pen-and-paper would work) so we can produce a
nice summary blogpost at the end and thus herald in 2016, a year of
working code, less fires, and quiet mornings where we sip our coffee
and read email.
-Ralph
[1] - http://threebean.org/presentations/debt-services-flock15/
[2] - https://apps.fedoraproject.org/calendar/meeting/3183/
7 years, 8 months
Migration to HyperKitty / Mailman 3
by Aurelien Bompard
Hi people!
Since it's Friday evening, I just unilateraly decided to migrate all
the lists to Mailman3 without telling you anything in advance... Nah
just kidding :-)
However, I think the best time to migrate the rest of the lists would
be the week before Thanksgiving. That would give me some time with you
all around to fix the most urgent problems, and time for me during a
week with less activity in the US to fix the lower priority ones.
Some lists are still using the two features that are not yet ported,
namely the filters and the topics. Those lists would stay on the
current server for now, but migrating the rest would still be an
improvement. This would mean migration would start on November 16th.
What do you think?
I'm also trying to write an announcement for the lists (like
devel-announce), but I'm looking for a native english speaker to help
me with that. It would be something like :
----------------
Dear list users,
The Fedora Engineering team has been working on a new system for our
mailing lists. Mailman 3 came out earlier this year and it has a new
shiny web UI: HyperKitty.
The Fedora project lists will be migrated starting November 16th. You
on't have to use the new UI to keep participating in the
mailing-lists, but the change to Mailman 3 may cause issues with the
way you filter your email. Here are a few things you should expect
after this change, especially if you're using procmail for filtering:
http://fedoraproject.org/wiki/Mailman3_Migration. But it should mostly
work as before.
A link to HyperKitty will be included in the email footers when your
list is migrated.
Some lists which use Mailman 2.1's advanced filtering capabilities (by
header or by topic) will remain on the current version until these
features are ported to Mailman 3.
If you have any questions, feel free to ask on the infrastructure
list: infrastructure(a)lists.fedoraproject.org.
------------------
Am I missing important information? Feel free to reword things if they
are not clear or if it's just bad style.
Thanks !
Aurélien
7 years, 10 months
[release] pagure: 0.1.34 and 0.1.35
by Pierre-Yves Chibon
Good Morning everyone,
I just cut a couple of pagure releases: 0.1.34 and 0.1.35.
The biggest change is the split of the web-hook logic into its own async server
(and thus service) allowing web-hook calls to time-out without blocking the web
UI.
The rest of the changes are either bug-fixes or small RFEs.
Here are the changelogs:
* Mon Nov 30 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.1.35-1
- Update to 0.1.35
- Fix the web-hook server by preventing it to raise any exception (rather log
the errors)
* Mon Nov 30 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.1.34-1
- Update to 0.1.34
- Fix the encoding of the files we're displaying on the UI
- Fix commenting on the last line of a diff
- Fix returning error message from the internal API (shows the PR as conflicting
then)
- Fix stacktrace encountered in some repo if the content of a folder is empty
(or is a git submodule)
- Split the web-hooks into their own server
- If you try to fork a forked project, redirect the user to the fork
- Show the repo from and repo to when opening a new PR
- Add the pagination links at the bottom of the repo list as well
- Add the groups to the pool of users to notify upon changes to a project
- Hide private repo from user who do not have commit access
Happy hacking!
Pierre
7 years, 10 months
Group vars update for wiki (production)
by David Shier
Below and attached are the diff for updates to the group vars for wiki.
--- wiki.orig 2015-11-23 22:06:37.551441866 -0500
+++ wiki 2015-11-23 22:57:52.441270349 -0500
@@ -30,3 +30,13 @@
nfs_mount_opts: "rw,hard,bg,intr,noatime,nodev,nosuid,nfsvers=3"
+csi_security_category: Moderate
+csi_primary_contact: #fedora-admin
+csi_purpose: Provides our wiki
+csi_relationship: |
+
+There are multiple servers that this service requires. Proxy 1,2 and 3 and
Wiki
1 and 2.
+
+- Wiki requires the proxy servers in order for traffic to pass to them
+- If the Apache processes stop on wiki01 and wiki02 the wiki will not
display
+- The wiki also requires fas for log in purposes. If fas is down, the wiki
will
not become unavailable; however, no on will be able to authenticate
-----------
Dave Shier
“Diplomacy is the art of telling people to go to hell in such a way that
they ask for directions.” -Winston Churchill
7 years, 10 months
Updated Group Vars for torrent
by David Shier
Attached and below.
--- torrent.orig 2015-11-21 08:06:28.981136020 -0500
+++ torrent 2015-11-23 21:33:43.759875093 -0500
@@ -14,3 +14,16 @@
csi_security_category: Low
csi_primary_contact: Fedora Admins - admin(a)fedoraproject.org
csi_purpose: Torrent master server for Fedora distribution
+csi_relationship: |
+
+torrent01 is the master torrent server for Fedora releases
+
+This host relies on:
+- The virthost it's hosted on (ibiblio03.fedoraproject.org)
+- FAS to authenticate users
+- VPN connectivity
+
+Things that rely on this host:
+- If this host is down, Fedora will lose a release distribution channel
+- The Apache that displays the torrent website
+- This server also has opentracker+ running to gather statistics for our
torrent
s
-----------
Dave Shier
“Diplomacy is the art of telling people to go to hell in such a way that
they ask for directions.” -Winston Churchill
7 years, 10 months
group_vars csi patch for virthost
by David Shier
Below and attached is a patch to add group vars for csi compliance for
virthost. As I did not find much in the way of documentation, and cannot
currently log on to any of the virthost servers I have left them pretty
general.
- virthost.orig 2015-11-19 13:18:42.781783307 -0500
+++ virthost 2015-11-19 13:18:18.305474418 -0500
@@ -1,5 +1,5 @@
-----
-scsi initiator for netapp iscsi volume
+---
+# iscsi initiator for netapp iscsi volume
netapp_nfs01_iscsi_name:
iqn.1992-08.com.netapp:sn.1573980325:vf.f88732f4-106e-1
1e2-bc86-00a098162a28
# iscsi portal for netapp iscsi volume
netapp_nfs01_iscsi_portal: 10.5.88.36
@@ -8,3 +8,15 @@
nrpe_procs_warn: 900
nrpe_procs_crit: 1000
+
+# These variables are pushed into /etc/system_identification by the base
role.
+# Groups and individual hosts should override them with specific info.
+# See http://infrastructure.fedoraproject.org/csi/security-policy/
+
+csi_security_category: High
+csi_primary_contact: Fedora Admins - admin(a)fedoraproject.org
+csi_purpose: Host guest virtual machines.
+csi_relationship: |
+ * Guests on this host will be inaccessible if the host is down.
+ * This host will be required by any application with a virtual machine
running on it, therefore, if this host is down those applications will be
impacted.
+
-------
Dave Shier
7 years, 10 months
image F23 + python2
by Miroslav Suchý
FYI
I prepared in Fedora cloud image:
Fedora-Cloud-Base-23.x86_64-python2
which is Fedora 23 Cloud image plus python2, selinux modules, plus
today's "dnf upgrade".
The problem I did not resolved so far is that:
growpart /dev/vda 2
now returns rc 2 when /dev/vda2 does not exist (compared to rc1
previously) so task
tasks/growroot_cloud.yml
fails.
Mirek
7 years, 10 months
