Neal, thanks for the feedback. After taking your comments into
consideration, here's version 2.
| ID | Compression type | Index size |
| Compressed Index | Compressed Dict |
| Chunk | Chunk | ==> More chunks
'\0ZCK1', identifies file as zchunk version 1 file
Type of compression used to compress dict and chunks
0 - Uncompressed
2 - zstd
This is a 64-bit unsigned integer containing the size of compressed
This is the index, which is described in the next section. The index
is compressed without a custom dictionary.
Compressed Dict (optional)
This is a custom dictionary used when compressing each chunk.
Because each chunk is compressed completely separately from the
others, the custom dictionary gives us much better overall
compression. The custom dictionary is compressed without a custom
dictionary (for obvious reasons).
This is a chunk of data, compressed with the custom dictionary
| Checksum type | Checksum of all data |
| Dict checksum | End of dict |
| Chunk checksum | End of chunk | ==> More
This is the type of checksum used to generate the checksums in the
0 = SHA-256
Checksum of all data
This is the checksum of the compressed dict and all the compressed
chunks, used to verify that the file is actually the same, even in
the unlikely event of a hash collision for one of the chunks
This is the checksum of the compressed dict, used to detect whether
two dicts are identical. If there is no dict, the checksum must be
End of dict
This is the location of the end of the dict starting from the end of
the index. This gives us the information we need to find and
decompress the dict. If there is no dict, the checksum must be all
This is the checksum of the compressed chunk, used to detect whether
any two chunks are identical.
End of chunk
This is the location of the end of the chunk starting from the end of
the index. This gives us the information we need to find and
decompress each chunk.
The index is designed to be able to be extracted from the file on the
server and downloaded separately, to facilitate downloading only the
parts of the file that are needed, but must then be re-embedded when
assembling the file so the user only needs to keep one file.
we are now in the infrastructure freeze leading up to the Fedora 27 Beta
release. This is a pre-release freeze.
We do this to ensure that our infrastructure is stable and ready to
release the Fedora 27 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:
ansible/scripts/freezelist -i inventory
Any hosts listed as freezes is frozen until 2017-09-19 (or later if Beta
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
I'm Elorm. On IRC, I'm elormes. I'm a CSE undergrad student in Ghana. I
code much in python and do web development with django. I am familiar
with other langs like C# and Java. I have a fascination with DevOps and
I saw a blog post requesting for maintainers for the fedora-tagger
application. I would like to volunteer for the migration and also as a
long time maintainer.
A patch is attached to update and better organize the Fedora
Council-related aliases and update the Flock email addresses.
The patch changes the following:
* Organizes and comments Fedora Council aliases together
* Changes board alias to council-private(a)lists.fp.o
* Links to new doc pages for FPL and FCAIC in comments
* Drop diversity alias (this was never used in Diversity Team)
* Use fcaic alias for Flock emails instead of hard-coding bex
Let me know if anything else is needed. Thank you!
Justin W. Flory
In a futile effort to get slightly less email to worry about, I'd like
to nuke the scholarship alias, since we no longer do the scholarship
and the address gets nothing but spam at this point.
I'd like to push this and run bastion.yml with -t fas_client
Author: Ricky Elrod <relrod(a)redhat.com>
Date: Wed Mar 28 21:39:07 2018 +0000
Remove myself from scholarship alias, it is all spam at this point anyway
Signed-off-by: Ricky Elrod <relrod(a)redhat.com>
diff --git a/roles/fas_client/files/aliases.template
index 41682da..a655be7 100644
@@ -243,7 +243,7 @@ nick.bebout: nb
# Fedora Scholarship
# Fudcon regional aliases - point to point person before that fudcon
I would like to add a bugzilla email exception for jbwillia
From 230a9e78c92c07880956072046080353d73f215f Mon Sep 17 00:00:00 2001
From: Nick Bebout <nb(a)batcave01.phx2.fedoraproject.org>
Date: Thu, 29 Mar 2018 17:39:34 +0000
Subject: [PATCH] Add a bugzilla email exception for jbwillia
roles/distgit/pagure/files/fas2.py | 2 ++
1 file changed, 2 insertions(+)
diff --git a/roles/distgit/pagure/files/fas2.py
index 7886c02..f20b0bd 100644
@@ -273,6 +273,8 @@ class AccountSystem(BaseClient):
# Dusty Mabe: dusty(a)dustymabe.com
+ # Ben Williams: vaioof(a)gmail.com
+ 100572: 'jbwillia(a)math.vt.edu ',
# A few people have an email account that is used in owners.list
# have setup a bugzilla account for their primary account system
This shared document is for the next fedora infrastructure meeting.
= Preamble =
The infrastructure team will be having its weekly meeting tomorrow,
2018-03-29 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.
= 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 (2018-03-29)
#chair smooge relrod nirik pingou puiterwijk tflink
= 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
(Please use #info <the thing> - your name)
#topic announcements and information
#info Infrastructure hackfest in april:
#info We are in F28 Beta Freeze! All changes to frozen hosts must get
+2 on list before being applied - kevin
= 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.
= Apprentice office hours =
#topic Apprentice Open office minutes
#info A time where apprentices may ask for help or look at problems.
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
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
Stephen J Smoogen.
Good Morning Everyone,
The Atomic CI pipeline running at:
is running on Fedora 27 but greenwave hasn't been instructed to gate based on
So I would like to make the following change to greenwave's policy and run the
greenwave playbook that should rebuild the containers with the new policy.
@@ -136,6 +136,7 @@ data:
+ - fedora-27