Pull NeoFS endpoints from network map #280

New issue

Open

opened 2025-12-28 17:36:51 +00:00 by sami · 3 comments

sami commented

2025-12-28 17:36:51 +00:00

Owner

Originally created by @alexvanin on GitHub (Jul 6, 2022).

For pilot installations, @realloc suggested having list of NeoFS endpoints from network map. But address field of node info should not be used, because it is going to be internal private address.

Instead, Node can define attribute PublicEndpoints with value grpc://public1:8080,grpcs://public1:8082. Consider addresses split by , or whitespace.

S3 Gateway makes request to the side chain and receives network map. If no public endpoint is defined, then use values from config.

Originally created by @alexvanin on GitHub (Jul 6, 2022). For pilot installations, @realloc suggested having list of NeoFS endpoints from network map. But [address](https://github.com/nspcc-dev/neofs-api/blob/10f18e4b69ec79991b1a2b83e212d99203f3ee1a/netmap/types.proto#L136) field of node info should not be used, because it is going to be internal private address. Instead, Node can define attribute `PublicEndpoints` with value `grpc://public1:8080,grpcs://public1:8082`. Consider addresses split by `,` or whitespace. S3 Gateway makes request to the side chain and receives network map. If no public endpoint is defined, then use values from config.

sami added the

enhancement

labels

2025-12-28 17:36:51 +00:00

sami commented

2025-12-28 17:36:51 +00:00

Author

Owner

@realloc commented on GitHub (Jul 6, 2022):

Additionally, here is the point where we could use advanced logic like network/Geo proximity for choosing the most appropriate endpoints. In the future, of course.

@realloc commented on GitHub (Jul 6, 2022): Additionally, here is the point where we could use advanced logic like network/Geo proximity for choosing the most appropriate endpoints. In the future, of course.

sami commented

2025-12-28 17:36:51 +00:00

Author

Owner

@alexvanin commented on GitHub (Oct 6, 2022):

I think @fyrchik did some tasks to split external and internal interfaces. Let's mention them here and look at it once again.

@alexvanin commented on GitHub (Oct 6, 2022): I think @fyrchik did some tasks to split external and internal interfaces. Let's mention them here and look at it once again.

sami commented

2025-12-28 17:36:51 +00:00

Author

Owner

@alexvanin commented on GitHub (Oct 6, 2022):

Looks very similar to https://github.com/nspcc-dev/neofs-sdk-go/issues/297
Need to consider if both issues are valid. It seems like pool update can close this issue?

@alexvanin commented on GitHub (Oct 6, 2022): Looks very similar to https://github.com/nspcc-dev/neofs-sdk-go/issues/297 Need to consider if both issues are valid. It seems like pool update can close this issue?