15f7be9a52
This external documentation for pyVmomi was generated using Googly Docs (aka Google Standard Documentation) which renders very cleanly in GitHub. Internal documentation for a class should be done in Sphinx format because tools like pyCharm and Eclipse can use that documentation as a hint for code completion. Note: External docs as Googly Docs, internal docs as Sphinx. Closes bug#15
1.8 KiB
vim.OvfManager.CreateImportSpecResult
The CreateImportSpecResult contains all information regarding the import that can be extracted from the OVF descriptor.For example, this includes the list of items that the caller must upload in order to complete the import, but not the list of URLs to which the files must be uploaded. These paths are not known until the VMs have been created, ie. until ResourcePool.importVApp has been called.
- extends
- since
- Attributes:
-
importSpec (vim.ImportSpec, optional):
The ImportSpec contains information about which VirtualMachine s and VirtualApp s are present in the entity and how they relate to each other.
fileItem (vim.OvfManager.FileItem, optional):
The files that must be uploaded by the caller as part of importing the entity.The files must be uploaded in order, because some of them may be delta files that patch already-uploaded files.
warning (vmodl.LocalizedMethodFault, optional):
Non-fatal warnings from the processing. The ImportSpec will be valid, but the user may choose to reject it based on these warnings.
error (vmodl.LocalizedMethodFault, optional):
Errors that happened during processing. Something will be wrong with the ImportSpec, or it is not present.