File: ImportSpec.rst

package info (click to toggle)
python-pyvmomi 6.7.1-3
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 14,980 kB
  • sloc: python: 9,206; xml: 77; makefile: 9
file content (30 lines) | stat: -rw-r--r-- 1,276 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
.. _OvfManager: ../vim/OvfManager.rst

.. _OvfConsumer: ../vim/OvfConsumer.rst

.. _vSphere API 4.0: ../vim/version.rst#vimversionversion5

.. _vmodl.DynamicData: ../vmodl/DynamicData.rst

.. _VirtualAppImportSpec: ../vim/vApp/VAppImportSpec.rst

.. _vim.OvfConsumer.OstNode: ../vim/OvfConsumer/OstNode.rst

.. _VirtualMachineImportSpec: ../vim/vm/VmImportSpec.rst

.. _vim.vApp.EntityConfigInfo: ../vim/vApp/EntityConfigInfo.rst


vim.ImportSpec
==============
  An ImportSpec is used when importing VMs or vApps.It can be built from scratch, or it can be generated from an OVF descriptor using the service interface `OvfManager`_ .This class is the abstract base for `VirtualMachineImportSpec`_ and `VirtualAppImportSpec`_ . These three classes form a composite structure that allows us to contain arbitrarily complex entitites in a single ImportSpec.
:extends: vmodl.DynamicData_
:since: `vSphere API 4.0`_

Attributes:
    entityConfig (`vim.vApp.EntityConfigInfo`_, optional):

       Configuration of sub-entities (virtual machine or vApp). This is used for sub-entities of a vApp that could be a virtual machine or a vApp.
    instantiationOst (`vim.OvfConsumer.OstNode`_, optional):

       The instantiation OST (see `OvfConsumer`_ ) to be consumed by OVF consumers.