I wrote  to devel some time ago regarding the deprecation of the apps.fp.o
index and plan to move its content to the main docs. Kevin mentionned that it
could end up in the infrastructure docs and that the whole should be moved to
docs.fp.o at some point. I will take a look at both since I have wanted to play
with the new documentation pipeline for a while. I am not the best guy to
meddle with the infrastructure doc but I might as well do something useful
while playing with antora. Tell me if it's not or if I missed something.
I might have something to show you at Flock if I have troubles sleeping in the
See you in Budapest,
On 2019-11-26 fedora 29 will go end of life and no longer supported.
We still have a number of things that are f29 (or older for various
reasons). I'd like everyone to look this over and see if you can't move
things to f31 (or at least f30) before the f29 eol.
builders: I am working on this, builders right now are mostly f29, but
should be all moved before the eol date I hope.
modernpaste: fedora-27. :) But I don't think it was ever moved to
openshift, so we should delete this.
joystick: we should fix this up, I think jdoss was going to take it
the-new-hotness: can we move to f31?
qa-stg01.qa.fedoraproject.org: f24? can we retire?
autocloud*: f27, but should die when f29 goes eol (it's only used to
mdadpi: f27, but it moved to openshift, can we clean up the non
openshift instances and files please?
modernpaste: f27. It goes eol soon, so I guess we just wait
notifs-backend: f27. I don't know what to do here. We need a
replacement, which we don't have. I'm afraid that upgrading will blow it
up, but I guess we could try and rollback?
qa-prod01: f27. can we retire?
ci-cc-rdu01: f28. Can we retire soon?
copr-frontend01/02.stg: f28 and I don't think we need them anymore, can
I nuke them?
db-qa03: f28. Can we upgrade please?
osbs: f28, but I think cverna was moving it to newer? any status?
aarch64-test01/02 - can be redone as f31 anytime
composer.stg - should be moved to f31
db-koji01.stg - should be moved to f31 and a prod->stg sync
kojipkgs01/02 - I should do these soon to f31, adding to my list.
os-proxy01 - I should do this one, on my list
packages03/04 - No idea here. Can we upgrade?
proxy* - we need to start working on this asap.
relepel01 - do we need this one anymore?
resultsdb/taskotron - can qa folks upgrade these?
old cloud instances:
glittergallery-dev: f23, should be nuked
fedora-bootstrap: f25, should be nuked
waiverdb-dev: f25, still needed?
commops: f27, still needed?
telegram-irc: ? still needed?
copr*stg: f28, can copr folks upgrade?
developer: f28, still needed?
libravatar: f28, should ask them to move to communishift
simple-koji-ci: f29. Can we upgrade to 31? or move it to communishift?
I think thats all of them.
On Mon, Apr 29, 2019 at 4:47 PM Kamil Paral <kparal(a)redhat.com> wrote:
> On Mon, Apr 29, 2019 at 11:39 AM Sinny Kumari <ksinny(a)gmail.com> wrote:
>> On Wed, Apr 24, 2019 at 12:19 AM Kevin Fenzi <kevin(a)scrye.com> wrote:
>>> Or could we move f29+ all to whatever is replacing it? (taskotron?)
>> It will be nice but I am not aware of any other system in place which
>> replace checks performed by autocloud.
>> (CC'ed tflink and kparal)
>> Does taskotron provides capability to perform tests on Fedora cloud
>> Images like booting images and other basic checks?
> Theoretically it is possible using nested virt. However, Taskotron is
> going away as well. The replacement is Fedora CI:
Thanks kamil! yeah, it doesn't make sense to move to Taskotron if it is
going to be deprecated as well.
> I recommend to ask in the CI list:
> It should be possible for them to provide the infrastructure you need.
Hmm, I am not very sure if we should spend time investigating and setting
to autocloud unless we have usecases for long run. Fedora Atomic Host Two
Week releases ends with F29 EOL.
Welcome to the CPE team weekly project update mail!
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
For better communication, we will be giving weekly reports to the
CentOS and Fedora communities about the general tasks and work being
done. Also for better communication between our groups we have
created #redhat-cpe on Freenode IRC! Please feel free to catch us
there, a mail has landed on both the CentOS and Fedora devel lists
with context here.
This document is currently built from individual reports rolled into a
google document which we edit and copy into a final document. We are
aware that this causes problems with some email readers, and are
working on a method to make this less problematic.
High Level Project Updates:
Bodhi was 5.1 released and is deployed in staging
Robosignatory is broken in staging preventing testing much there
Elections being moved to Communishift really soon! Stay tuned!
Still no progress on kanban board last four weeks
Jlanda is still hitting permission error in communishift
Still working on running local instance
Benson Muite is now working on OIDC authentication
A PR will be created on Github to test if we can see the progress
New PR from sebwoj - Porting to Fedora messaging is under review
Still on track for December 1 modernpaste shutdown
GDPR and privacy centric conversations with respect to application
handovers have resulted in…..more conversations needed - shock :)
The team have been testing projects migration from repospanner to
locally hosted git repositores on git.dev.centos.org and come back
with a migration script/plan to unblock RCM
Scoping meetings are still ongoing
Bugzilla sync script has been resolved
Email inviting to review its change has been sent
New changes to src.fedoraproject.org deployed:
Ability to set the anitya monitoring status directly in the UI
Ability to adopt orphan (and not retired) packages directly in the UI
New changes to Pagure on the horizon:
New API endpoint to enable/disable git hooks
Ability to set dist-git in the default assignee overrides for bugzilla
EPEL 8 modularity
Updates can now be created in bodhi staging!
We are currently testing pushes/composes
We are also testing epel8-playground-modules composes
Aarch64 is now racked and networked
New koji owner script was debugged
Koji client was updated
Koji was also patched for the --title option fix
Configured migrations from Ansible/Jinja template
Various Resolved Issues
Comments? Suggestions? Feedback? Let Us Know!
Have a great weekend!
Community Platform Engineering Team
Red Hat EMEA
My name is Daren. I am a full time web applications developer and a
computer science student in my junior year. I have dabbled in python for
about 2 years now and really enjoy it. I am a new fedora OS user and was
looking for some ways that I could contribute.
You are kindly invited to the meeting:
Fedora Infrastructure on 2019-11-28 from 15:00:00 to 16:00:00 UTC
The meeting will be about:
Weekly Fedora Infrastructure meeting. See infrastructure list for agenda a day before.
$ kinit mufti11(a)FEDORAPROJECT.ORG
Password for mufti11(a)FEDORAPROJECT.ORG:
$ fedpkg clone vcglib
Cloning into 'vcglib'...
No such repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Could not execute clone: Failed to execute command.
i had no success.
Is something wrong ?
Just a quick heads up (I am not really here today/this week):
Last week the tpm module in autosign01 failed. robosignatory normally
binds to a tpm so if any keys/files were copied off to somewhere else,
they would be useless, because they require that exact machines tpm to
Thanks to Patrick from the iot team, things are back and working, but in
a degraded state. Basically currently robosign is requiring passphrases
be manually input by an admin on any restart (and then keeping that
information in the kernel keyring).
I'm out this week, Patrick is also out for a while, so I would urge us
to not make autosign mods right now. As soon as we are back, we can
evaluate if getting the tpm replaced is the way to go or other measues.