Thank so much Rain!!! :) Still error result as below :( Also including glance-api.conf/glance-api-paste.ini/glance-registry.conf/glance-registry-paste.ini in line.

======================================================== root@gplab24:/tmp/images# glance --os_username=adminUser --os_password=secretword --os_tenant=openstackDemo --os_auth_url=http://127.0.0.1:5000/v2.0 add name="tty-linuxkernel" disk_format=aki container_format=aki < ttylinux-uec-amd64-12.1_2.6.35-22_1-vmlinuz [100%] 13.9M/s, ETA 0h 0m 0s Uploading image 'tty-linuxkernel' Failed to add image. Got error: You are not authenticated. Details: 401 Unauthorized

This server could not verify that you are authorized to access the document you requested. Either you supplied the wrong credentials (e.g., bad password), or your browser does not understand how to supply the credentials required.

Authentication required

Note: Your image metadata may still be in the registry, but the image's st[ 0%]

==================glance-api.conf start ======================== [DEFAULT] # Show more verbose log output (sets INFO log level output) verbose = True

            # Show debugging output in logs (sets DEBUG log level output)
            debug = False

            # Which backend store should Glance use by default is not specified
            # in a request to add a new image to Glance? Default: 'file'
            # Available choices are 'file', 'swift', and 's3'
            default_store = file

            # Address to bind the API server
            bind_host = 0.0.0.0
            # Port the bind the API server to
            bind_port = 9292

            # Log to this file. Make sure you do not set the same log
            # file for both the API and registry servers!
            log_file = /var/log/glance/api.log

            # Backlog requests when creating socket
            backlog = 4096

            # Number of Glance API worker processes to start.
            # On machines with more than one CPU increasing this value
            # may improve performance (especially if using SSL with
            # compression turned on). It is typically recommended to set
            # this value to the number of CPUs present on your machine.
            workers = 0

            # Role used to identify an authenticated user as administrator
            #admin_role = admin

            # ================= Syslog Options ============================

            # Send logs to syslog (/dev/log) instead of to file specified
            # by `log_file`
            use_syslog = False

            # Facility to use. If unset defaults to LOG_USER.
            # syslog_log_facility = LOG_LOCAL0

            # ================= SSL Options ===============================

            # Certificate file to use when starting API server securely
            # cert_file = /path/to/certfile

            # Private key file to use when starting API server securely
            # key_file = /path/to/keyfile

            # ================= Security Options ==========================

            # AES key for encrypting store 'location' metadata, including
            # -- if used -- Swift or S3 credentials
            # Should be set to a random string of length 16, 24 or 32 bytes
            # metadata_encryption_key = <16, 24 or 32 char registry metadata key>

            # ============ Registry Options ===============================

            # Address to find the registry server
            registry_host = 0.0.0.0
            # Port the registry server is listening on
            registry_port = 9191

            # What protocol to use when connecting to the registry server?
            # Set to https for secure HTTP communication
            registry_client_protocol = http

            # The path to the key file to use in SSL connections to the
            # registry server, if any. Alternately, you may set the
            # GLANCE_CLIENT_KEY_FILE environ variable to a filepath of the key file
            # registry_client_key_file = /path/to/key/file

            # The path to the cert file to use in SSL connections to the
            # registry server, if any. Alternately, you may set the
            # GLANCE_CLIENT_CERT_FILE ...

Thanks to both!!! We still have error to follow your suggestions.

We try your command as below:

======Command1 Request========= root@gplab24:~# curl -d '{"auth":{"passwordCredentials":{"username": "adminUser" ,"password": "secretword"}}}' -H "Content-type: application/json" http://localho st:35357/v2.0/tokens

======Command1 Result ========= {"access": {"token": {"expires": "2012-07-24T03:53:37Z", "id": "18c441aec809476f9747fd1a84d45cd7"}, "serviceCatalog": {}, "user": {"username": "adminUser", "rol es_links": [], "id": "518cacf232e040d1b6d42547047d479b", "roles": [], "name": "a

======Command2 Request ========= root@gplab24:~# glance --os_username=adminUser --os_password=secretword --os_tenant=openstackDemo --os_auth_url=http://127.0.0.1:5000/v2.0 index -A 18c441aec809476f9747fd1a84d45cd7 //18c441aec809476f9747fd1a84d45cd7 come from command1 result id

======Command2 Result ========= Failed to show index. Got error: You are not authenticated. Details: 401 Unauthorized

This server could not verify that you are authorized to access the document you requested. Either you supplied the wrong credentials (e.g., bad password), or your browser does not understand how to supply the credentials required. Authentication required

=======user list===========

root@gplab24:~# keystone user-list Expecting authentication method via either a service token, --token or env[SERVICE_TOKEN], or credentials, --os_username or env[OS_USERNAME].

root@gplab24:~# keystone --token 012345SECRET99TOKEN012345 --endpoint http://127.0.0.1:35357/v2.0 user-list +----------------------------------+---------+-------+-----------+ | id | enabled | email | name | +----------------------------------+---------+-------+-----------+ | 29c2d976987745fd9b8439dd4aac4701 | True | None | ec2 | | 518cacf232e040d1b6d42547047d479b | True | None | adminUser | | 7fe5bcbcb98d41f2aa6d371ea2a3157a | True | None | nova | | c567d5959b044db98b1c510e281741b2 | True | None | glance | | f4506084f78d4c81866cac7da07f82f3 | True | None | swift | +----------------------------------+---------+-------+-----------+

=======role list=========== root@gplab24:~# keystone --token 012345SECRET99TOKEN012345 --endpoint http://127.0.0.1:35357/v2.0 role-list +----------------------------------+------------+ | id | name | +----------------------------------+------------+ | 334828fc0a884c048f723c14a0cccf0b | memberRole | | 6a98b8ee20834bafaf7bd2c0580e0b51 | admin | +----------------------------------+------------+

=======service list=========== root@gplab24:~# keystone --token 012345SECRET99TOKEN012345 --endpoint http://127.0.0.1:35357/v2.0 service-list +----------------------------------+----------+--------------+---------------------------+ | id | name | type | description | +----------------------------------+----------+--------------+---------------------------+ | 05b4ff389a9449038dbed881ea6c26e1 | volume | volume | Nova Volume Service | | 0e7bb281ff72441db11020b890cea3f3 | nova | compute | Nova Compute Service | | 10db4791e77c421fb663f8d89151b128 | glance | image | Glance Image Service | | 31f32e4253264e84870a5ad87aa92c5c | ec2 | ec2 | EC2 Compatibility Layer | | 605961e742f44e1dac11f89c3f726751 | keystone | identity | Keystone Identity Service | | 942afb37d92a407b92c2e6ed4fefddfe | swift | object-store | Object Storage Service | +----------------------------------+----------+--------------+---------------------------+

=======endpoint list=========== root@gplab24:~# keystone --token 012345SECRET99TOKEN012345 --endpoint http://127.0.0.1:35357/v2.0 endpoint-list +----------------------------------+-----------+---------------------------------------------+---------------------------------------------+----------------------------------------+ | id | region | publicurl | internalurl | adminurl | +----------------------------------+-----------+---------------------------------------------+---------------------------------------------+----------------------------------------+ | 5a6e4d90889d428683182d9c1b6a58a6 | RegionOne | http://127.0.0.1:5000/v2.0 | http://127.0.0.1:5000/v2.0 | http://127.0.0.1:35357/v2.0 | | 6f74a335de774df2b59d70423502797f | RegionOne | http://127.0.0.1:9292/v1 | http://127.0.0.1:9292/v1 | http://127.0.0.1:9292/v1 | | b713eea1f0fb4d679a30a0d349b816ac | RegionOne | http://127.0.0.1:8774/v2/%25(tenant_id)s (http://127.0.0.1:8774/v2/%(tenant_id)s) | http://127.0.0.1:8774/v2/%25(tenant_id)s (http://127.0.0.1:8774/v2/%(tenant_id)s) | http://127.0.0.1:8774/v2/%25(tenant_id)s (http://127.0.0.1:8774/v2/%(tenant_id)s) | | b842289d645e42f3aa4031762724db3e | RegionOne | http://127.0.0.1:8888/v1/AUTH_%25(tenant_id)s (http://127.0.0.1:8888/v1/AUTH_%(tenan...) | http://127.0.0.1:8888/v1/AUTH_%25(tenant_id)s (http://127.0.0.1:8888/v1/AUTH_%(tenan...) | http://127.0.0.1:8888/ | | c289df94b93b4d64bf5717014259761d | RegionOne | http://127.0.0.1:8776/v1/%25(tenant_id)s (http://127.0.0.1:8776/v1/%(tenant_id)s) | http://127.0.0.1:8776/v1/%25(tenant_id)s (http://127.0.0 ... (more)