RFC: How to deal with account creation
by Stephen John Smoogen
Currently I am dealing with 1-3 failed account creations a day due to our
spam checking tool, basset.
Basset is the tool which sits in the account system creation path and tries
to check to see if an account is semi-valid or not. This was written by
Patrick Uiterwijk about 4 to 5 years ago to deal with a large increase of
spam accounts from a group who were paying people to get past other spam
tools versus using scripts. We came up with various heuristics and tools to
make for a general 'oh you are using a one-time-email system.. no account
for you' and other checks.
However it is almost a full time job to keep up with all the various spam
groups methods for creating fake accounts for whatever they want. I haven't
put much time into since 2018 and the heuristics that basset is using to
judge whether a person has a valid account or not are way out of date. The
spam groups have also gotten more sophisticated in creating accounts so we
are more likely to allow a spammer in than a 'ham'-mer.
I am not sure what to do.. I do not know how hard it would be to pull
basset out of the system and I do not have the time to update/fix/improve
Patrick's code on this. So I figured it would be good to get some feedback
on this.
--
Stephen J Smoogen.
3 years, 12 months
CPE Weekly: 2020-05-16
by Aoife Moloney
# CPE Weekly: 2020-05-16
---
title: CPE Weekly status email
tags: CPE Weekly, email
---
Background:
The Community Platform Engineering group is the Red Hat team combining
IT and release engineering from Fedora and CentOS.Check out our teams
info here https://docs.fedoraproject.org/en-US/cpe/
## GitForge Updates
I am going to try provide weekly updates here
https://fedoraproject.org/wiki/Git_forge_update, however this is
project is a huge undertaking and will not be achieved over the next
few months, so some weeks I may not have any new information to share
with you.
Currently our entire infra team are engaged in a datacentre move, and
then our team will be assisting in the F33 release so the rest of 2020
is pretty full to say the least!
This lengthy period of investigation is good though because it serves
as a great opportunity to explore every inch of this project
technically to ensure the best possible outcome from this change that
everyone benefits from. We as a team can actively engage in real time
with the community via the [ticket filed in
GitLab](https://gitlab.com/gitlab-org/gitlab/-/issues/217350) by
cverna for technical mapping and through my office hours on IRC @ 1300
UTC on #fedora-meeting-1 every Thursday for real conversation and
engagement with us. Its optional, but I really appreciate when people
can stop by and talk to me (and us) about this.
During these office hours I was reminded the Pagure community was owed
some insight on how Pagure was viewed during the process. This text
has been ported to a hackmd file from a google doc for readers who use
terminals, etc for easier reading and here is the link to the email
https://lists.pagure.io/archives/list/pagure-devel@lists.pagure.io/thread...
Thank you again for your continued engagement with us and your
patience over the coming months as we move slowly through all of the
technical aspects of this project.
### Current Projects We are Working on
The CPE team are using taiga.io for our projects backlog and to show
what projects we are currently working on.
Each team updates their project card with current information on their project.
If you want to see what we currently have in progress, and whats in
our backlog for our next quarter, feel free to check it out at:
https://tree.taiga.io/project/amoloney1-cpe-team-projects/kanban?epic=null
Its a work in progress and not perfect but we hope this is a good way
to get our initiatives out in the public in an easy to see manner.
### CFP Dates
* DevConf.US CFP open - https://www.devconf.info/us/
* CentOS Dojo @ DevConf.US CFP also open -
https://wiki.centos.org/Events/Dojo/DevconfUS2020
### Data Centre Move
* Communishift is unfortunately still offline until mid to end of June.
* Our primary focus is the bringup of the reduced Fedora offering that
is expected to be live from June 15th 2020 and will be in place until
estimated 28th July 2020.
* A recap of services you can expect to still have access to can be
found here https://hackmd.io/hpYYJQRjQy-oHxUS7IonIA?view
* Updates to impacted services are also being posted here
https://status.fedoraproject.org/
* Again, as this project is currently being run by a two man team, we
both appreciate and thank you for your patience for delayed replies to
tickets/requests/pings related to Fedora infra.
### AAA Replacement
* Recent changes include a few bugfixes, UI improvements, and a way
for users to programmatically request a certificate to be signed by
the IPA CA (CentOS packagers authenticate to their Koji instances with
certificates).
* Check out our new side-module Flask-Healthz if you have a Flask app
and you want to add the liveness and readiness checks in OpenShift. We
needed that so we made a reusable module that all our Flask apps
should be able to use should they need to. It’s on PyPI already, and
very simple to use.
### Sustaining Team
* We have Pull Requests for the ansible repo :-) and it works great.
Changes are verified with ansible-review by our Zuul CI.
* Bodhi 5.3 released, looking to deploy it next week in prod (rebuild
bodhi-backend01 to Fedora 32)
* Sigul is buildable now, the last time it was built is on F29.
* Improvement to our Ticket Dashboard, we are in a good place to start using it.
https://fedora-infra.github.io/tbs/
* Next few weeks will be focusing helping with Colo move (deployment
of apps in the IAD2)so some of our team members will be unavailable
for support
## Mbbox
Our Issue tracker dashboard is here
https://github.com/fedora-infra/mbbox/projects/1
* This weeks work included:
* Identity container image for testing
* Set up ReadTheDocs documentation
* Koji-builder CRD - still some issues connecting to koji-hub, but
most of the work on koji-builder is done
* Koji-hub CRD documentation
* Koji-builder MBOX automatic image build on quay.io -this is only
the image we provide as part of mbox, the koji doesn’t provide any
## CentOS Updates
### CentOS CI
* Configured dns/dhcp for the new ocp4 ocp.ci.centos.org cluster
* Provisioned 2 haproxy load balancers
* Provisioned the bootstrap, master and worker ocp4 nodes
* Have the basic openshift 4 cluster up and running internally for
testing/configuration
### CentOS
* CentOS Linux 8.2.2004 is ongoing with QA
* We have most GA content tagged for the upcoming release
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/NB88XG9fQpKwPLoHzF1FqQ?view
--
Aoife Moloney
Product Owner
Community Platform Engineering Team
Red Hat EMEA
Communications House
Cork Road
Waterford
3 years, 12 months
CPE Weekly: 2020-05-11
by Aoife Moloney
# CPE Weekly: 2020-05-11
---
title: CPE Weekly status email
tags: CPE Weekly, email
---
Background:
The Community Platform Engineering group is the Red Hat team combining
IT and release engineering from Fedora and CentOS.Check out our teams
info here https://docs.fedoraproject.org/en-US/cpe/
## GitForge Updates
* We are tracking our progress here (nothing new added yet, fyi)
https://fedoraproject.org/wiki/Git_forge_update
* And the council are tracking the community issues in this ticket
https://pagure.io/Fedora-Council/tickets/issue/292
* I have an Office hours IRC meeting slot on #fedora-meeting-1 @
1400-1500 UTC every Thursday. Feel free to stop by and say hi! We can
talk about Gitforge, or not :)
### Data Centre Move
* Communishift is unfortunately offline until mid to end of June. The
guys hit some unfortunate roadblocks which cost us a lot of time and
energy. As we are starting to bring up hardware in IAD2 for the
reduced Fedora offering next week, the hard but necessary decision was
taken to pause bringing up CommuniShift in RDU-CC for now and come
back to this once the *slightly* more critical work is done or close
to complete in IAD2.
* Thank you for your patience, this is a colossal undertaking for the
team and your support and understanding is very much appreciated.
* Full amended schedule is here https://hackmd.io/vDwoayVLQ8yjyDk3PDvC8A?view
* And updates are being posted here https://status.fedoraproject.org/
* Again, as this project is currently being run by a two man team, we
appreicateand thank you for your patience for delayed replies to
tickets/requests/pings related to Fedora infra.
### AAA Replacement
* The team have met with openSUSE and are supporting them when deploying Noggin
* Noggin UI improvements based on feedback have also been implemented
* Teh team will begin to work on upstream code changes of existing
apps to the FASjson api in their next sprint
* You can view the teams current, completed and backlog work here
https://github.com/orgs/fedora-infra/projects/6
### Sustaining Team
* The team are using this dashboard to track their work
https://github.com/fedora-infra/mbbox/projects/1
* They are also supportg the ELN work
* The ansible repo has also been moved to pagure!
https://pagure.io/fedora-infra/ansible
* Mbbox Upgrade
* ssl fix is done
* The team are also working on CRD for koji-builder
* Work is being tracked here if you wish to view in more detail
https://github.com/fedora-infra/mbbox/projects/1
## CentOS Updates
### CentOS CI
* The team are working on
* Improving monitoring on CI agents
* Manual install of RHCOS bootstrap node on bare metal
* Importing EL6 Image for CICO cloud
* VMs migration from OpenStack to OpenNebula
### CentOS
* CentOS 7.8.2003 was released for x86_64, aarch64,ppc64, ppc64le and
armhfp architectures. Including Cloud images (on
https://cloud.centos.org) -
https://blog.centos.org/2020/04/release-centos last week
* CentOS Linux 8.2 work is ongoing with compose level testing due to start soon
### CentOS Stream
* The team are working through debranding CentOS Stream content from
CentOS Linux
* Using CentOS Stream in the CentOS QA group to prep for 8.2
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
--
Aoife Moloney
Product Owner
Community Platform Engineering Team
Red Hat EMEA
Communications House
Cork Road
Waterford
4 years
Re: id.fedoraproject.org available when?
by Radka Gustavsson
On Fri, May 1, 2020 at 11:39 PM Radka Gustavsson <
radka.gustavsson(a)redhat.com> wrote:
> Hi all,
>
> as the subject suggests, we've been waiting for id.fedoraproject.org for
> reaaaaally long time now and we can't get any info on the status. And even
> the stage was ... shut down? It simply stopped working (certificate poof'd,
> scopes poof'd, ...)
>
> Please advise how to proceed - what's the status, is there anything we can
> do to help?
>
> Related: https://pagure.io/fedora-infrastructure/issue/8040
>
> Thank you,
> Radka
>
> ------------------------------
> *Radka Gustavsson - Janeková (she/her)*
> .NET Core QE Lead, Red Hat
> *radka.gustavsson(a)redhat.com <radka.gustavsson(a)redhat.com>*
> IRC: radka | Freenode: Rhea
>
4 years
CPE Weekly: 2020-05-02
by Aoife Moloney
# CPE Weekly: 2020-05-02
---
title: CPE Weekly status email
tags: CPE Weekly, email
---
Background:
The Community Platform Engineering group is the Red Hat team combining
IT and release engineering from Fedora and CentOS.Check out our teams
info here https://docs.fedoraproject.org/en-US/cpe/
## GitForge Updates
* We are tracking our progress here (nothing new added yet, fyi)
https://fedoraproject.org/wiki/Git_forge_update
* We are still doing a technical deep-dive with our own team on what
we need from GitLab and will have a technical plan developed and
publically available in the coming weeks - thanks again for your
patience, this will take some time to map out.
* Fedora have also released a blog post
https://communityblog.fedoraproject.org/fedora-council-and-the-git-forge/and
* And the council are tracking the community issues in this ticket
https://pagure.io/Fedora-Council/tickets/issue/292
* We are looking at ways to engage closer with the community too so I
will have an *optional* office hours slot on #fedora-meeting @
1400-1500 UTC every Thursday. Feel free to stop by and say hi! We can
talk about Gitforge, or not :)
## Releases!!
* F32 released! Congrats to all those who helped make this such an
awesome release :)
* Lenovo are releasing Fedora as a standard desktop offering!
* CentOS 7.8.2003 was released for x86_64, aarch64,ppc64, ppc64le and
armhfp architectures, including Cloud images (on
https://cloud.centos.org)!
### Data Centre Move
* Communishift is still out, est back online 11th May.
* Full amended schedule will be published week ending 8th May to
hackmd & will be sent to the devel & infra lists.
* Connectivity is now in place in IAD2 and should be in place in
RDU-CC over the weekend.
* In particular, a HUGE shout out to Stephen Smoogen who has been
working all the hours in every day for the last few weeks/months to
get this phase of the move operatoinal for the Fedora infrastructure -
we would not be able to do this without you Smooge :)
* This is literally a two man team of Kevin Fenzi and Stephen Smoogen,
who are carrying the weight of this infrastructure on their shoulders
and are invaluable to the success of this multi-team and multi-month
project, so thank you both.
* Given the pressures on the Infra folks, a general ask for patience
if your ticket / request / ping takes a little bit longer to reply to
### AAA Replacement
* The team will work with openSUSE to deploy FreeIPA + Noggin to
deploy it in their infra before we do!
* This is really exciting and the team are looking forward to seeing
how the solution works in another infrastructure!
* You can view the teams current, completed and backlog work here
https://github.com/orgs/fedora-infra/projects/6
### Sustaining Team
* The team are using this dashboard to track their work
https://github.com/fedora-infra/mbbox/projects/1
* Mbbox Upgrade
* Zuul CI set up is done
* Koji-hub TLS support added to CR
* Set up ReadTheDocs documentation - webhook missing for automatic build
* Identity container for testing
* Koji-builder CRD PR rebase - SSL authentication with koji-hub
* Refactor molecule test suite to share tests
## CentOS Updates
### CentOS CI
* OpenShift upgrade
* OpenStack to OpenNebula migration scripts
* Ansible playbooks to manage the creation and bootstrapping of
bare metal nodes with RHCOS
* Packaging work (fixing dependencies)
* Updated ci-user list on efforts we are putting for CI Infrastructure
### CentOS
* CentOS 7.8.2003 was released for x86_64, aarch64,ppc64, ppc64le and
armhfp architectures. Including Cloud images (on
https://cloud.centos.org) -
https://blog.centos.org/2020/04/release-centos-linux-7-2003/
### CentOS Stream
* Congratulations to Brian Stinson on his excellent session of Ask The
Expert, facilitated by Rich Bowen during Red Hat Summit - we hope you
caught it, it was really good!
* Using CentOS Stream in the CentOS QA group to prep for 8.2
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
--
Aoife Moloney
Product Owner
Community Platform Engineering Team
Red Hat EMEA
Communications House
Cork Road
Waterford
4 years
Meeting Agenda Item: Introduction Adwait Thattey
by Coder Dude
Hello,
I am Adwait Thattey.
I am a student in the 3rd Year of Indian Institute of Information
Technology.
I contributed to a few Fedora projects in the last month and I thoroughly
enjoyed working on them.
I joined this list so that I can explore more projects and issues.
The languages I work with the most are Python, Golang, and Bash.
I have worked with Docker and Kubernetes and currently learning Ansible.
I like working in Linux a lot and hope to work in DevOps or administration
after my graduation.
I am currently exploring the issues in fedora-infrastructure to see if I
can work on something.
My IRC handle is @coderdude and email is coderdude1999(a)gmail.com
Thank You
4 years
