Creating Servers via REST API on RDO Mitaka && Keystone API V3

As usual ssh-kepair for particular tenant is supposed to be created sourcing tenant’s credentials and afterwards it works for particular tenant. By some reasons upgrade keystone api version to v3 breaks this schema in regards of REST API POST requests issued for servers creation. I am not sure either following bellow is workaround or it is supposed to work this way.

Assign admin role user admin on project demo via openstack client

[root@ip-192-169-142-127 ~(keystone_admin)]# openstack project list| \
grep demo > list2

[root@ip-192-169-142-127 ~(keystone_admin)]#openstack user list| \
grep admin >> list2

[root@ip-192-169-142-127 ~(keystone_admin)]# openstack role list|\
grep admin >> list2

[root@ip-192-169-142-127 ~(keystone_admin)]# cat list2
| 052b16e56537467d8161266b52a43b54 | demo |
| b6f2f511caa44f4e94ce5b2a5809dc50 | admin |
| f40413a0de92494680ed8b812f2bf266 | admin |

[root@ip-192-169-142-127 ~(keystone_admin)]# openstack role add \
–project \
052b16e56537467d8161266b52a43b54 \
–user b6f2f511caa44f4e94ce5b2a5809dc50 \
f40413a0de92494680ed8b812f2bf266

*********************************************************************
Run to obtain token scoped “demo”
*********************************************************************

# . keystonerc_admin
# curl -i -H “Content-Type: application/json” -d \
‘ { “auth”:
{ “identity”:
{ “methods”: [“password”], “password”:
{ “user”:
{ “name”: “admin”, “domain”:
{ “id”: “default” }, “password”: “7049f834927e4468” }
}
},
“scope”:
{ “project”:
{ “name”: “demo”, “domain”:
{ “id”: “default” }
}
}
}
}’ http://192.169.142.127:5000/v3/auth/tokens ; echo

Screenshot from 2016-04-28 19-47-00

Created ssh keypair “oskeydemoV3” sourcing keystonerc_admin

Screenshot from 2016-04-28 19-50-02

Admin Console shows

Screenshot from 2016-04-28 20-28-57

***************************************************************************************
Submit “oskeydemoV3” as value for key_name into Chrome REST Client environment && issue POST request to create the server , “key_name” will be accepted ( vs case when ssh-keypair was created by tenant demo )
*************************************************************************************

Screenshot from 2016-04-28 19-52-24

Now log into dashboard as demo

Screenshot from 2016-04-28 19-56-25

Verify that created keypair “oskeydemoV3” allows log into server

Screenshot from 2016-04-28 19-58-56

4 Responses to Creating Servers via REST API on RDO Mitaka && Keystone API V3

  1. Very good info. I was pleased to stumble on this since I was also born in New York City. furthermore, we appreciate your seeing San Francisco and letting me to better have an understanding of baking skills. This really helped me with my entrance to University of Alabama. Looking forward to seeing you in our store and catch up with our hockey game.

  2. Hello. I have not been on this site since summer. It was basically because I was taking a trip to Sydney because of my contract at Coca-Cola Enterprises. This requires a whole lot of time from me, however I still think about your document. I remember our days at Columbia College (MO) in Florida. So thrilled that we had a opportunity to have fun close the pool. If you please forward my thanks to linda as well as mike. Cya

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: