disable networking in Copr by default
by Pavel Raiskup
Just to be more pedantic and probably bit more secure, what about making
networking in copr opt-in (at least for new projects)?
If build of my package used internet arbitrarily, I would be warned very
early..
Also, in Koji we also do not have networking, so we can faster teach
(future) Fedora packagers.
Thanks for considering,
Pavel
7 years, 4 months
Usability suggestions for Copr web interface
by Martin Cigorraga
Hi all,
First of all I want to say I'm really happy for having Copr, being an
Arch user for many, many years I got really used to the AUR (Arch User
Repository) so I can see Copr potential.
And speaking about that, I would like to make some suggestions to
improve the 'community' side of Copr as I believe from what I read the
technical side is already very well covered:
1. Copr needs a place where users and packager(s) can discuss stuff
about the packages and repositories, that could be achieved by simply
letting logged people to comment on each Copr repo page;
2. Likewise it would be nice to have a way to: a) contact the
packager(s)/maintainer(s), b) flag outdated packages, inform about any
errors found.
Having the chance for community to interact ultimately leads to
improved workflows and better quality projects; some folks will look
for guidance to create their first Copr repo, other people may want to
lend a hand and offer maintain a repo packed with the stuff they
usually use while others can just offer tips for improve things - or
ask for assistance as well!
Hope you guys take my suggestions in a positive way, I'm already happy
to have a great infrastructure like Copr already set and ready for
anyone to use, kudos!
-Martín
7 years, 11 months
changes in copr.fedoraproject.org
by Miroslav Suchý
Yesterday, we deployed a new version of Copr.
First we migrated to new Fedora Cloud instance, which give us more reliable infrastructure.
Previously we used 12 builders, but due problems with old OpenStack we were forced to lower it to 6 builders.
Today we are back to 12 builders and we are ready to increase the limit [1].
We are monitoring the new instance and we will very likely increase the number of builders to 20 soon. This should be
enough for some time.
Second change is reuse of VM. If builder finishes building of your package and there is in queue some other task from
you, then it is picked up and build on the same VM without re-provisioning of that VM. The logic is that you probably do
not want to do cracking of your own packages, so we can reuse that VM for yours packages. Packages are still build in
different chroot, but the same machine. Of course - if there is only packages of another users in the queue, then the
builder VM is terminated and clean one VM is spin up.
Last change is limitation of users. If you send dozens of task to Copr, then you are limited to just 4 parallel builds.
Other builders are used for other users next in queue.
Because we have more resources available. I recall that there we some use case where you requested more memory or disk.
However I could not find the details. If you have such use case, now is right time to contact me as I can increase the
limits if there is good reason.
Oh and I forgot that we have new storage for your repositories. Previously we had just 800 GB and we were reaching the
roof. On new location we have 4TB and it can be extended if needed.
And the conclusion? You should expect less delay. Not being blocked by other users.
And I can finally say, what I wanted to say for long time: Please use Copr more! You can even set up builds in Copr
after each commit in your project and Copr should handle that. Hopefully this will allow you to set up Continuous
Integration on your project, or make it even better.
[1] During testing of new cloud we tried to spawn enormous numbers of builders and it seems that number 200 is our hard
limit.
--
Miroslav Suchy, RHCA
Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys
8 years
Copr migration and outages
by Miroslav Suchý
Hi,
we plan to do migration of Copr today and tomorrow. So there may be some outages and the queue of builds may stop
processing. I kindly ask you with patience.
Detailed plan (may be subject to change):
1. Migrate Copr frontend today afternoon.
2. Migrate Copr backend and key signing machine tomorrow.
Those new machines will have different IP and all your data will be preserved.
We are migrating to new Fedora Cloud. Which will offer our more storage for your repositories. More compute power to
process more tasks in parallel.
If you see copr frontend webUI online during those two days, you can submit your task; it will be processed for sure. It
just may take some time.
--
Miroslav Suchy, RHCA
Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys
8 years
Idea: Rate Coprs
by Ralph Bean
For developers, copr is a good experience. You submit srpms and build
them nicely, you get repos, it's all very good.
For users, it is kind of a pile. You can search, but it is hard to
discover things.
It might be nice if copr had a 'rating' system where I could give this
copr 3 stars and that copr 5 stars. You could then have a page where
users could view coprs by popularity and find The Coolest Software.
8 years
Logo for Copr
by Klára Šimíčková
Hello,
I've tried to design a logo for the Copr project.
Since Copr sounds in Czech like "kopr" (dill), I've tried to use this in
logo, therefore I've used dill seed instead of "O".
I hope you will like it.
Have a nice day
Klara
8 years
New name for new service
by Miroslav Suchý
Hi,
we are working on new service [1], which will create docker image out of Copr repositories.
It will not be part of Copr itself, but of course is very tightly related to Copr.
We are looking for new name for this service.
Please submit your ideas here.
[1] if you are curious, it grows here
https://github.com/evilkost/cdic
--
Miroslav Suchy, RHCA
Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys
8 years
[PATCH] [frontend] Add optional fedmenu resources to every page.
by Ralph Bean
This is for https://fedoraproject.org/wiki/Fedora_Engineering/FY16_Plan
If the FEDMENU_URL and FEDMENU_DATA_URL options are left out of the
config, then nothing should change on the displayed page. If they are
included, then they will be pulled in at page load time to render little
menu buttons on the bottom right hand corner of the page.
There's an example up at http://threebean.org/fedmenu/
It will be a while until we are able to turn this on globally across all
our apps.
---
frontend/coprs_frontend/config/copr.conf | 4 ++++
frontend/coprs_frontend/coprs/__init__.py | 2 +-
frontend/coprs_frontend/coprs/context_processors.py | 11 +++++++++++
frontend/coprs_frontend/coprs/templates/layout.html | 16 ++++++++++++++++
4 files changed, 32 insertions(+), 1 deletion(-)
diff --git a/frontend/coprs_frontend/config/copr.conf b/frontend/coprs_frontend/config/copr.conf
index ab4fb96..064baa4 100644
--- a/frontend/coprs_frontend/config/copr.conf
+++ b/frontend/coprs_frontend/config/copr.conf
@@ -45,6 +45,10 @@ SEND_EMAILS = True
## post-process url leading to frontend
# ENFORCE_PROTOCOL_FOR_FRONTEND_URL = "https"
+# URLs for fedmenu resources
+#FEDMENU_URL = "http://threebean.org/fedmenu/"
+#FEDMENU_DATA_URL = "http://threebean.org/fedmenu/dev-data.js"
+
# Kerberos authentication configuration. Example configuration abbreviated
# like 'RH' (should not changed once used, reflects what is stored in database).
# This requires mod_auth_kerb package (Fedora/RHEL) installed on your frontend
diff --git a/frontend/coprs_frontend/coprs/__init__.py b/frontend/coprs_frontend/coprs/__init__.py
index e86bb64..032ed4d 100644
--- a/frontend/coprs_frontend/coprs/__init__.py
+++ b/frontend/coprs_frontend/coprs/__init__.py
@@ -52,7 +52,7 @@ from coprs.views import recent_ns
from coprs.views.recent_ns import recent_general
from coprs.views.stats_ns import stats_receiver
-from .context_processors import include_banner
+from .context_processors import include_banner, inject_fedmenu
setup_log()
diff --git a/frontend/coprs_frontend/coprs/context_processors.py b/frontend/coprs_frontend/coprs/context_processors.py
index b84c241..895bb03 100644
--- a/frontend/coprs_frontend/coprs/context_processors.py
+++ b/frontend/coprs_frontend/coprs/context_processors.py
@@ -10,3 +10,14 @@ def include_banner():
return {"copr_banner": open(BANNER_LOCATION).read()}
else:
return {}
+
+
+(a)app.context_processor
+def inject_fedmenu():
+ """ Inject fedmenu url if available. """
+ if 'FEDMENU_URL' in app.config:
+ return dict(
+ fedmenu_url=app.config['FEDMENU_URL'],
+ fedmenu_data_url=app.config['FEDMENU_DATA_URL'],
+ )
+ return dict()
diff --git a/frontend/coprs_frontend/coprs/templates/layout.html b/frontend/coprs_frontend/coprs/templates/layout.html
index bef3fbf..f9981e9 100644
--- a/frontend/coprs_frontend/coprs/templates/layout.html
+++ b/frontend/coprs_frontend/coprs/templates/layout.html
@@ -58,5 +58,21 @@
</small>
</p>
</div>
+
+{% if fedmenu_url is defined %}
+<script src="{{fedmenu_url}}/js/fedora-libravatar.js"></script>
+<script src="{{fedmenu_url}}/js/fedmenu.js"></script>
+<script>
+ fedmenu({
+ 'url': '{{fedmenu_data_url}}',
+ 'mimeType': 'application/javascript',
+ 'position': 'bottom-right',
+ {% if copr is defined %}
+ 'user': '{{copr.owner.name}}',
+ {% endif %}
+ });
+</script>
+{% endif %}
+
</body>
</html>
--
2.1.0
8 years
