Hello again,<div><br></div><div>Basically I am using Openstack itself, keystone folsom in particular. I understand then the API keys are just user's passwords?</div><div><br></div><div>Kind regards.<br><br><div class="gmail_quote">
On Fri, Feb 8, 2013 at 2:47 PM, Anne Gentle <span dir="ltr"><<a href="mailto:anne@openstack.org" target="_blank">anne@openstack.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote"><div class="im">On Fri, Feb 8, 2013 at 8:43 AM, Emilio García <span dir="ltr"><<a href="mailto:emilio.garcia@cloudreach.co.uk" target="_blank">emilio.garcia@cloudreach.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Thank your for taking your time answering.<div><br></div><div>I am aware about this not being a Zenoss list, so this was just to give a little bit of background. I can only find this sentence concerning API keys:</div>
<div>
<br></div><div><span style="font-family:Verdana,Geneva,sans-serif;font-size:13px"><i>Note: An API key — provided by some cloud providers auth systems. You or your OpenStack provider's administrator/support staff can revoke it and generate a new one. While an authentication token can have a short lifespan, an API key lasts until it is regenerated.</i></span><br>
<br>However I cannot see anywhere any reference on how to generate API keys (not tokens). It is just like some kind of holy grail which is mentioned but anyone really knows where exactly is. Am I overlooking something very obvious? Closest reference I found suggested that the API key could be just a user's password. Is that so? or is a dead end?</div>
<div><br></div></blockquote><div><br></div></div><div>API keys are specific to the provider. For example, Rackspace lets their users authenticate with either a username and password or a username and API key. See:<br><br>
<a href="http://docs.rackspace.com/servers/api/v2/cs-devguide/content/curl_auth.html" target="_blank">http://docs.rackspace.com/servers/api/v2/cs-devguide/content/curl_auth.html</a><br>
</div><div class="im"><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div></div><div>In a nutshell I am very confused about what is a API key exactly and how can they be generated (not a token).</div>
<div><br></div></blockquote><div><br></div></div><div>I think it really depends on your provider. Perhaps some others can chime in.<span class="HOEnZb"><font color="#888888"><br><br>Anne<br></font></span></div><div><div class="h5">
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div></div><div>Kind regards.<div><div><br><br><div class="gmail_quote">On Fri, Feb 8, 2013 at 2:34 PM, Anne Gentle <span dir="ltr"><<a href="mailto:anne@openstack.org" target="_blank">anne@openstack.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div>Hi Emilio, <br><br></div>This isn't exactly a Zenoss list, but look under Usage on this page:<br>
<a href="https://github.com/zenoss/ZenPacks.zenoss.OpenStack" target="_blank">https://github.com/zenoss/ZenPacks.zenoss.OpenStack</a><br>
<br></div><div>The above page doesn't clearly explain the versions of different APIs from different services. From OpenStack's release perspective for Folsom, the Identity API is currently v2 and the Compute API is currently v2 (which is identical to v1.1). So I'm not sure from the Zenoss perspective what API they are providing support for.<br>
</div><div><br></div>In the OpenStack docs, this page explains more about tokens and API keys. API keys are typically given by a particular provider. Tokens are handed out by Keystone, the Identity service under the OpenStack umbrella.<br>
<div><a href="http://docs.openstack.org/api/openstack-compute/programmer/content/getting-the-keys-to-the-kingdom.html" target="_blank">http://docs.openstack.org/api/openstack-compute/programmer/content/getting-the-keys-to-the-kingdom.html</a><br>
<br></div><div>This page describes the process of obtaining a token. <a href="http://docs.openstack.org/api/quick-start/content/index.html#Getting-Credentials-a00665" target="_blank">http://docs.openstack.org/api/quick-start/content/index.html#Getting-Credentials-a00665</a><br>
</div><div><br></div><div>Hope this helps.<br>Anne<br></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>On Fri, Feb 8, 2013 at 7:53 AM, Emilio García <span dir="ltr"><<a href="mailto:emilio.garcia@cloudreach.co.uk" target="_blank">emilio.garcia@cloudreach.co.uk</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div>Hi all,<div><br></div><div>I am trying to generate an API key for a Zenpack (Zenoss) to use the OpenStack API to gather stats. However I cannot see how to generate a API key in the documentation anywhere. How can I do that? Also is it possible to use the v1 of the API protocol in Folsom or only v2?</div>
<div><br></div><div>Kind regards.<br clear="all"><div><br></div><br>
</div>
</div></div><pre>Cloudreach Limited is a limited company registered in England with registered number 06975407
The above terms reflect a potential business arrangement, are provided solely as a basis for further discussion,
and are not intended to be and do not constitute a legally binding obligation. No legally binding obligations
will be created, implied, or inferred until an agreement in final form is executed in writing by all parties involved.
This email may be confidential or privileged. If you received this communication by mistake, please don't forward
it to anyone else, please erase all copies and attachments, and please let us know that it has gone to the wrong person.
</pre><br>_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
<br></blockquote></div><br></div></div>
</blockquote></div><br><br clear="all"><div><br></div></div></div><span><font color="#888888">-- <br><br><b>Emilio Garcia</b> <br> Systems Developer, Cloudreach Limited<br> [t] <a value="00442071833893">+44 20 7183 3893</a> (ext. 403)<br>
[m] <a value="7958 036 743">+44 7958 036 743</a><br>
<br>
</font></span></div><div><div>
<pre>Cloudreach Limited is a limited company registered in England with registered number 06975407
The above terms reflect a potential business arrangement, are provided solely as a basis for further discussion,
and are not intended to be and do not constitute a legally binding obligation. No legally binding obligations
will be created, implied, or inferred until an agreement in final form is executed in writing by all parties involved.
This email may be confidential or privileged. If you received this communication by mistake, please don't forward
it to anyone else, please erase all copies and attachments, and please let us know that it has gone to the wrong person.
</pre></div></div></blockquote></div></div></div><br></div></div>
</blockquote></div><br><br clear="all"><div><br></div> <br>
</div>
<pre>Cloudreach Limited is a limited company registered in England with registered number 06975407
The above terms reflect a potential business arrangement, are provided solely as a basis for further discussion,
and are not intended to be and do not constitute a legally binding obligation. No legally binding obligations
will be created, implied, or inferred until an agreement in final form is executed in writing by all parties involved.
This email may be confidential or privileged. If you received this communication by mistake, please don't forward
it to anyone else, please erase all copies and attachments, and please let us know that it has gone to the wrong person.