Skip to content
This repository has been archived by the owner on Dec 16, 2022. It is now read-only.

analyze need, propose architecture #125

Closed
tloubrieu-jpl opened this issue Jan 28, 2021 · 2 comments
Closed

analyze need, propose architecture #125

tloubrieu-jpl opened this issue Jan 28, 2021 · 2 comments
Assignees
@tdddblog
Labels
B11.1 enhancement New feature or request
Milestone
03.Wyomia.Tyus

Comments

@tloubrieu-jpl
Copy link
Contributor

tloubrieu-jpl commented Jan 28, 2021 •
edited
Loading

Questions are:

  • do we need a tool which will pull from elastic search directly ?
  • do we want a tool which will pulls from the API ?
  • do we want the nodes to push from their registry ?
  • can we re-use elasticsearch integration tools ?
@tloubrieu-jpl tloubrieu-jpl added this to the 02.Marion.Jones milestone Jan 28, 2021
@tloubrieu-jpl
Copy link
Contributor Author

tloubrieu-jpl commented Feb 24, 2021 •
edited
Loading

The conclusion of this ticket is to work on a request broadcast across the different registry's elasticSearch of the nodes by using CCS, see https://www.elastic.co/guide/en/cloud/current/ec-enable-ccs.html

@tdddblog
Copy link
Contributor

Added cross-cluster search (CCS) slides
RegistryIntegration.pdf

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@tdddblog tdddblog

Labels
B11.1 enhancement New feature or request
Projects
None yet
Milestone
03.Wyomia.Tyus
Development

No branches or pull requests
2 participants
@tdddblog @tloubrieu-jpl