openstack team mailing list archive

["Karajgi, Rohit" <Rohit.Karajgi@xxxxxxxxxxx>]

Hi Phil,

You might want to look at 
https://blueprints.launchpad.net/nova/+spec/interim-nova-authz-service

https://github.com/openstack/nova/commits/master/etc/nova/policy.json


Regards,
Rohit Karajgi | Lead Engineer | NTT Data Global Technology Services Private Ltd | w. +91.20.6604.1500 x 378 |  m. +91 992.242.9639 | rohit.karajgi@xxxxxxxxxxx





-----Original Message-----
From: Day, Phil [mailto:philip.day@xxxxxx] 
Sent: Tuesday, July 31, 2012 8:11 PM
To: Karajgi, Rohit; Wolfgang Hennerbichler; openstack@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Openstack] Instance stuck in deleting state with error

Sorry for a dumb question, but can someone point me to where the authorization is configured to determine who does and doesn't get access to these actions please ?

Thanks,	
Phil

-----Original Message-----
From: openstack-bounces+philip.day=hp.com@xxxxxxxxxxxxxxxxxxx [mailto:openstack-bounces+philip.day=hp.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of Karajgi, Rohit
Sent: 31 July 2012 15:17
To: Wolfgang Hennerbichler; openstack@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Openstack] Instance stuck in deleting state with error

Hi Wolfgang, 

Have you updated the your python-novaclient? The 'nova reset-state <server> --active' command is pretty much there. It is an admin action in Nova extensions.
$ nova help | grep reset
    reset-state         Reset the state of an instance


Regards,
Rohit Karajgi | Lead Engineer | NTT Data Global Technology Services Private Ltd | w. +91.20.6604.1500 x 378 |  m. +91 992.242.9639 | rohit.karajgi@xxxxxxxxxxx



-----Original Message-----
From: openstack-bounces+rohit.karajgi=nttdata.com@xxxxxxxxxxxxxxxxxxx [mailto:openstack-bounces+rohit.karajgi=nttdata.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of Wolfgang Hennerbichler
Sent: Tuesday, July 31, 2012 10:45 AM
To: openstack@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Openstack] Instance stuck in deleting state with error

On 07/30/2012 09:35 PM, Kevin L. Mitchell wrote:

> That said, be aware that there is a "reset-state" command to 
> novaclient, so that you can do Chris's recommended reset without 
> having to muck around with the database directly.

where?
nova help | grep reset
yields nothing.
I think this is one of openstack worst weaknesses, that if the status of an instance is in error-state and one has to wade through a couple of logfiles (scheduler, nova-network, nova-compute) in order to find out what really happened. I would be superior if the error itself would be reported back to the database.

Wolfgang

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

______________________________________________________________________
Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data.  If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

______________________________________________________________________
Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data.  If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding