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

refacto(overhaul): crate-split + QoL enhancements (#170) #171

Merged
merged 1 commit into from
Feb 5, 2024
Merged

Conversation

J-Loudet
Copy link
Contributor

@J-Loudet J-Loudet commented Feb 5, 2024

This commit has one main purpose: facilitating the usage of Zenoh-Flow.

For a complete log, see PR #170

To achieve that purpose, several major changes were made (the list is not exhaustive):

  • Instead of having a single — large — crate, this PR separates the different parts of Zenoh-Flow's logic into several smaller crates. A direct consequence of this split is that to compile a Zenoh-Flow node, it is no longer needed to have to compile Zenoh and Zenoh-Flow which drastically reduces the compilation time.

  • The writing of the data flow and node descriptors is more flexible:

    • the vars section is propagated to the "children",
    • the nodes descriptions can be written with the data flow descriptor, they don't have to live in a separate file,
    • all descriptors can be written in YAML or JSON (JSON support was only partial before).
  • A zenoh-flow-standalone-runtime executable was created to locally test a data flow. This executable does not require using our CLI to interact with it.

  • With the default options, Zenoh-Flow does not require configuration files or a Zenoh router with specific storages.

This commit has one main purpose: facilitating the usage of Zenoh-Flow.

For a complete log, see PR #170 #170

To achieve that purpose, several major changes were made (the list is not exhaustive):

- Instead of having a single — large — crate, this PR separates the different parts of Zenoh-Flow's logic into several smaller crates. A direct consequence of this split is that to compile a Zenoh-Flow node, it is no longer needed to have to compile Zenoh and Zenoh-Flow which drastically reduces the compilation time.

- The writing of the data flow and node descriptors is more flexible:
  - the vars section is propagated to the "children",
  - the nodes descriptions can be written with the data flow descriptor, they don't have to live in a separate file,
  - all descriptors can be written in YAML or JSON (JSON support was only partial before).

- A `zenoh-flow-standalone-runtime` executable was created to locally test a data flow. This executable does not require using our CLI to interact with it.

- With the default options, Zenoh-Flow does not require configuration files or a Zenoh router with specific storages.


Signed-off-by: Julien Loudet <julien.loudet@zettascale.tech>
@J-Loudet J-Loudet merged commit 06513f7 into main Feb 5, 2024
9 checks passed
@J-Loudet J-Loudet deleted the master branch February 7, 2024 10:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant