Meeting Agenda Item: Introduction Mohammed Tayeh
by Mohammed Tayeh
Hi All,
I'm a Systems Administrator, I have more than 4 years Experiences at Orange Palestine co. (ISP Company)
I'm using Fedora on my main laptop over 5 years and I'm looking to contribute to the Fedora community
my IRC nickname is "Tayeh"
I'm a certified Linux System Admin (LFCSA), and I'm worked on a lot of projects
I want to join the fedora system admin team if possible
and I need to learn more from the fedora team and improve my skills
I need some help from the team to help me to get started with fedora sysadmin team
Best Regards
3 years, 9 months
Testing new implementation of OIDC when updating app
by Jonathan Trossbach
Hi all,
I am working on updating nuancier to work with the OIDC authentication library. I believe I have made all the necessary changes but am not sure about the best way to go about testing the changes I have made, which can be found here: https://github.com/jontrossbach/nuancier/tree/update-to-oidc
Other applications like fedora elections have already been updated to OIDC, can someone tell me how they tested the new authentication process in their development environments for those applications and tell me how I can best test the changes for the OIDC in nuancier? I know at least one other person is wondering the same thing.
Thank You,
Jon Trossbach
3 years, 9 months
Vagrant (Was: Re: What is our technical debt?)
by Pavel Valena
> -------- Přeposlaná zpráva -------- Předmět: Re: What is our technical debt?
> Datum: Thu, 25 Jun 2020 21:59:37 +0200
> Od: Pierre-Yves Chibon <pingou(a)pingoured.fr>
> Adresa pro odpověď: Fedora Infrastructure
> <infrastructure(a)lists.fedoraproject.org>
> Komu: Fedora Infrastructure <infrastructure(a)lists.fedoraproject.org>
> On Thu, Jun 25, 2020 at 03:51:42PM -0400, Neal Gompa wrote:
> > On Thu, Jun 25, 2020 at 3:27 PM Pierre-Yves Chibon <pingou(a)pingoured.fr>
> > wrote:
>
> > >
>
> > > Good Morning Everyone,
>
> > >
>
> > > Just like every team we have technical debt in our work.
>
> > > I would like your help to try to define what it is for us.
>
> > >
>
> > > So far, I've come up with the following:
>
> > > - python3 support/migration
>
> > > - fedora-messaging
>
> > > - fedora-messaging schema
>
> > > - documentation
>
> > > - (unit-)tests
>
> > > - OpenID Connect
>
> > >
>
> > > What else would we want in there?
>
> > >
>
> > These are all good things, especially the documentation one. I'd like
>
> > to zero in on a particular aspect of documentation, though: getting to
>
> > hack on it. A lot of our projects are surprisingly difficult to get up
>
> > and running for someone to play with and hack on, and this is
>
> > increasingly true as we adopt OpenShift-style deployments. One way we
>
> > solved this in Pagure is by providing some quick start processes in
>
> > the documentation and a fully working Vagrant based process to boot up
>
> > and have a working environment to hack on the code.
>
> > I'm not necessarily going to specify it needs to be Vagrant for
>
> > everything, but I think this is something we should have for all of
>
> > our projects, so that people *can* easily get going to use and
>
> > contribute.
>
> I've recently had quite some pain with vagrant (just today, I've tried
> several
> time to start my bodhi vagrant box and lost my morning w/o success).
Hello,
sorry I'm late to the party, I've heard of your Vagrant issues-
I'm a Vagrant maintainer, and I'll gladly help if you encounter any Vagrant issues, feel free to ping me on IRC (`pvalena`).
I can also do some review of your Vagrantfiles, and run some tests, if you like (to prevent instabilities etc.).
One good thing I always advise to try are the latest stable (=rawhide) Vagrant builds from my COPR:
https://copr.fedorainfracloud.org/coprs/pvalena/vagrant/
(Built for all Fedoras and CentOS 7+8, although CentOS 7 currently needs manual workarounds.)
Pavel
> I guess it may be nice to see if there is something else out there that we
> could
> leverage.
> If we could adopt one and try to get have it on most of our apps this may be
> a
> nice goal for us to work towards.
> Pierre
> _______________________________________________
> infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedora...
3 years, 9 months
CPE Weekly: 2020-07-05
by Aoife Moloney
# CPE Weekly: 2020-06-218
Background:
The Community Platform Engineering group is the Red Hat team combining
IT and release engineering from Fedora and CentOS. Our goal is to keep
core servers and services running and maintained, build releases, and
other strategic tasks that need more dedicated time than volunteers
can give.
See our wiki page here for more
information:https://docs.fedoraproject.org/en-US/cpe/
## General Project Updates
The CPE team have finished our Quarterly Planning for Q3, July -
September, and will begin work on the following projects starting from
Monday:
* Data Centre Move - Final Works
* CentOS Stream Phase 3
* Noggin Phase 3
* Packager Workflow Healthcare
* Fedora Messaging Schemas
Details of the above projects, and of projects currently in progress,
done and what projects are in our backlog, can be found on our taiga
board per project card:
https://tree.taiga.io/project/amoloney1-cpe-team-projects/kanban?epic=null
We also have an updated initiative timetable for briefing in new
projects to our team & key dates
here:https://docs.fedoraproject.org/en-US/cpe/time_tables/
*Note: Initiatives are large pieces of work that require a team of
people and weeks/months to complete. Please continue to open tickets
in the normal way for bugs, issues, etc.
Look out for our Q2 project achievements blog post coming soon!
### CPE Product Owner Office Hours
#### #fedora-meeting-1
* Weekly on Thursdays @ 1300 UTC on #fedora-meeting-1
* Next Meeting: 2020-07-09
#### #centos-meeting
* Every second Tuesday @ 1500 UTC on #centos-meeting
* Next Meeting: 2020-07-07
## Fedora Updates
### Data Centre Move
* We are now officially operating under reduced Fedora services until
est 28th July to facilitate the final shipment of hardware to the new
data centre.
* Please View project card on taiga for builder - staging - remaining
app bringup dates here
https://tree.taiga.io/project/amoloney1-cpe-team-projects/us/42?kanban-st...
* A list of affected services is available here
https://hackmd.io/hpYYJQRjQy-oHxUS7IonIA?view
* Details on what this move may mean for you can be found here
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedora...
* If an application is not working correctly at all, please check this
list https://hackmd.io/hpYYJQRjQy-oHxUS7IonIA?view before opening a
ticket to make sure its not listed as being moved. If it is being
moved, please wait a day or two, then try again.
* Similarly, please be patient when opening tickets for service issues
in general as we have now reached the critical point in this move and
all of our sys-admins and wider teams will be assisting in the
successful bringup of the reduced Fedora service and facilitation of
the final hardware shipment and move.
* Most recent update to devel-announce is here
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedora...
### AAA Replacement
* User agreements for both CentOS and Fedora accounts are nearly
complete. We will be able to test this in more detail once staging has
been reinstalled (est July 25th due to colo move)
* Fasjson now supports search feature
* App migreations work still ongoing
* Spam detection service is being investigated and scoped for Q3 work
* Please feel free to check out the team kanban board for more
information on the features the team are working on and have already
completed here https://github.com/orgs/fedora-infra/projects/6
### Mbbox
* Project Dashboard here https://github.com/fedora-infra/mbbox/projects/1
* Tasks completed in the project currently
* MBBox handover to CentOS Stream
* The only thing that remains is putting the operator in the
public operator registry which is pending Stream team feedback
* MBox shared CRD is done
* Deployment guide - https://mbbox-operator.readthedocs.io/en/latest/
* Blog post published - check it out here
https://communityblog.fedoraproject.org/mbbox-module-building-in-a-box/
### Gitforge
We are still discussing technical aspects of the project and these are
tracked here:
https://gitlab.com/gitlab-org/gitlab/-/issues/217350
Planning a date in late August for an AMA session with GitLab that
will be run through IRC for any questions the Fedora and CentOS
communities may have to ask direct.
We will keep you up to date with the developments as and when we have
information to share and thank you again for your patience.
## CentOS Updates
### CentOS
* New website went live (https://www.centos.org)
* A new AWS CDN setup for Stream composes
(https://composes.centos.org) is being worked on with a goal to have
the latest stream artifacts to be publicly available and at faster
speed than through normal mirror.centos.org cdn (and/or external
mirrors)
### Centos Other
* CentOS CI began onboarding Fedora CI, CoreOS CI and Fedora CoreOS as
tenants this week
* Work going well and stable!
### CentOS Stream
* RealTime for Stream is released!
* The team are also working on more module builds for Stream
As always, feedback is welcome, and we will continue to look at ways
to improve the delivery and readability of this weekly report.
Have a great week ahead!
Aoife
Source: https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view
3 years, 9 months
Introduce my self [futur member]
by seddik alaoui ismaili
Hello team
I am very pleased to write you this email, to let you know my motivation
and my situation.
- Name : alaoui ismaili seddik
- Time zone / country : GMT +2 / France
I will start with an introduction of my experiences and skills,
So I was a GNU/LINUX administrator for 2 years, the first year was with a
software editor (competitive intelligence), during this period I was able
to develop my skills on different subjects including system administration
(Centos os ), maintenance in operational condition, the implementation of
basic tools/services, scripting (python/bash), db (mysql), C compilation.
I also managed to develop the sense of sharing and collaborative work.
Also for the second job at the company (numberly) as administrator/devops,
I took care of the DNS platform (powerdns), automatic deployment of the
conf via ansible, mainly the industrialization of the IT. And then on
different projects, for example on the cloud (hosting dns on route_53
AWS), centreon, grafana, elk stack, also managing the resolution of
incidents raised from the production servers.
I was system operator at capgemini for 1 year and 9 months more precisely,
the production piloting for two linux/unix (AIX, HP-UX, REDHAT) and
Mainframe (MVS) spells.
Currently I am an IT consultant at orange (telecom operator), I work in an
application environment (tomcat), os linux (REDHAT), and my main missions
are, the maintenance of the ELK stack, system administration, installation
of application instances in automatic way (ansible), continuous deployment,
migration of code on GITLAB.
I'm always interested in the linux operating system because it's an
opportunity to be closer to the machine, with it we can understand how a
system works, and react in case of bugs, it also allows to have a support
through a community that contributes behind it. For this I will be happy to
contribute on projects/tasks related to GNU/LINUX system administration,
bug analysis.
I will be able to give my time to the community, about 10 hours a week.
I hope I wasn't too long on my presentation.
Kind regards
Seddik
3 years, 9 months
