GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing docs.openstack.org — openstack — OpenStack Command Line Client 10.5.1.dev13 documentation openstack¶OpenStack Command Line SYNOPSIS¶openstack [<global-options>] <command> [<command-arguments>] openstack help <command> openstack DESCRIPTION¶openstack provides a common command-line interface to OpenStack APIs. It is generally equivalent to the CLIs provided by the OpenStack project client libraries, but with a distinct and consistent command structure. AUTHENTICATION METHODS¶openstack uses a similar authentication scheme as the OpenStack project CLIs, with
the credential information supplied either as environment variables or as options on the
command line. The primary difference is the use of ‘project’ in the name of the options
export OS_AUTH_URL=<url-to-openstack-identity> export OS_PROJECT_NAME=<project-name> export OS_USERNAME=<user-name> export OS_PASSWORD=<password> # (optional) openstack can use different types of authentication plugins provided by the keystoneclient library. The following default plugins are available:
Refer to the keystoneclient library documentation for more details about these plugins and their options, and for a complete list of available plugins. Please bear in mind that some plugins might not support all of the functionalities of openstack; for example the v3unscopedsaml plugin can deliver only unscoped tokens, some commands might not be available through this authentication method. Additionally, it is possible to use Keystone’s service token to authenticate, by setting the options Note To use the AUTHENTICATION USING FEDERATION¶To use federated authentication, your configuration file needs the following: export OS_PROJECT_NAME=<project-name> export OS_PROJECT_DOMAIN_NAME=<project-domain-name> export OS_AUTH_URL=<url-to-openstack-identity> export OS_IDENTITY_API_VERSION=3 export OS_AUTH_PLUGIN=openid export OS_AUTH_TYPE=v3oidcpassword export OS_USERNAME=<username-in-idp> export OS_PASSWORD=<password-in-idp> export OS_IDENTITY_PROVIDER=<the-desired-idp> export OS_CLIENT_ID=<the-client-id-configured-in-the-idp> export OS_CLIENT_SECRET=<the-client-secred-configured-in-the-idp> export OS_OPENID_SCOPE=<the-scopes-of-desired-attributes-to-claim-from-idp> export OS_PROTOCOL=<the-protocol-used-in-the-apache2-oidc-proxy> export OS_ACCESS_TOKEN_TYPE=<the-access-token-type-used-by-your-idp> export OS_DISCOVERY_ENDPOINT=<the-well-known-endpoint-of-the-idp> export OS_ACCESS_TOKEN_ENDPOINT=<the-idp-access-token-url> OPTIONS¶openstack takes global options that control overall behaviour and command-specific options that control the command operation. Most global options have a corresponding environment variable that may also be used to set the value. If both are present, the command-line option takes priority. The environment variable names are derived from the option name by dropping the leading dashes (’–‘), converting each embedded dash (‘-’) to an underscore (‘_’), and converting to upper case. openstack recognizes the following global options:
Note If you switch to openstackclient from project specified clients, like: novaclient, neutronclient and so on, please use –os-interface instead of –os-endpoint-type.
COMMANDS¶To get a list of the available commands: openstack --help To get a description of a specific command: openstack help <command> Note that the set of commands shown will vary depending on the API versions that are in effect at that time. For example, to force the display of the Identity v3 commands: openstack --os-identity-api-version 3 --help
Additional information on the OpenStackClient command structure and arguments is available in the OpenStackClient Commands wiki page. Command Objects¶The list of command objects is growing longer with the addition of OpenStack
project support. The object names may consist of multiple words to compose a
unique name. Occasionally when multiple APIs have a common name with common
overlapping purposes there will be options to select which object to use, or
the API resources will be merged, as in the Command Actions¶The actions used by OpenStackClient are defined with specific meaning to provide a consistent behavior for each object. Some actions have logical opposite actions, and those pairs will always match for any object that uses them. CLOUD CONFIGURATION¶Working with multiple clouds can be simplified by keeping the configuration
information for those clouds in a local file. openstack supports
using a Config Files¶openstack will look for a file called clouds.yaml in the following locations:
The first file found wins. The keys match the openstack global options but without the
clouds:
devstack:
auth:
auth_url: http://192.168.122.10:5000/
project_name: demo
username: demo
password: 0penstack
region_name: RegionOne
ds-admin:
auth:
auth_url: http://192.168.122.10:5000/
project_name: admin
username: admin
password: 0penstack
region_name: RegionOne
infra:
cloud: rackspace
auth:
project_id: 275610
username: openstack
password: xyzpdq!lazydog
region_name: DFW,ORD,IAD
In the above example, the public-clouds: rackspace: auth: auth_url: 'https://identity.api.rackspacecloud.com/v2.0/' Authentication Settings¶OpenStackClient uses the Keystone authentication plugins so the required
auth settings are not always known until the authentication type is
selected. openstack will attempt to detect a couple of common
auth types based on the arguments passed in or found in the configuration
file, but if those are incomplete it may be impossible to know which
auth type is intended. The When Logging Settings¶openstack can record the operation history by logging settings in configuration file. Recording the user operation, it can identify the change of the resource and it becomes useful information for troubleshooting. See Configuration about Logging Settings for more details. NOTES¶The command list displayed in help output reflects the API versions selected. For
example, to see Identity v3 commands EXAMPLES¶Show the detailed information for server openstack \ --os-project-name ExampleCo \ --os-username demo --os-password secret \ --os-auth-url http://localhost:5000:/v2.0 \ server show appweb01 The same but using openid to authenticate in keystone: openstack \ --os-project-name ExampleCo \ --os-auth-url http://localhost:5000:/v2.0 \ --os-auth-plugin openid \ --os-auth-type v3oidcpassword \ --os-username demo-idp \ --os-password secret-idp \ --os-identity-provider google \ --os-client-id the-id-assigned-to-keystone-in-google \ --os-client-secret 3315162f-2b28-4809-9369-cb54730ac837 \ --os-openid-scope 'openid email profile'\ --os-protocol openid \ --os-access-token-type access_token \ --os-discovery-endpoint https://accounts.google.com/.well-known/openid-configuration \ server show appweb01 The same command if the auth environment variables ( openstack server show appweb01 Create a new image: openstack image create \ --disk-format=qcow2 \ --container-format=bare \ --public \ --copy-from http://somewhere.net/foo.img \ foo FILES¶
ENVIRONMENT VARIABLES¶The following environment variables can be set to alter the behaviour of openstack. Most of them have corresponding command-line options that take precedence if set.
Note If you switch to openstackclient from project specified clients, like: novaclient, neutronclient and so on, please use OS_INTERFACE instead of OS_ENDPOINT_TYPE. BUGS¶Bug reports are accepted at the python-openstackclient Launchpad project “https://bugs.launchpad.net/python-openstackclient”. AUTHORS¶Please refer to the AUTHORS file distributed with OpenStackClient. COPYRIGHT¶Copyright 2011-2014 OpenStack Foundation and the authors listed in the AUTHORS file. LICENSE¶SEE ALSO¶The OpenStackClient page in the OpenStack Docs contains further documentation. The individual OpenStack project CLIs, the OpenStack API references. this page last updated: 2023-10-25 18:54:22
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.
|
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |