Page MenuHomeSoftware Heritage

webapp: use swh-search as main search engine in production
ClosedPublic

Authored by vsellier on Thu, Feb 11, 11:27 AM.

Details

Summary
  • Deploy and configure a swh-search environment on moma
  • Explicit the elasticsearch configurations for the

scheduler/storage and the webapps searches as they are not stored
on the same clusters

  • Simplify the overrides between staging/moma/webapp1

Related to T2182

Test Plan

octocatalog-diff moma (too long to be pasted here)
octocatalog-diff webapp1


File[/etc/softwareheritage/search/server.yml] =>
 parameters =>
   content =>
    @@ -1,5 +1,12 @@
     ---
     search:
    -  cls: remote
    -  url: http://search1.internal.softwareheritage.org:5010/
    +  cls: elasticsearch
    +  args:
    +    hosts:
    +    - host: search-esnode1.internal.softwareheritage.org
    +      port: 9200
    +    - host: search-esnode2.internal.softwareheritage.org
    +      port: 9200
    +    - host: search-esnode3.internal.softwareheritage.org
    +      port: 9200
    _

No changes on search1 or staging nodes

Diff Detail

Repository
rSPSITE puppet-swh-site
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.