On 02/04/12 16:32 -0400, Matt Wagner 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...
Matt, good work, I am glad you looked into this. I have a number of
questions here, I'll respond inline to the ones from this email, and
add others based on wiki page at the end.
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/
While this is indeed fast, I wonder what effect having our full
dataset would have on the speed, if any. This may be good to find out
before we make any decision.
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.
Could we not just use https for _login_ and leave the rest one our own
domain? Or is that outside the realm of the possible here?
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.)
Maybe I am remembering wrong, but I thought I saw something about
openshift apps being deployed via git repos. If that is the case,
could we just make a repo that all developers have access to so we can
make fixes quickly, and then also do the subset/group you mention
above for pushing those updates to openshift?
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.
I think this is a nice idea/addition to the community, especially as
it supports much the same functionality as our current blogroll plugin
for redmine, but in a way that makes more sense to me, since it is
actually a blog. If we did this, I propose we add any existing blogs
the blogroll lists, and then retire it. One less thing to clutter the
RM interface, imo. I would like to mention another plus of this
direction is that we have the option for developers and other
community members to have their own hosted aeolus blog, while also
providing the flexibility for them to run their own and have it
included (at least that is how I understaood what you told me when we
chatted about this, please correct here if I misunderstood).
Questions based on wiki page:
* You mention evaluating stability, how would we do this other than
setting up a long-running test app there?
* Would your suggestion to use 'something lie cloudfront' be needed,
* and if so, is the cost acceptable?
* is this the same version we have, or a newer one? You mention looking
at upgrading, but I didnt see you say anywhere if you in fact did that.
* The sending emails thing is another one that appears to need an
external service based on your wiki page. Do we want to incur that
extra cost, since we can do this ourselves now at no cost? Maybe
that free one for 200/day is enough for right now, but what about as
we grow? On a busy day of you editing this page (which I have set
as a watch), I can easily get 5-10 emails myself. It seems like
this could easily scale to much larger than we may want from a paid
service.
* While I am sure we coudl talk to them about more space, perhaps we
should consider storage/impact for things like release tarballs. I
think we put them on our fedorapeople account right now, so his may
not be an issue, just think we should consider it.
* Removing the repo browser may be a requirement if we go to
openshift, as that would at the least impact the disk space we are
using, and as you say, it does duplicate functionality in github. We
lose the option to easily hook issues to commits, but nobody has
used that anyway, so probably not a big loss.
* If we do go this route (and I am not sure really if you are
recommending we do), what are your thoughts on moving to
chiliproject as part of the migration? Any issues, thoughts
pro/con? I looked at their latest release, and it is soooo much
nicer looking by default than redmine, ans appears more easily
skinnable. It also has support for liquid templates, which is kind
of cook, though I'd prefer to just have markdown as well, like you
said. I just took a quick look and our backlogs plugin is supported
for chiliproject as well. My take is that chili is much more active
than redmine, which seems to be doing only infrequent bugfix
releases vs new feature dev and enhancements like chili is
(including moving to rails 3.1 or so in the next few months).
-j