Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Per-container event contracts #414

Open
roman-khimov opened this issue Jun 27, 2024 · 1 comment
Open

Per-container event contracts #414

roman-khimov opened this issue Jun 27, 2024 · 1 comment
Assignees
@carpawell
Labels
blocked Can't be done because of something feature Completely new functionality I1 High impact S2 Regular significance U2 Seriously planned

Comments

@roman-khimov
Copy link
Member

Is your feature request related to a problem? Please describe.

I'm always frustrated when I don't know what's up with the container contents. And we want to filter events per-container.

Describe the solution you'd like

The solution is to deploy a contract for containers that use meta (nspcc-dev/neofs-api#300, container contract would need to know it's enabled). This contract needs to accept event data from SNs and push them into notifications. It does not need to process/store these events. This gives a natural event feed for container.
@roman-khimov roman-khimov added U2 Seriously planned blocked Can't be done because of something S2 Regular significance I1 High impact feature Completely new functionality labels Jun 27, 2024
This was referenced Jun 27, 2024
Open
Open
@carpawell carpawell self-assigned this Aug 26, 2024
@roman-khimov
Copy link
Member Author

roman-khimov commented Sep 3, 2024 •
edited
Loading

There is a question of updates. Updating 1000 contracts at once is very much different from updating 10 contracts.

@carpawell carpawell mentioned this issue Sep 6, 2024
Merged
carpawell added a commit to nspcc-dev/neofs-node that referenced this issue Sep 6, 2024
@carpawell
node/object/put: exchange meta signatures during replication
c13f5f4 
Initial replication requires nodes to sign object's main meta information and
respond with it. Meta information is not sent on wire and treated as a fixed
ordered NEO's map. Signatures are verified, not stored/send anywhere yet.
It follows the recent API extension: nspcc-dev/neofs-api#299.
Further, this extension is planned to have a contract adoption:
nspcc-dev/neofs-contract#413 and nspcc-dev/neofs-contract#414.
Closes #2876.

Signed-off-by: Pavel Karpy <[email protected]>
carpawell added a commit to nspcc-dev/neofs-node that referenced this issue Sep 10, 2024
@carpawell
node/object/put: exchange meta signatures during replication
e63289a 
Initial replication requires nodes to sign object's main meta information and
respond with it. Meta information is not sent on wire and treated as a fixed
ordered NEO's map. Signatures are verified, not stored/send anywhere yet.
It follows the recent API extension: nspcc-dev/neofs-api#299.
Further, this extension is planned to have a contract adoption:
nspcc-dev/neofs-contract#413 and nspcc-dev/neofs-contract#414.
Closes #2876.

Signed-off-by: Pavel Karpy <[email protected]>
carpawell added a commit to nspcc-dev/neofs-node that referenced this issue Sep 10, 2024
@carpawell
node/object/put: exchange meta signatures during replication
b724d14 
Initial replication requires nodes to sign object's main meta information and
respond with it. Meta information is not sent on wire and treated as a fixed
ordered NEO's map. Signatures are verified, not stored/send anywhere yet.
It follows the recent API extension: nspcc-dev/neofs-api#299.
Further, this extension is planned to have a contract adoption:
nspcc-dev/neofs-contract#413 and nspcc-dev/neofs-contract#414.
Closes #2876.

Signed-off-by: Pavel Karpy <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@carpawell carpawell

Labels
blocked Can't be done because of something feature Completely new functionality I1 High impact S2 Regular significance U2 Seriously planned
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@roman-khimov @carpawell