There was a point in time in the past where we were gung ho on using
Munch as a halfway house to get us to pure dicts. However, we released
1.0 before we could do that, so we're pretty stuck with them for the
forseeable future. That's not terrible - they're pretty low overhead and
work pretty well.
Depends-On: Ie10099430481ffa76f5a19557e3693189544df6b
Change-Id: I8b7dd2c4038db999280ec0c2c9c43fb9499e6d22
Add a section to our Coding Standards documentation that describes
the use of reno for shade release notes.
Change-Id: I87973c5b3f68727aa0cb1ccb9a82c90a8a32ebd1
We have pretty much settled on sticking with Munch objects for the
1.x series of shade releases. Change the documentation to note this.
Change-Id: I8b2838c3a5a40b0c74e31081bfb1ed4b0d39280f
The OpenStack Release team has created a great release notes management
tool that integrates with Sphinx. Start using it. For reference on how
to use it, see http://docs.openstack.org/developer/reno/
Change-Id: I57692d720174fedb68ab2f52d5a4c496a6d993b2
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 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
