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
When building the native dhcp server config we use the dns domain/nameservers
from the network/subnet objects.
If not defined, we use the global values in the nsxlib config.
Now adding optional default parameters to be used instead of global ones.
This will enable using different configuration per network availability zone.
Change-Id: I38b458e2c530f29a0e5518257ed3041d0610df25
In nsxlib configuration, replace client certificate file with a
broader concept of provider: apart from certificate file name, the
provider can implement __enter__ and __exit__ routines to handle
file creation and disposal
Change-Id: I0c11107324786cf0852b054f32940422dffef5bb
Add client_cert_file to nsxlib initialization.
If specified, nsxlib will authenticate with client certificate.
If unspecified (default), basic user/pwd authentication is used.
Change-Id: If36841e9fd9701fa173ffa294732415dc07d49e7
Client certificate authentication will replace basic authentication.
A single client certificate will be generated by admin for the
configuration agent (openstack, container,..).
This commit focuses on certificate generation and coordination of
certificate management on backend, storage and in the agent itself.
Change-Id: Ib00e2c00aecb53cec63a746e9db6829a5594eb3a
Sometimes function under test makes multiple calls to the backend,
and being able to provide list of different responses would improve
test coverage.
Change-Id: I27a8cefe28287d25ed5411d44c6e2cc6f0a0701e
The NSX3Client did not get the nsx managers IPs, and they where missing
from error messages.
To fix this, and also better fix a similar problem with max_attempts,
the client init method may get another instance of the client, and copy
relevant information from it.
This option is used by the copy-constructor "new_client_for" without the
RestClient class being aware of arguments relevant only to the NSXClient.
Also adding a new test for a resource error message, to make sure it contains
the nsx_manager ip.
(Cherry picked from : I9e7e28eb5fd69ace44547d40cf8cd09e2457c5ed)
Change-Id: I5066ae12aadd286ff880c8545df99a567aeddbeb
Anna Khmelnitsky