Bugzilla – Full Text Bug Listing
| Summary: | Create a migration story for BETA OrionHub to 1.0 of OrionHub | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Ken Walker <ken_walker> |
| Component: | OrionHub | Assignee: | John Arthorne <john.arthorne> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | john.arthorne, webmaster |
| Version: | 0.5 | ||
| Target Milestone: | 1.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Ken Walker
Webmaster, would it be possible to use your front end proxy server to redirect a subdomain like beta.orionhub.org to a different port on orionhub.org. We could then keep the old server running on that port for say a month after the transition to enable people to access their old data. I know we never claimed to keep a copy of their data around but if we can do it with minimal extra work it would be nicer than giving our beta users a kick in the teeth. I like this much better than just migrating all the data over to the new server at 1.0, because there are probably a few thousand inactive accounts where people gave it a spin and never came back. Yep, that shouldn't be a problem. Ok Denis, dumb question but how do we set this up? Should we just pick a different port to run the "old" server, and you will redirect requests from beta.orionhub.org to that port? We will be ready to do this in a couple of days. Set up your new instance, tell me which port it's on and I'll do the rest. Hi Denis, can you set up a redirect from backup.orionhub.org to orionhub.org:8090. We are planning to "switch" the old server to that port. We will then run the new server on the default 8080 port with the workspace in the large new partition you set up. We will aim to switch this over around noon EDT tomorrow (Oct 19). Todo for tomorrow: Old server: - Shutdown server - Move install directory out of /current/eclipse - Change port in orion.ini - Disable account creation in orion.conf - Change virtual hosts argument in orion.conf (or maybe we just disable sites) New server: - Update workspace location in upgrade.sh I don't have the cycles to do that, John. Sorry. Our typical upgrade process involves taking a backup of app and data, sandboxing the current setup, upgrading it, then doing the same process to the live version assuming all went well. Just to be clear, that "todo" list was for myself. All we're looking for from you is one new redirect: backup.orionhub.org -> orionhub.org:8090 Does adding a redirect require all those steps? If so it is something you can schedule next week? Ah, ok. It's in. I'm assuming you wanted a proxypass, not a redirect, since port 8090 is not open to the world.
RewriteCond %{HTTP_HOST} ^backup.orionhub.org$ [NC]
RewriteRule .* http://orionhub.org:8090 [P,L]
Something's not working with the rewrite. We have a server running on port 8090, but any URL we request in the browser gets redirected to the same file. For example: http://backup.orionhub.org/hello/world.txt Gives us an HTML file That should have been:
RewriteCond %{HTTP_HOST} ^backup.orionhub.org$ [NC]
RewriteRule ^/(.*) http://orionhub.org:8090/$1 [P,L]
Much better, thanks Denis! backup.orionhub.org is up and running. Actually it is running, but slow as molasses. We don't need the same QoS as orionhub.org, but could it be speeded up a bit? We're getting terrible timeout errors trying to use it. Actually it's a bit better now. I wonder if the indexer is the issue on a fresh restart? It's all the same IP, so it gets the same QoS treatment as orionhub.org. LOg in and check with top to see if anything is bogging down the machine. We're fine. |