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.

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

feat:ec: integrate F3 dynamic manifest #12173

Merged
merged 7 commits into from
Jul 4, 2024

Conversation

adlrocha
Copy link
Contributor

@adlrocha adlrocha commented Jul 2, 2024

Related Issues

Closes filecoin-project/go-f3#370

Proposed Changes

This PR integrates support for F3's dynamic manifest. Through the dynamic manifest, a manifest server is able to trigger configuration changes over F3 remotely. The F3 node listens to new manifests, and when a new manifest is received:

  • It tearsdown and setup a new pubsub topic for the new F3 configuration.
  • It rebootstraps or applies the reconfiguration (depending on the parameters of the manifest).
  • It resumes the normal operation of F3.

Additional Info

Depends on filecoin-project/go-f3#391

Checklist

Before you mark the PR ready for review, please make sure that:

  • Commits have a clear commit message.
  • PR title is in the form of of <PR type>: <area>: <change being made>
    • example: fix: mempool: Introduce a cache for valid signatures
    • PR type: fix, feat, build, chore, ci, docs, perf, refactor, revert, style, test
    • area, e.g. api, chain, state, mempool, multisig, networking, paych, proving, sealing, wallet, deps
  • If the PR affects users (e.g., new feature, bug fix, system requirements change), update the CHANGELOG.md and add details to the UNRELEASED section.
  • New features have usage guidelines and / or documentation updates in
  • Tests exist for new functionality or change in behavior
  • CI is green

@adlrocha adlrocha changed the title F3-370: integrate F3 dynamic manifest feat:ec: integrate F3 dynamic manifest Jul 2, 2024
masih added 2 commits July 4, 2024 11:27
Peer ID is of type string internally but the internal string
representation is not the same as the encoded string representation.
Therefore, the latter needs to be decoded and cannot be casted to the
former. Otherwise, it will represent a different ID.
Copy link
Contributor

@Kubuxu Kubuxu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SGTM

@jennijuju jennijuju merged commit 4456943 into filecoin-project:master Jul 4, 2024
75 of 76 checks passed
jennijuju pushed a commit that referenced this pull request Jul 4, 2024
* F3-370: integrate F3 dynamic manifest

* F3-370: make linter happy

* Set manifest sender identities

* Decode manifest sender peer ID from string before using it

Peer ID is of type string internally but the internal string
representation is not the same as the encoded string representation.
Therefore, the latter needs to be decoded and cannot be casted to the
former. Otherwise, it will represent a different ID.

* `make gen` the pain of my life

---------

Co-authored-by: Masih H. Derkani <m@derkani.org>
jennijuju added a commit that referenced this pull request Jul 4, 2024
* F3-370: integrate F3 dynamic manifest

* F3-370: make linter happy

* Set manifest sender identities

* Decode manifest sender peer ID from string before using it

Peer ID is of type string internally but the internal string
representation is not the same as the encoded string representation.
Therefore, the latter needs to be decoded and cannot be casted to the
former. Otherwise, it will represent a different ID.

* `make gen` the pain of my life

---------

Co-authored-by: adlrocha <6717133+adlrocha@users.noreply.github.com>
Co-authored-by: Masih H. Derkani <m@derkani.org>
@rjan90
Copy link
Contributor

rjan90 commented Jul 22, 2024

Removing the backport label, as this was backported to v1.28.0 in: #12185

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Integrate the dynamic manifest with Lotus
5 participants