Vsphere-automation-sdk

Latest version: v0.0.1

Safety actively analyzes 688961 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 3

7.0.0.0

What’s New

VMware Cloud on AWS (VMC on AWS)

NSX
- New API specifications for NSX-T Policy API
- Updated API bindings for NSX-T Policy, NSX VMC Policy, and NSX VMC AWS Integration
VMC Console
- Updated APIs to get compatible subnets for a linked AWS account with an additional parameter (linked connected account identifier or linked Account Id)
- Delete SDDC API no longer supports forceful delete. Parameter "force" has been removed.

DRaaS
- Removed following APIs
-- Create audit setup task for specific appliance and configure rsyslog for it
-- Upload backup script to specific appliance
- Updated API to deactivate site recovery for a specific SDDC.

vSphere
This release contains following new/updated features.
- VSTATS(Tech Preview APIs) and samples
- vCenter Guest Customisation APIs
- VM Guest APIs and samples
- VM Life Cycle Management APIs(clone and relocate)
- Resource Pool APIs (create and delete)

Note: clone the SDK repository to get the most recent VMC API bindings

6.9.1

What’s New
pip Installation from GitHub repository
Ability to install the SDK package directly from the GitHub repository using `pip`
- `pip install --upgrade pip setuptools`
- `pip install --upgrade git+https://github.com/vmware/vsphere-automation-sdk-python.git`

Refer to following pull requests
- pip install from repository : 164
- updating new installation instructions : 165
- Optimized setup.py for version control 166

VMware Cloud on AWS (VMC on AWS)
- VMware Cloud on AWS library now includes APIs for Disaster Recovery as Service (DRaaS). With this version, users can automate the setup and the configuration of site recovery for a specified SDDC using DRaaS APIs.

vSphere
- vSphere library now supports VMware Certificate Authority (VMCA) root certificate, check-out VMs managed by content library, and a new appliance API to change hostname/IP of vCenter appliance.

6.8.7

What's New

- Updated VMware Cloud on AWS Console API bindings
- Updated VMware Cloud on AWS SDDC API bindings
- Updated NSX Manager, NSX Policy, NSX VMC Policy and NSX VMC AWS Integration API bindings
- New bindings and samples for Convergence and Decommission APIs
- New bindings for Content Library VMTX_Sync APIs
- New bindings and samples for Token Exchange and query External Identity Providers APIs

6.8.1

- Updated VMware Cloud on AWS Console API bindings
- Updated VMware Cloud on AWS SDDC API bindings
- Added Compute Policy API bindings
- Add compute Policy API samples
- Remove doc folder. The API specs are hosted on gh-pages branch now. The API doc links can be found on the main README.

6.8.0

- Updated bindings and samples for VMware Cloud on AWS APIs
- Added bindings for NSX APIs
- Added HVC samples

6.7.0

What's New

The vSphere Automation SDKs for vSphere 6.7 includes new APIs for:

- Storage Policy
- Guest Ops
- vCenter Server Appliance and Platform Services Controller appliance deployment
- Installing and Upgrading the vCenter Server Appliance and Platform Services Controller appliance stage 2
- Importing the historical data of vCenter Server
- Scheduling a backup job
- Updating the vCenter Server Appliance
- Managing and recovering the vCenter Server Appliance

Invoke vSphere APIs via the new vSphere Client module.

Refer to [quick start guide](https://github.com/vmware/vsphere-automation-sdk-python#connect-to-a-vcenter-server) for detailed usage.

Caveats and Limitations

The vcenter API includes the following methods that have known issues and might be removed in a future version. It is advised that these APIs are not invoked:

- DeploymentType.reconfigure
- PscRegistration.repoint
- Upgrade.cancel
- Deployment.rollback

Known Issues

- Unauthenticated exception following long-running operation

After an API client completes a long-running operation, such as an upload to the content library, the next operation might fail with an "Unauthenticated exception" message. This happens if the long running operation did not complete within the lifetime of the authentication session.

**Workarounds**:

- Keep the session alive by issuing short operations on another thread until the long running operation completes.
- Increase the session length using the VMware vSphere Web Client. Select Administration > System Configuration > Services > vAPI Endpoint > Manage> General, and increase the value for the Maximum session idle time.

- A couple of service endpoints under vCenter namespace are not accessible through the vSphere Client module.

ovfs, vcenter-inventory, iso, hvc and vm_template API endpoints are not accessible through the vSphere client module.

**Workaround**

Please use the legacy invocation mechanism demonstrated in the corresponding samples to access above API endpoints.

Page 2 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.