Ask Your Question

Revision history [back]

Take a look at post http://bderzhavets.blogspot.com/2016/04/rest-api-rdo-mitaka.html
I was able reproduce http://developer.openstack.org/api-guide/quick-start/api-quick-start.html
However , REST API requests like :-

[root@ip-192-169-142-127 ~(keystone_admin)]# curl -s -H "X-Auth-Token: $OS_TOKEN" \
http://128.136.179.2:8774/v2/$OS_TENANT_NAME/flavors \
| python -m json.tool

failed.
I got samples running after update :-

[root@ip-192-169-142-127 ~(keystone_admin)]# curl -s -H "X-Auth-Token: $OS_TOKEN"   http://192.169.142.127:8774/v2/b47473d8953d49b29910fc681a2ff773/flavors  | python -m json.tool

where b47473d8953d49b29910fc681a2ff773 is admin's tenant id.

Take a look at post posts :-
http://bderzhavets.blogspot.com/2016/04/rest-api-rdo-mitaka.html
http://bderzhavets.blogspot.com/2016/04/creating-server-via-rest-api-rdo-mitaka.html

I was able reproduce http://developer.openstack.org/api-guide/quick-start/api-quick-start.html
However , REST API requests like :-

[root@ip-192-169-142-127 ~(keystone_admin)]# curl -s -H "X-Auth-Token: $OS_TOKEN" \
http://128.136.179.2:8774/v2/$OS_TENANT_NAME/flavors \
| python -m json.tool

failed.
I got samples running after update :-

[root@ip-192-169-142-127 ~(keystone_admin)]# curl -s -H "X-Auth-Token: $OS_TOKEN"   http://192.169.142.127:8774/v2/b47473d8953d49b29910fc681a2ff773/flavors  | python -m json.tool

where b47473d8953d49b29910fc681a2ff773 is admin's tenant id.

Take a look at posts :-
http://bderzhavets.blogspot.com/2016/04/rest-api-rdo-mitaka.html
http://bderzhavets.blogspot.com/2016/04/creating-server-via-rest-api-rdo-mitaka.html

I was able reproduce http://developer.openstack.org/api-guide/quick-start/api-quick-start.html
However , REST API requests like :-

[root@ip-192-169-142-127 ~(keystone_admin)]# curl -s -H "X-Auth-Token: $OS_TOKEN" \
http://128.136.179.2:8774/v2/$OS_TENANT_NAME/flavors \
| python -m json.tool

failed.
I got samples running after update :-

[root@ip-192-169-142-127 ~(keystone_admin)]# curl -s -H "X-Auth-Token: $OS_TOKEN"   http://192.169.142.127:8774/v2/b47473d8953d49b29910fc681a2ff773/flavors  | python -m json.tool

where b47473d8953d49b29910fc681a2ff773 is admin's tenant id.
image description

Take a look at posts :-
http://bderzhavets.blogspot.com/2016/04/rest-api-rdo-mitaka.html
http://bderzhavets.blogspot.com/2016/04/creating-server-via-rest-api-rdo-mitaka.html

I was able reproduce http://developer.openstack.org/api-guide/quick-start/api-quick-start.html
However , REST API requests like :-

[root@ip-192-169-142-127 ~(keystone_admin)]# curl -s -H "X-Auth-Token: $OS_TOKEN" \
http://128.136.179.2:8774/v2/$OS_TENANT_NAME/flavors \
| python -m json.tool

failed.
I got samples running after update :-

[root@ip-192-169-142-127 ~(keystone_admin)]# curl -s -H "X-Auth-Token: $OS_TOKEN"   http://192.169.142.127:8774/v2/b47473d8953d49b29910fc681a2ff773/flavors  | python -m json.tool

where b47473d8953d49b29910fc681a2ff773 is admin's tenant id.

Starting server via Chrome Advanced REST API Client POST request

image description

Take a look at posts :-
http://bderzhavets.blogspot.com/2016/04/rest-api-rdo-mitaka.html
http://bderzhavets.blogspot.com/2016/04/creating-server-via-rest-api-rdo-mitaka.html

I was able reproduce http://developer.openstack.org/api-guide/quick-start/api-quick-start.html
However , REST API requests like :-

[root@ip-192-169-142-127 ~(keystone_admin)]# curl -s -H "X-Auth-Token: $OS_TOKEN" \
http://128.136.179.2:8774/v2/$OS_TENANT_NAME/flavors \
| python -m json.tool

failed.
I got samples running after update :-

