mirror of
https://github.com/vmware/vsphere-automation-sdk-python.git
synced 2024-11-24 18:30:00 -05:00
commit
c9c9855ae3
213
README.md
213
README.md
@ -5,24 +5,11 @@
|
|||||||
- [Supported vCenter Releases](#supported-vcenter-releases)
|
- [Supported vCenter Releases](#supported-vcenter-releases)
|
||||||
- [VMware Cloud on AWS Support](#vmware-cloud-on-aws-support)
|
- [VMware Cloud on AWS Support](#vmware-cloud-on-aws-support)
|
||||||
- [Quick Start Guide](#quick-start-guide)
|
- [Quick Start Guide](#quick-start-guide)
|
||||||
- [Installing the required Python Packages](#installing-the-required-python-packages)
|
- [Run SDK Samples](#run-sdk-samples)
|
||||||
- [Setting up a vSphere Test Environment](#setting-up-a-vsphere-test-environment)
|
|
||||||
- [Running the SDK Sample Setup Script](#running-the-sdk-sample-setup-script)
|
|
||||||
- [Running a complex sample](#running-a-complex-sample)
|
|
||||||
- [API Documentation](#api-documentation)
|
- [API Documentation](#api-documentation)
|
||||||
- [Submitting samples](#submitting-samples)
|
- [Submitting samples](#submitting-samples)
|
||||||
- [Required Information](#required-information)
|
|
||||||
- [Suggested Information](#suggested-information)
|
|
||||||
- [Contribution Process](#contribution-process)
|
|
||||||
- [Code Style](#code-style)
|
|
||||||
- [Resource Maintenance](#resource-maintenance)
|
- [Resource Maintenance](#resource-maintenance)
|
||||||
- [Maintenance Ownership](#maintenance-ownership)
|
|
||||||
- [Filing Issues](#filing-issues)
|
|
||||||
- [Resolving Issues](#resolving-issues)
|
|
||||||
- [VMware Sample Exchange](#vmware-sample-exchange)
|
|
||||||
- [Repository Administrator Resources](#repository-administrator-resources)
|
- [Repository Administrator Resources](#repository-administrator-resources)
|
||||||
- [Board Members](#board-members)
|
|
||||||
- [Approval of Additions](#approval-of-additions)
|
|
||||||
- [VMware Resources](#vmware-resources)
|
- [VMware Resources](#vmware-resources)
|
||||||
## Abstract
|
## Abstract
|
||||||
This document describes the vSphere Automation Python SDK samples that use the vSphere Automation
|
This document describes the vSphere Automation Python SDK samples that use the vSphere Automation
|
||||||
@ -39,52 +26,100 @@ Certain APIs and samples that are introduced in 6.5 release, such as vCenter, Vi
|
|||||||
The VMware Cloud on AWS API and samples are currently available as a preview and are subject to change in the future.
|
The VMware Cloud on AWS API and samples are currently available as a preview and are subject to change in the future.
|
||||||
|
|
||||||
## Quick Start Guide
|
## Quick Start Guide
|
||||||
This document will walk you through getting up and running with the Python SDK Samples.
|
|
||||||
Prior to running the samples you will need to setup a vCenter test environment and
|
|
||||||
install local Python packages, the following steps will take you through this process.
|
|
||||||
|
|
||||||
Before you can run the SDK samples we'll need to walk you through the following steps:
|
### Prepare a Python Development Environment
|
||||||
|
|
||||||
1. Installing the required Python packages
|
We recommend you to install latest [Python](http://docs.python-guide.org/en/latest/starting/installation/) and
|
||||||
2. Setting up a vSphere test environment
|
[pip](https://pypi.python.org/pypi/pip/) on your system.
|
||||||
3. Running SDK Samples setup script
|
|
||||||
|
|
||||||
### Installing the required Python Packages
|
A Python virtual environment is also highly recommended.
|
||||||
**Note:** The SDK requires Python v2.7+ (preferably v3.6) to run the setup/samples,
|
* [Install a virtual env for Python 2](https://virtualenv.pypa.io/en/stable/)
|
||||||
please make sure you have the appropriate version installed before continuing.
|
* [Install a virtual env for Python 3](https://docs.python.org/3/tutorial/venv.html)
|
||||||
If you are on macOS/OSX/Linux, please note that the system installed version of
|
|
||||||
Python may be outdated and/or not be intended for development and we recommended you [install Python](http://docs.python-guide.org/en/latest/starting/installation/) yourself before installing the required packages. [Virtualenv](https://virtualenv.pypa.io/en/stable/) is also highly recommended.
|
|
||||||
|
|
||||||
The required packages are:
|
### Installing Required Python Packages
|
||||||
|
|
||||||
* pyVmomi
|
|
||||||
* suds (suds-jurko for python3+)
|
|
||||||
* vapi-client-bindings
|
|
||||||
* vmc-client-bindings
|
|
||||||
* vapi-vmc-client
|
|
||||||
|
|
||||||
These dependencies are listed in the requirements.txt file and installed using "pip install"; For more details on how to install python packages using pip please refer to the [pip user guide](http://pip.readthedocs.io/en/latest/user_guide/).
|
|
||||||
|
|
||||||
```cmd
|
```cmd
|
||||||
pip install --upgrade --force-reinstall -r requirements.txt --extra-index-url <file:///abs_path/to/sdk/lib/>
|
git clone https://github.com/vmware/vsphere-automation-sdk-python.git
|
||||||
|
cd vsphere-automation-sdk-python
|
||||||
|
pip install --upgrade --force-reinstall -r requirements.txt --extra-index-url file:///`pwd`/lib
|
||||||
```
|
```
|
||||||
|
|
||||||
**NOTE:** The SDK also requires OpenSSL 1.0.1+ if you want to connect to vSphere 6.5+ in order to support TLS1.1 & 1.2
|
**NOTE:** The SDK also requires OpenSSL 1.0.1+ if you want to connect to vSphere 6.5+ in order to support TLS1.1 & 1.2
|
||||||
|
|
||||||
### Setting up a vSphere Test Environment
|
### Connect to a vCenter Server
|
||||||
**NOTE:** The samples are intended to be run against a freshly installed **non-Production** vSphere setup as the scripts may make changes to the test environment and in some cases can destroy items when needed.
|
|
||||||
|
|
||||||
To run the samples a vSphere test environment is required with the following configuration
|
```python
|
||||||
* 1 vCenter Server
|
import requests
|
||||||
* 2 ESX hosts
|
import urllib3
|
||||||
* 1 NFS Datastore with at least 3GB of free capacity
|
from vmware.vapi.vsphere.client import create_vsphere_client
|
||||||
|
session = requests.session()
|
||||||
|
|
||||||
Please have the details of these available but do not have any configuration pre-created on vCenter server or ESXi Hosts, for example there should be no existing datacenters, clusters or attached hosts on the vCenter server.
|
# Disable cert verification for demo purpose.
|
||||||
|
# This is not recommended in a production environment.
|
||||||
|
session.verify = False
|
||||||
|
|
||||||
### Running the SDK Sample Setup Script
|
# Disable the secure connection warning for demo purpose.
|
||||||
Before executing the samples we'll need to setup the vSphere test environment using one of the sample scripts. Before we run the script we'll need to edit one of the files and provide IP addresses for the various machine instances.
|
# This is not recommended in a production environment.
|
||||||
|
urllib3.disable_warnings(urllib3.exceptions.InsecureRequestWarning)
|
||||||
|
|
||||||
First, set PYTHONPATH to use SDK helper methods
|
# Connect to a vCenter Server using username and password
|
||||||
|
vsphere_client = create_vsphere_client(server='<vc_ip>', username='<vc_username>', password='<vc_password>', session=session)
|
||||||
|
|
||||||
|
# List all VMs inside the vCenter Server
|
||||||
|
vsphere_client.vcenter.VM.list()
|
||||||
|
```
|
||||||
|
|
||||||
|
Output in a Python Interpreter:
|
||||||
|
|
||||||
|
```shell
|
||||||
|
(venv) het-m03:vsphere-automation-sdk-python het$ python
|
||||||
|
Python 3.6.3 (v3.6.3:2c5fed86e0, Oct 3 2017, 00:32:08)
|
||||||
|
[GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin
|
||||||
|
Type "help", "copyright", "credits" or "license" for more information.
|
||||||
|
>>> import requests
|
||||||
|
>>> import urllib3
|
||||||
|
>>> from vmware.vapi.vsphere.client import create_vsphere_client
|
||||||
|
>>> session = requests.session()
|
||||||
|
>>> session.verify = False
|
||||||
|
>>> urllib3.disable_warnings(urllib3.exceptions.InsecureRequestWarning)
|
||||||
|
>>> vsphere_client = create_vsphere_client(server='<vc_ip>', username='<vc_username>', password='<vc_password>', session=session)
|
||||||
|
>>> vsphere_client.vcenter.VM.list()
|
||||||
|
[Summary(vm='vm-58', name='standalone-20e4bd3af-esx.0-vm.0', power_state=State(string='POWERED_OFF'), cpu_count=1, memory_size_mib=256),
|
||||||
|
...]
|
||||||
|
```
|
||||||
|
|
||||||
|
### Connect to VMware Cloud on AWS
|
||||||
|
|
||||||
|
```python
|
||||||
|
from vmware.vapi.vmc.client import create_vmc_client
|
||||||
|
|
||||||
|
# Connect to VMware Cloud on AWS using refresh token
|
||||||
|
vmc_client = create_vmc_client('<refresh_token>')
|
||||||
|
|
||||||
|
# Get organizations associated with calling user.
|
||||||
|
vmc_client.Orgs.list()
|
||||||
|
```
|
||||||
|
|
||||||
|
Output in a Python Interpreter:
|
||||||
|
|
||||||
|
```shell
|
||||||
|
(venv) het-m03:vsphere-automation-sdk-python het$ python
|
||||||
|
Python 3.6.3 (v3.6.3:2c5fed86e0, Oct 3 2017, 00:32:08)
|
||||||
|
[GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin
|
||||||
|
Type "help", "copyright", "credits" or "license" for more information.
|
||||||
|
>>> from vmware.vapi.vmc.client import create_vmc_client
|
||||||
|
>>> vmc_client = create_vmc_client('<refresh_token>')
|
||||||
|
>>> vmc_client.Orgs.list()
|
||||||
|
[Organization(updated=datetime.datetime(2018, 3, 2, 16, 57, 46), user_id='77aa6e6f-3257-3637-9cd9-14fae3a25b9d', updated_by_user_id='2021b5ae-890b-3472-ba9a-bc8cff776ca7', created=datetime.datetime(2017, 4, 4, 11, 57, 48, 861), version=15, updated_by_user_name='mdreyer@vmware.com', user_name='pgifford@vmware.com', id='2a8ac0ba-c93d-4748-879f-7dc9918beaa5', display_name='VMC-SET', name='j13hqg73', sla='VMC_INTERNAL', project_state='CREATED', properties=OrgProperties(values={'defaultAwsRegions': 'US_WEST_2,US_EAST_1', 'sddcLimit': '5', 'planVersion': '3.0', 'defaultHostsPerSddc': '4', 'invitationCode': '/csp/gateway/slc/api/service-invitations/aa7203c3617bbe755597b8b0ad652', 'enableAWSCloudProvider': 'true', 'enableZeroCloudCloudProvider': 'true', 'accountLinkingOptional': 'false', 'defaultPDXDatacenter': 'pdx2', 'skipSubscriptionCheck': 'true', 'minHostsPerSddc': '4', 'maxHostsPerSddc': '8', 'hostLimit': '16', 'maxHostsPerSddcOnCreate': '4', 'isAllAccess': 'true', 'enabledAvailabilityZones': '{"us-east-1":["iad6","iad7","iad12"],"us-west-2":["pdx1", "pdx4", "pdx2"]}'}), cloud_configurations={'AWS': AwsOrgConfiguration(provider='AWS')})
|
||||||
|
...]
|
||||||
|
```
|
||||||
|
|
||||||
|
## Run SDK Samples
|
||||||
|
|
||||||
|
In this section we will walk you through the steps to run the sample code for vSphere
|
||||||
|
and VMware Cloud on AWS APIs.
|
||||||
|
|
||||||
|
### First, set PYTHONPATH to use SDK helper methods
|
||||||
|
|
||||||
* Linux/Mac:
|
* Linux/Mac:
|
||||||
|
|
||||||
@ -94,7 +129,36 @@ First, set PYTHONPATH to use SDK helper methods
|
|||||||
|
|
||||||
set PYTHONPATH=%cd%;%PYTHONPATH%
|
set PYTHONPATH=%cd%;%PYTHONPATH%
|
||||||
|
|
||||||
Next, using a text editor open ../samples/vsphere/vcenter/setup/testbed.py and edit the following settings replace everything in < > brackets with your environment information. Leave the rest of the settings in this file at their default values.
|
### Run VMware Cloud on AWS Samples
|
||||||
|
|
||||||
|
```cmd
|
||||||
|
$ python samples/vmc/orgs/organization_operations.py -r <refresh_token>
|
||||||
|
```
|
||||||
|
|
||||||
|
### Run vSphere Samples
|
||||||
|
|
||||||
|
A vSphere test environment is required with the following configuration:
|
||||||
|
* 1 vCenter Server
|
||||||
|
* 2 ESX hosts
|
||||||
|
* 1 NFS Datastore with at least 3GB of free capacity
|
||||||
|
|
||||||
|
**Note** Please have the details of these available but do not have any configuration pre-created on vCenter server or ESXi Hosts, for example there should be no existing datacenters, clusters or attached hosts on the vCenter server.
|
||||||
|
|
||||||
|
#### Running the SDK Sample Setup Script
|
||||||
|
|
||||||
|
Before executing the samples we'll need to setup the vSphere test environment using one of the sample scripts (samples/vsphere/vcenter/setup/main.py). The script will perform the following:
|
||||||
|
|
||||||
|
* Create 2 test Datacenters
|
||||||
|
* Create a test Cluster
|
||||||
|
* Create Test Folders for VM Storage
|
||||||
|
* Attach the hosts
|
||||||
|
* Create a Distributed Switch
|
||||||
|
* Create a Distributed Portgroup
|
||||||
|
* Attach the NFS datastore (if Selected) to the hosts
|
||||||
|
* Copy the [Photon OS](https://vmware.github.io/photon/) ISO image downloaded from [VMware's bintray server](https://dl.bintray.com/vmware/photon) to the datastore
|
||||||
|
* Create directories to add sample ports
|
||||||
|
|
||||||
|
First, edit settings in samples/vsphere/vcenter/setup/testbed.py and replace everything in < > brackets with your environment information. Leave the rest of the settings in this file at their default values.
|
||||||
|
|
||||||
```python
|
```python
|
||||||
config["SERVER"] = "<vcenter_hostname_or_ip>"
|
config["SERVER"] = "<vcenter_hostname_or_ip>"
|
||||||
@ -111,48 +175,34 @@ config["NFS_HOST"] = "<nfs_ipaddress>"
|
|||||||
config["NFS_REMOTE_PATH"] = "/store1"
|
config["NFS_REMOTE_PATH"] = "/store1"
|
||||||
```
|
```
|
||||||
|
|
||||||
Save and close the file.
|
At this point, we're ready to run the setup script:
|
||||||
|
|
||||||
At this point, we're ready to run the setup script.
|
|
||||||
|
|
||||||
This script will perform the following:
|
|
||||||
* Create 2 test Datacenters
|
|
||||||
* Create a test Cluster
|
|
||||||
* Create Test Folders for VM Storage
|
|
||||||
* Attach the hosts
|
|
||||||
* Create a Distributed Switch
|
|
||||||
* Create a Distributed Portgroup
|
|
||||||
* Attach the NFS datastore (if Selected) to the hosts
|
|
||||||
* Copy the [Photon OS](https://vmware.github.io/photon/) ISO image downloaded from [VMware's bintray server](https://dl.bintray.com/vmware/photon) to the datastore
|
|
||||||
* Create directories to add sample ports
|
|
||||||
|
|
||||||
|
|
||||||
**Note:** The setup script may take several minutes to complete.
|
|
||||||
|
|
||||||
**To view the available command-line options:**
|
|
||||||
|
|
||||||
```cmd
|
```cmd
|
||||||
$ python ../samples/vsphere/vcenter/setup/main.py -h
|
$ python samples/vsphere/vcenter/setup/main.py -sv
|
||||||
```
|
```
|
||||||
|
|
||||||
**To run the setup script:**
|
After completion you will see from the output and also the vSphere Client that the environment has now been fully setup and is ready to easily run further samples.
|
||||||
|
|
||||||
|
To view other available command-line options:
|
||||||
|
|
||||||
```cmd
|
```cmd
|
||||||
$ python ../samples/vsphere/vcenter/setup/main.py -sv
|
$ python samples/vsphere/vcenter/setup/main.py -h
|
||||||
```
|
```
|
||||||
|
|
||||||
After completion you will see from the output and also the vSphere Webclient that the environment has now been fully setup and is ready to easily run further samples.
|
#### Run the vAPI vCenter sample suite:
|
||||||
|
|
||||||
### Running a complex sample
|
|
||||||
This SDK includes a sample script which can be used to perform a number of actions and give you an indication of how to perform multiple vCenter actions, this script is located in the /samples/vsphere/vcenter/setup/ directory, use the following instructions to run this sample:
|
|
||||||
|
|
||||||
**Run the vAPI vCenter sample suite:**
|
|
||||||
|
|
||||||
```cmd
|
```cmd
|
||||||
$ python ../samples/vsphere/vcenter/setup/main.py -riv
|
$ python samples/vsphere/vcenter/setup/main.py -riv
|
||||||
|
```
|
||||||
|
|
||||||
|
#### Run a specific sample in a standalone mode:
|
||||||
|
|
||||||
|
```cmd
|
||||||
|
$ python samples/vsphere/vcenter/vm/list_vms.py -v
|
||||||
```
|
```
|
||||||
|
|
||||||
## API Documentation
|
## API Documentation
|
||||||
|
|
||||||
The API documentation can be found [here](doc/client.zip)
|
The API documentation can be found [here](doc/client.zip)
|
||||||
|
|
||||||
## Submitting samples
|
## Submitting samples
|
||||||
@ -162,10 +212,12 @@ The API documentation can be found [here](doc/client.zip)
|
|||||||
Before you start working with this project, please read our [Developer Certificate of Origin](https://cla.vmware.com/dco). All contributions to this repository must be signed as described on that page. Your signature certifies that you wrote the patch or have the right to pass it on as an open-source patch.
|
Before you start working with this project, please read our [Developer Certificate of Origin](https://cla.vmware.com/dco). All contributions to this repository must be signed as described on that page. Your signature certifies that you wrote the patch or have the right to pass it on as an open-source patch.
|
||||||
|
|
||||||
### Sample Template
|
### Sample Template
|
||||||
|
|
||||||
[Sample template](sample_template) contains boilerplate code that can be used to build a new sample.
|
[Sample template](sample_template) contains boilerplate code that can be used to build a new sample.
|
||||||
Please copy the file and use it as a starting point to write a new sample.
|
Please copy the file and use it as a starting point to write a new sample.
|
||||||
|
|
||||||
### Required Information
|
### Required Information
|
||||||
|
|
||||||
The following information must be included in the README.md or in the sample docstring in case README already exists in same folder.
|
The following information must be included in the README.md or in the sample docstring in case README already exists in same folder.
|
||||||
* Author Name
|
* Author Name
|
||||||
* This can include full name, email address or other identifiable piece of information that would allow interested parties to contact author with questions.
|
* This can include full name, email address or other identifiable piece of information that would allow interested parties to contact author with questions.
|
||||||
@ -174,6 +226,7 @@ The following information must be included in the README.md or in the sample doc
|
|||||||
* Any KNOWN limitations or dependencies
|
* Any KNOWN limitations or dependencies
|
||||||
|
|
||||||
### Suggested Information
|
### Suggested Information
|
||||||
|
|
||||||
The following information should be included when possible. Inclusion of information provides valuable information to consumers of the resource.
|
The following information should be included when possible. Inclusion of information provides valuable information to consumers of the resource.
|
||||||
* vSphere version against which the sample was developed/tested
|
* vSphere version against which the sample was developed/tested
|
||||||
* SDK version against which the sample was developed/tested
|
* SDK version against which the sample was developed/tested
|
||||||
@ -194,18 +247,25 @@ Please conform to pep8 standards. Check your code by running the pep8 tool.
|
|||||||
|
|
||||||
## Resource Maintenance
|
## Resource Maintenance
|
||||||
### Maintenance Ownership
|
### Maintenance Ownership
|
||||||
|
|
||||||
Ownership of any and all submitted samples are maintained by the submitter.
|
Ownership of any and all submitted samples are maintained by the submitter.
|
||||||
|
|
||||||
### Filing Issues
|
### Filing Issues
|
||||||
|
|
||||||
Any bugs or other issues should be filed within GitHub by way of the repository’s Issue Tracker.
|
Any bugs or other issues should be filed within GitHub by way of the repository’s Issue Tracker.
|
||||||
|
|
||||||
### Resolving Issues
|
### Resolving Issues
|
||||||
|
|
||||||
Any community member can resolve issues within the repository, however only the board member can approve the update. Once approved, assuming the resolution involves a pull request, only a board member will be able to merge and close the request.
|
Any community member can resolve issues within the repository, however only the board member can approve the update. Once approved, assuming the resolution involves a pull request, only a board member will be able to merge and close the request.
|
||||||
|
|
||||||
### VMware Sample Exchange
|
### VMware Sample Exchange
|
||||||
|
|
||||||
It is highly recommended to add any and all submitted samples to the VMware Sample Exchange: <https://code.vmware.com/samples>
|
It is highly recommended to add any and all submitted samples to the VMware Sample Exchange: <https://code.vmware.com/samples>
|
||||||
|
|
||||||
Sample Exchange can be allowed to access your GitHub resources, by way of a linking process, where they can be indexed and searched by the community. There are VMware social media accounts which will advertise resources posted to the site and there's no additional accounts needed, as the VMware Sample Exchange uses MyVMware credentials.
|
Sample Exchange can be allowed to access your GitHub resources, by way of a linking process, where they can be indexed and searched by the community. There are VMware social media accounts which will advertise resources posted to the site and there's no additional accounts needed, as the VMware Sample Exchange uses MyVMware credentials.
|
||||||
|
|
||||||
## Repository Administrator Resources
|
## Repository Administrator Resources
|
||||||
|
|
||||||
### Board Members
|
### Board Members
|
||||||
|
|
||||||
Board members are volunteers from the SDK community and VMware staff members, board members are not held responsible for any issues which may occur from running of samples from this repository.
|
Board members are volunteers from the SDK community and VMware staff members, board members are not held responsible for any issues which may occur from running of samples from this repository.
|
||||||
@ -215,6 +275,7 @@ Members:
|
|||||||
* Steve Trefethen (VMware)
|
* Steve Trefethen (VMware)
|
||||||
|
|
||||||
### Approval of Additions
|
### Approval of Additions
|
||||||
|
|
||||||
Items added to the repository, including items from the Board members, require 2 votes from the board members before being added to the repository. The approving members will have ideally downloaded and tested the item. When two “Approved for Merge” comments are added from board members, the pull can then be committed to the repository.
|
Items added to the repository, including items from the Board members, require 2 votes from the board members before being added to the repository. The approving members will have ideally downloaded and tested the item. When two “Approved for Merge” comments are added from board members, the pull can then be committed to the repository.
|
||||||
|
|
||||||
## VMware Resources
|
## VMware Resources
|
||||||
|
Loading…
Reference in New Issue
Block a user