RFC: Moving Redmine to OpenShift (and adding a blog!)

Andrew Fitzsimon afitzsim at redhat.com
Mon Apr 2 20:35:23 UTC 2012


+111

Let me know when to add the fresh coat of paint.

On 03/04/2012, at 6:32 AM, Matt Wagner <matt.wagner at redhat.com> wrote:
> Hi all,
> 
> I've been planning out (and tinkering with) what it would take to move
> Redmine to OpenShift. You can see the planning page here:
> https://www.aeolusproject.org/redmine/projects/aeolus/wiki/Moving_Redmine_to_OpenShift
> 
> The reason for this proposed change is two-fold. First, our current
> Redmine instance is unbearably slow. (Rumor has it that it's running on
> this[1].) The second reason for this proposed change is that it would
> alleviate us from having to manage the VM instance powering this. From
> asking around, it sounds like the VM where this is running doesn't
> really have RAM to spare, so bumping us up from 1GB to 2GB is unlikely
> to be feasible.
> 
> I have a demo Redmine site running here:
> https://redminetest-mattydubs.rhcloud.com/
> 
> I'm seeing average page load times around 1 second. Sometimes it's
> closer to 250ms, and sometimes it's 3 seconds, but the average is
> somewhere around 1 second. With the existing site... Well, when I didn't
> get an Apache error about the connection to thin timing out, 5-25
> seconds is more the norm. Truthfully I find an average load time around
> 1 second to be disappointing, but it's in keeping with most other sites.
> (Pingdom's "Full Page Test" says it's "faster than 72% of all tested
> websites.")
> 
> While OpenShift supports HTTPS, they don't allow custom certificates
> (yet?), so we would have to run on the .rhcloud.com domain, or not use
> HTTPS if we wanted to use a CNAME for an aeolusproject.org subdomain.
> However, because we were likely going to end up on some sort of new
> subdomain to make this work anyway, I would argue that the domain we're
> on doesn't matter a bunch -- people will either follow a link, or
> they'll go from bookmarks / their browser's history.
> 
> If people are so inclined, what we should do is set up an account on
> OpenShift that's not in an individual's name (perhaps using the
> aeolus-devel list like we did on some other sites), and share the
> password with a handful of maintainers. You can attach multiple public
> keys, allowing everyone to use their own ssh key for management. (This
> means that access to the web interface isn't strictly necessary; you
> could get someone to add your key and work from the CLI tools.)
> 
> If you can believe it, this is not the full version; there's more
> information on the wiki feature page linked above. This should hit most
> of the high points, though. Please let me know what you think.
> 
> As a tangent, I also set up WordPress on OpenShift, as I referenced in a
> previous email. It ended up being pretty easy; I would really like to
> make it official. I think all we need to do to get that working is set
> up a CNAME (if we want one), since there's no need for SSL for
> non-management stuff, and maybe customize the theme to not look so
> "default". This isn't the main focus of this, though.
> 
> -- Matt
> 
> [1] http://hackaday.com/2012/03/28/building-the-worst-linux-pc-ever/



More information about the aeolus-devel mailing list