设为首页 收藏本站
查看: 745|回复: 0

[经验分享] man openstack >>1.txt

[复制链接]

尚未签到

发表于 2018-5-31 07:11:22 | 显示全部楼层 |阅读模式
OPENSTACK(1)                                                                                         OpenStack Command Line Client                                                                                        OPENSTACK(1)

NAME
       openstack - OpenStack Command Line Client
       OpenStack Command Line
SYNOPSIS
       openstack [<global-options>] <command> [<command-arguments>]
       openstack help <command>
       openstack --help
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 OS_PROJECT_NAME/OS_PROJECT_ID over the old tenant-based names.
          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:
       · token: Authentication with a token
       · password: Authentication with a username and a password
       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 --os-token and --os-url (or the environment variables OS_TOKEN and OS_URL respectively). This method takes precedence over
       authentication plugins.
       NOTE:
          To use the v3unscopedsaml method, the lxml package will need to be installed.
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:
       --os-cloud <cloud-name>
              openstack will look for a clouds.yaml file that contains a cloud configuration to use for authentication.  See CLOUD CONFIGURATION below for more information.
       --os-auth-type <auth-type>
              The authentication plugin type to use when connecting to the Identity service.  If this option is not set, openstack will attempt to guess the authentication method to use based on the other options.  If this  option
              is set, its version must match --os-identity-api-version
       --os-auth-url <auth-url>
              Authentication URL
       --os-url <service-url>
              Service URL, when using a service token for authentication
       --os-domain-name <auth-domain-name> | --os-domain-id <auth-domain-id>
              Domain-level authorization scope (name or ID)
       --os-project-name <auth-project-name> | --os-project-id <auth-project-id>
              Project-level authentication scope (name or ID)
       --os-project-domain-name <auth-project-domain-name> | --os-project-domain-id <auth-project-domain-id>
              Domain name or ID containing project
       --os-username <auth-username>
              Authentication username
       --os-password <auth-password>
              Authentication password
       --os-token <token>
              Authenticated token or service token
       --os-user-domain-name <auth-user-domain-name> | --os-user-domain-id <auth-user-domain-id>
              Domain name or ID containing user
       --os-trust-id <trust-id>
              ID of the trust to use as a trustee user
       --os-default-domain <auth-domain>
              Default domain ID (Default: 'default')
       --os-region-name <auth-region-name>
              Authentication region name
       --os-cacert <ca-bundle-file>
              CA certificate bundle file
       --verify | --insecure
              Verify or ignore server certificate (default: verify)
       --os-cert <certificate-file>
              Client certificate bundle file
       --os-key <key-file>
              Client certificate key file
       --os-identity-api-version <identity-api-version>
              Identity API version (Default: 2.0)
       --os-XXXX-api-version <XXXX-api-version>
              Additional API version options will be available depending on the installed API libraries.
       --os-interface <interface>
              Interface type. Valid options are public, admin and internal.
       --os-profile <hmac-key>
              Performance profiling HMAC key for encrypting context data
              This key should be the value of one of the HMAC keys defined in the configuration files of OpenStack services to be traced.
       --os-beta-command
              Enable beta commands which are subject to change
       --log-file <LOGFILE>
              Specify a file to log output. Disabled by default.
       -v, --verbose
              Increase verbosity of output. Can be repeated.
       -q, --quiet
              Suppress output except warnings and errors
       --debug
              Show tracebacks on errors and set verbosity to debug
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
       complete
              Print the bash completion functions for the current command set.
       help   Print help for an individual command
       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 quota object that has options referring to both Compute and Block Storage quotas.
   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 clouds.yaml configuration file.
   Config Files
       openstack will look for a file called clouds.yaml in the following locations:
       · Current Directory
       · ~/.config/openstack
       · /etc/openstack
       The first file found wins.
       The keys match the openstack global options but without the --os- prefix:
          clouds:
            devstack:
              auth:
                auth_url: http://192.168.122.10:35357/
                project_name: demo
                username: demo
                password: 0penstack
              region_name: RegionOne
            ds-admin:
              auth:
                auth_url: http://192.168.122.10:35357/
                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 auth_url for the rackspace cloud is taken from clouds-public.yaml:
          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 --os-auth-type option can always be used to force a specific type.
       When --os-token and --os-url are both present the token_endpoint auth type is selected automatically.  If --os-auth-url and --os-username are present password auth type is selected.
   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 OS_IDENTITY_API_VERSION must be set to 3.
