FBR
by Stephen John Smoogen
Need to fix opendkim on bastion
I merged a fix in https://pagure.io/fedora-infrastructure/issue/9250 but
have not run the playbook for bastion to push this out yet. I would like to
get a +1 or -1 on this before doing that. [I can remove the merge also if
that is better.]
--
Stephen J Smoogen.
3 years, 7 months
FBR: increase koji ram to 32 GB
by Stephen John Smoogen
Currently koji01 and koji02 are using 16 GB and need 32 GB . Bump each
guest in ansible and via virsh commands.
--
Stephen J Smoogen.
3 years, 7 months
What is our technical debt?
by Pierre-Yves Chibon
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?
Looking forward to your thoughts,
Pierre
3 years, 7 months
CPE Weekly: 2020-09-20
by Aoife Moloney
Hi Everyone,
Below is this week's CPE weekly for week ending 2020-09-20.
I found that if you want to skip to the hackmd, you can use the view
link https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view and then use the
header bar on your left to skip to either the Fedora or CentOS
updates, whichever interest you.
I'll also be adjusting these updates in the coming weeks to make them
a bit more direct to consume. Thanks for giving me this feedback in
the CPE survey, I want to deliver value to you all, so it's great to
KNOW what you find valuable first hand :)
# CPE Weekly: 2020-08-14
## General Project Updates
As a reminder, below are the projects the CPE team are working on for
the months of July, August & September:
* Data Centre Move - Final Works
* CentOS Stream Phase 3
* Noggin Phase 3
* Packager Workflow Healthcare
* Fedora Messaging Schemas
We have recently held our Q4 planning session and the CPE review team,
Fedora, CentOS and RHEL BU have voted the following projects for
action in Q4, which is the months of October November & December:
* OSBS for aarch64
* Fedora-messaging schemas
We are continuing to work on CentOS Stream and Noggin and took these
projects as confirmed when looking at what other work our team could
realistically complete in the Q4 period, given that there's both
Thanksgiving and Christmas time off to consider, plus any time off our
team wishes to take.
The taiga cards of Noggin, CentOS Stream, OSBS for aarch64 and
fedora-messaging schemas will be updated next week with what our team
hopes to deliver in the next quarter on each of the projects.
Our project board is here (it's just not updated properly - yet)
https://tree.taiga.io/project/amoloney1-cpe-team-projects/kanban?epic=null
### Misc
#### GitLab
Thank you so much to everyone for adding your questions to the doc for
the GitLab AMA session on Thursday 10th September, and for your
attendance on the day during the call.
Here is the full AMA transcript
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-09-10/ama_session...
however it is a bit confusing to read so we got a few great
suggestions to have dedicted topics like Message Bus and Branching,
etc go out to the devel lists to discuss. I'm happy to start this next
week, but I will collect the questions related to each topic and
propose a cadence to send them out first to discuss, so people dont
miss mails and know the week ending 2nd October will be (for example)
the topic of Group Permissions - What do you think?
GitLab have also agreed to answer the questions, we have asked them to
do so within 2 weeks of the AMA so as soon as this is complete I will
let you know so you can read through them on the hackmd link.
The link is here where we asked you to contribute your questions and I
will be posting answers once we have them underneath
https://hackmd.io/RW8HahOeR7OJPON1dwuo3w
I really appreciate your involvement with this as we begin to dig
deeper into how this might play out next year and what way it should
for everyone's benefit.
## Project Updates
*The below updates are pulled directly from our CPE team call we have
every week.*
## Fedora
### General
* 6 of 8 Beta-blockers have fixes for F33 beta
* New release of fedscm_admin
* FMW mac and windows binaries are signed
### Staging Environment
* About 70% done installing vm’s (27 left out of 88)
* Still need to bring up aarch64/armv7/ppc64le builders
* Databases need syncing
### AAA Replacement
* The team are working on testing Ipsilon in Staging and adding OpenID
Connect Capability
* they are also testing fas2ipa migration script in tiny-stage and improve it
* Add Noggin to tiny-stage environment and test
* The teams kanban board where they track their work can be found here
https://github.com/orgs/fedora-infra/projects/6
### Fedora Messaging Schemas
* This project is on hold until Noggin completes.
* It will be resumed around December timeframe and is part of our Q4
workload to complete
* There is a list of applications that require messaging schemas can
be found here https://hackmd.io/@nilsph/H1i8CAbkP/edit
* There is a readme which contains documentation on messaging schemas,
a cookie-cutter template to create the schema and a definition of Done
for writing a schemas
https://github.com/fedora-infra/fedora-messaging-schemas-issues
* The board they are working from can be viewed here
https://github.com/orgs/fedora-infra/projects/7
### Packager Workflow Healthcare
* The team have been working on more improvements and fixes to the
monitor-gating
* These improvements have led to
* Finding a bug in our testing script
* Improved log messages
* We actually caught a problem! :)
* The data the team have been reviewing have been from April - July
and have already discovered that so far it looks like Pagure, koji and
bodhi work well
* We see some intermittent problems, but nothing too big, mostly
only spikes in runtime
* Fedora CI still looks like a POC, but functional
* Our test-script hitting timeouts/failing 10% of the time
* Gating (greenwave/resultsdb/waiverdb) looks functional, but
relies on CI and doesn't have as much packages going through the
workflow
* A more formal report will be published soon as part of the project
deliverable so keep an eye on their work!
* The teams work is being tracked here
https://teams.fedoraproject.org/project/cpe-cicd/kanban
## CentOS Updates
### CentOS
* Deployed new 4.5.9 openshift cluster for Stream
* The team provisioned EC2 infra for team responsible for
registry.centos.org (we don’t maintain it, so just providing infra,
like Fedora does for Copr)
* They also migrated a bunch of nodes to the new Ansible CI inventory
### CentOS Stream
* Using Openshift cluster for engineering work and will be using it to
deploy & test mbbox in our infra
* Scoping and refining work for October November & December
## Team Info
### Changes to CPE Product Owner Office Hours
Following the feedback received in the CPE survey, I will be reducing
my IRC office hours to once per month.
#### #fedora-meeting-1
* Next Meeting: 2020-10-15 @ 1300 UTC on #fedora-meeting-1
#### #centos-meeting
* Next Meeting: 2020-10-13 @ 1500 UTC on #centos-meeting
## Background:
The Community Platform Engineering group, or CPE for short, 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/
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!
Aoife
Source: https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view
--
Aoife Moloney
Product Owner
Community Platform Engineering Team
Red Hat EMEA
Communications House
Cork Road
Waterford
3 years, 7 months
[Mentored Project Proposition] Unintrusive Synchronized Authorship Web
Application
by Akashdeep Dhar
Hi folks,
TL; DR.
Akashdeep/t0xic0der here. I would love to hear what you think about a project that I am proposing for Fedora's representation in this year's Google Summer of Code. I have built a functional prototype of
the project (which you would find [here](https://github.com/t0xic0der/syngrafias/), the documentation [here](https://github.com/t0xic0der/syngrafias/wiki/Usage) and the screenshots [here](https://github.com/t0xic0der/syngrafias/wiki/Screenshots)) so you would able to know what the project can potentially provide. You can find the project proposition [here](https://pagure.io/mentored-projects/issue/85). As this project pertains to facilitate convenient documentation creation as a service specifically, it is vital for me to know what you think about the project and the feasibility of implementation of this service on our infrastructure should it get selected and worked upon.
IWRTLV. (I wanna read the long version :P)
Take a look at the following excerpt which was taken from the proposition I wrote (Check issue https://pagure.io/mentored-projects/issue/85 of mentored-projects for the entire content and the conversation regarding it).
<EXCERPT START>
- There has been this web application I have been building a functional prototype for, which allows for synchronized authorship of documents in an unintrusive manner. The project is called Syngrafias.
- To explain this in a better way, people who have used Google Docs for editing documents collaboratively know how the changes made to the document are actively synchronized to all the collaborators during the time of editing. Syngrafias does that but with a much more distributive approach to it - as here the changes made in the document in the absence of the other user would not be synchronized, thereby seamlessly creating (say) a fork of the same document. ([See the attached image collabnt.png](https://raw.githubusercontent.com/t0xic0der/syngrafias/mast...)
- The unintrusiveness in the document editing can be better explained if I draw parallelism with Jupyterlab. Just like in Jupyterlab, we have distinctive cells here for editing text. It is a simple mechanism but with much greater functionality as it allows you to selectively share the parts of the document you want collaborators to edit and rearrange the parts of the document by simply using a drag-n-drop operation. I have added in Summernote for WYSIWYG editing for each cell. ([See the attached image opendocs.png](https://raw.githubusercontent.com/t0xic0der/syngrafias/mast...)
- Of course, there is activity tracking so any change in the document title, cell title or cell content gets logged and activities like cell creation and removal are synchronized across all connected clients. The way I see it, this project can bring about radical positive changes to the way Fedora's project documentation are worked upon collaboratively. Also, if I simply replace Summernote with CodeMirror - this can even be used for collaboratively editing code snippets on-the-go. ([See the attached image activlog.png](https://raw.githubusercontent.com/t0xic0der/syngrafias/mast...)
- With 57 commits as of the time of writing the idea description, the project is only getting started and only the bare functionalities of the project are complete. You can find the repository [here](https://github.com/t0xic0der/syngrafias), the usage instructions [here](https://github.com/t0xic0der/syngrafias/wiki/Usage) and the screenshots [here](https://github.com/t0xic0der/syngrafias/wiki/Screenshots). There are tons that we can expand upon if this ends up becoming a project for GSoC. I would very much love for you folks to try out the project, let know what you think about it and your valuable suggestions for it to become a GSoC project - if it can. I would be obliged.
<EXCERPT END>
The reason why I wish to propose this (outside) project for Fedora's GSoC representation is because it has the potential to be a project assisting the distro/community (e.g. Bodhi and Mote) by making the process of documentation creation much more efficient and conveniently collaborative (as compared to the Pagure and Antora-bound method that we use right now). Do note that the project (I believe) aims to complement the tried-and-tested systems in place as of now with the features it has (and plans to have).
The way I see it - the project I am proposing here can complement to Antora's functioning by cutting down on the mandated build times to generate a preview (as we have a WYSIWYG feature) and deferred collaboration (highly subjective though as active synchronization would mostly benefit only those who are living at the same timezone and decide to work together for the same time). I cannot emphasize enough how beneficial it can be to try out the project prototype to understand how capable the project can be. You can find the [project page](https://github.com/t0xic0der/syngrafias) and the [project wiki](https://github.com/t0xic0der/syngrafias/wiki) links here. (or drop a response expressing willingness for a demonstration and maybe, we can schedule a video meet ;-))
As the proposed project marks a departure from the kinds of project that were used to be proposed for GSoC, it would be vital for me to know what you think about the proposed idea and the likeliness of adoption of the ideas stated in the project. How effective do you think it can be (if it can be selected as a GSoC project) and what can be done to make it better?
As questions concerning the infra team, some basic information on the project architecture are as follows :
- Programming languages used - Python 3, JavaScript
- Frameworks and technologies used - Flask, Jinja, Click, Websockets, Asynchronous programming
- Tested load (automated load of 500 concurrent users typing "Lorem Ipsum" on the same document) - 115MB memory utilization (DDR4-2400, Upto 8-10% of CPU usage (i5-7300HQ)
How feasible would it be to implement this as a service for the Fedora infrastructure (if it gets selected that is) and what nuances do we consider for so?
Thanks in advance. Looking forward to your responses.
Yours faithfully,
Akashdeep Dhar
3 years, 7 months
Fedora's participation in Hacktoberfest
by Vipul Siddharth
Hello all,
October is almost here and it's a chance for us to participate in
another outreach program.
"Hacktoberfest is a month-long celebration of open source software run
by DigitalOcean in partnership with GitHub and Twilio. Hacktoberfest
is open to everyone in our global community!"
A lot of new comers use this opportunity to open PRs to projects with
issues labeled 'Hacktoberfest'. It can be useful especially for
easy-fixes.
I just wanted to start this thread to see if anyone has any specific
opinion on this.
Other than the possibliity of getting spammy PRs, it's a good
opportunity to get some traction to our projects. What do you think?
--
Vipul Siddharth
He/His/Him
Fedora | CentOS CI Infrastructure Team
3 years, 7 months
){kind=link}
){kind=link}
){kind=link}