Hi guys, I have submitted a patch for this issue. Just FYI.
https://review.openstack.org/#/c/34870/ 2013/1/31 Hanyu Xiao <hanyu.x...@eayun.com> > Hi guys: > > As I know, soft-delete an instance only power off the instance and then > mark the db state to "soft-delete". > > you can use `nova start ` to poweron the instance. > > Thanks. > > On 01/31/2013 01:32 PM, Sam Stoelinga wrote: > > It seems we're using start to restore the instance, which also works. > > novaclient(request).servers.start(instance_id) > > Sam > > On Thu, Jan 31, 2013 at 10:43 AM, Vishvananda Ishaya < > vishvana...@gmail.com> wrote: > >> >> Yes I noticed the other day that the restore and force_delete admin >> commands are not in novaclient. I was planning on adding them at some point >> soon, but it should be a really easy addition if someone wants to tackle it >> before I get to it. >> >> Vish >> >> On Jan 30, 2013, at 2:24 AM, "Day, Phil" <philip....@hp.com> wrote: >> >> Hi Vish, >> >> Sorry, I wasn’t very clear in my original post. I have >> reclaim_instance_inteval set, and the instance does go to “SOFT_DELETED”. >> I can see that the api extension adds a “restore” verb to the list of >> actions on an instance. >> >> What I was trying to find out was if that additional action was >> available from the nova client. E.g is there a “nova restore <xxx>” >> command ? Looking through the client code I can’t see one, but thought I >> might be missing something. >> >> Thanks >> Phil >> >> *From:* Vishvananda Ishaya [mailto:vishvana...@gmail.com] >> *Sent:* 30 January 2013 00:32 >> *To:* Day, Phil >> *Cc:* openstack@lists.launchpad.net (openstack@lists.launchpad.net) ( >> openstack@lists.launchpad.net) >> *Subject:* Re: [Openstack] nova client support for restore from soft >> delete ? >> >> >> On Jan 29, 2013, at 8:55 AM, "Day, Phil" <philip....@hp.com> wrote: >> >> >> Hi Folks, >> >> Does the nova client provide support to restore a soft deleted >> instance (and if not, what is the process for pulling an instance back >> from the brink) ? >> >> If you have reclaim_instance_interval set then you can restore >> instances via an admin api command. If not then you are not going to have >> much luck reclaiming the insance becasue the drive will be deleted. If by >> some chance you have the backing files still, then you should be able to >> fix the db and do a hard reboot on the instance to get it to come back up. >> Fixing the db is mostly about setting deleted=False but keep in mind that >> you will also have to manually restore the vif and reassociate the fixed ip >> which hopefully hasn't been associated to a new instance. >> >> Vish >> >> >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~openstack >> Post to : openstack@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp >> >> > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > > -- > Hanyu Xiao > Eayun.com > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
