My name is Anatoliy Kartashov. I am from Russia.
I start to work as freebsd system administrator, but later changed to Linux.
I have aroud 8 years of Linux system administration - CentOS/ SLES.
- squid,postfix, zabbix, bacula, named, and etc..
- manage distributed networks
- setup cisco, mikrotik, linux routers
Certification: RHCE on 6
What I want to learn:
First I am going to understand the ifrustructure of fedora project. How
to create and orginize and work in such projects.
Next web services - best pructice, high availability, monitoring, scaling.
Learn and train my skills in python or C.
Good Morning Everyone,
I just cut a new release of pagure: 2.13
Here is the corresponding changelog:
* Tue Feb 21 2017 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.13-1
- Update to 2.13
- Allow filtering issues for certain custom keys using <key>:<value> in the
search input (Patric Uiterwijk)
- Make loading the JSON blob into the database its own async service
- Add ACLs to pagure (Vivek Anand)
- Fix running the tests against postgresql
- Let the doc server return the content as is when it fails to decode it
- Fix rendering a issue when one of the custom fields has not been properly
setup (ie a custom field of type list, with no options set-up but still having
a value for that ticket)
- Fix auto-completion when adding a tag to a ticket
- Add the possibility to filter the issues with no milestone assigned (Mark
- Fix the callback URL for jenkins for pagure-ci
- Backport the equalto test to ensure it works on old jinja2 version (fixes
accessing the user's PR page)
It's currently happily running in stg, I'd like to test the pagure-loadjson
service there before pushing to prod.
My name is Will Turnage and I'm located in the US, central time zone. I
have around six years of UNIX/Linux system administration experience.
I've mostly been in big shops where the sysadmin only does OS work, but
I'm looking to learn more while sharing the knowledge I do have.
The reason I would like to join is to improve my automation and python
skills. I can offer at least 4 hours a week to start off with
(hopefully it will be more).
IRC handle : wfturnage
Programming skills include python (intermediate) and bash.
Sysadmin skills: cfengine 3, SaltStack, RHEL(4-7), nagios, BIND.
Certifications: RHCE on 7, and VCP6-DCV
Looking for an Easyfix to start off with and "#5154 Write SOP for
whatcanidoforfedora.org " catches my eye. I'm not much of a writer but
I'm willing to give it a shot. I'll start reading other SOPs to
familiarize myself with the formatting.
Will Turnage <wfturnage(a)gmail.com>
In the past we haven't bothered to make fedoraplanet.org https because
some/many of the blogs that are aggregated there are http. However, now
with the advent of letsencrypt, I wonder if we shouldn't revisit that.
I noticed this again due to a recent gnome planet post:
* We get a https cert for fedoraplanet.org and enable it.
(of course right now it will show lots of insecure content which will
be anoying support wise as people ask us about it, but no more so than
'why isn't it https enabled').
* We send out an announcement asking everyone who has a blog aggregated
on fedoraplanet to https enable their blogs.
* We have some deadline (like 6 months? a year? less?) and after that
point we drop all the http blogs and only allow https.
There's no real security advantage here, other than making more traffic
on the net encrypted, which I think is a good goal.
What do folks think? Doable? To harsh? Pointless?
anitya-0.11.0 has been released and is now running in production at
* Return 4XX codes in error cases for /projects/new rather than 200
* Allow projecst using the "folder" backend to make insecure HTTPS requests
* Fix an issue where turning the insecure flag on and then off for a project
resulted in insecure requests until the server was restarted (Issue #394)
* Add a data migration to set the ecosystem of existing projects if the
they use is the default backend for an ecosystem. Note that this migration
can fail if existing data has duplicate projects since there is a new
constraint that a project name is unique within an ecosystem (Issue #402).
* Fix the regular expression used with the Debian backend to strip the
being incorrectly included in the version (Issue #398)
* Added a new backend and ecosystem for https://crates.io (Issue #414)
The infrastructure team will be having it's weekly meeting tomorrow,
2017-02-16 at 19: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.
This shared document is for the next fedora infrastructure meeting.
= 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 (2017-02-16)
#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 CAA dns records added to fedoraproject.org and getfedora.org - kevin
#info DKIM mail signing active for pagure.io/fedoraproject.org/lists - kevin
#info mirrorlist containers now active on all proxies - kevin/patrick
#info mass rebuild in rawhide finished sunday - 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 fedorahosted migration status - kevin
#topic requiring blogs to be https - kevin
= 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 gsetup 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: mirrorlist containers - kevin
= Meeting end stuff =
#topic Open Floor
Hi folks! So I've been floating an idea around recently to people who
are currently using ResultsDB in some sense - either sending reports to
it, or consuming reports from it - or plan to do so. The idea was to
have a group where we can discuss (and hopefully co-ordinate) use of
ResultsDB - a place to talk about result metadata conventions and so
It seemed to get a bit of traction, so I've created a new mailing list:
resultsdb-users . If you're interested, please do subscribe, through
the web interface:
or by sending a mail with 'subscribe' in the subject to:
Please note: despite the list being a fedoraproject one, the intent is
to co-ordinate with folks from CentOS, Red Hat and maybe even further
afield as well; we're just using an fp.o list as it's a quick
convenient way to get a nice mailman3/hyperkitty list without having to
go set up a list server on taskotron.org or something.
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net