On 02/08/2014 07:37 PM, Kevin Fenzi wrote:
On Sat, 08 Feb 2014 21:29:49 +1100
Graham Williamson <graham(a)williamsonsinc.id.au> wrote:
> I've created a ticket to add some missing web apps to apps.fp.o.
> The question (as discussed in irc just now) is should copr be added at
> this stage. So, does "wide beta" equate to production enough to make
> it onto apps.fp.o?
Nearly. :) more below
For me to think of it as production ready I'd like:
* nagios monitoring
This weekend I learned more about fedmsg from Ralph, so I want to create alerts based on
fedmsg (probably today or tomorrow)
* Our cloud more updated/stable.
Not sure about this. Yes, sometimes we run out of space in Cloud and it cause problems.
Not sure what to do with this.
Beside requesting money for more HW for next fiscal year, what I already done.
If you want to migrate it to apps.fp.o then I'm more then happy. But there are some
problems to resolve.
1) You can migrate copr-fe.cloud.fedoraproject.org
(that is that user-facing
). You can try to set
it up in apps.stg.fp.o. This one should be quite easy as it is just python (wsgi)
application with postgresql db. We
will see how it will work and I can then migrate data.
2) But we have copr-be.cloud.fedoraproject.org
. This one spin up VM from Fedora Cloud.
I'm not sure if you can do that
outside of Fedora Cloud. And it have attached storage with all builded rpms. It currently
have 800 GB with 60 GB
consumed. For those reason I have *no* idea how to migrate copr-be to apps.fp.o.
But from Copr POV it can be completly fine to have copr-fe in apps and copr-be in cloud.
Miroslav Suchy, RHCE, RHCDS
Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys