Remove unused methods

o glance/common/utils.py:
  def add_features_to_http_headers(features, headers):

  This method was removed in the following commit.

    commit 76c3620c7effb15be577450c276db1e394c2de3e
    Author: Brian Waldon <bcwaldon@gmail.com>
    Date:   Fri Sep 7 17:21:34 2012 -0700

        Drop Glance Client

  In this case, it has been used only in the following test program.

  - glance/tests/unit/common/test_utils.py

o glance/tests/functional/__init__.py:    def reload_server(self,

  This method was removed in the following commit.

    commit 866cb846f5310e1ad36181e64e7d59ba54d9fd40
    Author: John Bresnahan <jbresnah@redhat.com>
    Date:   Fri May 3 10:50:42 2013 -1000

        Remove glance-control from the test suite

The following methods are not used(w/o tests), however, it can not be
deleted, added the comment.

o glance/common/location_strategy/__init__.py:
  def verify_location_strategy(conf=None,
      strategies=_available_strategies):

Change-Id: I50e3fdb6e929337b946e3534c8e7dbff77ac7998
Update documentation surrounding the api and registry servers

Change-Id: I24e288eae841190e0776623b29da0bf8b9b9d34c
Changing Sheepdog driver to use correct configuration function

Currently Sheepdog store driver is using configure_add() to handle
those essential options, which are not only be used for image 'add'
handling but also for other key functions e.g. 'get_size', 'get' and
etc. When store driver raises BadStoreConfiguration exception from
configure_add(), Glance will just makes this store be readonly instead
of fully disabled, so the handling for all the essential configurations
should be implemented in configure(), and then if any option of them get
failure the store will be fully disabled instead of being readonly
partially.

Closes-bug: 1302658

Change-Id: Idaa96036515f04ee8414f30990ee638855ede2d2
Signed-off-by: Zhi Yan Liu <zhiyanl@cn.ibm.com>
Use (# of CPUs) glance workers by default

The config docs have historically recommended that the number of
glance  workers should be set to the number of CPUs available for
best performance, so we should make this the default.

Commit 75c96a48fc7e5dfb59d8258142b01422f81b0253 did the same thing in
Nova in Icehouse and the plan is to do the same thing for Cinder
and Trove workers.

The config files are updated to match the help string in the code.

There is no upgrade impact since glance-api.conf previously
hard-coded the workers value to 1 so anyone upgrading to this
will still get whatever value was set in glance-api.conf prior
to this change.

DocImpact: glance workers will now be equal to the number of
           CPUs available by default if not explicitly specified
           in glance-api.conf and/or glance-registry.conf.

UpgradeImpact: There is no upgrade impact to glance-api workers
           since glance-api.conf previously hard-coded the workers
           value to 1 so anyone upgrading to tihs will still get
           whatever value was set in glance-api.conf prior to
           this change. There is an upgrade impact to the
           glance-registry workers since glance-registry.conf
           did not hard-code the workers value to 1 before change
           I0cee0d284eef9ce5dcb26720499f2c4d31eaca0f, which is
           overwritten here. So anyone upgrading to this change
           that does not have workers specified in
           glance-registry.conf will now be running multiple
           workers by default when they restart the glance
           registry service.

Closes-Bug: #1333325

Change-Id: I6795c6e22268bb3fb67331edc7af641aefa904cc
Added an extra parameter to the df command

The parameter is needed to avoid multi-line output,
which results in an IndexError,
because only one line is being searched for values.

Change-Id: Ie518c6a3573b7868065501a02cd0bd8565656a71
Closes-Bug: 1336238
Fix docstrings in enforce() and check() policy methods

Proper name of the  parameter is 'target', not 'object'.

Change-Id: Ia7a671c9aed644137e4c46452d8d8bf3bc3f2eee
Merge "Use (# of CPUs) glance workers by default"
Fix unsaved exception in store.rbd.Store.add()

When an exception occurs during exception handling, it lose the
information of the first exception.

We should use the excutils.save_and_reraise_exception() in this case.

Change-Id: I1154e17d98804270f9578bc34a5fca6629bd9af4
Closes-Bug: #1292455
Raise NotImplementedError instead of NotImplemented

Change-Id: I1a01a5ad60d0eff1609d422578b38fb19923746f
Updated from global requirements

Change-Id: I64468adc6983b8cb5d78fe50752ed35c9fb41c2e
Imported Translations from Transifex

Change-Id: I6259381698981a00a018a2b3eb90e26d9e15ca4c
Merge "Updated from global requirements"
Updated from global requirements

Change-Id: I449f493b17e55551f0f7d4f070f6d674f6e5a19a
Merge "Fix unsaved exception in store.rbd.Store.add()"
Merge "Updated from global requirements"
Merge "Remove unused methods"
Fix typo in comment

Change-Id: I181b5cafb80e30fe31a385631882f877c3c2ea13
Merge "Update documentation surrounding the api and registry servers"
Merge "Added an extra parameter to the df command"
Merge "Changing Sheepdog driver to use correct configuration function"