Revert the openstacksdk subclassing from shade. The idea was to
reduce the workload, but trying to make sure that the Cloud abstraction
in openstacksdk doesn't break shade's contract while we update things is
a ton of work to meet the contract that's not really valuable to people.
Instead, we'll put shade on lifesupport and only accept bugfix patches.
Revert "Make OpenStackCloud a subclass of Connection"
This reverts commit ab3f400064.
Revert "Use openstack.config directly for config"
This reverts commit 2b48637b67.
Revert "Remove the task manager"
This reverts commit 28e95889a0.
An 'example' anchor was being explicitly added that was
redundant with the 'Example' title it preceeded. This
causes failures with `python setup.py check -s -r` which
was added to release validation to prevent pypi package
Since the README is imported into the built docs, and the
docs link to the examples using this hidden anchor, this
renames it to avoid a conflict.
After migrating to openstackdocstheme, some shade document became
not easy to read. This commit fixes them a bit.
- openstackdocstheme assumee only one title per page.
Use a different level of title for the title.
Otherwise, titles with the same level are not shown.
- Release notes page has a lot of sections. It leads to a long TOC
in the user guide index page.
Use maxdepth=1 explicitly for the release notes.
- Add a link to a simple example to usage.rst.
It helps users who access the user guide directly.
The very first example of the usage of shade is easier to understand
if there is also an example of the needed `clouds.yml` file. Without
it, it is unclear what the meaning of the key `mordred` means.
Just noticed that the README says "for operating OpenStack". The word
operating has very specific connotations in OpenStack world, and that is
decidedly _not_ the primary use case of shade.
The README was discussing future design decisions as if they were
already implemented. This can be confusing for new users. This
separates that discussion into a separate doc page and clarifies
Also, fix sphinx doc build warnings.
We are currently butting up against the point where the functional
interface is a bit ugly. Write up a general design for an object
interface, as well as a few other design thoughts on the library.
We should not be returning raw client objects when creating or
rebuilding a server.
The usage document is updated to indicate that access to resource
values via attribute is deprecated, and the examples in the README
now reflect dict-style access.
The README used only python-*client objects, thus defeating the
purpose of shade, which is about putting a facade for all those
interfaces to simplify things.
README now shows you can use shade simplified interface and also
access the underlying python-*client API objects.