EXAMPLES
       Show the detailed information for server appweb01:
          openstack \
              --os-project-name ExampleCo \
              --os-username demo --os-password secret \
              --os-auth-url http://localhost:5000:/v2.0 \
              server show appweb01
       The same command if the auth environment variables (OS_AUTH_URL, OS_PROJECT_NAME, OS_USERNAME, OS_PASSWORD) are set:
          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
       ~/.config/openstack/clouds.yaml
              Configuration file used by the --os-cloud global option.
       ~/.config/openstack/clouds-public.yaml
              Configuration file containing public cloud provider information such as authentication URLs and service definitions.  The contents of this file should be public and sharable.  clouds.yaml may  contain  references  to
              clouds defined here as shortcuts.
       ~/.openstack
              Placeholder  for future local state directory.  This directory is intended to be shared among multiple OpenStack-related applications; contents are namespaced with an identifier for the app that owns it.  Shared con‐
              tents (such as ~/.openstack/cache) have no prefix and the contents must be portable.
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.
       OS_CLOUD
              The name of a cloud configuration in clouds.yaml.
       OS_AUTH_PLUGIN
              The authentication plugin to use when connecting to the Identity service, its version must match the Identity API version
       OS_AUTH_URL
              Authentication URL
       OS_URL Service URL (when using the service token)
       OS_DOMAIN_NAME
              Domain-level authorization scope (name or ID)
       OS_PROJECT_NAME
              Project-level authentication scope (name or ID)
       OS_PROJECT_DOMAIN_NAME
              Domain name or ID containing project
       OS_USERNAME
              Authentication username
       OS_TOKEN
              Authenticated or service token
       OS_PASSWORD
              Authentication password
       OS_USER_DOMAIN_NAME
              Domain name or ID containing user
       OS_TRUST_ID
              ID of the trust to use as a trustee user
       OS_DEFAULT_DOMAIN
              Default domain ID (Default: 'default')
       OS_REGION_NAME
              Authentication region name
       OS_CACERT
              CA certificate bundle file
       OS_CERT
              Client certificate bundle file
       OS_KEY Client certificate key file
       OS_IDENTITY_API_VERSION
              Identity API version (Default: 2.0)
       OS_XXXX_API_VERSION
              Additional API version options will be available depending on the installed API libraries.
       OS_INTERFACE
              Interface type. Valid options are public, admin and internal.
BUGS
       Bug reports are accepted at the python-openstackclient LaunchPad project "https://bugs.launchpad.net/python-openstackclient/+bugs".
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
       http://www.apache.org/licenses/LICENSE-2.0
SEE ALSO
       The OpenStackClient page in the OpenStack Docs contains further documentation.
       The individual OpenStack project CLIs, the OpenStack API references.
AUTHOR
       OpenStack contributors
COPYRIGHT
       2012-2013 OpenStack Foundation


3.8.1                                                                                                      February 08, 2017                                                                                              OPENSTACK(1)  

运维网声明 1、欢迎大家加入本站运维交流群:群②:261659950 群⑤:202807635 群⑦870801961 群⑧679858003
2、本站所有主题由该帖子作者发表,该帖子作者与运维网享有帖子相关版权
3、所有作品的著作权均归原作者享有,请您和我们一样尊重他人的著作权等合法权益。如果您对作品感到满意,请购买正版
4、禁止制作、复制、发布和传播具有反动、淫秽、色情、暴力、凶杀等内容的信息,一经发现立即删除。若您因此触犯法律,一切后果自负,我们对此不承担任何责任
5、所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其内容的准确性、可靠性、正当性、安全性、合法性等负责,亦不承担任何法律责任
6、所有作品仅供您个人学习、研究或欣赏,不得用于商业或者其他用途,否则,一切后果均由您自己承担,我们对此不承担任何法律责任
7、如涉及侵犯版权等问题,请您及时通知我们,我们将立即采取措施予以解决
8、联系人Email:admin@iyunv.com 网址:www.yunweiku.com

所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其承担任何法律责任,如涉及侵犯版权等问题,请您及时通知我们,我们将立即处理,联系人Email:kefu@iyunv.com,QQ:1061981298 本贴地址:https://www.yunweiku.com/thread-483226-1-1.html 上篇帖子: openstack控制台报出:找不到服务器 下篇帖子: RDO部署openstack
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

扫码加入运维网微信交流群X

扫码加入运维网微信交流群

扫描二维码加入运维网微信交流群,最新一手资源尽在官方微信交流群!快快加入我们吧...

扫描微信二维码查看详情

客服E-mail:kefu@iyunv.com 客服QQ:1061981298


QQ群⑦:运维网交流群⑦ QQ群⑧:运维网交流群⑧ k8s群:运维网kubernetes交流群


提醒:禁止发布任何违反国家法律、法规的言论与图片等内容;本站内容均来自个人观点与网络等信息,非本站认同之观点.


本站大部分资源是网友从网上搜集分享而来,其版权均归原作者及其网站所有,我们尊重他人的合法权益,如有内容侵犯您的合法权益,请及时与我们联系进行核实删除!



合作伙伴: 青云cloud

快速回复 返回顶部 返回列表