delta/openstack/python-openstackclient.git/doc/source/man, branch 2.4.0 opendev.org: openstack/python-openstackclient Rename --profile to --os-profile 2016-04-19T12:50:42+00:00 Dean Troyer dtroyer@gmail.com 2016-04-18T19:39:21+00:00 530fe42589a2138278f100f791d8c6d3fbed8950 * The --profile global option is deprecated but will be supported through at least April 2017. * Update man page Closes-bug: #1571812 Change-Id: I2e623411a56096b4cc352f4eedbf770632ae2cc3 
* The --profile global option is deprecated but will be supported
  through at least April 2017.
* Update man page

Closes-bug: #1571812
Change-Id: I2e623411a56096b4cc352f4eedbf770632ae2cc3
Support client certificate/key 2016-04-06T18:21:19+00:00 Cedric Brandily zzelle@gmail.com 2016-04-01T21:42:27+00:00 3a8320a1d73444b3bb823300e94c3e2ee85fd6ef This change enables to specify a client certificate/key with: * usual CLI options (--os-cert/--os-key) * usual environment variables ($OS_CERT/$OS_KEY) * os-client-config Change-Id: Ibeaaa5897ae37b37c1e91f3e47076e4e8e4a8ded Closes-Bug: #1565112 
This change enables to specify a client certificate/key with:
 * usual CLI options (--os-cert/--os-key)
 * usual environment variables ($OS_CERT/$OS_KEY)
 * os-client-config

Change-Id: Ibeaaa5897ae37b37c1e91f3e47076e4e8e4a8ded
Closes-Bug: #1565112
Add shell --profile option to trigger osprofiler from CLI 2016-02-25T20:13:27+00:00 Dina Belova dbelova@mirantis.com 2015-12-10T12:48:52+00:00 16f00833a70893979ccdf7ffb7f6e1e7653cdc24 This will allow to trigger profiling of various services that allow it currently and which APIs support is added to openstackclient. Cinder and Glance have osprofiler support already, Nova and Keystone are in progress. To use this functionality osprofiler (and its storage backend) needs to be installed in the environment. If so, you will be able to trigger profiling via the following command, for example: $ openstack --profile SECRET_KEY user list At the end of output there will be message with <trace_id>, and to plot nice HTML graphs the following command should be used: $ osprofiler trace show <trace_id> --html --out result.html Related Keystone change: https://review.openstack.org/#/c/103368/ Related Nova change: https://review.openstack.org/#/c/254703/ The similar change to the keystoneclient (https://review.openstack.org/#/c/255308/) was abandoned as new CLI extenstions are not more accepted to python-keystoneclient. Change-Id: I3d6ac613e5da70619d0a4781e5d066fde073b407 
This will allow to trigger profiling of various services that
allow it currently and which APIs support is added to openstackclient.
Cinder and Glance have osprofiler support already, Nova and Keystone
are in progress.

To use this functionality osprofiler (and its storage backend) needs
to be installed in the environment. If so, you will be able to trigger
profiling via the following command, for example:

$ openstack --profile SECRET_KEY user list

At the end of output there will be message with <trace_id>, and
to plot nice HTML graphs the following command should be used:

$ osprofiler trace show <trace_id> --html --out result.html

Related Keystone change: https://review.openstack.org/#/c/103368/
Related Nova change: https://review.openstack.org/#/c/254703/

