Skip to content

doc/rtd/topics/datasources/ovf.rst: fix doc8 errors #533

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
OddBloke merged 2 commits into from
Aug 13, 2020
Merged

doc/rtd/topics/datasources/ovf.rst: fix doc8 errors #533

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
349c0d8
doc/rtd/topics/datasources/ovf.rst: fix doc8 errors
OddBloke Aug 13, 2020
7297455
Merge branch 'master' into doc
OddBloke Aug 13, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 10 additions & 4 deletions doc/rtd/topics/datasources/ovf.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,12 +13,18 @@ source code tree in doc/sources/ovf

Configuration
-------------
On VMware platforms, VMTools use is required for OVF datasource configuration settings as well as vCloud and vSphere admin configuration. User could change the VMTools configuration options with command:
vmware-toolbox-cmd config set <section> <key> <value>
On VMware platforms, VMTools use is required for OVF datasource configuration
settings as well as vCloud and vSphere admin configuration. User could change
the VMTools configuration options with command::

vmware-toolbox-cmd config set <section> <key> <value>

The following VMTools configuration options affect cloud-init's behavior on a booted VM:
* a: [deploypkg] enable-custom-scripts
If this option is absent in VMTools configuration, the custom script is disabled by default for security reasons. Some VMware products could change this default behavior (for example: enabled by default) via customization specification settings.
* a: [deploypkg] enable-custom-scripts
If this option is absent in VMTools configuration, the custom script is
disabled by default for security reasons. Some VMware products could
change this default behavior (for example: enabled by default) via
customization specification settings.

VMWare admin can refer to (https://github.com/canonical/cloud-init/blob/master/cloudinit/sources/helpers/vmware/imc/config.py) and set the customization specification settings.

Expand Down