https registry client isnt symmetric wrt api client

[Tom Hancock]

https client operations can interact (optionally) with the API server without a ca file by specifying
--insecure, however for the V1 API there is no way to do something similar between the API and
Registry because the configuration code assumes a ca file if you don't specify one.

Adding a 'registry_client_insecure' option would make the registry https interface as flexible as the
API interface.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/14163

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/14163
Committed: http://github.com/openstack/glance/commit/d1f8e8b009e22836a32c9e4930a89eba891293c7
Submitter: Jenkins
Branch: master

commit d1f8e8b009e22836a32c9e4930a89eba891293c7
Author: Tom Hancock <email address hidden>
Date: Mon Oct 8 13:14:24 2012 +0000

    Add insecure option to registry https client

    This fixes LP bug #1063793.

    This adds a new API config option registry_client_insecure
    (default false) which optionally allows not to specify a ca
    file for registry connections from the API server.
    The default is false so existing behaviour is
    unchanged unless this option is specified.
    Adding this option makes the registry symmetric wrt the API
    with which you can connect using clients with --insecure

    Change-Id: I4fa462cd68afaf14f7d7de6c572980a41c0849d6