diff options
author | Ghe Rivero <ghe.rivero@hp.com> | 2015-06-04 09:56:33 +0200 |
---|---|---|
committer | Ghe Rivero <ghe.rivero@hp.com> | 2015-06-04 09:59:02 +0200 |
commit | 038ddd38185ace24e96017b3d638952a397e61c6 (patch) | |
tree | db1769cdf1bd35aaf0378124b5ccde459575df04 /README.rst | |
parent | a0df67704ace186b18fd1ecdc220a7e56409bc6f (diff) | |
download | os-client-config-038ddd38185ace24e96017b3d638952a397e61c6.tar.gz |
Add cloud vendor files config in doc
Although it is possible to include specific config files for
unknown vendors, this wasn't specified in the documentation.
Change-Id: Ib27277d480e373a8a083e820161e0bdb985de284
Diffstat (limited to 'README.rst')
-rw-r--r-- | README.rst | 6 |
1 files changed, 4 insertions, 2 deletions
@@ -108,10 +108,12 @@ An example config file is probably helpful: You may note a few things. First, since auth_url settings are silly and embarrasingly ugly, known cloud vendor profile information is included and -may be referrenced by name. One of the benefits of that is that auth_url +may be referenced by name. One of the benefits of that is that auth_url isn't the only thing the vendor defaults contain. For instance, since Rackspace lists `rax:database` as the service type for trove, os-client-config -knows that so that you don't have to. +knows that so that you don't have to. In case the cloud vendor profile is not +available, you can provide one called clouds-public.yaml, following the same +location rules previously mentioned for the config files. Also, region_name can be a list of regions. When you call get_all_clouds, you'll get a cloud config object for each cloud/region combo. |