Remove dual service support #1487

New issue

Open

opened 2024-11-12 07:46:30 +00:00 by aarifullin · 0 comments

aarifullin commented

2024-11-12 07:46:30 +00:00

Member

frost.fs namespace was introduced in frostfs-api#69. So, frostfs-sdk-go/api will use protobufs with the new namespace.
PR #1486 introduced dual service support for both neo.fs.v2 and frost.fs.
The reason of this dual service support is to reach smooth update:

While node A is not updated yet, it must able to request node B with the latest frostfs-sdk-go/api version (put, policer)
Node B must be able to request A with deprecated frostfs-sdk-go/api version (put, policer)
Old client must be able to request node B.

So, as soon as migration is complete, #1486 should be reverted.

`frost.fs` namespace was introduced in [frostfs-api#69](https://git.frostfs.info/TrueCloudLab/frostfs-api/pulls/69). So, `frostfs-sdk-go/api` will use protobufs with the new namespace. PR [#1486](https://git.frostfs.info/TrueCloudLab/frostfs-node/pulls/1486) introduced dual service support for both `neo.fs.v2` and `frost.fs`. The reason of this dual service support is to reach smooth update: - While node `A` is not updated yet, it must able to request node `B` with the latest `frostfs-sdk-go/api` version (`put`, `policer`) - Node `B` must be able to request `A` with deprecated `frostfs-sdk-go/api` version (`put`, `policer`) - Old client must be able to request node `B`. So, as soon as migration is complete, [#1486](https://git.frostfs.info/TrueCloudLab/frostfs-node/pulls/1486) should be reverted.