StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15770830
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-04-02T17:51:06.520
FavoriteCount
0
LastActivityDate
2013-04-02T17:51:06.520
LastEditDate
LastEditorUserId
0
OwnerUserId
798549
ParentId
15768064
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
<pre><code>http://10.0.0.2:5000/v2.0/tokens </code></pre> Likely refers to the Keystone Service API. This API authenticates you to OpenStack's keystone identity service. All REST API Services are catalogued there in the catalog service. Additionally all of OpenStack relies on keystone to authenticate all API queries. Knowing nothing about bosh the attribute 'api_key' to me requires better context. Generally OpenStack doesn't require an API Key in its own concept of API authentication. More about openstack api authentication here: <a href="http://docs.openstack.org/api/quick-start/content/index.html#Getting-Credentials-a00665" rel="nofollow">http://docs.openstack.org/api/quick-start/content/index.html#Getting-Credentials-a00665</a> However there is a concept of an API Key in relation to EC2 keys. These can be generated with this query: <pre><code>keystone ec2-credentials-create </code></pre> My guess is that's what it requires there. More alternatives there: Credentials could be in in novarc file generated for your Openstack project with nova-manage project zipfile command. This is also available from the horizon interface. Alternatively it could refer to a provider specific API Key such as rackspaces ( I doubt this ): <a href="http://docs.rackspace.com/servers/api/v2/cs-devguide/content/curl_auth.html" rel="nofollow">http://docs.rackspace.com/servers/api/v2/cs-devguide/content/curl_auth.html</a> 'default_key_name' probably refers to the name of a keypair that has been previously registered with openstack. This would be a keypair that can be injected into an image at instance run time. It should correspond to the .pem filename. The key would need to be available to your user and your tenant that you choose in the config. Check out a keypair creation / use example here: <a href="http://docs.openstack.org/developer/nova/runnova/managing.instances.html" rel="nofollow">http://docs.openstack.org/developer/nova/runnova/managing.instances.html</a> Best effort man. Hope that gives you what you need.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCloud Foundry - Installing Micro Bosh in a VM ( OpenStack )
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMatt Joyce
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COI found the answer in another question here in Stack OverFlow, the api-key is just a lame name for the password :D, you'are right about the keypair. Thanks for the help anyway :)
 singulars
 PostPostId
 PO
 UserUserId
 USuser2236681

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.