[root@ip-192-169-142-127 ~(keystone_admin)]# curl -s -H "X-Auth-Token: $OS_TOKEN"   http://192.169.142.127:8774/v2/b47473d8953d49b29910fc681a2ff773/flavors  | python -m json.tool

where b47473d8953d49b29910fc681a2ff773 is admin's tenant id.

Starting server via Chrome Advanced REST API Client Firefox RESTClient POST requestrequest

image descriptionimage description

UPDATE 04/25/2016
@Sofiane68,

1. When you obtain authentication token - http://controller:5000/v2  Keystone (httpd) is running on Controller, CONFIG_KEYSTONE_API=v2.0 was set during install.
2. If you send POST or GET to nova-api - http://controller:8774/v2  nova-api is running on Controller. Keystone public port is 5000, openstack-nova-api port is 8774.

Please, see http://lxer.com/module/newswire/view/228612/index.html
Lxer.com had me to make improvements to article during 2 or 3 days. They made about 70 moderations silently
Any given rejection I was supposed to guess which place they disliked this time. As far as it finally hit news wire means that article looks good to editorial team. It should be written good for you as well. Chrome Advanced REST Client provide a real relief, unless you run it in batch mode ( script ). I fixed confusing typo bellow just one IP address , which is Controller running keystone service ( public port 5000) and nova-api ( port 8774 )
(keystone service was included as apache wsgi in the past releases)

END UPDATE

Take a look at posts :-
http://bderzhavets.blogspot.com/2016/04/rest-api-rdo-mitaka.html
http://bderzhavets.blogspot.com/2016/04/creating-server-via-rest-api-rdo-mitaka.html

I was able reproduce http://developer.openstack.org/api-guide/quick-start/api-quick-start.html
However , REST API requests like :-

[root@ip-192-169-142-127 ~(keystone_admin)]# curl -s -H "X-Auth-Token: $OS_TOKEN" \
http://128.136.179.2:8774/v2/$OS_TENANT_NAME/flavors http://192.169.142.127:8774/v2/$OS_TENANT_NAME/flavors \
| python -m json.tool

failed.
I got samples running after update :-

[root@ip-192-169-142-127 ~(keystone_admin)]# curl -s -H "X-Auth-Token: $OS_TOKEN"   http://192.169.142.127:8774/v2/b47473d8953d49b29910fc681a2ff773/flavors  | python -m json.tool

where b47473d8953d49b29910fc681a2ff773 is admin's tenant id.

Starting server via Firefox RESTClient POST request

image description

UPDATE 04/25/2016
@Sofiane68,

1. When you obtain authentication token - http://controller:5000/v2  Keystone (httpd) is running on Controller, CONFIG_KEYSTONE_API=v2.0 was set during install.
2. If you send POST or GET to nova-api - http://controller:8774/v2  nova-api is running on Controller. Keystone public port is 5000, openstack-nova-api port is 8774.

Please, see http://lxer.com/module/newswire/view/228612/index.html
Lxer.com had me to make improvements to article during 2 or 3 days. They made about 70 moderations silently
Any given rejection I was supposed to guess which place they disliked this time. As far as it finally hit news wire means that article looks good to editorial team. It should be written good for you as well. Chrome Advanced REST Client Client provide a real relief, unless you run it in batch mode ( script ). I fixed confusing typo bellow just one IP address , which is Controller running keystone service ( public port 5000) and nova-api ( port 8774 )
(keystone service was included as apache wsgi in the past releases)

END UPDATE

Take a look at posts :-
http://bderzhavets.blogspot.com/2016/04/rest-api-rdo-mitaka.html
http://bderzhavets.blogspot.com/2016/04/creating-server-via-rest-api-rdo-mitaka.html

I was able reproduce http://developer.openstack.org/api-guide/quick-start/api-quick-start.html
However , REST API requests like :-

[root@ip-192-169-142-127 ~(keystone_admin)]# curl -s -H "X-Auth-Token: $OS_TOKEN" \
http://192.169.142.127:8774/v2/$OS_TENANT_NAME/flavors \
| python -m json.tool

failed.
I got samples running after update :-

[root@ip-192-169-142-127 ~(keystone_admin)]# curl -s -H "X-Auth-Token: $OS_TOKEN"   http://192.169.142.127:8774/v2/b47473d8953d49b29910fc681a2ff773/flavors  | python -m json.tool

where b47473d8953d49b29910fc681a2ff773 is admin's tenant id.

Starting server via Firefox RESTClient POST request

image description