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.7 KiB
vim.OvfManager.ResourceMap
Maps source child entities to destination resource pools and resource settings. If a mapping is not specified, a child is copied as a direct child of the parent.
- extends
- since
deprecated
- Attributes:
-
source (str):
Identifies a source VirtualSystem or VirtualSystemCollection in an OVF descriptor. The source cannot be the root VirtualSystem or VirtualSystemCollection of the OVF. This is a path created by concatenating the OVF ids for each entity, e.g., "vm1", "WebTier/vm2", etc.
parent (vim.ResourcePool, optional):
The parent resource pool to use for the entity. This must specify a resource pool that is not part of the vApp. If this is specified, a linked child (as opposed to a direct child) is created for the vApp.
resourceSpec (vim.ResourceConfigSpec, optional):
An optional resource configuration for the created entity. If not specified, the resource configuration given in the OVF descriptor is used.
datastore (vim.Datastore, privilege: Datastore.AllocateSpace, optional):
A client can optionally specify a datastore location in the resource map to override the default datastore passed into CreateImportSpec field. This enables importing to different compute resources that do not have shared datastores.