Enable signing on f30-signing-pending tag
by Mohan Boddu
This will enable signing on f30-signing-pending tag and once signed the
updates will be pushed to f30-updates-testing-pending tag
diff --git a/roles/robosignatory/files/robosignatory.production.py
b/roles/robosignatory/files/robosignat
index 32004e9..1de4b90 100644
--- a/roles/robosignatory/files/robosignatory.production.py
+++ b/roles/robosignatory/files/robosignatory.production.py
@@ -139,6 +139,12 @@ config = {
"keyid": "cfc659b9"
},
{
+ "from": "f30-signing-pending",
+ "to": "f30-updates-testing-pending",
+ "key": "fedora-30",
+ "keyid": "cfc659b9"
+ },
+ {
"from": "f30-modular-signing-pending",
"to": "f30-modular",
"key": "fedora-30",
5 years, 1 month
[Freeze Break Request: ] pagure.io: Increase upload size from 60MB to 100MB for virt-viewer
by kevin@scrye.com
From: Kevin Fenzi <kevin(a)scrye.com>
See ticket https://pagure.io/fedora-infrastructure/issue/7612
virt-viewer folks need to upload larger than 60MB content.
Signed-off-by: Kevin Fenzi <kevin(a)scrye.com>
---
roles/pagure/frontend/templates/pagure.cfg | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/roles/pagure/frontend/templates/pagure.cfg b/roles/pagure/frontend/templates/pagure.cfg
index 9c3eb4b..9c85d52 100644
--- a/roles/pagure/frontend/templates/pagure.cfg
+++ b/roles/pagure/frontend/templates/pagure.cfg
@@ -158,7 +158,7 @@ ITEM_PER_PAGE = 50
### Maximum size of the uploaded content
# Used to limit the size of file attached to a ticket for example
-MAX_CONTENT_LENGTH = 60 * 1024 * 1024 # 60 megabytes
+MAX_CONTENT_LENGTH = 100 * 1024 * 1024 # 100 megabytes
### Lenght for short commits ids or file hex
SHORT_LENGTH = 7
--
1.8.3.1
5 years, 1 month
cloud retirement
by Kevin Fenzi
Hey everyone.
As you know, we currently have a RHOSP5 ancient cloud. After a bunch of
work last year, we got a RHOSP13 cloud up and mostly working, but it was
a ton of work. After hearing from the Fedora Council and our various
management chains we determined that it wouldn't really be a good use of
our time moving forward to keep maintaining a OpenStack cloud.
We have not yet determined what we want to do with the hardware that we
had allocated to this, but are weighing our options. We may want to
setup OpenShift bare nodes so we can do kubevirt, we may want to just
setup a normal virthost setup managed by ansible.
For the items currently in our cloud, we will be looking at options for
them, we are definitely not shutting things off until we have plans in
place.
Happy to answer any questions and will make sure everything is properly
migrated.
kevin
5 years, 1 month
Migrating bugzilla2fedmsg to OpenShift
by Aurelien Bompard
Hey folks,
I'm migrating bugzilla2fedmsg to Fedora Messaging, and I thought it'd
be a good opportunity to migrate it to OpenShift also.
It only requires a connection to the STOMP brokers[0] on port 61612.
Is this available from inside OpenShift?
[0] messaging-devops-broker0{1,2}.web.prod.ext.phx2.redhat.com in the
prod environment, s/prod/stage/ for the staging environment
Any other reason you'd think it's a bad idea?
Aurélien
5 years, 1 month