Re: [openstack-dev] [Nova] shelved_offload_time configuration

2015-01-08 Thread Kekane, Abhishek
Hi Joe,

Thanks for update.

I am working on nova-specs to improve the performance of unshelve api 
https://review.openstack.org/135387
In this spec, I am proposing not to take snapshot if shelved_offload_time is 
set to -2.

As of now the logic of creating the image is on the controller node, where I 
cannot take the decision whether to take snapshot or not as this 
shelved_offload_time is not exposed to controller node.

Please review the specs and let me know your suggestions on the same.

Thank You,

Abhishek Kekane

From: Joe Gordon [mailto:joe.gord...@gmail.com]
Sent: 07 January 2015 22:43
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Nova] shelved_offload_time configuration



On Mon, Dec 22, 2014 at 10:36 PM, Kekane, Abhishek 
abhishek.kek...@nttdata.commailto:abhishek.kek...@nttdata.com wrote:
Hi All,

AFAIK, for shelve api the parameter shelved_offload_time need to be configured 
on compute node.
Can we configure this parameter on controller node as well.

Not 100% sure what you are asking but hopefully this will clarify things: 
nova.conf files are read locally, so setting the value on a controller node 
doesn't affect any compute nodes.


Please suggest.

Thank You,

Abhishek Kekane

__
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.

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
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.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Nova] shelved_offload_time configuration

2015-01-07 Thread Joe Gordon
On Mon, Dec 22, 2014 at 10:36 PM, Kekane, Abhishek 
abhishek.kek...@nttdata.com wrote:

  Hi All,



 AFAIK, for shelve api the parameter shelved_offload_time need to be
 configured on compute node.

 Can we configure this parameter on controller node as well.


Not 100% sure what you are asking but hopefully this will clarify things:
nova.conf files are read locally, so setting the value on a controller node
doesn't affect any compute nodes.




 Please suggest.



 Thank You,



 Abhishek Kekane

 __
 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.

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [Nova] shelved_offload_time configuration

2014-12-22 Thread Kekane, Abhishek
Hi All,

AFAIK, for shelve api the parameter shelved_offload_time need to be configured 
on compute node.
Can we configure this parameter on controller node as well.

Please suggest.

Thank You,

Abhishek Kekane

__
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.___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev