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

Proposal: Replace ephemeral nodes with a unix socket #208

Open
ghjm opened this issue Apr 21, 2020 · 2 comments
Open

Proposal: Replace ephemeral nodes with a unix socket #208

ghjm opened this issue Apr 21, 2020 · 2 comments
Milestone

Comments

@ghjm
Copy link
Contributor

ghjm commented Apr 21, 2020

  • Remove the send, ping and status subcommands from the receptor command-line. This greatly simplifies the command-line syntax because the only invocation is now node, which can be assumed - so we no longer need subcommand parsing.
  • Add parameters --control-socket=<path> and --no-control-socket to receptor. If no options are specified, the control socket defaults to something reasonable like /var/run/receptor.sock.
  • Modify the current send, ping and status entrypoints to respond to textual commands sent via the socket file, like echo status > /var/run/receptor.sock.
  • Create a new script receptorctl that provides a reasonable command-line syntax for the send, ping and status commands. All it does is validates that the command is sane and then passes it down the pipe, which is either the default or a path specified by --control-socket.

What do people think of this?

@Ichimonji10
Copy link
Contributor

I love the idea of being able to inspect a node and get information about a receptor mesh without needing to change the state of the mesh.

@ghjm
Copy link
Contributor Author

ghjm commented May 15, 2020

See ansible/receptor#223

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

No branches or pull requests

3 participants