[release] anitya: 0.10
by Pierre-Yves Chibon
Good Morning Everyone,
I just cut a new anitya release: 0.10
Here is the corresponding changelog:
* Fri Oct 28 2016 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.10-1
- Update 0.10
- Add a blacklist user feature preventing blacklisted users from logging in
- replaced yum by dnf in fedmsg in the doc (Jean-Baptiste)
- Specified (UTC) timezone in the footer. (Sourav Badami)
- Added backend column in search results. (Sourav Badami)
- Added border to the columns in the log view. (Sourav Badami)
- Fix tests (Ralph Bean)
- Use a common http session to make things a little faster. (Ralph Bean)
- Add support to backend for repo feeds (Ralph Bean)
- Add a --check-feed argument to the cronjob (Ralph Bean)
- Replace the version prefix only once (Chaitanya Kukde)
- Improved search results by adding substring search. (Sourav Badami)
- Port from user's email to user's OpenID identifier
- Keep the user's email when they flag a project (so admins know who did what)
- Remove the version_prefix much earlier in the process so we can do version
comparison without them
- Enforce that the homepage be an URL
- Fix the stackage regex for the change on the stackage website
- Add tabindex to our page/forms
- Improve the Dockerfile (PrahlM93)
- Start py3 compatibility (Nick Coghlan)
- Add upstream ecosystems to model (ick Coghlan)
- Improve reading the XML files (Slavek Kabrda)
- Allow checking for release when project is created/edited (Slavek Kabrda)
- Specify rel="noopener noreferrer" to link including target='_blank'
- Let AnityaInvalidMappingException inherit from AnityaException
- Fix the bitbucket backend as they have changed their behaviour
- When mapping a project make the package name be the project name to start with
- Implement filtering /api/projects for a certain distro
- Allow api_get_project_distro to receive package name with a '/'
- Use lstrip() instead of replace() to remove the version prefix
- Update footer and link to the API documentation
- project wide pep8 clean up
As you can see quite a few changes made, including changes to how we crawl repos
for version information, this is however not yet being used.
Thanks to all the contributors who help making this happen!
Pierre
7 years, 5 months
Proposal to mirror Docker images
by Randy Barlow
During Flock 2016, I had the opportunity to talk with Adam Miller,
Dennis Gilmore, and Pierre-Yves Chibon about the technical challenges
with distributing Docker images with Fedora's extensive mirror network.
These conversations helped me to solidify a proposal for how Fedora
could solve this problem, outlined below.
High level view
===============
In summary, the proposal is to write a patch for the docker client that
will give it the capability to accept metalink responses upon docker
pull operations. We would also need to add support for Docker images to
mirror list and mirror manager. Additionally, we will need a small tool
to pull the content to be mirrored out of a docker registry and write
them to disk in a format that can be mirrored, as well as some Ansible
code to run the tool when there is new content to be mirrored.
Background
==========
The Fedora project wishes to begin distributing new types of content
than it has in the past. One of the types that has been identified as a
goal is the Docker image. Adam Miller has already done the work that
will allow packagers to build Docker images, but we still need a way to
distribute those builds to Fedora's users. Adam Miller's implementation
helpfully drops the builds we want into a Docker registry.
Proposed Changes
================
Mirror List
-----------
Users will be pointing their docker clients at Mirror List when they
docker pull Fedora's Docker images. In order for this to work, we will
need to make two changes to Mirror List so that it can respond to the
docker client properly. The first change is that Mirror List will need
to respond with a special header and a body of "{}" when the docker
client sends a GET request for /v2/. The second change is that it will
need to return a metalink document when the client makes additional
requests so that the clients can be redirected to a list of mirrors
near their locations, just as it does with the dnf client today.
The docker client typically connects to port 5000. We could run a
second instance of Mirror List on port 5000 if we wanted to isolate it
from the current instance. We can also have the docker client pull from
443 as dnf does if we want to keep the deployment simpler.
Mirror Manager
--------------
We will need to make a few changes to Mirror Manager as well. We will
need to provide an interface to allow mirror admins to opt in/out of
mirroring Docker content. We will also need to modify the curler to
detect whether a given mirror is up to date or not. We will need to make
sure that UMDL is updated when content changes.
docker
------
The most significant work required will likely be modifying the docker
client to enable it to properly handle the metalink responses it will be
receiving from Mirror List. When requesting the manifest, it will
receive a metalink document that will give it a priority ordered list of
mirrors. It will need to work through the list in order until it reaches
a mirror that has the correct checksum for the requested manifest. It
will then use that same mirror for the subsequent blob requests.
There is some concern that such a feature would not be accepted by the
upstream docker project. If we were to proceed with this proposal, we
would propose this patch to the upstream Docker project. If upstream
were not willing to accept the feature, we would need to have the Fedora
docker packager carry this patch as a downstream add on.
New Tool
--------
The last piece that is needed is a tool that can create the filesystem
tree that we want to synchronize out to the mirrors. The mirrors only
need to carry manifests and blobs, so the tool needs only to pull these
documents out of the registry that Adam Miller has set up and write them
to disk in a particular structure. For optimization, we could use
hardlinks for blobs that are common across the various images (for
example, the Fedora base blob will be the same in all images) to save
rsync time and mirror disk space.
Additionally, we will need a playbook to run this new tool in response
to fedmsgs. We may be able to use Adam Miller's loopabull project to run
such a playbook at the right times.
Conclusion
==========
Thanks for reading, and please respond with any comments or questions
you have about this proposal. I'm happy to clarify any points further,
and if you have any alternative proposals I'd love to hear those as
well.
7 years, 5 months
Today's infrastructure meeting
by Stephen John Smoogen
Not a lot to be said in this week as I didn't ask for items yesterday.
= 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-10-27)
#meetingname infrastructure
#topic aloha
#chair smooge relrod nirik abadger1999 lmacken dgilmore threebean
pingou puiterwijk pbrobinson
#topic New folks introductions
= 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 kevin is on vacation til next week
#info closed/moved/upstreamed a bunch of old tickets - kevin
#info askbot replacement discussion
#info Bodhi 2.3.0 release into production today - puiterwijk and randy
#info we all live in a yellow submarine
= 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
= Apprentice office hours =
#topic Apprentice Open 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
--
Stephen J Smoogen.
7 years, 5 months
Bugzilla not accessible
by Zdenek Chmelar
Hello all
I'm not able to access bugzilla. Just getting error "Server not found".
The same happens for Zanata.
Do you experience the same please?
7 years, 5 months
Meeting Agenda Item: Introduction Edward G
by Edward G
Hi Everyone,
My name is Edward, and I am an undergraduate student. I am interested in
joining the Infrastructure Team and will start to observe the meeting from
next week.
IRC: cyberhack
CDT time zone
Plan to contribute: 10hr/week
Programming language: Java, C/C++, Python, and SQL.
some knowledge in OS system, Android Programing, and basic Linux kernel.
Since I am using Fedora and I will like to contribute to the community.
I will spend some time check out the repository and hopefully someone can
give me a direction to work on.
Thank you!
Best regards,
Edward G
7 years, 5 months
Pagure Migration - Design Team
by Micah Denn
Hi guys,
We are in the process of moving the design team over to pagure. We have some large files located here (https://fedorahosted.org/released/design-team/) that we would like to move over to the releases section of our pagure repo.
1) There appears to be 4mb limit on what we can upload there. As we deal with a lot of large image files, I'd like to ask if it is possible to raise this limit for our project?
2) Also is it possible for us push these files directly to pagure from their current location?
Thanks,
7 years, 5 months
Ticket #5533 Fedora Tagger contact point
by carlo
Hi All,
I am writing the SOP for the fedora-tagger app and I have been suggested
to ask in the list for you is the
contact point? I also wanted to ask you what should we do in case it
goes down.
Thanks to all.
Regards Carlo.
7 years, 5 months
Meeting agenda Item: Introduction Prashant Jamkhande
by Prashant Jamkhande
Hello Fedora-infra team,
Warm greetings!
Please allow me to introduce myself!
- IRC nick: PrashantJ
- Primary skills: Python, SQL, HTML, CSS
- Frameworks, Tools and systems: Django, git, vim
- Documentation tools: Sphinx, reST
- Associated with: DGPLUG (Open source knowledge sharing online
community)
Looking forward to learn about contribution to open source and use of
Python in FOSS together!
Thank you so much!
Regards,
--
*Prashant Jamkhande*
7 years, 5 months