-
Notifications
You must be signed in to change notification settings - Fork 20
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
check license from nsxt side #496
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TaoZou1
force-pushed
the
license
branch
2 times, most recently
from
January 22, 2024 02:53
210374d
to
35a18bf
Compare
/e2e |
TaoZou1
force-pushed
the
license
branch
2 times, most recently
from
January 26, 2024 09:17
60a5653
to
4c6c7a8
Compare
dantingl
reviewed
Jan 29, 2024
TaoZou1
force-pushed
the
license
branch
5 times, most recently
from
February 6, 2024 01:21
3d85843
to
cd94db8
Compare
dantingl
reviewed
Feb 18, 2024
TaoZou1
force-pushed
the
license
branch
3 times, most recently
from
February 19, 2024 02:31
42e0fa8
to
996bc0e
Compare
dantingl
reviewed
Feb 19, 2024
TaoZou1
force-pushed
the
license
branch
3 times, most recently
from
February 19, 2024 10:25
9006ec3
to
eeb58ff
Compare
dantingl
reviewed
Feb 20, 2024
While init, it will check the license from nsxt side. If CONTAINER license is disable, it will reboot. If DFW license is disable, security policy will be only response for DELETE operation. It will run a routine to check license periodically. If there is no DFW license, it will check license more frequently SecurityPolicy controller will check if error is invalid license error. Test Done: no CONTAINER license 1. if no CONTAINER license, nsx-operator should reset CONTAINER license enable, DFW disable 1. nsx-operator could bootup 2. security policy failed to create or update 3. security policy could be deleted CONTAINER license enable, DFW enable -> CONTAINER/DFW disable 1. nsx-operator restart due to DFW changed no DFW license, but nsx-operator try to create security policy 1. nsx-operator restart due to invalid license error
dantingl
approved these changes
Feb 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While init, it will check the license from nsxt side. If CONTAINER license is disable, it will reboot. If DFW license is disable, security policy will be only response for DELETE operation. It will check license periodically.