Meeting Agenda: Introduction Patrick Kuny
by Patrick Kuny
- IRC Handle: netcronin
- Github: netcronin
- Email: pmk62810(a)gmail.com
- What skills you have to offer and which you would like to learn.
- Beginner Ansible and Chef skills, beginner Perl and Bash
Scripting.
- Beginner experience in Linux Administration - experience setting
up various services: HTTP(S), FTP, SFTP, GlusterFS replication, Zabbix
monitoring, Chef cookbooks, Ansible playbooks, General Server
Administration (Fail2Ban, SELinux, iptables, FirewallD, etc.)
- Worked specifically with moving open-source technology stacks to
Docker containers.
- Studying for RHCSA
- Interested in automation, general Linux administration
- Run a small homelab for testing (automated via Ansible, of
course)
- Network knowledge
- Work for Cerner Corporation in Kansas City, MO as a System
Engineer
- Central Timezone
- Also plan to join the Fedora Ambassadors program
- Interested in teaching and mentoring new users/infra members
eventually, once I've earned it.
- What you want to learn
- Anything the team needs help with, especially Linux admin work and
best practices surrounding it.
- Interested in Fedora Infrastructure Apprentice program. Both
joining and helping out with.
- Any initial questions you have for the team
- Nothing specific. Lurking in IRC and have read the last few meeting
minutes, as well as looking over the architecture topology. Bear
with me as
I may ask some dumb qu
Thanks,
Patrick Kuny
C: 816.507.5495
[image: https://www.linkedin.com/in/patrick-kuny-3855964b]
<https://www.linkedin.com/in/patrick-kuny-3855964b>
6 years, 8 months
[Release] mdapi: 2.10.1 and 2.10.2
by Pierre-Yves Chibon
Good Morning Everyone,
I just cut a couple of new mdapi releases: 2.10.1 and 2.10.2.
Here are their changelog:
* Tue Aug 08 2017 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.10.1-1
- Update to 2.10.1
- Fix the srcpkg endpoints
* Tue Aug 08 2017 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.10.1-1
- Update to 2.10.1
- Fix the srcpkg endpoints
This second release was required because someone pushed to a stable Fedora
release (f25 in this case) an upgrade of python3-aiohttp from 1.0.5 to 2.2.0
which as you can see is a major version upgrade and of course lead to some API
changes.
This is currently happily working in prod and stg.
Happy querying!
Pierre
6 years, 8 months
Meeting Agenda Item: Introduction Kai Bojens
by Kai Bojens
Hello everybody,
please let me introduce myself. My IRC nick is 'profnixer' (Fedora Account:
kbojens) and I'd like to join the Infratructure Apprentice group.
I'm a Linux sysadmin for more than twenty years now and have gained some
experience in almost everything but networking. However, my main focus is
everything related to web hosting (mail, web, database, HA) and of course
some desktop stuff. So, I know how to use Bash, Perl, git, saltstack some
rudimentary C and sometimes even python.
For the start I'd like to see if I can solve some of the low hanging fruits
in 'easyfix' like the mapping for example.
6 years, 8 months
Big HyperKitty schema change
by Aurelien Bompard
Hey folks!
There's a pretty big DB schema change that I'd like to do in HyperKitty,
and since it involves a primary key I expect a downtime of several hours,
possibly a day (more precise testing going on)
The good news it that mailman will keep running, only the web UIs will be
down (HyperKitty & Postorius, the admin UI).
It's a change that I've put off for a while, but the more we wait the
longer the downtime will be (because it depends on the size of the email
table).
What time do you think would be the less worse for such a change? After
freeze break next week? After General Availability (whenever that is) ?
Another time?
I have a feeling that after freeze break is better because the folks who
use the web UIs to read email may also be those who will need to
communicate more after the GA, to discuss communication and reviews.
I don't mind starting the migration on a weekend of course, to impact less
people.
Thanks for your input.
Aurélien
6 years, 8 months
Meeting Agenda Item: Introduction Toni Rantala
by T. Rantala
Hello everyone!
I'm currently a service desk specialist, typical level 1 or 2 phone support
job but I also do server monitoring few days a month. Mainly monitoring
Windows servers but there are some RHEL and UNIX machines as well. Really
some basic stuff, restarting servers and services, making sure nothing runs
out of free space, investigating why some process is eating up all the RAM
or CPU and stuff like that. I started out with Linux with Fedora 14 some
years ago at school, gave up Linux for gaming and came back when F20 was
released and have used it ever since for everything else but gaming.
I've been doing some translations for Fedora in the Finnish group and now
I'm trying to give more back to the community and help any way I can. I'm
looking forward to learn much, much more about Linux (maybe something about
security too, Linux and security are the two things I'm most interested in)
and hopefully get a job as a Linux SysAdmin in the future. I believe being
a part of Fedora community and seeing the real life tickets is way more
valuable than just spinning up a few VMs and practicing on my own. I will
have to do a lot of studying and asking "stupid" questions around before I
can actually contribute but I will do my best.
IRC handle and FAS: bombandealer
Best regards
Toni
6 years, 8 months
Meeting Agenda Item: Introduction James Cassell
by James Cassell
Hello,
I'm a systems administrator for my day job. I'm currently working on using ansible to automate machine provisioning and management in a vmware virtualized environment. The linux machines are mostly CentOS 6 with some CentOS 7 and a couple RHEL 6 boxes. These are in a predominantly windows environment, with Microsoft Active Directory domains. (In a previous job, I worked with chef in a debian environment.)
I'm hoping to help out any way I can and "learn by doing." I'm specifically looking to do tasks with ansible and to learn best practices. I have not been active with Fedora for several years, but in the past, I've helped with the wiki, submitted lots of bodhi feedback, and helped with testing releases. Outside of Fedora, I've contributed an implementation of the sieve imap4flags extension to the cyrus imapd project. This was mostly done in C, but also included a bit of yacc/bison... I'm competent at programming but haven't done much of it as a day job. I expect I will end up learning python as it's becoming ubiquitous.
IRC Handle: cyberpear
I look forward to helping and learning! I've also just joined the fi-apprentice group and am looking around.
V/r,
James Cassell
6 years, 8 months
Syncing and archiving old releases
by Stephen John Smoogen
In the past, we would normally begin syncing soon to be EOL releases over
to Archives so that the mirrors would be ready for it. We haven't done this
for a bit and a couple of mirrors have complained that /pub/fedora is
larger than they want to keep. I would like to get an official policy to
them about how many releases that a mirror should expect to be in
/pub/fedora and when we plan to archive off releases.
The steps for syncing/hardlinking releases was the following:
log into a box with read-write access to the the release tree.
sudo su -s /bin/bash ftpsync
cd /pub/fedora/linux/releases
ls -l /pub/archive/fedora/linux/releases/ # to see if tree is already synced
If I were to archive off 23 I would now do the following:
cp -lr 23/ /pub/archive/fedora/linux/releases/
this should hardlink everything across so we save disk space.
cd ../updates
cp -lr 23/ /pub/archive/fedora/linux/updates/
cd testings
cp -lr 23/ /pub/archive/fedora/linux/updates/testing/
cd /pub/fedora-secondary/releases
cp -lr 23/ /pub/archive/fedora-secondary/releases/
cd ../updates/
cp -lr 23/ /pub/archive/fedora-secondary/updates/
cd testing
cp -lr 23/ /pub/archive/fedora-secondary/updates/testing/
Make any changes to scripts which do fullfilelist to make it know about new
trees.
Announce the mirroring to mirrors-list and then wait 2 weeks.
After two weeks are done, have mirrormanager point to the archive tree.
Remove the data out of /pub/fedora and /pub/fedora-secondary
Hardlink the file in a previous archived directory to the empty directory
Update the fullfilelist
Email mirrorlist about the changes being completed
======
What should we tell the lists that the number of releases which will be in
the main repository now? And how many releases should I archive off after
F24 goes EOL next week?
--
Stephen J Smoogen.
6 years, 8 months
Re: Aug status update for Fedora Infrastructure Apprentices
by Athos Ribeiro
On Aug 2, 2017 7:46 PM, "Kevin Fenzi" <kevin(a)scrye.com> wrote:
>
> 0. Whats your fedora account system login?
athoscr
>
> 1. Have you logged in and used your fi-apprentice membership to look at
> our machines/setup in the last month? Do you plan to?
>
yes
> 2. Has it helped you decide any area you wish to focus on or contribute
> to more?
yes
>
> 3. Have you looked at or been able to work on any of the fi-apprentice
> 'easyfix' tickets?
not lately
> 4. Do you still wish to be a member of the group? If not (for whatever
> reason) could you provide any hints to help others down the road?
>
yes. See the easyfixes, join IRC.
> 5. Is there any help or communication or ideas you have that would help
> you do any of the above?
>
no
> 6. What do you find to be the hardest part of getting involved? Finding
> things to work on? Getting attention from others to help you? Finding
> tickets in your interest area?
>
Organizing time spent in Fedora activities.
> 7. Have you been able to make any weekly irc meetings? Do you find them
> helpful or interesting? Do you have any suggestions for changing them?
>
yes/yes/not at all
> 8. Have you logged into our Gobby instance and read/seen/added to our
> meeting agenda? https://fedoraproject.org/wiki/Gobby
>
yes
> 9. What are the top 5 commands you run by number? You can get these with
> something like:
>
> history | awk '{print $2}' | sort | uniq -c | sort -nr | head -5
>
> (or something more clever of your own devising)
>
This is actually interesting. I believe some of them change a lot
depending on what I am working on.
265 ls
196 git
125 vim
105 cd
54 make
--
Athos Ribeiro
http://www.ime.usp.br/~athoscr
6 years, 8 months
Documentation review for fedmsg
by Jeremy Cline
Hey folks,
I recently started re-writing the fedmsg documentation. Since its
primary users are people in Fedora Infrastructure, I'd love your
feedback on the first draft.
There's a pull request[0] where you can leave comments on the diff,
but I also built the documentation so you can see what it really
looks like.
The current docs: https://fedmsg.readthedocs.io/en/latest/
The proposed docs: http://jcline-fedmsg.readthedocs.io/en/reorg-docs/
I'm particularly interested in how you find the organization of the
proposed docs. Is the order weird/unexpected/confusing? Is there a
section you think is missing? Do they go into enough detail?
Any feedback would be greatly appreciated (either on GitHub or here via
email).
[0] https://github.com/fedora-infra/fedmsg/pull/453
--
Jeremy Cline
XMPP: jeremy(a)jcline.org
IRC: jcline
6 years, 8 months
