Changes to cs_comments_service on master

[Robert Raposa]

TL;DR In preparation for an upcoming move to ElasticSearch 1.5 for cs_comments_service, there are changes for how to properly initialize forums.  This does not affect the Ficus release.  It only affects the master branch at this point.

Longer:

If you use the supervisor startup scripts provided by the ansible playbooks in the configuration repo to start cs_comments_service, if a "content" alias with the proper mappings is not set up, cs_comments_service will fail to start. This is an intentional change to ensure that the configuration of the index is in-sync with what is expected by cs_comments_service.

In order for the startup script to work properly, you will need the latest changes from master from both the configuration and cs_comments_service repos.

To initialize a fresh install, you'll need to first call:

bin/rake search:initialize

To validate if your install has a 'content' alias with up-to-date mappings, you can call:

bin/rake search:validate_index

This validate_index call is what the supervisor startup script uses to determine whether forums should start.

For more details, please read the cs_comments_service README. 

Feel free to reach out with any questions.

Thank you.

--

Robert Raposa

edX | Software Architect  | rra...@edx.org  

141 Portland Street, 9th floor

Cambridge, MA 02139

http://www.edx.org