Search queries sometimes return error 400 with:
error_code: 60508
error_message: 'Indexing is in progress, please retry after sometime.
This patche will retry the request on this error.
Change-Id: Id47886ba0e72ea946dcf07ae0bdbc81fef1dd4f0
New function under core_resources/NsxLibMetadataProxy to retrieve
md_proxy status.
Change-Id: I9b4e8520965878c949bee5129fa5c20a4b80671d
Signed-off-by: Michal Kelner Mishali <mkelnermishal@vmware.com>
The following methods now have the ability to add tags:
- add_fip_nat_rules
- add_gw_snat_rule
- add_nat_rule
Change-Id: I6dc34ab3749ff4a5f1a575f407d8474538c69f96
In NSX 2.2 & up, there is a logical router advanced config of
an overlay transport-zone-id.
Also adding a router api to get the tier0 router overlay TZ to
be used here.
Change-Id: I3a447202785b7b6ac320ddbb6a3f2cdeac1f78aa
1. Add support for the transport nodes resource basic operations
2. Use it for getting the list of TZ of a tier0 router
Change-Id: I381c947044454c04efbc1c38ed7691ef8213ffef
ostestr is no longer installed by default by infra and will be totally
removed longer term; stestr [1] is its replacement.
This is the reason out gate is failing with the following today:
nsx/tools/ostestr_compat_shim.sh: ostestr: not found
This patch moves us to stestr by:
- Updating tox.ini to use stestr rather than call ostestr_compat_shim.sh
and in turn ostestr.
- Removing ostestr_compat_shim.sh as its no longer used.
Change-Id: I1f97df69500058a7d330f7be5735a54c68f35559
The NSX policy manager changed the supported apis:
- Use PATCH instead of POST
- Remove the Communication profiles
- Add ID to communication maps, and allow multiple maps
Change-Id: I8cb2dd21892fd9e0878653f5667187fef76a3315
The NSX policy rules changed on the nSX.
The session rules will always be 'protect' rules,
and bypass rules were added to the vpn service.
Change-Id: I2dbf54544e7b49b828c5372f792e55fb1bd19d7c
The NsxLibApiBase can have the nsxlib_config passed as None.
In order to use the retry logic we retrieve the max_attempts from
the client object. This is always set.
Change-Id: I4ac60f9a3d89b60d9b35390825578cb7f849dfa8
Rate limit is returned as a part of node/services/http response
In order to update one should:
1. GET the current configuration
2. PUT the updated configuration (the http response will be 202)
3. POST a restart action request (the http response will be 202)
Change-Id: I35a05f9810832e9a22ec9db43f167f13df0744a4
- Allow passing direct members when creating a new NSGroup
- Allow removing membership_criteria when updating a NSGroup
Change-Id: Ib0e5f5193f2d9ed455e0918fdf67da7a0acfdb62
Adit Sarfaty