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

[schema] Add VNET Route tables in config_db #279

Merged

Conversation

weixchen1215
Copy link
Contributor

  • VNET_ROUTE
  • VNET_ROUTE_TUNNEL

common/schema.h Outdated
@@ -178,6 +178,9 @@ namespace swss {
#define CFG_VNET_TABLE_NAME "VNET"
#define CFG_NEIGH_TABLE_NAME "NEIGH"

#define CFG_VNET_RT_TABLE_NAME "VNET_ROUTE"
#define CFG_VNET_RT_TUNNEL_TABLE_NAME "VNET_ROUTE_TUNNEL"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

align with the spaces?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok. Will fix it

@prsunny
Copy link
Contributor

prsunny commented May 23, 2019

@weixi, can you please use space instead of tab to align. Its still not aligned.

@weixchen1215 weixchen1215 changed the title Add VNET Route tables in config_db [schema] Add VNET Route tables in config_db May 23, 2019
@prsunny
Copy link
Contributor

prsunny commented May 23, 2019

retest this please

3 similar comments
@weixchen1215
Copy link
Contributor Author

retest this please

@lguohan
Copy link
Contributor

lguohan commented May 24, 2019

retest this please

@lguohan
Copy link
Contributor

lguohan commented May 24, 2019

retest this please

Copy link
Contributor

@stcheng stcheng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thx

@prsunny prsunny merged commit 9e5e47e into sonic-net:master May 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants