New container estimations by Storage Nodes #413

New issue

Open

opened 2025-12-28 18:16:16 +00:00 by sami · 2 comments

sami commented

2025-12-28 18:16:16 +00:00

Owner

Originally created by @carpawell on GitHub (Aug 21, 2025).

I'm always frustrated when we update SN and it is not tested properly since.

Describe the solution you'd like

We have changed the way container estimations are written to container. This is now more descriptive and less complex: storage nodes put estimations directly to the contract, and the contract always has some average calculated value. We will adopt neofs-adm to work with the new estimations in https://github.com/nspcc-dev/neofs-node/pull/3540 and SN's reports will be updated in https://github.com/nspcc-dev/neofs-node/pull/3539.

However, any RPC calls to neo-go can be done using regular HTTP requests, so maybe it is even a better way to test neofs without neofs utils. Calls to chains can be placed in a package and reused for other tests.

Additional context

https://github.com/nspcc-dev/neofs-contract/pull/507, https://github.com/nspcc-dev/neofs-node/issues/3460.

Originally created by @carpawell on GitHub (Aug 21, 2025). ## Is your feature request related to a problem? Please describe. I'm always frustrated when we update SN and it is not tested properly since. ## Describe the solution you'd like We have changed the way container estimations are written to container. This is now more descriptive and less complex: storage nodes put estimations directly to the contract, and the contract always has some average calculated value. We will adopt `neofs-adm` to work with the new estimations in https://github.com/nspcc-dev/neofs-node/pull/3540 and SN's reports will be updated in https://github.com/nspcc-dev/neofs-node/pull/3539. However, any RPC calls to `neo-go` can be done using regular HTTP requests, so maybe it is even a better way to test neofs without neofs utils. Calls to chains can be placed in a package and reused for other tests. ## Additional context https://github.com/nspcc-dev/neofs-contract/pull/507, https://github.com/nspcc-dev/neofs-node/issues/3460.

sami added the

feature

labels

2025-12-28 18:16:16 +00:00

sami commented

2025-12-28 18:16:16 +00:00

Author

Owner

@carpawell commented on GitHub (Nov 21, 2025):

We have finished changing the payment flow in https://github.com/nspcc-dev/neofs-node/pull/3650. Now, storage nodes report 3 times every epoch about their loads, it is stored on the contract side. It also has container summaries. There are also neofs-adm's extensions for reports inspections: https://github.com/nspcc-dev/neofs-node/pull/3687, https://github.com/nspcc-dev/neofs-node/pull/3649 which allow looking at the current report and summary state. Every metric is multiplied by REP (3 objects in a REP 3 container will report about storing 9 objects).

@carpawell commented on GitHub (Nov 21, 2025): We have finished changing the payment flow in https://github.com/nspcc-dev/neofs-node/pull/3650. Now, storage nodes report 3 times every epoch about their loads, it is stored on the contract side. It also has container summaries. There are also neofs-adm's extensions for reports inspections: https://github.com/nspcc-dev/neofs-node/pull/3687, https://github.com/nspcc-dev/neofs-node/pull/3649 which allow looking at the current report and summary state. Every metric is multiplied by REP (3 objects in a REP 3 container will report about storing 9 objects).

sami commented

2025-12-28 18:16:16 +00:00

Author

Owner

@carpawell commented on GitHub (Nov 21, 2025):

However, any RPC calls to neo-go can be done using regular HTTP requests, so maybe it is even a better way to test neofs without neofs utils. Calls to chains can be placed in a package and reused for other tests.

Still a useful testing improvement IMO.

@carpawell commented on GitHub (Nov 21, 2025): > However, any RPC calls to neo-go can be done using regular HTTP requests, so maybe it is even a better way to test neofs without neofs utils. Calls to chains can be placed in a package and reused for other tests. Still a useful testing improvement IMO.