-
Notifications
You must be signed in to change notification settings - Fork 13
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
EVE Discovery service: move allow_to_discover
to AppInst port
#52
Conversation
I see yetus error
But I marked field 24 as reserved, not sure we should leave it there |
proto/config/netconfig.proto
Outdated
@@ -55,6 +55,10 @@ message NetworkAdapter { | |||
// valid vlan id range: 2 - 4093 | |||
// vlan id 1 is implicitly used by linux bridges | |||
uint32 access_vlan_id = 41; | |||
|
|||
// allow AppInstance to discover other AppInstances | |||
// attached to its network instances. default is false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this say "to this network instance" in singular?
Or to the network instance attached to this adapter?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
renamed to "this network instance"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but some comment nits
This is more granular approach. From appInstance perspective, you also know which network port will be used. Signed-off-by: Pavel Abramov <uncle.decart@gmail.com>
Signed-off-by: Pavel Abramov <uncle.decart@gmail.com>
b9724ca
to
d46864c
Compare
PR lf-edge#46 accidently added allow_to_discover field to app_instance which was removed in lf-edge#52 Not deprecating field number 25 (allow_to_discover) because we haven't had released EVE with this API yet, so we don't have to do this Signed-off-by: Pavel Abramov <uncle.decart@gmail.com>
This is more granular approach. From appInstance perspective,
you also know which network port will be used.