You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.
When studying logs and weave status output, it can get tiresome to keep mapping from the identity you know ("this is the node I run on EC2") to the hex peer-name used internally by Weave.
I propose that weave fetches the hostname of its container and displays it alongside the hex peer-name. It would also need to include this information in gossip messages so it is included in weave status on other peers.
The user would set the hostname by adding something like --hostname=ec2_node on the end of the weave launch command.
The text was updated successfully, but these errors were encountered:
When studying logs and
weave status
output, it can get tiresome to keep mapping from the identity you know ("this is the node I run on EC2") to the hex peer-name used internally by Weave.I propose that weave fetches the hostname of its container and displays it alongside the hex peer-name. It would also need to include this information in gossip messages so it is included in
weave status
on other peers.The user would set the hostname by adding something like
--hostname=ec2_node
on the end of theweave launch
command.The text was updated successfully, but these errors were encountered: