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
So here is a strong opinion that is weakly held. I would like for us to discuss this in detail.
I believe that auraed should only start by exposing gRPC server a unix domain socket, as well as a server bound to the special loopback interface loman. Additionally I think auraed should reserve TCP port 57 for its default port.
/var/aurae/aurae.sock
127.0.0.1
::1
Additional Network Devices
I believe we should be able to start auraed and pass configuration to the daemon at runtime to provision gRPC servers attached to various devices.
However we expose the network devices should be uniform and there should be no different between configuring a network device via the command line, or via the gRPC server APIs.
The text was updated successfully, but these errors were encountered:
I want to be clear that we also should be able to configure network devices exactly as they are implied above using the network subsystem that @taniwha3 defined here
So here is a strong opinion that is weakly held. I would like for us to discuss this in detail.
I believe that
auraed
should only start by exposing gRPC server a unix domain socket, as well as a server bound to the special loopback interfacelo
man. Additionally I thinkauraed
should reserve TCP port 57 for its default port.Additional Network Devices
I believe we should be able to start
auraed
and pass configuration to the daemon at runtime to provision gRPC servers attached to various devices.Some syntax such as this.
However we expose the network devices should be uniform and there should be no different between configuring a network device via the command line, or via the gRPC server APIs.
The text was updated successfully, but these errors were encountered: