search

ghwood / www.ietf.org

Previously issue tracking for new www.ietf.org IETF website. Please send issues to support@ietf.org
https://www.ietf.org
Apache License 2.0
0 stars 4 forks source link

update to Elasticsearch 5.6 #99

Closed ghwood closed 6 years ago

ghwood commented 6 years ago

Inquiry with Torchbox about upgrading to Elasticsearch 5.6 for Wagtail IETF website:

Initial email below.

Torchbox response with options here:

https://projects.torchbox.com/projects/ietf/tickets/167

Currently waiting on AMS to advise about preferred path forward.

On Nov 1, 2017, at 6:35 PM, Glen glen@amsl.com wrote:

Greg -

In Torchbox Ticket 107 ( https://projects.torchbox.com/projects/ietf/tickets/107 ), they asked us to install "ElasticSearch" on the IETF server, which, after some discussion, we did.

At that time (late 2016), they told us to install ElasticSearch 1.7, which we did, and which we have been running ever since.

I've recently learned that ElasticSearch 1.7 was released in mid-2015, and as of late 2016 (when they asked us to install ElasticSearch) the latest release was 5.1. So we have been running and install that was already a year or more out of date. ( https://en.wikipedia.org/wiki/Elasticsearch )

I now have an inquiry about upgrading ElasticSearch to the latest version, 5.6, which was just released in September 2017.

Since Wagtail (apparently) depends upon ElasticSearch, and since this is a significant set of release differences, would you please reach out to your contacts at Torchbox and ask them if they anticipate any problems with the Wagtail website if we upgrade to the latest version? We need to keep all of our software current, and our expectation is that all of our software can and should survive routine dependency upgrades, but given the situation here, I thought it best to ask you to reach out to Torchbox directly.

Please let us know, and thanks!

Glen

ghwood commented 6 years ago

This has been referred to Torchbox at: https://projects.torchbox.com/projects/ietf/tickets/167