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.
Change-Id: I3f5b5fb26af2f6c0bbaade24a04c3d1f274c8cce
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
upload failures.
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.
Change-Id: I6947e0ae420402cc9866e3c374626392b1d5194c
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.
Change-Id: If51afa471505296b502bed3288cc9bcf30a69ba3
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.
Change-Id: Iad3aba66b0c6344157da30f374e191d01e938b2b
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.
Change-Id: Ic0205c82abc3b5bfd6223ea7a6ee1bd6bfb365dd
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
its intentions.
Also, fix sphinx doc build warnings.
Change-Id: Ie66b60d972cae25a9805804ad17632aed0932627
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.
Change-Id: Iac675860336275ea56026fcbed27338ba80ef886
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.
Change-Id: Iac38d4c0b29f867cc3cefaccf48c1c3fcd17a3d9
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.
Change-Id: I0c638beab615177fc6ce3704c5443a3394a87ed0
xuanyandong