The similar change to the keystoneclient
(https://review.openstack.org/#/c/255308/) was abandoned as new
CLI extenstions are not more accepted to python-keystoneclient.

Change-Id: I3d6ac613e5da70619d0a4781e5d066fde073b407
Use Block Storage instead of Volume 2015-11-27T09:56:10+00:00 Xi Yang yang.xi@99cloud.net 2015-11-08T14:05:15+00:00 54b0ef3358b25b0c164ee5f4eba07ee474513d3a Volume is better to be replaced by Block Storage in the doc. Change-Id: I736669ee01c7385b6e701cb20f4334eff1c49286 
Volume is better to be replaced by Block Storage in the
doc.

Change-Id: I736669ee01c7385b6e701cb20f4334eff1c49286
Set up every time record log in file 2015-08-08T16:02:46+00:00 Daisuke Fujita fuzita.daisuke@jp.fujitsu.com 2015-05-29T11:39:24+00:00 e23dd6de5854fcc8ff76fe1b51eb46162770d9cc This will allow users to record logs of all their commands into a predefined log file, in clouds.yaml. The log should have a format similar to that of oslo.log. Change-Id: I1b334bf429d575fc25809c9706fc0b11116be3f1 Implements: blueprint every-time-record-log-in-file 
This will allow users to record logs of all their commands into
a predefined log file, in clouds.yaml. The log should have a
format similar to that of oslo.log.

Change-Id: I1b334bf429d575fc25809c9706fc0b11116be3f1
Implements: blueprint every-time-record-log-in-file
Rename endpoint type to interface 2015-07-15T16:11:59+00:00 TerryHowe terrylhowe@gmail.com 2015-07-04T15:32:16+00:00 36391a81a3415d24c55d6bbc318157dc119da8a7 Change-Id: I4e21d09bc747e8210f4f79a1d6c4c7ccf2f25d1c Closes-Bug: #1454392 
Change-Id: I4e21d09bc747e8210f4f79a1d6c4c7ccf2f25d1c
Closes-Bug: #1454392
Add --os-endpoint-type cli optional argument 2015-07-02T17:10:46+00:00 Roxana Gherle roxana.gherle@hp.com 2015-05-22T23:22:35+00:00 5521e4c504c6a3a06f17a9e4f80444743aa293c7 User should be able to specify the endpoint type through a CLI optional argument/ENV variable setting. We will name this new optional argument: --os-endpoint-type (Env: OS_ENDPOINT_TYPE) and based on the value given, the service API will use that specific endpoint type. Possible values: public, admin, internal. DocImpact Closes-Bug: #1454392 Change-Id: Ife3d4e46b44c0ddcd712b1130e27e362545a9a29 
User should be able to specify the endpoint type through
a CLI optional argument/ENV variable setting. We will name this new
optional argument: --os-endpoint-type (Env: OS_ENDPOINT_TYPE) and
based on the value given, the service API will use that specific
endpoint type. Possible values: public, admin, internal.

DocImpact
Closes-Bug: #1454392
Change-Id: Ife3d4e46b44c0ddcd712b1130e27e362545a9a29
Begin documenting --os-cloud 2015-04-19T04:04:53+00:00 Dean Troyer dtroyer@gmail.com 2015-03-04T05:12:07+00:00 6e7013954d4119c91345a5b83b9675c4be62a11d Change-Id: Id2e98ac5601840f6d380cabcd578f1a6d6d9b245 
Change-Id: Id2e98ac5601840f6d380cabcd578f1a6d6d9b245
Fix embarrassing typo in man page 2015-03-06T00:15:19+00:00 Zane Bitter zbitter@redhat.com 2015-03-06T00:15:19+00:00 fb2a5492df5a65a3670df9485befb4bc2cae24a2 Change-Id: Icf1fcd9f7952ebff9da0081ccb4b9272e17e7de4 
Change-Id: Icf1fcd9f7952ebff9da0081ccb4b9272e17e7de4
Unscoped federated user-specific commands 2014-10-30T16:27:28+00:00 Matthieu Huin mhu@enovance.com 2014-09-25T16:15:59+00:00 631ed3c8026e6b4539e7a8bf4adb8d2a7239b36a A federated user can authenticate with the v3unscopedsaml plugin and list the domains and projects she is allowed to scope to. This patch introduces the new commands 'federation domain list' and 'federation project list'. Note that for these commands -and plugin- to be available, the lxml library must be installed. Change-Id: I2707b624befcfb0a01b40a094e12fd68a3ee7773 Co-Authored-By: Florent Flament <florent.flament-ext@cloudwatt.com> 
A federated user can authenticate with the v3unscopedsaml plugin and
list the domains and projects she is allowed to scope to.
This patch introduces the new commands 'federation domain list' and
'federation project list'.
Note that for these commands -and plugin- to be available, the lxml
library must be installed.

Change-Id: I2707b624befcfb0a01b40a094e12fd68a3ee7773
Co-Authored-By: Florent Flament <florent.flament-ext@cloudwatt.com>