You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Peter Lee (Jira)" <ji...@apache.org> on 2025/01/28 08:54:00 UTC
[jira] [Assigned] (HDDS-1743) Create service catalog endpoint in the SCM
[ https://issues.apache.org/jira/browse/HDDS-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Lee reassigned HDDS-1743:
-------------------------------
Assignee: Peter Lee
> Create service catalog endpoint in the SCM
> ------------------------------------------
>
> Key: HDDS-1743
> URL: https://issues.apache.org/jira/browse/HDDS-1743
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: SCM
> Reporter: Marton Elek
> Assignee: Peter Lee
> Priority: Major
>
> Based on the the design doc in the parent pom, we need a Service Catalog endpoint in the SCM.
>
> {code:java}
> public interface ServiceRegistry {
> void register(ServiceEndpoint endpoint) throws IOException;
> ServiceEndpoint findEndpoint(String serviceName, int instanceId);
> Collection<ServiceEndpoint> getAllServices();
> }{code}
> Where the ServiceEndpoint is something like this:
> {code:java}
> public class ServiceEndpoint {
> private String host;
> private String ip;
> private ServicePort port;
> private String serviceName;
> private int instanceId;
> ...
> }
> public class ServicePort {
>
> private ServiceProtocol protocol;
> private String name;
> private int port;
> ...
> }
> public enum ServiceProtocol {
> RPC, HTTP, GRPC
> }{code}
> The ServiceRegistry may have multiple implementation, but as a first step we need a simple implementation which calls a new endpoint on SCM via REST.
> The endpoint should persist the data to a local Rocksdb with the help of DBStore.
> This task is about to create the server and client implementation. In a follow-up Jira we can start to use the client on the om/datanode/client side to mix the service discovery data with the existing configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org