On Wed, 17 Aug 2011 13:01:42 -0600 Stephen John Smoogen smooge@gmail.com wrote:
On Wed, Aug 17, 2011 at 12:24, seth vidal skvidal@fedoraproject.org wrote:
On Mon, 2011-08-08 at 10:54 -0600, Kevin Fenzi wrote:
Greetings.
I thought I would throw out some plans for hosted moving forward and see if we could hash out a plan and some timetable for implementing things.
Some things we talked about:
- A caching frontend of some kind. Could cache web requests and
take load off the main machines.
- Some way to distribute the data, so if serverbeach were off line
we could still switch to and use another machine.
- Adding more/different services.
IRC commit bot redmine (still not in fedora, but people are working on it) your idea here.
We talked a bit about this yesterday and I wanted to write it up here:
- move the mailman instance over to collab1 and have them share an
infrastructure - mailman is not (usually) easy to spread to lots of servers in a very clean way and it is not (usually) the source of a massive load (the archiver not withstanding)
- I think we should seriously consider building things for hosted
2.0 such that slices are possible:
you still go to fedorahosted.org/projectname
but it redirects you to project-##.fedorahosted.org - based on the first 2 letters of the name of your project or what not.
Just an idea to bring up when we implement:
Due to the fact that we would have huge groupings on certain letters ( re, fe, li py, sy) use the first 2 letters of the md5sum of the name. Hopefully that would spread out the load across enough. The project build script would automate this so people don't have to figure it out.
How about just even more simple:
01 02 03
when 01 fills up/gets loaded, move to 02, or add start just cycling thru them...
kevin