Tom Hancock d1f8e8b009 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		2012-10-09 10:43:57 +00:00
..
glance-api-paste.ini	Makes deployed APIs configurable	2012-09-05 21:01:25 +00:00
glance-api.conf	Add insecure option to registry https client	2012-10-09 10:43:57 +00:00
glance-cache.conf	Add metadata_encryption_key to glance-cache.conf.	2012-06-13 12:30:59 -04:00
glance-registry-paste.ini	Clean up comments in paste files	2012-09-03 12:51:56 -07:00
glance-registry.conf	Remove extraneous whitespace in config files	2012-09-05 16:37:30 -07:00
glance-scrubber.conf	Split out paste deployment config from the core glance	2012-01-17 11:40:26 +00:00
logging.cnf.sample	First round of logging functionality:	2011-02-01 13:18:40 -05:00
policy.json	Add policy checks for cache manage middleware	2012-03-16 14:50:37 -07:00
schema-image.json	Add kernel/ramdisk_id, instance_uuid to v2 schema	2012-08-29 09:31:38 -07:00