After seeing others come ask for help in IRC I decided to start
reoganizing the project documentations. It has grown into useful docs
for developers and users alike, however it lacks organization and focus.
The first step was to clean up the table of contents (TOC) to provide
sections and to take a first attempt at organizing the ordering and
renaming topics. This is to help point users asking for help.
Next some pages were serving multiple purposes or were not clear, so
capabilities, which was largely CLI focused, and moreinfo, where done
away with and the cli and faq pages created with their content and
filled in.
The remaining pages got additional examples and visual cleanups to aid
in viewing them.
Here is a summary page by page:
- analyze.rst: added output examples
- availability.rst: more complete list of clouds & distros
- boot.rst: clean up formatting, organize sections
- cli.rst: formerly capabilities.rst, focused on CLI
- datasource.rst: cleanup outupt
- faq.rst: formerly moreinfo.rst, focused on help and media links
- index.rst: organize TOC and add better description of project
VMWware: add option into VMTools config to enable/disable custom script.
VMWware customization already has support to run a custom script during
the VM customization. Adding this option allows a VM administrator to
disable the execution of customization scripts. If set the script
will not execute and the customization status is set to
GUESTCUST_ERROR_SCRIPT_DISABLED.
Add support for detecting netfailover[1] device 3-tuple in networking
layer. In the Oracle datasource ensure that if a provided network
config, either fallback or provided config includes a netfailover master
to remove any MAC address value as this can break under 3-netdev
as the other two devices have the same MAC.
* Create makefile and tox targets for documentation building and testing
to better replicate the live web docs using the same theme.
* Created docs.rst to explain how to build and contribute to documentation
with style guide and tips.
* doc/rtd/conf.py:
* Add copyright to rtd config
* Use Sphinx's RTD theme to replicate actual docs
Oracle: Render secondary vnic IP and MTU values only
When rendering secondary vnic configuration from IMDS, only emit
configuration for the IP and MTU values only. Add support to mutate
either a v1 or a v2 network_config input.
Make sure Exoscale supplements or overrides existing system config
setting cloud_config_modules instead of replacing it with a one item
list set-passords
