[Openstack] Keystone Identity API v3 interface
Hello. I'm trying to exploit new features of Keystone Identity API v3 in Grizzly, however I faced problems using* python-openstackclient*. If I specify to use v3 API to the *openstackclient*, it still tries to obtain tokens using v2.0 scheme and the server rejects such requests. So the first problem is -- I couldn't set up* python-openstackclient *to work with Identity API v3 (maybe any additional env variables or parameters need to be passed?). I have also tried to talk with the API server using curl, but I couldn't get detailed documentation on Identity v3 API. I found the draft API description at https://github.com/openstack/identity-api/blob/master/openstack-identity-api/src/markdown/identity-api-v3.md but managed to only obtain token. Afterwards whatever request I do (get .../v3/users for example), I get 401 Unauthorized error from the server. The example of a request I do: curl -i -H Content-Type: application/json -H Accept: application/json -H X-Auth-Token: ...PKI token obtained from X-Subject-Token header at /v3/auth/tokens/... http://localhost:5000/v3/users Could someone suggest the correct way of talking to Keystone Identity v3 API? Either configuration/parameters for correct *openstackclient *usage or plain curl requests would be highly appreciated. Thank you. -- Sincerely, Ruslan Kiianchuk. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Keystone Identity API v3 interface
Thanks a lot for the tip! Perhaps, --os-url is new parameter in *openstackclient *(can't remember it using in *keystoneclient*). By the way, a doc mentions that --os-url is a URL to OpenStack service. Do they mean URL of the Nova API on controller node or something else, do you know? On Mon, Jun 24, 2013 at 9:29 PM, Miller, Mark M (EB SW Cloud - RD - Corvallis) mark.m.mil...@hp.com wrote: I struggled figuring out the v3 syntax myself. Here is the same command in v2.0 and v3 format: ** ** openstack --os-token 012345SECRET99TOKEN012345 --os-auth-url http://15.253.57.115:35357/v3; --os-url http://15.253.57.115:35357/v3; --log-file /var/log/os.log --os-identity-api-version 3 role list openstack --os-token 012345SECRET99TOKEN012345 --os-auth-url http://15.253.57.115:35357/v2.0; --os-url http://15.253.57.115:35357/v2.0; --log-file /var/log/os.log --os-identity-api-version 2.0 role list ** ** Mark ** ** ** ** *From:* Openstack [mailto:openstack-bounces+mark.m.miller= hp@lists.launchpad.net] *On Behalf Of *Ruslan Kiianchuk *Sent:* Monday, June 24, 2013 11:09 AM *To:* openstack@lists.launchpad.net *Subject:* [Openstack] Keystone Identity API v3 interface ** ** Hello. ** ** I'm trying to exploit new features of Keystone Identity API v3 in Grizzly, however I faced problems using* python-openstackclient*. If I specify to use v3 API to the *openstackclient*, it still tries to obtain tokens using v2.0 scheme and the server rejects such requests. So the first problem is -- I couldn't set up* python-openstackclient *to work with Identity API v3 (maybe any additional env variables or parameters need to be passed?). ** ** I have also tried to talk with the API server using curl, but I couldn't get detailed documentation on Identity v3 API. I found the draft API description at https://github.com/openstack/identity-api/blob/master/openstack-identity-api/src/markdown/identity-api-v3.md but managed to only obtain token. Afterwards whatever request I do (get .../v3/users for example), I get 401 Unauthorized error from the server. The example of a request I do: ** ** curl -i -H Content-Type: application/json -H Accept: application/json -H X-Auth-Token: ...PKI token obtained from X-Subject-Token header at /v3/auth/tokens/... http://localhost:5000/v3/users ** ** Could someone suggest the correct way of talking to Keystone Identity v3 API? Either configuration/parameters for correct *openstackclient *usage or plain curl requests would be highly appreciated. ** ** Thank you. ** ** -- Sincerely, Ruslan Kiianchuk. -- Sincerely, Ruslan Kiianchuk. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [metering] Ceilometer plugin for VM provisioning metrics
Thank you for the help! There were issues with versioning (I have to run Ceilometer with Folsom OpenStack version) so few lines of code had to be changed for successful porting. Now everything works. Yet, another question arose, weather I can ignore some events from the RPC bus in process_notification() method or any other way? On Wed, May 15, 2013 at 2:22 PM, Julien Danjou jul...@danjou.info wrote: On Tue, May 14 2013, Ruslan Kiianchuk wrote: Could you please help on how the listener plugin is supposed to be created? There are good chances I have some misunderstandings in the concept of Ceilometer plugins. No, you got everything right! You should start by checking if your plugin is loaded by running ceilometer-collector with -v option I guess. Then I'd try to see if nova is really sending those messages on the RPC bus. -- Julien Danjou ;; Free Software hacker ; freelance consultant ;; http://julien.danjou.info -- Sincerely, Ruslan Kiianchuk. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] [metering] Ceilometer plugin for VM provisioning metrics
Hello. The task I'm trying to implement is gather provisioning metrics from OpenStack VMs using Ceilometer. Precisely, I need to provide time of execution for the provisioning tasks *scheduling, **spawning, networking *via Ceilometer. After reading Ceilometer and Nova documentation I figured out that Nova could already provide the needed events with the following configuration: notification_driver = nova.openstack.common.notifier.rabbit_notifier,ceilometer.compute.nova_notifier notify_on_state_change = vm_and_task_state This should make Nova generate corresponding events with compute.instance.update event type. So I guess there is no need to implement pollster plugin in this case, but listener plugin still needs to be implemented. From what I understand, it should be implemented in ceilometer/compute/notifications.py to process events that Nova sends to RabbitMQ. I've tried to do so similarly to already existing plugins in notifications.py and added it as an entry point in setup.cfg (ceilometer.collector section) but couldn't see any changes after reinstalling and restarting Ceilometer services. Could you please help on how the listener plugin is supposed to be created? There are good chances I have some misunderstandings in the concept of Ceilometer plugins. Thank you! -- Sincerely, Ruslan Kiianchuk. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
