Hi, I am Anatolii.
I have some time now and can work 5-6 hours a week. Sometimes more.
- puppet server configuration and manifest writing
- CentOS/RedHat linux administrator ( My RHCE finished at oct 16,
will update my certification)
- network engeeneer ( cisco, mikrotik, linux routers )
- vm - qemu-kvm, docker
- postfix mail servers
- hosting solutions ( nginx / apache + php/php-fpm +
mysql/mariadb/galera cluster )
Thats my skills and I hope I will be useful for Fedora communiti.
I know C, python, but I do not use it so I will be glad to work not
only as system administrator, but as developer. Just to test my skills.
I hope thats the right mail list.
Things changed a little here and I will have more time to help now.
I would like to work in these areas:
1. Web servers
3. Networking engineering
At this time I will be able to work 10 - 15 hours a week.
Just need a quick bit of advice, I have created a VM so I can use some
of the tools and software that is used I have installed ansible and
bookmarked the documentation for it, is there anything else I should be
looking at and adding to my VM?
I've tagged a new release for the-new-hotness, 0.8.0. There's not yet an
SOP for the-new-hotness so I'll be writing that along the way as I
deploy it in the next few days.
The changelog is included below:
- rebase-helper has been removed from the-new-hotness. For a detailed
discussion that lead to this decision, see issue #145.
- the-new-hotness now integrates with mdapi to determine the latest
versions of packages rather than repoquery. This fixes a bug where
the-new-hotness would report that the latest rawhide build was the
EPEL 7 (Issue #98)
- The ``userstring`` setting has been replaced by a ``user_email`` setting.
This setting is tuple in the form ('User Name', '<email address>').
- Several configuration URLs have been updated to use HTTPS
- Log entries are now emitted with their full Python path included so
- the-new-hotness now authenticates with Koji using Kerberos
Good Morning Everyone,
I just cut a new release of pagure: 2.12.1.
It's a bug-fix release with the following changelog:
* Mon Feb 13 2017 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.12.1-1
- Update to 2.12.1
- Include the build id in the flag set by pagure-ci on PR (Farhaan Bukhsh)
- Fix using the deploy keys (Patrick Uiterwijk)
- Add the possibility to ignore existing git repo on disk when creating a new
- Fix checking for blacklisted projects if they have no namespace
- Link to the documentation in the footer (Rahul Bajaj)
- Fix retrieving the list of branches available for pull-request
- Order the project of a group alphabetically (case-insensitive)
- Fix listing the priorities always in their right order
Happily running in stg and prod already :)
At a recent infrastructure meeting we agreed to move our SOPs to
Pagure as part of an infrastructure documentation project I proposed.
The new home will be https://pagure.io/infra-docs/. The project's README
contains instructions on how to build the project locally.
Unless there are objections, I would like to set the migration date for
February 16th. The migration will consist of the following tasks:
* Update all documentation that references the SOPs to point to the
* Pull the latest versions of the SOPs on batcave01 into the Pagure
project. This is an easy `git pull` operation.
* Set the repository on batcave01 to be a read-only copy that pulls from
pagure on a regular basis.
A few notes about the migration:
* All git history for the SOPs has been preserved.
* Adding or modifying SOPs can now be done via pull requests to the
Pagure project. For documentation on this process, consult
* I've manually added people as project administrators since there isn't
a group on Pagure I can add. I probably missed some people. If you
find yourself in need of write access to the repository any of the
admins should be able to add you.
* The project's master branch is automatically built on readthedocs
each time a commit is pushed. The HTML site is also available on
Pagure's docs hosting, but this is not built automatically yet.
I'd really appreciate it if people could take a few minutes and read
through the README as well as the SOP dev guide and let me know if
anything is unclear.
Last week I filed a Request For Resources for a highly available
container registry that I plan for us to run on our datacenter. It is
in the Pre sponsorship phase, so I am seeking someone from sysadmin-
main who can sponsor it for me. Is anyone interested?
I should write this earlier but I kept thinking how to say this. When I joined the infrastructure group I wanted to do some development contribution for the fedora project but soon I found that we are not doing development here. Then I thought maybe I can do something else to contribute and I learned something. However, I found there is too many different things to learn for me while I'm overwhelmed by a lot of things. I apologize if I let you down.
Good Evening Everyone,
I just cut a new release of pagure: 2.12.
Here is its changelog:
* Fri Feb 10 2017 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.12-1
- Update to 2.12
- Fix the place of the search and tags bars in the issues page (Pradeep CE)
- Support removing all content of a custom field (Patrick Uiterwijk)
- Improve the `My Pull Requests` page (Pradeep CE)
- Fix displaying binary files in the documentation
- Add a way to easily select multiple tags in the issues list and roadmap
- Allow selecting multiple milestones easily in the UI of the roadmap
- Fix displaying namespaced docs (Igor Gnatenko)
- Fix the web-hook server
- Add a way to view patch attached to a ticket as raw
- Allow milestone to be set when creating an issue using the API (Mark Reynolds)
- Fix adding and editing tags to/of a project
- Make the usage section of the doc be at the top of it (Jeremy Cline)
- Add notifications to issues for meta-data changes (Mark Reynolds)
- Fix not updating the private status of an issue when loading it from JSON
- Fix triggering web-hook notifications via the fedmsg hook
- Add a configuration key allowing to hide some projects that users have access
to only via these groups
- Fix figuring out which branches are not merged in namespaced project
- Automatically link the commits mentionned in a ticket if their hash is 7 chars
- Allow dropping all the priorities info of an issue
- Do not edit multiple times the milestone info when updating a ticket
- Only update the custom field if there is a value to give it, otherwise remote
- Make pagure compatible with flask-wtf >= 0.14.0
- Add a button to test web-hook notifications
- Fix the layout on the page listing all the closed issues (Rahul Bajaj)
- Load priorities when refreshing the DB from the ticket git repos (Mark
- Ignore `No Content-Type header in response` error raised by libgit2 on pull
from repo hosted on github (for remote PR)
- Add deployment keys (ssh key specific for a single project can be either read
and write or read-only) (Patrick Uiterwijk)
- Fix install the logcom service to log commits
- Fix deleting tickets that have a tag attached
- Allow pre-filling title and content of an issue via URL arguments:
- Re-initialize the backend git repos if there are no tickets/PRs in the DB
- Fix invalid pagination when listing all the tickets (regardless of their
status) and then applying some filtering (Vibhor Verma)
It is currently happily running in stg. I do not plan to update prod today,
maybe on Sunday if time allows.
This version is also intended to land in src.stg.fp.o/pagure sometime next week,
wish me luck with that :)