The NSX does not except few characters in the LS display name.
Replace those with '.' before creating or updating the LS name
Change-Id: I1fc4bb1530e37f09f61f92713c09ad0307e12d47
The following methods now have the ability to name nat rules:
- add_fip_nat_rules
- add_gw_snat_rule
- add_nat_rule
Change-Id: I62b36fcec1a53b6d2c0c0b64c9dcb4200c9b0ae9
Adding flag ro mark the support of new NAAT rules actions in version
2.2, and adding validation for this field on create & update.
Change-Id: I4d99193caac6940911cc071016359a1361428967
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
A small refactor to the nsxlib:
1. change the security object code to be more similar to the other resources
2. Use retry code in base resources class only and not in resources
implementations
3. generelize the resource update code, to avoid duplications in different
classes
4. Adding some tests to verify the fix does not damage anything
Change-Id: Iac2cc1d55d3525ad21cb6399da691e212d6d4722
Adding support for trunk vlan for logical switches in NSX 2.2 and up
This flag can be used for guest vlan, and is mutual exclusive from
the vlan id.
Change-Id: I0d08a84df796c226678a27c29cdd1e637f356e72
This patch adds support to retrieve resources of type
VirtualMachines and VirtualNetworkInterface.
Change-Id: I9d551e35e68cbaadbe2787f23775296f61c0e72d
Adding a caching mechanism to remember previous results of get commands
and return them if they are not too old.
This mechanism is disabled for most of the nsxlib resources, and used only
by a few resources that are accessed frequently and modifies rarely
such as transport zones.
Change-Id: I4c1c723ee878feab9a86ff9015246c9e1773bd8b
Using the load balancing related args for the router
update_advertisement should be done only if the NSX version
supports the load balancing feature.
Change-Id: I1a94ee58e6b8908e6122a69f6515dfdf2d2c1b28
Adding a new api to update the server url, secret or edge cluster
of a metadata proxy server on the nsx.
Change-Id: I702398f254a1329299ec2cb82e214caf0ae59a9c
Create/update a router port with a DHCP service UUID
This will be supported only if the nsx version is 2.0.0
or above.
Change-Id: I0843fd91e1631bec80ec19e9fa1edcc013523c28
On the NSX each resource has a resource-type and could be searched by it.
The new property of the resources can be used when using search_by_tags
Change-Id: I120bc9e31faa2bebb13f24a0ccbac314f8b2a1bf
Support different methods for deleting router nat rules
- delete a single rule with gw-ip
- delete a single rule with gw-ip and source ip
- delete all rules matching a gw-ip
Change-Id: Id43a2ced7d6526f538f485f345c20ba44673c7b2
1. Support updating of shaping in both direction in the same call
2. Deprecate the old api for update shaping
3. Allow updating the profile tags
Change-Id: I34ae54b7c4b5810694e4ea05265421c8e4c903d8
Adding nat_pass parameter to router NAT rules creation.
The backend default value for this parameter is True, meaning the
firewall rules will be bypassed.
So this is also the default of the api, for backwards compatibility.
This parameter is acceptable only since nsx v2, so the api needs the
ability to check the supported features before creating the request body.
For that use, the core_resources will now get the nsxlib object at init.
Change-Id: I7c9dfe13a146a47b180fc3df2d4d6174f252e0a3
This patch changes the class of some nsxlib resources to match the ones
in core_resources, and moves some resources between the 2 files.
The recommended way to consume all nsxlib resources is through the nsxlib object.
Some resources were duplicated and now unified into one.
This change is backwards compatible, leaving old classes at their old location
with deprecation warnings.
Change-Id: I3093cab65ee73af560c89c9fef12cab5e6167acb
NSX policy is conceptually a separate endpoint, with a different
set of managed objects, but same connection management funtionality.
NsxLib user might want to have two instances of the library (based
on different configurations), one for policy and one for core nsx api.
Note: This patch will require adjustments in vmware_nsx UTs, due to
resource mocks.
Change-Id: I0d3660a8f9092bcf4e2fb4bf93e86c0dc7be7aaa
Adit Sarfaty