Urllib3 Retry class's increment method has been used and we don't
understand why. Since it's impossible to add logs directly in Retry class,
this patch subclasses Retry and adds logging capabilities to log
server response and relevant cause if we hit this bug again
Signed-off-by: rmiao106 <rmiao@vmware.com>
Change-Id: I2bd13ee635879a343c7a05886b397b3ffda5006a
This patch adds an optional 'service_id' parameter to multicast
enablement / disablement methods to allow multicast to be set
also for locale-services whose id was not auto-generated by
vmware-nsxlib.
Change-Id: I68d0149179eea3177252f4986ce1b2d085b0950b
This patch allow for enabling or disabling multicast on a Tier-1 GW
router. This is simply done by setting a boolean flag in the router's
multicast configuration, which is however a sub-attribute of the
Tier-1 GW object accessed via its own API endpoint.
For the above reason, this patch introduces a definition object for
the Tier-1 Multicast settings.
Change-Id: I8308442ecd9b4d14f4ceb0ea55c4dcd4ee240e17
Add two parameters access_log_enabled and log_significant_event_only
They're supported since nsx-t 3.0.0.
1. for policy, it needs to add extra parameters.
2. for manager, ** kargs supports more parameters, nothing changed.
Change-Id: I2b313eef80def69e17d664022ae2074950812897
This change support create/update LB pool with tcp multiplexing
enabled and tcp multiplexing number.
Change-Id: I3c39bc2b4b07f138a2ac3d3efbdccd80929cc3b2
1. For MP, add logging parameter in snat rule creating api
2. For Policy, change parameter name from log to logging for tier0
and tier1 snat rule object.
Change-Id: I4f03fa6a35f138a7112782d58a1cc5a4b1648d61
In case of none default enforcement point value, the Segment
create might fail, because it is hard coded to use default ep
for querying transport zone, if specified. This change add
support for creating segment with transport zone in none default
enforcement point
Change-Id: Id122f9591c2bded5edc43fad514e6e1e9e6a9fa3
- Expose Building DHCP Config V4 and V6 in NsxPolicyTier1SegmentApi
- Update update_advertisement_rules to allow batch removal of existings
rules via prefix matching even if no new rules are to be added
Change-Id: I215630fb2af41d71431774d88129c08c4aeac904
Whenever the cluster in initialized, new loops for keepalive validation
are created.
The old loos should be stopped to not overload the nsx with keepalive checks.
Change-Id: I6ae746ba11457c141814424f42e9a0c0e2684601
- Add censoring of sensitive headers from being logged in _proxy()
- Fix issue where Cookie and X-XSRF-TOKEN were not censored as intended
Change-Id: I14b422a25b40d0014c05226f9ae4fe8be75e33fb
In addition to status code, also log error message and
local NSX time for failed NSX authentication for
easier troubleshooting for failed JWT authentication and
potential clock drift between NSX, VC and Master node.
Change-Id: Icf31477bffda85ba73a1123232b6aa5503066922
Since the NSX fix the certificate pem when creating it, we should
do the same when comparing a new one to existing ones.
Change-Id: I7da39447869c7ec2a99820676b6fb75b0a098acf
This patch adds an option to collect per cluster or per endpoint API
call records during _proxy() call. This enables client side API auditing
without the need to rely on NSX support bundles. By default this option
is disabled.
Change-Id: Ied30d90fc745d5009850c1c83c74eacd46d5fbd9
If IP block is created by Policy API, we need
{'X-Allow-Overwrite': 'true'} in header to delete subnet
Change-Id: Ib05437fef32d2ea206ee5af67b441f710d6f5016
asarfaty
Enhao Cui
Zuul
Salvatore Orlando
rmiao106
Tao Zou
Erica Liu
sean
Anna Khmelnitsky
Shawn Wang
Xiaotong Luo
lxiaopei
Shih-Hao Li
Danting Liu