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

Improve MachineRegistry Events propagation #10

Open
Fra-nk opened this issue Jul 7, 2016 · 2 comments
Open

Improve MachineRegistry Events propagation #10

Fra-nk opened this issue Jul 7, 2016 · 2 comments

Comments

@Fra-nk
Copy link
Contributor

Fra-nk commented Jul 7, 2016

Currently every MachineRegistry event is published to every subscribed adapter.
NewMachineEvent & MachineRemovedEvent are currently rarely used due to missing information (MR doesn't have have any information/attributes for these machines). Currently you also lack the information on site and batch system...

→ Develop a way to discern a machine's "target" adapters and only publish the information to these adapter(s).
Then NewMachineEvent & MachineRemovedEvent could be used similar to constructors/destructors in those adapters.

@Fra-nk
Copy link
Contributor Author

Fra-nk commented Jul 20, 2016

35391f7 addresses some issues.

@Fra-nk
Copy link
Contributor Author

Fra-nk commented Sep 8, 2016

Python coroutines may be a good way to optimize the code.

giffels pushed a commit to giffels/ROCED that referenced this issue Feb 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant