-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Vrf stuff #537
Vrf stuff #537
Conversation
Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
1) Cleanup SA warnings, more to come 2) Cleanup some non debug guarded zlog_info code Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
Segregate the vrf enable/disable functionality from other vrf code. This is to ensure that people are not actually using the functions when they should not be. Also document the why of it properly in the new vrf_int.h header. Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
vrf_iflist_create -> By the time this is called in enable, the vrf's iflist is already created. Additionally this code should be a properly of the vrf to init/destroy not someone else. vrf_iflist_terminate -> This function should be a property of vrf deletion and does not need to be exposed. Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
We only needed to add/change the vrf callbacks when we initialize the vrf subsystem. As such it is not necessary to handle the callbacks in any other way than through the init function. Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
Changing vrf api subtly so wanted some people to look at it, that is why I have asked for your review if you are wondering :) |
Continous Integration Result: FAILEDSee below for issues. This is a comment from an EXPERIMENTAL automated CI system. Get source and apply patch from patchwork: SuccessfulBuilding Stage: FailedFreeBSD10 amd64 build: Successful FreeBSD9 amd64 build: FailedFreeBSD9 amd64 build: Unknown Log <log_pytests.txt> Ubuntu1204 amd64 build: FailedUbuntu1204 amd64 build: Unknown Log <log_pytests.txt> Ubuntu1404 amd64 build: FailedUbuntu1404 amd64 build: Unknown Log <log_pytests.txt> Debian8 amd64 build: FailedDebian8 amd64 build: Unknown Log <log_pytests.txt> FreeBSD11 amd64 build: FailedFreeBSD11 amd64 build: Unknown Log <log_pytests.txt> OpenBSD60 amd64 build: FailedOpenBSD60 amd64 build: Unknown Log <log_pytests.txt> NetBSD6 amd64 build: FailedNetBSD6 amd64 build: Unknown Log <log_pytests.txt> NetBSD7 amd64 build: FailedNetBSD7 amd64 build: Unknown Log <log_pytests.txt> Fedora24 amd64 build: FailedFedora24 amd64 build: Unknown Log <log_pytests.txt> Ubuntu1604 amd64 build: FailedUbuntu1604 amd64 build: Unknown Log <log_pytests.txt> CentOS7 amd64 build: FailedCentOS7 amd64 build: Unknown Log <log_pytests.txt> CentOS6 amd64 build: FailedCentOS6 amd64 build: Unknown Log <log_pytests.txt> |
@mwinter-osr Looks like something has gone completely wrong with the CI system here. Can you take a look? |
It is a real failure, but my parsing of the log_pytest failed. Commit breaks the 'make check'. |
Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
data is actually allowed to be NULL. So allow pass in. Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
Continous Integration Result: FAILEDSee below for issues. This is a comment from an EXPERIMENTAL automated CI system. Get source and apply patch from patchwork: SuccessfulBuilding Stage: FailedOpenBSD60 amd64 build: Successful Ubuntu1604 amd64 build: FailedUbuntu1604 amd64 build: Unknown Log <log_snapcraft.txt> |
Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
Continous Integration Result: SUCCESSFULCongratulations, this patch passed basic tests Tested-by: NetDEF / OpenSourceRouting.org CI System CI System Testrun URL: https://ci1.netdef.org/browse/FRR-FRRPULLREQ-700/ This is a comment from an EXPERIMENTAL automated CI system. |
Continous Integration Result: SUCCESSFULCongratulations, this patch passed basic tests Tested-by: NetDEF / OpenSourceRouting.org CI System CI System Testrun URL: https://ci1.netdef.org/browse/FRR-FRRPULLREQ-701/ This is a comment from an EXPERIMENTAL automated CI system. |
Looks good to me, tough maybe it should've been 2 PRs, one with the SA fixes and one with the VRF stuff :) Either way if no one else comments I'll merge this in the evening [EU]. |
Cleanup some SA issues found in coverity
Cleanup the vrf.h api some