On Tue, 2013-02-12 at 13:00 -0700, Kevin Fenzi wrote: > On Tue, 12 Feb 2013 19:42:56 +0100 > Pierre-Yves Chibon <pingou@xxxxxxxxxxxx> wrote: > > > Hi all, > > > > I am getting some pressure to move fedocal to production (which is > > pretty nice). > > > > So just to be sure the next steps should be: > > - roll out the 0.1.0 release > > - package it > > - it now has a setup.py so I hope that it'll be pretty simple > > - request for hosting/hw ? > > - create the adequate puppet module > > - which url? admin.fedoraproject.org/calendar ? > > Sounds reasonable. In addition: > > - What are the monitoring requirements? None specific, the standard package? > - Should we use caching/proxies for it? Caching might be nice, especially for the ical feed if lot of people subscribe to it/them. > - If it gets a lot of load, can we add more instances and load balance > them? Toshio said that should work for flask. I did not perform any tests though. > - Whats the db requirement? Postgres is fine. > > Do I miss anything? > > I think admin.fedoraproject.org/calendar or perhaps > apps.fedoraproject.org/calendar would be fine. hm, since it needs login shouldn't it be admin? > > Also, what's the traditional time-line to move from stg to prod? > > Mostly stg is so we can get puppet sorted out and find any issues with > proxying and caching and such. It can sometimes be pretty short if > there's no particular issues found. Cool! :) Thanks for the feedback, Pierre _______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
