Closed
Bug 1601451
Opened 5 years ago
Closed 5 years ago
Move to Ubuntu 18.04 LTS
Categories
(Webtools :: Searchfox, enhancement)
Webtools
Searchfox
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: asuth, Assigned: asuth)
Details
In https://github.com/mozsearch/mozsearch/pull/248 :emilio did most of the research and legwork to update us from 16.04 to 18.04. The super nice thing there is to allow us to use libvirt for local virtualization instead of virtualbox. (Many props to virtualbox for existing, but it has been a major source of hassle and mysterious failures (short reads!), so it's nice to be able to avoid it.)
I'm also going to make sure we disable unattended upgrades which have been a problem for debugging. (I proposed this in https://bugzilla.mozilla.org/show_bug.cgi?id=1498207#c12)
My plan is to, right now:
- [x] Fork :emilio's https://github.com/mozsearch/mozsearch/pull/248 to a local branch for me
- [x] Make local changes such as
unattended-upgrades
. - [x] Locally validate the virtualization is happy.
- [x] Perform provisioning to get us new AMI's. (These will include my local changes beause of how provisioning works and may involve some iteration on the branch.)This will get us newly named AMI's.
- [x] Update my branch to use the new AMI's.
- [x] Run a test "dev" run.
- [x] Put the pull request for the switchover up for review.
- [x] Once reviewed and merged, regenerate the lambda images. (The lambda images are what call trigger_indexer.py from their local snapshotted state.)
Assignee | ||
Comment 1•5 years ago
|
||
- Successful run up at https://dev.searchfox.org/ for config.json.
- Pull request up at https://github.com/mozsearch/mozsearch/pull/258. (I thought about trying to push to Emilio's existing https://github.com/mozsearch/mozsearch/pull/248 but figured that wasn't a huge win for the effort/potential mistakes.)
Assignee | ||
Comment 2•5 years ago
|
||
Okay, all merged in, lambda zips regenerated and uploaded and now triggered. Marking fixed but I'll reopen if there's a problem.
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•