Explicitly set ConfigOpts._args to sys.argv[1:]

Fixes bug #1146426

If you don't pass an args list to ConfigOpts.__call__() we pass
args=None down to ArgumentParser.parse_args() and it defaults to
sys.argv[1:].

However, in log_opt_values() we reference sys._args and you'd expect it
to show sys.argv[1:] in this case too but it shows None.

Fix this by explicitly setting _conf to sys.argv[1:] rather than relying
on argparse's behaviour.

Also add a test which would fail without this fix.

Change-Id: Id5a769bdda5f2359da18c301cb6305aaf3ed8617
Switch to semantic versioning

Discussed here:

  http://lists.openstack.org/pipermail/openstack-dev/2013-March/006283.html

The date based 2013.1 version is likely to be disallowed by PEP426
when it is ratified and we'll be required to treat the date based
version as a "private version" and use 0.2013.1 as the official
version.

Also, I'm coming around to the idea of using semantic versioning
(i.e. x.y.z) and increasing the major number when removing any
deprecated APIs. Th is the trend that Python is following according to
a discussion on distutils-sig.

One consequence of using semantic versioning is that we'll be very
loathe to remove any deprecated APIs since it will mean a version bump
from 1.y.z to 2.y.z. That's probably not a bad thing.

With this versioning scheme, I figure we should start with 1.1.0
(2013.1-2012). We'll increase the micro number when we do release from
the stable branch and increase the minor number with every coordinated
OpenStack release.

Change-Id: Ibe033d37742b82dee5f42d9e3d6a0b51582bd3ce
Change the name of the project to oslo.config

Again discussed here:

  http://lists.openstack.org/pipermail/openstack-dev/2013-March/thread.html#6283
  http://lists.openstack.org/pipermail/openstack-dev/2013-March/thread.html#6138

The rationale is that the use of namespace packages is likely to
increase and there is apparently some consensus that the convention
should be to use period to separate the namespace package name from
the subpackage name - i.e. call it oslo.config. The zope.interface is
an example of this convention, but PasteDepoy is a counter-example.

Oslo is going to have a family of libraries, so it'd be much nicer if
they followed what the future Python convention is likely to be.

This is a disruptive change for packagers and the benefit isn't huge,
but pairing it with the also disruptive change to the versioning
scheme makes it somewhat more acceptable.

Change-Id: I63e96a8b48b166b07f1c8e79b6eaffb6234cc751
Correct some typos in docstrings in cfg.py.

Change-Id: I3c56596cf0154c342e0a0aa0e60e9111519f3554
Copyright rename LLC to Foundation

One code change, rest are in file headers

Change-Id: I22c3a271edab63b382eb07cecd8b5ef02834b540
Merge "Copyright rename LLC to Foundation"
Open 1.1.x development

The 1.1.x series will be for grizzly bugfix releases.

Change-Id: I041046bb97bf4072f598c91b8a127f4e6bba9f19
Set default branch in .gitreview to stable/grizzly

This allows people to run git-review without any arguments.

Change-Id: Id901d5b948e0419b944e9c7bc12152dc12226b87
Add Environment::OpenStack classifier

Doug had this registered for us:

  http://mail.python.org/pipermail/catalog-sig/2012-October/004634.html

It makes it easier to find all OpenStack packages.

Change-Id: I17ee76616eb11a02a65b7a624f625a207b9e9631
Rename oslo-config to oslo.config.

Change-Id: Ie9c891e5ec54ee908dead98f5133a4f2aa88da58
isdir('.git') is never correct.

this doesn't solve the breakage when setup.py isn't in the cwd, but that
can wait.