Bugzilla – Full Text Bug Listing
| Summary: | Move babel vserver to the Eclipse Foundations cloud provider | ||
|---|---|---|---|
| Product: | [Technology] Babel | Reporter: | Eclipse Webmaster <webmaster> |
| Component: | Server | Assignee: | Babel server inbox <babel.server-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | denis.roy, kitlo |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| See Also: | https://bugs.eclipse.org/bugs/show_bug.cgi?id=463293 | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 549119 | ||
|
Description
Eclipse Webmaster
Kit, this is a major change for Babel. We've been relying on the same old virtual server for a very, very long time. The old server is what is causing bug 548890, and moving to a new vserver will inherently fix this. One of the biggest issues we'll face with the migration is user authentication. The server code has not been worked on in a long time, and the effort to adapt it to something like oAuth is unkown. See bug 463293 We could ask the community to step up here. Kit, what are your thoughts? Denis, I don't have much experience with user authentication. How do other Eclipse vservers do it? We really need the community's help. To answer Matt's questions, I believe we just need ports 22 and 443 to be opened. Denis, can you think of anything else? > Denis, I don't have much experience with user authentication. How do other > Eclipse vservers do it? We really need the community's help. Other vservers either have their own authentication mechanism, or use OAuth: https://api.eclipse.org/docs/auth I do believe Antoine made the Bugzilla authentication an add-on back in 2008, and there is a mechanism for local logins. I'd have to check. Between a local login and OAuth, I'm not sure which is less effort. > To answer Matt's questions, I believe we just need ports 22 and 443 to be > opened. Denis, can you think of anything else? Port 80, for a redirect. Denis, what's the plan for this move? Now that my shell access is restricted, I cannot perform any maintenance on the babel vserver. I cannot deploy any new changes to the server. I cannot restart the Apache web server if needed. I cannot apply any changes to the SQL database (sometimes needed to prepare for a new releases). I also cannot run syncup nor process project source locations on demand. Perhaps we can get that OpenID patch in so that the server part still works. In the meanwhile, we can ask for provisioning the new VM at Azure. The babel db is 10G, so the default 30G VM should suffice. We'll need port 22, 80 (for a redirect) and 443. We'll also need to use letsencrypt for the SSL certificate. Kit, can you send your SSH public key to webmaster@eclipse.org to set up the VM ? Babel has been moved to Azure. I've shut off Apache on the existing vserver. Can we keep it online for a few days while I migrate cron jobs? Also, Matt, how long do you plan on keeping the old image file? (In reply to Denis Roy from comment #7) > Also, Matt, how long do you plan on keeping the old image file? Usually for around 4-6 months, but if you're certain it won't be needed I'm happy to just delete it so nobody has to remember to clean up later. -M. I've shut down the old vserver and marked the image file for deletion in a few months. |