Pull FrostFS endpoints from network map #50

New issue

Open

opened 2023-03-08 23:38:12 +00:00 by snegurochka · 0 comments

snegurochka commented

2023-03-08 23:38:12 +00:00

Member

Original issue: https://github.com/nspcc-dev/neofs-s3-gw/issues/582

For pilot installations, @realloc suggested having list of FrostFS 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.

Original issue: https://github.com/nspcc-dev/neofs-s3-gw/issues/582 For pilot installations, @realloc suggested having list of FrostFS 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.